Entity Name Changes
Hi Team,
I would like to understand how you are managing the Entity changes on a monthly basis.
For eg: the Entity name in 2021 M6 is San_Jose_213 and it is changed to SFO_213 in 2021 M7. If I ch...
Forum Discussion
Satish
Based on my understanding from your comments, here are a couple of ideas:
The integration between your ERP and OneStream should always be using unique codes which would never change. For example your entity San_Jose_213 would be constructed like this:
Entity Code: 213 (Name in OneStream)
Entity Name: San_Jose_213 (Description in OneStream)
So if there is a legal entity name change in your ERP, the code 213 will still be the same in both ERP and OneStream. You’ll only update the Description in OneStream. This way your AcctRec would be done using the code 213 always.
OR
You can create a parent entity hierarchy like this:
Parent_SFO_213_San_Jose_213
- San_Jose_213 (Load data upto 2021 M6 here)
- SFO_213 (Load data from 2021 M7 here)
Sai
Hi Sai,
Thanks for your reply. Your suggestion won’t work in my case.
Let me explain with an example.
Parent Entity - SFO
Child Entities - SFO_210; SFO_211 and San_Jose_213.
Business users performed Account Reconciliation till 2021M6 under the entity name San_Jose_213 (ID - 11225). In 2021M7 rollover, the Corporate team decides to change the Entity name to SFO_213 (ID - 11338).
So if user want to see the historic data up to 2021M6, the entity should display as San_Jose_213 whereas from 2021M7 onwards it should be shown as SFO_213.
I would like to understand how other organizations using OS for their Account reconciliation are managing this issue.
We have used custom tables in our solution to store additional attributes provided by users as part of substantiation. I need some guidance on how to handle this scenario