Currency Conversion Round-off problem

Hello
My customer is in import business.
When a journal entry is made in Dollar it is converting into Indian Rupee (local currentcy), which is correct
but it is not rounding off. Also user cannot change it mannualy to adjust the roundo-off figure
Is there any solution to this
Regards
Indrajit

Hello Indrajit,
What is your rounding setting for currency?
Thanks,
Gordon

Similar Messages

Currency Conversion Cuts off at 10 decimal places

Hello all,
When doing currency conversions the database cuts off the data two the 10th decimal place. I need to be at 12 decimal places. In the database the setting is set at decimal(25,10). Is there a way to change it so the database will go out to more decimal places?
Thanks for your help
Steve

It is possible to change the format to accept larger values, however this change will only impact any newly created Applications.
To change the default, open Administrator and select "Set Application Parameters"
Add the KeyID "SIGNED_DATA_FORMAT" and for the Value enter the total number of digits and the number of decimals, ex: "20,15" would indicate 20 digits to the left of the decimal and 15 to the right.
Click on Update.
Any new Application created will now use this new value for the Signed data column.
I hope this helps in answering your question.

GR for PO in forex resulted in currency conversion rounding difference

Hi,
I have created a PO in foreign currency and when I perform a GR in MIGO, it created the following 4 FI postings:
1) DR Stock - Amount in Forex, Amount in Local Curx
2) CR GR/IR - Amount in Forex, Amount in Local Curx
3) DR Rounding Diff 0.00 in Forex, 0.01 in Local Curx
4) CR Rounding Diff 0.00 in Forex, 0.01 in Local Curx.
Below are the information for the PO item:
Quantity = 350
Unit Price in EUR = 10.39. ==> Amount in forex = 350 * 10.39 = 3,636.50
Conversion rate = 10.61 ==> Amount in local curx = 350 * 10.39 * 10.61 = 38,583.265 rounded to 28,583.27.
Line 1 & line 2 ==> Rounded amount = 28,583.27.
Question: Why is the additional lines (3) & (4) being generated ?
When I did the MIGO posting, the system ask for the additonal account keys PRD and KDM in OBYC which I have supplied with "Rounding Diff" Account.
We have tried with different quantities and this problem so far only happens when the quantiy = 350. (Incidently, the rounding diffence for quantity 350 is exactly 0.005 and the same rounding difference of 0.005 is also applies to quantity 1050, 1750, 2450 etc at every 700 units increment; BUT the 0.01 rounding difference only happeded for quantity 350. Very strange ??)
Additional Info:
No special rounding rules is configured in the system.
Please advice.
Thanks and regards,
Hu Ghee.

Hi Pankaj,
Actually, your suggestion worked. It was jus that when I went to the OMRW screen earlier (even before I posted this message), I saw that the setting was "Blank" and thought that it meant "Not activated" whereas what I need to do was to set it to "No" for no exchange difference.
TQVM.
Rgds,
Hu Ghee

Round off problem in unit of measurement

Dear Experts
We are in SAP 4.7 , we are having more than 12 plants using same client.
One of our plant requirement we were changed the UOM 'Nos' with 3 decimels allowed.So where ever we not useing decimel places we have to use UOM as 'EA' (each).This is dont have any decimel places.
Now we are in implementation project for our one more new plant in same client. But for them we are going to introduced Batch specific unit of measurement. Base unit of measurement is KG and Batch specific UOM is EA.
All sale material have both unit of measurement , inward or production posting in KG and we will create batch number. We will enter the coversion value of how many quantity per kg for each batch.This will be in 'EA'
While i'm doing transfer posting or consumption or sales for the material in UOM 'EA' , it is coming with 3 decimel places.
If the same UOM 'EA' in normal condition (without batch specific UOM) it is working correctly.It is getting roundoff correctly.
Please help me out on this.I need the consumption should not be decimel places for UOM 'EA'.
Suresh

Hi Senthilkumar SD,
You have not read the thread before posting.
It quite clearly states that the UOM EA already has NO DECIMAL PLACES.
Quote "<b>we have to use UOM as 'EA' (each).This is dont have any decimel places."</b>
It is good to see lots of people trying to help and so I am pleased to see you trying, but it really doesn't help if you haven't read the question before posting the answer.
Steve B

