Configuring Subscription for Alternate Hierarchies.
We are currently using the Main hierarchy and multiple Alternate Hierarchies (IFRS, RBC2, and OCBC) within the target viewpoint.
Is there any recommended approach for configuring a subscription from the source viewpoint so that data is simultaneously loaded into both the Main hierarchy and the Alternate Hierarchies in the target viewpoint?
Additionally, for the Alternate Hierarchies, the parent nodes may either:
- Follow a naming convention such as Source Parent name followed by _IFRS, _RBC2, and _OCBC
- Parent Name as per above point doesn't exist in certain scenarios within the target viewpoint.
How should the subscription be configured to handle these conditions effectively and ensure the hierarchy relationships are maintained correctly?
Tagged:
0