Monitoring and Management

This section provides information about how you can monitor and manage Master Data Replication.

Configuring Error Notification Emails

You can configure Master Data Replication to send you notification emails when a job is run. Additionally, a .csv file containing the errors that have occurred when a job is run to extract the business partner or material source data or to import the promoted records and mappings file to SAP S/4HANA is also sent with the email notification.

To configure the email address for error notification emails

1. Configure the SMTP server when creating the SAP Data Services repository on the client computer. For information about how to configure the SMTP server, see the SAP Data Services Technical Manuals.
2. In your repository, import the .atl files, and for the $$SCH_SP_RECIPIENT substitution parameter, enter the email address of the Master Data Replication administrator or user who must receive the ETL job notifications and error log emails. For more information about how to configure this variable, see the SAP Central Finance Master Data Replication by insightsoftware Administrator Guide.

Checking Error Logs

Master Data Replication validates and logs errors in the following scenarios:

• When running the job to extract the business partner and material source records, if the source data has not been mapped with target data in the SCH_MASTER_LOOKUP table for the entity or if the source data does not comply with the column length constraints or the mandatory column requirement. The source records that contain errors are extracted to the SCH_<EntityType>_<DataSourceName>_ERROR_LOG.csv file.
• When running the job to import the mappings file to SAP S/4HANA, SCH_<EntityType>_MAPPING_LOAD_ERROR_REPORT.csv file is created with mappings that are not imported to SAP S/4HANA because of any validations that you might have in SAP S/4HANA.

For more information about the validation errors, see the SAP Central Finance Master Data Replication by insightsoftware Administrator Guide.

Starting and Stopping Change Data Capture (CDC) Jobs

When running the job to extract the source data, you can enter 0 or 1 for the appropriate variable to start and stop the CDC job. For example, for the business partner entity if your source is Oracle E-Business Suite, enter 1 for the $EBS_BP_CDC variable in the SCH_JOB_BP_EBS_EXTRACT job. For the cost center entity, enter 0 for $EBS_COSTCENTER_OT variable in the SCH_JOB_COSTCENTER_EBS_EXTRACT job. For more information about the CDC variables for the different data sources and entities, see the SAP Central Finance Master Data Replication by insightsoftware Administrator Guide.

Reloading Failed Master Data Records

Depending on the job that has failed, perform the following steps to reload the failed master data records:

• When running the job to extract the business partner and material source records, if you receive the SCH_<EntityType>_<DataSourceName>_ERROR_LOG.csv file, you can delete the records in the staging tables or the data source, correct the issues, and then run the job again. To delete the staging table records, review the records with the value E for the STATUS column in the staging tables SCH_BP_ADDR_STG, SCH_BP_ADDRUSAGE_STG, SCH_BP_COMP_STG, or SCH_BP_HEADER_STG tables for business partner and SCH_MATERIAL_STG for material.
• When running the job to import the mappings file to SAP S/4HANA, if you receive the SCH_<EntityType>_MAPPING_LOAD_ERROR_REPORT.csv file, review the error messages that are captured in the the staging tables MDG_MAPPINGS_LOG for business partner entity and SCH_<EntityType>_MDG_LOG for the other entities, fix the errors, and then run the job again.

For more information about how to run the jobs and reload the failed master data records, see the SAP Central Finance Master Data Replication by insightsoftware Administrator Guide.