METHODOLOGY REFERENCE
An integration map I authored: how the modules post to FI and how SAP talks to the outside world. The integration thinking is real — I wired POS-to-accounting and multi-system flows on XeerSoft — framed here in SAP interface terms; it is not a delivered SAP integration build.
Home/SAP Design/Integration Architecture
Integration Architecture · Interfaces
How the ledger stays the single source of truth

Integration Architecture

Finance is only trustworthy if everything posts to it correctly. Two kinds of integration make that happen: the real-time module postings inside SAP (MM, SD and CO into FI) and the external interfaces to banks, the Revenue Department, POS and CRM. This map lays them out — pick an interface to see its technology, direction, trigger and error handling.

InternalMM · SD · CO → FI (real-time)
ExternalBank · Revenue Dept · POS · CRM
TechIDoc · BAPI/RFC · OData · SAP CPI
StatusMethodology reference
The core
SAP S/4HANA Universal Journal · ACDOCA — one line-item table for FI + CO
FI CO MM SD AA

In S/4HANA, FI and CO share one table (ACDOCA) — no reconciliation between them. Logistics modules post through FI in real time via account determination, so the ledger is never out of step with operations.

01 · The interfaces

Every way in and out of the ledger.

Six integration points — three internal module postings, three external system interfaces. Tap one to open its spec.

Select an interface above to see its technology, direction, trigger and error handling.
ABOUT THIS MAP

The interfaces, technologies and account-determination points are the standard SAP mechanism. The integration thinking is real — on XeerSoft I built automatic POS-to-accounting posting, GL account determination and multi-branch consolidation, which are exactly the internal-posting and external-interface patterns shown here. This is a methodology artifact, not a delivered SAP integration.

See the delivered integration work behind it →