So over the years and dozens of SAP implementations I have gotten very good at managing and figuring out transports. I am working with an EDI team right now that is promoting a mixed release of objects to production and of course since we are cherry picking functionally in a way that was not originally planned we are having some issues with missing objects and/or transport object sequence. I am not going to explain in the blog how to trouble shoot specific transport issue but point you at a few tricks for figuring out which transports you care about.
So the easiest way to figure the SAP transport that contains your object is by using Version Management when viewing the object in the SAP GUI. Version management can be access from any number of development transactions. I am using SE80.
As you can see in the print screen above. I have a complete history of the changes and transports that captured those changes in version management. But what if I want to look up a list in bulk or want to look at more than just a change to the object by it self.
What if the object is a table and I want to see the change to the table content how would I figure that out?
This is where the table E071 and E070 come into to play.
In the using SE16 and the table E071 I can look up the objects associated with an SAP transport. Lets look at the example above. If I restrict my search by TABD and TABU. I get basically the same list. (technically I am getting the correction request and the the associate task in this view) but what I am looking for is here.
However if I do a less restricted search I can see other object types with the same name and I can also see the transports that contain the table entries for this table as well.
I mentioned table E070 above. Think of this as a header record for E071. Use this table to look at transports within a specific time window or to search by a particular user.
Check back in the future for more useful transport tricks. Feel free to post your own questions or approach as well.