Cleaning unwanted CTS from import queue

[Former Member]

We have more than 300 CTS in the PRD import queue waiting to be imported. More than 250+ are pending from last 2-3 years and keep on adding as the change request get closed for them after the request get imported in QA and get added to PRD queue.

I wish to know whether its required to clean the unwanted requests pending in the queue. Is there should be any practise to monitor the queue on regular basis. The affect which we have is that, after every refresh we again have to import all the CTS into QA which is a very hugh task.

Please share from your experience. Thanks.

[naveen_kumar1 · Accepted solution]

Hi,

Yes you can clean up the queue in STMS. In your import queue for PRD, execute Extras --> Delete imported Requests.

Please review the below function modules and write an ABAP also works.

Use TMS_QAM_GET_WORKLIST to get the total list of requests.

Use TR_READ_GLOBAL_INFO_OF_REQUEST to get the information about each request.

Use TMS_CFG_READ_CONFIGURATION to get the system configuration

Then set a filter, and called the worklist display fm which then allows the user to select all tp in the filter and delete them.

Regards,

Naveen.

[Former Member · Accepted solution]

Dear ALL,

I think the issue is not clear to all the replied I received.I will try to rephrase the question.

Is there any process in other companies to delete the old pending CTS from the Production import queue which are not required to be imported in Production in future. It means the changes are not implemented in PRD and will not be required in future also, the changes were tested in QA due to which the CTS got added in the import queue.

[Former Member · Accepted solution]

As far as I could understand question , then we can implement QA approval policy in our SAP landscape. If any change needs not to be imported to prod environment then we can reject that change for production environment via QA approval process.

Please reply.

-Sandeep Jain

[former_member184551 · Accepted solution]

Hi , Might be late in the day but, we usually clean up unwanted and already imported requests from the production q because

a) the batch job in production keeps reimporting already imported stuff

b) the risk of by mistake pulling an incorrect transport.

Thanks

Sameer

[former_member185954 · Accepted solution]

Hello Sameer,

Why would a batch job re-import already imported stuff? When would that be needed? Also, in the long run, it may not be a sustainable thing to do.

An easy way to weed out the 300 odd transports waiting in the queue would be to goto the production buffer in STMS and include the Return Code of Transport Request into view.

This can be setup by selecting Personal Setting button in the tool bar and checking the 'Display return code check box'.

Further select the column labelled as RC or return code and filter for RC=INIT.

Once you have selected this, you should get list of all transports that are yet to be imported in production.

Select them all and Delete them from buffer.

However, from future perspective the transport approval procedure suggested by Sandeep is the best bet for avoiding this issue altogether and keeping your production safe.

Hope that helps.

Regards,

Siddhesh

[Former Member]

Hi,

It is always recommended to make all changes in Dev first and transport to QA and PRD.

Delete all request in Dev first and transport it to PRD.

if the changes contained in those Transport Request have already reached Prod then it doesn't make sense to delete the request numbers only.. as the database for Prod has already been updated with those stuffs. Include them in a Change request in Dev ,... then Delete them from Dev.... release the CR and Transport it to Prod. Database will be updated with deletion of those Unwanted Transport contents..

Regards,

Venkata S Pagolu