You are on page 1of 114

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

Catalyst SAP Implementation Overview

Business Requirements Following 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

Catalyst SAP Implementation Landscape Dynamics Deployment Basics

Deployment Basics - Definitions Functional Releases Introduces new SAP/business process functionality, or major rework of business process functionality during a future deployment Rollout 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

Catalyst SAP Implementation


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

Three-tier Environment

End Users

Web AS 1

Web AS 2

Web AS 3

Web AS n

Database Server

Catalyst SAP Implementation


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

Catalyst SAP Implementation


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 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 Configuration and custom development are integration tested here Typically refreshed from Production environment to allow testing with production data 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 Multiple End user classroom training is conducted here Trained users can practice here in a practice client prior to go live 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 consists of a single client

Development Environment

Quality Assurance Environment Regression Environment Training Environment Production Fix Dev & QA Environments

Production Environment

Catalyst SAP Implementation


When do I need each environment?

Sandbox environment Implemented at the beginning of blueprint phase to demonstrate, and use it as a reference Development environment Implemented prior to implementation phase Quality 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 Implementation


Catalyst SAP System Naming Convention

System Identifier ( e.g. EWD )

Position 1
A NetWeaver Infra (eg.RFID) B Business Warehouse/SEM E ECC G GTS

Position 2
Differentiates Regional vs. Global Systems E: East W: West G: Global

Position 3
X Sandbox D Development Q Quality Assurance R Regression T Training F Prod Fix Dev S Prod Fix Test P Production

L LiveCache for SCM


M MDM P Portal R SRM S SCM/SolMan W Ware House Management X XI

Catalyst SAP Implementation Phased Development Scenario

Manual re-entry of changes

On going support

Release N

Regression

Development

Quality Assurance

Production
Training

Production Support

Prod-Quality Assurance

Owner of Objects

Release N+1
Project Development

Development
ECC 6 CRM SRM SCM XI EP EWF CWF RGF SWF XWF PGF Global Trade Warehouse BI (Global) BI (Local for West) SEM TREX xAPP GGF WWF BGF BWD BSF TWF --ECC 6 CRM SRM SCM XI EP

Pre-Prod
EWS CWS RGS SWS BSS PGS Global Trade Warehouse BI (Global) BI (Local for West) SEM TREX xAPP

Catalyst SAP Implementation


GGS WWS BGS BWS SWS TWS ECC6 --CRM SRM CWP KPE EWP

Production

MDM
Support

MGF

MDM

MGS

SCM SMT

SWP

XI EP MDM Global Trade Warehouse BI (Global) GGR Global Trade CRM SRM SCM XI EP CWD RGD SWD XWD PGD Warehouse BI (Global) WWD BGD CRM SRM SCM XI EP CWQ RGQ SWQ XWQ PGQ Warehouse BI (Global) BI (Local for West) SEM TREX xAPP WWQ BGQ BWQ BSQ TWQ --CRM SRM SCM XI EP CWR RGR SWR XWR PGR WWR BGR Warehouse BI (Global) BI (Local for West) TREX xAPP TWR --SEM Sol Man TREX xAPP NWDI GSLD

XWP PGP MGP

Development Sol Man ECC 6 EWD Global Trade GGD ECC 6

Quality Assurance EWQ Global Trade GGQ ECC 6

Regression Test EWR

GGP WWP BGP BWP BSP SMP TWP --NDP ---

BI (Local for West) BWD SEM TREX xAPP BSD TWD ---

BI (Local for West) BWR SEM BSR

Sandbox & Training ECC 6 CRM EWX CWX SRM SCM RGX SWX XI EP XWX PGX Global Trade MDM GGX MGX

Project

MDM

MGD

MDM

MGQ

MDM

MGR

BI (Global) BI (Local for West) SEM

BGX BWX BSX

Warehouse TREX xAPP

WWX TWX ---

Sol Man

SMX

ECC 6 CRM

EWT CWT

SRM SCM

RGT SWT

XI EP

XWT PGT

Global Trade Warehouse

GGT WWT

BI (Global) BI (Local for West) SEM

BGT BWT BST

Warehouse TREX xAPP

WWT TWT ---

Development
ECC 6 CRM SRM SCM EWF CWF RGF SWF XWF PGF MGF Global Trade Warehouse BW (Global) BW (Local for West) GGF WWF BGF BWF ECC 6 CRM SRM SCM XI EP MDM

Pre-Prod
EWS CWS RGS SWS XWS PGS Global Trade Warehouse BW (Global) BW (Local for West)

Catalyst SAP Implementation


GGS WWS BGS BWS

Support

XI EP MDM

Production
ECC6 EWP CWP KPE SWP XWP PGP MGP BGP BWP GGPF WWP SMP

MGS CRM SRM SCM

ECC 6 CRM SRM SCM

ECC6 XI All changes in EWF to be manually replicated to EWD For Config Changes, Solution manager, table compare and table sync may be used EP Replication Process doc to be created Development Quality Assurance Regression Test MDM Transport path : EWD ->EWQ ->EWR then imported to as a Cut over TP package to EWF EWD ECC 6 EWQ ECC 6 EWR Global Trade GGD Global Trade GGQ Global Trade GGR And transported to ->EWS ->EWP BW (Global) CWD CRM CWQ CRM CWR Warehouse WWD Warehouse WWQ Warehouse WWR The following systems are tightly coupled with this landscape and should be considered at the time of refresh RGD SRM RGQ SRM RGR BW (Global) BGD BW (Global) BGQ BW (Global) BGR BW (Local for West) CRM, SRM, SCM, BI / BW, Warehouse, XI, Portal, SEM SWD SCM SWQ SCM SWR
BW (Local for West) BWD BW (Local for West) BWQ BW (Local for West) BWR XWD PGD MGD XI EP MDM XWQ PGQ MGQ XI EP MDM XWR PGR MGR Global Trade Warehouse Sol Man

Sol Man

SMT

Project

XI EP MDM

Sandbox & Training


ECC 6 CRM EWX CWX SRM SCM RGX SWX XI EP XWX PGX Global Trade MDM GGX MGX Sol Man BW (Global) BW (Local for West) BW (Global) BW (Local for West) BGX BWX BGT BWT Warehouse WWX

ECC 6 CRM

EWT CWT

SRM SCM

RGT SWT

XI EP

XWT PGT

Global Trade Warehouse

GGT WWT

SMX

Development
ECC 6 CRM SRM SCM EWF CWF RGF SWF XWF PGF MGF Global Trade Warehouse BW (Global) BW (Local for West) GGF WWF BGF BWF ECC 6 CRM SRM SCM XI EP MDM

Pre-Prod
EWS CWS RGS SWS XWS PGS Global Trade Warehouse BW (Global) BW (Local for West)

Catalyst SAP Implementation


GGS WWS BGS BWS

Support

XI EP MDM

Production
ECC6 EWP CWP KPE SWP XWP PGP MGP BGP BWP GGPF WWP SMP

MGS CRM SRM SCM

SMT

XI EP

Development
Sol Man ECC 6 CRM SRM SCM EWD CWD RGD SWD XWD PGD MGD Global Trade Warehouse BW (Global) BW (Local for West) GGD WWD BGD BWD ECC 6 CRM SRM SCM XI EP MDM

Quality Assurance
EWQ CWQ RGQ SWQ XWQ PGQ MGQ Global Trade Warehouse BW (Global) BW (Local for West) GGQ WWQ BGQ BWQ ECC 6 CRM SRM SCM XI EP MDM

Regression Test
EWR CWR RGR SWR XWR PGR MGR Global Trade Warehouse BW (Global) BW (Local for West) GGR WWR BGR BWR

MDM BW (Global) BW (Local for West) Global Trade Warehouse Sol Man

Project

XI EP MDM

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

Sandbox & Training


ECC 6 CRM EWX CWX SRM SCM RGX SWX XI EP XWX PGX Global Trade MDM GGX MGX Sol Man BW (Global) BW (Local for West) BW (Global) BW (Local for West) BGX BWX BGT BWT Warehouse WWX

ECC 6 CRM

EWT CWT

SRM SCM

RGT SWT

XI EP

XWT PGT

