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. 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 Rekognition - PPE Detection and the actions for these events are taken in SAP S/4HANA. 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
Safety hazards can exist in every workplace in many different forms: sharp edges, falling objects, flying sparks, chemicals, noise, and other potentially dangerous situations. Safety regulators such as Occupational Safety and Health Administration (OSHA) and European Commission often require that businesses protect their employees and customers from hazards that can cause injury by providing them personal protective equipment (PPE) and ensuring their use.With Amazon Rekognition PPE detection, customers can analyze images from their on-premises cameras across all locations to automatically detect if persons in the images are wearing the required PPE such as face covers, hand covers, and head covers. SAP customers use SAP Environment health and safety module to record these detections manually as safety observations.This solution provides an integration framework between Amazon Rekognition and SAP Envriroment, Health and Safety(EHS).
The key services used from AWS are Amazon Rekognition PPE Detection, 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 - Decision capability, SAP Destination service and SAP Business Application Studio.
SAP Private Link service is used for connectivity between SAP BTP and SAP S/4HANA when both the systems are running on 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) Equipment (Camera): CCTV cameras at the factory capture images of people and location and pushes them to an Amazon S3 bucket.
(2) Amazon S3 holds the images for model inference. A lambda function can be scheduled or triggered to execute the inference.
(3) The lambda function calls Amazon Rekognition PPE detection model to detect any visual inspection issues with the product.
(4) Amazon Rekognition – PPE detection evaluated the image for any missing PPE equipment like Hand gloves, Face covers, Head gears and safety visors. if an anomaly is detected, The Lambda function accesses AWS secrets Manager for credential information for SAP BTP
(5) The lambda function calls the SAP Integration Suite, Advanced event mesh and passes the event payload. Event-to-Business-Action framework(extension app) processor module's endpoint is subscribed to SAP Advanced Event Mesh, hence receives this event.
(6) Event-to-Business-Action framework(extension app) processor module leverages the Decision capability of SAP Build Process Automation to derive business action (for example, In this scenario,EHS Report Incident- Safety Observation creation in SAP S/4HANA system) based on certain characteristics of incoming event.
(7), (8), (9) (10) and (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, 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.
- 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 Rekognition
- 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
- SAP Build Process Automation - Decisions service to configure business decisions that needs to be taken based on the type of event received from Amazon Rekognition.
- 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.
Amazon Web Services
-
A valid AWS subscription
-
Amazon Rekognition - PPE Detection
- 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.
-
Amazon Secrets Manager
- Required to store the 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 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-Decisions Project
Step 7: Configure SAP S/4HANA Business Actions in the extension application
Step 8: Update and Activate SAP Business Rule Project
Step 9: Test the Extension Application
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 Amazon Rekognition - PPE Detection 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.