Create Sales Order Action Project in SAP Build Actions
- to discover APIs in SAP Business Accelerator Hub
- to download Open API specification
- to create action project based on the API specification
- to configure API methods to update title, input and output fields and their description to improve readability for business users
- to test API using destination option
- to release and publish action project to be consumed in the business process modelling
Prerequisites
- Access to a SAP BTP tenant with SAP Build Process Automation
- S/4HANA Cloud system where Sales Order business module is available
- A communication user to access S/4HANA Sales Order inbound services based on
SAP_COM_0109communication scenario ID
Action is a feature in SAP Build Process Automation to connect processes with external systems, be it SAP or non-SAP systems. This is an important piece of the puzzle especially if you want to automate or extend your business processes for any available LoB processes like S/4HANA, Ariba, SuccessFactors etc. These extensions can be easily build using SAP Build Process Automation, and using actions you can connect to your given S/4HANA, Ariba or other SAP LoB systems for any kind of GET, POST, PATCH and other calls.
In this tutorial, you will create an action project based on Sales Order API. The Sales Order (A2X) API is already available in Business Accelerator Hub. For this workshop you will leverage Sales Order Header - POST API which will be used to create a sales order in S/4HANA Cloud system after the approval is done.
The same scenario can be used for posting an invoice to the S/4HANA system after approval from business process or getting the employee details from SuccessFactors system for off-boarding process or updating purchase requisition details for the changes in the order in Ariba system or getting asset details from Asset Management system before sending it for approval for asset depreciation. There are many such real-world examples where you can use action concept to create, fetch or update the data in the backend system based on the process outcomes (approval, validation etc.)


























