On the page"Decoupling via Data Store" there is a text which is not relevant for this case:
"Because the retry is performed within the same instance of the message processing log, the message processing log ID and, as a result, the mapped unique ID remain the same."
Seems it is copy-paste from referenced "Decoupling via JMS Queue" page.
In the current Data Store case, MPL ID is not used as the unique ID, but the Data Store entry ID is used which is updated from ${property.orderNumber}, which in its turn is retrieved from the payload.
Issue description
On the page"Decoupling via Data Store" there is a text which is not relevant for this case: "Because the retry is performed within the same instance of the message processing log, the message processing log ID and, as a result, the mapped unique ID remain the same."
Seems it is copy-paste from referenced "Decoupling via JMS Queue" page.
In the current Data Store case, MPL ID is not used as the unique ID, but the Data Store entry ID is used which is updated from ${property.orderNumber}, which in its turn is retrieved from the payload.
Feedback Type (Optional)
incorrect statement
Page Title on SAP Help Portal (prefilled)
Decoupling via Data Store
Page URL on SAP Help Portal (prefilled)
https://help.sap.com/docs/cloud-integration/sap-cloud-integration/decoupling-via-data-store