Siebel Customer-Centric Enterprise Warehouse Installation and Configuration Guide > Configuring Common Components of the Siebel Customer-Centric Enterprise Warehouse > Configuring Conformed Dimensions >

About Specifying Correct Entity Cross-References in Flat File Uploads

It is recommended that you specify an entity type for the Reference Dimension ID when updating the Cross Reference Entities table (IA_XRF_ENTITIES) from a flat file. If you use random dimensions as the Reference Dimension ID, you risk making a cyclic reference in IA_XRF_ENTITIES, in which case the M_PLP_XRF_ENTITIES_CONSOLIDATION mapping creates a partial or incorrect cross-reference.

Figure 38 depicts a correctly structured flat file that matches the Base Dimension ID to the Reference Dimension ID, enabling a proper update to the IA_XRF_ENTITIES table. In the first row, the flat file shows that Supplier1 is the same entity as Customer1. The corresponding update to the IA_XRF_ENTITIES table updates the second row, changing Supplier1's ENTITY_KEY to be the same as Customer1. Supplier1 and Customer1 now share the same ENTITY_KEY— Entity1.

The next row in the flat file indicates that Employee1 is also the same entity as Customer1 (and, therefore, as Supplier1). The corresponding update to the IA_XRF_ENTITIES table updates the third row, changing Employee1's ENTITY_KEY value to Entity1, matching that of Customer1 and Supplier1.

Figure 38. Successful Update of IA_XRF_ENTITIES Using the Same Entity Type as the Reference Dimension

Figure 39 depicts what happens if the entities used as Reference Dimension IDs in the flat file are cyclic from the definition. Supplier1, Employee1, and Customer1 are all still the same entity, as they were in the Figure 38. However, in the previous example, the Customer entity was consistently used as the Reference Dimension, whereas in Figure 39, the Supplier entity is used once and the Customer entity is also used only once.

The first row of the flat file links Employee1 to Supplier1. The corresponding update to the IA_XRF_ENTITIES table changes the ENTITY_KEY of Employee1 to Entity2, matching the ENTITY_KEY value of Supplier1. The second row of the flat file links Supplier1 to Customer1. The corresponding update to the IA_XRF_ENTITIES table changes the ENTITY_KEY column of Supplier1 to the value of Entity1. The cross-reference, then, is only partial—it identifies Supplier1 and Customer1 as the same entity, but fails to indicate that Employee1 is yet another role played by that very same entity.

Figure 39. Unsuccessful Update of IA_XRF_ENTITIES Caused by Cyclic Reference

NOTE:  After loading cross-references, make sure all relationships are accurately defined.