3768577 - ProductMDMBulkReplicateRequest_In Asynchronous Processing Failure does not Return Error Details to the External System

• Using the asynchronous SOAP inbound API ProductMDMBulkReplicateRequest_In (SAP_COM_0009) to send product data results in immediate technical acceptance only.
• When backend asynchronous processing fails (for example, due to validation or business errors), ProductMDMBulkReplicateConfirmation_Out is not initiated.
• The external system and CPI do not receive the final failure status or detailed error reason.
• Error details are only visible in S/4HANA Cloud Message Monitoring / AIF.
• CPI captures only synchronous technical faults (for example, connection/authentication/SOAP/XML issues), not asynchronous business processing errors.

• Product: SAP S/4HANA Cloud Public Edition
• Product Master for Public Cloud

1. Send a ProductMDMBulkReplicateRequest_In message that causes a backend business/validation error during asynchronous processing.
2. Observe that S/4HANA Cloud returns only a technical acceptance to CPI.
3. Check CPI: no asynchronous error is received; only successful confirmations appear when processing succeeds.
4. Check S/4HANA Cloud Message Monitoring / AIF: the failure and its details are recorded there.
5. Note that ProductMDMBulkReplicateConfirmation_Out is not sent for the failed processing.

This is a Standard system behavior where ProductMDMBulkReplicateConfirmation_Out is sent only for successfully processed messages. 
In error cases, failures are recorded in AIF / Message Monitoring and are not returned to CPI/external systems. 
There is no standard mechanism exists in this API to push asynchronous failure details back to the sender.

1. ProductMDMBulkReplicateConfirmation_Out is triggered only in successful scenarios for ProductMDMBulkReplicateRequest_In.

2. In error scenarios, the failure details are only recorded in AIF / Message Monitoring and are not returned to CPI/CIF / external systems via the confirmation interface.

3. As per current design, asynchronous Product Master SOAP API does not provide a standard mechanism to send failure status and error details back to CPI / external systems.

4. After fixing the error in S/4HANA Cloud and restarting/reprocessing the failed message from Message Monitoring for Administrators App, ProductMDMBulkReplicateConfirmation_Out will trigger if the reprocessing is successful.
Correct the failed data in the Target System and Restart the failure message. The message is Successful and according Confirmation Message is available in Source System.
Note : This Test was done between two(source and target) S/4HANA Public Cloud Systems.

By current design, the ProductMDMBulkReplicateConfirmation_Out message is triggered only in successful scenarios. In error cases, messages are reported to the Application Interface Framework (AIF) instead.

Recommendation is to submit a Customer Influence Request at https://influence.sap.com/sap/ino/#/campaign/4186 for confirmations to be triggered for error cases as well, so it can be considered for future development.

• Refer to: Note 3600487 - Issue with SOAP API ProductMDMBulkReplicateRequest_In
• Refer to: SAP BTP Alert Notification Service - Documentation
• Refer to: Customer Influence - SAP S/4HANA Cloud
• Refer to: Note 2963059 - How to Submit Feature Requests for SAP S/4HANA Cloud Product

ProductMDMBulkReplicateRequest_In, ProductMDMBulkReplicateConfirmation_Out, SAP_COM_0009, asynchronous, SOAP, CPI, AIF, Message Monitoring, product replication, confirmation, error details, failure, inbound, outbound confirmation, S/4HANA Cloud , KBA , LO-MD-MM-2CL , Product Master for Public Cloud , Problem