S/4HANA Cloud Public - Executing SOAP API upon Sales Order Creation (Before Save Logic)

[diana_gonzalezcr60]

Dear SAP Community,

We are seeking guidance on the best practice for implementing a custom action triggered during the Sales Order creation process in SAP S/4HANA Cloud Public Edition.

Core Requirement

We need to implement a Before Save action (similar to a Pre-Exit logic) during the creation of a Sales Order (SO) by the Key User. The goal is that, once the Sales Order is successfully created in the system, the external SOAP API: https://api.sap.com/api/SERVICECONTRACTREQUEST_IN must be consumed and executed immediately.

Specific Technical Questions

1. Internal API Consumption via ABAP Environment (ADT)

Internal Consumption via ADT: Is it possible to consume this specific SOAP API directly within the ABAP Environment (ADT) using Developer Extensibility options (e.g., via EML (Entity Manipulation Language) or an internal release)? Or is this API strictly intended for external consumption (side-by-side extensibility via RAP, Java, or JavaScript)?

• If internal consumption is possible, what is the recommended BAdI (Business Add-In) in the Sales Order flow that executes after all consistency checks but before the final commit to ensure API execution aligns with the SO creation?

2. Locking Behavior & Concurrency

Locking Behavior: If a Key User currently has the specific Sales Order open and is actively using it within the UI, will the API request fail due to a locking conflict if the API attempts to create a follow-up document?

• In systems like SAP Business ByDesign, concurrent editing is strictly disallowed. We would like to confirm if S/4HANA Cloud Public Edition behaves similarly, and what implications this has for external API calls triggered by the Key User's save action.

Thank you for your insights and recommendations.

[ThomasM]

I think you should Take a Look at RAP Events. An Event exists for Sales Order creation you can listen to that Event either onstack or SidebySide for example via SAP Events Mesh and Trigger your follow up API.

Regarding remote calls in Cloud Badi I dont think this is allowed most Cloud Badis have API classification functional see also

https://help.sap.com/doc/abapdocu_cp_index_htm/CLOUD/en-US/ABAPAPI_CLASSIFICATION.html

For what ist allowed according to each classification 

[diana_gonzalezcr60]

Hi @ThomasM, thanks for the quick reply!. I’ve followed these steps to use the Event Mesh within the Integration Suite. However, when trying to retrieve the topic, I searched for apps containing 'event' in my demo tenant. Some apps won't let me access them (i'm admin role) and others don't show any options. I’m not sure if this is restricted because I'm on a demo tenant. Or are you referring to a different Event Mesh service, distinct from the Integration Suite one? Steps taken: Activated necessary capabilities: 'Build Integration Scenarios' (Cloud Integration) - To create the iFlow that calls the SOAP service. 'Manage Business Events' (Event Mesh) - To receive Sales Order events. S/4HANA Public Cloud Configuration: Accessed the 'Event' app to retrieve the topic."