---
title: "Overview"
slug: "overview-sap-idocs"
updated: 2026-08-05T07:16:09Z
published: 2026-08-05T07:16:09Z
canonical: "docs.turbo360.com/overview-sap-idocs"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.turbo360.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Overview

The SAP IDOCS demo illustrates how Turbo360 can be used to manage an integration solution built around one of the most common patterns for integrating with SAP.

## Demo story

The finance team uses SAP, which publishes IDocs to support multiple outbound integration scenarios. The solution receives IDocs from SAP and implements a pub/sub pattern to drive downstream interfaces that integrate data with different target systems. Specifically, MATMAS and ORDERS05 message types are used to integrate with Maximo.

The diagram below represents the solution architecture.

![image.png](https://cdn.document360.io/a21734f9-5f67-4835-bb81-a488f8191fa8/Images/Documentation/image%28408%29.png)

## Implementation

The solution is implemented with Logic Apps and the Logic App SAP connector. IDocs are received from SAP and published to Service Bus, where the pub/sub pattern is applied. Separate Logic Apps then process messages for each subscriber, and API Management is used to integrate with Maximo web services.

The diagram below shows the Azure view of the solution.

![image.png](https://cdn.document360.io/a21734f9-5f67-4835-bb81-a488f8191fa8/Images/Documentation/image%28409%29.png)

## Who this demo is for

This demo is relevant if you work with Logic Apps, integrate with SAP, use API Management, or are building iPaaS solutions on Azure.

## Azure services covered

- Logic Apps
- API Management

## Turbo360 features covered

**Business Applications**

- Service map
- Business Application dashboard
- Logic Apps: run history, action required, monitoring
- API Management: monitoring

**Business Activity Monitoring**

- Transaction tracking for SAP IDoc processing