One object, two transport requests?

[Former Member]

Hi,

Does it make sense to have one object in two different transport requests? First, is it possible to have an object in two unreleased transport requests?

User1: Needs changes on a program.

Programmer: Makes neccessary changes to program. Saves it in a transport request.

User2: Needs some other changes on the same program. Previous transport request has not been released.

Please help as this is confusing in terms of how this would work. Points will be awarded immediately on logical solution.

Thanks in advance.

Prem.

[Former Member]

In this case when USER2 makes his/her changes it will be included under a new TASK under same Transport request of USER1 whose transport was unreleased...

[Former Member]

Hi Arun,

User1 and User2 are not programmers. They just raise requests for changes.

The programmer makes the changes. He makes changes for the 1st user and creates a TR. The second user needs some changes too.

At this point what does the programmer do? Creating a new TR for the same object is not possible.

Thanks for your reply.

[Former Member]

Hi ,

You cannot create more than one transport request on an object when there is already one request mounted on it.In such case when another user edits the object a new task will be created under his/her userid.New requests can be created only if already created requests are either released or deleted.

Regards,

Kiran

Edited by: Kiran NN on Mar 7, 2008 7:43 AM

[Former Member]

You can create an additional Task for User2 in the same request in which User1 is available and do the changes for the requirements.

Hope this helps.

Regadrs

Vinayak

[Former Member]

Hi Prem,

When User1 makes some changes in a program a request is created on the name that user for that particular object.

when other user comes and makes some changes a Task is created for the same object under the parent transport request.

That means User1 creates parent transport request and User2 creates a child request ( A new task) under the Transport request of User1.

Hope it clears your doubt.

Regards

Sourbah Verma

[Former Member]

It creates a new task and the same transport request for the second user. You can change the owner of the transport request or merge the transport request(see menu options in SE09)

Thanks,

Krishna

[Former Member]

Hi,

1.Once you have creeated a request and not released the request.Though you have changed the object at the time of saving it never ask you to create one more request.Means without first trequest release you can not asign same program to other request.

[Former Member]

Hi,

In this case you can either club both the changes in a single tr and move it production or do it in a sequential way, obvoiusly one among the users have to wait until the changes reach production.

Regards,

Kiran

[Former Member]

Hi All,

Let me rephrase that question.

User1 and User2 only raise requests for change.

The programmer is the one that acutally makes the changes to the object.

If both the users have different change requests for the same object, how does the programmer make the changes to the program and provide each of them with a TR to release when tested?

Thanks for your replies. All will be awarded points.

[Former Member]

Actually my previous reply answers this. You need to prioritize which change needs to reach production first . Is it the one which carries the user1's change request or is it user2's.Since both change requests are pertained to the same object, we have a situation called TR conflict here.So you need to follow the above said approach to resolve this.Determine the priority from the user.Hope this helps.

Regards,

Kiran

[Former Member]

Hi All,

That was a good array of messages. Confirmed my doubt about it.

Thanks a lot for your answers. As promised, points awarded to all.

Kiran, as a final request, any documentation on the TR conflict that you mentioned would be very useful. Could you send me a link or doc on [email protected]?

Regards,

Prem.

[Former Member]

Actually i dont have any link which details this. Anyways the approach which i mentioned is been followed for TR conflicts pertaining to any object.Actually these scenarios will be contained in project specific documents.You may find it in your quality templates confined to your organisation.

Regards,

Kiran