SAP Build Extensibility Scenario

Approval for Financial Asset Creation in SAP S/4HANA

Overview

This scenario allows to establish a lean governance process for the creation of Financial Assets in SAP S/4HANA. The project represents an example how SAP Build can consume and invoke BAPIs and Remote Function Calls (RFC) to connect with SAP S/4HANA.

Business users can request the creation of new Financial Assets using a dedicated mobile app developed in SAP Build Apps: once a request is submitted, a dedicated workflow - defined in SAP Build Process Automation - is triggered for further review and approval. To ensure a proper segregation of responsibilities, the list of reviewers is determined based on the Company Code specified in the request. Once a request is finalized and approved, the corresponding data are pushed to SAP S/4HANA, the new Financial Asset is created in the system and the process completed.

Note

• This usecase is developed using SAP Build Apps and SAP Build Process Automation services.
• Records are finally created in an SAP S/4HANA system; therefore its availability is required to enable the end-to-end scenario

Key Features

• Enables a lean governance process for new Financial Assets.
• Enforces segregation of duties: users can request Financial Assets only for the Company Codes they are authorized to; dynamic approvers determination based on Company Code.
• Enables approvers to review the creation request.
• Enables requestors to modify and resubmit the rejected requests.

Solution Flow

1. From Work Zone (or using a direct link), the requestor access the dedicated mobile application
   • the app is technically developed in SAP Build Apps
2. The requestor maintains the desired attributes
   • The field "Company Code" is pre-populated based on the requestor's roles and authorizations
   • Format validations are executed at runtime as soon as the user maintain a field in the app
3. Once done, the user click the "submit" button to trigger the corresponding approval process
   • The process is defined and implemented in SAP Build Process Automation;
4. In the background, the system dynamically determines the list of approvers based on the selected Company Code
5. The request is then routed to the authorized approvers for review and validation
   • The workitems to be evaluated are accessible from the SAP Build Inbox
6. The approver must add a comment to the request and then he can decide to approve or reject it.
7. In case the request is approved, the data are then pushed to the SAP S/4HANA backend via an RFC call

Content Download and Installation

The following paragraphs explain how the delivered content can be setup and enabled in your SAP Build tenant. The repository consists of three content packages for SAP Build - one for the destination, one for SAP Buil Apps and one for SAP Process Automation - and one package containing some ABAP code for the SAP S/4HANA system. To complete the setup of this scenario, please follow the instructions carefully.

Note

To setup this scenario, we assume a basic technical knowledge of the SAP BTP platform (in particular related to Destination and Cloud Connector setup), SAP Build and SAP S/4HANA (in particular, on custom development).

1️⃣ Installation and configuration of Cloud Connector

SAP Cloud Connector is required to establish a connection between SAP Build and an SAP S/4HANA backend; therefore its configuration and operability is pre-requisites for this scenario.

Note

The configuration and setup of Cloud Connector is not covered by this document.

2️⃣ Create the required Role Collections in SAP BTP Cockpit

The following role collection must be manually created in SAP BTP Cockpit and assigned to the users involved in the process.

• FA_CompanyCode1_User - This role collection must be granted to the users authorized to submit requests for Assets in Company Code 1010
• FA_CompanyCode2_User - This role collection must be granted to the users authorized to submit requests for Assets in Company Code 1710
• FA_CompanyCode1_AssetStaff - This role collection must be granted to the users authorized to process and approve requests for Assets in Company Code 1010
• FA_CompanyCode2_AssetStaff - This role collection must be granted to the users authorized to process and approve requests for Assets in Company Code 1710

3️⃣ Import the action in SAP Build

The action "" is a dependency for the automation process and it must be imported in your tenant as part of the initial project setup.

The content is stored in folder "actions" and it can be downloaded from there.

Note

The setup of the required destination to the SAP S/4HANA backend is not covered by this document. The destination must be defined both in the BTP cockpit as well in SAP Build.

4️⃣ Import the content for SAP Build Apps

The content is stored in folder "build_apps" and it can be downloaded from there.

To import the content in your tenant, please follow the procedure described in the official documentation of SAP Build.

5️⃣ Import the content for SAP Process Automation

The content is stored in folder "build_process_automation" and it can be downloaded from there.

To import the content in your tenant, please follow the procedure described in the official documentation of SAP Build.

License

Copyright (c) 2025 SAP SE or an SAP affiliate company. All rights reserved. This project is licensed under the Apache Software License, version 2.0 except as noted otherwise in the LICENSE file.