1. Stefan Kätker, Peter Lorenz Monday, June 26, 2006 ESA Modeling in Application Platform

2.  SAP AG 2006, ESA Modeling in AP, S. Kätker, P. Lorenz - June 26 th 2005 / 2 CONFIDENTIAL Value of Modeling will be delivered via integration of Methodology, Content, Tools & structured documentation Tool Landscape Methodology Content Creation Process

3.  SAP AG 2006, ESA Modeling in AP, S. Kätker, P. Lorenz - June 26 th 2005 / 3 CONFIDENTIAL ESA Modeling in Application Plattform KEY MESSAGE ESA Modeling Methodology defined & fully operational / implemented All essential entities like BO´s, Service Definitons / Interfaces / Messages, Global Datatypes 100% covered Designed from a business perspective Based on standards (CCTS-UNCEFACT, RosettaNet, …); open Consistently used in AP  Governance Process SAP wide Methodology – rolled out to PTG as well (mySAP and ESA fast track) All SAP services modeled through ARIS and registered in 1 unified ESR; based on 1 set of GDT´s Methodology currently extended to cover composition Integrate Business Configuration and UI Large View – Click! Business Object MapCircuit Diagram

4.  SAP AG 2006, ESA Modeling in AP, S. Kätker, P. Lorenz - June 26 th 2005 / 4 CONFIDENTIAL Key Objectives and Scope of Process Integration Modeling Transparency on process integration landscape of Application Platform (“circuit diagram”) Supported integration scenarios and deployment options Cross-LDU & B2B Service Operations and their orchestration Key deliverable of product definition and application design – no “ex-post approach” From business scope to high quality Enterprise Services Repository content Models define the ESA structure of the platform Linkage between model and implementation via ESR Business Objects and Services Model structure to be reused for development planning, documentation, testing, roll-out Models are the basis for composition No business process flow modeling No modeling of process flow (instance level, time dependency) in BO’s or Process Components or in Integration Scenarios Focus on service orchestration

5.  SAP AG 2006, ESA Modeling in AP, S. Kätker, P. Lorenz - June 26 th 2005 / 5 CONFIDENTIAL ESA Modeling Process AP KEY MESSAGE Break down of (rather unstructured) business scope to structured ESA entities Models key part of development – no ex-post documentation Holistic Governance Process ensures consistent content creation across development areas Active Models controlling implementation High investment into models pays back later through higher development productivity Models reused for development plan, testing, documentation, roll-in

6.  SAP AG 2006, ESA Modeling in AP, S. Kätker, P. Lorenz - June 26 th 2005 / 6 CONFIDENTIAL Overview: Key Aspects of Modeling Methodology Methodology handbook Content creation guidelines  How to build good content according to the methodology Content Coaching Real content issues drive methodology Governance Process  Content consistency and quality cross area  Model content part of specification and kept current during dev. process Tools Basis for Governance and high quality content Integration with implementation Documentation Models have to be well integrated into documentation concept Documentation along models Reuse of model entities for composition Composition based on models

7. Tool Landscape Methodology Content Creation Process

8.  SAP AG 2006, ESA Modeling in AP, S. Kätker, P. Lorenz - June 26 th 2005 / 8 CONFIDENTIAL AP ESA Modeling: From Business Scope to Implementation Process Integration Model (in ESR) Business Object Models (in ESR) Implemen- tation Business Object Model State/Action Model Business Object Editor Integration Scenario Model Process Component Model Integration Scenario Catalog BO Map Business Scope (in Excel) Proxy generation in backend system ABAP Workbench Process Component Interaction Model

9.  SAP AG 2006, ESA Modeling in AP, S. Kätker, P. Lorenz - June 26 th 2005 / 9 CONFIDENTIAL AP ESA Modeling: From Business Scope to Implementation Process Integration Model (in ESR) Business Object Models (in ESR) Implemen- tation Business Object Model State/Action Model Business Object Editor Integration Scenario Model Process Component Model Integration Scenario Catalog BO Map Business Scope (in Excel) Proxy generation in backend system ABAP Workbench Process Component Interaction Model