Global Trade Warehouse

GGT WWT

SMX

Development
ECC 6 CRM SRM SCM EWF CWF RGF SWF XWF PGF MGF Global Trade Warehouse BW (Global) BW (Local for West) GGF WWF BGF BWF ECC 6 CRM SRM SCM XI EP MDM

Pre-Prod
EWS CWS RGS SWS XWS PGS Global Trade Warehouse BW (Global) BW (Local for West)

Catalyst SAP Implementation


GGS WWS BGS BWS

Support

XI EP MDM

Production
ECC6 EWP CWP KPE SWP XWP PGP MGP BGP BWP GGPF WWP SMP

MGS CRM SRM SCM

SMT

XI EP

Development
Sol Man ECC 6 CRM SRM SCM EWD CWD SRM RGD Global Trade Warehouse BW (Global) GGD WWD BGD ECC 6 CRM SRM

Quality Assurance
EWQ CWQ RGQ Global Trade Warehouse BW (Global) GGQ WWQ BGQ ECC 6 CRM SRM

Regression Test
EWR CWR RGR Global Trade Warehouse BW (Global) BW (Local for West) GGR WWR BGR BWR

MDM BW (Global) BW (Local for West) Global Trade Warehouse Sol Man

There will be a single landscape of SRM for Eastern and Western Hemisphere regions SWD SCM SWQ SCM SWR
BW (Local for West) BWD BW (Local for West) BWQ

Project

XI EP MDM

The following STAR systems will be renamed : EP PGQ PGD Old SID New SID MDM MGQ MGD KDJ RGF KTE RGQ KTF KGS

XWD

XI

XWQ

XI EP MDM

XWR PGR MGR

Sandbox
ECC 6 CRM

MDM Production SID will remain KPE to mitigate any risks associated with changing the MGQ of a production system SID (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 & Training Links into : Catalog management systems Decision will be taken on either MDM or CCM EWX CWX SRM SCM RGX SWX XI EP XWX PGX Global Trade MDM GGX MGX Sol Man BW (Global) BW (Local for West) BW (Global) BW (Local for West) BGX BWX BGT BWT Warehouse WWX

ECC 6 CRM

EWT CWT

SRM SCM

RGT SWT

XI EP

XWT PGT

Global Trade Warehouse

GGT WWT

SMX

Development
ECC 6 CRM SRM SCM EWF CWF RGF SWF XWF PGF MGF Global Trade Warehouse BW (Global) BW (Local for West) GGF WWF BGF BWF ECC 6 CRM SRM SCM XI EP MDM

Pre-Prod
EWS CWS RGS SWS XWS PGS Global Trade Warehouse BW (Global) BW (Local for West)

Catalyst SAP Implementation


GGS WWS BGS BWS

Support

XI EP MDM

Production
ECC6 EWP CWP KPE SWP XWP PGP MGP BGP BWP GGPF WWP SMP

MGS CRM SRM SCM

SMT

XI EP

Development
Sol Man ECC 6 CRM SRM SCM EWD CWD Global Trade Warehouse BW (Global) BW (Local for West) GGD WWD BGD BWD ECC 6 CRM SRM SCM XI

Quality Assurance
EWQ CWQ RGQ SWQ XWQ Global Trade Warehouse BW (Global) BW (Local for West) GGQ WWQ BGQ BWQ ECC 6 CRM SRM SCM XI

Regression Test
EWR CWR RGR SWR XWR Global Trade Warehouse BW (Global) BW (Local for West) GGR WWR BGR BWR

MDM BW (Global) BW (Local for West) Global Trade

SCMSWD
XWD

RGD

Project

XI EP

EP PGQ EP PGR PGD Warehouse External systems like Manugistics instances will interact directly with SCM. SCM in turn MGQ manage the relationships to LiveMGR will Cache, ECC and BI systems MDM MDM MDM MGD Sol Man 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 MDM MGQ 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 Sandbox & Training SAP systems Planning will occur in Manugistics and the output will be imported into the Catalyst suite of ECC 6 EWX SRM RGX XI XWX BW (Global) BGX Global Trade GGX Warehouse Sol Man CRM CWX SCM SWX EP PGX MDM MGX BW (Local for West) BW (Global) BW (Local for West) BWX BGT BWT

WWX

ECC 6 CRM

EWT CWT

SRM SCM

RGT SWT

XI EP

XWT PGT

Global Trade Warehouse

GGT WWT

SMX

Development
ECC 6 CRM SRM SCM EWF CWF RGF SWF XWF PGF MGF Global Trade Warehouse BW (Global) BW (Local for West) GGF WWF BGF BWF ECC 6 CRM SRM SCM XI EP MDM

Pre-Prod
EWS CWS RGS SWS XWS PGS Global Trade Warehouse BW (Global) BW (Local for West)

Catalyst SAP Implementation


GGS WWS BGS BWS

Support

XI EP MDM

Production
ECC6 EWP CWP KPE SWP XWP PGP MGP BGP BWP GGPF WWP SMP

MGS CRM SRM SCM

SMT

XI EP

Development
Sol Man ECC 6 CRM SRM SCM EWD CWD RGD SWD XWD PGD MGD Global Trade Warehouse BW (Global) BW (Local for West) GGD WWD BGD BWD ECC 6 CRM SRM SCM XI EP MDM

Quality Assurance
EWQ CWQ RGQ SWQ XWQ PGQ MGQ Global Trade Warehouse BW (Global) BW (Local for West) GGQ WWQ BGQ BWQ ECC 6 CRM SRM SCM XI EP MDM

Regression Test
EWR CWR RGR SWR XWR PGR MGR Global Trade Warehouse BW (Global) BW (Local for West) GGR WWR BGR BWR

MDM BW (Global) BW (Local for West) Global Trade Warehouse Sol Man

Project

XI EP MDM

XI / Process Integration (PI)


MDM MGQ 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. EWX CWX SRM SCM RGX SWX XI EP XWX PGX BW (Global) BW (Local for West) BW (Global) BW (Local for West) BGX BWX BGT BWT

Sandbox & Training


ECC 6 CRM

Global Trade MDM

GGX MGX

Sol Man

Warehouse

WWX

ECC 6 CRM

EWT CWT

SRM SCM

RGT SWT

XI EP

XWT PGT

Global Trade Warehouse

GGT WWT

SMX

Development
ECC 6 CRM SRM SCM EWF CWF RGF SWF XWF PGF MGF Global Trade Warehouse BW (Global) BW (Local for West) GGF WWF BGF BWF ECC 6 CRM SRM SCM XI EP MDM

Pre-Prod
EWS CWS RGS SWS XWS PGS Global Trade Warehouse BW (Global) BW (Local for West)

Catalyst SAP Implementation


GGS WWS BGS BWS

Support

XI EP MDM

Production
ECC6 EWP CWP KPE SWP XWP PGP MGP BGP BWP GGPF WWP SMP

MGS CRM SRM SCM

SMT

XI EP

Development
Sol Man ECC 6 CRM SRM SCM EWD CWD RGD Global Trade Warehouse BW (Global) GGD WWD BGD ECC 6 CRM SRM SCM XI

Quality Assurance
EWQ CWQ RGQ SWQ XWQ Global Trade Warehouse BW (Global) BW (Local for West) GGQ WWQ BGQ BWQ ECC 6 CRM SRM SCM XI

Regression Test
EWR CWR RGR SWR XWR Global Trade Warehouse BW (Global) BW (Local for West) GGR WWR BGR BWR

MDM BW (Global) BW (Local for West) Global Trade

Enterprise Portal SWD BW BWD


(Local for West)

Project

XI EP MDM

XWD

Sandbox
ECC 6 CRM

EP EP PGR PGD Warehouse Portal is a required component in this PGQ landscape as SAPs roadmap suggests a continued and increased focus MDM MGR in MGD area to deliver new MDM this functionality.MGQ Sol Man 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) MDM MGQ 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 will be closely integrated. Training additional components such as TREX and Document Management If Yes, EWX SRM RGX XI XWX BW (Global) BGX Global Trade GGX Warehouse Sol Man (Consumer)Portal systems need to be on a PGX platform as they MGX intended to beBW (Local for West) BWX the SAP HA MDM are the gateway to CWX SCM SWX EP domain. EWT CWT SRM SCM RGT SWT XI EP XWT PGT Global Trade Warehouse GGT WWT SMX BW (Global) BW (Local for West) BGT BWT

