...
Do we need to put the status into each intersection that has been processed? I guess no, because it would not be filled for combinations that have no data - this would mean we would never be able to close certain steps.
We need to ensure data in Audit Trail cube get properly cleared when running a step so all descendants of FIN Company and FIN Consolidation Value Measure will get cleared (per process parameters).
The technical solution would be to use a snippet that will be a standard part of roundtrip process.
No, we implement this into main wrapper.
How do we link the process name with status code - it would be good to avoid hardcoded values, but we can’t use a process name, since we are using the same process in different roundtrip steps
The easiest would be to use existing roundtrip step dimension, that would simply define status code, but there would be issue with running the process outside main wrapper, as this is the only component that knows which roundtrip step we are processing, the process itself doesn’t know it and doesn’t have any parameters that would contain this information.
We could have an additional field in Roundtrip Control cube that would allow to setup the associated status code with each step so the link would be obvious and easily configurable.