10.  SAP AG 2006, ESA Modeling in AP, S. Kätker, P. Lorenz - June 26 th 2005 / 10 CONFIDENTIAL Process Interaction Modeling Approach AP 2006 Integration Scenario Catalog AP 2006 (excerpt). * Number changes significantly with scope x 1 Integration Scenario Model Sell from Stock (excerpt) x ~16* Process Component Model (PCM) Sales Order Processing (excerpt) x ~61 PCM ::= BO’s, Operations, Process Agents for cross-LDU or B2B and compound services. Intra DU Process Interactions are only represented as simple arcs, no models Process Component Interaction Model (PCIM) Sales Order Processing  Customer Invoice Processing x ~90 Enterprise Services Repository

11.  SAP AG 2006, ESA Modeling in AP, S. Kätker, P. Lorenz - June 26 th 2005 / 11 CONFIDENTIAL AP ESA Modeling: From Business Scope to Implementation Process Integration Model (in ESR) Business Object Models (in ESR) Implemen- tation Business Object Model State/Action Model Business Object Editor Integration Scenario Model Process Component Model Integration Scenario Catalog BO Map Business Scope (in Excel) Proxy generation in backend system ABAP Workbench Process Component Interaction Model

12.  SAP AG 2006, ESA Modeling in AP, S. Kätker, P. Lorenz - June 26 th 2005 / 12 CONFIDENTIAL Object Models and Data Type Models: Navigation for Reader Data Type Model (Node Data Type) - Purchase Order Item Elements Data Type Model (Global Data Type) - Amount - Business Transaction Document ID Data Type Model (Intermediate Data Type) - message header, - purchase order message payload Data Type Model (Message Data Type) - Purchase Order Request BO Node Model - Purchase Order Item Service Interface Model - Purchasing Out Business Object Model - Purchase Order ESR Process Component Interaction Model - B2B Purchasing

13.  SAP AG 2006, ESA Modeling in AP, S. Kätker, P. Lorenz - June 26 th 2005 / 13 CONFIDENTIAL Business Object Model Business Object Node Dependent Object Composition Association

14.  SAP AG 2006, ESA Modeling in AP, S. Kätker, P. Lorenz - June 26 th 2005 / 14 CONFIDENTIAL Data Type Model Element Data Type of Element Is derived from Data Type

15.  SAP AG 2006, ESA Modeling in AP, S. Kätker, P. Lorenz - June 26 th 2005 / 15 CONFIDENTIAL Data Type Model Is derived from global data type Data Type Attribute Data Type of Attribute

16.  SAP AG 2006, ESA Modeling in AP, S. Kätker, P. Lorenz - June 26 th 2005 / 16 CONFIDENTIAL Service Interface Model Operation Message Type Is derived from Message Data Type

17.  SAP AG 2006, ESA Modeling in AP, S. Kätker, P. Lorenz - June 26 th 2005 / 17 CONFIDENTIAL AP ESA Modeling: From Business Scope to Implementation Process Integration Model (in ESR) Business Object Models (in ESR) Implemen- tation Business Object Model State/Action Model Business Object Editor Integration Scenario Model Process Component Model Integration Scenario Catalog BO Map Business Scope (in Excel) Proxy generation in backend system ABAP Workbench Process Component Interaction Model

18.  SAP AG 2006, ESA Modeling in AP, S. Kätker, P. Lorenz - June 26 th 2005 / 18 CONFIDENTIAL Status and Action Management in a Nutshell Basic Elements Actions represent the process steps to be performed on a business object  Actions are service operations within the Enterprise Services Respository (ESR) that implement business logic  Performing actions change status depending on the result Status describes the progress of the business object life cycle  Driven by actions  Status values desribe the progress of the associated actions Constraints describe which actions are allowed to be performed when specific status are reached Meaning Status and action management is a constraint-based model which governs the life cycle of a business object (node) by defining constraints between status and actions Action

