Take care of entries from Cleansing Error tables
During the load of a Dimensional Project, you may encounter some entries in the CLS_XXX_Error tables. These tables log all warnings and errors produced by the cleansing actions.
Each Model Object in the Core Layer with a target table has its own corresponding error table.
Here is an example of entries in an error table:
You need to regularly review these entries because they may indicate potential issues in the design of your Entities or Fact Model Objects.
An entry in this table can be of different types:
- Nulled non-nullable business key
- The Term defined as Business Key is set to Not Null but contains a NULL value
- ACTION: Define a Business Key that will always have a value (i.e., it can never be NULL)
- Duplicated business keys
- The Term defined as Business Key has a value that already exists
- ACTION: define a Business Key that will be unique for all records
- Missing foreign key value
- The Foreign Key value doesn't exist in the referenced Entity and is NULL
- ACTION: Update the referenced Entity to ensure all values used in related Entities or Facts exist
For alternative methods to handle missing Foreign Key values and reduce the number of logged errors, refer to the article: Reduce the volume of the Cleansing Error tables.