Hierarchy Datasets

Hierarchy datasets are populated by LiveCompare actions where the results are stored as a hierarchy of objects. Hierarchy datasets store the results of retrieval, comparison or filter actions. For example, the Make Hierarchy action may be used to create a Hierarchy dataset from a table of objects retrieved from SAP.

When a Hierarchy dataset is populated, the dataset node in the workflow diagram is labeled to indicate the number of result sets that were retrieved, compared or filtered. Each result set corresponds to the type of object that was retrieved, compared or filtered, for example, ‘Transaction Results’. There is also a result set for ‘All Objects’.

To examine the contents of a Hierarchy dataset, double-click the dataset node in the workflow diagram, or choose ‘View Details’ from the node’s context menu.

Hierarchy datasets have the following structure (result sets are shown in bold):

<Dataset Name> (Data Set)

All Objects

...

<Object Type> Results

...

Select an object from the hierarchy to display its comparison details in the Details Pane.

The <Object Type> Results folders in the hierarchy store retrieval or comparison results for each individual object type. If an Object Type <Results> folder contains comparison results, each object in the hierarchy is marked with either one or two icons to indicate its comparison status.

Icon	Description
	The object is the same in each of the compared systems (Same).
	The object is different in each of the compared systems (Different).
	The object exists in the first compared system only (In1).
	The object exists in the second compared system only (In2).
	The object was not compared (NotCompared).
	The object could not be compared (CantCompare).
	For Table Key comparison results, this comparison status indicates that no rows matching the table key could be found in either system (NotIn1Or2).

Icons in hierarchy datasets reflect the actual comparison status of objects. This is independent of the Details pane display, which may be affected by your ‘Attribute Filtering’ user preference or by a workflow’s Object Attribute Filter. For example, an object with the same code and different attributes will be marked with a icon in a Hierarchy dataset that stores comparison results. However if the different attributes are excluded by an Object Attribute Filter, the Details pane will show the object as being the same.

If an object is marked with two comparison status icons, the icon on the left indicates the rolled-up comparison status of the object’s children, and the icon on the right indicates the object’s local comparison status. For objects with ‘Details’ subfolders, the icon on the right indicates the comparison status of the entire object.

The rolled-up comparison status for an object O is calculated as follows. In the following, objects without comparison statuses are ignored:

If every object beneath O is NotCompared, then O’s rolled-up comparison status is NotCompared.
If every object beneath O is In1 or NotCompared, then O’s rolled-up comparison status is In1.
If every object beneath O is In2 or NotCompared, then O’s rolled-up comparison status is In2.
If every object beneath O is Same or NotCompared, then O’s rolled-up comparison status is Same.
If any object beneath O is different, then O’s rolled-up comparison status is Different.
If none of the above is true, and the objects beneath O are any of In1, In2, Same, CantCompare or NotIn1Or2, then O’s rolled-up comparison status is Different.
If there are no comparison statuses beneath O, then O has no rolled-up comparison status.

If an object is marked with a single comparison status icon, it may be:

An object with no children, in which case the icon represents the object’s local comparison status, or
A container object, in which case the icon represents the rolled-up comparison status of the object’s children.

SAP tables are compared as follows:

Table1 <Sys1>	Table2 <Sys2>	Comparison Status
Exists but has no rows	Exists but has no rows
Does not exist	Does not exist
Has rows	Does not exist or has no rows
Does not exist or has no rows	Has rows
Exists but has no rows	Does not exist
Does not exist	Exists but has no rows

Notes

When Programs are compared in the hierarchy component, blank lines and comments are ignored when determining their comparison status. However, blank lines and comment differences are considered in the more detailed comparison results available for individual objects.

If a Table exists on each of the compared systems, and a Table Key for the Table exists in one system only, the Table Key is marked as different in the hierarchy. However, the comparison details for the Table Key will indicate that it exists in either the first or second compared system.

Specifications for Transport Table Keys retrieve the Transports that match the specification into the hierarchy. All the Transport Table Keys for the specified Transports are retrieved.

<Dataset Name> (Data Set)