6\VWHP $GPLQLVWUDWLRQ 0DGH (DV\

Chapter 17: Change ManagementTransporting ObjectsThis section describes the standard transport process from your development system toyour production system.The following steps are part of your company’s change management process:1. Obtain proper authorization to transport the objects.Obtaining this authorization is the responsibility of the person who requests thetransport move. The required authorizations and approval process differ based on thecompany. Some companies require the approval of only one person, while othercompanies require the approval of numerous people.A major purpose of the approval process is to give other functional groups a “heads up”as to what you are moving.If the move affects any of the functional groups, and they know about it, they can takethe appropriate action: review, test, etc. If necessary, your transport is delayed until theaffected functional groups are satisfied. This way, there will not be problems related toyour transport.2. Define other necessary transport management related information, such as: Who to contact in case of problemsThe person doing the transport typically is not a programmer. If there is a problemwith the transport, that person will need assistance to determine what failed. What recovery process to follow if the transport fails Who will test the transport in the target system to determine that it works asintended The transport number The source system The target system(s) Relationship to other transports, such as sequence order, etc.For more information, see chapter 12.3. Use transactions SE01, SE09, or SE10 as necessary to release the transport.First release the task, then release the request (or transport).The TMS (normal) import and one of the OS import options, tp import all, willimport all transports in the import buffer. The assumption is that all objects releasedinto the import buffer have been tested and approved for transport into the targetsystem. If you use either method, it is important to not release the objects until they havebeen tested and approved for transport.Up to, and including Release 4.5, in a three-system landscape, once the transport isimported into the quality assurance system, it is added into the production systemimport buffer, and there is no “second release” out of the quality assurance system.4. Import the request into the target system.System Administration Made Easy17–17