When you are triggering programatically synchronization in service layer you might experience unexpected, inconsistent behavior between programmatic approach and triggering synchronization from backoffice interface. It can be observed especially on the out-of-the-box SAP Commerce installation for "update scenario" when an item is modified in source catalog version (it's counterpart has been already created in target catalog version after "create scenario") and when there is no explicitly set session user for synchronization process.
Personalization rule, session user, search restriction, synchronization triggered programmatically , KBA , CEC-COM-CPS-CAS , Catalog & Sync , CEC-COM-CPS-COR , SAP Commerce Core , How To
About this pageThis is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).
Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.