Pre-implementation Notes
Audit Trail cube will allow to check status of roundtrip across FIN Version, T Year-Month (we have issue with having two different dimension for time in roundtrip objects), FIN Company, FIN Consolidation Value Measure (by default we are loading data descending from CON, so this must be ensured to be present when writing the status).
Status will be measure with numeric codes in ascending order, so we can calculate min and max within certain rollups to see if status codes are consistent. That means the code needs to be a measure rather than a dimension. We can use ConsolidatedMax and ConsolidatedMin functions to see both min and max status code values. If they are equal then we know status codes are consistent. A good prerequisite will be to have non-zero status codes so if min=0 we would know there are some nodes in un-initialized state. This would work nicely with ViewZeroOut. We need to have some free codes between each roundtrip step to allow adding new steps.
Open questions:
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.
How do we link the process name with status code - it would be good to avoid hardcoded values