Each entity type has a code that derives from the data analysis and the design. John choses to use Product as one type, and Product Group as another.

This code must be referenced in the corresponding RBO base object table. In this example, the code Product is referenced in the C_RBO_BO_CLASS table. The value of the BO_CLASS_CODE is ‘Product’.

The following table shows the relationship between the

HM

entity objects and

HM

relationship objects to the RBO tables:

Object	Table	Relationship
Product Entity Object	BO_CLASS_CODE	many-to-one (from object to table)
Product Relationship Object	C_RBO_BO_CLASS	many-to-one (from object to table)
	C_RBO_HIERARCHY	one-to-one (from table to object)

When John has completed all the steps in this section, he will be ready to create other HM components, such as packages, and to view his data in the HM. For example, the following graphic shows the relationships that John has set up in the Hierarchies Tool, displayed in the Hierarchy Manager. This example shows the hierarchy involving Mice devices fully. For more information on how to use Hierarchy Manager, see the

Multidomain MDM Data Steward Guide

.