2310-How to Build an Efficient SAP Application Landscape Based on Your Business Requirement

8/11/2019 2310-How to Build an Efficient SAP Application Landscape Based on Your Business Requirement

1/50

Session Id 8116:

How to build an efficient SAP Applicationlandscape based on your Business

RequirementJoerg Noack SAP America, Chief Architect


2/50

SAP 2007 /

Architecture Documentation:

Creating a Common Understanding

Great

everyone now has clear

picture of the architecture

! !!


3/50

SAP 2007 /

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 oflearning


4/50


5/50

ARCHITECTURE DESIGN


6/50

On DEVICE

On DEMAND

On PREMISEORCHESTR

ATION

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-disruptiveenhancements

SAP Business Suite 7

SAP Business

ByDesignLoB 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
https://portal.wdf.sap.corp/go/releasemanagementhttps://portal.wdf.sap.corp/go/releasemanagement


7/50

Stakeholder

Concerns

Requirements

OptimizationTooling Solution

Implementation

Architectural Governance & Change Management

SAP Global Architecture

Meta Model

SAP

Architecture

Artifacts&Deliverables

SAP Solutions

SAP Best PracticesReference Content

Modelling

SAP ArchitectureStakeholder Driven Method


8/50

Business

Process

Core

Artifacts

Data

ApplicationTechnology

Value

Strategy

map

Capability

map

Business

footprint

diagram

Businesssystem floor

plan

Data

distribution

diagram

Data Process

matrix

Instance

Strategy

Technical

Reference

modelLogical

Application

Architecure

SAP Architecture core artifactsExamples and Illustration

Application

Deployment

View


9/50

Architects Need Courage

SAP 2007 /

Defining Application Architecture Technical decisions required in uncertain and dynamic environment

Requires expertise and leadership

Incomplete

Information Changingrequirements

Multiple

SuboptimalAlternatives

Different Opinions

and Viewpoints

No Guarantee

For Success

Limited

Resources &

Budget

Strategic

Changes

Increasing

Constraints

Standard vs.

Customization


10/50 SAP 2007 /

6 Golden Principles For Software Architecture

Simplicityfind the appropriate deployment scenario for your objectives

Keep Conceptual Integrityaligned to SAP product structure principles

Business Scenario Oriented designBusiness drives technology

Think Aheadyour architecture is alive (), requirements change

Document Your Architecture (the right way)

Get Early Feedbackknow your stakeholders and communicate accordingly


11/50


12/50

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


13/50 SAP 2007 /

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


14/50

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

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 requirementsSAP support standards, benchmarks,

Follow your companies global and local architecture guidelinesaddress 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 platformOn

Premise, On Demand, On Device - Know SAP product guidelines & standards (SCN!!)


15/50

TCO

Follow SAP recommendations for your scenariogroup 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 strategySeparate Maintenance from Project

development

Apply software logistics principles and practices (OTO, CTS+) and Retrofit tools


16/50

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


17/50

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


18/50

SAP SOLUTION EXPLORER


19/50

SAP Solution Explorer - for the customer


20/50

SAP Solution Explorer

SAP Solution Explorer Future Single Entry Point


21/50

SAP Solution Explorer Roadmap


22/50

ADDITIONAL CONTENT

Use as reference only


23/50

Additional SAP Solution engagement Platforms

SAP Business ContentSAP Business Solution Maps

SAP Solution Architectureas 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:


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 graphicrepresentation of a key business process

and its business process steps

