Hi Rishav,
Thanks for the reply.Before the transport of copies and the import from DEV to QA was based on the current status of the change document thus bypassing the import all. We never had an import strategy from DEV to QA before and it would only import what was attached on the change document based on its status; for example, it was "ready for unit test" or "UAT successful" which would tell the "import transport request (background)" job to only import that specific transport to QA. Is it a new requirement now in SP13 that we need to define an import strategy for DEV and QA as well to overwrite the "import_all" parameter that is called when scheduling program /tmwflow/scma_trorder_import" in SCMA?
This is the flow:
It starts in DEV 100. We set the status to "Ready for Unit Test" and create transport of copies. Then we hit the M00000033 task list and schedule the import job which temporarily puts ToC to Dev120. If all looks good, we set the status to "Unit Test Successful" and schedule another import job. This officially moves the transport to DEV120. After that is tested, the status is set to "Ready for User Acceptance Test" and another import job is scheduled which brings the transport to QA5 400. Through this whole process, we never had to specify any transport as the system knows what to transport based on the status of the change document. After the patch, every time we schedule an import job no matter what the change document status, it imports everything in the TMS queue. Hope this made sense.
thanks!
alvin