Identifying the Relationship between SAP Build and SAP BTP

Objective

After completing this lesson, you will be able to identify the Connection between SAP Build and SAP BTP.

SAP BTP and SAP Build

Illustration of SAP BTP features that are relevant for SAP Build

In addition to the main app-building features, there are a bunch of features that make it easy to build SAP extensions and other SAP-related apps:

Destinations
Destinations are connections to back-end systems, often SAP systems, defined within SAP BTP for use by SAP BTP services. SAP Build is aware of destinations defined in the SAP BTP cockpit and can create data resources (that is, connections to back-end systems) based on these destinations. SAP Systems describes how to set up destinations for SAP Build Apps.
Deployment to SAP BTP
SAP Build Apps lets you deploy your app to run on SAP BTP. SAP Build Apps enables you to build your project into an MTAR, an application file understood by SAP BTP’s Cloud Foundry environment, and then enables you to send the file to be deployed in SAP BTP.
SAP BTP Authentication
You can make it mandatory for the users to be authenticated with SAP BTP before using the app. This is required for many other features, such as referencing SAP BTP destinations.

More Advanced Features

SAP Build Apps also has more sophisticated features to let more advanced business users and developers make the most of the platform. The integration of SAP Build Apps with the SAP Business Technology Platform (BTP) provides several practical capabilities. One of the key advantages is the ability to utilize the Formula Editor to dynamically incorporate variables that retrieve information from SAP BTP, such as the authenticated user’s name or email address. For example, the email address can be accessed using a specific variable within the Formula Editor.

Screenshot of the formula editor showing system variables

This variable, let’s call it userEmail, can then be dynamically embedded within SAP Build Apps. This functionality enhances the utility for end-users and optimizes end-to-end processes. By leveraging this feature, the email address of a user authenticated via SAP BTP Authentication can serve as input for various processes or parameters when these processes are triggered. This integration highlights the value of authentication in enhancing personalization and streamlining workflow automation, ensuring that user-specific data is securely and efficiently utilized within applications.

Destinations

In SAP Business Technology Platform (BTP), destinations are predefined endpoints that facilitate secure communication between your applications and external systems, whether on-premise or in the cloud. They store crucial connection details such as URLs and authentication information, ensuring secure data exchange.

Within the scope of SAP Build products, properly configured destinations are vital for seamless integration and communication across various services like SAP Build Process Automation, SAP Build Work Zone, SAP Build Apps, and SAP S/4HANA Cloud. These configurations ensure that processes are correctly triggered, and data is consistently transferred, supporting coherent workflows.

Screenshot of the destination for triggering SAP Build Process Automation processes with SAP Build Apps

The SAP BTP destination sap_process_automation_service_user_access enables secure and efficient communication between various SAP services, facilitating new process flows between SAP Build Apps and SAP Build Process Automation to trigger processes seamlessly. The OAuth2JWTBearer mechanism uses JSON Web Tokens (JWT) for authorized access, ensuring only legitimate users can interact with the services. Additional security measures such as mTLS (Mutual Transport Layer Security) verify both communication partners, while CSRF protection prevents unauthorized commands.

Support for mobile and HTML5 applications provides flexible access to SAP Build Process Automation and other SAP Build products, making it possible for users to integrate these services into their existing workflows from anywhere. Relevant credentials like the Client ID, Client Secret, and Token Service URL can be found in the SAP BTP Cockpit. The Client ID uniquely identifies the OAuth client, the Client Secret is a confidential key necessary for authentication, and the Token Service URL is used to generate and retrieve authentication tokens. This configuration allows for the automation and streamlining of processes within SAP Build Apps and SAP Build Process Automation, ensuring secure and uninterrupted usage of the SAP services.

Further Reading

Log in to track your progress & complete quizzes