topic Re: Transport Import issue in DevOps and System Administration Forum

Transport Import issue

former_member738068 — Mon, 20 Feb 2023 12:18:36 GMT

Hi Experts,

Please note TR sequence below. Both TR1/TR2 contains same smartform.

TR1 - from dev system released in sep - Moved into test in Jan

TR2 - from dev system released in Dec - Moved into test in Dec

Issue was TR1 moved late in Jan, it actually wiped changes of TR2 in test system. so decided TR2 changes will be done again by another TR3 later to match with Test system.

Now TR1 is ready to implement in Prod in Feb. But not TR2. Please note sequence mentioned above. So question is

1)Can only TR1 go into prod without carrying changes from TR2? Will TR1 carry TR2 changes to Prod because late in importing?

2)My concern is when TR2/TR3 will be move together later, will it affect or wipe out any TR1 changes? Can TR2 can go together later without affecting TR1 changes?

Re: Transport Import issue

mamartins — Tue, 21 Feb 2023 10:16:13 GMT

When you releasead TR1 from DEV on sep, a set of files were created on the DEV file system. This set of files contains the objects you changed or you said to include on the TR. Even if you make changes to the same objects, that TR set of files never changes again, it's like a photograph of those objects on that particular moment of time.

Question 1) When you transport TR1 to PROD, only TR1 objects versions matters. TR1 doesn't know nothing about TR2 or TR3. The way you choose to transport orders in TEST doesn't change anything on their content.

Question 2) From your description, TR2 and TR1 both have same objects because you said that TR1 imported wiped out TR2 changes. So if you import them with the same order as they were released, you will end up with the same state as they are currently on DEV.

Re: Transport Import issue

Matt_Fraser — Tue, 21 Feb 2023 21:58:40 GMT

Manuel,

That is true, that if the transports are imported to PRD in the same order they were released from DEV, then the same status as in DEV will be created in PRD. The problem is that isn't the order in which they were imported to QAS, so therefore it will not be the same status that was tested, and that could be an issue.

Cheers,
Matt

Re: Transport Import issue

mamartins — Wed, 22 Feb 2023 10:18:06 GMT

Right, but there is nothing that you can do about it unless restore the QAS database to the state prior to the TR import and do the transport on the proper sequence...

Re: Transport Import issue

Ryan-Crosby — Wed, 22 Feb 2023 13:02:22 GMT

From what you have described TR2 should already include the changes that were done in TR1 because it was generated after TR1 was released from the development system but involved the same objects (unless someone specifically reversed those changes in TR2). Simply re-import TR2 into your quality environment to test and verify that it includes changes from both and proceed.

Regards,

Ryan Crosby

Re: Transport Import issue

former_member738068 — Thu, 23 Feb 2023 10:38:38 GMT

@m14927 @matt.fraser - Thanks Manuel and Matt for your information. Very useful.

Very important point Manuel mentioned that TR contains set of files contains the objects you changed when released TR (does not matter when imported in QA) and that is carried when imported in next system. So in our case, TRs released from DEV in correct sequence. Only imported in wrong sequence in QA.

So what i am planning to do.....

1)Let TR1 go into production and it does not contain changes from TR2.

2)Then re-import TR2 into QA , So DEV and QA systems will match and do business testing.

3)Finally TR2 will be move into PROD.

Is this sounds correct? Please suggest.

Re: Transport Import issue

Matt_Fraser — Thu, 23 Feb 2023 15:41:02 GMT

yogisap007

This seems the wise strategy to me. This way you should be able to properly replicate your DEV status in your QAS system, and thus obtain a proper test before approving either transport for PRD. The alternative would be to advise the business that TR2 cannot be approved unless TR1 is approved at the same time, and then import both transports together into PRD in the same order you imported them into QAS (e.g., TR2 and then TR1). In this case, order of creation in DEV is not important, and even order of release from DEV is not important; it's order of import into QAS that is important.

Cheers,
Matt