19.  SAP AG 2006, ESA Modeling in AP, S. Kätker, P. Lorenz - June 26 th 2005 / 19 CONFIDENTIAL Runtime Development Process and Programming Model Service Provider... « class » CL_SALES_ORDER Business Object / Core Services Provider « interface » IF_ESF_PROVIDER_ACTION DO_ACTION(NODETYPE, ID, ACTION, PARAMETERS) « interface » IF_ESF_PROVIDER_ACCESS MODIFY() RETRIEVE() RETRIEVE_BY_ASSOCIATION() ESF Update Buffer IF_ESF_PROVIDER_ACTION Implementation SalesOrder METHOD DO_ACTION.... case action. when ‚ATPCHECK‘. call method me->check_atp exporting.... when ‚CONFIRMINVOICE‘.... endcase. ENDMETHOD. S&AM RUNTIME MODEL « class » CL_SAM_RUNTIME CREATE ACTION_CHECK_ALLOWED ACTION_RESULT... DO_ACTION(SALESORDERHEADER, 4711, ATPCHECK,...) Button ATPCheck pushed Status & Action Model ESR Method CHECK_ATP Implementation METHOD CHECK_ATP. Data: l_result type SAM_result.... * Check if action is currently allowed call method SAM->action_check_allowed exporting I_ACTION = ‘ATPCHECK’ exceptions NOT_ALLOWED = 1. if not sy-subrc is initial. exit. endif. * Start of business logic implementation … * call ATP-Check from ATP Engine … * End of business logic implementation * Return result to S&AM call method SAM->action_result exporting I_ACTION = ‘ATP_CHECK’ I_RESULT = l_result exceptions ENDMETHOD.

20. Content Creation Process Methodology Tool Landscape

21.  SAP AG 2006, ESA Modeling in AP, S. Kätker, P. Lorenz - June 26 th 2005 / 21 CONFIDENTIAL Decentral content ownership Central methodology definition and governance Decentral Content Creation by Development Central Coaching and Governance Process Central documentation based on model structure Methodology Council Methodology HandbookContent Creation Guidelines KEY MESSAGE Content ownership and content creation is with development Clear guidelines, methodology discussion offline Strong governance – clear gates – no process progress w/o approval Consistency checks ensure that models and implementation stay in sync

22.  SAP AG 2006, ESA Modeling in AP, S. Kätker, P. Lorenz - June 26 th 2005 / 22 CONFIDENTIAL Key Rules for Process Integration Modeling in AP 2006 §1 For each Integration Scenario in Catalog an Integration Scenario Model is required. §2 Intra DU Process Interactions are only represented as simple arcs, no underlying detailed Process Component Interaction models. §3 For each Process Component a model is required. §4 Process Component Models represent only Business Objects, Service Operations and Process Agents for cross-DU and B2B Process Interaction. In addition, Compound Services offered by the Business Objects and by AP for usage in Composite Applications are shown. No other BO interactions, calls or services are shown. §5 For each Process Component Interaction cross DU or B2B a Process Component Interaction Model is required. §6 Process Component Interaction Model entities are represented in the Enterprise Services Repository. §7 Models and Enterprise Services Repository have to be in sync, Implementation follows modeling. §8 Each key model entity has an owner.

23.  SAP AG 2006, ESA Modeling in AP, S. Kätker, P. Lorenz - June 26 th 2005 / 23 CONFIDENTIAL Holistic Governance Process ensures consistent content creation across development areas Key Message Consistency & quality assurance on model content Basis for easy understanding and transparency of content Governance process scales, further optimization and enhanced tool support in ESR under way

24.  SAP AG 2006, ESA Modeling in AP, S. Kätker, P. Lorenz - June 26 th 2005 / 24 CONFIDENTIAL ESA Entities - Volume KEY MESSAGE ESA Models are complete – all areas are modeled in the same depth Numbers below show entities for AP Base Scope Additional ~ 3800 compound services for composites could be derived by wrapping core services with moderate effort Complete AP Content went through governance process and is well documented Process Component BO Process Component Composition Business Objects Core Services Compound Services Global Data Types Partner User Interface « belong to » « use » « call internally » «consume» Business Objects Current Scope: 241 Core Services Est. full scope: ~ 15.000 A2X Compound Services Candidates by wrapping core services: 3.800 Compound Services Current A2A, B2B: 288 Global Data Types - GDT Estimate: ~ 1200 AP ESR Content A2A B2B A2X Process Component Deployment Units Release 1.0: 15 Process Components Release 1.0: 50 Integration Scenarios Release 1.0: 17

25. Content Creation Process Methodology Tool Landscape

