Kraft Global SAP Landscape

Catalyst SAP Infrastructure

Catalyst SAP Implementation

GLOBAL SAP INFRASTRUCTURE

Global/West SAP Landscape Model

Global/West SAP Instance Landscape

Global/West SAP Instance / Client Strategy Model

Global SAP Change Management Status Diagram

Global SAP Change Management Workflow Diagram


Overview

Business RequirementsFollowing business requirements to support Catalyst Team Project:

Ability to support concurrent Development and Testing Streams Environment and processes must support an aggressive and dynamically changing

deployment schedule Ability to support Rollouts as well as Functional Releases Reliable Production Support Stream

Goals to be Achieved Improve quality of development, test and migration process Reduce Production Freeze Window Effective use of landscape Improve cycle times for cutover process

Key Decisions Business requirements drive all other decisions Business requirements for Select Global Landscape Single Versus Multiple Development and Test Environments (other than Production Support) Use of BCV or similar rapid replication technology for Production Support and Next Wave

Testing


Landscape Dynamics – Deployment Basics

Deployment Basics - DefinitionsFunctional Releases – Introduces new SAP/business process functionality, or major rework of

business process functionality during a future deploymentRollout Releases – Deploys functionality that already exists in Production Stream to new

locations. Examples: bring new plants online. Primary changes that will occur during Rollout releases include additional master and transactional data, new user population, and possible minor adjustments to configuration to add plant specific configuration data. All changes related to Rollout Releases should originate in the Production Support Stream, and will be manually migrated to all streams below.

Technical Maintenance Releases – Typically encompasses software upgrades to the SAP software, operating system, database or significant bolt-on tools. Whenever possible, upgrade releases should not be combined with functional releases during cutover activities. Upgrade changes should be introduced prior to the start of Integration test. Introduction of upgrade releases requires full regression test, and must be carefully planned to minimize business impact and delays in deployment schedule.

Upgrade Releases - Require expansion of the traditional landscape to include following systems: 1) Full copy of production for test upgrades, Full up-to-date separate copy of Development system to be upgraded, and to apply fixes prior to Production upgrade, full Production copy Test system for regression testing prior to actual production upgrade.

Production Break/Fix – Encompasses pre-approved fixes to production-related problems


NetWeaver 2004s environment consists of Database and SAP runtime environment known as SAP Web Application Server; Depending on number of concurrent users and user load, SAP

environment allows the three-tier scalability

DatabaseServer

Web AS1

Web AS2

Web AS3

Web ASn

…

End Users

Three-tier Environment


Small SAP implementation project consists of three environments

Development Environment All configurations and custom developments are conducted in this environment This environment is the owner of configuration and custom development. Maintains version history of configuration and custom development Not refreshed from any other environments

Quality Assurance & Test Environment Configuration and custom development are integration tested in this environment End user training can be conducted in a separate training client

Production Environment Production environment consists of a single client


A very large SAP implementation project such as CATALYST, consists of more environments depending on business requirements

Sandbox Environment Used early in the project during the blue-print phase for a demonstration Used by technical team to test OS, Database, and SAP Patches without affecting other

environment and production support Used by business teams to test special proto-types without affecting development support Typically refreshed from other environments like Dev/QAT/Prod

Development Environment All configurations and custom developments are conducted here This is the owner of configuration and custom development. Maintains version history of configuration and custom development Not refreshed from other environments

Quality Assurance Environment Configuration and custom development are integration tested here Typically refreshed from Production environment to allow testing with production data

Regression Environment Production cut-over timing and load testing are conducted here Used as a stand by production environment for DR and also for volume/stress testing

Training Environment Multiple End user classroom training is conducted here Trained users can practice here in a practice client prior to go live

Production Fix Dev & QA Environments These environments provide development/test capabilities to troubleshoot production

problems; any changes made to the production fix dev system are manually repeated in Project Development landscape

Production Environment Production environment consists of a single client


When do I need each environment?

Sandbox environment Implemented at the beginning of blueprint phase to demonstrate, and use it as a

referenceDevelopment environment

Implemented prior to implementation phaseQuality Assurance Test environment

Prior to integration test for testing end to end business processes Typically 2~3 months after implementation starts and depends on project schedule

Training environment At least a couple of months prior to go-live in order to train end users

Regression environment At least a couple of months prior to go-live to complete data data-loads, load-test,

technical testing, etc.Production Fix (Dev & QA) environment

At least a couple of weeks prior to go-live to complete landscape setup and complete the cut-over transport methodology

Production environment At least a couple of months prior to go-live to complete installations, high availability

and other technical infrastructure validations.


Catalyst SAP System Naming Convention

A – NetWeaver Infra (eg.RFID) B – Business Warehouse/SEM E – ECC G – GTS L – LiveCache for SCM M – MDM

P – Portal R – SRM S – SCM/SolMan

W – Ware House Management X – XI

System Identifier ( e.g. EWD )

X – Sandbox D – Development

Q – Quality AssuranceR – Regression

T – TrainingF – Prod Fix Dev

S – Prod Fix Test

P – Production

Differentiates Regional vs. Global Systems

E: EastW: WestG: Global

Position 1 Position 2 Position 3


Phased Development Scenario

Development QualityAssurance

ProductionSupport

Prod-QualityAssurance

Production

Release N+1

Release NManual

re-entry of changes

Training

Regression

Project Development

On going support

Owner of Objects


Sandbox & Training

Pro

ject

S

uppo

rt

Production

ECC 6 EWF

SRM RGF

SCM SWF

XI XWF

EP PGF

ECC 6 EWS

SRM RGS

CRM CWS

SCM SWS

CRM CWF

XI BSS

EP PGS

Development Pre-Prod

ECC6 EWP

SRM KPE

CRM CWP

SCM SWP

XI XWP

EP PGP

Development Quality Assurance Regression Test

ECC 6 EWD

SRM RGD

SCM SWD

XI XWD

EP PGD

CRM CWD

ECC 6 EWQ

SRM RGQ

SCM SWQ

XI XWQ

EP PGQ

CRM CWQ

ECC 6 EWR

SRM RGR

SCM SWR

XI XWR

EP PGR

CRM CWR

ECC 6 EWX

SCM SWX

XI XWX

CRM CWX EP PGX

ECC 6 EWT

CRM CWT SCM SWT

XI XWT

EP PGT

MDM MGP

MDM MGX

Sol Man SMX

Global Trade GGF

Warehouse WWF

BI (Global) BGF

SEM BSF

Global Trade GGS

Warehouse WWS

BI (Global) BGS

BI (Local for West) BWS

SRM RGX

SRM RGT

Global Trade GGP

Warehouse WWP

BI (Global) BGP

BI (Local for West) BWP

Global Trade GGD

Warehouse WWD

BI (Global) BGD

BI (Local for West) BWD

Global Trade GGQ

Warehouse WWQ

BI (Global) BGQ

BI (Local for West) BWQ

Global Trade GGR

Warehouse WWR

BI (Global) BGR

BI (Local for West) BWR

Global Trade GGT

Global Trade GGX

Sol Man SMP

Sol

Man

SM

T

BI (Global) BGX

BI (Local for West) BWX

BI (Global) BGT

BI (Local for West) BWT

Warehouse WWX

Warehouse WWT

MDM MGF MDM MGS

MDM MGD MDM MGQ MDM MGR

SEM SWS

SEM BSP

SEM BSD SEM BSQ SEM BSR

SEM BSX

SEM BST

TREX TWP

xAPP ---

NWDI NDP

GSLD ---

TREX TWS

xAPP ---

TREX TWF

xAPP ---

TREX TWD

xAPP ---

TREX TWQ

xAPP ---

TREX TWR

xAPP ---

TREX TWX

xAPP ---

BI (Local for West) BWD

Warehouse WWT

TREX TWT

xAPP ---


Sandbox & Training

Pro

ject

S

uppo

rt Production

ECC 6 EWF

SRM RGF

SCM SWF

XI XWF

EP PGF

ECC 6 EWS

SRM RGS

CRM CWS

SCM SWS

CRM CWF

XI XWS

EP PGS

Development Quality Assurance Regression Test ECC 6 EWD

SRM RGD

SCM SWD

XI XWD

EP PGD

CRM CWD

ECC 6 EWQ

SRM RGQ

SCM SWQ

XI XWQ

EP PGQ

CRM CWQ

ECC 6 EWR

SRM RGR

SCM SWR

XI XWR

EP PGR

CRM CWR

ECC 6 EWX

SCM SWX

XI XWX

CRM CWX EP PGX

ECC 6 EWT

CRM CWT SCM SWT

XI XWT

EP PGT

MDM MGXSol Man

SMX

Global Trade GGF

Warehouse WWF

BW (Global) BGF

BW (Local for West) BWF

Global Trade GGS

Warehouse WWS

BW (Global) BGS

BW (Local for West) BWS

SRM RGX

SRM RGT

Global Trade GGD

Warehouse WWD

BW (Global) BGD

BW (Local for West) BWD

Global Trade GGQ

Warehouse WWQ

BW (Global) BGQ

BW (Local for West) BWQ

Global Trade GGR

Warehouse WWR

BW (Global) BGR

BW (Local for West) BWR

Global Trade GGT

Global Trade GGX

Sol

Man

SM

T

ECC6 EWP

SRM KPE

CRM CWP

SCM SWP

XI XWP

EP PGP

MDM MGP

Global Trade GGPF

Warehouse WWP

BW (Global) BGP

BW (Local for West) BWP

Sol Man SMP

BW (Global) BGX

BW (Local for West) BWX

BW (Global) BGT

BW (Local for West) BWT

Warehouse WWX

Warehouse WWT

ECC6•All changes in EWF to be manually replicated to EWD

•For Config Changes, Solution manager, table compare and table sync may be used•Replication Process doc to be created

•Transport path : EWD ->EWQ ->EWR then imported to as a Cut over TP package to EWF And transported to ->EWS ->EWP•The following systems are tightly coupled with this landscape and should be considered at the time of refresh

CRM, SRM, SCM, BI / BW, Warehouse, XI, Portal, SEM


MDM MGF MDM MGS



Sandbox & Training

Pro

ject

S

uppo

rt Production

ECC 6 EWF

SRM RGF

SCM SWF

XI XWF

EP PGF

ECC 6 EWS

SRM RGS

CRM CWS

SCM SWS

CRM CWF

