diff between task and request

[Former Member]

wht is the diff between request and task in transport organiser?

[former_member188829]

Hi,

Check this thread..

[Former Member]

Hi,

A request is one which contains many tasks under it. The tasks are each one type of object and are released to the request.Once the tasks are relased to the request then the request can be transported

Many tasks will be under one request.

suppose say in a project different users have to change one program

for every user one task will be created under only one request

Request is the highest level in the hierarchy. The tasks will be stored under the request.

It has 1 to many relation ship. i.e, a request may contain 1 or more task. But task cannot contain any request under it.

A task is nothing else but a "container" for your transport objects. You cannot have a task without a request (like you cannot have fields without a table or structure).

Eventually, the request is the "vehicle" used to transport your object to the next SAP system

see you trying to create a progam where for a particular Report needs a Ztable , zdataelement, zfunction module.

ok , while saving this first Request will create and in that for program you will have one task, and for table while creating it will generate a task at that time you have to see in which request you want to save, like dataelement , function Group .

once complete this you can check in SE10 where you can see one request , in that you can find all tasks which you created for z objects and these tasks also

you can see in the utilities-> version.

A task is nothing else but a container for changes made by one ore more developers.

Tasks are a means to organize your transport request. For example, if you have a team developing on the same subject then you create a single request and for each team member a task. Every team member collect her changes in her own task. Sooner or later the development is finished and one task after another will be released. After finishing the final tests the team leader will release the entire request.

Note that this is just one possible scenario for organizing transports.

Refer to this link

http://help.sap.com/saphelp_47x200/helpdata/en/44/b4a0137acc11d1899e0000e829fbbd/frameset.htm

Reward with points if it is helpful..

Cheers,

Chandra Sekhar.

[Former Member]

an object is assigned mainly to a request,and if that request is not yet released and another user wants to change that object then a new task is crearted for that user's id and original remains as it is.

[Former Member]

Usually, a Request is a number for an object, which saves under that request. And task is a sub request. A single request consists many tasks. Generally when you are developing an object you need to develop many includes or data dictionary objects. each one saves under a task of the same request, if u are trying to saving it under the same task.