Skip to main content

Application to Application Integration

Last updated on by avikSap

With the help of application-to-application (App2App) integration, you can exchange transactional data along internal company processes by connecting involved business applications in a (near-) real-time fashion. Messages are used for exchanging transactional data, which trigger the execution of the next process step in a connected business solution. Transactional data refers to data about ongoing business activities such as physical goods movement or sales order documents.

This reference architecture is based on the concepts of the SAP Integration Solution Advisory Methodology. App2App integration is defined as an integration use case pattern that belongs to the process integration style. The diagram illustrates the runtime perspective for App2App integration, covering the integration domains Cloud2Cloud, Cloud2OnPremise, and OnPremise2OnPremise.

Architecture​

image of solution diagram
Copy to clipboard

Solution Diagram Resources
You can download the Solution Diagram as a .drawio file for offline use. Alternatively, you may view and edit the Solution Diagram directly on draw.io.
Please note that any changes made online will need to be saved locally if you wish to keep them.
DownloadEdit

Flow​

The message flow for application-to-application integration is outlined as follows:

  1. Message Generation: An SAP or third-party cloud solution issues transactional data as messages. The message comprises a header (e.g., receiver information) and a payload (e.g., business data).

  2. Direct Exchange: Direct message exchange is possible when the outbound API of the sender and the inbound API of the receiver are aligned. This option is suited for simple landscapes or custom-built/partner solutions with aligned APIs.

  3. Cloud Integration: For unaligned APIs between sending and receiving solutions (Cloud2Cloud, Cloud2OnPremise), the Cloud Integration capability within SAP Integration Suite applies mediations (e.g., receiver determinations, filtering) and transformations (e.g., structure mappings, protocol conversion). It enables decoupled integration, error handling, and more.

  4. Predefined Integration Flows: SAP Business Accelerator Hub provides predefined integration flows, APIs, adapters, and more, which can be configured and deployed on Cloud Integration.

  5. On-Premise Connectivity: For Cloud2OnPremise scenarios, use the SAP Connectivity service with a cloud connector and SAP Destination service to establish secure connections.

  6. Edge Integration Cell: For data compliance and governance requirements, the edge integration cell runtime enables processing data locally within customer-managed private landscapes. It is an optional extension to SAP Integration Suite, designed for private Kubernetes environments.

Edge Integration Cell (design, runtime and operations view)

  1. SAP S/4HANA or SAP ECC Integration: Use the SAP Application Interface Framework for integration monitoring and error handling when involving SAP S/4HANA or SAP ECC.

Characteristics​

  • Use of Asynchronous Communication: Preferred for most App2App integration scenarios, it eliminates tight coupling between business applications and increases resilience. Use SOAP, REST, or OData for asynchronous communication. Synchronous communication is used only when required (e.g., availability-to-promise checks).
  • Directed Messages: Messages are used to exchange transactional data between sender and receiver(s). Receivers are determined within the sending system (logical receiver) or the integration technology (physical receiver).
  • Support for Exception Handling: Proper handling of transmission failures due to issues like unavailability of receiving solutions or incorrect message content.
  • Transport and Message-Level Security: Ensure secured communication over the public internet (transport-level security) and use digital encryption/signatures to protect message content (message-level security).

Examples in an SAP Context​

SAP delivers predefined App2App integration scenarios for end-to-end business processes spanning multiple SAP business applications. Examples include:

  • Lead-to-Cash Process: Exchange sales orders between SAP Commerce Cloud and SAP S/4HANA for cloud deployment.
  • External Workforce Process: Replicate service entry sheets or timesheets from SAP Fieldglass Vendor Management System to SAP S/4HANA for cloud deployment.
  • Acquire-to-Decommission Process: Exchange maintenance orders between SAP S/4HANA and SAP Service and Asset Manager for hybrid deployment.

Reasonable Alternatives​

For selected SAP solutions, additional integration technologies tailored to specific needs are available:

  • SAP Integration Suite, Managed Gateway for Spend Management and SAP Business Network: Formerly known as SAP Ariba Cloud Integration Gateway, this solution facilitates integration of SAP ERP or SAP S/4HANA systems with SAP intelligent spend solutions and SAP Business Network. It includes self-service wizards, automated testing, and real-time monitoring. Learn more: Content Transformation Service.

Services and Components​

Resources​