Assigning relationships - for time entites

Assigning relationships

Each member of the child entity must have a parent from the parent entity. For example, considering the MonthàYear relationship, each month (Jan.09, Feb.09, etc) is related to a Year (2009). When there is a missing childàparent relationship, the item in the child entity is called an orphan. Relationships between the standard time entities are managed by Board, which grants integrity and absence of orphans. When custom time entities are used, you must make sure that there are no orphans for all existing childàparent relationship.

 

Relationships between members of a child and parent entity can be assigned either manually, one by one selecting for each child member its parent, or through a DataReader that reads a file containing the child codeàparent code information. Refer to the DataReader section for more details on loading relationships from an external file.

 

To assign a relationship manually, go to the relationships window

On the child entity row, click the name of the desired parent entity. For example, to assign MonthàSeason relationship, click Season on the Month row.

 

Clicking the entity opens a window listing all child entity members with the related parent in case a relationship already exists.

Select the child member you wish to define a parent for. In the illustrated example, we click on May.04 to assign it to a season.

The member’s list of the parent entity is displayed. Choose the desired item.

 

Note:

After manually assigning relationships, click the Scan button to verify that all members of a child entity are assigned to a parent. The scan function highlights in red entities that have undefined relationships (orphan items).