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.

7439 results

  1. Extending and Modifying SAP Standard with Business Add-Ins and the New Modification Assistant

    Reading time: 1 mins

    Up until now, Customer Exits and Modifications were the only development techniques available for extending and modifying standard SAP applications. Release 4 introduces two new techniques – Business Add-Ins and the Modification Assistant. Business Add-Ins are predefined exit points in a source that allow developers to either insert their own logic during implementation or simply…...…
  2. Real-Time, Outbound Interfaces to Non-R/3 Systems Made Simple with Change Pointers, Message Control, and Workflow

    Reading time: 1 mins

    Developers often struggle with custom ABAP/4 code or database logging to devise ways to track changes to data and then to trigger output of that changed data across outbound interfaces to non-R/3 systems. The onus of creating a way to track changes as they occur rests squarely on the shoulders of these developers, but it…...…
  3. Size Does Matter – Strategies for Successful SAP R/3 Capacity Planning

    Reading time: 2 mins

    Capacity planning is not a trivial task. Choose your hardware vendor and equipment carefully, and upgrades will pose few problems. Choose the wrong vendor-model combination, and you will be forced to make extensive changes to your hardware and operating system that will entail extensive planning and testing, and could ultimately require all new equipment. So…...…
  4. An Introduction to SAP’s New and Improved Frontend Printing

    Reading time: 1 mins

    Dr. Stefan Fuchs describes a new spool access method that allows the transfer of print data from the application server to the current location of the SAPGUI. From there the data is sent to the local spooler on the user’s particular frontend. That new spool access method — method “F” — is what SAP calls…...…
  5. Achieving a More Manageable and Reliable R/3 Spool Server Landscape Using Release 4 Output Classifications, Logical Servers, and Alternate Servers

    Reading time: 2 mins

    Three new output features give rise to a more manageable, more reliable R/3 spool server environment — classifications, logical servers, and alternate servers. With Release 4, classifications of output devices and spool servers (along the lines of production, high-volume, desktop, and test printing) are now made possible within R/3 itself. This helps you ensure that…...…
  6. ABAP Programming – An Integrated Overview

    Reading time: 2 mins

    With Release 4.0 and the debut of ABAP Objects, SAP is replacing the classical distinction between reporting and transaction programming with an integrated view, recognizing the simple fact that all application logic is programmed in ABAP and that the application can communicate with the user via screens and with the database via a common interface…....…
  7. A Beginner’s Guide to Accessing BAPIs with the SAP DCOM Connector

    Reading time: 2 mins

    This article will introduce you to the basic design principles behind SAP DCOM Connector (SDC), show you how to build BAPI-enabled applications with SDC in Visual Basic, and discuss some advanced concepts for SDC-based applications. In order to keep things simple, we will assume that our applications are built without MTS. So I will not…...…
  8. Extending SAP Business Workflow with Web Forms

    Reading time: 1 mins

    Web forms are the means by which developers can create applications that enable users to start workflows and execute work items from the comfort of a Web browser. A Web form is a simple, intuitive interface, which is made up of a relatively short list of fields and a “Submit” button. This interface obviates the…...…
  9. Lessons in Logon Load Balancing

    Reading time: 2 mins

    In large SAP R/3 environments that require multiple application instances, you can achieve intelligent, automated distribution of workload across multiple application instances, with minimal impact to end users, through logon groups. This article explains how logon groups work and how to use them to establish a logon load balancing strategy that can improve system performance,…...…
  10. Leveraging the R/3 Warehouse Management Structure with the MM-MOB and WM-LSR Interfaces

    Reading time: 2 mins

    /Project ManagementIntegrating the R/3 Warehouse Management (WM) module with mobile data entry devices and external warehouse management systems is made possible by two interfaces — Mobile Data Entry (MM-MOB), which enables mobile entry and transfer of data to and from SAP, and Warehouse Control Unit (WM-LSR), which enables the sending and receiving of information between…...…