Skip to Content
0

Time between creating and releasing transport request

Oct 10, 2016 at 02:21 PM

131

avatar image

Hi! How much time is limit between creating and releasing transport request in urgent change?Sorry for bad english.

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

4 Answers

Raghu Govindarajan Oct 10, 2016 at 02:42 PM
1

Time between creating and releasing a transport are dependent on how fast you can make your changes and test them.

I think you are trying to ask about what is the time between releasing a transport and it moving to the next system in your landscape. This is set up by your basis team, and is a question to ask them. There is a background job running that looks for released transports that are ready to move and moves them to the next system. How fast your transport moves depends on this frequency.

Alternatively, if it is that urgent that you can't wait, you can manually push a transport using STMS if you have the correct authorizations.

Show 1 Share
10 |10000 characters needed characters left characters exceeded

It is a bit more complicated than that. You have client-dependent and client-independent transports.

1. You make the settings or change code in DEV (you may need to run SCC1 for configuration to get the settings in the client, where you perform testing).

2. You test in DEV and confirm that everything is working.

3. You attach some proof in the system, which you use for tracking CTS, release your tasks and inform your administrators that they can move these changes to QA. There can be specific sequence in the transports related to a single change, there can be some manual activities to be done after importing a specific transport.

In most cases it is a bad idea that you import anything on your own and bypass the BASIS team (even if you are authorized), because it can happen that you mess up another import or that your import should be scheduled at a time when no activities by the business are executed.

All these checks/procedures/times are done by following the internal rules in your company. Maybe you have some SLA in your ticketing system, which can give you some rough idea when you need to finish your work.

1
Rizwan Javed Oct 10, 2016 at 07:36 PM
1

Totally depends on the change control process that each organization follows. In some places the urgent emergency fixes/changes can be instantly deployed provided they are tested and have the required approval. Technically system will not stop you from transporting the changes to next system. It only depends on the change control process.

Share
10 |10000 characters needed characters left characters exceeded
Muldagaliev Zhanbulat Oct 14, 2016 at 09:17 PM
0

Thanks for your answers. I have asked a question because I have faced a problem with transport some urgent changes via Solution manager to QA system.Transport request added to this urgent changes and then there has passed more than one month before realeasing them. Other urgent changes moving without problems. (No import into test system has taken place yet)

Share
10 |10000 characters needed characters left characters exceeded
sapHunt Yin Oct 11, 2016 at 01:36 PM
0

Hi, I believe it depends on your organization SAP change process, you can check your basis team , or Change management team for detail. at my organization , change should be approved by Manager, and Map to Work week, after required test and IT governance processes, after that , IT and Business function owners should approve not matter how urgent it is.

Share
10 |10000 characters needed characters left characters exceeded