Verification and monitoring the Master Data Management integration
You can verify the Master Data Management synchronisation status in Business NXT, using the SyncEngine meta information and SyncEngine control information tables.
Verification using the SyncEngine control information table
| Field | Information |
|---|---|
| MDM data type |
|
| MDM snapshot id | A version number showing how many times this data type has been restored in Master Data Management (only via resend entities operations, the export operation does not increase the snapshot ID) |
| MDM previous snapshot id | |
| MDM processing |
This field is blank before activating Master Data Management on the computer. Double-clicking on the value will reveal the status of the processing (1 = pending restore, 4 = restore in progress, 8 = pending export, 16 = export in progress, etc) After the Resend to Master Data Managementprocessing has been completed, the field will be blank again. |
If a few entities are found to be missing or mismatched in other applications, then select just those in the SyncEngine meta information table and resend.
If there is a complete mismatch between the local dataset and the data in Master Data Management, all data for the affected master data type should be sent again to Master Data Management. This is done using the Export to Master Data Management processing.
See also: Export to Master Data Management
Troubleshooting using the SyncEngine meta information table
| Field | Information |
|---|---|
| MDM public id | An identifier (GUID) assigned when creating the record. |
| MDM data type |
|
| MDM version no. | This field is blank before the initial synchronisation. It gets the value 1 after the first synchronisation and increases for each subsequent synchronisation (when synchronised data is edited.) |
| Master Data Management processing |
This field is blank before activating Master Data Management on the computer. Processing status overview:
|
If some synchronisation lines failed, you can retry the synchronisation by selecting the lines and using the Resend failed synchronisations processing.
See also: Resend failed synchronisations