Updating Synchronization Status (GDSN Only)

Records are always synchronized with Datapools.

For the following reasons, the synchronization state (synch status) of a record can be incorrect:
  • Datapool failed to respond.
  • Message failed in Datapools and there was no response from messages.
  • Response was received but response format was not comprehensive and the processing failed.
  • The record was synchronized outside the application. For instance, you migrated from the application to another GDSN system.

When the synch status is incorrect, it affects the next message generated by application and the synchronization is not possible. To resolve this issue, the synch status needs to be updated.

Procedure

  1. Click Master Data > Repositories. A list of repositories are displayed.
  2. Click the name of the repository.
  3. Click the View All button. A list of records are displayed.
  4. Click any record whose synch status you want to update. The Record View screen is displayed.
  5. Click More Actions > Update synch status. The Update Synch Status screen is displayed.
  6. Specify the following fields in the Update Synch Status screen:

    Datapool

    Backend System

    Operation

    Sub-operation

  7. Click Save to update synch status.
    Note: An out-of-box installation assumes that EAN.UCC is associated with the repository. If this format is not associated, the operation fails. To correct this, either associate the synchronization format or use another synchronization format in the rulebase rbsyncstatusupatederivation.xml.