Professional Documents
Culture Documents
Transport Strategy - Standards - Proj Etc 1
Transport Strategy - Standards - Proj Etc 1
Enterprise Delivery
R7 Transport Strategy Enabling Downtime Minimization
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
Version #
2
Requester
Tasha Bailey
Change Description
Added Transport Naming Standards for EBS and Security
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:
V.
Navigate to Project field, use dropdown to select CTS Project PR7_MASTER and select Save Icon
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
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
Defects <release>_<process team>_<starteam #>_<Short description> ~ for example: R7_DM_ 98765_DSD Logistics Config
IV.
10
11