landscape based on your Business Requirement Joerg Noack SAP America, Chief Architect SAP 2007 / Page 2 Architecture Documentation: Creating a Common Understanding Great everyone now has clear picture of the architecture ! ! ! SAP 2007 / Page 3 A guided tour through important topics SAP Solution & Enterprise Architects have to deal with building SAP application architectures What is this Session about? Basics you should have in mind when defining the application architecture Architectural Principles and basic knowledge Presenting very important information sources for creating the SAP application architecture Building architectures is pure innovation and requires constant adoption of SAP architecture principles, otherwise it is not getting any easier ! The Session material is far from complete It is a starting point for a common way of understanding Should trigger discussions for a common way to describe and model Contribute your own experience and examples to trigger a common way of learning LEGO City ARCHITECTURE DESIGN On DEVICE On DEMAND On PREMISE O R C H E S T R A T I O N
All devices All user experiences Easy to extend Instant value Line of business or suite Integrated to On Premise SOA-enabled Best-practices packages Non-disruptive enhancements SAP Business Suite 7 SAP Business ByDesign LoB on Demand Collaboration Analytics Mobile Platform In-Memory Internal Use Only Maintenance Strategy: 7+2, see release strategy, /go/releasemanagement SAP 2010 / Architecture Definition / Page 6 SAP Product Strategy Stakeholder Concerns Requirements Optimization Tooling Solution Implementation Architectural Governance & Change Management SAP Global Architecture Meta Model S A P
A r c h i t e c t u r e
A r t i f a c t s
&
D e l i v e r a b l e s
SAP Solutions SAP Best Practices Reference Content Modelling SAP Architecture Stakeholder Driven Method Business Process Core Artifacts Data Application Technology Value Strategy map Capability map Business footprint diagram Business system floor plan Data distribution diagram Data Process matrix Instance Strategy Technical Reference model Logical Application Architecure SAP Architecture core artifacts Examples and Illustration Application Deployment View Architects Need Courage SAP 2007 / Page 9 Defining Application Architecture Technical decisions required in uncertain and dynamic environment Requires expertise and leadership Incomplete Information Changing requirements Multiple Suboptimal Alternatives Different Opinions and Viewpoints No Guarantee For Success Limited Resources & Budget Strategic Changes Increasing Constraints Standard vs. Customization SAP 2007 / Page 10 6 Golden Principles For Software Architecture Simplicity find the appropriate deployment scenario for your objectives Keep Conceptual Integrity aligned to SAP product structure principles Business Scenario Oriented design Business drives technology Think Ahead your architecture is alive (), requirements change Document Your Architecture (the right way) Get Early Feedback know your stakeholders and communicate accordingly SAP ARCHITECTURE DESIGN PROCESS SAP Architecture Design Process Analyze Business Model, Operating Model Business Capabilities Assessment Business Architecture alignment. Technology Modeling Process Modeling Application Modeling Data Modeling Business Model, Operating Model, Core Competencies (Differentiating& competitive) Strategy Map, Instance strategy & Value Driver (KPI, PPI) Define E2E processes in Value Chain Define Level of standard. & harmonization Model Business Objects & Process Flow Models Documentation of Business Area, Process Group (L1, L2) Business Process, - Variant (L3), Business Process Step (l4), Activity & Variant (L5) Identify Application components Design App. Landscape incl. Legacy apps. Create Communication & Integration Model Identify Gaps & development needs As-IS analysis, Application mapping to processes Transition Plan for As-Is to To-Be architecture Communication & Integration design for Solution Architecture Decide System of record, distribution needs Define Data Harmonization & Standardization Design Target Data Architecture Availability Requirements Data Model and Data usage Distribution model & processes Technical Platform design - Map Platform landscape to Infrastructure Map Technology Components to platform for On Device, On Demand, On Premise Infrastructure & Platform architecture design Development strategy & Transport Landscape. Hosting & Design Virtualization, High availability Business Modeling Activities Deliverables SAP 2007 / Page 13 Aspects Of Application Architecture more Business Requirements Design Time Design time components, modules Reuse Model Driven Development Development Landscape Run Time Runtime components Component landscape and deployment options Communication, protocols Performance Configuration Configuration concepts Adaptability Operation and Using TCO Administration, monitoring Supportability User experience Operation and Using TCO Administration, monitoring Supportability User experience General rules for architecture work Provide options with flexible UIs to different user groups see SAP UI Strategy Keep Enhancements modification-free, educate your developer teams Use simplified models to communicate with stakeholders SAP 2007 / Page 14 Basic Principles for Defining Architecture at SAP Know Stakeholders, Requirements and Constraints Know your stakeholders and their goals (write it down) - Meet them whenever possible Dont forget the NON-FUNCTIONAL requirements SAP support standards, benchmarks, Follow your companies global and local architecture guidelines address conflicts to SAP Align With SAP Strategy Know SAP product strategy & roadmap - Note it down what it means for your architecture Apply SAP architectural standards to orchestrate all categories of the SAP platform On Premise, On Demand, On Device - Know SAP product guidelines & standards (SCN!!) TCO Follow SAP recommendations for your scenario group by maintainability & supportability (SMP Quicklink: /instguides) Always (at all times!) address sizing & scalability requirements (SMP Quicklink /quicksizer) Ensure compatibility of Product versions and release levels (SMP Quicklink: /pam) Information Lifecycle Management Plan your Data archiving strategy from the beginning Use SAP recommendations, reach our to partners Consider information Flow in your architecture (including Legacy systems) Basic Principles for Defining Architecture at SAP Architecture Best Practices Consider Open standards to ensure compatibility (APIs, configuration, enhancements) Evaluate all available deployment options (SMP Quicklink: /scl ) Plan Your instance & Landscape strategy Separate Maintenance from Project development Apply software logistics principles and practices (OTO, CTS+) and Retrofit tools SAP Architecture Design Process Analyze Business Model, Operating Model Business Capabilities Assessment Business Architecture alignment. Technology Modeling Process Modeling Application Modeling Data Modeling Business Model, Operating Model, Core Competencies (Differentiating& competitive) Strategy Map, Instance strategy & Value Driver (KPI, PPI) Define E2E processes in Value Chain Define Level of standard. & harmonization Model Business Objects & Process Flow Models Documentation of Business Area, Process Group (L1, L2) Business Process, - Variant (L3), Business Process Step (l4), Activity & Variant (L5) Identify Application components Design App. Landscape incl. Legacy apps. Create Communication & Integration Model Identify Gaps & development needs As-IS analysis, Application mapping to processes Transition Plan for As-Is to To-Be architecture Communication & Integration design for Solution Architecture Decide System of record, distribution needs Define Data Harmonization & Standardization Design Target Data Architecture Availability Requirements Data Model and Data usage Distribution model & processes Technical Platform design - Map Platform landscape to Infrastructure Map Technology Components to platform for On Device, On Demand, On Premise Infrastructure & Platform architecture design Development strategy & Transport Landscape. Hosting & Design Virtualization, High availability Business Modeling Activities Deliverables SAP Software Entities What is a Software / Product Version?` Software Component Versions Product Instances = (Software) Product Versions = Sets of Software Component Versions Sets of product instances SAP SOLUTION EXPLORER SAP Solution Explorer - for the customer SAP Solution Explorer SAP Solution Explorer Future Single Entry Point SAP Solution Explorer Roadmap ADDITIONAL CONTENT Use as reference only Additional SAP Solution engagement Platforms SAP Business Content SAP Business Solution Maps
SAP Solution Architecture as used Business Scenario oriented Industry specific Solution Maps Oriented along the Value Chain and to illustrate end-to-end business processes Link: http://solutioncomposer.sap.com/socoview A consistent multi-level solution blueprint showing the processes for a particular cross- industry solution Link: http://solutioncomposer.sap.com/socoview The solution browser will help you to discover new functionality across different SAP applications, releases and respective enhancement packages based on the application area / key capability of interest. Link: http://sapsolutionbrowser.com/Search.aspx SAP Business Scenario Maps are a graphic representation of a key business process and its business process steps Link: http://solutioncomposer.sap.com/socoview SAP Solution Explorer provides partial information about a subset of all SAP solutions and will be the future content base for functional and business content of SAP solutions Link: https://rapid.sap.com/se/ ES Workplace is the central place to view all information about available Enterprise Services by SAP, as the starting point for SOA adoption, SAP hosted PoC System available Link http://esworkplace.sap.com/socoview Solution road maps cover innovations on business solutions and processes relevant for LoB and in industries. Product road maps describe how features & functions of an SAP product are planned to progress over time. Link: http://service.sap.com/roadmaps SCL / PCL AND PAM Scenario and Process component List and Product Availability Matrix Bill-of-Material of software required for implementing a scenario/process What is a Scenario / Process Component List SP and SP Stack Constraints (optional) A SCL / PCL consists of: System Landscape ( = Object Matrix) with System Landscape Elements (-> Normally: Instances of Product Versions)
Attributes & Status
SAP Notes & Comments (optional) -> SAP Notes -> Links to important information Combination Constraints (optional) -> Constraints on combining system landscape elements => valid and invalid combinations S A P
T e c h n i c a l
v i e w
B u s i n e s s
V i e w
Combine Business Usage and Technical Implementation! Scenario and Component List /Product Component List (http://service.sap.com/scl ) SAP Business Solution View
Cross-Industry Solution Map
Industry-specific Solution Map C-Business Maps M a p
i t
t o
Business Process Hierarchy Business Scenario Process Function Business Scenario Process Function Business Scenario Business Process Process-Steps Product Version Instances
CRM IPC CRM Server
SAP NetWeaver 7.03 SAP CRM 7.02 Software Product Versions OS/DB Release Software Component Versions
SAP CRM IPC 4.0 SAP BBPCRM 4.0 Product Versions Construction Plans Product Instances and Software Component Versions * How to access PPMS data: system css -> tcode /nbopp Products and Versions Software Components and Versions SAP SCM SAP SCM 7.0 SAP SCM 5.0
SAP ABA SAP ABA 7.01 SAP ABA 7.00 SAP BASIS SAP BASIS 7.01 SAP BASIS 7.00
SAP Kernel SAP Kernel 7.01 SAP Kernel 7.00
SAP SCM SAP SCM 5.0 SAP SCM 7.0 Product Instance SAP SCM Server Product Instance
Product Instance Frontend GUIs SAP NETWEAVER SAP NETWEAVER 04 SAP EHP1 for SAP NETWEAVER 7.0 Product Instance AS ABAP Product Instance AS Java Product Instance
SAP SCM 7.0 SAP EHP1 for SAP NetWeaver 7.0 AS ABAP
SAP GUI FOR WIN. 7.10
SAP ABA 7.01 SAP BASIS 7.01 SAP J2EE ENG. 7.01 AS = Application Server SAP Kernel 7.01 SCL & PCL on SAP Service Marketplace The Scenario & Process Component List narrows the gap between the business view and the technical view. It shows you which software product version instances are needed to realize a business scenario or process and which business scenarios are possible with a given set of software product version instances. The Scenario & Process Component List is accessible on Service Marketplace via http://service.sap.com/scl. Product Availability Matrix Product Availability Matrix (PAM) Version 2.0 recently released PAM is derived from a master data registry used by SAP development Link http://service.sap.com/pam MAIN SAP DOCUMENTATION TYPES Documentation Types in the Application Lifecycle Relevant document types for designing the SAP Application Landscape - The Main SAP documentation types are a crucial and comprehensive information source for architects of all kind. - Used during the Architectural development process the relation between business requirement and technical deployment, these documents provide SAP recommendations, examples demonstrated by SAP - Complement all available technical documentation from the SAP Developer Network - Can be found at http://service.sap.com/instguides and http://help.sap.com Application Architecture Core Artifacts The Release Strategy and Master Guides are the ideal starting point for planning an SAP landscape. Main SAP Documentation Types Document Type Description Planning Guide - Available for Major SAP Solutions to provide comprehensive SAP recommendations with regard to building system landscapes, and - Provides an understanding of the overall implementation procedure for a system landscape. - Delivers based on concrete examples on how the SAP recommends to drive the implementation of a system landscape Master Guide - provides a central starting point for the technical implementation of SAP Solutions - contains all the information for the implementation of SAP Solution based business processes to facilitate the implementation and upgrade process, - Is organized by business processes and business process groups and - Describes how business Scenarios can be mapped to the required (and optional) software components, as well as listing all the required parts of other applications, such as SAP NetWeaver or SAP Business Suite Technical Infrastructure Guide - describes how you can distribute the SAP NetWeaver building blocks on physical hosts, to provide stability, performance and scalability for productive systems. - is required to decide the deployment model of your SAP Landscape. Solution operation Guide - provides a starting point for managing your SAP solutions and keeping them up and running optimally. - contains specific information for various tasks, and lists the tools that you can use to carry them out. - use this guide only in connection with other guides such as the Master Guide APPLICATION ARCHITECTURE THE VIEWS Applications are to be clustered pre-defined principles (example) SAP Business Suite Components SOX / legal compliance Business / Mission critical & sensitve data Characteristics User Interaction Components and Aplications User Interaction Clients Portal Application Strong customer/partner interaction
Characteristics Legacy Systems (as Part of Business Scenarios, non- technical) Part of a Business Scenario Require data and Process Integration Characteristics Integration Platform Orchestration Integration Communoication Characteristics Central Engines and Instances (non Java or Non-ABAP) Cross application Basic tools for all Apps Indeendent Release cycle
Characteristics Application Lifecycle Management Monitoring Reporting Implementation Support Characteristics Business System Floorplan - Legend The Business System Floorplan visualizes the current and future state of the system architecture on an instance level. Goal of the plan is to - understand the issues and opportunities with the current applications and technical architecture - Develop a future state and migration path for the technology that supports the enterprise - Provide business executives with a direction and decision making framework for IT capital expenditures - Provide information system (IS) with a blueprint for the future deployment development E-Commerce Shops ABC / DEF CRM 4.0 / R/3 4.5B
Partner Relationship AWP MS CRM + Partner Mgt. Partner Activity Mgt. Logical Application Architecture (contd.) Retailer Enterprise Supplier SCM System Supply Chain Planning System Production/ Manufacturing Planning Module Supply Chain Execution System Supplier System Retailer System Invoice Management System Production Control System Quality Control System Billing System Data Warehouse SRM System SRM System CRM System ERP System Distribution/ Transportation Planning Module Demand Planning Module Supply Planning Module Strategic Planning Module Distribution/Transportation Subsystem Sales Order Management Subsystem Purchase Order Management Subsystem Inventory Management Module Warehouse Management Module Distribution Management Module Credit Institution Credit Institution i retreive statistical/ analytical data i monitoring/ alerting i create order f order product f report defective/ excess/ MRO product i place bill, check payment status i monitoring/ alerting i monitoring/ alerting Returns Management Subsystem i reject/ confirm invoice payment f report defective/ excess/ MRO product f order materials monitoring/ alerting f create order g check stock status j schedule inbound returns k schedule outbound returns l report MRO/ defective product f check avail. f place task Logical application architecture - provides a high-level, functionality based view on its components that are necessary to the support the business requirements. - Aims to understand, document, adapt or improve the organization of the solution architecture - Builds a common understanding of the solution landscape through a general map, and to define the target for the future desired architecture which is independent of technology. (as much as possible) SAP 2007 / Page 40 Software Architecture Deployment View Deployment View - models the physical layout of a solution landscape and therefore represents the handover artifact to the Next Architecture Phase - Aims to illustrate the physical nodes on which your system components executes or support execution, as well as their physical connections and their relationships. Summary This Session should have Give you insight into Best Practices for defining SAP application architecture(s) Made you understand what information materials, collaterals and guidelines are available to gain the required knowledge Demonstrated to you, that building SAP architectures is a business-driven process and should not be attempted without a profound understanding of Business requirements Help you build the confidence of understanding the principles of SAP application architecture and a good architecture practice
THANK YOU !
Contact Details: Joerg Noack - Chief Architect Business Transformation Services SAP America, Inc., 6400 S. Fiddlers Green, Suite 1400 , Greenwood Village, CO 80111 M +1-303 243-2381 E joerg.noack@sap.com THANK YOU FOR PARTICIPATING
Please provide feedback on this session by completing a short survey via the event mobile application.
SESSION CODE: ####
For ongoing education on this area of focus, visit www.ASUG.com
APPENDIX Detailed Screen Flow for SCL / PCL View: SAP Scenarios and Realization Alternatives List View & Details of Software Product Version Instance View: SAP Scenarios and Realization Alternatives Matrix View & Additional Information View: SAP Software Product Versions and Possible Scenarios By marking the scenario / process of interest and proceeding to the next step it would take the same steps as given in the overview search option SAP Scenarios and Realization Alternatives Number of possible scenarios based on the implemented or planned product version instances as well as possible upgrades added before View: SAP Software Product Versions and Possible Scenarios Results by automatic limitation to maximum two additional components (product version instances) to be installed Results of ALL components selected, further selection by the single components in the drop-down given Further Tips & Tricks Use SAP nomenclature as much as possible, avoid simplifications (it is not just ECC, it is SAP ECC 6.0 XXX) this makes it a lot easier to understand all complexities Check regularly the SAP PAM for updates including SAP OSS for Deployment restrictions Prepare simplified, logical application views to facilitate conversations with non-technical stakeholders (K.i.s.s. and avoid t.m.d.) It is important to be able to explain the architecture to Managers Development Teams Operations & Support teams With a different levels of abstraction Make sure the views are consistent from simple view to deployment view to avoid confusion (Floorplans) Build logical Deployment units of Applications according with the same Release cycle Prepare Application Integration & Communication diagrams separately, because of different audience (developer community) Use comparable coloring as SAP documentation (suggestion) Blue ABAP Applications Yellow JAVA Applications Green - Lifecycle & Monitoring Tools Bourbon Central Engines (Trex, IGS etc.) Iterations are key to success. Socialize the Application Architecture as early as possible. Business Requirements change constantly ! You know that your architecture is wrongly-engineered if . You have problems explaining it and experienced architects dont understand it