Solved
Central Import and Account Reconciliations
I’m starting an Account Reconciliations implementation and the current process loads Actuals for all entities through a central import. They do have individual workflows for each entity where securit...
That is correct. I personally don't like the native central load functionality in OneStream for precisely this reason, as you lose ability to interrogate the imported data at the Workflow level.
What I like to do is set up a central load based on a centralized batch process which takes the data for all entities and then hands off the loads to each entity workflow based on the Entity associations. This has a number of benefits:
- You always have visibility of the imported data at the individual workflow level.
- Validation errors / missing mappings etc only stop the load for data associated with a specific Workflow not the entire central load as happens with the native Central Import.
- If you have large volumes of data being imported you can take advantage of the in built parallelism option present in the BRApi BatchHarvest method.
- You have the ability to import data through individual workflows alongside the central load function if required
