Ensure the data source load is adjusted to accommodate the newly added field of data. e.g. if the cube is sourced from an ODBC link, then the SQL statement will need to be updated to accommodate the additional field.
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.
This button executes the overnight update procedure manually. The process looks for any cubes that are to be updated today. So if the “Auto Update” is set to “Y” then the process will review the “Update Frequency” and “Update Start Date” to determine if this cube should be updated, and if so will load data.
When creating a BASE cube the maximum dimensions that can be selected is 50. The maximum of 40 SBR dimensions can be added to a Tagged cube. If more are required it is suggested that the cube be split up into more detailed subject areas.