Show TOC Start of Content Area

Background documentation Inner Node Assignments and Internal Leaf Nodes  Locate the document in its SAP Library structure

Recall that for proper organization of the records within an MDM repository, a hierarchy lookup field can normally be assigned only to the value of a leaf node in the hierarchy.

Sometimes, however, remote systems may have records with inner node assignments, in which the lookup field is assigned to the value of an internal (that is non-leaf) node. Moreover, you may wish to preserve these inner node assignments during inbound processing of records and/or to create inner nodes and assign records to them during data editing, for subsequent syndication of records having inner node assignments back to the remote system.

MDM supports inner node assignments indirectly – while preserving the rule that a hierarchy lookup field be assigned only to a leaf node in the hierarchy – using an internal leaf node, a special type of leaf node that represents the internal parent node immediately above it.

You can then make inner node assignments to the parent by assigning records to the internal leaf – which acts as a proxy for the parent for assignment purposes – just as you would assign records to any other leaf node (for more information, see Creating an Internal Leaf Node).

Note

You can search for records having an inner node assignment by selecting the internal leaf node in the hierarchy of lookup table values in the Search Parameters tab.

Internal leaf nodes dovetail with the Partition and Consolidate Children commands in Taxonomy mode, which interpret records having a NULL-valued partitioning attribute as having inner node assignments corresponding to an internal leaf node, and vice versa. (For more information, see Partitioning a Category and Consolidating Categories).

 

End of Content Area