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.

Similar Messages

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

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

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 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

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.

Problem in formula:value getting round off

Hi All,
I need to divide 2 keyfigures and fill it in one keyfigure..
What i am doing , In transformation i have 2 fields in datasource one is value and other is quantity and i am mapping these 2 fields with one keyfigure in ODS..
I am creating formula in rule in which I am dividing value by quantity (value/quantity) but when i am running DTP and loading data the value in my keyfigure is coming after rounding off... like
I have value 4,311,781.58 and quantity 16,200.000 , if i divide i should get 266.159
but in my ODS this value is coming as 266.16..
Please advise how to remove this roundoff functionality...
Regards
Shweta

Hi shweta,
You have two options in this case.
1. Go to your created key figure. After clicking on change go the tab 'Additional properties".
There you can see Decimal Places under business explorer. you can change the number of places if you know to what places you need the calculated value.
2. Go to your created key figure. After clicking on change go to the first tab Type/unit and change your data type to FLTP- Floating point number.
Hope it helps.
Thanks,
Rahul

Round off error?

Hi,
I'm playing a little bit with the trial version of Numbers, just to see if my good old Ti is still capable to run it properly before buying a full license of iWorks.
By the way, it seems like there's some kind of round-off error. Try to build a series as follows: enter -10 in to a cell, then let Numbers build the series using the usual formula "previous cell value - 0.1". Apply a format so that only two decimal values are visible. Drag the formula and build twenty values (just to have some values). Now use the previous series and calculate its squared values. Then select some cells in the squared values column, starting from the first one: as soon as you include the squared value of -9.3 in the selection you will see that the data inspector will show a min value equal to 86.4900000000001 , which should be the squared value of +/- 9.3.
Now, try to subtract 86.49 to that cell and you will see that the result is not exactly zero: you can try to calculate the inverse of it and, instead of an error, you get a very big (actually, not that big!) number.
You can easily reproduce this weird behavior if you open Calculator and calculate the squared value of 9.3: until you set the precision up to 14, you get the correct value, you select precision >= 15, you get the round off value.
So, it seems it is not a Numbers only related problem.
Just for the record, I've just calculated the same value into Octave, and the result is correct (and different):
86.4900000000000 (Octave)
86.4900000000001 (Numbers)
Yet not so serious, this kind of "numerical noise" might lead to annoying issues...

HI SIR,
WE CREATED ONE PO .IN THAT PO ITEM NO2 SHOWING NET VALUE AS 11.63 FOR MATERIAL CS PLATE WHER AS ITEM NO 5 SHOWING NET VALUE AS 11.62 FOR SAME MATERIAL AND SAME PRICING CONDITIONS.
Hi ,
Please check in item conditions whether have you entered discount conditions in line itenm 5.
Regards,
Vijay

Need rounding off value for partial Goods receipt

Hi,
My requirement is that the PO value,PO tax value ,GR value and Invoice value(IR) should get rounded off.
When I am using the PO value which is rounded off in PO, but at the time of posting partial goods receipt the value for the GR/IR clearing or the stock value is not getting rounded off for these G/ls.
What should I do for this to get the rounded off values in GR.
Regards,
Goraksh

Hi Goraksh,
The problem is that the pricing (incl. the rule 17) is not normally called at the time of GR. As Jürgen wrote, the system just uses the "net value" field of the PO.
I have however a "wild" idea. If the price in the PO comes from the info record or from a contract (and not changed manually there), then you can set the "pricing date category" = 5 there, meaning "GR date". This causes the pricing to be called again at the time of GR and your formula 17 will fire.
The side effect of course is that the price that you had in the PO, printed and sent to the vendor will not be binding: if you change the PIR price before the GR, the GR will be posted to the new PIR price, despite the fact that the PO printout showed something else. So the question is if the price printed on the PO is indeed binding in your business case - in many business cases it is the current vendor price that matters for the billing by the vendor, not the one that you prined on the PO. For such business cases you should have had pricing date category 5 anyway...
BR
Raf

Using round off function in where clause

Hi All,
I'm trying to use round off function in where clause, I seek help in completing this script.
WITH CR_Details AS
(Select
request_id,
parent_request_id,
fcpt.user_concurrent_program_name Request_Name, phase_code, status_code,
round((fcr.actual_completion_date - fcr.actual_start_date),3) * 24 * 60 as Run_Time,
round(avg(round(to_number(actual_start_date - fcr.requested_start_date),3) * 1440),2) wait_time,
fu.User_Name Requestor,
fcr.argument_text parameters,
to_char (fcr.requested_start_date, 'MM/DD HH24:mi:SS') requested_start,
to_char(actual_start_date, 'MM/DD/YY HH24:mi:SS') ACT_START,
to_char(actual_completion_date, 'MM/DD/YY HH24:mi:SS') ACT_COMP,
fcr.completion_text
From
apps.fnd_concurrent_requests fcr,
apps.fnd_concurrent_programs fcp,
apps.fnd_concurrent_programs_tl fcpt,
apps.fnd_user fu
Where 1=1
and fcr.concurrent_program_id = fcp.concurrent_program_id
and fcp.concurrent_program_id = fcpt.concurrent_program_id
and fcr.program_application_id = fcp.application_id
and fcp.application_id = fcpt.application_id
and fcr.requested_by = fu.user_id
and fcpt.language = 'US'
and fcr.actual_start_date like sysdate )
     select crd.*
     from CR_Details crd
     where Run_time <> '0'
     AND wait_time <> '0'