WWX

ECC 6 CRM

Development
ECC 6 CRM SRM SCM EWF CWF RGF SWF XWF PGF MGF Global Trade Warehouse BW (Global) BW (Local for West) GGF WWF BGF BWF ECC 6 CRM SRM SCM XI EP MDM

Pre-Prod
EWS CWS RGS SWS Global Trade Warehouse BW (Global) BW (Local for West)

Catalyst SAP Implementation


GGS WWS BGS BWS

Repository

Support

XI EP MDM

Repository

XWS PGS

Production
ECC6 CRM SRM SCM EWP CWP KPE SWP XWP PGP MGP BGP BWP GGPF WWP SMP

MGS

SMT

XI EP

Development
Sol Man ECC 6 CRM SRM SCM EWD CWD RGD SWD XWD PGD MGD Global Trade Warehouse BW (Global) BW (Local for West) GGD WWD BGD BWD ECC 6 CRM SRM SCM XI EP MDM

Quality Assurance
EWQ CWQ RGQ SWQ Global Trade Warehouse BW (Global) BW (Local for West) GGQ WWQ BGQ BWQ ECC 6 CRM SRM SCM XI EP MDM

Regression Test
EWR CWR RGR SWR Global Trade Warehouse BW (Global) BW (Local for West) GGR WWR BGR BWR

MDM BW (Global) BW (Local for West) Global Trade Warehouse Sol Man

Project

EP MDM

PGQ MGQ

PGR

MGR

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


ECC 6 CRM EWX CWX SRM SCM RGX SWX XI EP XWX PGX Global Trade MDM GGX MGX Sol Man BW (Global) BW (Local for West) BW (Global) BW (Local for West) BGX BWX BGT BWT Warehouse WWX

ECC 6 CRM

EWT CWT

SRM SCM

RGT SWT

XI EP

XWT PGT

Global Trade Warehouse

GGT WWT

SMX

Repository

Repository

Repository

XI

XWQ

XWR

Development
ECC 6 CRM SRM SCM EWF CWF RGF SWF XWF PGF MGF Global Trade Warehouse BW (Global) BW (Local for West) GGF WWF BGF BWF ECC 6 CRM SRM SCM XI EP MDM

Pre-Prod
EWS CWS RGS SWS XWS PGS Global Trade Warehouse BW (Global) BW (Local for West)

Catalyst SAP Implementation


GGS WWS BGS BWS

Support

XI EP MDM

Production
ECC6 EWP CWP KPE SWP XWP PGP MGP BGP BWP GGPF WWP SMP

MGS CRM SRM SCM

SMT

XI EP

Development
Sol Man ECC 6 CRM SRM SCM EWD CWD RGD SWD Global Trade Warehouse BW (Global) BW (Local for West) GGD WWD BGD BWD ECC 6 CRM SRM SCM

Quality Assurance
EWQ CWQ RGQ SWQ Global Trade Warehouse BW (Global) BW (Local for West) GGQ WWQ BGQ BWQ ECC 6 CRM SRM SCM XI EP

Regression Test
EWR CWR RGR SWR XWR PGR Global Trade Warehouse BW (Global) BW (Local for West) GGR WWR BGR BWR

MDM BW (Global) BW (Local for West) Global Trade Warehouse

Project

XI EP

Business Warehouse (Global and Western Hemisphere) XWD XI XWQ


PGD EP PGQ

Sandbox & Training


ECC 6 CRM EWX CWX SRM SCM

BW Systems are closely linked to ECC instances and will closely follow processes and procedures linked to Man Sol MDM MGQ MDM MGR MDM MGD 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 : MDM MGQ 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
RGX SWX XI EP XWX PGX Global Trade MDM GGX MGX Sol Man BW (Global) BW (Local for West) BW (Global) BW (Local for West) BGX BWX BGT BWT Warehouse

WWX

ECC 6 CRM

EWT CWT

SRM SCM

RGT SWT

XI EP

XWT PGT

Global Trade Warehouse

GGT WWT

SMX

Development
ECC 6 CRM SRM SCM EWF CWF RGF SWF XWF PGF MGF Global Trade Warehouse BW (Global) BW (Local for West) GGF WWF BGF BWF ECC 6 CRM SRM SCM XI EP MDM

Pre-Prod
EWS CWS RGS SWS XWS PGS Global Trade Warehouse BW (Global) BW (Local for West)

Catalyst SAP Implementation


GGS WWS BGS BWS

Support

XI EP MDM

Production
ECC6 EWP CWP KPE SWP XWP PGP MGP BGP BWP GGPF WWP SMP

MGS CRM SRM SCM

SMT

XI EP

Development
Sol Man ECC 6 CRM SRM SCM EWD CWD RGD SWD XWD Global Trade Warehouse BW (Global) BW (Local for West) GGD WWD BGD BWD ECC 6 CRM SRM SCM XI EP MDM

Quality Assurance
EWQ CWQ RGQ SWQ XWQ PGQ MGQ Global Trade Warehouse BW (Global) BW (Local for West) GGQ WWQ BGQ BWQ ECC 6 CRM SRM SCM XI EP MDM

Regression Test
EWR CWR RGR SWR XWR PGR MGR Global Trade Warehouse BW (Global) BW (Local for West) GGR WWR BGR BWR

MDM BW (Global) BW (Local for West) Global Trade Warehouse Sol Man

Project

XI EP MDM

Global Trade Services PGD


MGD

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 MDM MGQ 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


ECC 6 CRM EWX CWX SRM SCM RGX SWX XI EP XWX PGX Global Trade MDM GGX MGX Sol Man BW (Global) BW (Local for West) BW (Global) BW (Local for West) BGX BWX BGT BWT Warehouse Warehouse WWX WWX

ECC 6 CRM

EWT CWT

SRM SCM

RGT SWT

XI EP

XWT PGT

Global Trade Warehouse

GGT WWT

SMX

Development
ECC 6 CRM SRM SCM EWF CWF RGF SWF XWF PGF MGF Global Trade Warehouse BW (Global) BW (Local for West) GGF WWF BGF BWF ECC 6 CRM SRM SCM XI EP MDM

Pre-Prod
EWS CWS RGS SWS XWS PGS Global Trade Warehouse BW (Global) BW (Local for West)

Catalyst SAP Implementation


GGS WWS BGS BWS

Support

XI EP MDM

Production
ECC6 EWP CWP KPE SWP XWP PGP MGP BGP BWP GGPF WWP SMP

MGS CRM SRM SCM

SMT

XI EP

Development
Sol Man ECC 6 CRM SRM SCM EWD CWD RGD SWD XWD PGD MGD Global Trade Warehouse BW (Global) BW (Local for West) GGD WWD BGD BWD ECC 6 CRM SRM SCM XI EP MDM

Quality Assurance
EWQ CWQ RGQ SWQ XWQ PGQ MGQ Global Trade Warehouse BW (Global) BW (Local for West) GGQ WWQ BGQ BWQ ECC 6 CRM SRM SCM XI EP MDM

Regression Test
EWR CWR RGR SWR XWR PGR MGR Global Trade Warehouse BW (Global) BW (Local for West) GGR WWR BGR BWR

MDM BW (Global) BW (Local for West) Global Trade Warehouse Sol Man

Project

XI EP MDM

SAP Warehouse Management The Warehouse management systems are closely linked to ECC instances and will MGQ closely follow processes MDM 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.

Sandbox & Training


ECC 6 CRM EWX CWX SRM SCM RGX SWX XI EP XWX PGX Global Trade MDM GGX MGX Sol Man BW (Global) BW (Local for West) BW (Global) BW (Local for West) BGX BWX BGT BWT Warehouse WWX

ECC 6 CRM

EWT CWT

SRM SCM

RGT SWT

XI EP

XWT PGT

Global Trade Warehouse

GGT WWT

SMX

