Hi,
We are actually doing this for all of our customers. First note: The figures you pull from the ERP system should always be balanced!
How this could be configured in OneStream: We generally configure this in a UD dimension; in our default setup, this is UD1. In this UD, we are distinct by where the data is coming from. There is a member for Local input (usually a combination of import from the ERP + some entries done using cube views). On top of that, there are more UDs, which, in general, are journals that are posted for top-sided adjustments. This way, you can distinguish what was done in Onestream from what is coming from the local ERP.
When implementing this, I always propose a few best practices or rules:
- No entries in parents in the entity dimension.
- Try to keep the bookings to a minimum. Your current approach (everything is posted in the ERP) is, for me, the best practice.
With kind regards,
Tim