XI XWS

EP PGS


SRM RGD

SCM SWD

XI XWD

EP PGD

CRM CWD

ECC 6 EWQ

SRM RGQ

SCM SWQ

XI XWQ

EP PGQ

CRM CWQ

ECC 6 EWR

SRM RGR

SCM SWR

XI XWR

EP PGR

CRM CWR

ECC 6 EWX

SCM SWX

XI XWX

CRM CWX EP PGX

ECC 6 EWT

CRM CWT SCM SWT

XI XWT

EP PGT

MDM MGXSol Man

SMX

Global Trade GGF

Warehouse WWF

BW (Global) BGF


Global Trade GGS

Warehouse WWS

BW (Global) BGS


SRM RGX

SRM RGT

Global Trade GGD

Warehouse WWD

BW (Global) BGD


Global Trade GGQ

Warehouse WWQ

BW (Global) BGQ


Global Trade GGR

Warehouse WWR

BW (Global) BGR


Global Trade GGT

Global Trade GGX

Sol

Man

SM

T

ECC6 EWP

SRM KPE

CRM CWP

SCM SWP

XI XWP

EP PGP

MDM MGP

Global Trade GGPF

Warehouse WWP

BW (Global) BGP


Sol Man SMP

BW (Global) BGX


BW (Global) BGT


Warehouse WWX

Warehouse WWT

CRM•CRM Infrastructure involves the deployment of Mobile applications for CRM Field Sales

•Project team will need to determine the deployment method for this CRM Sales infrastructure architecture •CRM instances are tightly coupled with the ECC and mobile infrastructure instances


MDM MGF MDM MGS



Sandbox & Training

Pro

ject

S

uppo

rt Production

ECC 6 EWF

SRM RGF

SCM SWF

XI XWF

EP PGF

ECC 6 EWS

SRM RGS

CRM CWS

SCM SWS

CRM CWF

XI XWS

EP PGS


SRM RGD

SCM SWD

XI XWD

EP PGD

CRM CWD

ECC 6 EWQ

SRM RGQ

SCM SWQ

XI XWQ

EP PGQ

CRM CWQ

ECC 6 EWR

SCM SWR

XI XWR

EP PGR

CRM CWR

ECC 6 EWX

SCM SWX

XI XWX

CRM CWX EP PGX

ECC 6 EWT

CRM CWT SCM SWT

XI XWT

EP PGT

MDM MGQ

MDM MGXSol Man

SMX

Global Trade GGF

Warehouse WWF

BW (Global) BGF


Global Trade GGS

Warehouse WWS

BW (Global) BGS


SRM RGX

SRM RGT

Global Trade GGD

Warehouse WWD

BW (Global) BGD


Global Trade GGQ

Warehouse WWQ

BW (Global) BGQ


Global Trade GGR

Warehouse WWR

BW (Global) BGR


Global Trade GGT

Global Trade GGX

Sol

Man

SM

T

ECC6 EWP

SRM KPE

CRM CWP

SCM SWP

XI XWP

EP PGP

MDM MGP

Global Trade GGPF

Warehouse WWP

BW (Global) BGP


Sol Man SMP

SRM RGR

BW (Global) BGX


BW (Global) BGT


Warehouse WWX

Warehouse WWT


MDM MGF MDM MGS


SRM There will be a single landscape of SRM for Eastern and Western Hemisphere regions

The following STAR systems will be renamed : Old SID New SIDKDJ RGFKTE RGQKTF KGS

•Production SID will remain KPE to mitigate any risks associated with changing the SID of a production system (Interfaces etc) •Strong Change Management and project co-ordination between the hemispheres will be required•Meeting to discuss client strategy of SRM is required•This Landscape Links into : Catalog management systems – Decision will be taken on either MDM or CCM


Sandbox & Training

Pro

ject

S

uppo

rt Production

ECC 6 EWF

SRM RGF

SCM SWF

XI XWF

EP PGF

ECC 6 EWS

SRM RGS

CRM CWS

SCM SWS

CRM CWF

XI XWS

EP PGS


SRM RGD

SCM SWD

XI XWD

EP PGD

CRM CWD

ECC 6 EWQ

SRM RGQ

SCM SWQ

XI XWQ

EP PGQ

CRM CWQ

ECC 6 EWR

SRM RGR

SCM SWR

XI XWR

EP PGR

CRM CWR

ECC 6 EWX

SCM SWX

XI XWX

CRM CWX EP PGX

ECC 6 EWT

CRM CWT SCM SWT

XI XWT

EP PGT

MDM MGQ

MDM MGXSol Man

SMX

Global Trade GGF

Warehouse WWF

BW (Global) BGF


Global Trade GGS

Warehouse WWS

BW (Global) BGS


SRM RGX

SRM RGT

Global Trade GGD

Warehouse WWD

BW (Global) BGD


Global Trade GGQ

Warehouse WWQ

BW (Global) BGQ


Global Trade GGR

Warehouse WWR

BW (Global) BGR


Global Trade GGT

Global Trade GGX

Sol

Man

SM

T

ECC6 EWP

SRM KPE

CRM CWP

SCM SWP

XI XWP

EP PGP

MDM MGP

Global Trade GGPF

Warehouse WWP

BW (Global) BGP


Sol Man SMP

BW (Global) BGX


BW (Global) BGT


Warehouse WWX

Warehouse WWT


MDM MGF MDM MGS


SCM

•External systems like Manugistics instances will interact directly with SCM.•SCM in turn will manage the relationships to Live Cache, ECC and BI systems

•Each SCM system will have an instance each of Live Cache and Optimiser •SCM will be linked to the ECC6 systems via CIF•Each SCM repository has a dedicated Live cache repository•Synchronization between live cache and the SCM repository has to be controlled via change management processes•‘Optimiser’ will be on Wintel platform infrastructure. SCM and Live Cache will be based on SUN Platforms. •Assumption : Global ATP will be the principal reason that SCM / APO is used. All other Supply chain planning eg. Production forecasting and Planning will occur in Manugistics and the output will be imported into the Catalyst suite of SAP systems


Sandbox & Training

Pro

ject

S

uppo

rt Production

ECC 6 EWF

SRM RGF

SCM SWF

XI XWF

EP PGF

ECC 6 EWS

SRM RGS

CRM CWS

SCM SWS

CRM CWF

XI XWS

EP PGS


SRM RGD

SCM SWD

XI XWD

EP PGD

CRM CWD

ECC 6 EWQ

SRM RGQ

SCM SWQ

XI XWQ

EP PGQ

CRM CWQ

ECC 6 EWR

SRM RGR

SCM SWR

XI XWR

EP PGR

CRM CWR

ECC 6 EWX

SCM SWX

XI XWX

CRM CWX EP PGX

ECC 6 EWT

CRM CWT SCM SWT

XI XWT

EP PGT

MDM MGQ

MDM MGXSol Man

SMX

Global Trade GGF

Warehouse WWF

BW (Global) BGF


Global Trade GGS

Warehouse WWS

BW (Global) BGS


SRM RGX

SRM RGT

Global Trade GGD

Warehouse WWD

BW (Global) BGD


Global Trade GGQ

Warehouse WWQ

BW (Global) BGQ


Global Trade GGR

Warehouse WWR

BW (Global) BGR


Global Trade GGT

Global Trade GGX

Sol

Man

SM

T

ECC6 EWP

SRM KPE

CRM CWP

SCM SWP

XI XWP

EP PGP

MDM MGP

Global Trade GGPF

Warehouse WWP

BW (Global) BGP


Sol Man SMP

BW (Global) BGX


BW (Global) BGT


Warehouse WWX

Warehouse WWT

XI / Process Integration (PI)

•Developments will be a combination of ABAP and Java Services•All systems will have a single client (010) •Any homogeneous SAP middleware traffic in the SAP ecosystem will be managed by XI•Other systems that will also be used for middleware traffic : ItemField, SeeBeyond (Jcaps) , and Datastage.


MDM MGF MDM MGS



Sandbox & Training

Pro

ject

S

uppo

rt Production

ECC 6 EWF

SRM RGF

SCM SWF

XI XWF

EP PGF

ECC 6 EWS

SRM RGS

CRM CWS

SCM SWS

CRM CWF

XI XWS

EP PGS


SRM RGD

SCM SWD

XI XWD

EP PGD

CRM CWD

ECC 6 EWQ

SRM RGQ

SCM SWQ

XI XWQ

EP PGQ

CRM CWQ

ECC 6 EWR

SRM RGR

SCM SWR

XI XWR

EP PGR

CRM CWR

ECC 6 EWX

SCM SWX

XI XWX

CRM CWX EP PGX

ECC 6 EWT

CRM CWT SCM SWT

XI XWT

EP PGT

MDM MGQ

MDM MGXSol Man

SMX

Global Trade GGF

Warehouse WWF

BW (Global) BGF


Global Trade GGS

Warehouse WWS

BW (Global) BGS


SRM RGX

SRM RGT

Global Trade GGD

Warehouse WWD

BW (Global) BGD


Global Trade GGQ

Warehouse WWQ

BW (Global) BGQ


Global Trade GGR

Warehouse WWR

BW (Global) BGR


Global Trade GGT

Global Trade GGX

Sol

Man

SM

T

ECC6 EWP

SRM KPE

CRM CWP

SCM SWP

XI XWP

EP PGP

MDM MGP

Global Trade GGPF

Warehouse WWP

BW (Global) BGP


Sol Man SMP

BW (Global) BGX


BW (Global) BGT


Warehouse WWX

Warehouse WWT


MDM MGF MDM MGS


Enterprise Portal

•Portal is a required component in this landscape as SAPs roadmap suggests a continued and increased focus in this area to deliver new functionality.•All developments on this system are in Java •There will be a Federated Consumer producer Relationship between EP and other SAP systems (ECC, BI, CRM, SCM, SEM and SRM)

•Every backend system has a portal installed (producer portal) •Business packages need to be loaded into the Producer portal

•Active directory will be used for the user persistence store in the User Management Engine (UME) •Discussions with the project team required to determine the full requirements for ‘internal’ and ‘external’ portals •Project to determine if Knowledge management is part of the Portal deployment

•If Yes, additional components such as TREX and Document Management will be closely integrated. •(Consumer)Portal systems need to be on a HA platform as they are intended to be the gateway to the SAP domain.


Sandbox & Training

Pro

