Generate Data Integration Layer -- Errors

Generate Data Integration Layer -- Errors

  1. Click on "Generate Data Integration Layer"
  2. Select Staging Fact Tables to Validate, then Click on "Step 1: Validate Staging Data"
  3. An error message should pop up indicating we detected errors, with a list of missing dimensional data, a list of non-matching calculations on the Stage_GL_Data table, or both.

 

Error Handling -- Missing Dimensional Data

Missing dimensional data means that rows on a certain fact table contain dimensional values which do not exist in the parent table (Example: Stage_FTE_Data contains an Employee_Code of "01231" but that Employee_Code does not exist in Stage_Employee).

Typically, this means that either the dimensional data loaded for the set was incomplete, or the fact table data loaded for the set was invalid.

In order to pinpoint the root cause, you may expand the error list by clicking on the "+" next to the Fact Table with the error. This will expand another list which will indicate what dimensional value is missing as well as how many rows contain the dimensional value.

Optionally, you may download a full report or a report for just a specific fact table. In order to do this, select either CSV or Excel in the dropdown of the main (or specific fact table) list. Then click the corresponding Download button. If you are downloading for reporting purposes, it is recommended you use the Excel option.

The fact or dimensional data must be re-uploaded in order to alleviate this error.

 

Error Handling -- Table Level Validations

A number of table level validations are performed before rebuilding the DIL. The table validation errors are designed to inform the user what is wrong with the data set for the table.

To get a more detailed view of the error to pinpoint the issue, click on "Download Detailed Error Report" to get an Excel file with a detailed view of the row(s) of data that are failing a particular table validation, or click the "+" next to the table in question to view the validation error messages.

 

Table Level Validations Inventory

  • Stage_Asset_Data
  • Ensures that the currency code defined on a row matches the default currency code for the row's defined office
  • Ensures that the concatenated key for the fact table does not repeat (a combination of Year, Period, Office_Code, PG_Dept_Code, Asset_Class_Code, and Currency_Code)
  • Stage_Salary
  • Ensures that the currency code defined on a row matches the default currency code for the row's defined office
  • Stage_TK_Rates_Data
  • Ensures that the currency code defined on a row matches the default currency code for the row's defined office
  • Ensures that the concatenated key for the fact table does not repeat (a combination of Year, Employee_Code, and Currency_Code)
  • Stage_GL_Data
  • Ensures, for rows with US based offices, that Local and Base amounts match for both budget and actual (if they are both provided)
  • Ensures, for rows with non-US based offices, that Local and Base amounts do not match for both budget and actual (if they are both provided)
  • Ensures that the calculated Credit and Debit amounts match the Net amount (only if all three amounts are provided)
  • Stage_Employee_Data
  • Ensures that the concatenated key for the fact table does not repeat (a combination of Year, Employee_Code, and Currency_Code)
  • Stage_WIP_AR_Data
  • Ensures that the concatenated key for the fact table does not repeat (a combination of Year, Period, Office_Code, PG_Dept_Code, and Currency_Code)
  • Ensures that the currency code defined on a row matches the default currency code for the row's defined office
  • Stage_FTE_Data
  • Ensures that the concatenated key for the fact table does not repeat (a combination of Year, Employee_Code, Office_Code, PG_Dept_Code, and Title_Code)

 

Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.
Powered by Zendesk