How to know how the upgrade was done ?

[hagit]

Hello experts,

In our system the version of a standard class /UI2/CL_JSON  in DEV is different from the version in the QA.

There are not versions in the DEV.

How can I know how the upgrade was done in DEV?

Maybe a note was implemented?

Thank you in advanced

Hagit

[RaymondGiuseppi · Accepted solution]

Look for object R3TR CLAS /UI2/CL_JSON in transaction SE03 in both systems.

(if a SAP upgrade, look also at transactions such as SAINT if allowed)

[hagit · Accepted solution]

@RaymondGiuseppi thankyou for your answer. I looked at object R3TR CLAS /UI2/CL_JSON in transaction SE03 in both systems and it is the same. There is no log for the transports. I looked at transaction SAINT (goto=>import history => OCS package) – it is the same in both systems. Do I have to look at another section of SAINT? My aim is that in QA the version of /UI2/CL_JSON will be the same as in DEV.

[hagit · Accepted solution]

@RaymondGiuseppi I cannot paste print screen into a comment, so I pasted it into an answer

[RaymondGiuseppi · Accepted solution]

creating a short comment

then updating it 

[RaymondGiuseppi · Accepted solution]

• Did you find any transport request(s) related to some subobject(s) of CLASS (LIMU CPUB, METH, CINC, etc.)
• Are there some Repaired Objects in quality system (check with SE03) 

[hagit · Accepted solution]

@RaymondGiuseppi

Thank you for your answer.

• creating a short comment then updating it – thank you.

•  Did you find any transport request related to some subobject of CLASS (LIMU xxxx) – In DEV I found 2 transports that are not in QA. Those transport do not have log . How can I know who creates them (maybe I can ask him)?

• Are there some Repaired Objects in quality system (check with SE03) – In DEV I see 2 repaired classes (but not  /UI2/CL_JSON).

  In QA I do not see any repaired classes

  thank you  

[RaymondGiuseppi · Accepted solution]

Check the exact level of SP in both systems, 12 (may 2015) vs 17 (december 2016) ?

NB: Thats pretty old?

[hagit · Accepted solution]

@RaymondGiuseppi

What do you mean by "exact level of SP" ?

This what I see:

In QA

In DEV

It is very old but I just used that class now.

[RaymondGiuseppi · Accepted solution]

Basically, your systems are not at the same service package level, so the class or some of its components are different.

It seems someone forgot or chose not to complete an upgrade a few years ago...

• until SAPK-74012INSAPUI (2015) complete
• SAPK-74013INSAPUI to SAPK-74017INSAPUI (2016) in progress

[hagit · Accepted solution]

@RaymondGiuseppiHow can I make only the version of the class in QA the same as in DEV? (not the whole SP)

[RaymondGiuseppi · Accepted solution]

You could identify the OSS Notes that changed the class, but as your development system is already at a higher SP, you cannot implement them in that system.

So you could create a Transport of Copies request for the whole class, but first do a where-used search to make sure that no other Workbench object that uses this class will fail after the import, you would need to transport those changed objects as well, and again look for the usage case and add new objects to the request until no more objects are added.

[hagit · Accepted solution]

@RaymondGiuseppi  I will try and let you know the results

[RaymondGiuseppi · Accepted solution]

Until the last SP is transported into production, you're in the middle of an SAP upgrade. It's customary to keep development to a minimum during these phases, and it's even worse if you only have one development system.

[hagit · Accepted solution]

@RaymondGiuseppi

I didn't understand if you're suggesting to move the class from DEV to QA and PROD or not. The need for the transfer arose due to development that I wanted to move from DEV to QA.

[RaymondGiuseppi · Accepted solution]

The correct way to do this is to transport the entire new SP to your entire system perimeter.

If you transport only part of the SP (such as simulating a simple OSS note implementation), you also have to transport every required object related to those changes, so the where-used search and much testing effort.

[hagit · Accepted solution]

@RaymondGiuseppi 

We decided to wait for the complete upgrade.

Thank you for your great & quick help.

Hagit

[RaymondGiuseppi · Accepted solution]

I think this is the best solution. We need to keep development to a minimum during these upgrade periods.