ject

S

uppo

rt Production

ECC 6 EWF

SRM RGF

SCM SWF

XI XWF

EP PGF

ECC 6 EWS

SRM RGS

CRM CWS

SCM SWS

CRM CWF

XI XWS

EP PGS


SRM RGD

SCM SWD

XI XWD

EP PGD

CRM CWD

ECC 6 EWQ

SRM RGQ

SCM SWQ

XI XWQ

EP PGQ

CRM CWQ

ECC 6 EWR

SRM RGR

SCM SWR

XI XWR

EP PGR

CRM CWR

ECC 6 EWX

SCM SWX

XI XWX

CRM CWX EP PGX

ECC 6 EWT

CRM CWT SCM SWT

XI XWT

EP PGT

MDM MGXSol Man

SMX

Global Trade GGF

Warehouse WWF

BW (Global) BGF


Global Trade GGS

Warehouse WWS

BW (Global) BGS


SRM RGX

SRM RGT

Global Trade GGD

Warehouse WWD

BW (Global) BGD


Global Trade GGQ

Warehouse WWQ

BW (Global) BGQ


Global Trade GGR

Warehouse WWR

BW (Global) BGR


Global Trade GGT

Global Trade GGX

Sol

Man

SM

T

ECC6 EWP

SRM KPE

CRM CWP

SCM SWP

XI XWP

EP PGP

MDM MGP

Global Trade GGPF

Warehouse WWP

BW (Global) BGP


Sol Man SMP

BW (Global) BGX


BW (Global) BGT


Warehouse WWX

Warehouse WWT


MDM MGF MDM MGS


Rep

osito

ry

Rep

osito

ry

Rep

osito

ry

Rep

osito

ry

Rep

osito

ry

MDM

•Originally considered: Single Instance for the Support systems with multiple repositories (MGF)•Originally considered: Single instance for the Project stream with Multiple repositories (MGQ)•Production instance will be global and feed all SAP Instances in the Eastern and Western Hemispheres•A producer portal will exist for each instance (assumption to be validated)


Sandbox & Training

Pro

ject

S

uppo

rt Production

ECC 6 EWF

SRM RGF

SCM SWF

XI XWF

EP PGF

ECC 6 EWS

SRM RGS

CRM CWS

SCM SWS

CRM CWF

XI XWS

EP PGS


SRM RGD

SCM SWD

XI XWD

EP PGD

CRM CWD

ECC 6 EWQ

SRM RGQ

SCM SWQ

XI XWQ

EP PGQ

CRM CWQ

ECC 6 EWR

SRM RGR

SCM SWR

XI XWR

EP PGR

CRM CWR

ECC 6 EWX

SCM SWX

XI XWX

CRM CWX EP PGX

ECC 6 EWT

CRM CWT SCM SWT

XI XWT

EP PGT

MDM MGQ

MDM MGXSol Man

SMX

Global Trade GGF

Warehouse WWF

BW (Global) BGF


Global Trade GGS

Warehouse WWS

BW (Global) BGS


SRM RGX

SRM RGT

Global Trade GGD

Warehouse WWD

BW (Global) BGD


Global Trade GGQ

Warehouse WWQ

BW (Global) BGQ


Global Trade GGR

Warehouse WWR

BW (Global) BGR


Global Trade GGT

Global Trade GGX

Sol

Man

SM

T

ECC6 EWP

SRM KPE

CRM CWP

SCM SWP

XI XWP

EP PGP

MDM MGP

Global Trade GGPF

Warehouse WWP

BW (Global) BGP


Sol Man SMP

BW (Global) BGX


BW (Global) BGT


Warehouse WWX

Warehouse WWT


MDM MGF MDM MGS


Business Warehouse (Global and Western Hemisphere)

•BW Systems are closely linked to ECC instances and will closely follow processes and procedures linked to transports, change management and testing.•Transport management methodology is specific to BW (Process document to be prepared ) •BW systems require Portal infrastructure •Additional technology will be used in conjunction with BW :

•Pre-Calc & Business Explore Analyzer (Desktop Deployment) •BIA (BI Accelerator)

•External data sources will be linked to BW systems •Additional data analytical tools like Crystal reports has not been planned as part of this landscape


Sandbox & Training

Pro

ject

S

uppo

rt Production

ECC 6 EWF

SRM RGF

SCM SWF

XI XWF

EP PGF

ECC 6 EWS

SRM RGS

CRM CWS

SCM SWS

CRM CWF

XI XWS

EP PGS


SRM RGD

SCM SWD

XI XWD

EP PGD

CRM CWD

ECC 6 EWQ

SRM RGQ

SCM SWQ

XI XWQ

EP PGQ

CRM CWQ

ECC 6 EWR

SRM RGR

SCM SWR

XI XWR

EP PGR

CRM CWR

ECC 6 EWX

SCM SWX

XI XWX

CRM CWX EP PGX

ECC 6 EWT

CRM CWT SCM SWT

XI XWT

EP PGT

MDM MGQ

MDM MGXSol Man

SMX

Global Trade GGF

Warehouse WWF

BW (Global) BGF


Global Trade GGS

Warehouse WWS

BW (Global) BGS


SRM RGX

SRM RGT

Global Trade GGD

Warehouse WWD

BW (Global) BGD


Global Trade GGQ

Warehouse WWQ

BW (Global) BGQ


Global Trade GGR

Warehouse WWR

BW (Global) BGR


Global Trade GGT

Global Trade GGX

Sol

Man

SM

T

ECC6 EWP

SRM KPE

CRM CWP

SCM SWP

XI XWP

EP PGP

MDM MGP

Global Trade GGPF

Warehouse WWP

BW (Global) BGP


Sol Man SMP

BW (Global) BGX


BW (Global) BGT


Warehouse WWX

Warehouse WWT

Warehouse WWX


MDM MGF MDM MGS


Global Trade Services

•Tightly coupled with the ECC instances•Additional Security, Firewall restrictions will need to be considered as data in the application will have external access •The instances will be based on the standard : ABAP + J2EE architecture •Assumption to be validated : GTS will be a system with Global usage & there will not be any regional GTS instances for the Eastern and Western hemispheres.


Sandbox & Training

Pro

ject

S

uppo

rt Production

ECC 6 EWF

SRM RGF

SCM SWF

XI XWF

EP PGF

ECC 6 EWS

SRM RGS

CRM CWS

SCM SWS

CRM CWF

XI XWS

EP PGS


SRM RGD

SCM SWD

XI XWD

EP PGD

CRM CWD

ECC 6 EWQ

SRM RGQ

SCM SWQ

XI XWQ

EP PGQ

CRM CWQ

ECC 6 EWR

SRM RGR

SCM SWR

XI XWR

EP PGR

CRM CWR

ECC 6 EWX

SCM SWX

XI XWX

CRM CWX EP PGX

ECC 6 EWT

CRM CWT SCM SWT

XI XWT

EP PGT

MDM MGQ

MDM MGXSol Man

SMX

Global Trade GGF

Warehouse WWF

BW (Global) BGF


Global Trade GGS

Warehouse WWS

BW (Global) BGS


SRM RGX

SRM RGT

Global Trade GGD

Warehouse WWD

BW (Global) BGD


Global Trade GGQ

Warehouse WWQ

BW (Global) BGQ


Global Trade GGR

Warehouse WWR

BW (Global) BGR


Global Trade GGT

Global Trade GGX

Sol

Man

SM

T

ECC6 EWP

SRM KPE

CRM CWP

SCM SWP

XI XWP

EP PGP

MDM MGP

Global Trade GGPF

Warehouse WWP

BW (Global) BGP


Sol Man SMP

BW (Global) BGX


BW (Global) BGT


Warehouse WWX

Warehouse WWT

SAP Warehouse Management

•The Warehouse management systems are closely linked to ECC instances and will closely follow processes and procedures linked to transports, change management and testing.•Availability of the Production system is critical to business operations and hence a High Availability Solution is mandatory.


MDM MGF MDM MGS



Sandbox & Training

Pro

ject

S

uppo

rt Production

ECC 6 EWF

SRM RGF

SCM SWF

XI XWF

EP PGF

ECC 6 EWS

SRM RGS

CRM CWS

SCM SWS

CRM CWF

XI XWS

EP PGS


SRM RGD

SCM SWD

XI XWD

EP PGD

CRM CWD

ECC 6 EWQ

SRM RGQ

SCM SWQ

XI XWQ

EP PGQ

CRM CWQ

ECC 6 EWR

SRM RGR

SCM SWR

XI XWR

EP PGR

CRM CWR

ECC 6 EWX

SCM SWX

XI XWX

CRM CWX EP PGX

ECC 6 EWT

CRM CWT SCM SWT

XI XWT

EP PGT

MDM MGQ

MDM MGXSol Man

SMX

Global Trade GGF

Warehouse WWF

BW (Global) BGF


Global Trade GGS

Warehouse WWS

BW (Global) BGS


SRM RGX

SRM RGT

Global Trade GGD

Warehouse WWD

BW (Global) BGD


Global Trade GGQ

Warehouse WWQ

BW (Global) BGQ


Global Trade GGR

Warehouse WWR

BW (Global) BGR


Global Trade GGT

Global Trade GGX

Sol

Man

SM

T

ECC6 EWP

SRM KPE

CRM CWP

SCM SWP

XI XWP

EP PGP

MDM MGP

Global Trade GGPF

Warehouse WWP

BW (Global) BGP


Sol Man SMP

BW (Global) BGX


BW (Global) BGT


Warehouse WWX

Warehouse WWT

Solution Manager

•Solution manager sandbox (SMX) will be used for testing new releases, and other sandbox related prototyping etc•Solution manager pre-production (SMT) will be used for security testing, initial input of project template creation and testing. •Solution manager Production (SMP) is the live system used for concurrent and live activity. •There will be no transports of application related information between SMT and SMP. All functional and Business related changes will be made directly in SMP.


MDM MGF MDM MGS



GLOBAL/WEST SAP SYSTEM LANDSCAPE

ECC EWF ECC EWS ECC EWPECC EWR

CRM CWF CRM CWS

SRM RGF SRM RGS

SCM SWF SCM SWS

LIVECACHE LWF LIVE

CACHE LWS

XI/PI XWF XI/PI XWS

TREX TWF TREX TWS

EP PGF EP PGS

MOBILEINFRASTRUCTURE


