topic Re: CTS Customizing Request in Application Development and Automation Discussions

CTS Customizing Request

miguel_silva3 — Thu, 05 May 2016 09:31:42 GMT

Hello All,

Anyone Can Help, I have a doubt related with customizing transports. When some made a changed an create a customizing request with for example:

TR 1 : Table tXX and KEY 100300 Check Fields Changed X X

Then another guy create another customizing order with a change in the same table for example:

TR2: Table tXX and KEY 100300 Check Fields Changed X X X

THen if I released the TR1 first which entries will I transport to the target system ?

Thank you In Advance

Re: CTS Customizing Request

Former Member — Thu, 05 May 2016 11:50:25 GMT

Hi Miguel,

I dint get you. How come you store a table in 2 TR's at a time in development? Are you talking about table and TMG? You can save TMG in 2 different TRs but not the Transparent Table.

Could you please let us know what exactly are you talking about? Provide the screenshots if possible.

Regards,

Mounika

Re: CTS Customizing Request

Sandra_Rossi — Thu, 05 May 2016 12:29:28 GMT

A transport request only stores the key of the data to transport (even ABAP repository objects), and the data is saved into a file only at release time. So, in your case, if you had not release TR1 before the other guy changed the record, that will transport the data you indicate in TR2.

Re: CTS Customizing Request

miguel_silva3 — Thu, 05 May 2016 15:11:05 GMT

Hi Sandra,

Thank you for the reply. It's exactly what I understood, only when I released the TR it's when the system made a screenshot of the key value and save this content in a LOG file.

But my doubt it's if you release another order TR2 with diferent content and transport the first order which data it's transport ?

Thank you in advance.

Re: CTS Customizing Request

Sandra_Rossi — Thu, 05 May 2016 21:25:20 GMT

Sorry if I was not clear. Differently said, the transported data is the data from the "file" (2 files in fact) corresponding to the transport request (files R<TR number>.<SID> and K<TR number>.<SID> of the "data" and "cofiles" directories of DIR_TRANS). The files are built when you release the transport request, the "R" file contains the data which is taken from the table at the present time (the "K" file being the "header").