SAP Enterprise Delivery R7 Transport Strategy

Enterprise Delivery
R7 Transport Strategy Enabling Downtime Minimization

SAP Enterprise Delivery R7 Transport Strategy

1. DOCUMENT REVISION HISTORY ............................................................................................. 2 2. TEAM AND LEADERSHIP APPROVALS ................................................................................... 3 2.1 2.2 TEAM ......................................................................................................................................... 3 LEADERSHIP APPROVALS.......................................................................................................... 3

3. OVERVIEW......................................................................................................................................... 4 3.1 3.2 NEW CTS PROJECT FOR MASTER DATA RELATED RICEFS & CONFIG .................................. 4 Steps to Move a Transport to a New CTS Project .................................................................... 4 NEW CTS PROJECT FOR PROD SYNCHS .................................................................................... 6 What is a pure Prod Synch? ..................................................................................................... 6 Has the object been touched by R7? .......................................................................................... 6 3.3 SAP TRANSPORT NAMING STANDARDS...................................................................... 8 EAD Transport Naming Standard ........................................................................................... 8 EBS Transport Naming Standard ............................................................................................ 8 Security Transport Naming Standard ...................................................................................... 9 BW Transport Naming Standard ............................................................................................. 9 3.4 TRANSPORT RECOLLECT ................................................................................................ 11 Transport Cross Reference: ..................................................................................................... 11 4.1 ACTION ITEM SUMMARY.......................................................................................................... 11

1. Document Revision History

Date
6/24/10

Version #
2

Requester
Tasha Bailey

Change Description
Added Transport Naming Standards for EBS and Security

SAP Enterprise Delivery R7 Transport Strategy

2. Team and Leadership Approvals

2.1 Team
Tasha Bailey, Cutover Jason Kurtz, Cutover Suzanne Leonard, Cutover Ramiro Valdivieso, SAP Dev Rob Bogacz, SAP Dev Kevin Flattery, Basis/Infrastructure

2.2 Leadership Approvals

Chris Hendrie, Enterprise Delivery Vivek Sundarajan, R7 Technology Lead Paul Dilorenzo, Basis/Infrastructure Martin Daeufel, Basis/Infrastructure Stephen Hardy, EBS Subodh Chawla, EAD Maura Corcoran, DAS Abdullah Siddiqui, Quality

SAP Enterprise Delivery R7 Transport Strategy

3. OVERVIEW
The following standards support ongoing efforts to minimize system downtime and the associated business disruption and costs. They enable Enterprise Delivery to shorten the migration window and meet business requirements of three to five hour standard outages and twelve hour project outages. NOTE: All screenshots are from D12 but applies to all lower landscape environments

3.1 New CTS Project for Master Data related RICEFs & Config
Move all master data related transports to CTS Project = PR7_MASTER. Bundling these objects into one project allows for early migration (may migrate before technical cutover). This will reduce the overall number of transports migrating during cutover and decrease the downtime window. Master Data Related CTS Project: PR7_MASTER Note: Configuration changes made via Solution Manager are automatically saved to CTS Project = PR7_IMP_1 PepsiCo One Up - Release 7 Implementation Project. To change, log into D12 and follow steps below:

Steps to Move a Transport to a New CTS Project

I. Transaction: SE09 II. Search for transport III. D12K944414 is in Project: PR7_IMP_1: PepsiCo One Up - Release 7 Implementation Project

Double click on Transport Number.

4

SAP Enterprise Delivery R7 Transport Strategy

IV. Navigate to the Properties Tab and select Change Icon

V.

Navigate to Project field, use dropdown to select CTS Project PR7_MASTER and select Save Icon

SAP Enterprise Delivery R7 Transport Strategy

3.2 New CTS Project for Prod Synchs

Save all pure Prod Synch transports in CTS Project = PROD_SYNC. Transports in this CTS Project will not migrate to production during R7 Cutover however they will migrate to UA to ensure availability during regression testing. This will eliminate thousands of transports from reapplying changes that already exist in the production landscape.

What is a pure Prod Synch?