OPTIMIZER OPS

CRM CWP

SRM KPE

SCM SWP

LIVECACHE LWP

OPTIMIZER OPP

XI/PI XWP

TREX TWP

EP PGP


SOLUTION MGR SMP

BI BWF BI BWS BI BWP

BW-GLOBAL BGF BW-GLOBAL BGS BW-GLOBAL BGP

MDM MGF MDM MGS MDM MGP

ECC-WM WWF ECC-WM WWS ECC-WM WWP

ECC EWD ECC EWQ

CRM CWD CRM CWQ

SRM RGD SRM RGQ

SCM SWD SCM SWQ

LIVECACHE LWD LIVE

CACHE LWQ

XI/PI XGD XI/PI XGQ

TREX TWD TREX TWQ

EP PGD EP PGQ



OPTIMIZER OPQ

SOLUTION MGR SMT

BI BWD BI BWQ

BW-GLOBAL BGD BW-GLOBAL BGQ

MDM MGD MDM MGQ

ECC-WM WWD ECC-WM WWQ

CRM CWR

SRM RGR

SCM SWR

LIVECACHE LWR

ECC-WM WWR

XI/PI XWR

TREX TWR

EP PGR


BI BWR

BW-GLOBAL BGR

MDM MGR

PROJECT RELEASE LANDSCAPE PRODUCTION SUPPORT LANDSCAPE PRODUCTION

SANDBOX | PROTOTYPE

ECC-GTS GGT CRM CWTSRM RGT

SCM SWT LIVECACHE LWTECC-WM WWT

XI/PI XWT

TREX TWTEP PGT


FRONT END COMPONENTS -TECHNICAL

BW BWT

BW-GLOBAL BGT

------ --T

OPTIMIZER OPT MDM MGX SOLUTION MGR SMX

ECC EWX

CRM CWXSRM RGX

SCM SWXLIVECACHE LWX

ECC-GTS GGX

XI/PI XGX

TREX TWXEP PGX


FRONT END COMPONENTS -TECHNICAL

BW BWX

BW-GLOBAL BGX

----- --X

TRAINING

NWDI DGD

DEVELOPMENT PRE-PRODUCTIONDEVELOPMENT QUALITY ASSURANCE REGRESSION TEST

ECC-GTS GGF ECC-GTS GGS ECC-GTS GGPECC-GTS GGD ECC-GTS GGQ ECC-GTS GGR

WebAS-XAPP PWF WebAS-XAPP PWS WebAS-XAPP PWPWebAS-XAPP(PLM) PWD WebAS-XAPP

(PLM) PWQ WebAS-XAPP PWR

ECC EWT

ECC-WM WWX

WebAS-XAPP(PLM) PWT

WebAS-XAPP(PLM) PWX

SEM BSD SEM BSQ SEM BSR SEM BSF SEM BSS SEM BSP

SEM BSX

SEM BST

GO

LIVE

AGD AGQ AWR AWF AWS AWP

AGX

AGT

NWDI DGP

GlobalSystLandDir GSLD

CUTOVER

RELEASE


What is our client strategy for dev

• A client is a container for segmenting data within the ECC application itself. It is a self-contained unit of separate master records and with its own sets of data. • A user or developer can log in to a specific client, which is a totally separate data environment. • Theory: Keep it simple – there is only one client in PROD so keep everyone working in the same environment as much as possible.


Clients in DEV Environment

Prototype Configuration client will be used by the business process team for initial configuration work. It will contain some master data to allow configuration prototype development. On request this client may get refreshed via client copy of Unit Test client. Work done in this client will not be recorded and must be entered in the Configuration client manually. Client independent work will not be allowed in this client.

Golden client for business process teams to enter master “Gold” configuration manually after it has been entered and tested in Prototype Configuration Client. It will contain some master data to allow configuration work but entered configuration will not be tested in this client. All changes will be recorded and all customization transports will originate from this client.

Unit Test client for unit testing of configuration entered in the Configuration client. For unit testing, desired configuration request will be copied from Configuration client into this client via SCC1 without releasing the configuration request. No changes will be allowed in this client.

Development client for ABAP development work. Developed objects in this client will be cross-client and will be available to all clients. All development changes will be recorded and all workbench transports will originate from this client.

Security client for Security Authorization development without effecting other development clients


Development

90 Prototype Configuration

mySAP Development System

Business Process Teams perform initial configuration work in Prototype Configuration client. To allow testing of the configuration, this client contains required master data thus allowing Business Process Teams to fine tune configuration. However, work done in this client is not recorded by the system.

800 Security


<ProtoType client 090> – Validation

• This client is for exercising / sandboxing configuration solutions.All config setup has to be prototyped in this client Configuration activities for this environment are not done thru Solution Manager.•SPRO is not accessible from this client. In order to do the configuration you must go to the TCode directly.• No changes will be recorded in this system. Therefore, no transports will be generated from this environment.• This environment will be refreshed periodically from 100 (The Unit Test Client) to keep the information current. (tbd:frequency)• New team members coming on board to Catalyst should be given at a minimum display access to this environment first.


<Seucrity Client 800> – Security

• This client is for prototyping security roles that would be done in ECC only. • Security team will be the only ones with access to this environment.• No changes to configuration activities are allowed in this environment at all.• Only transports associated with security are done from this environment. (TBD by Security team)


Development

010 Golden



Since the work performed in the Prototype Configuration client is not recorded by the system, the business process teams keep record of their work to enter the final configuration in Golden client manually.

800 Security


<Golden Client 010> – Configuration Only

• Configuration Only. All customizing configuration is done here.• No transaction data is done in this client – you will not be entering a sales order, journal entries, etc.• Very limited master data will be done in this client – you will not be entering products, customers etc. Only master data allowed will be that required to perform configuration activities.• Will often be referenced as the Golden Client.• All activity done here is anticipated to move to QA, Regression and eventually PROD environment (‘F’, ‘S’, ‘P’).•Access to this is restricted to team members who have been approved to do customizing (configuration).• Configuration activities will be done via Solution Manager.


<010> – Configuration Only

• All activity will be recorded against a change request or transport request•Data will be moved to the other dev clients via the SCC1 transaction


Development

010 Golden



Work performed in the Golden client is recorded automatically and entered configuration is captured in Configuration Transport Requests. This client contains required master data to allow configuration work only. Testing of the entered configuration is not done in this client in order to keep the configuration pure.

800 Security


Development

100 Unit Test

010 Golden



To test configuration entered in the Golden client, the Business Process Teams copy their configuration captured in the Configuration Transport Requests into Unit Test client. Here they unit test their configuration and if needed, adjust their configuration in the Golden client and copy it back into unit test client.

Why Separate clients for Configuration and Unit Test? Keeps Configuration Client “pure”

No transactional data corruptions

Guarantees integrity of the configuration transports

Unit Test Client contains enough master data to allow testing

800 Security


<Unit Test Client 100> – Unit Test

• This client is for unit testing Configuration and Workbench developed solutions. All team members can access.• No changes to configuration activities are allowed in this environment at all.• This environment is the recipient of configuration data from <Golden (010) Client>.• No changes will be recorded in this system. Therefore, no transports will be generated from this environment.• Standard / Minimal master data required to support this activity needs to be scripted via ALE or LMSW to support reloading of basic master data elements – such as customer, product, vendor.• This is the only client ‘HUB’ that is linked to the new dimension products. Any activities that span multiple components needs to be done here.


Development

100 Unit Test

010 Golden



Unit tested and approved Configuration Transport Requests are copied into Development client. Development Team develops custom ABAP programs using the copied configuration and tests development work in the Development Client. All development work is recorded and is captured in Workbench Transport Requests. Note that ABAP development is client independent hence any changes become immediately available to all clients in the Development system. (TBD: SCC1 access?!)

110 Development

Why Separate clients for Configuration and Development? Configuration work

Can easily be grouped and entered from start to finish

Does not require frequent testing in between while entering it

Tested after all work is complete

Development work

X Is iterative and can not be grouped and entered from start to finish

X Requires frequent testing during development 800

Security


<ABAP Client 110> – Development

• This client is for developing Workbench (ABAP) solutions. • Service delivery team will be the only ones with access to this environment.• No changes to configuration activities are allowed in this environment at all.• This environment is the recipient of configuration data from Dev Client.• Although activity here is client independent, the expectation is that testing will be done in the Unit test environment• All development activity will be saved to transports to promote migration to QA, Regression and PROD.• Standard / Minimal master data required to support this activity needs to be scripted via ALE or LMSW to support reloading of basic master data elements – such as customer, product, vendor.


Development

100 Unit Test

010 Golden

110 Development



Over time the Prototype client becomes unusable. On request and with coordination with all business process teams it is refreshed from the Unit Test client via Client Copy. Also Special Temporary client for Data Conversion Unit Tests will be created via Client Copy from Unit Test Client.

800 Security

120 DataConv Unit Test


Additional Clients<DataLoad1 Client 120> – Data Conversion

• This client is for validating the load method for data conversion activities into ECC. • Data Quality individuals will be the only ones with access to this environment.• No changes to configuration activities are allowed in this environment at all.• This environment is the recipient of configuration data from Development Client.


Client Refresh /

Copy(if required)

Config Master Client015

Gold Customizing Client010

Unit Test100

Additional Clients- SAP ECC Development Client Strategy—EWD

EWD

Prototyping Client090

Notes:

• Client 015 is the configuration master. No data will be stored in this client.

• All development activities will be performed in client 110.

• All customizing/ configuration will be performed in client 010.

• The prototyping client will be used to test client-dependent changes only.

Development110

Security Client800

Data Conversion Unit Test120


Catalyst System/Client Usage ECC Landscape – Sandbox & Development

System System Use Client Static or Dynamic Usage *

Client Description /Functional Use

Client Refreshed from?

Comments

EWD ECC Development

100 S Unit Test N/A

010 S Gold Master N/A Transports originate from this client

090 S Sandbox Client 010 No transport tracking. Periodically refreshed (on demand/schedule) from 010.

800 S Security User Master

N/A Security construction client

110 S Development N/A Created from client 010

120 D Data Conversion Unit Test

100 Refreshed on request from Data Mgmt Team

EWX ECC Sandbox 300 S Sandbox environment

EWD/010 Refreshed on demand from EWD

* Static use = functional use of client is consistent, Dynamic = functional use may change


Development