Development
ECC 6 CRM SRM SCM EWF CWF RGF SWF XWF PGF MGF Global Trade Warehouse BW (Global) BW (Local for West) GGF WWF BGF BWF ECC 6 CRM SRM SCM XI EP MDM

Pre-Prod
EWS CWS RGS SWS XWS PGS Global Trade Warehouse BW (Global) BW (Local for West)

Catalyst SAP Implementation


GGS WWS BGS BWS

Support

XI EP MDM

Production
ECC6 EWP CWP KPE SWP XWP PGP MGP BGP BWP GGPF WWP SMP

MGS CRM SRM SCM

SMT

XI EP

Development
Sol Man ECC 6 CRM SRM SCM EWD CWD RGD SWD XWD PGD MGD Global Trade Warehouse BW (Global) BW (Local for West) GGD WWD BGD BWD ECC 6 CRM SRM SCM XI EP MDM

Quality Assurance
EWQ CWQ RGQ SWQ XWQ PGQ MGQ Global Trade Warehouse BW (Global) BW (Local for West) GGQ WWQ BGQ BWQ ECC 6 CRM SRM SCM XI EP MDM

Regression Test
EWR CWR RGR SWR XWR PGR MGR Global Trade Warehouse BW (Global) BW (Local for West) GGR WWR BGR BWR

MDM BW (Global) BW (Local for West) Global Trade Warehouse Sol Man

Project

XI EP MDM

Solution Manager Solution manager sandbox (SMX) will be used for testing new releases, and other sandbox related prototyping MDM MGQ 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. & Training There will be no transports of application related information between SMT and SMP.BW (Global) All functional andWarehouse EWX SRM RGX XI XWX BGX Global Trade GGX Sol Man Business SCM related changes will beEP made directly in SMP. CWX SWX PGX MDM MGX BW (Local for West) BWX
EWT CWT SRM SCM RGT SWT XI EP XWT PGT Global Trade Warehouse GGT WWT SMX BW (Global) BW (Local for West) BGT BWT

Sandbox
ECC 6 CRM

WWX

ECC 6 CRM

Catalyst SAP Implementation

GLOBAL/WEST SAP SYSTEM LANDSCAPE


PROJECT RELEASE LANDSCAPE
DEVELOPMENT
ECC ECC-WM CRM SRM SCM
LIVE CACHE

PRODUCTION SUPPORT LANDSCAPE


DEVELOPMENT
ECC ECC-WM EWF WWF CWF RGF SWF LWF

PRODUCTION
EWS WWS CWS RGS SWS LWS OPS ECC ECC-WM CRM SRM SCM
LIVE CACHE

QUALITY ASSURANCE
ECC ECC-WM CRM SRM SCM
LIVE CACHE

REGRESSION TEST
ECC ECC-WM CRM SRM SCM
LIVE CACHE

PRE-PRODUCTION
ECC ECC-WM CRM SRM SCM
LIVE CACHE

EWD WWD CWD RGD SWD LWD

EWQ WWQ CWQ RGQ SWQ LWQ

EWR WWR CWR RGR SWR LWR OPQ

EWP WWP CWP KPE SWP LWP OPP XWP BWP TWP PGP BGP MGP GGP PWP AWP BSP DGP SMP GSLD

OPTIMIZER XI/PI BI TREX EP BW-GLOBAL MDM ECC-GTS WebAS-XAPP (PLM)


MOBILE INFRASTRUCTURE

XGD BWD TWD PGD BGD MGD GGD PWD AGD BSD

XI/PI BI TREX EP BW-GLOBAL MDM ECC-GTS WebAS-XAPP (PLM)


MOBILE INFRASTRUCTURE

XGQ BWQ TWQ PGQ BGQ MGQ GGQ PWQ AGQ BSQ

XI/PI BI TREX EP BW-GLOBAL MDM ECC-GTS WebAS-XAPP


MOBILE INFRASTRUCTURE

XWR BWR TWR PGR BGR MGR GGR PWR AWR BSR

C U T O V E R R E L E A S E

CRM SRM SCM


LIVE CACHE

OPTIMIZER XI/PI BI TREX EP BW-GLOBAL MDM ECC-GTS WebAS-XAPP


MOBILE INFRASTRUCTURE

XWF BWF TWF PGF BGF MGF GGF PWF AWF BSF

XI/PI BI TREX EP BW-GLOBAL MDM ECC-GTS WebAS-XAPP


MOBILE INFRASTRUCTURE

XWS BWS TWS PGS BGS MGS GGS PWS AWS BSS DGD SMT

G O L I V E

OPTIMIZER XI/PI BI TREX EP BW-GLOBAL MDM ECC-GTS WebAS-XAPP


MOBILE INFRASTRUCTURE

SEM NWDI SOLUTION MGR

SEM

SEM

SEM

SEM

SEM NWDI SOLUTION MGR


GlobalSystLandDir

ECC ECC-GTS ECC-WM

EWT GGT WWT

WebAS-XAPP (PLM) SRM SCM

PWT RGT SWT

SEM CRM
LIVE CACHE

BST CWT LWT XI/PI EP XWT PGT BW BW-GLOBAL BWT BGT -----TREX --T TWT
MOBILE INFRASTRUCTURE

TRAINING
AGT

FRONT END COMPONENTS TECHNICAL

OPTIMIZER WebAS-XAPP (PLM) SRM SCM

OPT

MDM

MGX

SOLUTION MGR

SMX

ECC ECC-GTS ECC-WM

EWX GGX WWX

PWX RGX SWX

SEM CRM
LIVE CACHE

BSX CWX LWX

XI/PI EP

XGX PGX

BW BW-GLOBAL

BWX BGX

----TREX

--X TWX

MOBILE INFRASTRUCTURE FRONT END COMPONENTS TECHNICAL

AGX

SANDBOX | PROTOTYPE

Catalyst SAP Implementation 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.

Catalyst SAP Implementation


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

Catalyst SAP Implementation


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.

Development

90 Prototype Configuration
800 Security

Catalyst SAP Implementation <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.

Catalyst SAP Implementation <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)

Catalyst SAP Implementation


mySAP Development System

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.

Development 010 Golden

90 Prototype Configuration
800 Security

Catalyst SAP Implementation <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.

Catalyst SAP Implementation <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

Catalyst SAP Implementation


mySAP Development System

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.

Development 010 Golden

90 Prototype Configuration
800 Security

Catalyst SAP Implementation


mySAP Development System

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.

Development 010 Golden

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

100 Unit Test

90 Prototype Configuration
800 Security

Catalyst SAP Implementation <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.

Catalyst SAP Implementation


mySAP Development System

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?!)

Development 010 Golden

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

100 Unit Test

110 Development

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

90 Prototype Configuration
800 Security

X Requires frequent testing during development

Catalyst SAP Implementation <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.

Catalyst SAP Implementation


mySAP Development System

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.

Development 010 Golden

100 Unit Test 110 Development 120 DataConv Unit Test 90 Prototype Configuration
800 Security

Catalyst SAP Implementation 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.

Catalyst SAP Implementation


Additional Clients- SAP ECC Development Client StrategyEWD

EWD
Notes:

Config Master Client 015 Gold Customizing Client 010 Client Refresh / Copy (if required)

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 clientdependent changes only.

Unit Test 100 Development 110 Data Conversion Unit Test 120 Prototyping Client 090 Security Client 800

Catalyst SAP Implementation


Catalyst System/Client Usage ECC Landscape Sandbox & Development

System

System Use

Client

Static or Dynamic Usage * S S S

Client Description /Functional Use Unit Test Gold Master Sandbox Client

Client Refreshed from? N/A N/A 010

Comments

EWD

ECC Development

100 010 090

Transports originate from this client No transport tracking. Periodically refreshed (on demand/schedule) from 010. Security construction client Created from client 010 Refreshed on request from Data Mgmt Team Refreshed on demand from EWD

800 110 120 EWX ECC Sandbox 300

S S D S

Security User Master Development Data Conversion Unit Test Sandbox environment

N/A N/A 100 EWD/010

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

Catalyst SAP Implementation


mySAP Development System

Business Process Teams release their completed configuration by releasing corresponding Configuration Transport Requests. Similarly the Development Team releases its completed work by releasing corresponding Workbench Transport Requests. Released transport requests become ready for import into Quality Assurance Testing System.

