cancel
Showing results for 
Search instead for 
Did you mean: 

Unable to see History Version of object in QA, Preprod (SAP PO) systems

Former Member
0 Kudos

Hi Guys

Recently our EIS team(responsible for moving PO transport )moved PO transports to Pre-Prod prematurely.As result testing team were unable to do

testing in preprod environment.

Due to unavailability of version history of object in QA and Preprod, we had “clean up” transports in the Lower Landscape Dev environment and transport them to Pre-Prod.

While working with PO(single stack/7.4)observed that, when we moved transport through ChaRM(CTS+) sometimes version history of objects updated in QA/Preprod and sometimes only latest version updated.

My questions are whether below statements are true for SAP PO in QA/Pre-prod and Prod environments

In ESR - Always last date changed in Dev before transport is exported will show in QA, Pre-prod and Prod. So whatever last Deveopment box change date/time showing will show in QAS, pre-prod and prod.


In ID - Always shows the activation date and time in Dev, QA, Pre-prod and Prod. This date/time is particular to that system for object activation.

Accepted Solutions (1)

Accepted Solutions (1)

bhavesh_kantilal
Active Contributor
0 Kudos

So here is how the Version Management for Transported Objects work.

ESR


  • You started Development and made 2 activation, V1 and V2.
  • V2 is now transported to QA. You will see only V2 in QA.
  • Now in Development you made additional change and activated the same V3.
  • Transport V3 to QA,
  • You will see the version management in QA show V2 with active version as V3.
  • In Development, make 2 more activation, V4 & V5. V5 is transported to QA.
  • In QA, you will see, V2, V3 and V5.

Basically the target environments will have version management for the version transported.

ID

  • Same as ESR but also includes any local direct changes done in the QA Integration Directory.

Regards,

Bhavesh

Answers (2)

Answers (2)

Former Member
0 Kudos

Thanks Harish and Bhavesh for quick responses.

  • Harish:- Yes it is true. Only the transport version will be shown in QA, Pre-prod and Prod.

Does it mean that only last version updated/activated and transported in DEV should be reflect in QA/Prep rod and Prod ?

  • Bhavesh:- I have seen two different characteristics in SAP PO/7.4 where sometimes, activated and transported object(from DEV) showing in QA followed by Preprod and Production and sometimes, only few activated versions updated.

Here are the updates across three systems for one object in ESR(PO/7.4) where history version updated.

DEVQAPreprod
V1Sep 24, 2014 2:03:12 AM CreatedMar 25, 2016 10:41:12 AM CreatedMar 25, 2016 10:41:12 AM Created
V2Feb 26, 2016 2:16:45 AM ChangeJun 21, 2016 2:18:47 PM ChangeJun 21, 2016 2:18:47 PM Change
V3Mar 25, 2016 10:41:12 AM ChangeJun 21, 2016 3:24:05 PM Change
V4Jun 21, 2016 2:18:47 PM Change
V5Jun 21, 2016 3:24:05 PM Change

My only impulsion here is , if we moving through CTS+, post activated across all environments(DEV/QA/Preprod) in few, it shows history versions of object and in few scenarios only last updated/activated and transported from DEV to QA/Preprod/Production.

Does it something bug in CTS+ tool or SAP PO(7.4 single stack) ?

Thanks for your patience and understanding.

Former Member
0 Kudos
Harish
Active Contributor
0 Kudos

Hi Rahul,

The behavior is same as earlier version or any transport mechanism (File, CTS+ etc.).

If you observe the object  created on 25th Sep but the version v3 created on Mar 25, 2016  is moved to QA and Pre prod. So QA and pre prod only has March 25 as first version.

also the version V4 and V5 moved to QA, while only V4 is moved to Preprod.

Hope this is clear.

regards,

Harish

bhavesh_kantilal
Active Contributor
0 Kudos

This is inline with what I had mentioned in my previous response. Only selected versions of the objects have moved from Dev  to QA / Pre Prod and only those versions are visible. You should also be able to check in the Transport History the same.

There is no difference between CTS+ and File Transports and nor is this a bug. This is a valid way of working.

In your example,

  • V3, V4 and V5 were moved to QA and hence they are visible in QA.
  • V3 and V4 moved to pre prod and hence they are visbile in pre Prod versions. If V5 is moved to PreProd, you will then see V3,V4,V5 in PreProd.
  • V1 and V2 will not be visible in both QA and Pre-Prod and V1 and V2 were never transported to those systems.

The Target Systems only keep track of versions of "active" objects that were imported. A TPZ file only contains the active version object details and not its entire history..

Harish
Active Contributor
0 Kudos

Hi Rahul,

In ESR - Always last date changed in Dev before transport is exported will show in QA, Pre-prod and Prod. So whatever last Deveopment box change date/time showing will show in QAS, pre-prod and prod.

-->> Yes it is true. Only the transport version will be shown in QA, Pre-prod and Prod.


In ID - Always shows the activation date and time in Dev, QA, Pre-prod and Prod. This date/time is particular to that system for object activation.

-->> this is not true, the ID behaviour is also the same.

AFAIK - The version history should be present in ID, but there might be some configuration parameter missing.

regards,

Harish