100 Unit Test

010 Golden

110 Development



Business Process Teams release their completedcompleted configuration by releasing corresponding Configuration Transport Requests.

Similarly the Development Team releases its completedcompleted work by releasing corresponding Workbench Transport Requests.

Released transport requests become ready for import into Quality Assurance Testing System.

800 Security

120 Data Conversion Unit


<**delete**> SAP R/3 Development Client Strategy—EWD

Client Client Name Purpose Description

015 Configuration Master

Serves as configuration backup for client 010 Maintained through transports released from client 010 No data will exist in this client No transports will be generated from this client.

This will serve as a read-only copy of configuration in client 010. This client will be used to recover quickly from corruption errors that might otherwise require a database restore. Only the Basis team will have access to this client.

110 Development / Unit Test

All ABAP development will be performed in this client Open for repository changes All unit testing will be performed in this client Master data and transaction data will be loaded to facilitate testing All changes are recorded

All ABAP transports are generated out of this client. All interfaces which require programming effort will be developed in this client. Any custom table creation and other repository changes are performed in this client.

010 Customizing / Configuration

• All configuration will be entered into this client• Cross-client customizing allowed • No ABAP development allowed• No testing• Master data required for configuration will be loaded• All changes are recorded

All configuration transports are generated out of this client. Testing occurs in client 100. After the successful implementation of a development / customizing phase, the customizing information is propagated to other clients via configuration transport.

090 Prototyping Used for client-dependent changes only No transports will be generated from this client. Master data, transaction data will exist in this client No changes will be recorded

This is where client-dependent changes can be tested. After prototyping has been completed, the configuration will be manually entered into client 010.


Clients in EWQ Environment

Golden client will be initially created via client copy of EWQ client 000 and then importing unit tested, approved, and released configuration transport requests and workbench transport requests from the Development environment. This client will hold pure configuration data without any master data and will be used to build other clients in the EWQ system on request bases.

Integration Test client will be initially created via client copy of EWQ client 000 and then importing unit tested, approved, and released configuration from the Development environment. Required master data will be loaded here to allow integration testing.

Process Step/Process client will be created via client copy of Golden client and then loading required master data. It will be used for special testing purposes like data load, conversion, etc.

Data conversion Dry Run Test client will be created via client copy of Golden client and then loading required master data. It will be used for dry run of conversion processesc.

No changes will be allowed in any Quality Assurance Testing clients


Development

100 Unit Test

010 Golden

110 Development


Quality Assurance Test

100 Integration Test

010 Golden

mySAP Quality Assurance and Test System

Released Configuration Transport Requests are imported both into Golden and Integration Test clients of the Quality Assurance Test system.

Since the Workbench Transport Requests are client independent, they are imported into Golden client only.

Why Golden Client in Quality Assurance Test? Can be used to refresh Integration Test Client

Can be used to create other clients

Does not require transports from the development to refresh or to create new clients

800 Security

110 Process Test

120 DataConv DryRun Test



Development

100 Unit Test

010 Golden

110 Development




010 Golden


Rigorous integration testing takes place in the Integration Client. Any failures detected during the integration testing are fixed in the Golden Client of the Development system and the fixes are transported into the Quality Assurance system.

800 Security

110 Process Test




Development

100 Unit Test

010 Golden

110 Development




010 Golden


Any failures found during the integration testing are corrected in appropriate clients in the Development System, unit tested there and then transported again to the Quality Assurance System

800 Security

110 Process Test




Development

100 Unit Test

010 Golden

110 Development




010 Golden


For special testing needs like conversion testing, timing runs, etc. Special Test (Process Step/Process Testing; Data Conversion Dry Run Test) client is created in the Quality Assurance system via client copy of the Golden Client and then loading required master data.

800 Security

110 Process Test




Development

100 Unit Test

010 Golden

110 Development




010 Golden


Successfully integration tested Configuration Transport Requests and Workbench Transport Requests are approved for import into Training and Regression System.

800 Security

110 Process Test




Development

100 Unit Test

010 Golden

110 Development




010Golden

Training

010 Training Master

mySAP Training System

Approved Configuration Transport Requests and Workbench Transport Requests are imported into Training Master client of the Training System.

Trainers use this client to enter necessary data for class use and develop training material.

800 Security

110 Process Test




Clients in Training Environment

Training Master client will be initially created via client copy of EWT client 000 and then importing integration tested and approved configuration and workbench transport requests. It will be used by trainers to refresh various Class Room clients.

Class Room clients will be created via client copy of the Training Master Client and it will be used to train end users

No changes will be allowed in any Training clients


Development

100 Unit Test

010 Golden

110 Development




010 Golden

Training

710 Class Room 1

010 Training Master

720 Class Room 2

7n0 Class Room n

:

mySAP Training System

For end user training, demonstrations, walkthroughs, etc. various Class Room clients are created via client copy of the Training Master client.

800 Security

110 Process Test


110 Development


Catalyst System/Client Usage ECC Landscape – Training System (EWT)

System System Use

Client Static or Dynamic Usage *


Client Refresh from?

Comments

EWT ECC Training

010 S Training Client Master 015 Receives transports from EWD/010 on weekly basis. All master & transactional data for training purposes loaded into this client.

015 S Training Client Master – Backup Client

N/A Receives transports from EWD/010 on weekly basis.

710 D End User Training Client #1 010 Refreshed weekly after transports.




750 D End User Training Client #5 010 Refreshed weekly after transports

300 D End User Sandbox Area N/A Sandbox area after formal training. Receives transports from RD1/200



Development

100 Unit Test

010 Golden

110 Development




010Golden

Training

010 Training Master

mySAP Regression System

Approved Configuration Transport Requests and Workbench Transport Requests are imported into Regression client based on Regression Testing requirements.

800 Security

Regression

010 Regression

110 Process Test




Catalyst System/Client Usage ECC Landscape – QA, Regression & Production Systems



Client Refreshed from?

Comments

EWQ ECC QA/ Test 010 S Gold Client N/A Receives all transports from EWD 010

100 S Integration Test Client

N/A

110 D Process Step 010 Refreshed on request from Data Mgmt Team

120 D Data Conversion Dry Run Test

010 Refreshed on request from Data Mgmt Team

EWR(V) Regression Test 010 S Cutover Rehearsals; Infrastructure Test

010 Stress/Volume Test Client

EWP Production 010 S Production Client N/A Receives all transports from EWD 010



Clients in Production Environment

Production Fix Dev consists of clients 010 (Golden), 200 (Unit test), 210 (Development) and 230 (Security).

Production Fix QA consists of clients 010 and 200 (Integration test)

Production client will be created from a client copy of EWP client 000 and then importing integration tested and approved configuration and workbench transport requests. This will be the production client.

No changes will be allowed in Production client

Quality Assurance TestProduction

010 Production

Development

200 Unit Test

010 Golden

210 Development


010 Golden

230 Security



Development

100 Unit Test

010 Golden

110 Development




010 Golden

Training

710 Class Room 1

010 Training Master

7n0 Class Room n

:

Production

010 Production

mySAP Production System

Integration tested and approved Configuration Transport Requests and Workbench Transport Requests are also be imported into Production client of the Production System.

720 Class Room 2

Development

200 Unit Test

010 Golden

210 Development


010 Golden

800 Security

230 Security

Regression

010 Regression

110 Process Test




Other Non ECC system Clients

• The remaining mySAP components will be installed as single client systems. These include XI, BW, CRM, and SCM. • All customizing (dependent and client independent) plus development will be done here. • Configuration access should be limited to the select team members from the individual streams responsible for the component.• Configuration for these systems will be linked to Solution Manager. • All systems will have a change control mechanism to migrate code from one environment to the next, be it a transport or other means.


Development

010 Golden


010Golden

Regression

010Regression

Production

010Production

Transports

Next Wave Client Strategy for NetWeaver BI

BWD BWRBWQ

BWP

Development

010 Golden


010Golden

BWF BWS

Training

010Training Master

BWT


SCM

SWD

SWQ

SWX

SWR

SWTLogical System SWTCL700

Logical System SWRCL010

Logical System SWXCL300

Logical System SWQCL010

EWD

ECC

Development

QA/Test

User Training

Technical Sandbox

Regression

BI

EWQ

EWT

EWX

EWR

BWD

BWQ

BWX

BWR

BWT

Logical System EWDCL100

Logical System EWQCL100

Logical System EWTCL700

Logical System EWRCL010

Logical System EWXCL300

Logical System BWDCL010

Logical System BWQCL010

Logical System BWTCL700

Logical System BWRCL010

Logical System BWXCL300

Logical System Name (LSN) strategy:A logical system naming strategy is extremely important as it additionally has Impacts on the system copies and the work to complete

this.Logical system re-naming of OLTP system data can be very time consumingNaming and assigning logical system: Using unique logical system names across systems in the same landscape and unique

logical system names within each system type (DEV, QA, TRN).

ALE / RFC

Logical System SWDCL010

CWD

CWQ

CWX

CWR

CWTLogical System CWTCL700

Logical System CWRCL010

Logical System CWXCL300

Logical System CWQCL010

Logical System CWDCL010

CRM


Development

010 Golden


010Golden

Regression

010Regression

Production

010Production

Transports

Next Wave Client Strategy for NetWeaver CRM

CWD CWRCWQ

CWP

Development

010 Golden


010Golden

CWF CWS

Training

010Training Master

CWT


Development

010 Golden


010Golden

Regression

010Regression

Production

010Production

Transports

Next Wave Client Strategy for NetWeaver SCM

SWD SWRSWQ

SWP

Development

010 Golden


010Golden

SWF SWS

Training

010Training Master

SWT


Catalyst System/Client Usage Non-ECC Systems




Comments

SWX SCM Sandbox 300 S Sandbox N/A

SWD SCM Development 010 S Development Client N/A SWQ SCM QA/Test 010 S QA/Test Client N/A SWR SCM Regression 010 S Regression N/A SWT SCM Training 010 S End-User Training N/A SWF SCM Production Support 010 S Production Fix Dev N/A

SWS SCM Production Support 010 S Production Fix QA N/A

SWP SCM Production 010 S Production N/A

CWX CRM Sandbox 300 S Sandbox N/A

CWD CRM Development 010 S Development N/A CWQ CRM QA/Test 010 S QA/Test N/A CWR CRM Regression 010 S Regression N/A CWT CRM Training 010 S Training N/A CWF CRM Production Support 010 S Production Fix Dev N/A

