Different change request about the same object

[Former Member]

Hi Gurus,

I have some doubts about CR (change request) from one system to another, such as from development system to quality or quality to production.

If I have 2 or more CUSTOMIZING CR about the same object Can I say that they are however identical (they contain the same information)?

For example on the customizing table:

record1 contains value 'A' --> CR number 1 is opened

record1 contains value 'B' --> CR number 2 is opened

If now I transport CR number 1 I transport value 'B'.

And the same if I transport CR number 2.

Is it correct? Both CR points to the actual value of the record?

Instead if I have 2 or more WORKBENCH CR I know they "remember" the history of the modifications:

For example on a program with only 1 istruction:

data: x.

--> CR number 1

data: x,y.

--> CR number 2

What happen If I transport the 2 CR simultaneously (selecting both from STMS) ?

What will be the result in quality/production system? Which CR "wins"?

Thanks in advance

Guido

[raviprakash]

Hi Guido,

The transport requests (whether Workbench or Customizing) contains the reference of the Object chnaged. They do not keep the changed data. When you release a request, the reference is picked from the Transport Request and object is added and released to other system.

Hence if you have request 1 and request 2 referring to same object, when you release them in any order, the target system shall have always most up to date change.

Regards,

Ravi.

[Former Member]

Hence if you have request 1 and request 2 referring to same object, when you release them in any order, the target system shall have always most up to date change.

Sure??? How Can you have versions management in abap program? Each version of the program is linked to a CR!

[ThomasZloch]

At time of release from DEV, the current object version or table content is written into the transport data file, thus "detached" from further changes in DEV.

Now if two transport requests 1 and 2 contain the same object in two versions (older and newer) and are being imported into QA, the following scenarios are possible:

- 1 is imported first, then 2: newer version will be in QA -> OK

- 2 is imported first, then 1: older version will be in QA -> not OK

- both are imported at same time: newer version will be in QA -> OK (STMS checks when the requests were added to the import queue and sorts accordingly)

Thomas