SAP EAF Mapping

The SAP Enterprise Architecture Framework (EAF) provides a structured approach to enterprise architecture aligned with SAP solutions. This page documents how Orthogramic domains map to SAP EAF concepts, enabling interoperability between business architecture and SAP-centric landscapes.

Mapping Version: 2.1
SAP EAF Version: Current
Format: Conceptual mapping with JSON examples

Overview

What is SAP EAF?

SAP Enterprise Architecture Framework is SAP's approach to enterprise architecture that covers:

Business Architecture — Business capabilities, processes, organization
Application Architecture — SAP solutions and custom applications
Data Architecture — Master data, transactional data, analytics
Technology Architecture — Infrastructure, integration, security

Why Map to SAP EAF?

Benefit	Description
SAP alignment	Align business architecture with SAP implementation
Solution architecture	Bridge business capabilities to SAP solutions
Data governance	Connect business entities to SAP master data
Roadmap planning	Link transformation initiatives to SAP projects

Domain Mappings

Business Architecture Layer

Orthogramic Domain	SAP EAF Concept	SAP Component
Organization	Organizational Unit	SAP Org Structure
Capabilities	Business Capability	SAP Solution Capability
Value Stream	Business Process	SAP Process Model
Products	Product/Service	SAP Product Master
Services	Business Service	SAP Service Portfolio
Stakeholder	Business Role	SAP Business Partner

Application Architecture Layer

Orthogramic Domain	SAP EAF Concept	SAP Component
Technology	Application Component	SAP Solution
Information	Data Object	SAP Data Model
Initiatives	Project	SAP Solution Manager
Performance	KPI	SAP Analytics

Integration Points

Orthogramic Concept	SAP Integration	Description
Capability → Technology	Solution Mapping	Capabilities enabled by SAP solutions
Value Stream → Process	Process Hierarchy	Value streams decomposed to SAP processes
Information → Data	Master Data Governance	Business entities to SAP MDG
Organization → Org Structure	Org Unit Mapping	Business units to SAP org elements

Detailed Mappings

Organization Domain → SAP Organizational Structure

Orthogramic Attribute	SAP EAF Element	SAP Field/Object
`title`	Org Unit Name	`ORG_UNIT_NAME`
`orgType`	Org Unit Type	Company Code, Plant, Sales Org
`parent`	Parent Org Unit	`PARENT_ORG_UNIT`
`responsibilities`	Org Unit Function	Function assignment

Capability Domain → SAP Business Capability

Orthogramic Attribute	SAP EAF Element	Notes
`title`	Capability Name	Direct mapping
`description`	Capability Description	Direct mapping
`capabilityLevel`	Capability Level	L1, L2, L3 hierarchy
`enablingSolutions`	SAP Solutions	Solution references

Value Stream Domain → SAP Process Model

Orthogramic Attribute	SAP EAF Element	SAP Component
`title`	Process Name	Best Practice Content
`stages`	Process Steps	SAP Signavio
`inputs`	Process Inputs	Input data objects
`outputs`	Process Outputs	Output data objects
`performanceIndicators`	Process KPIs	SAP Analytics

Information Domain → SAP Data Architecture

Orthogramic Attribute	SAP EAF Element	SAP Component
`title`	Data Object Name	Master Data Object
`informationType`	Data Category	Master, Transaction, Reference
`owner`	Data Owner	SAP MDG Steward
`quality`	Data Quality Rules	SAP Data Quality

SAP Solution Mapping

S/4HANA Core Modules

SAP Module	Primary Orthogramic Domains	Mapping Type
Finance (FI)	Finance, Performance	Strong
Controlling (CO)	Finance, Capabilities	Strong
Sales & Distribution (SD)	Customer, Value Stream, Products	Strong
Materials Management (MM)	Supply Chain, Products	Strong
Production Planning (PP)	Manufacturing, Value Stream	Strong
Human Capital (HCM)	People, Organization	Strong
Plant Maintenance (PM)	Technology, Capabilities	Moderate

SAP Cloud Solutions

