Sap fundamentals overview_for_sap_minors

1 © Copyright 2014 EMC Corporation. All rights reserved. © Copyright 2014 EMC Corporation. All rights reserved.

SAP Minors Program TEEAM Region Webex Series

“”SAP Fundamentals“

Cenk Ersoy Advisory SE [email protected]


SAP Minors Program

Please see the “SAP Minors Program Global Kickoff” presentation by Ken Saul at: • https://community.emc.com/docs/DOC-28232

or

https://emccorp.webex.com/emccorp/lsr.php?RCID=a341b36ea8854d46b7c84d31f4059168

https://community.emc.com/docs/DOC-28232







SAP Minors Program

SAP Minors Community Page:

https://community.emc.com/community/connect/presales/presalesminorsprogram/presales-minors-sap

SAP Minors Training Path and Training Modules are available here:












If you are an EMC employee, engage your local SAP Champion

Name Email Country

Chetan Govind [email protected] Saudi Arabia

Johannes Quendler [email protected] Austria

MohD Basti [email protected] UAE/Gulf

Maciej Przepiorka [email protected] Poland

Mark Potter [email protected] South Africa

Victor Seme [email protected] Kenya

If you are an EMC partner, please engage your Partner Manager

mailto:[email protected]
















Engage your SAP Specialist

([email protected])

How will they help you?

Develop a strategy to have meaningful conversations with key SAP resources at your customer accounts

Identify sources of information and map the current customer landscape

Determine the customer’s compelling events

Educate the customer on EMC innovations that have successfully addressed customer challenges


Agenda • What is SAP • SAP Licensing • SAP Industry Solutions • SAP Business Suite • Netweaver • SAP Landscapes • Clients • Transports • Migrations • SAP Automation • HANA • Customer Assessments • Resources • Q/A


COMPANY XYZ

factory


ENTERPRISE RESOURCE PLANNING

Source: SAP AG


SAP FACTS • SAP stands for “Systems, Applications and Products” • Founded in 1972 • Headquarters in Walldorf, Germany • with a vision : “to develop a software package that stiches a company’s diverse business functions together” •One of the largest enterprise applications provider (including business software, BI and DWH) worldwide

Source: SAP AG


http://www.sap.com/solution.html

Source: SAP AG

http://www.sap.com/solution.html


SAP PORTFOLIO & LICENSING

SAP licensing is a combination of “package” licenses and “named user” licenses.

Source: SAP AG


SAP FLAGSHIP PRODUCT: BUSINESS SUITE 7

Business Suite, including Enterprise Resource Planning (ERP)

Product Lifecycle Management (PLM) Customer Relationship Management (CRM)

Supply Chain Management (SCM) Supplier Relationship Management (SRM)

------------------------- Business Data Warehouse (BW) and -Intelligence (BI)

(*) Almost every customer will have Solution Manager (SolMan). (**) Enterprise Central Component (ECC) is a component of ERP.


• There are also other components of the SAP Business Suite for special purposes, such as:

• SAP BusinessObjects Governance

• Risk and Compliance solutions (GRC)

• Quality Issue Management (QIM)

• Supplier Lifecycle Management (SLM)

• SAP Document Builder etc

SAP FLAGSHIP PRODUCT: BUSINESS SUITE 7


SAP PORTFOLIO & LICENSING

Business One : http://www.sap.com/solutions/sme/businessone Business By Design http://www.sap.com/solutions/sme/businessbydesign Business All-in-One : http://www.sap.com/solutions/sme/businessallinone Business Suite http://www.sap.com/solution/lob/finance/software/business-suite-apps/index.html

http://www.sap.com/solutions/sme/businessone

http://www.sap.com/solutions/sme/businessbydesign

http://www.sap.com/solutions/sme/businessallinone

http://www.sap.com/solution/lob/finance/software/business-suite-apps/index.html






factory

Source: SAP AG


IMPACT OF SAP

•The decision to implement SAP is a C-level decision. • It impacts all aspects of a company (transformation!):

•Business •People •Processes •Technology

• SAP itself is evolving rapidly.


Timeline Year Release

SAP Release Architecture

1973 SAP R/1 Mainframe

1979 SAP R/2 Mainframe

1992 SAP R/3 Client-Server

1998 SAP R/3 Release 4.0B Client-Server

1999 SAP R/3 Release 4.5B

Client-Server

1999 SAP R/3 Release 4.6B

Client-Server

2001 SAP R/3 Release 4.06C

Client Server, Web Application

2003 SAP R/3 Enterprise Relase 4.70

Client Server, Web Application

