The SAP Enterprise Architecture Framework (EAF) provides a structured approach to enterprise architecture aligned with SAP solutions. This page documents how Triodian domains map to SAP EAF concepts, enabling interoperability between business architecture and SAP-centric landscapes.
Mapping file: triodian-sap.context.jsonld
Mapping Version: 1.0.0
Format: JSON-LD graph of skos:closeMatch statements
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
The mapping file states, for each Triodian domain it covers, which SAP EA concepts are a close match (skos:closeMatch). A close match means the concepts are similar enough to be used interchangeably in some contexts, without claiming they are identical.
Mapping File Correspondences
| Triodian Concept | Label | SAP Close Matches |
|---|
triodian:Strategy | Strategy | sap:StrategicGoal, sap:StrategicObjective |
triodian:Capability | Capability | sap:BusinessCapability, sap:Capability |
triodian:ValueStream | ValueStream | sap:BusinessProcessSegment, sap:ValueStream |
triodian:Policy | Policy | sap:GovernancePrinciple, sap:Policy |
triodian:Organization | Organization | sap:OrgUnit, sap:OrganizationalUnit |
triodian:Initiative | Initiative | sap:ChangeInitiative, sap:Initiative |
triodian:Information | Information | sap:DataEntity, sap:InformationObject |
triodian:Product | Product | sap:Product, sap:ServiceOrProduct |
triodian:Service | Service | sap:BusinessService, sap:Service |
triodian:Stakeholder | Stakeholder | sap:BusinessRole, sap:Stakeholder |
triodian:Performance | Performance | sap:KPI, sap:PerformanceIndicator |
Business Architecture Layer
| Triodian Domain | SAP EAF Concept (close match) | SAP Component |
|---|
| Strategy | sap:StrategicGoal, sap:StrategicObjective | SAP LeanIX (objectives) |
| Organization | sap:OrgUnit, sap:OrganizationalUnit | SAP Org Structure |
| Capabilities | sap:BusinessCapability, sap:Capability | SAP Solution Capability |
| Value Stream | sap:BusinessProcessSegment, sap:ValueStream | SAP Process Model |
| Policy | sap:GovernancePrinciple, sap:Policy | SAP GRC |
| Products | sap:Product, sap:ServiceOrProduct | SAP Product Master |
| Services | sap:BusinessService, sap:Service | SAP Service Portfolio |
| Stakeholder | sap:BusinessRole, sap:Stakeholder | SAP Business Partner |
Application Architecture Layer
| Triodian Domain | SAP EAF Concept (close match) | SAP Component |
|---|
| Information | sap:DataEntity, sap:InformationObject | SAP Data Model |
| Initiatives | sap:ChangeInitiative, sap:Initiative | SAP Solution Manager |
| Performance | sap:KPI, sap:PerformanceIndicator | SAP Analytics |
| Technology | Application Component (not in the mapping file) | SAP Solution |
Integration Points
| Triodian 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
| Triodian Attribute | SAP EAF Element | SAP Field/Object |
|---|
orgUnitTitle | Org Unit Name | ORG_UNIT_NAME |
orgType (organization) | Org Unit Type | Company Code, Plant, Sales Org |
parentOrgUnitID | Parent Org Unit | PARENT_ORG_UNIT |
roles | Org Unit Function | Function assignment |
Capability Domain → SAP Business Capability
| Triodian Attribute | SAP EAF Element | Notes |
|---|
title | Capability Name | Direct mapping |
description | Capability Description | Direct mapping |
parentCapabilityID, childCapabilityIDs | Capability Level | L1, L2, L3 hierarchy |
toolsAndTechnologies | SAP Solutions | Solution references |
Value Stream Domain → SAP Process Model
| Triodian Attribute | SAP EAF Element | SAP Component |
|---|
title | Process Name | Best Practice Content |
valueStreamStage elements (stageTitle, parentValueStreamID) | Process Steps | SAP Signavio |
inputs (stage) | Process Inputs | Input data objects |
outputs (stage) | Process Outputs | Output data objects |
performanceIndicators | Process KPIs | SAP Analytics |
Information Domain → SAP Data Architecture
| Triodian Attribute | SAP EAF Element | SAP Component |
|---|
title | Data Object Name | Master Data Object |
informationType | Data Category | Master, Transaction, Reference |
dataOwner, dataSteward | Data Owner | SAP MDG Steward |
quality | Data Quality Rules | SAP Data Quality |
SAP Solution Mapping
S/4HANA Core Modules
| SAP Module | Primary Triodian 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 Triodian 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
The mapping file states correspondences as JSON-LD nodes. Each node names a Triodian concept and lists its SAP close matches. The examples below are copied from the file's @graph; the file's @context declares the prefixes:
{
"triodian": "https://triodian.com/ontology#",
"sap": "https://sap.com/enterprise-architecture/",
"rdfs": "http://www.w3.org/2000/01/rdf-schema#",
"skos": "http://www.w3.org/2004/02/skos/core#"
}
Capability to SAP Business Capability
triodian:Capability is a close match for sap:BusinessCapability and sap:Capability:
{
"@id": "triodian:Capability",
"rdfs:label": "Capability",
"skos:closeMatch": [
{
"@id": "sap:BusinessCapability"
},
{
"@id": "sap:Capability"
}
]
}
Value Stream to SAP Process
triodian:ValueStream is a close match for sap:BusinessProcessSegment and sap:ValueStream:
{
"@id": "triodian:ValueStream",
"rdfs:label": "ValueStream",
"skos:closeMatch": [
{
"@id": "sap:BusinessProcessSegment"
},
{
"@id": "sap:ValueStream"
}
]
}
To relate a specific capability or value stream to the SAP solutions and processes that support it, record them in the Triodian record (for example in a capability's toolsAndTechnologies) and use these correspondences to translate between the two models.
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
| 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 |
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.