Development 010 Golden

100 Unit Test 110 Development 120 Data Conversion Unit 90 Prototype Configuration
800 Security

Catalyst SAP Implementation


<**delete**> SAP R/3 Development Client StrategyEWD

Client
015

Client Name
Configuration Master

Purpose

Description
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.

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.

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.

Catalyst SAP Implementation


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

Catalyst SAP Implementation


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.

Development 010 Golden

Quality Assurance Test


010 Golden

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

100 Unit Test 110 Development 120 Data Conversion Unit 90 Prototype Configuration
800 Security

100 Integration Test 110 Process Test 120 DataConv DryRun Test

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

Catalyst SAP Implementation


mySAP Quality Assurance and Test System

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.

Development 010 Golden

Quality Assurance Test


010 Golden

100 Unit Test 110 Development 120 Data Conversion Unit 90 Prototype Configuration
800 Security

100 Integration Test 110 Process Test 120 DataConv DryRun Test

Catalyst SAP Implementation


mySAP Quality Assurance and Test System

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

Development 010 Golden

Quality Assurance Test


010 Golden

100 Unit Test 110 Development 120 Data Conversion Unit 90 Prototype Configuration
800 Security

100 Integration Test 110 Process Test 120 DataConv DryRun Test

Catalyst SAP Implementation


mySAP Quality Assurance and Test System

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.

Development 010 Golden

Quality Assurance Test


010 Golden

100 Unit Test 110 Development 120 Data Conversion Unit 90 Prototype Configuration
800 Security

100 Integration Test 110 Process Test 120 DataConv DryRun Test

Catalyst SAP Implementation


mySAP Quality Assurance and Test System

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

Development 010 Golden

Quality Assurance Test


010 Golden

100 Unit Test 110 Development 120 Data Conversion Unit 90 Prototype Configuration
800 Security

100 Integration Test 110 Process Test 120 DataConv DryRun Test

Catalyst SAP Implementation


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.

Development 010 Golden

Quality Assurance Test


010 Golden

Training
010 Training Master

100 Unit Test 110 Development 120 Data Conversion Unit 90 Prototype Configuration
800 Security

100 Integration Test 110 Process Test 120 DataConv DryRun Test

Catalyst SAP Implementation


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

Catalyst SAP Implementation


mySAP Training System

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

Development 010 Golden

Quality Assurance Test


010 Golden

Training
010 Training Master

100 Unit Test 110 Development 110 Development 90 Prototype Configuration


800 Security

100 Integration Test 110 Process Test 120 DataConv DryRun Test

710 Class Room 1

720 Class Room 2 :

7n0 Class Room n

Catalyst SAP Implementation


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

System

System Use ECC Training

Client

Static or Dynamic Usage * S

Client Description /Functional Use Training Client Master

Client Refresh from? 015

Comments

EWT

010

Receives transports from EWD/010 on weekly basis. All master & transactional data for training purposes loaded into this client. Receives transports from EWD/010 on weekly basis. Refreshed weekly after transports. Refreshed weekly after transports. Refreshed weekly after transports. Refreshed weekly after transports. Refreshed weekly after transports Sandbox area after formal training. Receives transports from RD1/200

015

Training Client Master Backup Client End User Training Client #1 End User Training Client #2 End User Training Client #3 End User Training Client #4 End User Training Client #5 End User Sandbox Area

N/A

710 720 730 740 750 300

D D D D D D

010 010 010 010 010 N/A

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

Catalyst SAP Implementation


mySAP Regression System

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

Development 010 Golden

Quality Assurance Test


010 Golden

Training
010 Training Master

Regression
010 Regression

100 Unit Test 110 Development 120 Data Conversion Unit 90 Prototype Configuration
800 Security

100 Integration Test 110 Process Test 120 DataConv DryRun Test

Catalyst SAP Implementation


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

System

System Use

Client

Static or Dynamic Usage * S S D D

Client Description /Functional Use Gold Client Integration Test Client Process Step Data Conversion Dry Run Test

Client Refreshed from? N/A N/A 010 010

Comments

EWQ

ECC QA/ Test

010 100 110 120

Receives all transports from EWD 010

Refreshed on request from Data Mgmt Team Refreshed on request from Data Mgmt Team

EWR(V)

Regression Test

010

Cutover Rehearsals; Infrastructure Test

010

Stress/Volume Test Client

EWP

Production

010

Production Client

N/A

Receives all transports from EWD 010

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

Catalyst SAP Implementation


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

Development 010 Golden 200 Unit Test 210 Development


230 Security

Quality Assurance Test


010 Golden

Production
010 Production

200 Integration Test

Catalyst SAP Implementation


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.
Development 010 Golden 200 Unit Test 210 Development
230 Security

Quality Assurance Test


010 Golden

Production
010 Production

200 Integration Test

Development 010 Golden

Quality Assurance Test


010 Golden

Training
010 Training Master

Regression
010 Regression

100 Unit Test 110 Development 120 Data Conversion Unit 90 Prototype Configuration
800 Security

100 Integration Test 110 Process Test 120 DataConv DryRun Test

710 Class Room 1

720 Class Room 2


: 7n0 Class Room n

Catalyst SAP Implementation 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.

Catalyst SAP Implementation


Next Wave Client Strategy for NetWeaver BI

Development

Quality Assurance Test Production


010 Golden 010 Production

010 Golden

BWF

BWS

BWP

Development

Quality Assurance Test


010 Golden

Regression
010 Regression

Training
010 Training Master

010 Golden

BWD Transports

BWQ

BWR

BWT

Catalyst SAP Implementation


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 consuming Naming 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).

ECC

CRM

SCM
Logical System CWDCL010 Logical System CWQCL010

BI
Logical System SWDCL010

CWD CWQ

SWD SWQ

Logical System SWQCL010

CWT
Development
Logical System EWDCL100

Logical System CWTCL700

SWT

Logical System SWTCL700

EWD CWR
Logical System CWRCL010

BWD SWR SWX


Logical System SWRCL010

Logical System BWDCL010

QA/Test

Logical System EWQCL100

EWQ CWX
Logical System CWXCL300

BWQ
Logical System SWXCL300

Logical System BWQCL010

User Training

Logical System EWTCL700

EWT
EWR EWX
ALE / RFC

BWT
BWR BWX

Logical System BWTCL700 Logical System BWRCL010

Regression Technical Sandbox

Logical System EWRCL010

Logical System EWXCL300

Logical System BWXCL300

Catalyst SAP Implementation


Next Wave Client Strategy for NetWeaver CRM

Development

Quality Assurance Test Production


010 Golden 010 Production

010 Golden

CWF

CWS

CWP

Development

Quality Assurance Test


010 Golden

Regression
010 Regression

Training
010 Training Master

010 Golden

CWD Transports

CWQ

CWR

CWT

Catalyst SAP Implementation


Next Wave Client Strategy for NetWeaver SCM

Development

Quality Assurance Test Production


010 Golden 010 Production

010 Golden

SWF

SWS

SWP

Development

Quality Assurance Test


010 Golden

Regression
010 Regression

Training
010 Training Master

010 Golden

SWD Transports

SWQ

SWR

SWT

Catalyst SAP Implementation


Catalyst System/Client Usage Non-ECC Systems
System System Use Client Static or Dynamic Usage * Client Description /Functional Use Client Refresh from? Comments

SWX SWD SWQ SWR

SCM Sandbox SCM Development SCM QA/Test SCM Regression

300 010 010 010

S S S S

Sandbox Development Client QA/Test Client Regression

N/A N/A N/A N/A

SWT
SWF

SCM Training
SCM Production Support

010
010

S
S

End-User Training
Production Fix Dev

N/A
N/A

SWS
SWP CWX CWD CWQ CWR CWT CWF CWS CWP

SCM Production Support


SCM Production CRM Sandbox CRM Development CRM QA/Test CRM Regression CRM Training CRM Production Support CRM Production Support CRM Production

010
010 300 010 010 010 010 010 010 010

S
S S S S S S S S S

Production Fix QA
Production Sandbox Development QA/Test Regression Training Production Fix Dev Production Fix QA Production

