Skip to Content

What would be the best way to handle the transport to change the revised version to active state?

We have a BW content infoobject present across the systems (dev, qa,prod). This is in active state in development. However it is in revised state in QA (as it is at the moment a copy of production) and production. I am looking at the best possible way to handle the transport or change of the state from "Revised" to "Active" so that there are no adverse effects on the infoobject status.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Feb 08, 2017 at 04:30 PM

    Hi Ajina

    Can you just check the following important checks :

    - Are there any differences between your dev system object and prod/qa object specifically the attributes ?

    if yes then capture those changes in your transport and move it across. if no changes then just capture your object in your new transport and move it across all the systems.

    Usually any of the business content object will have 3 version as A- Active , R - Revised , M- Modified.


    K M R

    Add comment
    10|10000 characters needed characters exceeded

    • Thank you for the reply KMR. We found that there is an additional attribute which can in fact be seen in the production version BW content infoobject's attribute tab. However the infoobject appearing in the "attribute" tab is not present in the production system. Hence we have collected the attribute, infoobject and all dependent transformations via transport connection. Hopefully this should work on transport.

      We were also wondering the root cause of the changed status in production as we couldn't find a reference point of a transport movement for the particular infoobject.