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
Elena
2 years agoNew Contributor II
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...
- 2 years ago
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.
Elena
2 years agoNew Contributor II
Now, when the entity is in the desired place, I can update its relationship properties in both hierarchies. Also, the consolidation view should be switched to Periodic. What consequences should I anticipate after changing the Consolidation View for the Scenario from YTD to Periodic in the application with existing data?
- JackLacava2 years ago
OneStream Employee
That's above my paygrade 😅 I would say take backups and test in your development environment. Changing the consolidation view will very likely impact a lot of rules though, assuming a moderately complex application.
- Elena2 years agoNew Contributor II
Thank you, Jack! I'll test and share the results here.
Related Content
- 1 year ago
- 10 months ago
- 2 years ago
- 4 years ago