OBIA 11g - GL Segment Dimensions DO NOT support multiple parent hierarchy rolling to same top most node

Business Intelligence Applications Consumer - Version 11.1.1.7.1 and later
Information in this document applies to any platform.
This applies to the following source systems:
EBS 11.5.1.0 and higher
PSFT 9.0 and higher
Fusion Apps 11.x
The GL Segment Dimensions are not loaded with hierarchy data having multiple parents rolling up to same top most node.

Considering the scenario as follows for an example with EBS source:

The hierarchy set up in EBS is as follows:

Top	#2	#3	#4	#5
100000	110000	111100	111111
100000	110000	111000	111100	111111
100000	111000	111100	111111
100000	111100	111111

The node 111100 has multiple parents like 110000 and 111000 rolling up to the same top most node 100000.

The OOTB load plan task SIL_GLSegmentDimensionHierarchy_Delete runs the following query after populating the W_GL_SEGMENT_DHS from the source:

DELETE FROM W_GL_SEGMENT_DHS
WHERE (hierarchy_id, hierarchy_version, hierarchy_lov_id,datasource_num_id)
IN (
SELECT hierarchy_id, hierarchy_version, hierarchy_lov_id, datasource_num_id
FROM TEST_DW.W_GL_SEGMENT_DHS
GROUP BY integration_id, hierarchy_id, hierarchy_lov_id,hierarchy_version, datasource_num_id
HAVING COUNT (1) > 1
);

This query deletes/removes all the records from the W_GL_SEGMENT_DHS table which have multiple parent records rolling up to same top most node i.e. 100000 in above example.

Hence the W_GL_SEGMENT_DH table will further not have these records.

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

This is applicable to following tables:

W_GL_SEGMENT_DH

W_COST_CENTER_DH

W_NATURAL_ACCOUNT_DH

W_BALANCING_SEGMENT_DH 

Solution

The current versions of BI Apps DO NOT support this kind of hierarchy with records having multiple parents rolling up to the same top most node.