Employee dynamic attributes records load

Data from integration tables is loaded to the ATCDATA_EMPLOYEE_CUSTOM cube. It is a dynamic cube and you can list custom specific attributes in the METADATA_WDSETTINGS table where the variable is emplDA. Attributes must be comma separated.

When attributes are defined the depm_integration_wp_employee_custom_create_staging.sql script creates the DAT_ATCDATA_EMPLOYEE_STAGE table.

It also checks if the table already exists with the same attributes. If there is a difference in the attribute list or names table is dropped and all data is erased before recreating the table with the listed attributes in the METADATA_WDSETTINGS table.

The depm_integration_wp_employee_custom_prepare_staging.sql script performs data validation and loads to the DAT_ATCDATA_EMPLOYEE_TRANSFORMED table. Validation checks if the employee dimension value exists in the employee dimension table. Therefore, employee dimension tables _ELEMENTS and _PARENTS need to be updated.

If an element does not exist in the dimension table, an error is shown in the TRANSFORMED employee custom table for that record.

If an element is empty, an error is shown.

The depm_integration_wp_employee_custom.sql script checks for errors. If errors are found, the process is stopped.

If no errors are found, the script loads the data to the ATT_ATCDATA_EMPLOYEE_CUSTOM table from where data can be loaded to the OLAP database.

Before the data load to OLAP, dimension elements in the ATDATTRIBUTE_EMPLOYEE_CUSTOM must be created in Designer. The same attributes should be created as what are listed in the METADATA_WDSETTINGS table.