N/A
N/A N/A N/A N/A N/A N/A N/A N/A N/A

Catalyst SAP Implementation


Catalyst System/Client Usage Non-ECC Systems
System System Use Client Static or Dynamic Usage * Client Description /Functional Use Client Refresh from? Comments

BWX BWD BWQ BWT BWF BWS BWP

BW Sandbox BW Development BW QA/Test BW Training BW Production Support BW Production Support BW Production

010 010 010 010 010 010 010

S S S S S S S

Sandbox Development QA/Test Training Production Fix Dev Production Fix QA Production

N/A N/A N/A N/A N/A N/A N/A

XGX XGD
XWQ XWT XWF XWS XWP

XI Sandbox XI Development
XI QA/Test/Training XI Training XI Production Support XI Production Support XI Production

010 010
010 010 010 010 010

S S
S S S S S

Sandbox Development
QA/Test XI Training Production Fix Dev Production Fix QA Production

N/A N/A
N/A N/A N/A N/A N/A

Catalyst SAP Implementation 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
is returned to production support organization (---)

Upon completion of migration/consolidation activities, production stream sole ownership

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 Implementation

CATALYST SAP CHANGE MANAGEMENT

KRAFT - Project Team Member

WIP - UNIT TEST GLOBAL DEV

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

VOLUME TESTING / Regression / DEPLOYMENT PRE-PROD

RELEASE TO DEPLOYMENT PRODUCTION SUPPORT LANDSCAPE

Initial Status is O

I RO

OU

KRAFT - Project Team Lead

J RA OA RU
Distribute Transport within The Global Development & ITL (QA) Systems

UAT

VT OP OK C

RQ
Distribute Transport to The Deployment Pre-Production System

KRAFT Transport Management KRAFT SAP Factory / Integration Management / CAB Management KRAFT - CCM

Distribute Transport to The Deployment ITL (QA) System

Distribute Transport to The Deployment Production System

A
CAB

RI

B
CAB

RP

OX
LEGEND

Ticket is Originated

OA

Ticket is approved at the project team lead level

Work in Progress

RU

Work has been UNIT Tested and released to ITL/QA

RO

Work has failed and rework requested

UAT

Work has passed User Acceptance Testing

VT

Work has passed Volume Testing

OP

Work is Approved for Production

OX

Ref. CPR validated for downstream change notification

Ticket is closed

Ticket is closed Work is stopped and any work is undone.

A CAB

Ticket is approved at the Integration Management level for work start

RI

Work has been UNIT Tested and validated for release to ITL/QA

RQ

Work has been Integration tested and approved for delivery to Deployment ITL

RA

Work has been approved for rework

B CAB

Work is approved by the CAB for PreProduction

OU

Work is ready for Production

RP

Work is in Production

OK

Work has been verified and functioning as designed

Catalyst SAP Implementation

CATALYST SAP CHANGE MANAGEMENT WORKFLOW

CSC-100 - Initial Request GD0-100 - Tasks Validated CPR Ticket is created to request work to start at the project level

O
NO

Initial Request Ticket Created to request development work approval

RQ0200 - User Acceptance Test

Transport / Work has passed UNIT Test and is approved for release Global ITL/QA Integration Testing

RI
Ticket Approval

Transports are approved to be released ITL (QA) for Integration Testing

Transport / Work has passed User Acceptance Testing

UAT
FAIL

User acceptance testing has completed and status set to UAT for delivery to the CAB for release approval to PreProduction

RPD200 - GoLive Approval Transports are approved for delivery to Production

OP

Transports are approved for release to production by the Team Lead / Codeset Managers

YES
CSC-100 - Project Approval CPR ticket is approved at the project level

GD0-100 - Tasks Validated

CAB Approval

OA

<<<

Initial CPR Tickets approved for work initiating automatic transport generation on target development systems

Transport / Work has passed UNIT Test and is ready for Integration Testing

RU

Transports are released to ITL (QA) for Integration Testing

PASS
RQ0200 - CAB Approval Transport / Work has been reviewed and verified by the CAB

Distribute Transport to The Deployment Production System Block point release of work is granted by the CAB for delivery to the PreProduction system for Volume Testing.

RP

Transports are moved to production and the release is deployed

NO

YES
CSC-100 - SAP Factory Approval

>>>

Ticket Approval

Distribute Transport within The Global Development & to the ITL (QA) Systems

RPD200 - Production Activation

FAIL
Integration Management reviewed and approved development requests

>>>

PASS
GQ0200 - Integration Testing Transport / Work has passed Integration Test and is ready for distribution to Deployment ITL

<<<

SAP Factory / CAB approval is granted for work to start

INT. TEST

Distribute Transport to The Deployment Pre-Production System

Transport / Work has been successfully imported and activated in Production and is live

OK

Transport work is complete and working in production

FAIL

I
GD0-100/200 - Support Work Starts

Transport / Work is started and prepared for UNIT Test

<<<

Tasks are applied to team members for work to start. Team Members can also transport locally via SCC1 to GD0-200 for validation Validated UNIT Test Transports are sent to Lead and CAB for approval

RQ

<<<

<<<

Transports are approved in ITL (QA) for block point release to Deployment ITL (QA) and User Acceptance Testing

PASS
RPP200 - Volume Testing Transport / Work has passed Volume Testing

>>>

VOL TESTING

VT
Distribute Transport to The Deployment ITL (QA) System

Block Point release work has passed volume testing and is ready for release to production

RPD200 - Production Activation Reference CPR is created for downstream notification of change

OX

Changes are reported back to the respective sustain or enhancement landscapes N-1 -> N N -> N+1

FAIL

Rel To PROD

FAIL
UNIT TEST

FAIL

PASS
UAT TEST RPD200 - Production Activation RPD200 - Production Release Transport / Work has been successfully imported and activated in Production and is live

PASS

<<<

PASS

Transport are approved for release to Production

<<<
GD0100 - Stop Work Transport / Work is stopped and undo process applied for work released GD0100 - Reopen Work Transport / Work is reviewed for rework or undo process GD0100 - Reopen Approval

OU

Transports are set to release to production by team members

Work is done and ticket is closed

YES
Rework?

J RO

Transport / Work is approved for rework and is returned to the initiate work state

NO

RA

Catalyst SAP Implementation


Catalyst Realization Landscape Stage 1

Availability Timeline: Mar 2007 through Apr 2007


ECC
Development

BI

SCM

CRM

SolMan

EWD
010 Golden 100 Unit Tst 110 ABAP 120 Data Ld1

BWD
Client 010

SWD
Client 010

CWD
Client 010

SMT
Client 200

SMP
Client 200

090 ProtoType
800 Security Master

Technical Sandbox

EWX
Client 300

BWX
Client 300

SWX
Client 300

CWX
Client 300

SMX
Client 300

Catalyst SAP Implementation


Catalyst Realization Landscape Stage 2

Availability Timeline: Apr 2007 through June 2007

ECC

BI

SCM

CRM

SolMan

Development

EWD

BWD

SWD

CWD

SMT

QA/Test

EWQ

BWQ BWT BWR

SWQ SWT SWR

CWQ CWT CWR SMP

User Training

EWT
EWR

Regression

Technical Sandbox

EWX

BWX

SWX

CWX

SMX

Catalyst SAP Implementation


Catalyst Realization Landscape Stage 2

Availability Timeline: July 2007 through Go Live and Sustain


ECC BI SCM CRM SolMan

Development QA/Test User Training Regression ProdFix Dev ProdFix QA Production Technical Sandbox

EWD EWQ EWT EWR EWF EWS EWP EWX

BWD BWQ BWT BWR BWF BWS BWP BWX

SWD SWQ SWT SWR SWF SWS SWP SWX

CWD CWQ CWT CWR CWF CWS CWP CWX

SMT

SMP

SMX

Catalyst SAP Implementation


Logical RFC Connections Between Sandbox Systems

Legacy Data Systems

SCM System SWX 010 Solution Mgr SMT 200

Ascential / ItemField/Jcaps Data Transformation Systems

ECC System SWX 100 CRM System CWX 010 BW/ Reporting BWX 010
Legend
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

Catalyst SAP Implementation


