Transports missing from QA worklist

[Former Member]

Hi all -

We recently performed a system copy on our CRM system to refresh the QA

environment. Pending transports that were not yet in the production

system were re-imported into the QA environment post-refresh. (Our

STMS paths are configured to require 2 approvals in QA prior to move to

PRD). However, although they still show as "inactive" status in the

production import queue, these transports are missing from the QA worklist for

approval.

Anyone know how to get these transports to show back up in the QA worklist so that they can go through our standard approval procedure?

Thanks for the help!

Abby

[Former Member]

I  have the same problem,

Did you finally solve it , did it work ?

Let me know,

Regards,

[Former Member]

Hi Abby, I realize this answer is probably a little late to help you but it may help others...

The previous answer only explains how to get the transports into a transport queue, which are just files on the OS under /usr/sap/trans/buffer.

Your question was how to get the transports into the QA worklist which is table TMSQWL in the QA approval system.

There are 3 steps to getting a transport ready for approval...

1. Add the transport to the delivery queue as per Pryan's reply.

2. Set the transport in the delivery queue as inactive (waiting for approval)

    tp setinactive <TR> <qa_sid> pf=<path to TMS profile>

3. Add the record to table TMSQWL in the QA approval system

    This could be done using SQL or by writing an ABAP program, but I don't know of an official way to do this.

regards,

Colin

[Former Member]

Dear Abby

System import request not be displayed in TMS que automatically, you should manually add this to the que using tcode

STMS --> GO to QAS system --> Extras -> Other request --> Add then manually can be add.

Then you can provide the dev request no according to the requst exported to the usr/sap/trans directory.

after importing you can see the request.

reg

priyanshann

[Former Member]

Hello Abby,

I think you need to reexport those transports from Dev system.

Thanks,

Siva Kumar