SAP Solution	Primary Orthogramic Domains	Use Case
SAP SuccessFactors	People, Organization	HR processes
SAP Ariba	Supply Chain, Finance	Procurement
SAP Customer Experience	Customer, Products, Services	CRM
SAP Analytics Cloud	Performance, Information	Reporting
SAP Integration Suite	Technology, Information	Integration

Example Mapping

Capability to SAP Solution

{
  "orthogramicCapability": {
    "id": "cap-order-management",
    "title": "Order Management",
    "description": "Capability to receive, process, and fulfill customer orders",
    "capabilityLevel": "L2",
    "owner": "Sales Operations Director"
  },
  "sapMapping": {
    "eafLayer": "Business Architecture",
    "eafConcept": "Business Capability",
    "enablingSolutions": [
      {
        "solution": "SAP S/4HANA",
        "module": "Sales & Distribution (SD)",
        "processes": [
          "Order Processing (OTC)",
          "Pricing and Conditions",
          "Availability Check"
        ]
      },
      {
        "solution": "SAP Customer Experience",
        "module": "Commerce Cloud",
        "processes": [
          "Online Order Capture",
          "Order Status Tracking"
        ]
      }
    ],
    "masterDataObjects": [
      "Customer Master",
      "Material Master",
      "Pricing Conditions"
    ],
    "transactionTypes": [
      "Sales Order",
      "Delivery",
      "Billing Document"
    ]
  }
}

Value Stream to SAP Process

{
  "orthogramicValueStream": {
    "id": "vs-order-to-cash",
    "title": "Order to Cash",
    "description": "End-to-end value stream from customer order to payment receipt",
    "stages": [
      "Order Capture",
      "Order Fulfillment",
      "Delivery",
      "Invoicing",
      "Payment Collection"
    ]
  },
  "sapMapping": {
    "sapProcess": "Order to Cash (OTC)",
    "sapBestPractice": "J63 - Order to Cash",
    "processSteps": [
      {
        "stage": "Order Capture",
        "sapTransaction": "VA01",
        "sapObject": "Sales Order"
      },
      {
        "stage": "Delivery",
        "sapTransaction": "VL01N",
        "sapObject": "Outbound Delivery"
      },
      {
        "stage": "Invoicing",
        "sapTransaction": "VF01",
        "sapObject": "Billing Document"
      }
    ]
  }
}

Implementation Approach

Mapping Lifecycle

Best Practices

Start with capabilities — Map L1/L2 capabilities to SAP solution areas
Use SAP Best Practices — Reference SAP's process content library
Align data objects — Ensure Information domain maps to SAP master data
Document gaps — Note where SAP coverage is partial
Version control — Track mappings against SAP release versions

Usage Guidelines

When to Use SAP EAF Mappings

SAP implementations — New S/4HANA or cloud deployments
SAP upgrades — Migrating from ECC to S/4HANA
Solution architecture — Designing SAP-centric landscapes
Data migration — Planning master data transitions

Integration with SAP Tools

SAP Tool	Integration Point
SAP Solution Manager	Initiative tracking, project mapping
SAP Signavio	Process modeling, value stream alignment
SAP LeanIX	Enterprise architecture, capability mapping
SAP MDG	Master data governance, information domain

For Data Engineers

SAP EAF mappings help bridge business architecture to SAP's data model. When populating data catalogs, use these mappings to connect business entities (from the Information domain) to their corresponding SAP master data objects and transactional tables.

BIAN Mapping — Banking industry mapping
FIBO Mapping — Financial ontology mapping
Technology Domain — Technology architecture modeling

Overview​

What is SAP EAF?​

Why Map to SAP EAF?​

Domain Mappings​

Business Architecture Layer​

Application Architecture Layer​

Integration Points​

Detailed Mappings​

Organization Domain → SAP Organizational Structure​

Capability Domain → SAP Business Capability​

Value Stream Domain → SAP Process Model​

Information Domain → SAP Data Architecture​

SAP Solution Mapping​

S/4HANA Core Modules​

SAP Cloud Solutions​

Example Mapping​

Capability to SAP Solution​

Value Stream to SAP Process​

Implementation Approach​

Mapping Lifecycle​

Best Practices​

Usage Guidelines​

When to Use SAP EAF Mappings​

Integration with SAP Tools​

Related Documentation​