Transport Tracking Made Easier in SAP _ SCN
Post on 07-Feb-2016
Embed Size (px)
Getting Started Newsletters Store
Products Services & Support About SCN Downloads
Industries Training & Education Partnership Developer Center
Lines of Business University Alliances Events & Webinars Innovation
Log On Join UsHi, Guest Search the Community
Activity Communications Actions
0 Tweet 3
This blog will help in understanding the concept of transport request attributes and how it will help in transport
management. This will help in achieving good governance of transport requests in big SAP implementation projects.
Pre-requisite: Basic knowledge of SAP transport request.
Transport requests are used to transfer the changes done to existing objects or new objects created in the
development system to quality and then finally to production system.
Production system has real and confidential data, hence while importing transports to production system transport
requests needs to be verified correctly. Any mistakes in transport list can hamper existing functionality which intern
will cause in change backout and development failure.
The order in which transports should be imported to production needs to be same as per the sequence they were
moved in Quality/Acceptance system.
In big SAP implementation projects which are having more than 100 transport requests created by developer /
functional, there will be more chance of missing transport request in final list of production. If any transport is missed
in the production list, there are several possible risks involved.
Other factors involved are number of developers working on the same project, developers working on the same
objects , transports which are being moved in case of production bug fixes and multiple projects being run in single
Possible risks if transport is missed in the production list:
1. Wrong object versions can go to production: If there are multiple transport requests for one object and one of the
transport requests is missed during production move, then this will lead to incorrect version of the object.
For e.g. for report program ZTEST one transport request AB123 was created and moved from DEV system to
Acceptance system. Later on there was a defect detected in Acceptance testing.
Then to fix this defect again new transport request AB456 was created and moved to Acceptance box. Now while
preparing the production transport list for program ZTEST, latest transport request for defect fix AB456 was missed.
Then incorrect version of program ZTEST will go to production system and same defect which was already fixed
in acceptance testing will remain unfixed as it is.
2. Possibility of RC8 Error during transport movement to production: If any transport of dependent object is missed in
the final list of production movement then transport movement will result in RC8 Error.
E.g. there are 2 transport requests one is for table and another is for data element which is used in table. Both table
and data element are new objects and does not exist in production before transport movement.
Object Type Object Name Transport Request
Data Element ZDTELE AB1234
Table ZTABLE AB5678
Now while preparing final transport list for production movement if transport AB1234 for Data Element ZDTELE is
missed then while moving transport request AB5678 (i.e. for table) RC8 error will occur.
Hence transport movement will end up with error and intern will need analysis on transport failure. Again for missing
transport request separate change management process will be required to move transport to production.
Transport Tracking Made Easier in SAP
Posted by Sanjana Lingras in ABAP Development on Sep 7, 2013 6:17:55 PM
Share 4 2Like
Above mentioned are major risks during production transport movement and may cause HUGE BUSINESS IMPACT.
To avoid such issues because of simple mistakes, good transport management and tracking is needed in projects.
Steps for better transport management and tracking:
o Create custom transport attribute.
o Maintain custom transport attribute for each new transport request for specific development before
releasing it. Hence the entire transport list related to development will have attribute maintained.
o Fetch the list of transports from E070A table where attribute name = custom attribute name.
o This result will give complete list of transport requests for which custom attribute was maintained.
o This will avoid human error of missing any transport request in production transport list.
o Transport attribute maintenance check can be enforced for specific projects. E.g. In development
environment multiple projects are being run and if we want to make transport attribute maintenance
mandatory only for our project then this check can be performed specific to project ID by
implementing method CHECK_BEFORE_RELEASE of BADI CTS_REQUEST_CHECK.
o Once this check is implemented developer/functional will not be able to release transport request
without maintaining transport attribute.
o Hence at the time of production move list of transports for specific development can be fetched from
E070A table where transport attribute value =XXXXXX.
Scenario for how attribute maintenance will help in better management of transports:
In single project there are multiple developments going in parallel. Each development will have separate requirement
specification document with unique number of requirement document.
Below is example:
Project Name: Project1
Now under project1 there are multiple developments executed,
Development Name Requirement Spec. Document number
Now if we create a custom transport attribute ZREQ_DOCNO for maintaining requirement specification document
Then while creating transport requests for development (i.e. DEV1), maintain transport attribute ZREQ_DOCNO =
R1111 (which is req. spec. doc. Number for DEV1).
Now if there are total 40 transport requests were created for DEV1 then list of transports can be fetched from
E070A table where TRANSPORT ATTRIBUTE = ZREQ_DOCNO and ATTRIBUTE VALUE = R1111.
This data fetch from E070A table will give complete list of transports created for DEV1 and there will not be any miss
in transport list.
Also this transport request maintenance can be made mandatory based on project ID by implementing BADI.
Transport attributes creation and BADI implementation is explained in detail further.
How to create Transport Attribute? We can create custom transport Attributes (Z-attribute) for easier project
level transport tracking. This custom transport attribute can be maintained, so that we can find specific
development transports according to custom Transport Attribute values. You can use attributes to define change
requests. Also using these Attribute values, we can perform transport analysis.
Steps for creation of TP Attribute:
1. Go to transaction SE03 (Transport Organizer Tools).Select Display/Change Request Attributes option.
2. 2. Click on Create. New pop-up window will appear.
3. Now enter the respective values for new custom Attribute:
Attribute: Enter the Attribute name for i.e. ZREQ_DOCNO
Short Description: Enter Short description Project1 Transport Attribute.
There are 3 options which need to be selected according to purpose of this attribute:
1. Attribute Value Obligatory: This specifies whether the attribute can only be assigned with a value. If it is
essential that value should be specified for the attribute, then select attribute value obligatory.
2. Attribute Assigned Externally: If this field is selected, the attribute is assigned using external interfaces
only. You can then no longer add this attribute to a request, or delete it from a request. Mostly this option
will not be used as we need to track transport requests in SAP.
3. Attribute can only be assigned once for Each Request: If this field is selected then you can only assign
this attribute once for each transport request.
We can also make these attributes mandatory to specific development client by mentioning client specific
So here we will select option 1 & 3 to create custom attribute: then SAVE.
Now new attribute ZREQ_DOCNO will be available for maintenance through SE01.
How to maintain transport attribute?
1. Go to SE01. Display transport request.
2. Go to properties tab of transport and enable change mode.
3. Attribute ZREQ_DOCNO will be available for maintenance in attribute list.
4. Select the attribute and enter the value for the attribute e.g. If we are creating transport request for DEV1
and requirement document number
for DEV1 is R1111 then we can maintain attribute having same value.
We can define Attribute value such as some unique number for each Development for e.g. Design
Document number will be different for each development. If we maintain transport attribute value R1111
(i.e. Requirement Doc. Number) for all transport requests specific to one of the development i.e. DEV1,
then it will be easier to track all the transport requests related to DEV