SAP Transport Procedures and Best Practices

Download SAP Transport Procedures and Best Practices

Post on 28-Oct-2014

116 views

Category:

Documents

0 download

Embed Size (px)

TRANSCRIPT

<p>SAP Transport Procedures and Best Practices</p> <p>Applies to:SAP R/3, SAP ECC 6.0 and SAP BW 3.5/SAP BI 7.0. For more information, visit the EDW homepage.</p> <p>SummaryThis article gives an overview of the SAP Transport Procedure (STMS) and the Best Practices which would help in smooth flow of Transports. Author: Vinay Soin</p> <p>Company: Cognizant Services Pvt. Ltd. Created on: 17 August 2011</p> <p>Author BioVinay is currently working with Cognizant as BW Consultant. He has around 6 years of experience in BW. He is involved in various Implementation projects across various clients.</p> <p>SAP COMMUNITY NETWORK 2011 SAP AG</p> <p>SDN - sdn.sap.com | BPX - bpx.sap.com | BA - boc.sap.com | UAC - uac.sap.com 1</p> <p>SAP Transport Procedures and Best Practices</p> <p>Table of ContentsPurpose............................................................................................................................................................... 3 Overview ............................................................................................................................................................. 3 Landscape .......................................................................................................................................................... 3 Packages ............................................................................................................................................................ 3 Change Request ................................................................................................................................................. 4 Creating a task .................................................................................................................................................... 4 Prerequisite ..................................................................................................................................................... 4 Steps. .............................................................................................................................................................. 4 ECC Request Transport Path ............................................................................................................................. 5 BW Transport Path ............................................................................................................................................. 6 Process and Dependencies ............................................................................................................................ 6First Steps .................................................................................................................................................................... 6 Dependencies .............................................................................................................................................................. 6 Sequence ..................................................................................................................................................................... 7</p> <p>Transport Naming Standards.............................................................................................................................. 8 Transporting Procedure ...................................................................................................................................... 9 Build Phase Developments ............................................................................................................................. 9Customizing / Development ......................................................................................................................................... 9</p> <p>Ongoing Development / Fixes ......................................................................................................................... 9 Transport Schedule ....................................................................................................................................... 12 Emergency Transports .................................................................................................................................. 12 Releasing Exporting Transports .................................................................................................................... 12 TMS QA......................................................................................................................................................... 12 Best Practices ................................................................................................................................................... 12 Glossary ............................................................................................................................................................ 13 Related Content ................................................................................................................................................ 14 Disclaimer and Liability Notice .......................................................................................................................... 15</p> <p>SAP COMMUNITY NETWORK 2011 SAP AG</p> <p>SDN - sdn.sap.com | BPX - bpx.sap.com | BA - boc.sap.com | UAC - uac.sap.com 2</p> <p>SAP Transport Procedures and Best Practices</p> <p>PurposeThe purpose of this document is to describe the transport policy, procedures and best practices. This document will provide a detailed approach on the transport strategy.</p> <p>OverviewThis document covers the transport procedure for ECC and BW. SAP provides the necessary mechanisms and tools for supporting this strategy such as the SAP Transport Management System (STMS). This is a SAP designed tool to ensure that data and objects are migrated correctly and are accurately tracked from system to system and client to client</p> <p>LandscapeFor each SAP component we will have a system landscape, Development, Assembly/Product Test, UAT and Production. Developments will be made in the Development environments. Initial assembly and product testing will commence in QA1. Later testing phases take place in QA2. Cutover testing, (pre) Production testing and eventually go-live will take place in Production.</p> <p>Configuration customizing and ABAP development objects will be transported through the systems from Development, QA1, QA2 and onto Production.</p> <p>Development</p> <p>String QA1</p> <p>QA2 QA</p> <p>Production</p> <p>Figure 1 : Basic Transport Path through the system landscape</p> <p>All customization and developments occur in the Development systems. The majority will be transported to QA1, QA2 and Production systems. The transports are managed by SAPs Transport Management System (TMS).</p> <p>PackagesPackages contain a group of development objects that are logically related that is, objects that must be developed, maintained, and transported together. It allows the easy creation of a transport with all the elements included in it. a. BW Objects are created as local objects (non-transportable) and by default are saved in the development class $TMP. As we will be migrating newly created BW Objects, it is imperative that ALL BW Objects be transportable, hence they cannot be saved under the default development class. Rather, all transportable objects are to be saved under Z development classes that (e.g., ZDEV). Or other classes as maintained by the projects. Example: $TMP is used for local objects, and is non transportable. Z packages are used to capture all development objects and enable transport to the next system environment (DEV to QA1 and then to QA2 and PROD)</p> <p>All objects that are to be transported MUST BE SAVED using a Z package.</p> <p>SAP COMMUNITY NETWORK 2011 SAP AG</p> <p>SDN - sdn.sap.com | BPX - bpx.sap.com | BA - boc.sap.com | UAC - uac.sap.com 3</p> <p>SAP Transport Procedures and Best Practices</p> <p>Change RequestStandard SAP tools will be used to manage the change and transport process between environments. The standard SAP Change and Transport System (CTS) mechanism called SAP Transport Change Request (SAP CR) is used to manage recording, documenting and transporting changes throughout the SAP system landscape. All changes in the implementation process are recorded to change requests. The change requests once released are exported into the SAP transports. Changes should be unit tested in Development system before being released from the Dev environment. Steps 1. 2. 3. 4. 5. 6. 7. Change Request is created in the respective clients (ECC DEV and BW DEV). Login to clients ECC DEV and BW DEV. Transaction SE10. Select create request and decide if it is a customizing or workbench request. Enter a short description for the request and use the naming conventions in section 9. Add users to the tasks. Save the request</p> <p>The Delegate has to notify the developer / configurator in the team Result Request is created in the clients ECC DEV/100 and BW DEV/100</p> <p>Creating a taskPrerequisite Configuration / development request has to be created in clients ECC DEV and BW DEV Change Request has been created and user has been assigned. Steps When users start build, they can assign their work to transportable requests. It is important that users assign their work to the correct Change Request as it is possible to have many for a single user. So when a user begins development/customization and is asked to assign work to a transportable request, the user should select one of their own requests.</p> <p>SAP COMMUNITY NETWORK 2011 SAP AG</p> <p>SDN - sdn.sap.com | BPX - bpx.sap.com | BA - boc.sap.com | UAC - uac.sap.com 4</p> <p>SAP Transport Procedures and Best Practices</p> <p>1. Once they have completed the discrete piece of work, the user should unit test to ensure accuracy. 2. The task would be documented. This will be invaluable whenever there are problems with transports between clients. This can be achieved in transaction SE10. Double click the task and then click the Documentation Tab. 3. Release the task. In SE10, click on the task and press F9 or click on the truck icon.</p> <p>ECC Request Transport PathClient 100 in DEV is used for development (ABAP) and customizing and should not contain any application data (just configuration/customizations) Transport flow (after releasing change request in DEV client 100): 1. QA1 client 100 2. QA2 client 100 3. PROD client 100</p> <p>The following figure below shows the transport path for both ECC.</p> <p>ECC - Customizing/Developments R/3 Development PSV Routes100 Gold Develop Development &amp; Customise</p> <p>120 Unit Test</p> <p>130</p> <p>140 Sandbo x</p> <p>Assembly Test</p> <p>100 Assembly Testing</p> <p>100</p> <p>UAT</p> <p>UAT</p> <p>Transport route to QA1 100</p> <p>Production</p> <p>Production</p> <p>Transport route to QA2 Transport route to Production</p> <p>Figure 2 : ECC Transport Path</p> <p>SAP COMMUNITY NETWORK 2011 SAP AG</p> <p>SDN - sdn.sap.com | BPX - bpx.sap.com | BA - boc.sap.com | UAC - uac.sap.com 5</p> <p>SAP Transport Procedures and Best Practices</p> <p>BW Transport PathThe following figure below shows the transport path for BI.</p> <p>BW Clients/Instances - Customizing/Developments Routes R/3 Development PSV100 100 Gold Develop Development &amp; Customise 140</p> <p>Assembly Test</p> <p>100 Assembly Testing</p> <p>UAT</p> <p>100 UAT</p> <p>Transport route to QA1</p> <p>Production</p> <p>100 Production</p> <p>Transport route to QA2 Transport route to Production</p> <p>Figure 3 : BW Transport Path</p> <p>Process and Dependencies First Steps The first step in transporting BW Objects is the successful transportation of all necessary ECC Objects that reference the BW Object. Example: The 0FIAA_C04 InfoCube uses three DataSources, one of which is 0FI_AA_O01. In order for the BW transport from DEV to TEST to successfully take place, ensure that the ECC DataSource 0FI_AA_O01 was successfully transported in QA1. If not, then associated transports will fail in BW. Dependencies The issue of dependency for a transport is paramount. If there are three transports, A, B and C, B is dependent upon A, then A must be successful and active in the new environment; otherwise the transport for B will fail. If C is not dependent on NEITHER A or B, then C is considered non-dependent, and can be transported regardless if the transports for A or B fails.</p> <p>SAP COMMUNITY NETWORK 2011 SAP AG</p> <p>SDN - sdn.sap.com | BPX - bpx.sap.com | BA - boc.sap.com | UAC - uac.sap.com 6</p> <p>SAP Transport Procedures and Best Practices</p> <p>Sequence The sequence in which a transport is to take place is extremely important. The mechanism for a transport can not deviate; else the transport will fail, and cause the subsequent transports for that particular InfoCube to fail as well. The order of battle for the transport release queue is defined below. a. All ECC components, User Exits, Programs, etc b. BW components (Import Execution Order) Info Area Info Object Catalog Info Objects c. Info Providers: Which is composed of these elements: Info Cubes Multi Providers Info Sets Data Store Objects Info Cube Aggregates</p> <p>d. Rules: which contains of: Application Components Communication Structure Data Source replica Info Packages Transfer Rules Transformations Info Source Transaction data Transfer Structure Data sources (Active version) Routines &amp; BW Formulas used in the Transfer routines Extract Structures Update Rules, which may have: o Routines associated with them. DTPs e. Process Chains: Process Chains Process Chain Starter Process Variants Events f. Reports/Queries which are made up of a combination of: Variables Calculated Key Figures/Formula Restricted Key Figures Structures Query Work Books Web Templates</p> <p>SAP COMMUNITY NETWORK 2011 SAP AG</p> <p>SDN - sdn.sap.com | BPX - bpx.sap.com | BA - boc.sap.com | UAC - uac.sap.com 7</p> <p>SAP Transport Procedures and Best Practices</p> <p>Transport Naming StandardsDepending on organizations the naming conventions for the Transports vary. For example the naming convention followed for reference is as below: ::::</p> <p> (work phase): 1 For example: 0 Application Component 1 InfoObjects</p> <p>: For Example: FI Finance, HR HR, PS Projects, PP Procurement, BI Reporting, SE SEM, BA Basis AB ABAP (if not assign to any of the above teams);</p> <p>: CU customizing/configuration WO ABAP/Workbench</p> <p>: Subsequent numbers which can be used if change request will need to be re-transported. 1, 2, 3 ..</p> <p>Example: 1:HR:CU:1: Address Details configuration 1:FI:WO:1: Account Details - ABAP The identifier indicates if a change request is a fix to a tested and rejected change request. For example if a CR has been assembly tested in QA1 and requires adjustments then the change request has to be rejected in the QA1 and the work has to be redone in the DEV system. A new CR is created and all objects from the rejected CR should be added to the new CR (automatic process; there is a process to specify the change request number to copy from) and the new task is created to do the required fix. If the fix is the first one, the identifier will be incremented by 1, therefore the identifier...</p>