SAP Knowledge Base Article - Preview

3084142 - How to detect corrupted data of non-existing sourceitems and targetitems from itemsynctimestamps table

Symptom

There are situations where problematic incorrect data is kept in itemsynctimestamps table. Such corrupt data can cause synchronization process failures, loops or cause further data corruption.

Columns named p_sourceitem and p_targetitem contain item's PKs. Those PKs should be a connection between itemsynctimestamp and existing source and target items (Products, Media, CMSItems and many other catalog aware types). When sourceitem's PK points to non-existing data then such itemsynctimestamp is corrupted and needs to be removed. Sometimes both source and target items point to non-existing items, but if only targetitem is affected then synchronization process may notice that and recover from that situations. In any case, the cleanup is the best solution.


Read more...

Environment

SAP Commerce All Versions

Keywords

sync
synchronize
synchronization
cleanup
clean-up
ItemSyncTimestamp
ItemSyncTimestamps
table
targetitem
sourceitem
source, Incorrect data handling, data migration, manual data removal from both source and target catalog version, synchronization misconfiguration , KBA , CEC-SCC-PLA-PL , Platform , How To

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.