2004 SAP ECC 5.0 ERP (mySAP ERP 2004) NetWeaver AS ABAP+Java, SOA

2005 SAP ECC 5.0 ERP (mySAP ERP 2006) NetWeaver AS ABAP+Java, SOA

2009 SAP Business Suite 7 (ERP 6, EhP 4) NetWeaver AS ABAP+Java, SOA, Business Process Platform, Composite Application Platform

2011 SAP Business Suite7 (ERP 6, EhP 6) NetWeaver AS ABAP+Java, SOA, Business Process Platform, Composite Application Platform

2013 - SAP Business Suite 7 (ERP 6, EhP 7) – Netweaver 7.4


SAP &

BUSINESS

ARCHITECTURE


• Discovering, defining, and mapping needs back to a company’s business vision and forward to an application strategy is the subject of business architecture. • There is “business view”, “functional view” and “technical view” of any company. The “busines view” is what the company does, the “functional view” is how the company does its job (processes, applications, modules etc) and “technical view” deals with the infrastructure. • ”Business blueprinting” entails defining a firm’s to-be business processes, identifying gaps between the current state and this to-be state, determining how well SAP’s templates can be applied, identifying and prioritizing the need for customizations to these templates, and then locking down the scope of work necessary to make all this happen.

BUSINESS ARCHITECTURE


Business Processes are called “Business Scenarios” in SAP

Source: SAP AG


IT Practice

IT Scenario Scenario variant

Usage Type

Technical Platform IT

Busin

ess

User Productivity Enablement

SAP Mobile Infrastructure (MI)

SAP Web AS ABAP + JAVA

Example: equip field sales force with mobile devices

Mobilizing Business Processes Enabling Mobile Applications for Occasional Connection

Source: SAP AG


SAP NETWEAVER


Solution Platform

ERP = Enteprise Resource Planning (used to be called ECC) CRM = Customer Relationship Management PLM = Product Lifecycle Management SCM = Supply Chain Management SRM = Supplier Relationship Management BI = Business Intelligence (data mining, business reporting etc). EP = Enterprise Portal PI = Process Integration (XI) MI = Mobile Infrastructure MDM = Master Data Management


NetWeaver Application Servers (WebAS)

ABAP Java ABAP/Java

Single Stack

Dual Stack

ABAP = Advanced Business Applications Programming

Single Stack

Source: SAP AG


Basic Terminology

• SAP Module : ERP

• SAP Instance : SID

• Database : Oracle, SQL-Server

etc

• OS: Unix, Windows etc

• Server : HP, DELL etc SERVER

Operating System

Database

SAP Instance

NetWeaver

ERP BI CRM

An SAP “instance” is a group of processes that are started and stopped at the same time. Instances can reside on one host, or they can be distributed on several hosts.

(SID = Security Identifier Definition a.k.a. System ID, Instance ID)


Tiered Architecture Options

DB & CI

OS

CRM

Presentation

Layer

Database &

Application

Layer

(Combined)

2-Tier Architecture 3-Tier Architecture

DB

OS

Presentation

Layer

Application

Layer

App

OS

App

OS

Database

Layer

Online

Process

Batch

Process

Database

Process

Online

Process

Batch

Process

Database

Process


Three-Tiered Architecture

The three layers are:

Presentation layer:

– The PC-based GUI interface that is used by the end-user community. VDI replaces the typical old style PC.

Application layer:

– The SAP application servers that service requests for data and manage the interface to the presentation layer.

Database layer:

– The actual DBMS that communicates with the application servers to fulfill their requests for data.


Source: SAP AG


Operating System / Database

DB2 / UDB (DB6)

DB2 / OS400 (DB4)

DB2 / z/OS (DB2)

MaxDB Oracle SQL-Server Sybase ASE

AIX Yes No No Yes Yes No Yes

HP-Unix Yes No No Yes Yes No Yes

Linux (SUSE / Red Hat)

Yes No No Yes Yes No Yes

OS/400 No Yes No No No No No

Solaris Yes No No Yes Yes No Yes

Windows Yes No No Yes Yes Yes Yes

z/OS No No Yes No No No No

Supported Platforms

Average size of an SAP database is 6TB


SAP SYSTEM


WHAT IS A SAP SYSTEM? • An SAP System (Solution/Application)

consists of:

• Exactly one database instance , one

central instance and one or more

dialog instances.

• The instance that runs Message

Service and Enqueue Service in an

SAP system is known as the central

instance. There should be a single

central instance configured for every

SAP system

