Explaining the Training Use Case and Solution Architecture

After completing this lesson, you will be able to:

After completing this lesson, you will be able to:

  • Explain the three-layer architecture of SAP Integration Suite

Step-by-Step Overview of the Training Use Case

You work at the fictional company eCarHero. The company wants to order vehicle parts for its electric cars from a manufacturer. For easier processing, the supplier requires an SAP purchase order in SOAP format. The message for a successful order is deposited in a special Slack channel.

The following video outlines the integration solution that has been designed by your colleagues. Your company has appointed you with the task to implement the integration scenario using the SAP Integration Suite and its four core capabilities Cloud Integration, SAP API Management, SAP Open Connectors, and the SAP Integration Advisory Methodology.

Solution Architecture

The figure above illustrates the three-layer architecture.

Let's take a closer look at each layer.

  • Data/Backend Layer
    In the exercise scenario, the data/backend layer consists of the SAP API Business Hub which provides the purchase order (PO). In a productive scenario, this would be an SAP S/4HANA system. The PO is delivered by an OData interface in JSON format.
  • Standard API Layer
    This layer encapsulates outward access to third-party apps, such as Slack, and provides a decoupled, secure, and controllable access page. The required SAP Integration Suite capabilities are SAP Open Connectors and SAP API Management. From the developer's point of view, the SAP API Business Hub Enterprise page is the only place from where APIs may be consumed. In a productive scenario, SAP S/4HANA backend APIs could be consumed from here as well. The SAP API Business Hub Enterprise is a part of the SAP API Management capability within the SAP Integration Suite.
  • Consumer Layer
    The processing of the purchase order takes place in the Cloud Integration capability of the SAP Integration Suite. The message is read, processed, mapped, and finally delivered to Slack. The individual processing steps above show the functionality. For a productive scenario, essential steps are still missing to increase the resilience of the entire process. The mapping step will be performed with the SAP Integration Advisory Methodology tool.


To solve the technical requirements technically, you will use the SAP Integration Suite. You will encapsulate the access to Slack via Open Connectors. An SAP API Business Hub Enterprise page needs to be created to give other developers access to Slack without the need for registration and setup steps. For training reasons, you will consume the purchase order directly from the SAP API Business Hub. The purchase order will be consumed directly by Cloud Integration and further processed for you to be delivered to Slack.

Related Resources

You find related resources here:

Save progress to your learning plan by logging in or creating an account

Login or Register