This can be seen through the Review Data loads function – CoreBUILD / Cubes / Review Data Loads. Alternatively you could double click on a cube directly via the navigation panel on the lefthand side and browse the cube. You can also review the reconcilation report via the data workflow task.
A base cube load brings data from source into CoreBIS. The base cubes are completely made up of business dimensions and represent business data. Updating a tagged cube takes data from the base cube and transforms it using the tagging data to populate the sbr dimensions. Once tagged the data is ready for mapping.
The frequency of updates is controled via the Dimension or Cube screens in CoreBUILD. Updating dimensions daily will cause no issues, it will check the source each night and update the lists to reflect any new elements. Updating cubes Daily could cause issues though, the data volumes associated with monthly snapshot data can cause issues […]
A dimension update is the structure data. Lists of accounts, cost centres, etc. Loading cube data is the period specific data. January Balances, etc. If a cube load is bringing data into CoreBIS for an element (i.e account) that does not exist an error will occur. For this reason we always update dimensions before cubes.
BASE_Entity is mantained just like any other dimension in the CoreBUILD > Dimension screen. If you are required to report both Level 1 and Level 2 for a form, rather than duplicate all the source data we idenitify the level 2 differences via tagging and add them to level 1 to report the total for […]
Mapping needs to be updated when; a) a new attribute is to be mapped on the form. b) a change to the form mapping is required due to an error
Tagging needs to be updated when; a) a new element is added to the business dimension used in that sbr dimensions tagging. b) A change to the tagging is required due to a mistake or a reclassification is require due to an APRA ruling. c) a new form version has been released and there is […]
Yes, new requirements for tagging can be added in advance of the form requiring it as it will not affect existing tagging. Provided those changes can be made and applied to the current period without issue.
No, the workflow will need to roll forward to the next period before you can make changes. Any changes made in the current period will affect the current period.
Yes you can, so long as the tagging version is not locked