Why should I need Task inside Transport Request?

[rajkumarnarasimman]

Hi All,

I have few clarifications, I don't know whether this may be right or wrong. But I want everyone to have attention about this topic.

Why we are creating Transport Request and Task Number?

I created the report in my dev client, that need to be moved to QAS client.  In order to do that,  I need TR(Transport Request) which contains all the dev objects that need to be imported in QAS. After importing done, report will be available in QAS system.

So TR is required; it looks like container(Truck) which moves data from one place to another place safely. Then why we need Task Number.. Why SAP included Task concept inside TR.

But When I saw my TR in SE01/SE09, everything is stored under Task instead of TR....

If all the objects are in Task means, Why our consultants always asking before releasing the TR like below.

Functional Consultants: Is all the objects are included in the TR?

Why they are not asking about Task? i.e (Is all the objects are included in Task?)

If all the objects are saved in Task itself, then I can move Task itself know, why system needs me to move both the things?

Inside single TR, Multi task can be included that is acceptable. But only for this case, are we creating TR and Task Number every time.

Regards

Rajkumar Narasimman

[rajkumarnarasimman]

Hi Raj,

Sorry for the late reply as i was out of town.

Putting my 2 cents here.

I believes in Task-TR concept.Reason let me put in a situation which i come across.

I was involved in a tool development in webdynpro where we tried to replicate the each modules in SPRO. As you we have lot of subdivisions in SPRO for each module.We were working parallel on each of these subdivisions.Our delivery manager have created a Task stating the description of the module and assigned each sub task for each of the developer.So were able to work independently on our own namespace without any dependency.

Modularization becomes easy and well organised. Even it helps to identify any problems easily in case your transport fails.

Hope it helps...

Regards,

Kannan

[Former Member]

Hi Rajkumar,

A task is created automatically whenever a new request is created. The main request will be called as Parent Request.

Each Parent request by default consists of one task.

If a user wants to do changes to the object that is already present in the task, then instead of saving those changes in the already existing task,a new task will get create under the same parent request.

This is the hierarchy:

Parent Request(Transport request):

   - Task1 for user1

       -Object1

       -Object2

   - Task2 for user2

       - Object1

   - Task3 for user3

      - Object2

And this number of tasks will increase based on the number of users doing the changes for the same object.

For additional information on the Tasks and TR's please check the below link:

http://www.guru99.com/what-is-transport-request-how-to-importexport-it-check-logs.html

Hope this helps...

Regards,

Shafi

[rajkumarnarasimman]

Hi Shafi,

Multi user concept is acceptable, but in rare case only we are using multi task in single TR.  But every time during TR creation itself, by default the system is generating both TR number and Task number.

Even the same object can be stored in multiple task in TR(Userwise). But at a time, single person only work in that object .

I understood, even during client copy (SCC1), we are considering only Task Number, that shows the objects are under Task.

Then why we need TR?? Do we have any other specific properties technically for Task and TR. 

Regards

Rajkumar Narasimman

[ramesh_narayanasamy]

Hi Raj,

It is not required to move the Main TR from Development system to Quality system,  We can do it by releasing the task alone in development system and do transport of copying the Main Parent TR from development system to Quality system. Once we feel that our objects are completely finished after testing then we can release the  Parent TR by that time and move to Quality and Production system.

In solman we have used this concepts of releasing the task alone and do transport of copies from main Parent TR without releasing it.

Hence for this is also could be one of the main reason that SAP has provided Tasks under main TR.

Regards,

Ramesh

[rajkumarnarasimman]

Hi Ramesh,

If Task itself is enough to move the objects to QAS and PRD, then again why we need TR?

Ramesh Narayanasamy wrote:

 Once we feel that our objects are completely finished after testing then we can release the  Parent TR by that time and move to Quality and Production system. 

If testing is possible in QAS, it is nothing but all the objects are imported in QAS.

Why are you moving the TR again to QAS and PRD?

Regards

Rajkumar Narasimman

[ramesh_narayanasamy]

HI Raj,

As u know that we can create multiple tasks and while releasing the task, the objects will be inside the TR also and after that we will do transport of copying the main TR to do test transports to Quality system(i.e simailar to transport of copies ). These process will be repeated until developments has been tested completely which mean unit and integration testing is over.

Once all is ok then we should release the main TR from development and import to Production as well.

These imports can be done directly to Production system from dev system or via Quality system.

Hope u clear about the purpose of tasks inside TR.

Regards,

Ramesh

[rajkumarnarasimman]

Hi Ramesh,

Thanks for the information.

Do you have any document from SAP, which explains task can be released and imported to QAS without using TR in SAP?

If possible, Can you please share it?

Regards

Rajkumar Narasimman

[Jelena_Perfiljeva]