Round off problem?

A ColdFusion program is trying to store a value or 0.25 into a column of type decimal(11,6) of SQL Server table but 0.0000000 is getting stored. 0.50 is getting stored at 1.0000000. This started happenning after using cfqueryparam. Maxlength is 17.
What am I doing wrong?

Was using cf_sql_decimal. Numeric didn't workeither but float did.
Why is this?
Thank you very much.

Foreign Currency rounding off while conversion

Hi All,
I am experiencing a scenario while foreign currency conversion.
I have searched for a solultion but i am unlucky to find one regarding this problem.
The scenario:
Example:
Foreign Curr | Value | Rate | SAP converted Local Curr(Yen) | Act Con Value(Y)
Euro | 1210Eur| 127.99Y| 154868Y | 154867(-veRound Off)
Is there any setting where you can round off the converted amount to its negative whole amount?
I have searched all the setting in Foreign Currency transactions(OB52,OB59) but couldnt find.
Hope i can get a solution.
Regards
Andrew

Hi
Reason and Prerequisites
u2022Your tax country is Slovakia
u2022You billed an order with several items in foreign currency,
u2022where the exchange rate factor between foreign currency and local
u2022currency is very large or very small.
u2022The accounting document created during the billing has a tax line item that contains incorrect amounts in local currency
Solution
The solution is using the same solution as note 832477 and 32477 with the difference that the country is Slovakia. For other countries you should put the variable L_LAND1 to the string that represent the country.
Limitations:
The solution will NOT lead to a recalculation of taxes in local
currency. However, it will serve to minimise any rounding differences
which may arise from converting the individual tax lines which are
transferred from SD to FI. In most practical cases, this should fulfill
the legal requirements, even though rounding differences may occur for
individual documents in special cases.
Regards
uday

How to turn off Currency Conversion within the execution of Fox code

Hi All:
We have a number of custom key figures defined in a Planning Layout.
We had wanted to define those fields as type CURR with 4 Decimals, however it appeared that 2 Decimals was the maximum we could specify. We therefore wound up using Type FLOATING POINT with 16 Decimals.
In some Fox code that calculates these custom key figures we then use a ROUND statement to produce values such as 3.2735000000000000.
When this Fox code executes in debug mode, I see a generated ABAP program running which includes Include programs RUPFGENTOP and RUPFGEN00. This program executes a Form F_00001, which is essentially the Fox code. Here I can see the ROUND statement producing the desired result. Right after though a Form TCURX_CONVERSION executes, which often reintroduces all 16 decimals, and I might get values, such as 3.2735000000000001 or 3.2734999999999998. These small fractions cause other issues later on in the process.
In our case we are not trying to convert an amount from one currency to another, so we don't understand why it even would try to do a currency conversion.
My question: is there any way to "turn off" this currency conversion routine?
Please advise - any suggestions would be most welcome.
Many thanks in advance,
Robert van der Kam

Hi Robert,
the solution suggested by Anass only works for key figures of type number. For key figures of type amout or quantity it is not allowed to change the number of decimals. Especially for amounts the number on the DB can only be intepreted correctly knowing the currency. Depending on the currency the value 1 on DB may be 100. This is why the FOX does the TCURX_CONVERSION, a better word would be currency shift since currency values have to be scaled depending on the values maintained in table TCURX. Since FOX needs one common number type for calculations the shift is neccessary.
This is the reason why amounts have only 2 decimals on DB, the real number of decimals comes from TCURX; no entry there means 2 decimals, i.e. not scaling is neccessary. This is why changing the number of decimals via domains might corrupt all data.
It seems that you are using release 7.0x, in releases 7.3x internally uses DECFLOAT data type, thus the 'problems' coming from binary arithmetic in ABAP FLOAT will not occur any more.
Regards,
Gregor

Problem in VAT Round off during MIRO

