2911856 - How to reveal exception and stacktrace for synchronization process for SAP Commerce below 1905

Symptom

Synchronization process finishes with:

19.11.05 16:10:00:159	ERROR	sync ended with 1 unfinished items - see last sync media for details
19.11.05 16:10:00:160	ERROR	Finished synchronization in 0d 00h:00m:00s:152ms. There were errors during the synchronization!

although there is no obvious reason behind.

Root types configuration has been verified on synchronization job level (it affects what the list of items scheduled for synchronization is consisted of - root types and their subtypes by default; like category or product; attribute rootTypes of synchronization job).

Other synchronization properties like session user for synchronization job (his usergroup assignment can inflict activation of Personalization Rules and thus limit access to what's returned via FlexibleSearch queries; attribute sessionUser of synchronization job) or attributes explicitly excluded from synchronization (attribute syncAttributeConfigurations of synchronization job).

Synchronization record (ItemSyncTimestamp instance linked with both source and target counterparts of a catalog item) usually shows (printed in 'dump medias' attached to synchronization cronjob):

{sourceItemPK};;

which suggests that counterpart of an item has not been created at all due to some conditions (like excluding mandatory attributes on synchronization job level or interceptor throwing exception which precedes persistence).

Environment

Workaround tested on patch 1905.12, 1811.21, 1808.23 and 6.7.0.28

Product

SAP Commerce 1811 ; SAP Commerce 1905

Keywords

TBD , 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.