Link:


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
http://solutioncomposer.sap.com/socoviewhttp://solutioncomposer.sap.com/socoviewhttp://solutioncomposer.sap.com/socoviewhttp://sapsolutionbrowser.com/Search.aspxhttp://solutioncomposer.sap.com/socoviewhttp://solutioncomposer.sap.com/socoviewhttps://rapid.sap.com/se/http://esworkplace.sap.com/socoviewhttp://service.sap.com/roadmapshttp://service.sap.com/roadmapshttp://service.sap.com/roadmapshttp://esworkplace.sap.com/socoviewhttp://esworkplace.sap.com/socoviewhttps://rapid.sap.com/se/https://rapid.sap.com/se/http://solutioncomposer.sap.com/socoviewhttp://solutioncomposer.sap.com/socoviewhttp://solutioncomposer.sap.com/socoviewhttp://sapsolutionbrowser.com/Search.aspxhttp://sapsolutionbrowser.com/Search.aspxhttp://solutioncomposer.sap.com/socoviewhttp://solutioncomposer.sap.com/socoviewhttp://solutioncomposer.sap.com/socoview


24/50

SCL / PCL AND PAM

Scenario and Process component List and Product Availability Matrix


25/50

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


26/50

SAPTechnicalview

BusinessView

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

Mapitto

Business Process Hierarchy

Business ScenarioProcess

Function

Business Scenario

ProcessFunction

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

d i C i l
http://service.sap.com/sclhttp://service.sap.com/scl


27/50

Product Versions Construction Plans

Product Instances and Software Component Versions

* How to access PPMS data: system css -> tcode /nbopp

Products and VersionsSoftware 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 InstanceSAP SCM Server

Product Instance

Product InstanceFrontend 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 SAPNetWeaver 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


28/50

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.
http://service.sap.com/sclhttp://service.sap.com/scl


29/50

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
http://service.sap.com/pamhttp://service.sap.com/pam


30/50

MAIN SAP DOCUMENTATION TYPES


31/50

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/instguidesand http://help.sap.com
http://service.sap.com/instguideshttp://help.sap.com/http://help.sap.com/http://service.sap.com/instguides


32/50

Application Architecture Core Artifacts

The Release Strategy and

Master Guides are the ideal

starting point for planning anSAP landscape.


33/50

Main SAP Documentation Types

Document Type Description

Planning Guide - Available for Major SAP Solutions to provide comprehensive SAP recommendationswith 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


34/50

APPLICATION ARCHITECTURETHE VIEWS

A li ti t b l t d d fi d i i l


35/50

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 andAplications

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


36/50

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


37/50


38/50

E-Commerce Shops

ABC / DEF CRM 4.0 / R/3 4.5B

Partner Relationship

AWP MS CRM

+ Partner Mgt.

Partner Activity Mgt.


39/50

Logical Application Architecture (contd.)

RetailerEnterpriseSupplier

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

WarehouseSRM

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

iretreive statistical/

analytical data

imonitoring/alerting

icreateorder

forderproduct

freportdefective/excess/MRO

product

iplace bill,check

paymentstatus



Returns Management Subsystem

ireject/confirminvoice

payment

freportdefective/excess/MRO

product

fordermaterials

monitoring/alerting

fcreateorder

gcheckstock status

jscheduleinbound

returns

kscheduleoutboundreturns

lreportMRO/

defective

product

fcheckavail.

fplacetask

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)


40/50

SAP 2007 /

Software ArchitectureDeployment 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.


41/50

Summary

This Session should have

Give you insight into Best Practices for defining SAPapplication 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 attemptedwithout a profound understanding of Businessrequirements

Help you build the confidence of understanding theprinciples of SAP application architecture and a goodarchitecture practice


42/50

THANK YOU !

Contact Details:

Joerg Noack - Chief Architect Business Transformation Services

SAP America, Inc., 6400 S. Fiddlers Green, Suite 1400 , Greenwood Village, CO 80111M +1-303 243-2381

[email protected]
mailto:[email protected]:[email protected]


43/50


44/50

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


45/50

APPENDIX

Detailed Screen Flow for SCL / PCL

View: SAP Scenarios and Realization Alternatives


46/50

View: SAP Scenarios and Realization AlternativesList View & Details of Software Product Version Instance


47/50

View: SAP Scenarios and Realization AlternativesMatrix View & Additional Information

View: SAP Software Product Versions and


48/50

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


49/50

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


50/50

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 teamsWith 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

Documents

2310-How to Build an Efficient SAP Application Landscape Based on Your Business Requirement