Integration and Data Architecture for SAP S/4HANA

Keep this: job aid

Integration and data architecture card

• Per data domain: one system of record, named data owner, listed consumers and engagement systems.
• Changes flow toward the record; receivers send change requests, not second writes.
• Separate governance (right record) from integration (moving it).
• Each flow: which records, which fields, key mapping, one direction, error owner.
• Embedded analytics for operational, real-time, single-system needs; data platform for history and cross-system.
• One definition and one calculation place per KPI; reconcile it to the source.
• ISA-M: domain → style → use case pattern → technology mapping → interface request.
• Sync for answers now; async messaging for documents; events for many consumers; batch for volume.
• Controls: validate at entry, monitor in transit with business context, reconcile counts, totals and keys.