Originates in upper landscape production system Impacts an object that has not been touched by an upcoming release

Has the object been touched by R7?

Option 1: Check Version Management

Double click on Project Number.

If the latest transport is assigned to one of the R7 projects below, it is being touched by R7 and is not a pure prod synch.
PR7_IMP_1 PR7_EARLY PR7_MASTER PepsiCo One Up - Release 7 Implementation Proj Release 7 Early Release Customer Release 7 Master Data
6

SAP Enterprise Delivery R7 Transport Strategy

https://teamwork1.pepsico.com/eRoom/anchor/ProjectOneUpTechConversionCutover/0_91301

For detail and questions on the Prod Sync process, please reach out to the Application Planning Coordinator.

Option 2: Check Custom Inventory Sheets One Up maintains an inventory of custom objects modified for each release. If the object exists in the inventory, it is being touched by R7 and is not a pure prod synch. Eroom Location: https://teamwork1.pepsico.com/eRoom/EnterpriseApplicationDevelopment/EA D-TechArch/0_2307b Filenames: Release 7 SAP Custom Inventory Sheet.xls

SAP Enterprise Delivery R7 Transport Strategy

3.3 SAP TRANSPORT NAMING STANDARDS

Name (rename) all transports to follow the SAP transport naming standards prior to releasing. The analyst that releases the transport is accountable for ensuring transport naming standard is followed. Type identifies transports for migration bundling and will be used to support pull forward/hold back activities.

EAD Transport Naming Standard

<release>_<process area>_<type & FD caliber ID>_<Short description> type RPT INT CON ENH FRM ~ for example, for R7initial migration: R7_OTC_RPT12345_OM_Order header table modifications R7_OTC_INT12345_IM_Order header table modifications R7_OTC_CON12345_DIST_Order header table modifications R7_OTC_ENH12345_FIN_Order header table modifications ~ for example, for R7 defects: R7_OTC_INT12345_OM_Order header table modifications_defect98765 Report Program Interface Program Conversion Enhancement Form (Smart Form, SAPscript Program)

EBS Transport Naming Standard

Initial Migration <release>_<process team>Initial_<Short description> ~ for example: R7_DM_Initial_DSD Logistics Config

Defects <release>_<process team>_<starteam #>_<Short description> ~ for example: R7_DM_ 98765_DSD Logistics Config

SAP Enterprise Delivery R7 Transport Strategy

Security Transport Naming Standard

<team>:SIR <starteam #> <Short description> ~ for example: SEC:SIR 265331 Maintained tcode in SU24

BW Transport Naming Standard

TBD: Follow-up scheduled 6/24/10

SAP Enterprise Delivery R7 Transport Strategy

Steps to Rename a Transport

I. II. III. Transaction: SE09 Search for transport Navigate to the Properties Tab and select Change Icon

IV.

Update Short Description and select Save Icon

10

SAP Enterprise Delivery R7 Transport Strategy

3.4 TRANSPORT RECOLLECT

To reduce the overall number of transports migrating during cutover weekend, Basis will recollect transports into a smaller subset of transports. Mock 1 Mock 2 Mock 3 Cutover Rehearsal Production Cutover All individual transports will migrate to UA1 Mock 1 transports + incremental transports recollected into a smaller subset of transports Mock 2 transports + incremental transports recollected into a smaller subset of transports Mock 3 transports + incremental transports recollected into a smaller subset of transports Cutover Rehearsal transports + incremental transports recollected into a smaller subset of transports

Transport Cross Reference:

Basis will upload the spreadsheets used to build the import queue to eroom. The spreadsheets will store the cross reference between individual transports and recollected transports. https://teamwork1.pepsico.com/eRoom/OneUpFLNA/OneUpRelease7/0_15e90

4.1 Action Item Summary

Move all master data related transports to CTS Project = PR7_MASTER. Save all pure Prod Synch transports in CTS Project = PROD_SYNC. Name (rename) all transports to follow the SAP transport naming standards prior to releasing. For your awareness: Basis will recollect transports into a smaller subset of transports prior to migration.

11