Difference in V_TCURR between EHP5 and EHP6

[Former Member]

Hi,

We recently upgraded our system from ECC6 EHP5 to EHP6.

We have a table maintenance of V_TCURR.

In EHP5 system, recording routine is set to "Standar recording routine",

in EHP6 system, recording routine is set to "no, or user, recording routine".

I wanted to know, weather SAP has done this changes in new version EHP6 ?? If yes, why ??

If this is not a SAP chagnes, then why this difference in both version.

I have checked, there is no chagnes in this view V_TCURR in any of the system.

Also , this object is not registered and no access key have been taken for this object.

Thanks.

Khushboo

[Former Member]

Hi,

There are many ways to find it.

go in se03 in your system and then give below details.

Search for Objects in Requests/Tasks

PGMID  R3TR Obj VDAT V_TCURR

This will show you what all changes are done on the V_TCURR.

Or go in Sm30 and give V_TCURR and then display ---> utility and then change log.

Thanks

Rishi Abrol

[Former Member]

Thanks Rishi,

I checked in SE03 and SM30, but I couldn't find any fruitful.

Since there is nothing found in above Tcodes, and also no manual modification using access key have been done,

It seems that SAP has changed "no, or user, recording routine" to  "Standar recording routine".

I want to confirm, weather this is a SAP change or not. If it is SAP changes, from where we can get the documentation on this?

Thanks

[Former Member]

Hi,

I could find the below changes

ISB1_BSK             IS-B: Basis, kritisch                                        SAP          10.09.2003 Piece List           Modifiable

ISB_BSK_03           IS-B: Delta-Stückliste Basis, kritisch zu F4.02              SAP          10.09.2003 Piece List           Modifiable

P45A_C_PCO           Command File Kosten (olpr -> Kosten)                         SAP          08.09.1998 Piece List           Modifiable

SAPK-731BTINSAPBASIS SAP_BASIS 731 Update: Table entries                          SAPBASISUSER 24.11.2012 Delivery Transport   Released

SAPKE60021           SP 21 for SAP_HR 6.00                                        SAP          20.11.2007 Delivery Transport   Released

SAPKE60028           SP 28 for SAP_HR 6.00                                        SAP          26.06.2008 Delivery Transport   Released

SAPKGEF04G           EA-FINSERV 600 : Add-On Installation                         SAP          25.08.2005 Delivery Transport   Released

And they all are sap changes. did you get this list in your system.

Thanks

Rishi Abrol

[Former Member]

Hi Rishi,

Yes, I got this list in both EHP5 & EHP6 system.

Below entry is not there in EHP5, but it is there is EHP6.

SAPK-731BTINSAPBASIS SAP_BASIS 731 Update: Table entries SAPBASISUSER 2013/10/02 Stückliste für Patch Freigegeben

Inside SAPK-731BTINSAPBASIS, I can see V_TCURR under node "View Maintenance: Data".

My understanding is, whatever is there in SAPK-731BTINSAPBASIS, is SAP addition in EHP6.

If so, there are only data changes in V_TCURR, but I could not find any technical changes, i.e. change of radiobutton from "no or user recording routine" to "standard recording routine".

so, how can i confirm that this radiobutton changes is due to SAPK-731BTINSAPBASIS ??

Thanks.

[Former Member]

Hi,

Yes i can see the data changes as there are come currency exchange changes.

Can you provide me more details about the radio button and than i could search more.(Screenshot of the button that you are talking about.)

Thanks

Rishi Abrol

[Former Member]

Thanks Rishi,

Below screenshot from EHP5 system.

Below screen shot form EHP6 system.

I want to confirm weather this is a SAP change or not.

Also, if it is a SAP changes, we need something (like screenshot or sap release note) which can say that this is a SAP changes and not customer modification.

Thanks.

[Former Member]

HI,

Could find some of the info related to this.

1487401 - Settings for customizing market data tables

1635841 - Table V_TCURR is not transportable

Thanks

Rishi Abrol

[Former Member]

Thanks Rishi,

I too have gone through these notes.

It gives me a solution of my problem, but I want to know root cause for it.

Please help.

[Former Member]

Hi,

What i can think off as a part of the first note some of the team would have created the table and would have created it with no option and when this note or EHP6 would have applied sap would have activated the table with usual default settings.

If you see all the maintenance view are created with standard routing option in sap.

Thanks

Rishi Abrol