Currency Conversion Solution - is it safe?

[former_member246728]

Hi,

We have to change our currency in 2009. Now we use "YTL" as currecncy key in all SAP tables. But, our currency will change from "YTL" to "TL" in 2009. There will be no conversion between those two, only the name is changing. In other words, 1 "YTL" is equal to 1 "TL".

In order to solve this problem, consultants propose to change all "YTL"s to "TL" in all tables. This solution causes downtimes and it is costly.

I realized that the currencies mostly are in "WAERS" domain. Therefore, adding a custom conversion_exit to the domain "WAERS" will show all "YTL"s as "TL". In a separate test system, we repaired the domain and saw that most of the SAP screens are in "TL".

This solution is new and not applied before. So, we don't know its impact. Except some repairs in currency domains, would there be dangerous affects like inconsistencies in the tables?

Best regards,

Davut Culha

[Former Member]

Hi,

Changing in the domain field using the user exit only changes in the screens as output. But the in background its still sitting in your tables as YTL.Since the change of currency is valid for transactions after 2009.

I would suggest this as follows

Why dont you maintain one more currency 1TL = 1YTL ?

So that there is no inconsistencies , in future make sure all the transactions use TL rather than YTL.Let all documents dating upto 2009 using YTL be as it. If in case all transactions needs to be shown in TL then neways user exit would take care of it

Cheers,

KD

[former_member246728]

Hi,

We will not maintain one more currency because at that time we can see all the values in two currencies. It can not be acceptable for the reports. Our endusers want to see "TL" values after the 1st January, 2009.

In addition, keeping "YTL" values in the tables are not important because only developers deal with them. In other words, it is not important for the endusers how the values are kept in the tables (like the doimain "MATNR").

In short, we have only one solution which is to change the values in the tables. Or, we can use this conversion exit solution.

Is there a disadvantage of this solution?

Best wishes,

[Former Member]

Although the user exit would work fine, but in the customising we still are maintianing YTL as the Curency. isnt it !

In future( 2009 onwards) we still are maintaining the currency as YTL although the end user things its TL.

What i am trying to say is that, the user exit will not be able to perform both the below tasks..

Example

1) On screen - TL user exit converts it into YTL in background --> can be achieved by user exit

2) On screen input as YTL --user exit converts it and stores in TL --> how can this be achieved

In future we would want all data to be stored with currency 'TL'.

Cheers,

KD

[former_member246728]

The conversion exit is very simple and performs those two thisng. The code is below:

***************************

FUNCTION CONVERSION_EXIT_Z0000_INPUT.

if input = 'TL'.

output = 'YTL'.

else.

output = input.

endif.

ENDFUNCTION.

FUNCTION CONVERSION_EXIT_Z0000_OUTPUT.

if input = 'YTL'.

output = 'TL'.

else.

output = input.

endif.

ENDFUNCTION.

***************************

Users will see "TL" everywhere and input as "TL". But the actual values would be "YTL" in the tables. And it will be known as a technical detail.

[Former Member]

Hi

The right solution should be to get a convertion project from YTL to TL, just like a changeover project.

There's a std SAP tool to do that, but I think it's very expensive and only SAP can run this kind of tool.

So your problem is just only an output problem, so I think your solution is good and it should have any impact, because the systm still uses the old currency YTL, and the user will start to see TL insetad of YTL on certain date.

The problem can be only for the hystory, because after activing the convertion routine the old data in YTL can be shown with TL: if this isn't a problem for you, I believe there isn't other particular problems.

Max

[Former Member]

Hi,

Users will see "TL" everywhere and input as "TL". But the actual values would be "YTL" in the tables. And it will be known as a technical detail.

So will the information after 2009 be stored in YTL or TL. I believe we should store it in 'TL'.

I think you have the solution if you can address the endusers & Database's concern together

i.e.

Year DB Frontend

LT2009 YTL TL

GT2009 TL TL

Cheers,

KD

[former_member246728]

Hi,

Only the display solution is enough and good for us. We don't care about the actual representation like most of the other data. But, this problem is general in Turkey. Because, in Turkey all the firms running SAP see "TRY" and they will see "TRY" after the beginning of 2009. This is the solution offered by SAP.

I think the other firms also want to see "TL" although it is kept as "YTL" or "TRY". Therefore, maybe there should be some user exits, enhancement, or something else. In other words, SAP developers should provide some way to enter custom code for the domains and conversion exits without repairing the original SAP code.

What do you think of this?

Best regards,

Davut Culha