Global Master Data Sync gives you a clear overview of where your master data stands as a subscriber company. The role center shows you which records you have received but not yet synchronized, which ones have been skipped after repeated failed attempts, and which record actions are still waiting to be executed.
When synchronization is skipped, you control how many attempts the system makes before stopping. You set this number in the Global Master setup. After the limit is reached, you need to check the error to find the actual cause.
You can also see obsolete record IDs that no longer exist in the master company, records that fall outside your template filters, and configuration packages that have been downloaded but not yet applied. The imported templates tile shows you the full list of data templates you have received from a master company.
Records received but not yet synchronized
The first tile relevant to a subscriber is the not synchronized record data. This shows the records you have received from your master company but have not yet synchronized into your own tables.
There are two reasons a record can end up here. Either you have just received the record and it is waiting to be processed, or the record contains errors that you need to be aware of and resolve.
Skipped synchronization after repeated attempts
Skipped synchronization record data shows the records where synchronization has been stopped. This happens when the system has tried to synchronize a record several times without success.
You define how many attempts the system makes in the Global Master setup. For example, you might set it to try five times before skipping the record. When a record reaches that limit, you should go in and check the error to see what is actually causing it.
Record actions not yet executed
Record action not executed means you have received record actions from your master company that you have not executed yet.
A record action can be a deletion of a record, or it can be a renaming of a record. These actions wait here until they are processed.
Obsolete record IDs from the master company
The obsolete record IDs tile tells you that some of your record IDs no longer exist in the master company.
This often happens because of a filter on a template. A record you have received can become obsolete because it now falls outside your records filter and is no longer relevant to your company.
Configuration packages downloaded but not updated
Not updated configuration package link means you have downloaded or received a configuration package file but have not yet applied it.
This can happen in two situations. If you use a job queue to download files, the file may be downloaded but not yet updated and synchronized. It can also happen when you receive a file that updates the full template. In both cases, the file shows up as not updated until you run the synchronization.
Imported templates from the master company
The imported templates tile shows the number of data templates you have imported from a master company. From here, you can see the full list of all the templates you have received.
Q&A
What does not synchronized record data mean in Global Master Data Sync?
It shows records you have received from your master company but have not yet synchronized into your own tables. They are either waiting to be processed or contain errors you need to resolve.
Why does a record end up as skipped synchronization?
A record is skipped when synchronization has failed several times. You set the number of attempts in the Global Master setup, for example five attempts, after which the system stops trying. You then need to check the error to find the cause.
What kinds of record actions can be not executed?
A record action can be a deletion of a record or a renaming of a record received from the master company that has not yet been executed.
Why would a record ID become obsolete?
A record ID becomes obsolete when it no longer exists in the master company. This often happens because of a filter on a template, where the record falls outside your records filter.
What does not updated configuration package link mean?
It means you have downloaded or received a configuration package file but have not yet applied it. This can occur when a job queue downloads a file without synchronizing it, or when you receive a file that updates the full template.