The OneStream Community is temporarily frozen until June 29th due to the ongoing maintenance. Please read the blog post here to learn more.
Forum Discussion
Solved
Org-By-Period in multi-cube application
Has anyone gained experience with the 'org-by-period' consolidation in a multi-cube application? We are currently addressing changes in organizational structure. Specifically, we need to consolidate...
The recommended approach here would be to rename the entity in the old segment relationship to be a historical member and then create the entity in the new segment with the current name. Since the Entity is rolling to the Tot_Org from two different sub-cubes the org-by-period functionality cannot be applied. For this functionality to work with the appropriate multiple relationships and consolidation percent settings, the entity needs to reside in the same cube. From there the entity could have relationships to different parent cubes. So an option would be to have a 3 tiered cube structure, where the base entity would be connected to a higher level segment cube with varying time/consolidation properties.
To sum up, having the same entity in two cubes doesn't appear to be a viable option unless I overlooked any crucial settings or configurations.
The below error popped up during consolidation after I updated Relationship Properties in both hierarchies, changed Consolidation Algorithm Type to 'Org-By-Period Elimination' in all cubes, and set Scenario's Consolidation View to 'Periodic':
I am going to add a new entity to solve this. Meanwhile I would appreciate it if anyone with experience in multi-cube applications could share their insights and advice on the best approach to consolidating one entity in one cube for part of the year and in another cube afterward.
The recommended approach here would be to rename the entity in the old segment relationship to be a historical member and then create the entity in the new segment with the current name. Since the Entity is rolling to the Tot_Org from two different sub-cubes the org-by-period functionality cannot be applied. For this functionality to work with the appropriate multiple relationships and consolidation percent settings, the entity needs to reside in the same cube. From there the entity could have relationships to different parent cubes. So an option would be to have a 3 tiered cube structure, where the base entity would be connected to a higher level segment cube with varying time/consolidation properties.
Ryan, many thanks for your help on this.