CWS CRM Production Support 010 S Production Fix QA N/A

CWP CRM Production 010 S Production N/A


Catalyst System/Client Usage Non-ECC Systems




Comments

BWX BW Sandbox 010 S Sandbox N/A

BWD BW Development 010 S Development N/A

BWQ BW QA/Test 010 S QA/Test N/A

BWT BW Training 010 S Training N/A

BWF BW Production Support 010 S Production Fix Dev N/A

BWS BW Production Support 010 S Production Fix QA N/A

BWP BW Production 010 S Production N/A

XGX XI Sandbox 010 S Sandbox N/A

XGD XI Development 010 S Development N/A

XWQ XI QA/Test/Training 010 S QA/Test N/A

XWT XI Training 010 S XI Training N/A

XWF XI Production Support 010 S Production Fix Dev N/A

XWS XI Production Support 010 S Production Fix QA N/A

XWP XI Production 010 S Production N/A


Landscape Dynamics – Best Practices

Clear Communication and Identification of roles and responsibilities Program Migration Coordinator currently reports to --- organization --- manages and owns the Production Support Stream --- manages and owns the Development Stream Basis/ARCH resources support both Production Support and Development

environments. Coordinating the logistics of the Migration process belongs to both the Wave &

Migration Coordinators. Basis/ARCH resources responsible for executing the technical mechanism of TMS

system based on input from coordinators.

During migration from development stream to Production Support Stream, both Production Support Resources and Program Migration Coordinator must be involved to ensure successful consolidation

Upon completion of migration/consolidation activities, production stream sole ownership is returned to production support organization (---)

Test Landscapes must include adequate test environments for all legacy systems to be impacted.

Production Support Stream and Next Wave Development should remain in separate, distinct landscapes to preserve integrity and quality of changes migrated to Production, as well as Next Wave Testing environments


CATALYST SAP CHANGE MANAGEMENT

VOLUME TESTING / Regression /DEPLOYMENT PRE-PROD

INTEGRATION TEST GLOBAL ITL(QA) /USER ACCEPTANCE TEST DEPLOYMENT ITL(QA)

WIP - UNIT TESTGLOBAL DEV

RELEASE TODEPLOYMENT PRODUCTION SUPPORT

LANDSCAPE

KRAFT - ProjectTeam Member

KRAFT - ProjectTeam Lead

KRAFT -TransportManagement

KRAFT -SAP Factory /IntegrationManagement /CABManagementKRAFT - CCM

Initial Statusis “O” O

OA

I

RO

RA

ACAB

J

Distribute Transportwithin The Global

Development & ITL(QA) Systems

VT

OU

OP C

OX

Distribute Transportto The DeploymentProduction System

RPBCAB

RQRU

LEGEND

C Ticket isclosedOX

Ref. CPR validatedfor downstreamchangenotification

RP Work is inProduction

OP Work is Approvedfor Production

OU Work is ready forProduction

VT Work has passedVolume Testing

BCAB

Work is approvedby the CAB forPreProduction

UATWork has passedUser AcceptanceTestingO

Ticket isOriginated

JTicket is closed -Work is stoppedand any work isundone.

OATicket is approvedat the project teamlead level

ACAB

Ticket is approvedat the IntegrationManagement levelfor work start

I Work in Progress RUWork has beenUNIT Tested andreleased to ITL/QA

RQWork has beenIntegration testedand approved fordelivery toDeployment ITL

ROWork has failedand reworkrequested

RAWork has beenapproved forrework

OKWork has beenverified andfunctioning asdesigned

OK

Distribute Transportto The Deployment

Pre-ProductionSystem


ITL (QA) System

RI

RIWork has beenUNIT Tested andvalidated forrelease to ITL/QA

UAT


CATALYST SAP CHANGE MANAGEMENT WORKFLOW

GD0100 - Reopen Work

Transport / Work is reviewed forrework or undo process

RO

TicketApproval

<

<<

>>>

NO

YES

UNITTEST

FAIL

RQ0200 - CAB Approval

Transport / Work has beenreviewed and verified by the CAB

B

GQ0200 - Integration Testing

Transport / Work has passedIntegration Test and is ready fordistribution to Deployment ITL

RQ

Validated UNITTest Transportsare sent to Leadand CAB forapproval

PASS

PASS

FAIL

RPP200 - Volume Testing

Transport / Work has passedVolume Testing

VT

I

FAIL

Rework?

YES

NO

PASS

RQ0200 - User Acceptance Test

Transport / Work has passed UserAcceptance Testing

UAT

<<<

RPD200 - Production Release

Transport are approved forrelease to Production

OU

RPD200 - Production Activation

Transport / Work has beensuccessfully imported and activated

in Production and is live

C

INT.TEST

I

GD0-100 - Tasks Validated

Transport / Work has passed UNITTest and is ready for Integration

Testing

RU

TicketApproval

<<<

NO

YES

Transports arereleased to ITL(QA) forIntegrationTesting

CSC-100 - Initial Request

CPR Ticket is created to requestwork to start at the project level

O

Initial RequestTicket Created torequestdevelopmentwork approval

CSC-100 - Project Approval

CPR ticket is approved at theproject level

OA

CSC-100 - SAP Factory Approval

SAP Factory / CAB approval isgranted for work to start

A

Initial CPRTicketsapproved forwork initiatingautomatictransportgeneration ontargetdevelopmentsystems

IntegrationManagementreviewed andapproveddevelopmentrequests

GD0-100/200 - Support Work Starts

Transport / Work is started andprepared for UNIT Test

I

Tasks areapplied to teammembers forwork to start.Team Memberscan alsotransport locallyvia SCC1 toGD0-200 forvalidation

UATTEST

<<<

FAIL

PASS

FAIL

PASS

CABApproval

<<

<


Pre-ProductionSystem

RelTo

PROD

>>>

FAIL

PASS

Distribute Transportto The DeploymentProduction System

RP

>>>

Distribute Transportwithin The GlobalDevelopment & to

the ITL (QA) Systems

VOLTESTING

GD0100 - Stop Work

Transport / Work is stopped andundo process applied for work

released

J

Transports areapproved in ITL(QA) for blockpoint release toDeployment ITL(QA) and UserAcceptanceTesting

User acceptancetesting hascompleted andstatus set toUAT for deliveryto the CAB forrelease approvalto Pre-Production

Block pointrelease of workis granted by theCAB for deliveryto the Pre-Productionsystem forVolume Testing.

Block Pointrelease work haspassed volumetesting and isready for releaseto production

Transports areset to release toproduction byteam members


Transport / Work has beensuccessfully imported and activated

in Production and is live

OK


Reference CPR is created fordownstream notification of change

OX

RPD200 - GoLive Approval

Transports are approved fordelivery to Production

OP

GD0-100 - Tasks Validated

Transport / Work has passed UNITTest and is approved for release

Global ITL/QA Integration Testing

RI

Transports areapproved to bereleased ITL(QA) forIntegrationTesting


ITL (QA) System

<<<

<<<

GD0100 - Reopen Approval

Transport / Work is approved forrework and is returned to the initiate

work state

RA

Transports areapproved forrelease toproduction bythe Team Lead /CodesetManagers

Transports aremoved toproduction andthe release isdeployed

Transport workis complete andworking inproduction

Work is doneand ticket isclosed

Changes arereported back tothe respectivesustain orenhancementlandscapesN-1 -> NN -> N+1


Catalyst Realization Landscape – Stage 1

Availability Timeline: Mar 2007 through Apr 2007

ECC

Development

BI SolManSCM CRM

SMT

Client 200

CWD

Client 010

SWD

Client 010

BWD

Client 010

EWD

010 Golden

100 Unit Tst

110 ABAP

120 Data Ld1

090 ProtoType

800 Security

Master

Technical Sandbox BWX

Client 300

SWX

Client 300

CWX

Client 300

SMX

Client 300

EWX

Client 300

SMP

Client 200



Availability Timeline: Apr 2007 through June 2007

EWD

ECC

Development

QA/Test

User Training

Technical Sandbox

Regression

BI SolManSCM CRM

EWQ

EWT

EWX

EWR

BWD

BWQ

BWX

BWR

SMT

SMX

SMP

SWD

SWQ

SWR

SWX

CWD

CWQ

CWR

CWX

BWT SWT CWT



Availability Timeline: July 2007 through Go Live and Sustain

EWD

ECC

Development

QA/Test

User Training

Technical Sandbox

Regression

BI SolManSCM CRM

EWQ

EWT

EWX

EWR

BWD

BWQ

BWX

BWR

SMT

SMX

SMP

SWD

SWQ

SWR

SWX

CWD

CWQ

CWR

CWX

BWT SWT CWT

ProdFix Dev

ProdFix QA

Production

EWF

EWSEWP

BWF

BWP

SWF

SWP

CWF

CWPBWS SWS CWS


Logical RFC Connections Between Sandbox Systems

Data is extracted out of legacy systems, cleansed, mapped and loaded via IDOCs into Receiving ERP systems

Data is extracted out of ECC systems via RFC and loaded into BW InfoCubes

Bi-directional feed to/from systems, either via RFC or IDOC. SolMan obtains/pushes centralized system mgmt data to/from all systems

Potential bi-directional interface to/from legacy systems & ERP systems

Legend

ECC SystemSWX 100

Legacy Data Systems

Ascential / ItemField/JcapsData Transformation Systems

BW/ Reporting BWX 010

SCM SystemSWX 010

CRM SystemCWX 010

Solution Mgr SMT 200


Logical RFC Connections Between Development Systems

Data is extracted out of legacy systems, cleansed, mapped and loaded via IDOCs into Receiving ERP systems

Data is extracted out of ECC systems via RFC and loaded into BW InfoCubes

Bi-directional feed to/from systems, either via RFC or IDOC. SolMan obtains/pushes centralized system mgmt data to/from all systems

Potential bi-directional interface to/from legacy systems & ERP systems

Legend

ECC SystemEWD 100

Legacy Data Systems

BW/ Reporting BWD 010

SCM SystemSWD 010

CRM SystemCWD 010

Solution Mgr SMP 200

Ascential Data / ItemFieldData Transformation Systems


Transports

Transports are a mechanism for migrating SAP ABAP based objects from one environment / client to the next.

