Updating Synchronization Status

Records are always synchronized with Datapools.

The synchronization state (synch status) of a record can be incorrect in the following cases:

  • Datapool failed to respond.
  • Message(s) failed in Datapool(s) and there was no response from messages.
  • Response was received but response format was not comprehensive and the processing failed.
  • Record was synchronized outside the application. For instance, you migrated from MDM to another GDSN system.

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

You can update the synch status of the record.

Procedure

  1. Click Browse and Search. A list of Repositories are displayed.
  2. In the Repository list, select the repository.
  3. Click View All Records. A list of records is displayed.
  4. Click on the record whose synch status you want to update. The View Record screen is displayed.
  5. Click More Actions > update synch status.
  6. The Update Synch Status screen is displayed.
  7. Specify the following fields on the Update Synch Status screen:
    • Datapool
    • Trading Partner
    • Operation
    • Sub-Operation
  8. 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.