topic Re: How works transport request management tool? (Version / Reference) in Application Development and Automation Discussions

How works transport request management tool? (Version / Reference)

nicolas_cottin — Fri, 14 Mar 2014 10:58:41 GMT

Hi,

I would like to understand how is working the transport management tool.

When you save an object in a transport request, what do we save exactly ?

Is it just a reference to the object to lock it

Or it is a specific instance/version of the object ?

This question because I'd like to understand if it is possible to update an object in an older version in the next system.

For example, I transport an Infocube v1 with TR1. Then I update this infocube and save the change in a TR2. I transport TR2 to my next system and I am getting here my V2 Infocube.

Then, let's imagine that the TR1 is transported again by mistake. What will happen ? Will I get my infocube in version 1 in the next system ? Or will I keep the version 2 as it was just a reference saved in theTR ?

Thanks,

Nico.

Re: How works transport request management tool? (Version / Reference)

ThangaPrakash — Fri, 14 Mar 2014 12:18:47 GMT

Hello Nicolas,

"Will I get my infocube in version 1 in the next system ? Or will I keep the version 2 as it was just a reference saved in theTR ?"

No, you won't get back the version 1 if you transport TR1, until you do the version reversal.

Regards,

Re: How works transport request management tool? (Version / Reference)

nicolas_cottin — Fri, 14 Mar 2014 12:35:23 GMT

Hi,

What do you mean by version reversal ? is it a manual action or something that could be triggered autommatically?

Thanks,

Nico.

Re: How works transport request management tool? (Version / Reference)

ThomasZloch — Fri, 14 Mar 2014 12:57:56 GMT

As long the transport request is not released, it is just a reference to the active version of the object.

When you release a transport request, the active version is being exported into a data file and later imported into the subsequent system.

So in your example, you are overwriting the newer version 2 with the older version 1 -> inconsistent.

You would need to import version 2 again to reach a consistent state.

This can get very complex if your transports contain many other objects as well...

My area of expertise is just SAP ECC though, I've heard that things are quite "special" in BW systems (since you mentioned infocubes).

Thomas

Re: How works transport request management tool? (Version / Reference)

nicolas_cottin — Fri, 14 Mar 2014 13:02:48 GMT

Ok thanks!

Re: How works transport request management tool? (Version / Reference)

RajatSahu — Fri, 14 Mar 2014 13:27:21 GMT

Hi Nicolas,

Let me demonstrate with example.

Let's say there an InfoCube A v1 with 10 Infoobjects in Development system.

Now we capture this in TR1and then we release the TP. So TR1 now contains the image of Infocube A v1 with 10 infoobjects .

Then lets say we make some changes such that the Cube A v2 now have 20 infoobjects and capture it in TR2. After releasing TR2 ,it will contain 20 infobjects .

So now when we move TR2 to next system(Production system lets say ) , the Infocube A v2 with 20 infoobjects will move and will be present in the Production system.

And again if by mistake we move TR1 , then infocube A v1 with 10 infoobjects will move to Production system (next system).

So in short the Transport stores the properties of the changes done to the BW object in tabular format and when we move a TR that corresponding tabular image gets replaced in the new system and the BW object gets modified accordingly .

Hope I am able to explain the situation you are facing .

Re: How works transport request management tool? (Version / Reference)

RaymondGiuseppi — Fri, 14 Mar 2014 15:05:19 GMT

Or, more likely, the transport will fail as there are now news objects like requests in the target system that use the former new fields So transport will update the "definition" of the Infocube in the "import" step, but will fail in last step "Method Execution" when actually trying to regenerate the ddic and program objects behind the Infocube, there could also be warnings in the "Check Versions" step.

Regards,

Raymond

Re: How works transport request management tool? (Version / Reference)

nicolas_cottin — Fri, 14 Mar 2014 15:12:17 GMT

Ok thanks for the detailed information. And in the case when a transport failed. What happens in the target system ?

Is the existing object corrupted or the old active version before the import is restored?

Regards,

Nico.

Re: How works transport request management tool? (Version / Reference)

RaymondGiuseppi — Fri, 14 Mar 2014 15:17:08 GMT

Last time (...) objects (ddic table) and requests behind were corrupted, e.g. unable to open any of those queries created in production (and the BEx transport request which collects those objects was not yet released...)

Regards,

Raymond