Derivative Object Maps
Derivative object maps are used by Get SAP Objects actions to allow objects of the same type, but with different names to be retrieved for comparison. This allows customized objects to be compared with their standard SAP equivalents.
Derivative object maps are specified using a Table parameter or dataset with the following columns:
| Column | Description |
|---|---|
| NAME1 | The name of the object in the first system to be compared. This system is specified in the RFC Destination1 property of the Get SAP Objects action. |
| NAME2 | The name of the object in the second system to be compared. This system is specified in the RFC Destination2 property of the Get SAP Objects action. |
| TYPE | The type of the object to be compared. |
Object names should be specified using UPPER CASE.
Some object names have two components, for example Data Source 7.0 (RSDS) objects have a Data Source and a Source System. To use these object names in a derivative object comparison, use a space to separate the component parts in the NAME1 and NAME2 fields, for example:
PLANDATALOAD3 SAP_DEMO
Example:
The following derivative object map allows the transactions VA01 and ZVA01 to be compared.
| NAME1 | NAME2 | TYPE |
|---|---|---|
| VA01 | ZVA01 | TCOD |
At least one object from the derivative object map should be specified in either the Objects, Selects or IMG Select List parameter supplied to the Get SAP Objects action. If both objects are specified, and they can each be retrieved from both compared systems, the Hierarchy dataset that stores the retrieval results includes the following objects:
<NAME1 in Sys1> (<NAME2 in Sys2>)
In the above example, transaction VA01 from the first system is compared with transaction ZVA01 from the second system.
<NAME2 in Sys1> (<NAME1 in Sys2>)
In the above example, transaction ZVA01 from the first system is compared with transaction VA01 from the second system.
<NAME1>
In the above example, transaction VA01 is compared on each of the systems.
<NAME2>
In the above example, transaction ZVA01 is compared on each of the systems.
Derivative object maps may be used to compare two objects from the same system. However, in this case you should create two separate RFC Destinations for the system and link these to the RFC Destination1 and RFC Destination2 properties for the Get SAP Objects action. If only one RFC Destination is used, the objects will be marked as being the same in LiveCompare’s Tier1 comparison results.