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
Org-by-period Consolidation | Eliminations
Good Day, In order to implement Org-by-period Consolidation, you need to set the Consolidation View to Periodic so that the correct Share for e.g. the income statement can be calculated for only the...
KarlT
OneStream Employee
OneStream EmployeeHi Chris, Do you have any change in the ownership of the entity or IC partner in Feb with your example?
Hi,
No changes in ownership. Doing regression testing on an entity where ownership didn't even change.
From OneStream support this is because even if data is loaded YTD, because there is no movement periodically, there will be no elimination.
So basically what is in the guide: If a Consolidation View is Periodic and no data is loaded to the IC accounts for a specific month, custom elimination rules are required in the FinanceFunctionType.ConsolidateElimination section of a business rule attached to the cube to calculate expected elimination results. This requires storaging the C#Share member, which impacts overall consolidation performance"
However, the sentence is incomplete in the guide, because we have data loaded, just in YTD. So they should state that "...no data is loaded in periodic view to IC accounts...." or something.
The system behaviour is completely illogical to me where you are loading data YTD. As most entities load actuals YTD and would require org-by-period. So saying that you need custom rules to make this work, makes the org-by-period consolidation algorithm redundant.