Request Transport...

[Former Member]

Hello all,

I want to learn a support process- I have studied one of thread regarding work process of support.

And there is something which I want to understand in depth and that is only overview:

"When you need to solve the ticket. You would analyze the problem and identify that the SAP configuration has to be done for the required change.

You would request a transport for DEV CLIENT to BASIS. You do the change and Request one more Transport to BASIS for QA client. The End user will test the same by creating a sales order for the new plant and approve it.

Finally, you request a transport to move the changes to PRODUCTION. Once the change is deployed in production the TICKET is closed. "

In the above process, I want to know about the Request Transport process and relevant Basis people work in depth, which t-code they use, Pls explain me the example and relevant practicle aspects, if you can give an example and relative practical solution to practice this request transport regarding the issue, would be best for me to understand because once i do it at my own with your guidance, I will be more confident how to transport the request from here to there.

Rgrds,

Geeta

Edited by: GeetaChaudhary on Nov 12, 2011 3:16 AM

Edited by: GeetaChaudhary on Nov 12, 2011 3:18 AM

[Former Member]

Usually you will have a landscape of 3 servers, Development, QA and production. You have to perform your customizing changes in DEV, then SAP will ask you for a transport to save those changes, when you are done you have to release your transport in transaction SE10 and then import the changes into the next server which would be QA* (where the user will test that your changes are ok) using transaction STMS, if everything is ok you release** again the transport from QA and import it into Production.

*Depending on the politic sand customizing of the company you work on, you can create yourself the new transport request, or you will have to ask the basis guy to create it for you

• Usually the import into QA is performed by a recurrent job, which after x minutes imports every transport release from DEV into QA. It could also happen that there is no such a job, and you have to inform the basis guy to import the change into QA

• Usually to release a transport from QA the manager will have to also approve the release (there can be n approvers needed)

[Former Member]

Hi Federico,

Thnkx your worthy inputs in depth, Great Explaination,I actually learned a lot regarding practical procedure.

I some queries still, Pls explain those:

1. These Basis people are from which team Client side or Our side, means Support Team side???*

1. Explain the term- Politic Sand Customizing*

&

Recurrent Job???

1. Who is this Manager over here who approve the release, Pls explain???*

Thnkx & Rgrds,

Geeta

[Former Member]

The basis team can be part of the client or the support company, usually the team is a mixed of both, since it is a critical area so the client wants to have some control. When they assign you to a client, they will have to explain it to you in great detail, since it is different from client to client.

Recurrent job is a program that is executed automatically every time

The manager in my example is the responsible of the SAP production system, he/she is in charge of the changes that are imported to production, so he/she will have to give the last approbation before moving the changes into producdtion. Usually this rol is done by a person from the client side, but again, it cant change.

Dont worry, all these stuffs will be explained to you when they assing you to a new client.