Request number and Task number

[Former Member]

Every Request number have hirerachy with Task Numbers,

Why SAP provdided 2 numbers like request number and task number...

Why we are not saving all the tasks under one Request number only...?why sap provided task number seperately..?

Please clear my doubt ,i am unable to find any forum related to this query in SDN..

[Former Member]

You can refer :

http://help.sap.com/saphelp_nw70/helpdata/EN/7e/75ac89a9f811d2850d0000e8a57770/frameset.htm

Still copying the portion that gives your answer :

"The Transport Organizer helps you when you organize development projects by allowing you to distribute project work for individual developers or teams between different change requests. These change requests record all changes made to development objects and Customizing settings. Objects from the areas of Customizing and the ABAP Workbench are managed and recorded in separate requests. Special checks have been implemented for each of these applications.

Developments, corrections, and repairs are recorded in tasks and transported using change requests.

The target system and type of transport are assigned automatically and no longer need to be maintained by the user.

Several users can work together on a project by organizing their development work in tasks. These tasks belong to a common change request."

Thanks,

Amurta

[GauthamV]

Check this documentation provided by SAP

Requests and tasks allow objects from the Repository or Customizing to be managed 
within an SAP System or transported between different SAP Systems.

There are different types of requests or tasks, which fulfill different functions in the SAP System:

Change requests

Transportable change request
For recording changes to Repository objects and transporting them to other SAP Systems
Local change requests
For recording changes to Repository objects within an SAP System
Customizing request
For recording changes to Customizing settings and transporting them, if necessary, to other SAP Systems or clients

Tasks

Correction
For recording changes to
Repository objects if they are carried out in the object's original system
Customizing settings
Repair
For recording changes to Repository objects if they are not carried out in the object's original system

Other request types are:

Transports of copies
Transports of originals
Relocations of objects with package change
Relocations of objects without package change
Relocations of packages (with transport layer changed automatically)
Client transports
Piece lists
Delivery transports (for upgrades and Support Packages)

[Former Member]

You can refer :

http://help.sap.com/saphelp_nw70/helpdata/EN/7e/75ac89a9f811d2850d0000e8a57770/frameset.htm

Still copying the portion that gives your answer :

"The Transport Organizer helps you when you organize development projects by allowing you to distribute project work for individual developers or teams between different change requests. These change requests record all changes made to development objects and Customizing settings. Objects from the areas of Customizing and the ABAP Workbench are managed and recorded in separate requests. Special checks have been implemented for each of these applications.

Developments, corrections, and repairs are recorded in tasks and transported using change requests.

The target system and type of transport are assigned automatically and no longer need to be maintained by the user.

Several users can work together on a project by organizing their development work in tasks. These tasks belong to a common change request."

Thanks,

Amurta