A transport migration can be seen as having two phases: an export and an import phase.

Releasing a transport initiates the export phase which causes all the changes to the objects in the transport to be written out to a file in the operating system.

Importing the transport takes the objects from the file to be uploaded to the new client or new environment


Development

100Unit Test

010 Golden

110Development

90Prototype Configuration


100Integration Test

010Golden

110Security Test

Training

710Class Room 1

010Training Master

720Class Room 2

7n0Class Room n

:

Manual Entry

Configuration TransportsWorkbench Transports

Client Copy

Transport Management and Client Copy Tool

120Process Test

105Unit Test Ref Mst

Quality Assurance TestProduction

010 Production

Development

200 Unit Test

010 Golden

210 Development


010 Golden

800 Security

230 Security

Regression

010 Regression



Extended TMS Setup for Next Wave mySAP ERP Systems

Configuration Transport Requests automatically get assigned to ZC1 transport layer

Workbench Transport Request automatically get assigned to ZD1 transport layer

ZC1 transport layer points to /ZCON1/ transport group

/ZCON1/ transport group points to Unit Test and Development client in Development system and Golden and Integration Test client in Quality Assurance System

ZD1 transport layer points to /ZDEV1/ transport group

/ZDEV1/ transport group points only to the Integration client in Quality Assurance System

For future waves, new transport layers ZC2 & ZD2, and transport groups /ZCON2/ & /ZDEV2/ can be added according to the phase 2 clients and requirements

TMS can be automated where released requests get imported into appropriate

clients automatically.

April 7, 2023


Transport Organizer (1)

Provides tools for complex system landscapes

Enables navigation to: Selection screens for

different transport types

Workbench Organizer Customizing

OrganizerAny selection screen can

be defined as a user-specific default initial screen

Transport Organizer: Initial Screen

Request types

CustomizingWorkbench

Copy transports and relocations

Object list

Client transports

SAP/partner customer

Choose

April 7, 2023



The functions for transport of copies and relocations are:Transport of copies:

Transports objects without changing location of original object

Relocation without development class change: Transports objects making them originals in target

system; for temporary relocationsRelocation with development class change:

Transports objects making them originals in target system; for permanent relocations

Relocation of a complete development class: Used to change the development system

of an entire development class

April 7, 2023


Include object lists from other requests

Replace subobjects with complete objects

Select objects freely

Display Transport Requests

Object list of user D40BC

Modifiable

Object List Freely created object list

ZSD-PROGS SD programs

ZFI-PROGS FI programs


With Object lists, you can:

April 7, 2023



Include objects in request Is an extension of the former Include template

functionIs available in all Change and Transport Organizer

transactions

Allows you to merge the object lists of selected requests into the current request

Object Lists

Change object listDisplay object list

Lock objectsSort / compress

Obj. directory entriesDisplay object keys

Include objects

Include Objects in Request

Object list from requestObject list from several requestsFreely selected objects


How Transport Management System (TMS) captures Changes?

Changes are tracked in Requests and Tasks.(Request = Transport & Tasks = Work)

A Request is a logical group of work.

One Request may contain multiple Tasks.

Functional Lead creates a Request and assigns Team Members a Task under the request.


Example:Three members of a Team are working on related information.

Result:Functional Lead creates a Request for the work and assigns each Member a Task in the Request.



REQUEST (owned by Functional Lead)

TASK 1 (owned by Team Member A)

TASK 2 (owned by Team Member B)

TASK 3 (owned by Team Member C)



As Team Members finish their work, they document it and release their own task to the request.

When all tasks are released, the Process Lead and Configuration Review Board will review the work, verify proper documentation, and release the Request.

Exporting and Importing of transports in the same sequence on respectively source and target systems is critical to ensure the correct synchronization of such systems.

When the configuration teams get started in their configuration activities, they will be picking from the list of tasks that are assigned to them.

Transports requests should be grouped in logical constructs for your stream. Not all work is going to be done in one transport – yet we don’t want one transport for each IMG configuration item.


How Does Customizing Move Between Systems?ECC Configuration Example

EWD

100 Unit Test

110 ABAP

120 Data Ld1

010 Gold Mstr

800 Security

Master

090 Prototype

1) Configurator logs into Sandbox client 090

2) Performs initial prototype configuration and baseline testing. No change control enabled. No client-independent changes allowed.

2

EWX

300 Sandbox

1) Configurator logs into Sandbox System/ client 300, and performs initial prototype with no change control enabled, OR

2) Can perform initial prototype in EWD Client 090/010.

3) NOTE: All client-independent changes must be prototyped in EWX

1

Tip: Open separate login sessions for each client, to facilitate work



EWD

100 Unit Test

110 ABAP

120 Data Ld1

010 Gold Mstr

800 Security

Master

090 Sandbox

3 1) Configurator Lead logs into Gold Client 010

2) Lead Opens New Change Request for Customization, and assigns tasks to configuration team members

3) Configurator performs customizing, and saves changes in Task




EWD

100 Unit Test

110 ABAP

120 Data Ld1

010 Gold Mstr

800 Security

Master

090 Proto

4 1) Configurator logs into Unit Test Client 100

2) Executes Transaction SCC1 and provides Change Request # already created in Client 010 to bring transport into Unit Test Client

3) Perform Unit Test with subset of master and transactional data

4) If Unit Test unsuccessful, user logs back into client 010, and continues making changes to open transport/tasks

5) Once changes have been made, repeat from step 2 above to bring revised transport into Unit Test Client for testing




EWD

100 Unit Test

110 ABAP

120 Data Ld1

010 Gold Mstr

800 Security

Master

090 Proto

5 1) Configurator Lead logs into Gold Client 010

2) Tasks and transport are released for export




On Demand/Daily TransportsWeekly Scheduled/Controlled Transports

Weekly Client Refreshes from 200 Master Client after Transports received from RD1On Demand/scheduled Cross-system client copy/refresh

EWR010 RegressionEWD

100 Unit Test

110 ABAP

120 Data Ld1

010 Gold Mstr

800 Security

Master

090 Proto

EWQ


010 Master Int.

110 Mstr Data Ld1

120 Mst Data Ld2

EWT

010 Train Master

701 User Train #1

702 User Train #2

703 User Train #3

300 User Sandbox

Lab Area

704 User Train #4

EWX

300 Sandbox


Transport Requests

Configuration Activity

Development Activity

Basis / Security Activity

Create Tranport Request in DevBusiness Process Substream Lead

Delivery Service Substream Lead

Basis Team Member

• Transport requests will be created by the following individuals:

Request to transport will be reviewed daily by the integration / testing team to ensure that it is an appropriate time to release the activity to the QA environment.




Approval 1 Release to QABusiness SubStream Lead

IT Delivery Service Lead

Support / Security Lead

Approval 2 Release to QAIntegration / Test Coordinator

Integration / Test Coordinator


Proposed migration to QA transport time – 4 times a day: at 9AM, 11AM, 1PM, & 3PM


TMS related FAQs

Question:Is order important when transporting from one system (development) to

another (quality assurance) ?

Answer:YES! Items are imported in the same order in which they are released.

You and the Functional Lead need to ensure that objects which are dependent upon each other are released in the proper order. (see example on next two slides)


TMS related FAQs

Importance of Sequence while Transporting

(example)

Server buffer

Request #1 independent of other objects

Request #2 program which references ZTEST table


Request #4 table ZTEST definition and structure


TMS related FAQs

Importance of Sequence while Transporting

(example)

Server buffer


Request #2 program which references ZTEST table


Request #4 table ZTEST definition and structure

will FAIL the import because it references ZTESTwhich isn’t imported until Request #4!!!


TMS related FAQs

Question:Is there a way to move any changes from the Prototype or Unit Test

client ?

Answer:NO! Since change tracking is turned off within these clients, nothing can

be moved out of them.


TMS related FAQs

Question:Is everything transported via the normal transport methods ?

Answer:NO! Certain objects require manual intervention either for creating the change

request or performing post-import tasks.

Examples:

•Some Client Master Data are not transported via TMS. They are either entered manually, or via batch input programs. Some Client Master Data are transportable; refer to specific IMG tasks for applicability.

•SAP Scripts are transportable via normal TMS methods, but special considerations should be taken when the target system has multiple-clients.

•SAP Queries (ad-hoc) require special steps for transporting to another client and/or system.

•Factory Calendar is transportable via normal TMS methods, but the change request must be manually created via the IMG customizing (SCAL).


Best Practices When Transporting BW Objects (I)•Transport all customer-defined packages (dev classes) before transporting objects•Transport InfoProvider(s) using the “In Data Flow Before” or “Only Necessary Objects” grouping option•Transport all Global Variables with primary package assignment i.e. ZBW•Transport BEx objects with appropriate individual package assignment•Transport roles and workbooks together

Best Practices When Transporting BW Objects (II)•Objects need to be transported with respect to their dependencies•InfoProviders will bring in all relevant InfoObjects•Importing of Global variables is dependant on their reference•InfoObject being already active•Queries, workbooks and roles are dependant on InfoProviders and InfoObjects being active•Use the Transport Connection Tool to analyze your objects•Is it in another transport owned by someone else?


Release the requests together! What is its relationship to other objects? What else does it contain within it? Consider transporting smaller units of work Reduce complexity and dependencies Logical grouping of object (i.e. InfoOjects, InfoCubes) to create building

blocksBenefitsEasier to analyze transport errorsAvoids cascading failure effectEasier to manage objects in transportsEasier debugging


PROD Approval Process

Production approval process




Approval 1 Release to ProdIntegration / Test Coordinator



Migration Request Created by Integration

Approval 2 Release to ProdBusiness Stream Lead

Business Stream Lead

Business Stream Lead

Proposed migration to production transport time – Saturday evenings


SAP ApplicationRequest

Catalyst Initial Support Flow

Resume Work Activity

SAPSecurity Request

SAP Installation, SAP GUI,

SAP Printing Request

Submit an email to: [email protected] OR

Call Customer Support: (xxx) xxx-4111, Select SAP Option (3-1)1-877-xxx-xxxx, Select SAP Option (3-1)

1. Request password reset

2. Request access change

3. Request an SAP user id

Download Forms link: http://catalyst.intranet.kraft.com/

3. Consult On Site Support if available

1.Check ProdPak/ Training material on website

2. Consult Super User No

Yes

Resolved?

* Follow existing procedures for non-SAP system security and application support.