Logical RFC Connections Between Development Systems

Legacy Data Systems

SCM System SWD 010 Solution Mgr SMP 200

Ascential Data / ItemField Data Transformation Systems

ECC System EWD 100 CRM System CWD 010 BW/ Reporting BWD 010
Legend
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

Catalyst SAP Implementation Transports

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

A transport migration
an import phase.

can be seen as having two phases: an export and

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

Catalyst SAP Implementation


Transport Management and Client Copy Tool

Development 010 Golden 200 Unit Test 210 Development


230 Security

Quality Assurance Test


010 Golden

Manual Entry

Production
010 Production

Configuration Transports Workbench Transports

200 Integration Test

Client Copy

Development

Quality Assurance Test


010 Golden

Training
010 Training Master

010 Golden 105 Unit Test Ref Mst 100 Unit Test 110 Development

Regression
100 Integration Test 710 Class Room 1 010 Regression

110 Security Test

120 Data Conversion Unit


90 Prototype Configuration
800 Security

720 Class Room 2 :

120 Process Test

7n0 Class Room n

Catalyst SAP Implementation


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.

Catalyst SAP Implementation Transport Organizer (1)

Transport Organizer: Initial Screen


Workbench Customizing

Provides tools for complex system landscapes Enables navigation to:

Request types

Copy transports and relocations


Object list Client transports SAP/partner customer

Selection screens for different transport types Workbench Organizer Customizing Organizer

Any selection screen can be defined as a userspecific default initial screen

Choose

May 2, 2012

Catalyst SAP Implementation Transport Organizer (2)

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

Transports objects without changing location of original object Transports objects making them originals in target system; for temporary relocations Transports objects making them originals in target system; for permanent relocations Used to change the development system of an entire development class

Relocation without development class change:

Relocation with development class change:

Relocation of a complete development class:

May 2, 2012

Catalyst SAP Implementation Transport Organizer (3)

With Object lists, you can:


Display Transport Requests
Object list of user D40BC Modifiable Object List Freely created object list SD programs FI programs

Include object lists from other requests Replace subobjects with complete objects Select objects freely

ZSD-PROGS ZFI-PROGS

May 2, 2012

Catalyst SAP Implementation Transport Organizer (4)

Include objects in request


Object Lists
Change object list Display object list

Is an extension of the former Include template function Is available in all Change and Transport Organizer transactions Allows you to merge the object lists of selected requests into the current request

Lock objects
Sort / compress Obj. directory entries Display object keys Include objects

Include Objects in Request


Object list from request Object list from several requests Freely selected objects

May 2, 2012

Catalyst SAP Implementation


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.

How Transport Management System (TMS) captures Changes?

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.

Catalyst SAP Implementation


How Transport Management System (TMS) captures Changes?

REQUEST

(owned by Functional Lead) TASK 1 TASK 2 TASK 3 (owned by Team Member A) (owned by Team Member B) (owned by Team Member C)

Catalyst SAP Implementation


How Transport Management System (TMS) captures Changes?

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 dont want one transport for each IMG configuration item.

Catalyst SAP Implementation


How Does Customizing Move Between Systems? ECC Configuration Example

EWD EWX
300 Sandbox
1 120 Data Ld1 1) Configurator logs into Sandbox System/ client 300, and performs initial prototype with no change control enabled, OR Can perform initial prototype in EWD Client 090/010. NOTE: All clientindependent changes must be prototyped in EWX 010 Gold Mstr
090 Prototype

100 Unit Test 110 ABAP

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

800 Security Master

2 1) 2) Configurator logs into Sandbox client 090 Performs initial prototype configuration and baseline testing. No change control enabled. No clientindependent changes allowed.

2)

3)

Catalyst SAP Implementation


How Does Customizing Move Between Systems? ECC Configuration Example

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

EWD
100 Unit Test 110 ABAP 120 Data Ld1 010 Gold Mstr 090 Sandbox 800 Security Master 3) 3 1) 2) Configurator Lead logs into Gold Client 010 Lead Opens New Change Request for Customization, and assigns tasks to configuration team members Configurator performs customizing, and saves changes in Task

Catalyst SAP Implementation


How Does Customizing Move Between Systems? ECC Configuration Example

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

EWD
100 Unit Test 110 ABAP 120 Data Ld1 3) 010 Gold Mstr 4) 090 Proto 800 Security Master 4 1) 2) Configurator logs into Unit Test Client 100 Executes Transaction SCC1 and provides Change Request # already created in Client 010 to bring transport into Unit Test Client Perform Unit Test with subset of master and transactional data 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

Catalyst SAP Implementation


How Does Customizing Move Between Systems? ECC Configuration Example

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

EWD
100 Unit Test 110 ABAP 120 Data Ld1 010 Gold Mstr 090 Proto 800 Security Master 5 1) 2) Configurator Lead logs into Gold Client 010 Tasks and transport are released for export

Catalyst SAP Implementation


How Does Customizing Move Between Systems? ECC Configuration Example

EWR EWD
100 Unit Test 110 ABAP 120 Data Ld1 010 Gold Mstr 090 Proto 800 Security Master
010 Regression

EWQ
100 Integration Test

EWT
010 Train Master 701 User Train #1

010 Master Int.


110 Mstr Data Ld1 120 Mst Data Ld2

702 User Train #2


703 User Train #3 704 User Train #4

EWX
300 Sandbox

300 User Sandbox Lab Area

On Demand/Daily Transports Weekly Scheduled/Controlled Transports Weekly Client Refreshes from 200 Master Client after Transports received from RD1 On Demand/scheduled Cross-system client copy/refresh

Catalyst SAP Implementation Transport Requests

Transport requests will be created by the following individuals:


Configuration Activity Create Tranport Request in Dev Business Process Substream Lead Development Activity Delivery Service Substream Lead Basis / Security Activity Basis Team Member

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.
Configuration Activity Approval 1 Release to QA Approval 2 Release to QA Business SubStream Lead Integration / Test Coordinator Development Activity IT Delivery Service Lead Integration / Test Coordinator Basis / Security Activity Support / Security Lead Integration / Test Coordinator

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

Catalyst SAP Implementation


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)

Catalyst SAP Implementation


TMS related FAQs

Importance of Sequence while Transporting


(example)

Server buffer
Request #1 Request #2 independent of other objects program which references ZTEST table

Request #3
Request #4

independent of other objects


table ZTEST definition and structure

Catalyst SAP Implementation


TMS related FAQs

Importance of Sequence while Transporting


(example) Server buffer Request #1 Request #2 Request #3 Request #4 independent of other objects program which references ZTEST table independent of other objects table ZTEST definition and structure

will FAIL the import because it references ZTEST which isnt imported until Request #4!!!

Catalyst SAP Implementation


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.

Catalyst SAP Implementation


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).

Catalyst SAP Implementation

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?

Catalyst SAP Implementation

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 blocks

Benefits
Easier to analyze transport errors Avoids cascading failure effect Easier to manage objects in transports Easier debugging

Catalyst SAP Implementation PROD Approval Process

Production approval process

Configuration Activity

Development Activity

Basis / Security Activity

Approval 1 Release to Prod

Integration / Test Coordinator

Integration / Test Coordinator

Integration / Test Coordinator

Migration Request Created by Integration Approval 2 Release to Prod Business Stream Lead Business Stream Lead Business Stream Lead

Proposed migration to production transport time Saturday evenings

Catalyst SAP Implementation Catalyst Initial Support Flow


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

SAP Installation, SAP GUI, SAP Printing Request

Submit an email to: Call Customer Support:

SAPHelpdesk@kraft.com OR (xxx) xxx-4111, Select SAP Option (3-1) 1-877-xxx-xxxx, Select SAP Option (3-1)

1. Request password reset

Submit an email to: Call Customer Support:

SAPHelpdesk@kraft.com OR

SAP Security Request

2. Request access change 3. Request an SAP user id

SAPHelpdesk@am.sony.com Passwords are synchronized to network ID 1. Request Password Reset

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

1.Check ProdPak/ Training material on website

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

SAP Application Request

2. Consult Super User

Resolved?

No

3. Consult On Site Support if available

Yes

