This repository contains code samples and instructions for developing an extension application in SAP BTP. The sample application has been developed in a partner collaboration to help customers integrate any type of events from systems into SAP ecosystem via SAP BTP. This application helps to configure actions that needs to be taken in SAP LoB systems based on the events that is received in SAP Integration Suite, Advanced Event Mesh. This application leverages Amazon Bedrock LLM Model via Gen AI hub to generate summary of the event which is then used for creating Business Actions in SAP system. The application scenario you will develop in this tutorial leverages Event-To-Business actions framework (extension application).
This framework can be used in combination with any hyperscalar/telco IoT.
In this tutorial, the events are received from Amazon Monitron and the actions for these events are taken in SAP S/4HANA System. You can use this application to further customize it for other systems as well.
Scenario
Solution Architecture
Requirements
Implementation: Configuration and Development
Additional Resources
Known Issues
Reference
Disclaimer
How to Obtain Support
Code of Conduct
Contributing
License
Amazon Monitron is an end-to-end system including hardware ( sensors and gateway) and software, that uses machine learning to detect abnormal conditions in industrial equipment and enable predictive maintenance. However, the output of machine learning in industrial operations only provides valuable results if action is taken on the machine learning insights. To reduce the burden of change management and ensure action is taken on the Monitron inferences, this sample project has demonstrated how to automatically record the Amazon Monitron inferences in SAP Plant maintenance/asset management.
The key services used from Amazon Web Services are Amazon Monitron, Amazon Kinesis, Amazon S3, Amazon Lambda Function, AWS Secrets Manager. The services used from SAP BTP are the Cloud Foundry Runtime, SAP Integration Suite Advanced Event Mesh, SAP Connectivity service, SAP Private Link service, SAP Build Process Automation- Decisions, SAP HANA Cloud , SAP Business Application Studio and SAP Destination service, SAP AI Core, SAP AI Launchpad.
SAP Private Link service is used for connectivity between SAP BTP and SAP S/4HANA when both the systems are running on Amazon AWS Infrastructure, in this tutorial you will find implementation steps for SAP BTP Private Link service and AWS Private Link service. Alternatively you can use SAP Connectivity service and Cloud Connector for integration of SAP BTP and SAP S/4HANA as well.
Figure-1: High-level architecture (with SAP S/4HANA on AWS)
The following steps depicts the information flow across systems:
(1) Event is triggered from Amazon Monitron Hardware and sent to Amazon Monitron Software.
(2) and (3) Amazon Kinesis streams the sensor data from Amazon Monitron and dumps it into the Amazon S3 bucket.
(4) AWS Lambda is a serverless function, which will orchestrate the process of detecting a stream contains any alerts related to failure or warnings, and then the inference result is passed to SAP Integration Suite, Advanced Event Mesh.
(5a) AWS secrets manager is used to store credentials, these are used by the lambda function to provide payload to SAP Integration Suite, Advanced Event Mesh.
(5), (6) Event-to-Business-Action framework(extension app) processor module's endpoint is subscribed to SAP Integration Suite, Advanced Event Mesh, hence receives this event.
(7) Event-to-Business-Action framework(extension app) processor module leverages the Business Rules capability of SAP Build Process Automation to derive business action (for example, In this scenario, Plant Maintenance Notification creation in SAP S/4HANA system) based on certain characteristics of incoming event.
(8a), (8b) Event-to-Business-Action framework(extension app) calls Amazon Bedrock LLM model using Gen AI hub to generate summary of the event.
(9), (10), (11) Event-to-Business-Action framework (extension app) processor module triggers the defined action in the SAP S/4HANA system by using the SAP Destination Service and SAP Private Link Service.
For more information, see Set Up Connectivity Between SAP BTP and SAP S/4HANA Using SAP Private Link Service page.
These are the technical prerequistics for an integration between AWS IoT Core, SAP BTP and SAP S/4HANA.
Services in SAP BTP
- Cloud Foundry Runtime - Foundation for running the CAP extension application for translating events to business actions.
- Memory/Runtime quota - Required for deploying and running the extension application in SAP BTP
- Authorization & Trust Management Service - Required for securing the extension application in SAP BTP
- SAP Integration Suite,Advanced Event Mesh - Required to receive events from Amazon Monitron
- SAP HANA Cloud - Required to store action configuration and logs for CAP application
- SAP HANA Schemas & HDI Containers - Application database for CAP Application -SAP Build Process Automation, Decision capability - Decision service to configure business decisions that needs to be taken based on the type of event received from Amazon Monitron.
- SAP S/4HANA System - To execute the business action associated with the event received.
- SAP Connectivity Service - To establish connections between cloud applications and on-premise systems.
- SAP Destination Service - To find the destination information required to access a remote service or system from your extension application.
- SAP Private Link Service - To establishe a private connection between selected SAP BTP services and selected services in your own IaaS provider accounts.
- SAP Business Application Studio - A powerful and modern development environment, tailored for efficient development of business applications for the Intelligent Enterprise.
- SAP AI Core - SAP AI Core supports full lifecycle management of AI scenarios and also provides access to generative AI capabilities of LLM Models like Amazon Bedrock via the generative AI hub.
- SAP AI Launchpad - SAP AI Launchpad is a multitenant software as a service (SaaS) application in SAP Business Technology Platform that provides generative AI capabilities via the Generative AI Hub. Customers and partners can use SAP AI Launchpad to manage AI use cases (scenarios) across multiple instances of AI runtimes (such as SAP AI Core).
Amazon Web Services
- A valid AWS subscription
- Amazon Monitron - Required for receiving and sending the events whenever an abnormality is detected in the equipment.
- Amazon S3 - Required to store the received streaming event data.
- AWS Secrets Manager - Required to store the SAP Integration, Advanced Event Mesh credentials that are accessed by the Amazon Lambda Function.
- Amazon Lambda Function - Required to orchestrate the process of detecting a stream contains any alerts related to failure or warnings, and then the inference result is passed to SAP Integration Suite Advanced Event Mesh.
This scenario talks about the steps needed for translating events from AWS IoT to business actions in SAP business systems.
These are the steps to configure SAP S/4HANA, SAP BTP and Amazon AWS.
Step 1: Set Up the Subaccount in SAP BTP
Step 2: Check SAP S/4HANA Readiness
Step 3: Connect SAP BTP and SAP S/4HANA
Step 4a: Build and Deploy the Extension Application
Step 4b: SAP Integration Suite, Advanced Event Mesh Configuration
Step 6: Create SAP Build Process Automation - Decision Project
Step 7: Configure SAP S/4HANA Business Actions in the extension application
Step 8: Update and Deploy SAP Build Process Automation - Decision Project
Step 9: Test the Extension Application
This project has been implemented based on the following SAP CAP sample repository.
Related projects :
No known issues.
This project has been a proof of concept, including several limitations and prerequisites. The objective was to build a extension application for receiving and automating the actions in SAP S/4HANA. For this reason, the coding should not be seen as any recommendation for productive implementation. It fulfils the purpose and requirements of a proof of concept and is not intended for productive usage. It has been declared as pure proof of concept only to give the development teams ideas for solving potential challenges when integrating events from other platforms like AWS Monitron and SAP S/4HANA using SAP BTP. This can be extended to integrate with any other SAP LoB system as well.
Create an issue in this repository if you find a bug or have questions about the content. For additional support, ask a question in the SAP Community.
If you wish to contribute code, offer fixes or improvements, send a pull request. Due to legal reasons, contributors will be asked to accept a DCO when they create the first pull request to this project. This happens in an automated fashion during the submission process. SAP uses the standard DCO text of the Linux Foundation.
Refer to the CONTRIBUTING file for guidelines to contributions from external parties.
For additional support, ask a question in the SAP Community.
Refer to the CODE OF CONDUCT file.
Copyright (c) 2022 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.