Translating IDocs, BAPIs, and BW into data entities, business events, and Fabric

How SAP's integration estate — IDocs and ALE for messaging, BAPIs and RFC for synchronous calls, SAP PI/PO for middleware, LSMW and LTMC for data migration, BW for analytics — maps to D365 data entities and DMF, OData services, business events, Azure Integration Services, dual-write, and Microsoft Fabric; with practical rules for idempotency, batching, and throughput.

What you will be able to do

• Map each SAP integration pattern to its closest D365 equivalent
• Explain when to use OData versus DMF versus business events for D365 integration
• Describe the idempotency requirements for recurring integrations and why they differ from IDoc behaviour
• State the throughput limits that affect D365 integration design and the mitigation patterns
• Identify the D365 replacement for SAP BW extraction and explain what changes in the analytics architecture

Introduction

An SAP system's integration estate is usually larger and more varied than anyone anticipated at the start of a migration programme. There are outbound IDocs to EDI partners that have been running unmonitored for a decade. There are RFC calls from warehouse management systems to SAP WM that are triggered by barcode scans.

SAP integration patterns: IDocs, BAPIs, and PI/PO

IDocs (Intermediate Documents) are SAP's asynchronous messaging format. An IDoc has a defined structure (control record + data records organised as segments), a message type (e.g., ORDERS05 for purchase orders, INVOIC02 for invoices, DESADV01 for despatch advice), and a partner profile (WE20) that defines the delivery method, logical…

D365 integration patterns: data entities, OData, and business events

D365 data entities are the primary integration surface. A data entity is a denormalised view over physical tables, exposing a business-meaningful record (e.g., a sales order header with all required header fields from multiple physical tables). Data entities support:

The data migration toolchain: LSMW and LTMC versus DMF

LSMW (Legacy System Migration Workbench, transaction LSMW) is SAP's tool for loading legacy data into SAP. It reads source files, applies field mapping rules, and either calls BAPIs or generates batch input (BDC) to post the data.

Analytics and reporting: BW versus Fabric

SAP BW is a purpose-built analytical database. Its architecture is optimised for OLAP queries: InfoCubes store data in star schemas; DSOs (DataStore Objects) store inbound delta data; BEx queries define the analytical view that business users consume.

Practical rules: idempotency, batching, and throughput

D365 OData services are subject to platform throttling. The standard limit is approximately 1,000 concurrent OData requests per tenant per five minutes. High-volume real-time feeds that call OData per record will breach this limit under production load. Design rules:

Knowledge check

Summary

SAP's integration estate — IDocs, BAPIs, ALE, PI/PO, BW extractors — maps to D365's integration patterns through a combination of DMF, OData, business events, and Azure Integration Services. The mechanics are different; the functional purposes are equivalent.