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 Us Hi, Guest Search the Community Activity Communications Actions Brow se ABAP Development 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. Introduction 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 environment. 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 2 Like
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
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
Brow se
ABAP Development
Previous
post
Next
post
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.
Introduction
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
environment.
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
Nice Blog with a lot of things not knowen to me. Looking at transports i always ask myself why are so few people are working with tasks? This wouldeliminate things like domains and tables in different transports. If the domain transport is forgotten,you will get an import error, but if those transports are go in in wrong order you wil have an importerror as well.
Sanjana Lingras Sep 10, 2013 2:25 AM (in response to Rainer Hübenthal)
Hi Rainer,Thanks for your feedback. Once you get the complete transport number list, we can check table E070 in Quality system. We need to sort TP numbers by date and timein E070 table.Then this same sequence can be referred for production move which will not have RC8errors in production.
Like (0)
Rainer Hübenthal Sep 10, 2013 7:50 AM (in response to Sanjana Lingras)
Well even with this you are not sure if sorting by timestamp is the correct order. Wehave a third party tool in place to achieve a proper import, but still people arefighting against the rules and produce import errors instead of just talking aboutdependant objects and let th tp do the job to decide in wich sequence objectsneeds to be imported.
Like (0)
Rahul Saroha Sep 10, 2013 8:49 AM
Simple but Detailed blog!!! keep it up....!
Like (0)
Edw in Vleeshouw ers Sep 12, 2013 9:52 AM
I do have some concerns regarding the benefit of using a Transport attribute... Even if all transports are selected that belong to a certain development (a certain group), the objectsIN the transport(s) may still have been modified for other requirements. And by other developers. The versions of these objects might still be missed. To check all dependencies (previous or later),you will need to check all the objects in the transports and find transport requests they are in,regardless of any 'group' they belong to (i.e. project, attribute, description, etc). Also, even if an attribute has been set, a developer may still move the transport with completedisregard of other versions in Acceptance (or as an emergency transport).
Like (0)
Pradip Nikam Sep 18, 2013 6:45 AM
Very Good Blog.. providing detailed insight of Transport Management...!!!
Like (0)
Ramesh T Sep 18, 2013 6:55 AM
Nice document..... Regards,Ramesh.T
Like (0)
Ragavan Nagarajan Sep 18, 2013 6:59 AM
Excellent Blog. Thanks for sharing such an informative article. Great Work buddy. -Regards,Ragavan
Like (0)
abilash n Sep 21, 2013 3:57 PM
Hi Sanjana, Excellent Blog. This shows how much in depth knowledge you possess in Transport Requests.Never expected that this is available.
Like (0)
Satyabrata Sahoo Sep 21, 2013 5:00 PM
Informative. Thanks for sharing.
Like (0)
Sanjana Lingras Sep 23, 2013 8:26 PM
Thanks all for valuable comments !! This is my first blog.
Thanks a lot for sharing this Well expalined in detail. Thanks,Priyanka
Like (0)
Bhavani Prasad Sep 25, 2013 2:06 AM
Good work!. Please keep it up. ThanksBhavani Prasad
Like (0)
Lucas Tétreault Sep 26, 2013 5:01 PM
Check out transaction: SPRO_ADMIN to create a project. Then go to SE03 -> Display/Change Request Attributes and set SAP_CTS_PROJECT toMandatory/Obligatory. Now every transport must be assigned to a project. You can get the list of requests in the
SPRO_ADMIN transaction. Much easier than the solution you are proposing
Like (0)
Glenn Michaels Sep 3, 2014 3:49 PM (in response to Lucas Tétreault)
I Agree with your comments and that is used here. Our challenge is having projects with long lead times & other projects with shorter leadtimes and the risk of shorter project could grab an object that was already released to Q fora larger project. & if the shorter project goes to PRD 1st it would take that object with it. How to manage transports from Q to PRD, we need a program to see if there transports inQ not yet moved to PRD with the same object. This is with a Dev > Q > Prd landscape.
Like (0)
Rainer Hübenthal Sep 3, 2014 3:55 PM (in response to Glenn Michaels)
You can buy such a program from Revelation Software concepts. As far as i knowyou can achieve this via the solution manager, too.
Like (0)
solen dogan Oct 1, 2013 10:53 AM
I havent tried the attribute but certainly gives you a good way to eliminate the missing transportsissue cheers mate
Like (0)
Mohammed Jaffer Oct 11, 2013 11:52 AM
Very good blog. Thanks for sharing.
Like (0)
DIVAKAR CHOUDHURY Oct 15, 2013 9:57 AM
very nice document............
Kiran K Sep 3, 2014 4:26 PM (in response to DIVAKAR CHOUDHURY)
Thanks for sharing this.Now SAP has got ChaRm a tool to manage transports. Frankly speaking,even then at the end of the day making the Developers of the concerneddevelopments responsible for better management of their transports is the best way.If weuse INCLUDE OBJECTS concept in a TR that solves most the problems in Transport