Basic clarification about LIMU REPS Transport

I just want to clarify some basic stuff about TR and transport. Imagine I have 4 systems : DEV -> INT -> QA -> PROD.

I have two different changes locked through 2 different workbench TRs (A and B) but on the same object. This is a modification of a preexisting report so the type of the transport entry is LIMU and the object type is REPS.

First, on dev system, the first change is made and locked in the first TR (A) then transported on INT system. Then, on dev system, the second change is made on the same report and locked in the second TR (B) then transported on INT system. It contains change A and change B.

I want to transport first change (A) from INT to QA system, but keep the second change (A + B) to INT system. Does transporting the first TR will only transport the code version of the first change (A) to QA system or the transport of a LIMU REPS object is to basically take a picture of the current version in INT (A + B) and transport it to QA ?


  • Released transport contents remain unchanged. When transport requests are released in DEV, they preserve the object version at the release moment, meaning that a transport with change A will exclusively include the object with change A. Subsequently, after importing this transport into QA, only the object with change A will be present in the system.