• Beginning with Netweaver 7.1 the “central instance” is now called “primary application server instance”. Also the “dialog instance” is now called “additional application server instance”.


HORIZONTAL SCALING

Central Instance is the hearthbeat of SAP !! CI = Message Server + Enqueue Server


SAP

LANDSCAPES


Business Transaction Spans Modules

ECC

BW

CRM

Portal

SCM

extract extract

interface interface


QA Disaster Recovery Develop and Test Production

User Access

TCP/IP

Remote Local

Network

SCM ERP SCM ERP SCM BI

Firewall

Portal XI MDM CRM

Network

ERP SCM BI

Archive Backup

Network

SAP “Landscape”

ERP


SAP Landscape with Web Dispatcher


Examples: Dev, QA, Test, Pre-Prod, Prod, Training, Sandbox


An Example SAP Landscape


CLIENTS


Clients in a SAP system A Client

• Is a unit of the SAP system that is technically, organizationally and commercially self-contained

• Has its own set of user master data, application data and customizing

• Users from different companies can use the same SAP application and not interfere with each other

Implementation • Users connect to a client

• Application data belongs to a specific client

Client 100 • Application data (invoices, orders …) • Client specific customizing (company

codes …) • User master data


Clients in a SAP System

Repository Objects (such as structures, programs, transactions, function modules)

Cross-client customizing

