- 17.9K All Categories
- 3.4K Industry Applications
- 3.3K Intelligent Advisor
- 63 Insurance
- 536.4K On-Premises Infrastructure
- 138.3K Analytics Software
- 38.6K Application Development Software
- 5.8K Cloud Platform
- 109.5K Database Software
- 17.5K Enterprise Manager
- 8.8K Hardware
- 71.1K Infrastructure Software
- 105.3K Integration
- 41.6K Security Software
We're currently updating some rules for an existing application that has the OrgbyPeriod set to Yes. However, the setting for the Actual scenario are:
They have some companies as subsidiaries and others as associates that didn't consolidate, so there were not any problems.
But now they are acquiring some of the associated companies, and these companies that were in HFM are naturally bringing the YTD results. In this case, we need them to start with a beginning balance of 0, but not to lose their history in the other hierarchy (the ones for associates).
We're thinking in disabling the OrgByPeriod (it hasn't been used and is not really configured properly) and maybe creating a new entity or renaming the existing one (that is a practice more common in Essbase). Additionally, they are going to merge all their current companies in one so they will have keep the holding and a single company that will fusion all the existing companies. And this will happen in the next few months.
Do you have any experience with disabling OrgbyPeriod? Is there any recommended process to handle these fusions and mergers? We're also thinking in adjusting the data with journals.
We'd really appreciate your feedback.