Transport Request Check List

Check list - Transport Request release

DOCUMENT HISTORY

REVISION HISTORY

Date Document Version Document Revision Description

Author

08/04/2013 1.0 Draft Jeevan Kumar Pothuru


Check list to be verified before releasing the Transport Request.

1. Maintain the proper naming convention for the Transport Request as per project / client naming

standards ( Highlighted in red colour)

2. Specify the “Project” in the Transport Request as the client / project standards.( Highlighted in

red colour)


3. Make sure the object’s in the Transport Request is saved in correct package as per client / project

standards. ( If the package has to be changed, execute the below program as per screenshot)


4. Perform the consistency check of the Transport Request. To perform this check, display the

Main transport request and perform the below steps as per below screenshots.


5. Perform the syntax check of the objects in the Transport Request.

A. Select the Task of the request


B.


C.

D. Result should be as shown above screenshot. If there are any messages / critical errors, they

should be cleared before TR release. If the errors can’t be handled, specify in Technical

specification why it can’t be handled.

6. Perform Request consistency.



B.

C. Below message should be displayed at the bottom of the screen.

7. Perform Inactive objects checks in Transport Request. If any found, active them and release the

TR.



B.


8. Mention the Transport Request’s in sequence.

A. For Example : Say, Custom table(ZEMP) is saved in TR ESYK900145 , but one of the data

element which is used in that custom table is saved in TR ESYK900142, then in below

sequence the TR should be imported to new system.

ESYK900142

ESYK900145.

B. If any of the already existing custom objects developed by others are being used in your

development, then check whether other custom objects are promoted through the

landscape.

Ex: For Example, in the custom program developed by you, say, ZEMP_DETAILS, (saved in

TR ESYK900155) you are using one include program developed by other, Say,

ZEMP_DECLARATIONS. The TR ESYK900148 which contains include program

“ZEMP_DECLARATIONS” is already released & imported to Quality, but not to production.

So if the program “ZEMP_DETAILS” has to be moved to production i.e. TR ESYK900155 has to

be moved to quality first and then production. When importing the TR ESYK900155 to

quality, it will be imported without errors. But when it is being imported to production, it will

end in error status because in production, the include program “ZEMP_DECELARTIONS” is

not available as TR ESYK900148 is not yet imported to production.

Transport Request Check List

Documents

Transcript of Transport Request Check List