Hi Friends,
I having problem in VAT round off during MIRO. We have created PO with excise +VAT. VAT amount has been rounded off. After GRN, we are trying to post the Invoice in MIRO, the VAT amount shows with Decimal.
We are using TAXINN, in the tax pricing proceedure i have mede 17 for call type for VAT condition type. in OB90 we have mede the rounding rule as 100 for currency INR.
When i create the FI direct invoice using the same Tax code it works fine, but having problem in MIRO. I want the decimal should be rounded to the nearest value.
Can any one help me is there any standard set up where we can arrive this?? OR is it required any user exit??
Regards,
Deva

Check whether you can use the user exit function module KR_USER_EXIT_ROUNDOFF
Regards,
SDNer

Rounding off value problem in sales order

Hi All,
This is related to a rounding off value problem in sales order.
The problem is described by an example which is as follows -
Selling Price of Material A = Rs. 176.76
Excise charged = Rs. 21.80
Total Price = Rs.176.76 + Rs.21.80 = Rs. 198.56
On this total Trade Discount (ZDTD) having access sequence,is calculated at the rate of 4% = Rs. 7.94
But the condition base value after the discount is showing Rs.198.60 instead of Rs.198.56
I want the system to reflect the value as Rs.198.56 intact and it should not round up to the nearest value i.e. Rs. 198.60
Why is this happening? Is it possible to reflect the exact value? If yes what is needed to be done?
The commercial round off is activated for the DIFF Condition Type.
Looking forward to some valuable suggestions.
Thanks & Regards
Priyanka Mitra

Hi Ramesh,
Thanks for your suggestion but the problem has been solved by me.
Regards
Priyanka Mitra

Problem in Routine after rounding off the condition value

Dear all,
      I have attached the routine for rounding off value for condition value for T.Code va02. Routine is working fine but the problem is after the execution of routine it goes in some standard program LV61AA55 where again the rounded value gets changed . Maximum points will be allocated ..
Thanks anr Regards

FORM FRM_KONDI_WERT_925.
*{   INSERT         D01K911062                                        2
data : wa_xkomv like xkomv,
        v_kwert like xkomv-kwert,
       W_INDEX TYPE SY-TABIX.
read table xkomv into wa_xkomv with key kschl = 'JIN6'.
W_INDEX = SY-TABIX.
v_kwert = 1 * wa_xkomv-kwert / 100.
V_KWERT = WA_XKOMV-KWERT.
read table xkomv with key kschl = 'JHSC'.
CALL FUNCTION 'J_1I6_ROUND_TO_NEAREST_AMT'
   EXPORTING
     I_AMOUNT                 = v_kwert
   I_AMOUNT1                =
   I_AMOUNT2                =
   I_AMOUNT3                =
   I_AMOUNT4                =
   I_AMOUNT5                =
   I_EXADDTAX1_AMOUNT       =
   I_EXADDTAX2_AMOUNT       =
   I_EXADDTAX3_AMOUNT       =
IMPORTING
    E_AMOUNT                 = v_kwert
   E_AMOUNT1                =
   E_AMOUNT2                =
   E_AMOUNT3                =
   E_AMOUNT4                =
   E_AMOUNT5                =
   E_EXADDTAX1_AMOUNT       =
   E_EXADDTAX2_AMOUNT       =
   E_EXADDTAX3_AMOUNT       =
xkomv-kwert = v_kwert.
xkwert = v_kwert.
modify xkomv INDEX W_INDEX transporting kwert.
*}   INSERT
ENDFORM.

Small Differences Rounding Off in case of Payments in Foreign Currency

Hi all
I have a scenario wherein I want to round off the Foreign Exchange amount to the nearest Rupee. I.e when I am making a payment in Foreign currency, the amount in local currency appears upto 2 decimal places. However, I want the same to be rounded off to the nearest rupee.
E.g I am making a payment of USD 111 @42.1277 which comes to 4676.17 in the local currency INR. Now I want the system to round off the amount to 4676 at the time of the payment transaction itself. Is this possible through the RDF key in Forex Automatic Postings? If yes, then I already have an account assigned there but the system does not round off the amount.
Help would be highly appreciated.
Cheers
Hrishi

i'm not aware of that functionality.
But you can always add some logic into your fast formulas, so that the data is alreay rounded for cash payments, before you launch Prepayments.

Currency Conversion Problem