Submit an email to: [email protected] OR

Call Customer Support: [email protected]

Passwords are synchronized to network ID “1. Request Password Reset”

Submit an email [email protected]

ORCall Customer Support:

Link: http://catalyst.intranet.kraft.com/Training/indexr.asp

Contact Designated Contact


Change Management (ITIL Scenario)

“The objective of change management is to carry out changes economically and in a timely manner with minimal risk”

Registration andClassification

Approval

Evaluation / PostImplementation Review

ChangeManage-

ment

Building

Testing

Implementation

Program/Project

Manage-ment

Monitoring andPlanning

Authorization andImplementation

ChangeMonitoring


Ability toEXECUTE

Strategy forGROWTH

Businesschange

Processes in Change Request Management

SAP Solution Manager – Change Request Management

Management of all change requests

Change request categorization

Change impact analysis

Approval workflow

Status reporting

Complete change history

Change Administration

Customizing & Development (Realization)

Test execution

Transport scheduling

Transport tracking

Change Logistics

Project Management

Project planning & budgeting

Project documentation

Customizing & Development (Specifications)

Test management


Change Request Management - Roles

Requester

… is the central role in Change Request Mgmt. He categorizes and approves Change Requests.

… is the Steering Committee when changes like upgrade or new implementations are concerned.

… implements a change, sets status in the Change Document and hands over to the Tester.

… tests a change, sets status in the Change Document.

… takes care of software logistics.IT Operator

Change Manager

Change Advisory Board

Developer

Tester

IT Operator

Change Manager

Change Advisory Board

Developer

Tester

… creates an error message or a Change Request directly (e.g. as in idea management) Requester


Emergency Correction Process

Change LogisticsProblem Message

Implement correction

SAP Solution Manager – Change Request Management

Change Administration

Test correction

Tester

€User

€Change Manager

Release correction

Import correction (PRD)

Complete task plan

Import correction (QAS)

‚Operator

€Developer

Task plan

Change Document Open

In process

Realized

To be tested

Tested

Productive

Confirmed

Change Request

Open

In process

(Rejected)

Approved

Realized

Confirmed


Technical Scope of Change Request Management

Import SAP support packages (transaction SPAM)

Implement SAP notes (transaction SNOTE)

Modification adjustments (transaction SPAU)

Install Add-Ons (transaction SAINT)

Implement Upgrade (from technical and content point of view)

Change scenarios, processes, and process steps

Implement new scenarios, processes, and process steps

Implement new SAP products and Add-Ons

Change and enhance customer owned developments

Change Customizing

Add and change master data

Add and change organizational data


SIR Process: Overview

Create SIR in Solution Manager

Review and Approve SIR

Review Approved SIR &

Move In Process

Fix in Development and Unit Test

Request Migration

Approve Migration Transport Test

1 2 3 4 5

6 7 9No

Yes

Verify Transport

10

Request Production Migration

TransportVerify

TransportValidate

Production

SIR Fixed?

Approve Production Migration

13Notify User

of Resolution

PROJECT TEAM/HELP DESK/POINT OF CONTACTS

PROJECT TEAM

BASIS TEAM

8

15141211

SIR = System Investigation Request


Post Cutover Change Control Process for Production Support

EWD

EWF EWS

EWP

ECCEWQ

BWT

BWF BWSBWP

BI

BWD

1. Review SIRs. • Daily 9am, 4pm• Cross team impact? • Team members

should not work on SIRs until Approved

• Once actively working on a SIR, status updated to In Process

2. Approve migration to Test ‘S’:•BW - approvers•ECC – approvers•CRM – approvers•SCM – approvers•Code per standards? Need training documents? Config documented? Performance? Security? Batch?

3. Test:•Document results in SIR•Obtain business resource sign off in SIR (see slide 3)•Business resource to assess responsibility for S testing

4. Migrate and Test in S:•F -> S migrations approved by •Test SIR in S •Monitor daily list of migrations to S not moved to P (to maintain integrity of S)

5. Approve Production Migration:•Daily 4pm meeting•Review change control checklist•Approvers: •Transports moved daily 6pm, if required for batch, otherwise 7:30 am (after batch)•Person assigned to SIR to update status to User Confirmation after confirming in production

New Developments Production Support Fix System Copy (Monthly Refresh)

Transports to training environments on case by case basis

Open -> Approved -> In Process -> In Development

Completed -> User Confirmation (email sent to User)

SIR StatusNew -> Open (email sent to User)

In Test -> Business Sign Off

EWR

BWQ BWR


SWD

SCM

SWF

SWR

SWPSWS

SWQ

1. Review SIRs. • Daily 9am, 4pm• Cross team impact? • Team members

should not work on SIRs until Approved

• Once actively working on a SIR, status updated to In Process

2. Approve migration to Test:•APO - approvers•Code per standards? Need training documents? FD/config documented? Performance? Security? Batch?

3. Test:•Document results in SIR•Obtain business resource sign off in SIR (see slide 3)• SOAR business resource to assess responsibility for Q testing

Post Cutover Change Control Process

New Developments Production Support Fix System Copy (Monthly Refresh)Transports to training environments on case by case basis

4. Migrate and Test in Q:•T -> Q migrations approved by Venkat (Rey)•Test SIR in Q •Monitor daily list of migrations to Q not moved to P (to maintain integrity of Q)

5. Approve Production Migration:•Daily 4pm meeting•Review change control checklist•Approvers:•Transports moved daily 6pm, if required for batch, otherwise 7:30 am (after batch)•Person assigned to SIR to update status to User Confirmation after confirming in production

Completed -> User Confirmation (email sent to User)

SIR StatusNew -> Open (email sent to User)

Open -> Approved -> In Process -> In Development In Test -> Business Sign Off

SWT

SWD


Post Card – Aug 07

Support / Contact Info

Transports / General SupportEmail: [email protected]

On Site Support8:30 AM – 5:30 PM EST

Remote SupportUS: 5:30 PM – 9:00 PM ESTIDC: 9:00 PM – 9:00 AM EST

BASIS PrimaryPager: 888-xxx-0962Email: [email protected]

BASIS SecondaryPager: 877-XXX-XXXXEmail: [email protected]

Escalation

VVVVMobile: Email:

RRRRRPager: Email:

Transport Schedule

Test Systems02:00, 05:00, 08:00, 11:00, 15:00, 17:30 – EST

Production Systems – After BatchR3: 1st & 3rd Friday’sBW & APO: 1st & 3rd Thursday’s

Outages

PRODUCTIONSecond & Third Sundays – 05:00 – 09:00 PM EST

NON PRODUCTIONSecond Wednesday – 05:00 – 09:00 AM EST

OUTAGE CALENDEROutage Calendar - 2007.DOC


CATALYST Production System – Legend

LowCriticality

HighCriticality

MediumCriticality

Connected to,but outside

of CATALYST

Criticality Rating SAP System Size Data Flow

one directional

bi-directional

NFS mount

May 2004



Presentation Ends…. Rest of the slides TBD


CATALYST SAP WM System – SAP Console

SAPWarehouse

Management (WPA)

chp433eupmcchsap37eupmcchsap38

Web Consoles

Warehouses

W-LAN

WAN LAN

Core SAP ERP SystemEWP

May 2004


CATALYST Production System Integration View – Level 1

SCM

ECC

SAP WM(Catalyst)

SAP BI

PBS/IXOSArchive

Printing(Jetform)

Middleware

Scheduling

Oracle DWSwift

SAP Console

Galaxy

XCOM

Pandora

SCORE

CRM


Pandora

CATALYST Production System View – Level 2

SAP Procurement(???)

Core SAP ERPSystem(EWP)


(Catalyst)(WPA)

SAP Business Warehouse

(KPW)

PBSArchive

PageFormatting(Jetform)

E*Gate(page 04)

Control-M

SAP Consoles

Galaxy

XCOM

DataWarehouse

RFCBapi,Edi

ALE

NFS mount

RFC

RFCRFC, rsh

NFS RFC

LAN

“Printing”

NFS mount

May 2004

Oracle DWSwift

SCORE


SCORE

Pandora

Lotus

CATALYST Production EWP SAP System – E*Gate

SAP Procurement(KPE)

Core SAP ERPSystem(EWP)


(Orion)(WPA)

SAP Business Warehouse

(KPW)

IXOSArchive

PageFormatting(Jetform)

E*Gate

Control-M

Oracle DWSwift

SAP ConsoleRadio Frequency

Galaxy

XCOM

DataWarehouse

RFC

Bapi,Edi, FTP

ALE

NFS mount

RFC

RFCRFC NFS RFC

May 2004


CATALYST Production E*Gate – SAP EWP

EWP

chd003

baut101

chp143

Nordic

Italy

Switzerland

StarUk

StarIberia

chp152

Central

StarSap

baut201(Banbury)

StarUk

LocalSystems

LocalSystems

laua0313

Benelux

eupmcchlauapp27

EAI

KFI

P

XCOM SAP EGATEORACLE

May 2004


GLOBAL/WEST SAP Client Hub Landscape

GLOBAL EAST - EUROPEWEST - NORTH AMERICA

SAP

ECCWEST

SAP

WMWEST

SAP

CRMWEST

SAP

SCMWEST

SAP

XMIIWEST

CLIENT 100HUB

SAP

EPGLOBAL

SAP

PLMWEST

SAP

MI-RFIDWEST

CLIENT 010/110CONFIG/ABAP

CLIENT 1n0UNIT TESTS

SAP

BWWEST



SAP

TREXWEST

SAP

SOLUTIONMGR

GLOBAL

CLIENT 100HUB

SAP

--GLOBAL

SAP

--GLOBAL

SAP

PIGLOBAL

SAP

MDMGLOBAL

SAP

SRMGLOBAL



SAP

BWGLOBAL

LIVECACHE

OPTIMIZER

SAP

ECC*EAST

CLIENT 100HUB

SAP

BWEAST

CLIENT 101CONFIG/ABAP

CLIENT 102-5UNIT TESTS

SAP

TREXEAST

SAP

--

GLOBAL

SAP

SRMEAST

SAP

NWDIGLOBAL

SAP

SEMWEST

SAP

SCMEAST

LIVECACHE

OPTIMIZER

SAP

XMIIEAST

SAP

MI-RFIDEAST

SAP

TREXEAST

Documents

Kraft Global SAP Landscape