You can't move the task alone without a transport request. I believe Ramesh meant 'transport of copies' when a transport of copies is created that includes task(s) from another transport. (I think there was a blog or document on this on SCN.) It is still a transport request, so the statement that a task can be imported to QA on its own is incorrect. If you go to STMS and try to put the task number there you'll just get a "not found" message.

In all honesty, I'm not sure why this is such a concern or even a question. It's just a structure that we have in SAP. There could be multiple tasks under one transport either for different users or of different types (e.g. one could be Repair and one Workbench). Yes, there is an additional button to click to release the task first but in 10 years with SAP it never bothered me a single bit personally. If this is your biggest concern about SAP then I envy you.

[rajkumarnarasimman]

Hi Jelena,

Yes, you are right. At the end it is nothing but a structure which need to be followed. Even it is not bothered me also.

The main reason for raising the thread to have attention on the concept(TR/Task) which we do in daily manner. Even I raised the thread as like discussion not Question.

Regards

Rajkumar Narasimman

[Former Member]

HI Rajkumar,

As of my knowledge whenever we are doing work on particular object that includes ex: module pool, table, smartforms then TR and task will come to picture, that means we need to include all TASK that means module pool tables smartofrm under one object that means one TR, i think one task cant contain all(mpp form tables).

And one more point-- In one object that includes mpp tables form, these can be assigned to different technical consultants by project manager like

mpp assigned to techincal consultant1

form assigned to techincal consultant2

etc..

and project manager will create one TR and ask them to save your tasks under this TR, so whenever different consultants are trying to save the their objects to under one TR then TASK will be generated respect to the consultant.

hope it may clear you something.

regards

laxman

[rajkumarnarasimman]

Hi Laxman,

Thanks for the update.

Laxman P wrote:

As of my knowledge whenever we are doing wor on particular object that includes ex: module pool, table, smartforms then TR and task will come to picture, that means we need to include all TASK that means module pool tables smartofrm under one object that means one TR, i think one task cant contain all(mpp form tables).

If I am not wrong, we can store all objects in single Task itself, For this case multi task is not required. 

When we edit the standard program, a repair task will be generated. In that case only we may face two different task(Repair & dev/correction) in same TR, if we include the customizing changes also in the same TR.

Regards

Rajkumar Narasimman

[Former Member]

HI Raj

til now whenever i am working with object that having report and smartform those will have the different tasks in under one TR.

Can we save those objects(report and form) under one task???

regards

laxman

[rajkumarnarasimman]

Yes we can have all the customizing objects in same task inside TR.

To confirm, create the smartform & report and save it, then you can find it.

Regards

Rajkumar Narasimman

[Former Member]

Yes that is ok.

but when i create table the table created under one task and for the same table i am creating data element and i choose the same TR to save that then another task is automatically created by system.

In this case how we need to restrict that the data element also should save in same task that table has saved ?.

regards

laxman

[rajkumarnarasimman]

Hi Laxman,

Create the Table and data element in the same User, I hope the task won't split. Try it and let us know, if you face the problem still after created, kindly share the TR screenshot.

Regards

Rajkumar Narasimman

[Former Member]

You can see the image. In this ABAP4 is the user

[ramesh_narayanasamy]

Hi Laxman,

There are 3 types of tasks are there in SAP.

* Customising Task

* Workbench Task

* Repair Task.

Since you have done some changes in Table definition. Am not sure why this was saved in repair tasks.

Also you have created some data elements and this was stored in Development tasks.

Hope you are clear in task types.

Regards,

Ramesh

[venkata_emandi]

Hello Rajkumar,

Task to include different type of objects within the transport.

You can also create transport of copies ( i.e one transport holding several transport request).

hope this helps.

Regards

venkata emandi

[Former Member]

Hi Raj,

Sorry for the late reply as i was out of town.

Putting my 2 cents here.

I believes in Task-TR concept.Reason let me put in a situation which i come across.

I was involved in a tool development in webdynpro where we tried to replicate the each modules in SPRO. As you we have lot of subdivisions in SPRO for each module.We were working parallel on each of these subdivisions.Our delivery manager have created a Task stating the description of the module and assigned each sub task for each of the developer.So were able to work independently on our own namespace without any dependency.

Modularization becomes easy and well organised. Even it helps to identify any problems easily in case your transport fails.

Hope it helps...

Regards,

Kannan

[Former Member]

The request includes the target system, while the task does not.

Rob

[former_member185054]

Dear Raj,

      when sending data to one system to another system, example took tcp/ip protocol. basic type should have header, message, footer.Here parent task act as a header, it will have the details of where to send, who created, time ..blah blah things. in message it contains our child task(only objects).

footer is not there, because footer will have the redundacy data,which is used for error analysis. CRC check

so its like a data transmission from one system to another system. sap CTS architecture build like that. you can post this discussion to basis or network people. we may get detailed information on how this architecture is built.

Thanks and regards,

sampath.