SAP Knowledge Base Article - Preview

3546842 - Why PrePersistHook and PostPersistHook not being triggered together while both sent via request header

Symptom

The pre-persist-hook and post-persist-hook have been configured in the message mapping for "batchparts" and are sent from CPI iflow to SAP Commerce Cloud during material replication. But the post-persist hook is not being called at the commerce end and no exceptions/errors are found in Kibana logs.

If either of the hooks is configured, they are executed correctly. But both pre-persist and post-persist hooks are required to be executed.


Read more...

Environment

  • SAP Commerce Cloud, integration extension pack
  • SAP Commerce Cloud

Product

SAP Commerce Cloud all versions ; SAP Commerce Cloud, integration extension pack all versions

Keywords

Web hook, Inbound, replication, material data, CPI iflows, pre-persist-hook, post-persist-hook, message mapping, sapCpiProductFeaturePersistenceHook, hooks. , KBA , CEC-SCC-INT-S4I-MOD , SAP Model , Problem

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.