SAP Knowledge Base Article - Preview

2356068 - Triggering synchronization programatically between catalogs - no specific session user

Symptom

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.


Read more...

Product

SAP Commerce 1811 ; SAP Commerce 1905 ; SAP Commerce 2005 ; SAP Commerce 2011 ; SAP Commerce 2105 ; SAP Hybris Commerce 1808 ; SAP Hybris Commerce 6.0 ; SAP Hybris Commerce 6.1 ; SAP Hybris Commerce 6.2 ; SAP Hybris Commerce 6.3 ; SAP Hybris Commerce 6.4 ; SAP Hybris Commerce 6.5 ; SAP Hybris Commerce 6.6 ; SAP Hybris Commerce 6.7 ; SAP hybris Commerce 5.0.3 ; SAP hybris Commerce 5.0.4 ; SAP hybris Commerce 5.7 ; SAP hybris Commerce Suite 5.2 ; SAP hybris Commerce Suite 5.3 ; SAP hybris Commerce Suite 5.4 ; SAP hybris Commerce Suite 5.5 ; SAP hybris Commerce Suite 5.5-1 ; SAP hybris Commerce Suite 5.6 ; hybris Commerce Suite 4.4 ; hybris Commerce Suite 4.5 ; hybris Commerce Suite 4.6 ; hybris Commerce Suite 4.7 ; hybris Commerce Suite 4.8 ; hybris Commerce Suite 5.0 ; hybris Commerce Suite 5.1 ; hybris Commerce Suite 5.1.1

Keywords

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 page

This 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.