26.  SAP AG 2006, ESA Modeling in AP, S. Kätker, P. Lorenz - June 26 th 2005 / 26 CONFIDENTIAL Integration of Modeling Environment and ESR in NetWeaver Enterprise Services Repository NW Modeling Environment (ARIS integrated in ESR) ESR Object Editor (Part of Integration Builder) KEY MESSAGE Modeling environment and Repository closely linked Governance process support (status, reporting, consistency checks) build into modeling environment

27. Content Creation Process Methodology Tool Landscape Documentation

28.  SAP AG 2006, ESA Modeling in AP, S. Kätker, P. Lorenz - June 26 th 2005 / 28 CONFIDENTIAL Solution “Hat” ESA Modeling - Achievements Modeling entities and ESA repository entities are one! Integrated NW ESA tool environment incl. embedded ARIS All Entities stored in the ESA Repository (ESR) Modeling tools are connected allowing “drill down”: ARIS -> ESR -> BO Modeler; Interface Designer etc. Active ESR environment Implementation linked to ESR models Model based generation of data structures Model based generation of implementation “skeletons” for service providers, Agents … “Model First” development paradigm Strong implementation guidance Simulation of Implementation for early UI building possible Early scenario integration achieved during development although development happens decoupled (interface / GDT is “contract”) Early automated testing Increased development speed – ease of adding new scenarios Complete ESA Documentation for all entities – accessible e.g. in HTML Enterprise Services Repository Modeling Implementation Generated Implementation Structures Implemented Service Providers (coding!) UI Dev. Comp. Dev. Analyt ics Dev. TEST Script

29. BACKUP

30.  SAP AG 2006, ESA Modeling in AP, S. Kätker, P. Lorenz - June 26 th 2005 / 30 CONFIDENTIAL Business Process Platform – Business Object and Deployment Unit Map Back to Overview – Click! AP Engineering Version: 1.4 Status: draft Date: May, 18th 2006 Owner: S. Kätker/AP Engineering Process Modeling

31.  SAP AG 2006, ESA Modeling in AP, S. Kätker, P. Lorenz - June 26 th 2005 / 31 CONFIDENTIAL Business Process Platform – Process Integration: Circuit Diagram AP Engineering Version: 1.4 Status: draft Date: May, 18th 2006 Owner: S. Kätker/AP Engineering Process Modeling Back to Overview – Click!

32.  SAP AG 2006, ESA Modeling in AP, S. Kätker, P. Lorenz - June 26 th 2005 / 32 CONFIDENTIAL Integration Scenario Model Example Process Component inside company (drill down) Process Component Interaction (drill down) Process Component outside company Connector (to optimize layout) Deployment Unit

33.  SAP AG 2006, ESA Modeling in AP, S. Kätker, P. Lorenz - June 26 th 2005 / 33 CONFIDENTIAL Process Component Model Example Selected content from the Process Component „Sales Order Processing“ The in detail modeled Process Component Operation Business Object Outbound Process Agent Inbound Process Agent Process Component Operation Synch. Outbound Process Agent Interface

34.  SAP AG 2006, ESA Modeling in AP, S. Kätker, P. Lorenz - June 26 th 2005 / 34 CONFIDENTIAL Process Component Interaction Model - Example Process Component Message Type Interface Inbound Process Agent Operation Business Object Outbound Process Agent Link to ESR Object Editor

35.  SAP AG 2006, ESA Modeling in AP, S. Kätker, P. Lorenz - June 26 th 2005 / 35 CONFIDENTIAL.. Process component inside company.. Process component inside company Process Component Interaction Model - Process Agents Interface Out Operation1 OperationN … Interface In Operation1 In OperationN_I n … Message Out Mapping Message In Business object

36.  SAP AG 2006, ESA Modeling in AP, S. Kätker, P. Lorenz - June 26 th 2005 / 36 CONFIDENTIAL Process Component Interaction Model - Example Remember: in B2B case only the known part will be modelled! If you know, which standard interfaces the partners are using, you should model these and model mappings to them.

37.  SAP AG 2006, ESA Modeling in AP, S. Kätker, P. Lorenz - June 26 th 2005 / 37 CONFIDENTIAL Legend for Process Component Interaction Model Business object Interface Operation … Message Mapping.. Process component outside company.. Process component inside company uses/is realized by