SAP Knowledge Base Article - Public

3795593 - VRS LD Sync Errors for Labeler Code Change in SAP Traceability Hub

Symptom

Messages fail in SAP Traceability Hub (TH) with the following error: current record owner [0003] is not the same as incoming record owner [80739]

Environment

SAP Traceability Hub

Cause

The issue occurs when a GTIN Labeler Code change results in an LD Sync mismatch between SAP Traceability Hub and the external trading partner system (TPI). 

The expected delete transaction was not processed, causing the record ownership information to become out of sync.

Resolution

To restore synchronization, perform the following steps:

1)Delete the GTIN under the new labeler code (72603).
2)Create the GTIN under the old labeler code (16714).
3)Delete the GTIN under the old labeler code (16714) again.
4)Recreate the GTIN under the new labeler code (72603).

This sequence generates the delete transaction for the old labeler code (16714) that the trading partner integration (TPI) expects and helps bring both systems back into sync.
 
Please Note:

Requesting TPI Do not update the labeler code directly on an existing product record.

Whenever a labeler code change is required:

   - Delete the existing product record.
   - Recreate the product record with the new labeler code.

This approach ensures that the required delete and create transactions are generated and processed correctly by all participating systems.

If the issue persists, create a support ticket under component IS-LS-TH at https://support.sap.com

Keywords

SAP Traceability Hub, Manage message application, US DSCSA, Supply Chain Partner Collaboration, LD Sync, GTIN, VRS. , KBA , IS-LS-TH , SAP Traceability Hub , Problem

Product

SAP Traceability Hub all versions