SAP Enterprise Architecture Framework
What is SAP Enterprise Architecture Framework?
Based on The Open Group Architecture Framework (TOGAF), the SAP Enterprise Architect Framework (EAF) was developed to be an extension of TOGAF with the intention of supporting customers with an extensive SAP footprint. TOGAF and SAP EAF are intended to be complementary, with TOGAF 8.1 being the foundation for SAP EAF, and TOGAF 9.0 and higher being enhanced by contributions from the SAP EAF. The SAP EAF was initially developed by SAP to support the effective adoption of packaged software in a services-oriented enterprise.
What is SAP Enterprise Architecture Framework?
Based on The Open Group Architecture Framework (TOGAF), the SAP Enterprise Architect Framework (EAF) was developed to be an extension of TOGAF with the intention of supporting customers with an extensive SAP footprint. TOGAF and SAP EAF are intended to be complementary, with TOGAF 8.1 being the foundation for SAP EAF, and TOGAF 9.0 and higher being enhanced by contributions from the SAP EAF. The SAP EAF was initially developed by SAP to support the effective adoption of packaged software in a services-oriented enterprise.
While the TOGAF 8.1 Architecture Development Method (ADM) provides a narrative of each phase and describes the phase in terms of objectives, approach, inputs, steps, and outputs. What the SAP EAF adds is specific guidance around concepts, tasks, and terminology. In addition, narratives, worksheets describing outputs, and accelerators that can be leveraged for the ADM are included in the SAP EAF. The SAP EAF also provides a level of process flexibility that allows customers to focus on a target architecture rather than spending time defining a current architecture. Both extensions to the TOGAF 8.1 were included in TOGAF 9.0 content.
Key capabilities in the SAP Enterprise Architect Framework:
- SAP EAF Meta Model. The SAP EAF explicitly introduced a Meta Model concept as one did not exist in TOGAF 8.1, with the Meta Model enabling a comprehensive view of the entire enterprise architecture. The Meta Model classifies the enterprise into contextual and architectural elements and defines EA concepts into defined entities. These entity relationships provide the basis for a scheme for many enterprise architecture modeling tools.
- SAP EAF Artifacts. SAP EAF expanded on what was in TOGAF 8.1, which only provided a list of sample architectural views, to organize artifacts into Catalogs, Matrices, and Views (or Diagrams). The artifacts are integrated into the SAP EAF Process and Meta Model, and customers can leverage guidance and examples in SAP EAF to develop these artifacts.
- SAP Specific Mappings. The biggest area of distinct content for the SAP EAF is in providing content level guidance for organizations with a large SAP footprint. Mapping SAP content can help customers accelerate their efforts to develop their enterprise architecture as it includes references and mappings to SAP business, application, and technical content.
The SAP Enterprise Architecture Framework can offer specific advantages to SAP customers, and complements TOGAF to accelerate the development of an enterprise architecture for their business.
Ever since SAP first introduced SAP S/4HANA back in early 2015, there’s been a lot of confusion in the SAP community about what SAP S/4HANA really is and how it will affect the SAP development landscape going forward. With so much misinformation out there, these mysteries can be hard to unravel — especially for customers that have significant investments in customized solutions within their legacy SAP systems. Learn from an SAP expert what you need to know about migrating custom ABAP code to SAP S/4HANA.
This article explains how SAP HANA Enterprise Cloud enables organizations to migrate their data from their legacy on-premise applications to SAP S/4HANA or to complete a greenfield implementation of SAP S/4HANA. Learn the advantages of moving to SAP HANA Enterprise Cloud rather than relying on a classic hosting partner.