Client 100 • Application data (invoices, orders … • Client specific customizing (company

codes … • User master data

Client 200

Client ###


Clients in a SAP system

Default clients:

• 000: default

• 001: SAP template client

• 066: Early Watch client


Client Copies

Source: SAP AG


Business Transactions are at Client Level

ECPCLT800

BWPCLT200

CRPCLT100

Portal

SCPCLT200

extract extract

interface interface


TRANSPORTS


SOFTWARE LOGISTICS IN SAP

• SAP defines the process of transporting changes from the development system, through a test system, to a production system as “software logistics”.

• SAP software logistics includes such topics as SAP system landscapes, SAP change management, SAP client concepts, SAP client instance strategies, SAP transport strategies, SAP transport management system, SAP multi-release strategies, N and N+1 architectures

• Moving code from development to production is called “promote to production strategy”.


Transport Sequence

SAP

Database

SAP

Database

SAP

Database

Development Acceptance Production

Transport Directory (/usr/sap/trans)

export import import YOU CAN NOT UNDO TRANSPORTS


MIGRATIONS

IN SAP


Types of SAP migration

Homogeneous Migration ( System Copy ) / Unicode Migration

• No change of OS and DB

Heterogeneous Migration / Unicode Migration (replatforming)

• Changing the OS ( e.g. AIX Windows 2008 )

• Changing the DB ( e.g. Oracle SQL Server 2008 )

• Changing both ( e.g. OS400/DB2 Solaris / Oracle 11g )

• Virtualization

Heterogeneous migrations require SAP certified consultants and project approval from SAP.


Homogeneous Migrations

Source: SAP AG


SYSTEM CLONE/ COPY / REFRESH

Source: SAP AG


Homogeneous Migrations

SAP

Database

SAP

Database

Acceptance Production

System Copy (database

tools)

SAP

QASCLT200

SAP

PRDCLT200

Acceptance Production

Client Copy (RFC)

Source: SAP AG


Heterogeneous Migrations

(Replatforming or OS/DB Migrations)

Changing the OS ( e.g. AIX Windows 2008 ) Changing the DB ( e.g. Oracle SQL Server 2008 ) Changing both ( e.g. OS400/DB2 Solaris / Oracle 11g )

Heterogeneous migrations require SAP certified consultants and project approval from SAP.


Requirements for Heterogeneous Migrations (PROD)

SAP must be informed of intention to migrate

Migration must be done by a certified consultant

Send questionnaire & detailed project plan to SAP to get Migration Key (http://service.sap.com/migrationkey )

Hardware / Database / SAP-Kernel must be supported

Must be done with SAP Migration tools. SAP migration tools are release, vendor and OS independent.

http://service.sap.com/migrationkey


NEED SOME SERIOUS SAP AUTOMATION HERE

Source: SAP AG


SAP &

AUTOMATION


• SAP offers “Software Provisioning Manager 1.0” which can be used for system copy as well as software installation and un-installation. See http://scn.sap.com/docs/DOC-30430. • SAP Landscape Virtualization Management (LVM) is an add-on to NetWeaver 7.3 and it uses Java AS. LVM provides application virtualization and management of SAP systems through a single user interface. • EMC Replication Manager helps automate some of the post copy actions. EMC Replication Manager can be integrated with TDMS. However RM for SAP supports only Linux and HP-UX.

SAP & AUTOMATION

http://scn.sap.com/docs/DOC-30430




• Other third party software such as eCloudManager by fluidOps, Redwood, Libelle, UC4, Cisco Intelligent Automation (not Cisco Tidal Enterprise Scheduler), Basis Technologies, BlueSystemCopy by Empirius and Cloupia (acquired by Cisco) can be used to automate cloning, copying and post processing.

SAP & AUTOMATION


LVM

Source: SAP AG


SAP LVM Infrastructure for EMC Storage

LVM Management Server LVM Services and Resources

SAP Host Control Agent EMC Solutions Enabler 7.5 SAP LVM Managed Systems

SAP Host Control Agent EMC SMI-S EMC Storage Integrator (ESI) for SAP LVM

Centralized Storage (Block/File) Symmetrix VMAX, VMAXe, DMX VNX, CLARiiON CX4


LVM

• See http://scn.sap.com/docs/DOC-43343 on how vBlock integrates with LVM. • See http://scn.sap.com/docs/DOC-42216 for details on how different vendors integrate with LVM 2.0 • LVM can be customized to add custom tabs, integrated additional applications, extend functionality of built-in activities, integrate custom replication, define custom actions such as provisioning etc. See http://scn.sap.com/docs/DOC-48942 for details on customizing LVM.











In-Memory

Computing

&

SAP HANA


http://no-disk.com

http://no-disk.com/

http://no-disk.com/

http://no-disk.com/


What is SAP HANA?

Prepackaged “in-memory DB” solution, delivered as installed and preconfigured system (appliance model) to the customer site.

Built-in Tools for lifecycle management, security optimization and operation.

Best practices in tasks, concepts and procedures necessary for the ongoing operation

Installed on certified hardware only!

http://help.sap.com/hana_appliance

http://help.sap.com/hana_appliance


• It is an in-memory DB optimized for both transactional and analytical workload

• The SAP HANA database is a hybrid in-memory database that combines row-based, column-based, and object-based database technology.

• Real-time analysis for high volumes of data (with changing data value over time)

• Business performance improvements => Ad-hoc planning, simulations, etc…

• Better qualified analysis => Queries against larger amount of data in less time

SAP HANA KEY POINTS:

Fast decisions on “real” data in “real time” !


• No pre-processing of data

• No resource sharing

• One appliance per SAP HANA System (SID) For a usual PRD-QAS-DEV landscape three “appliances” are recommended At least two appliances are required if QAS and DEV run on one together

• No other apps can run on HANA

• Strategic to driving new competitive advantage and revenue growth

• Platform for SAP ERP moving forward (“Suite on HANA”)

SAP HANA KEY POINTS:


SAP HANA

The defined components for SAP HANA are: • Intel Xeon E7-4870 CPU • 128 GB per CPU socket max • 10 GbE or 8 Gb FC redundant storage connectivity • 10 GbE redundant HANA node to HANA node connectivity • 1 GbE / 10 GbE redundant uplink • Complete the performance test in less than 1500 seconds • I/O performance of the data device has to show >600 MB/sec • SuSE Linux Enterprise Server 11 SP2 or • SuSE Linux Enterprise Server for SAP SP2


SAP HANA Vision ...everything on one HANA database

HANA 1.0

HANA nxt

SAP ERP

RDBMS

new Apps

HANA 1.0

SAP BW

SAP ERP 1 SAP ERP n …

SAP BW non-SAP

TODAY

VISION

New BW Scenario

BW as the first SAP application running 100% on HANA

Side-by-side Scenario

SAP ERP running on a traditional RDBMS. In addition first programs can alternatively benefit from HANA (e.g. CO-PA)

new apps on HANA

One Store for Data and Analytics

SAP HANA only persistence layer for SAP Business Suite

SAP Business Suite optimized for in-memory computing

71 © Copyright 2014 EMC Corporation. All rights reserved. © Copyright 2014 EMC Corporation. All rights reserved. VCE Confidential

© 2013 VCE Company, LLC. All rights

reserved.

• THREE WAYS TO DEPLOY HANA

71

HANA Appliance Types

Scale-Up

Single-Node

Internal Disk

No HA

Software DT

XS = 128 GB S = 256 GB M = 512 GB L = 1024 GB

Scale-Out

Multi-Node

Shared Disk

Integrated HA

Software/Storage DT

2 – Many nodes 512GB per node

Tailored DC Integration

Multi-Node

Shared Enterprise Disk

Integrated HA

Software/Storage DT

Any certified server configuration


Size Model Intel CPU

Memory Form Factor

Log Persistence

Data Storage

XSmall C260 2 x E7 128GB (16 x 8GB)

rack 6 x 100GB SSD 10 x 600GB

Small C260 2 x E7 256GB (32 x 8GB)

rack 6 x 100GB SSD 10 x 600GB

Medium C460 4 x E7 512GB (32 x 16GB)

rack 2 x FusionIO 12 x 600GB SAS

Large B440 8 x E7 1TB 2 blades (+1 HA)

EMC VNX5300 EMC VNX5300

XL B440 16 x E7 2TB 4 blades EMC VNX5300 EMC VNX5300

XXL B440 64 x E7 8TB 16 blades EMC VNX5300 EMC VNX5300

Cisco HANA Offerings: Single System (SS) and Scale-Out (SO) Solutions

EMC/VCE offer ONLY “scale-out” HANA solutions


SAP HANA PAM Some of the supported Hardware Platforms for SAP HANA Scale out (Dec 2013)

See https://help.sap.com/hana_appliance Additional Info PAM

https://help.sap.com/hana_appliance


HANA Tailored Datacenter Integration

As of Jan/2014 only VMAX is TDI certified. VNX certification is pending.

Source: SAP AG


Real-Time Data Platform (RTDP)

• It is a Data Lifecycle Management framework, integrating HANA, Sybase IQ, Sybase ASE and HADOOP file system, to enable a company wide data management and orchestration strategy:

• SAP HANA is for fast data (OLTP + OLAP)

• Sybase IQ is for historic “not so fast” data (OLAP)

• Sybase ASE is operational “not so fast” data (OLTP)

• HDFS is big data expansion to HANA (DB & non-DB data, high volumes)


SAP NETWEAVER

ADMINISTRATION


Typical Tasks of Netweaver (BASIS) Admin

Monitoring (including performance)

Troubleshooting

Backup / restore

Export / import

Migrations

System Cloning + post clone clean-up

In house scripting

Client copies

Scheduling backgroung tasks

User & Output configuration / management


CUSTOMER

CHALLENGES


Key Observations on SAP

• SAP landscapes are complex • Applications are exchanging messages with other applications • Difficult to maintain consistency across applications and DBs • Difficult to make changes • Difficult to undo changes • There are several different landscapes (DEV, QA, PROD etc) • Need automated tools to manage the environment Note: SAP is not necessarily always mission-critical for the customer.


WHY SAP IS SO SUCCESSFUL

Focus on business processes, not just software

Customizable SAP source code on the DB

OS/DB abstraction and standard programing language (ABAP and OpenSQL)

Development environment is provided

Repository of objects, functions, etc – reusable and business related

No limitation of functionality due to licensing restrictions (end of year audit)

Comprehensive online information both for customers and partners


SAP customer compelling reasons

Converged infrastructure for

SAP

Replatforming

HANA deployment

• Cisco/EMC HANA Appliance solution for Scale-Out, HA, Data Protection

• VCE HANA Appliance

SW upgrade

Cloud journey

Greenfield deployment

Acquisitions and merges

Growth and consolidation

• UNIX to Linux • Oracle on Itanium • Proprietary platform • Obsolete or inefficent platform

• Unicode or <4.7 • Good candidate for archive

• Intel bare metal to virtual

• Automation • Capex to Opex model

• Application migration

• New SAP functions • New geos • Datacenters consolidation • Physiological growth (no archive)

• New geos • Compliancy • Subsidiaries • M&A


CUSTOMER

ASSESSMENTS


Questions to Ask:

•Which SAP applications do you have ? •What are the versions? •Which OS ? •Do you use virtualization ? Which one ? •Which DB ? •Do you have DR in place ? How ? •Do you have active/active operation ? •What do you want to improve ? •Who is your SAP technology partner ?


RESOURCES


Resources

• http://scn.sap.com/welcome • http://www.news-sap.com/ • https://community.emc.com/community/connect/everything_sap (start here) • http://www.saponwin.com • http://www.saphana.com • http://help.sap.com • http://service.sap.com (Need account)

http://scn.sap.com/welcome

http://scn.sap.com/welcome

http://www.news-sap.com/




https://community.emc.com/community/connect/everything_sap

https://community.emc.com/community/connect/everything_sap

http://www.saponwin.com/



http://www.saphana.com/





http://help.sap.com/

http://help.sap.com/


THANK YOU

Sap fundamentals overview_for_sap_minors

Technology

Transcript of Sap fundamentals overview_for_sap_minors