differnce

[Former Member]

What is the difference between task and change request

[Former Member]

Dear rakesh reddy ananathula,

I would advice you to please visit www.sap-img.com/sap-sd.htm. It will give you the overall view of SD module.

Hope this helps you.

Do award points if you found them useful.

Regards,

Rakesh

P.S. you can send me a mail at my mail id rakeshsinghchauhan@gmail.com for any specific details

[Former Member]

The Change Request is that request when you do some thing new in customizing or configuration in the system. The system will automatically pop with the change request pop box , when you can give request name as defined by the system or can give your own request name with heading of what changes you have made while customization. The system will generate a request number and you save it. (e.g.:- VEDK-2785467) VEDK- means the Clients System name then followed by the system generated request number.

Now when you want to release the request you have to use the T-code SE10 where you can see the requests under the heading modifiable or released. Go to the modifiable option. Each request will have again an internal request number. First you have to release the internal request and then release the external request number. This will in turn released by the basis guys thru the T-code SM64 in a group when all the requests are pooled from different users.

The task which you have mentioned in your question is nothing but the what task you have performed while customizing the client system and the heading name which have given it for that task and generated a request for that task.

[Former Member]

hi

<a href="http://help.sap.com/saphelp_nw04/helpdata/en/57/38ddff4eb711d182bf0000e829fbfe/frameset.htm">http://help.sap.com/saphelp_nw04/helpdata/en/57/38ddff4eb711d182bf0000e829fbfe/frameset.htm</a><a href="http://help.sap.com/saphelp_nw04/helpdata/en/57/38ddff4eb711d182bf0000e829fbfe/frameset.htm">http://help.sap.com/saphelp_nw04/helpdata/en/57/38ddff4eb711d182bf0000e829fbfe/frameset.htm</a>

Transport Request is generated in following scenarios:

1. Customizing Request - When doing or changing some customization.

2. WorkBench Request - When configuration is cross-client. Eg Generating new Table, making changes in access sequence, Abap development, etc.

Transport request is not generated for Master Data. For eg: Customer Master, Material Master, price master, etc.

Benefit of Transport Request:

SAP Landscape normally has 3- Tier system:

Development Server - Where customization takes place. Transport request is generated at this level & then first transported to Quality server for testing whether it meets the requirement or not. Once the requirement is met in Quality server then Request is transported from Development Server to Production Server (Actual / Live System)

Quality Server - Mainly useful for testing.

Production Server Actual / Live server, where the real transactions are created & posted.

Procedure to Release & Transport Request:

1. In development server, go to T.Code: SE10 & select the check box Modifiable & enter

2. In the next screen, you will see list of transport request created.

Note: Transport request consist of main request along with sub request. These sub request hold the object to be transported.

3. Expand the main request & you will be able to view the sub requests attached to main request.

4. First release the sub requests.

Note: To release the request, select the request ni & click on release request individually (Do not select release all request)

5. Next release main request.

6. Once the request is released sucessfully, imform the basis person to import the request to QA server.

or

If the authority is with you, through T.Code: STMS, select development server --> select request no & release to QA server. Here when it pops up client no, user id & password, maintain it of QA server & release the request to QA server.

[Former Member]

Hi

<b>Tasks </b>are the sub-requests which holds the object changes. A <b>change </b>request is a collection of tasks for the same object (or) related developments.

It is not possible to release the request without releasing its tasks. You have to release the tasks and then release the request.