Skip to Content

Releasing a request

Hi Guru's

Can anybody tell me the real meaning of releasing a request

In basic terms with examples..

waiting very eagerly for your replies

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

4 Answers

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Sep 03, 2007 at 11:46 AM

    Hi,

    Releasing a request means , it is ready to import to another system by using TCode : STMS.

    Request will contain Core file and Data file will be stored in unix level directory.

    The merging information from the above files will be stored in Transport request that will be used to transfer object from one system to another system.

    Hope the info will help you, Rewards points if helpful.

    With Regards,

    K K V.

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Sep 03, 2007 at 11:45 AM

    Hi

    there will be 3 serevers in the real time

    development , quality , production servers

    after developing the object in the development sever , it will be transpoted to qualityserver , before trasporting it to the quality server

    the request you created for the object in development server needs to be released

    process:- go to T-code se01

    enter ur susername

    click on ur trasport request which is to be released and click on release button (truck symbol)

    then that request will be released in development and the basisi people will trasport this object to next sever

    reward if usefull

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Sep 03, 2007 at 12:36 PM

    hi,

    We have three server.

    development, quality and production.

    when u make some report, it is in development server.

    If its working fine , u need to check it on real data as development server may not having correct data.

    so we transport that report on quality server and for that we have to transport that request as every object in that request will transport in quality.

    until u do this, u cant use that report in quality.

    That report will not available.

    and u cant use it directly on production.

    its having cycle like,

    first made it on development than check it on quality and than pass it on production for real time use.

    hope it will b useful.

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Sep 03, 2007 at 02:50 PM

    hi manu,

    actually your project manager create the change request and he will assign the users to the transport request(the users nothing but the people are working under the project).Under the transport request task is created for the included users.for example there are 5 people working on the project including the project manager total 1 change request and 5 tasks are going to created. if change request no is 1 then the task nos are 2,3,4,5,6.the project manager will give or in the specifications the transport no will be given to the users and the developed objects are going to stored under the task no.for example you are request report then your development is going to store under your task request completing your developing and if you found there are no issues then you have to release your task and after the releasing of all the tasks then the project manager will release the change request. upto this its the work of technical consultant(ABAPers) after that BASIS people will transport from development server to quality server.

    <b>here i am givingthe the procedure.</b>

    -


    > When a new development project starts, the person responsible for development creates a change request, and assigns the project team members to it. The Transport Organizer assigns a project number to the change request using the naming convention <sid>K9<nnnnn> (for example, C11K900001). A change request should include objects between which there exists a logical relationship, and which can only be meaningfully executed together. This means that change requests allow the transport and management of complete and meaningful developments.

    -


    > The Transport Organizer then creates a task for each team member. Whenever a team member assigns a Repository object to the change request, it is entered in his or her task. At the end of the project, the task contains all of the objects that the team member has worked on.

    -


    > When they have finished with their part of the development project, each team member releases his or her task. The task objects are then passed to the change request. Once all team members have released their tasks, the project leader can release the change request. A change request combines all Repository objects that were created or changed during a development project.

    -


    > The transactions SE09 and SE10 are identical in function as well as in operation( these 2 transactions are used to create and transport the change request).

    -


    > When you create or change a Repository object during a development project, you must assign it to a development class. A development class is a container for objects that belong to one functional area. All of the objects in a development class share a common transport path. You can create development classes either when you set up the Workbench Organizer or later on using the ABAP Workbench.

    -


    > Development classes allow you to divide up your Repository objects logically and thus provide helpful orientation within the ABAP Workbench.

    -


    > Each development class has a contact person who is responsible for it.

    -


    > Once you have assigned a Repository object to a development class, you must also assign it to a change request. This links the object to a project, providing a temporal division.

    -


    > The Workbench Organizer automatically assigns objects to the relevant task within a change request.

    <b>actions after the completion of the development.</b>

    -


    > While developers are working on objects in a change request, these objects are reserved exclusively for those developers. These reservations/locks are created in addition to temporary object locks that the enqueue work process creates when an object is edited.

    -


    > When the developers have finished their work, they release their tasks. The objects and their locks are passed from the task to the change request. The objects can still be changed by all project team members, as the Transport Organizer automatically creates additional tasks as required.

    -


    >When the project is complete, the person responsible for development releases the change request. The locks on the objects in the change request are released.

    -


    >Change requests may be transportable or local. The Transport Organizer classifies them automatically depending on their development class. The following steps are performed only after transportable change requests are released:

    -


    >As soon as the change request has been exported, a test import determines whether all of the objects can be imported into the target system

    -


    >The Repository objects are exported to a transport directory. The success of the export and the test import is recorded in the change request transport log and checked by the developer.

    -


    >The export and test import results are written to the transport log for the change request, which is then checked by the developers.

    -


    >Import into the target system is not usually automatic. It is triggered in the Transport Management System (TMS). After the import, you can check the import logs.

    <b>if helpful reward some points.</b>

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.