Hello, in our company we have defined a rigid procedure to transport R/3 change request to our production system, now we are thinking to change this procedure.
We have checked again the online help about TMS, and we can read that SAP talk about two strategies to import request in R3 systems using TMS queues.
You can choose between two procedures when you use import queues to perform imports:
You can import mass transports into your systems. This procedure imports all requests waiting for import in the queue. All requests are imported into the target systems in the order they were exported. This minimizes the risk of errors in the target systems caused by requests being imported in the wrong order, and the risk of objects being missing in the target system.
Mass imports are particularly well suited for the quality assurance system and production systems in the implementation phase of a project.
You can import single transports into your systems. This procedure makes a selection of requests from the import queue and imports them into the target system. The other requests remain in the import queue, where you can choose to import them later, or not at all. Single imports are the most flexible method, however, they demand more administration.
In our system we can no use the mass imports because in the production transport queue, every day there is many requests that was not tested still in QA system these requests can not be imported in production system yet, and then, we must use import single transport.
We must use import single transport , but also we want to assure the consistency of the production system, and to minimize the errors due to a transport request in wrong order with the same or dependent objects or errors due to transport request with partial object.
Nowadays to assure the consistency in the transport process, we donu2019t allow to transport a request to the production system, if there is any requests not imported ahead in the queue that have the same objects or objects that belong to the same functional module.
Our development department request us to relax this procedure and to allow more transports of request to the production system, and then now we are thinking to change de prodedure, and we want to know how other companies work with the transport system, or if there is any SAP expert recommendation about this.
Does everybody allow single transport request to production system? If yes how they control that the request donu2019t cause problem due to other request that still are pending of transport, really does everybody respect the transport queue order of the request in the single import??
Thanks in advance for your help
>in the production transport queue, every day there is many requests that was not tested still in QA system
Why are requests being released to the prod queue if they have not been tested in the QA system? Fix this issue and all of your problems will disappear!
we have configured 3 system in STMS DEV, QAS and PRO, frist the request was relesed from DEV and automatically was added to QAS transport queue, waiting for import, after import in QAS system automatically the request was added to PRO transport queue, because this while the user is testing the request in QAS systema, the request remain waiting for import in PRO transport queue.
First think you have to take into account is clear understood what STMS is
You wrote: "In our system we can no use the mass imports because in the production transport queue, every day there is many requests that was not tested still in QA system these requests can not be imported in production system yet, and then, we must use import single transport."
As Matt wrote, you should set up QA approval step at your QAS system, Please see the link
Then 2 point, how it works in other companies>
Best practice, which I recommend is to used this process>
Developer did his transport at DEV system, after developer release it and it is automatically imported into QAS import queue.
At QAS is running job every 10 minutes, to import all request in the queue to system QAS.
Developer/tester/responsible person test it at QAS and if responsible person is happy with it, they approve it at QA approval process.
In case they are not happy with it, they can reject transport or postpone it approval.
If case is approved, it will be ready for import at PRD import queue, where we have import job for all transport with status waiting for import, but with option leave request at import queue for later import running one a day after business hours. It will not delete transport request from queue and it will be there for final "release - project" Before system copy, we did import all transport to production also those request which have already beeing imported to PRD.
QA approvers are only few person, they are usually project manager, boss of development team and basis team.
In case you are not sure about this, ask for consulting service from SAP.
Only one question, if you use this procedure "Quality Assurance Approval Procedure" there is transport request that can be reject, and so never will be imported in production system, and so you can not garantee the order of the import in production system, because the order is defined by the order in the prroval procedure.
in the SAP documentation i can read this about this procedure:
If you reject requests, there is the risk that errors may occur when they are imported into the delivery systems. This is a result of the requests containing objects that are referenced from other requests. It is safer to correct an error using a subsequent transport.
I think that all procedure have more or less risk and so the procedure that you must use is what it was more sutable for your system.
In your system there is many transport request by month??
At customer side, they never reject transport request, instead correct it with other transport.
They have about 1000 transport request and import them all to production once per 3 months, it call "refresh" because at the end of import, we are doing system copy from production to test.
Of course everything is done during weekend.
If there is not recject transport request all request will be trasnported to production, but how do you assure the order in the import of the requests in production system?, with this procedure it seem that the order deppend of the aproval process order, not the order in which the request was released in development system, no???
thanks very much for your answerd
It will be in same order as request was exported.
DEV - you export transport - it will be added to QAS
QAS - import job every "5 minute" pick up all request at import queue and import them to QAS system
they are added in the same order to PRD; of cause if request is reject it will not be imported to PRD - but this is only after developer know that it will not have any impact to other request/object.
PRD - in case of import you need to approve them,
Before refresh queue at QAS must be empty and export of transport at DEV must be blocked!.
If i understand your procedure, you have two import procedures to production system:
.- one there is a job that import some request that remain in que queue that was aproved by
the developer or the project manager, this procedure run one time a day at night.
.- import process each three months you import all request in the production queue and
make a system copy and refresh the QAS system.
One question, in the first import process, the job that import all aproved request every
night, this job import all aproved requests all night?, in the queue of production there
is 3 request not aproved:
request1 --> not aproved
request2 --> not aproved
request3 --> not aproved
today (day 1) the developer aprove request1 and request3, the import job that
will run on night of day1 will import this two request in correct order request1 first
and second request3.
request1 --> aproved
request2 --> not aproved
request3 --> aproved
tomorrow the developer aprove the request2,
request1 --> aproved
request2 --> aproved
request3 --> aproved
the question is, in night of day 2 the import job will import only the request2 or will
import again request1, request2 and request3??
thanks in advance for your help
We are currently Importing the Request into QAS(Quality) server after releasing the request from DEV. We do it through stms . After that we import into PRD.
I want to avoid this step of importing the request into QAS. i.e The Moment Transport request is released from DEV ,the request should automatically gets imported into QAS(Qualtiy) specific client.
How to do this ?? .Can anybody share his experience of how this can be done.