PI Object Movement via RevTrac - Object already present in change list

[poornimal_nathan]

Hi Folks,

We're moving PI changes across our landscape (shown below) when we face some errors. I have some clarifications about the same.

DEV -> TEST -> UAT -> Performance -> Regression -> PROD

We move our transports individually upto UAT, even though they are under a single RevTrac. After that, the objects are moved on a per RevTrac basis. We get the following errors in transports that forces us to do file transport, which we want to avoid.

1. OOPS Errors for objects under the same SWCV - Even when different objects are being worked upon. Should we reduce the granularity in RevTrac?

2. Transports fail with manual activities like filling up a password or the URL in the channel. How do we control these errors?

3. From PT onwards, since all transports under a RevTrac are migrated together, we get the following error: 'RC - 12: Object already present in change list' - How can this be controlled?

4. Lastly, even when the transports are moved, the objects have not been moved, this occurs from PT onwards only and is irrespective of the transport status.

I know it's a boatload of queries, but we're really stuck with these issue. Any pointers would be good.

[poornimal_nathan · Accepted solution]

Hi All, thanks for your inputs.

Quick update: we tried turning off the auto activation parameter. That resolved the manual activities issue.

But problem #3 remains. Whenever transports are moved in bulk (under a RevTrac), subsequent transports fail, with Objects Present in ChangeList error. This one is controlled by turning off the Auto-activation parameter

[former_member202642]

Hi Poornima,

'Object already present in change list', means that there are some objects which are yet to be activated inside the target Integration Directory.

Firstly, activate those objects under target ID change list.

Thanks,

Aamir

[former_member194786]

Hi Poornima,

1) As far as I can tell, you can not rely on OOPS for consistency check in SAP PI. We decided to ignore it for SAP PI and keep a tab on changes in more old fashioned way.

2 & 3) Adding to Harish's comment above, another option could be enabling parent child relationship between rev-tracks. So all changes up to PT can be part of individual revtracks and the parent revtrack will then have these independent revtracks referenced in order of import in the consecutive environments. I vaguely remember there being an option of Pause/Un-Pause option in revtrack. If that is available in your system, you can use ensure that the pause is triggered for each of the config related transports. Then once the pause step is reached, you simply transfer the object to your changelist and Basis can un-pause the revtrack for it to proceed with the rest of the imports till any further pause is hit or alternately import finishes.

4) Have you looked at the logs of CTS+ to figure what was the return code for the transports which went through but the changes didn't reflect? Unfortunately, with the details available that is the only pointer I can provide.

Regards,

Sanjeev

[Harish]

Hi Poornima,

we used Revtrac for ABAP transport.

2. Transports fail with manual activities like filling up a password or the URL in the channel. How do we control these errors?

-->> This has to manually updated in every environment after the transport. according to SAP note, you can not auto activate the ID object transport.

3. From PT onwards, since all transports under a RevTrac are migrated together, we get the following error: 'RC - 12: Object already present in change list' - How can this be controlled?

-->> The change list has to activate first. Please turn off the auto-activation parameter for integration directory.

regards,

Harish