on 09-13-2013 8:27 AM
Hi Travel Experts,
when we are uploading AMEX file details in SAP for the currency BYR(Belarussian Ruble) through T-code PRCC , we are receiving errors for employees
"Overflow during currency translation for currency BYR , Transactions were moved to Table PTRV_CCC for correction
What could be the issue here, can anyone help me here please?
Thanks in advance
Regards
Sriram
Hi Siram,
Please check your currency and exchange rate values. I suspect there's sth wrong with the multipliers. Some exchange rates are not for 1:1, but e.g. 1 Eur - 10000 Turkish lira
If those multipliers are wring - even opposite way round - you might get an overflow somewhere.
Also check the definition of BYR in your system to see whether the number of decimals expected is correct. Note that amounts are usually not stored as decimals, but in the smallest unit - the decimal point - if any - is set by the system dynamically depending on the currency definition.
Apart fron a real coding error somewhere, decimals and multipliers seem the most likely candidates for such an error.
Ah yes: working with Amex always requires thorough checks on the quality of the data they send. Thechnology is not there core competence.
Hope this helps you getting ahead a bit.
Kind regards
Sven
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Just to follow on from Svens very helpful reply, there are some very important corrections that can prevent these overflow errors, please make sure you have these also.
1734719 1712962
Also: 1757133, 1758685 & 1761635 (Last two solve a slightly different dump that can occur)
In addition, it is slightly off topic but we introduced some new logic for rounding differences (the class CL_FITV_ROUNDING which can be maintained with the constant NORND in V_T706_CONST) and you might like to take a look at that as improves the rounding logic when handling CC expenses
1766030 1731810 1712292
cheers
Sally
Hi Sriram,
Yes you have to check table TCURF for currencies translation rations and then table TCURR for exchange rates. From your screenshots I can see an entry in table TCURF for Exchange rate type 'M', FROM Currency GBP, TO Currency BYR which is fine but you need to have an entry from BYR to GBP however, in your screenshot it shows MYR to GBP and MYR (Malaysian Ringgit) is a different currency to BYR (Belarussian Ruble) . Please check this.
Thanks
Ankur
Hi Ankur, Sally,
I deeply apologize for putting the same question in the old thread. i just missed it. i am sorry for that.
Let me come to the issue , i do not have much idea on this exchange currency issues,as this is first
time for me. Please help me in this regard,
in the table TCURF : BYR to GBP and GBP to BYR maintained as from 01.01.2008 as 1: 1
In the table TCURR : GBP TO BYR
From BYR to GBP
in the table TCURN : i have attached file from my system and what has been maintained so far,
For all the currencies we have maintained as direct quotation only. i am still struggling here to get understood the things.
Could you please help me solving this, it would be really greatful and good learning experience for me
thanks
Sriram
Hi Sriram,
Have you tried what I mentioned in the locked thread below?
http://scn.sap.com/thread/3431779
Ankur
Hi
are you sure you are using the right rate type in TCURR? Check Travel Management global settings which rate type is used by travel management. Then check if TCUR* settings will fit to this.
In TCURF, you will find alternative rate type: (here: EURX)
If this is filled, TCURR will be read with rate type EURX, not with M. Normally BYR should not have alternative rate type.
TCURF must be filled both directions in a consistent way. TCURN not required.
Hi Ankur,Sven,Sally,Michael
Thanks for your superb inputs on this issue. now its working fine without any issue, i am able to over come the error.
Thanks a ton for your help on this issue
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
108 | |
12 | |
11 | |
6 | |
5 | |
4 | |
3 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.