GROUP BY
crd.request_id,
crd.parent_request_id,
crd.fcpt.user_concurrent_program_name,
crd.requested_start_date,
crd.User_Name,
crd.argument_text,
crd.actual_completion_date,
crd.actual_start_date,
crd.phase_code,
crd.status_code,
crd.resubmit_interval,
crd.completion_text,
crd.resubmit_interval,
crd.resubmit_interval_unit_code,
crd.description
Not sure about the GROUPBY function referencing the "crd." .

Hi,
The best thing for you to do is start over. Start as small as possible, then take baby steps.
Pick one of the tables; fcr perhaps, and write a query that just uses that table, like this:
SELECT    *
FROM       apps.fnd_concurrent_requests     fcr
WHERE       fcr.actual_start_date          >= TRUNC (SYSDATE)
AND       fcr.actual_start_dt          < TRUNC (SYSDATE) + 1
;(I think this is what you meant to do when you said "... LIKE SYSDATE".)
Make sure this little query gets credible results. When that tiny query is working perfectly, add another line or two. You can cut and paste code from what you posted, if that helps you.
If you get stuck, post the last version of your code that worked perfectly, and the latest version (only a line or two bigger) that has the problem. Describe what the problem is. If you get an error, post the complete error message. In any event, post CREATE TABLE and INSERT statements for all the tables and columns needed to run the query, and the results you want to get from that query.
When you post any code, format it, so that how the code looks on the screen gives some clues about how it is working.
When you post any formatted text on this site, type these 6 characters:
\(small letters only, inside curly brackets) before and after each section of formatted text, to preserve spacing.
If you going to use the AVG function in the sub-query, then you probably need to do a GROUP BY in the sub-query.
If you're not using any aggregate functions (like AVG) in the main query, then you probably don't want to do a GROUP BY in the main query.
I know this is a lot of work. I'm sorry. If there was an easier way, I wouldn't ask you to do all this.

Condition type: DIFF-Rounding Off

Dear Colleagues,
The condition type DIFF-Rounding off is not woring in sales order.
Config details as follows.
1. OB90->Respective Company Code, Currency & rounding unit of '5' is being set in this transaction.
2. Define condition type DIFF via Transaction V/06. This condition type is maintained as "Group and Item Condition".
3. Included the condition type DIFF in the pricing procedure:setting are as per standard Reqt = 13, Caltype = 16, BasType = 4.
Two issues noticed:
1) In the sales order: DIFF is determined at item level and header level as well but value of DIFF shows "Zero".
2) Crdit memo: DIFF was not determined.
In both the cases Net value + Tax was in decimals, supposed to round off.
Could anyone help what needs to be done or missing data.
What exactly the functionaly of DIFF condittion type... Does it round of Net value + Tax or each condition value .
Thanks & Regards,
Vamsi P.

Further, you can refer following SAP notes for your understanding and reference:
- Note 0022963
: Rounding problems in condition basis
- Note 0080183
: Rounding
- Note 0130742
: Roundings in subtotal lines
- Note 0154789
: Roundings in subtotal lines, part 2
- Note 0311135
: Rounding errors of condition value
- Note 0886532
: Pricing: Displaying and rounding numbers
- Note 1481061
: Rounding Customizing in SD
Regards
JP

Rounding off Miro Values

Hi ,
I having problem in VAT round off during MIRO. We have created PO +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 ZTAXIN , in the tax pricing proceedure i have made requirement 13 & call type 16 for VAT condition type.
If i am doing 13 and 16 then vat is not calculating in PO
I want the decimal should be rounded to the nearest cost.

Hi,
What I understand that you want to roundoff the amount during invoice posting. If my understanding is correct then please set tolerance limit for BD. While posting invoice fill the Invoice Amount (Basic Data) as 100 instead of 100.13
Now 0.13 will be posted to GL account maintained in OBYC-DIF

Exchange rate and GST round off differences

Hi,
When we create a invoice with tax then some times the vendor invoice tax amt may differ from the tax amt calculated by our system. This may be due to the rounding differences. So how to handle these kind of payments?
Can any one pls explain me the procedure for handling the exchange rate differences.
Thanks,
Sravanthi.

Dear Sravanthi,
The difference is not because of the rounding off. Rounding off differnce come only till nearest rupee. And that is acceptable. But in your case I think the difference is coz of the exchange rate maintained in the system. If you maintain the exchange at which the vendor invoice is preapared then i think ur problem may get resolved.
Also execute F.05 - Valuation of open items in foreign currency, before you run the payment transaction.
Hope this will help you.
Regards,
Ajay

Invoice Amount Rounding Off

Good Day.
Is it possible to have my selling price have 2 decimal places, but the Invoice amount will be rounded of to hundreds, only for a specific currency?
Example:
Price: 123.45 Yen per 1 pc
Invoice Amount: 123.00 Yen <-- rounded off, does not require decimal place
Let me know.
Best regards,

hi
not a problem.
you need to maintain prices for your product with 2 decimals in VK11 so that this brings 2 decimal pricing in sale order.
for rounding off in invoicing activate 'round off' condtion type to the nearest yen either up or down.
hope this is useful to u.
suresh

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

Round off problem?

Similar Messages

Maybe you are looking for