Professional Documents
Culture Documents
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
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
Three-tier Environment
End Users
Web AS 1
Web AS 2
Web AS 3
Web AS n
Database Server
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
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
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.
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
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
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
BI (Local for West) BWD SEM TREX xAPP BSD TWD ---
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
Sol Man
SMX
ECC 6 CRM
EWT CWT
SRM SCM
RGT SWT
XI EP
XWT PGT
GGT WWT
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)
Support
XI EP MDM
Production
ECC6 EWP CWP KPE SWP XWP PGP MGP BGP BWP GGPF WWP SMP
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
ECC 6 CRM
EWT CWT
SRM SCM
RGT SWT
XI EP
XWT PGT
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)
Support
XI EP MDM
Production
ECC6 EWP CWP KPE SWP XWP PGP MGP BGP BWP GGPF WWP SMP
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
ECC 6 CRM
EWT CWT
SRM SCM
RGT SWT
XI EP
XWT PGT
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)
Support
XI EP MDM
Production
ECC6 EWP CWP KPE SWP XWP PGP MGP BGP BWP GGPF WWP SMP
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
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
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)
Support
XI EP MDM
Production
ECC6 EWP CWP KPE SWP XWP PGP MGP BGP BWP GGPF WWP SMP
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
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
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)
Support
XI EP MDM
Production
ECC6 EWP CWP KPE SWP XWP PGP MGP BGP BWP GGPF WWP SMP
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
GGX MGX
Sol Man
Warehouse
WWX
ECC 6 CRM
EWT CWT
SRM SCM
RGT SWT
XI EP
XWT PGT
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)
Support
XI EP MDM
Production
ECC6 EWP CWP KPE SWP XWP PGP MGP BGP BWP GGPF WWP SMP
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
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)
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)
ECC 6 CRM
EWT CWT
SRM SCM
RGT SWT
XI EP
XWT PGT
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)
Support
XI EP MDM
Production
ECC6 EWP CWP KPE SWP XWP PGP MGP BGP BWP GGPF WWP SMP
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
Project
XI EP
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
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)
Support
XI EP MDM
Production
ECC6 EWP CWP KPE SWP XWP PGP MGP BGP BWP GGPF WWP SMP
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
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.
ECC 6 CRM
EWT CWT
SRM SCM
RGT SWT
XI EP
XWT PGT
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)
Support
XI EP MDM
Production
ECC6 EWP CWP KPE SWP XWP PGP MGP BGP BWP GGPF WWP SMP
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.
ECC 6 CRM
EWT CWT
SRM SCM
RGT SWT
XI EP
XWT PGT
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)
Support
XI EP MDM
Production
ECC6 EWP CWP KPE SWP XWP PGP MGP BGP BWP GGPF WWP SMP
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
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
EWP WWP CWP KPE SWP LWP OPP XWP BWP TWP PGP BGP MGP GGP PWP AWP BSP DGP SMP GSLD
XGD BWD TWD PGD BGD MGD GGD PWD AGD BSD
XGQ BWQ TWQ PGQ BGQ MGQ GGQ PWQ AGQ BSQ
XWR BWR TWR PGR BGR MGR GGR PWR AWR BSR
C U T O V E R R E L E A S E
XWF BWF TWF PGF BGF MGF GGF PWF AWF BSF
XWS BWS TWS PGS BGS MGS GGS PWS AWS BSS DGD SMT
G O L I V E
SEM
SEM
SEM
SEM
SEM CRM
LIVE CACHE
BST CWT LWT XI/PI EP XWT PGT BW BW-GLOBAL BWT BGT -----TREX --T TWT
MOBILE INFRASTRUCTURE
TRAINING
AGT
OPT
MDM
MGX
SOLUTION MGR
SMX
SEM CRM
LIVE CACHE
XI/PI EP
XGX PGX
BW BW-GLOBAL
BWX BGX
----TREX
--X TWX
AGX
SANDBOX | PROTOTYPE
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.
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
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
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.
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)
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.
90 Prototype Configuration
800 Security
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
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.
90 Prototype Configuration
800 Security
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.
90 Prototype Configuration
800 Security
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.
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
Development work
X Is iterative and can not be grouped and entered from start to finish
90 Prototype Configuration
800 Security
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.
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.
100 Unit Test 110 Development 120 DataConv Unit Test 90 Prototype Configuration
800 Security
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.
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
System
System Use
Client
Client Description /Functional Use Unit Test Gold Master Sandbox Client
Comments
EWD
ECC Development
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
S S D S
Security User Master Development Data Conversion Unit Test Sandbox environment
* Static use = functional use of client is consistent, Dynamic = functional use may change
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.
100 Unit Test 110 Development 120 Data Conversion Unit 90 Prototype Configuration
800 Security
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
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.
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
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
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
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.
100 Unit Test 110 Development 120 Data Conversion Unit 90 Prototype Configuration
800 Security
100 Integration Test 110 Process Test 120 DataConv DryRun Test
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
100 Unit Test 110 Development 120 Data Conversion Unit 90 Prototype Configuration
800 Security
100 Integration Test 110 Process Test 120 DataConv DryRun Test
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.
100 Unit Test 110 Development 120 Data Conversion Unit 90 Prototype Configuration
800 Security
100 Integration Test 110 Process Test 120 DataConv DryRun Test
Successfully integration tested Configuration Transport Requests and Workbench Transport Requests are approved for import into Training and Regression System.
100 Unit Test 110 Development 120 Data Conversion Unit 90 Prototype Configuration
800 Security
100 Integration Test 110 Process Test 120 DataConv DryRun Test
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.
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
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
For end user training, demonstrations, walkthroughs, etc. various Class Room clients are created via client copy of the Training Master client.
Training
010 Training Master
100 Integration Test 110 Process Test 120 DataConv DryRun Test
System
Client
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
D D D D D D
* Static use = functional use of client is consistent, Dynamic = functional use may change
Approved Configuration Transport Requests and Workbench Transport Requests are imported into Regression client based on Regression Testing requirements.
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
System
System Use
Client
Client Description /Functional Use Gold Client Integration Test Client Process Step Data Conversion Dry Run Test
Comments
EWQ
Refreshed on request from Data Mgmt Team Refreshed on request from Data Mgmt Team
EWR(V)
Regression Test
010
010
EWP
Production
010
Production Client
N/A
* Static use = functional use of client is consistent, Dynamic = functional use may change
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
Production
010 Production
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
Production
010 Production
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
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.
Development
010 Golden
BWF
BWS
BWP
Development
Regression
010 Regression
Training
010 Training Master
010 Golden
BWD Transports
BWQ
BWR
BWT
ECC
CRM
SCM
Logical System CWDCL010 Logical System CWQCL010
BI
Logical System SWDCL010
CWD CWQ
SWD SWQ
CWT
Development
Logical System EWDCL100
SWT
EWD CWR
Logical System CWRCL010
QA/Test
EWQ CWX
Logical System CWXCL300
BWQ
Logical System SWXCL300
User Training
EWT
EWR EWX
ALE / RFC
BWT
BWR BWX
Development
010 Golden
CWF
CWS
CWP
Development
Regression
010 Regression
Training
010 Training Master
010 Golden
CWD Transports
CWQ
CWR
CWT
Development
010 Golden
SWF
SWS
SWP
Development
Regression
010 Regression
Training
010 Training Master
010 Golden
SWD Transports
SWQ
SWR
SWT
S S S S
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
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
S S S S S S S
Sandbox Development QA/Test Training Production Fix Dev Production Fix QA Production
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
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.
Production Support Resources and Program Migration Coordinator must be involved to ensure successful consolidation
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
Initial Status is O
I RO
OU
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
A
CAB
RI
B
CAB
RP
OX
LEGEND
Ticket is Originated
OA
Work in Progress
RU
RO
UAT
VT
OP
OX
Ticket is closed
A CAB
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
B CAB
OU
RP
Work is in Production
OK
CSC-100 - Initial Request GD0-100 - Tasks Validated CPR Ticket is created to request work to start at the project level
O
NO
Transport / Work has passed UNIT Test and is approved for release Global ITL/QA Integration Testing
RI
Ticket Approval
UAT
FAIL
User acceptance testing has completed and status set to UAT for delivery to the CAB for release approval to PreProduction
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
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
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
NO
YES
CSC-100 - SAP Factory Approval
>>>
Ticket Approval
Distribute Transport within The Global Development & to the ITL (QA) Systems
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
<<<
INT. TEST
Transport / Work has been successfully imported and activated in Production and is live
OK
FAIL
I
GD0-100/200 - Support Work Starts
<<<
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
<<<
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
YES
Rework?
J RO
Transport / Work is approved for rework and is returned to the initiate work state
NO
RA
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
ECC
BI
SCM
CRM
SolMan
Development
EWD
BWD
SWD
CWD
SMT
QA/Test
EWQ
User Training
EWT
EWR
Regression
Technical Sandbox
EWX
BWX
SWX
CWX
SMX
Development QA/Test User Training Regression ProdFix Dev ProdFix QA Production Technical Sandbox
SMT
SMP
SMX
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
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
Transports are a mechanism for migrating SAP ABAP based objects from one
environment / client to the next.
A transport migration
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
Manual Entry
Production
010 Production
Client Copy
Development
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
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.
Request types
Selection screens for different transport types Workbench Organizer Customizing Organizer
Choose
May 2, 2012
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
May 2, 2012
Include object lists from other requests Replace subobjects with complete objects Select objects freely
ZSD-PROGS ZFI-PROGS
May 2, 2012
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
May 2, 2012
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 TASK 2 TASK 3 (owned by Team Member A) (owned by Team Member B) (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.
When the configuration teams get started in their configuration activities, they
will be picking from the list of tasks that are assigned to them.
stream. Not all work is going to be done in one transport yet we dont want one transport for each IMG configuration item.
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
Tip: Open separate login sessions for each client, to facilitate work
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)
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
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
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
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
EWX
300 Sandbox
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
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
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)
Server buffer
Request #1 Request #2 independent of other objects program which references ZTEST table
Request #3
Request #4
will FAIL the import because it references ZTEST which isnt imported until Request #4!!!
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.
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).
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
Configuration Activity
Development Activity
Migration Request Created by Integration Approval 2 Release to Prod Business Stream Lead Business Stream Lead Business Stream Lead
SAPHelpdesk@kraft.com OR (xxx) xxx-4111, Select SAP Option (3-1) 1-877-xxx-xxxx, Select SAP Option (3-1)
SAPHelpdesk@kraft.com OR
Link: http://catalyst.intranet.kraft.com/Training/indexr.asp
Resolved?
No
Yes
The objective of change management is to carry out changes economically and in a timely manner with minimal risk
Approval
Change Monitoring
Building
Testing
Implementation
Change Management
Change Logistics
Customizing & Development (Realization) Test execution Transport scheduling
change
EXECUTE
Transport tracking
Test management
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
Change Logistics
Task plan Implement correction Release correction Import correction (QAS)
Change Document
Developer
Test correction
Tester Operator
BASIS TEAM
1
Create SIR in Solution Manager
2
Review and Approve SIR
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
15
Notify User of Resolution
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
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
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
SWT
SWD SWD
SWQ
SWR
SWF
SWS
SWP
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
New Developments Production Support Fix Transports to training environments on case by case basis
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:
Criticality Rating
Data Flow
one directional
bi-directional
NFS mount
W-LAN
Web Consoles
WAN
LAN
Warehouses
eupmcchsap37 eupmcchsap38
EWP
May 2004
SAP WM (Catalyst)
Middle ware
SAP BI
Galaxy
XCOM
ECC
Oracle DW Swift
SCORE
Scheduling
CRM
SCM
PBS/IXOS Archive
Printing (Jetform)
E*Gate
(page 04)
Pandora
LAN
SAP Consoles
Galaxy
ALE Data Warehouse
RFC
Oracle DW Swift
(EWP)
SCORE
Control-M
RFC, rsh
RFC
NFS RFC
SAP Procurement
(???)
PBS Archive
May 2004
E*Gate
Galaxy
ALE Data Warehouse
RFC
Oracle DW Swift
(EWP)
SCORE
RFC
RFC
Control-M
NFS RFC
SAP Procurement
(KPE)
IXOS Archive
May 2004
chp152 laua0313
StarSap
Central
EWP
Benelux
chp143
Local Systems
EAI KFI P
baut101
Switzerland
Local Systems
StarIberia
May 2004
GLOBAL
SAP SAP SAP -GLOBAL 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
NWDI
GLOBAL
LIVE CACHE
OPTIMIZER
SAP
MI-RFID
EAST
MDM
GLOBAL
SRM
GLOBAL
ECC
WEST
SEM
WEST
SCM
EAST
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