Hi frndz,
I am facing a problem with the currency conversion.
In my Report i have used two keyfgures.
One is directly calculating the values from R/3 side and converting into EURO.
the other one is calculating through update rule.
These teo keyfigures should have the same value.
In this update rule i have used one function module "Convert into foreign currency".
This function module is calculating the value correct for all other currency only in Korean(KRW)currency i am getting probelm.
Like R/3 side value converting in EURO in coming as
507.35
and through function module value is coming as 50,736.00.
Please if any one having this problem or any one could suggest some solution then it would be great help.
I have also tried the solution of deleting the values from SPRO but still the problem is there.
Thanks in advance

Revab,
The admin may delete the record for KRW from TCURX table.
BUT, it may affect the other applications. It should be carefully considered.
Though, after deletion end users may check if theirs applications results with regard to KRW have been changed.
If yes, then the record in TCURX may be added again.
If not, then it might be a solution. Though, not recommended.
Best regards,
Eugene

Problem with ENTITY FX TYPE in Currency Conversion

Hi Experts,
I have a problem regarding currency translation. I tried to use the property FX_TYPE so as to use the value in this as filter in the ENTITY FX TYPE field of the currency conversion table. I want some rules to apply only to specific entities so I used this filter but what seems to be happening is that I doesn't seem to filter it. It still applies to other entities as well thus I get wrong translation. I validated it by removing all other rules except for the ones that's being used by the entity I am analyzing and my values translation is OK but when I put the other rules again, which I have already filtered to run on specific entities only using the FX_TYPE property, my translations are wrong again. Does ENTITY FX TYPE really work or I'm just missing some set up?
Thanks,
Marvin

Hello Martin,
Could you solve this issue, Im having the same problem.
Im trying to use this functionality but it seems that it does not apply the filter. When I run the currency convertion it stills run the business rule I have configure for all the other entities.
Best regards,
Aldrin Liendo

Problem in currency conversion rate

Dear Experts,
I'm facing a problem in client place , here when the Sales invoice is posted it shows wrong currency conversion rate, whearas In excise invoice its showing correct conversion rate which I maintained at OB08. In customer master also exchange rate given correct one.
Plz guide me a solution.

Can you give us more details?

Rounding off currency value

Hi all,
       Is there a function module to round off the currency value to nearest 0.05 , ie. if the currency value is 10.63, it should be rounded off to 10.65 and when it is 10.68, it should be rounded off to 10.70?
      If yes, could you please let me know?
      Any help in this regard is appreciated.
Regards,
Partha.

hi,
try this out.here is the sample program.
pl look into my modified program,
i am assuming your requirement is like
if the last digit in your value is < 5. it should be rounded to 5.
like 10.23 should come to 10.25
& if the last character value is > 5 , it should be rounded to next value with 0.
    10.67 should be 10.70
    10.98 should be 11.00.
with this assumption, i developed this small code. let me know, if i am wrong.
regards
srikanth
DATA : V_CURR TYPE VBAK-NETWR,
       V_CHAR(10) TYPE C.
V_CURR = '10.67'.
WRITE V_CURR TO V_CHAR.
CONDENSE V_CHAR NO-GAPS.
DATA : V_STRLEN TYPE I.
BREAK-POINT.
V_STRLEN = STRLEN( V_CHAR ).
IF V_STRLEN <> 0 .
V_STRLEN = V_STRLEN - 1.
IF V_CHAR+V_STRLEN < '5'.
    V_CHAR+V_STRLEN = '5'.
    V_CURR = V_CHAR.
ELSE.
    IF V_CHAR+V_STRLEN = '6'.
      V_CURR = V_CURR + '0.04'.
    ELSEIF V_CHAR+V_STRLEN = '7'.
      V_CURR = V_CURR + '0.03'.
    ELSEIF V_CHAR+V_STRLEN = '8'.
      V_CURR = V_CURR + '0.02'.
    ELSEIF V_CHAR+V_STRLEN = '9'.
      V_CURR = V_CURR + '0.01'.
    ENDIF.
ENDIF.
ENDIF.
write :/ v_curr,
         v_char.
added modified code.
Message was edited by: Srikanth Kidambi

Currency Conversion Round-off problem

Similar Messages

Maybe you are looking for