Submit an email to SAPHelpdesk@kraft.com OR Call Customer Support:

Resume Work Activity

Catalyst SAP Implementation Change Management (ITIL Scenario)

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

Registration and Classification

Monitoring and Planning

Approval

Authorization and Implementation

Change Monitoring

Building

Testing

Evaluation / Post Implementation Review

Implementation

Change Management

Program/ Project Management

Catalyst SAP Implementation Processes in Change Request Management

SAP Solution Manager Change Request Management


Change Administration
Management of all change requests Change request categorization Change impact analysis Approval workflow Status reporting Complete change history

Project Management Strategy for Project planning & GROWTH budgeting


Project documentation Business Customizing & Development Ability to (Specifications)

Change Logistics
Customizing & Development (Realization) Test execution Transport scheduling

change

EXECUTE

Transport tracking

Test management

Catalyst SAP Implementation Change Request Management - Roles

Requester

creates an error message or a Change Request directly (e.g. as in idea management) 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.

Change Manager
Change Advisory Board

Developer

Tester

IT Operator

Catalyst SAP Implementation Emergency Correction Process

SAP Solution Manager Change Request Management Change Administration


Problem Message User Change Request Change Manager
Open In process (Rejected) Approved Realized Confirmed

Change Logistics
Task plan Implement correction Release correction Import correction (QAS)

Change Document
Developer

Open In process Realized To be tested Tested Productive Confirmed

Test correction

Tester Operator

Import correction (PRD) Complete task plan

Catalyst SAP Implementation 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

Catalyst SAP Implementation


PROJECT TEAM/HELP DESK/POINT OF CONTACTS PROJECT TEAM

SIR Process: Overview

BASIS TEAM

1
Create SIR in Solution Manager

2
Review and Approve SIR

Review Approved SIR & Move In Process

4
Fix in Development and Unit Test

5
Request Migration

6
Approve Migration

7
Transport

8
Verify Transport

9
Test

10
SIR Fixed? Yes

No

11
Request Production Migration

12
Approve Production Migration

13
Transport

14

Verify Transport Validate Production

15
Notify User of Resolution

SIR = System Investigation Request

Catalyst SAP Implementation Post Cutover Change Control Process for Production Support ECC
EWD EWF
SIR Status New -> Open (email sent to User)

EWQ

EWR

EWS

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?

EWP

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

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: 3. Test:


Document results in SIR Obtain business resource sign off in SIR (see slide 3) Business resource to assess responsibility for S testing
In Test -> Business Sign Off

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

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)

BI

BWF

BWS

BWP

BWD

New Developments Production Support Fix Transports to training environments on case by case basis

BWQ BWR System Copy (Monthly Refresh) BWT

Catalyst SAP Implementation Post Cutover Change Control Process


SCM

SWT

SWD SWD

SWQ

SWR

SWF

SWS

SWP

SIR Status New -> Open (email sent to User)

2. Approve migration to Test:


APO - approvers Code per standards? Need training documents? FD/config documented? Performance? Security? Batch?

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)

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

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
In Test -> Business Sign Off

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)

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

New Developments Production Support Fix Transports to training environments on case by case basis

System Copy (Monthly Refresh)

Catalyst SAP Implementation Post Card Aug 07


Transport Schedule Test Systems 02:00, 05:00, 08:00, 11:00, 15:00, 17:30 EST Production Systems After Batch R3: 1st & 3rd Fridays BW & APO: 1st & 3rd Thursdays Outages PRODUCTION Second & Third Sundays 05:00 09:00 PM EST NON PRODUCTION Second Wednesday 05:00 09:00 AM EST OUTAGE CALENDER Outage Calendar - 2007.DOC

Support / Contact Info Transports / General Support Email: SoarBasisSupport@am.sony.com On Site Support 8:30 AM 5:30 PM EST Remote Support US: 5:30 PM 9:00 PM EST IDC: 9:00 PM 9:00 AM EST BASIS Primary Pager: 888-xxx-0962 Email: 8884680962@skytel.com BASIS Secondary Pager: 877-XXX-XXXX Email: 877XXXXXXX@skytel.com Escalation VVVV Mobile: Email: RRRRR Pager: Email:

Catalyst SAP Implementation CATALYST Production System Legend

Criticality Rating

SAP System Size

Data Flow

High Criticality Medium Criticality Low Criticality


Connected to, but outside of CATALYST
May 2004

one directional

bi-directional

NFS mount

Catalyst SAP Implementation

Catalyst SAP Implementation

Presentation Ends. Rest of the slides TBD

Catalyst SAP Implementation


CATALYST SAP WM System SAP Console

W-LAN
Web Consoles

WAN

LAN

SAP Warehouse Management (WPA) chp433

Warehouses

eupmcchsap37 eupmcchsap38

Core SAP ERP System

EWP

May 2004

Catalyst SAP Implementation CATALYST Production System Integration View Level 1

SAP WM (Catalyst)

Pandora SAP Console

Middle ware
SAP BI

Galaxy

XCOM

ECC

Oracle DW Swift

SCORE

Scheduling

CRM

SCM

PBS/IXOS Archive

Printing (Jetform)

Catalyst SAP Implementation CATALYST Production System View Level 2

E*Gate
(page 04)

SAP Warehouse Management (Catalyst)


(WPA)

Pandora
LAN

SAP Consoles

Galaxy
ALE Data Warehouse

Core SAP ERP System


XCOM
NFS mount

RFC

SAP Business Warehouse (KPW)

Oracle DW Swift

(EWP)
SCORE

Control-M

RFC, rsh

RFC

NFS RFC

SAP Procurement

(???)

PBS Archive

Page Formatting (Jetform)

May 2004

Catalyst SAP Implementation


CATALYST Production EWP SAP System E*Gate

E*Gate

SAP Warehouse Management (Orion)


(WPA)

Pandora SAP Console Radio Frequency


Lotus

Galaxy
ALE Data Warehouse

Core SAP ERP System


XCOM

RFC

SAP Business Warehouse (KPW)

Oracle DW Swift

(EWP)
SCORE

RFC

RFC

Control-M

NFS RFC

SAP Procurement

(KPE)

IXOS Archive

Page Formatting (Jetform)

May 2004

Catalyst SAP Implementation CATALYST Production E*Gate SAP EWP

baut201 (Banbury) StarUk

chp152 laua0313

StarSap

Central

EWP

Benelux

chp143

Nordic chd003 Italy eupmcchlauapp27

Local Systems

EAI KFI P

baut101

Switzerland

Local Systems

StarIberia

StarUk ORACLE XCOM SAP EGATE

May 2004

Catalyst SAP Implementation

GLOBAL/WEST SAP Client Hub Landscape

GLOBAL
SAP SAP SAP -GLOBAL SAP

WEST - NORTH AMERICA


SAP SAP SAP SAP

EAST - EUROPE
SAP SAP SAP

EP
GLOBAL

BW
GLOBAL

-GLOBAL

WM
WEST

CRM
WEST

PLM
WEST

SCM
WEST

ECC*
EAST

SRM
EAST

TREX
EAST

SAP

CLIENT 010/110 CONFIG/ABAP CLIENT 1n0 UNIT TESTS

NWDI
GLOBAL

LIVE CACHE
OPTIMIZER

CLIENT 101 CONFIG/ABAP CLIENT 102-5 UNIT TESTS

SAP

MI-RFID
EAST

SAP SAP SAP SAP SAP

MDM
GLOBAL

CLIENT 100 HUB

SRM
GLOBAL

ECC
WEST

CLIENT 100 HUB

SEM
WEST

SCM
EAST

CLIENT 100 HUB

CLIENT 010/110 CONFIG/ABAP CLIENT 1n0 UNIT TESTS

CLIENT 010/110 CONFIG/ABAP CLIENT 1n0 UNIT TESTS

LIVE CACHE
OPTIMIZER

SAP

SAP

SAP

SAP

SAP

SAP

SAP

SAP

SAP

SAP

PI
GLOBAL

SOLUTION MGR
GLOBAL

-GLOBAL

XMII
WEST

BW
WEST

TREX
WEST

MI-RFID
WEST

BW
EAST

TREX
EAST

XMII
EAST