We take advantage of ABAP Test Cockpit in order to optimize our ABAP programs and other objects. We know that ATC can be done via SE80 with right clicking object and Check->ATC with option menu path. However if we want to control objects under a transport request and we dont want to check each object if there are many objects under the transport request, there are two alternatives for executing an ATC check over a transport request.
You may have seen requests with icon on request description and wonder how to make this. This feature arise from the fact that WRITE command forms the related icon when it meets an @ character in ABAP code. Therefore in order to generate an icon for text elements for list screens( with WRITE command) you have to find the character counterpart of the icon. You can find this code in ICON.
I want to post about a very common STMS error which holds STMS queue in running status. As you know after you click transport button in STMS screen, your request is displayed in truck(pending) status. Here, requests with pending statuses are imported to the system thanks to execution of a background job.
For instance you found the name of a custominizg table and want to know how your customization is done via SPRO. Moreover you could be looking for cusotmizing requests that you have taken to transport your customizations. In fact for a functional consultant the reverse is more probably on the other hand ABAP’ers have more technical perspective therefore this post will be helpful for them.
In order to merge requests from multiple requests, you can use SE03 transaction. In SE03 this functionality is available under Requests/Tasks->Merge Object List branch of the tree. However there is a big pitfall while merging modifiable requests with unreleased tasks. If you try to merge objects from a modifiable request with unreleased tasks, some of the objects will not be included into the merge request. This is because your are only giving requests to Merge Object List but not tasks under tasks.
As you may know if you have configured SAP system routes in STMS correctly and requests are given the correct target system (either Target system or Target group), then each released requests will automatically transported to next target destinaiton in your transpor route. For example in a SAP landscape with Development->Quality->PrePoduction->Production configuration, a released Development request will be ready to be imported in Quality system.
If you have an enhancement object in your request object list sometimes there is a posibility that your request is not released succesfully. “Piece List for Objects ‘SHI3’ or ‘SHI6’ is Incomplete” error is thrown and displayed in Pre-Export phase of request release.
According to your company’s needs you can put some controls on transportation of requests. For example you may have quality, pre-production and production systems. And among these systems you can put some checks in order to prevent mistransportations. Or you may want your requests to be transported once , because retransportation of a request may lead to overriding problems.