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

Similar Messages

Rounding off error between stock transport order and GR (Quantity)

Hello,
I would appreciate your help in an issue. Our customer uses stock transfer order in which a conversion rule was set. Since the transport company requires another unit, the purchase order is created in ton but MIGO is done with Megawatt Hour. SAP takes into consideration only three digits after comma. Therefore, a rounding off error occurs which can only be seen in MB52 but not in the transitsaldo MB5T. The difference or the missing quantity (i.e. 0,001 MH which is 0,0000xxx TON) can not be found and thus a GR can not be posted in MIGO either.
If you have any idea how to solve this or if there is any OSS message on this, please post on this thread. I am waiting for your comments.
Thanks,
Esra

Hi Ram Prasad,
The note you suggested is very useful. I need to download the correction. When I use movement types
557/558, I got the error that the transit saldo exceeded xxx MWH.
PO = TON
GI = 2,159 MWH
GR = 2,157 MWH which corresponds to 0,459 TON
Conversion rule= 1 TON = 4,7 MWH
Do you know how to book 0,002 MWH away with these scrapping mov.types? This quantity is missing and is not shown in MB5T because this list functions with TON as far as I figured it out.
Thanks a lot for your help.
Esra Nilsson

Csv round off error

I am getting all the values under the channel "calc G level" in the attached csv file as round off value when loaded in Table view in diadem.
Kindly help to solve this issue.
Solved!
Go to Solution.
Attachments:
bHard Brake.csv ‏54 KB

The CSV loader tries to guess the datatype of you column. So in your case it looks at the first lines and guesses int.
in newer DIAdem versions this was changed to guess double instead of int.
For DIadem 11.1 dataplugin ight be a solution.
If you have a lot of those files you can use a dataplugin to access them. In them you can switch the channel type to double and it would work out. If I remember right 11.1 already had the dataplugin wizard that makes generating dataplugins easy.
Hope this helps a little
Andreas

ROUND -OFF ERROR IN POs

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

PR to PO quantity rounding off

Hi Team
I am facing a peculiar error when i am trying to create the PO with respect to PR
I have created the PR for 1.130(one point one three zero) TO(tonnes). Now when i am creating the PO wrt to this PR then the PO quantity is coming as 2.000(1.130 is rounded off to 2.000)
now the system is populating ERROR as - Materials of requisition 10000012 item 00010 alr. ordered in full
Message no. 06076
If i change the PO quantity manually to 1.130 then the error will vanish off.
Please let me know how to get the same quantity(without rounding off) from PR to PO during PO creation wrt PR
Thanking you in advance
Regards
Shuban

Hi,
This just because of rounding value maintained for the material in the MRP1 view either 1000 or 2000 which results in creating PO of 2000 even though the PR has created requirement of 1.130 assume if your requirement is under 1000 then still when your creating PO it would create for 1000 because of rounding value of 1000 maintained.
If you donu2019t want this rounding value then remove it from Material Master, MRP-1view. Then the system will consider the order quantity from the purchase requisition during MRP run and same will flow in the purchase order. Hope this helps you.

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.

Rounding off differences for Vendor and Customer payment

Dear All,
Rounding off differences for vendor payment in T Code F-53 is giving the following error when I want to post.
Item category 06000 not allowed in accounting transaction 1000/0001
Message no. GLT2001
Diagnosis
The online document splitting is active in your system. Here, each document is assigned to a accounting transaction variant and each document row to an item category.
You determine for each business transaction variant which item categories can or must be posted here.
The following error occurred for the document you entered:
Item category 06000 in accounting transaction 1000, variant 0001 is not allowed.
System Response
The document cannot be posted.
Procedure
Check the document entered, the derivation of the business transaction variant, the derivation of the item category, and the assignment of the item categories to the business transaction variant.
Please advice
Regards
BIJUDAS

Thx for the quick answer Andreas. n further discussions we found that the actual requirement is to only have the payment history data for both the vendor and the customer only as a referece. I mean they dont want to have the actual accounts posted for historical data, since we have to anyway have a conversion for the GL accounts related data afterwards.
I hope i cleared what we want here. Do we have any way we can update the data in this case. Is there anyway we can have data stored in LIS possibly for such cases..
Any ideas

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

Web dynpro + adobe form decimal field round off

hello all,
I am now developing an application which is based on the SAP WebDynpro and Adobe form, but the application has an error, if one can help me to resolve the error, I will be very thankful.
The error is as follows, for a decimal filed on the Adobe form which is binded to a deicmal attribute of Webdynpro, if I get the value of the decimal field using the programming code as "context.nodexx.getAttribute("xx")", the decimal value is rounded off (e.g., 2.4 is changed to 2.0, 2.7 is changed to 3.0).
for example:In Web Dynpro, A node name is "TestNode" which has a type of decimalattribute named "TestAttr" , in adobe form a decimal field bind to the TestAttr . when i input 2.3 in adobe form, i click the button with code:
this.wdComponentAPI.getMessageManager.reportSuccess(this.wdContext.nodeTestNode.getTestAttr()+"");
the rusult is : 2.0
if i input the value 2.5 the result will be 3.0
Thanks All !

Hi,
there is a special display pattern to check for null values:
null{pattern}
Example:
null{'please enter a value'}
But I don't know if WDJ is really sending a null value. You can combine this with alternatives using '|' to separate alternatives.
Regards,
Juergen

Rounding off to 0.05 decimal

Post Author: masto123
CA Forum: General
Hi there,
I am tring to round off a field which is displayed in AUD currency as $23.43 to $23.45. I have tried the round function
round(,0.05) but I get an error. Is there any other way.
pls help.
regards
m

Post Author: yangster
CA Forum: General
If its a numeric value either a simple field or a summed field you should simply be able to format the number field and apply custom formatting to change it to 2 decimal places. If its a text field you can use totext(field, 2).but the problem with your formula is that the format is round(field, #places)# of places needs to be a whole number not a fractionround(field, 2)

CO assignment missing at at the time rounding off material in MIRO

Dear All,
Iam facing the problem with co object assignment missing at the time of MIRO,
>when iam posting miro with higher value than PO, it should hit rounding off of material(GL)
>it is hitting that, but it is not allowing to post into the rounding off gl, showing error like cos object missing.
>Here we r mapped setting in OKB9 with cost centers depends upon plant wise.
>if i assign in okb9 valuation area mandatory level(1), it is not allowing me to post,
>but if i assigh GL at main screen in okb9, instead of selecting valuation area mandatory(1),it is allowing me.
Please help me how to overcome the problem, is there any special setting or logic for rounding off material gl.
>That GL has cost element, cost center is in active,field staus group setting also correct,
Where else i have to check please guide me.
Thank,
chinni

HI,
Once you set valuation area is mandatory, then you need to do another setting in the same screen.
Select level 1 in the OKB9 initial screeen and double click on the second screen with header " Detail per business area and valuation area". There u need to enter the value with the combination of cost center and valuation area.
You will not have any issue once you do this setting.
Vijay

Rounding off a float to two decimal places

I want to make a function where I shall pass a float and and integer.
The float shall have to be rounded off to a value in the integer.
Can anyone please suggest how to round off a float.
E.g.: if the float is 12.56890 and I want to round it off to 2 decimal places, then it should be 12.57.
Regards
Hawker

I didn't mention any datatypes like float, double.True, but that is what the question is about, so you weren't answering the question. For a change.
As I mentioned, that was just a mathematical steps to round of the floating point value. (Not in any programming languages point of view).False. You didn't mention that at all.
This is the code for that in java.So here you are mentioning datatypes and floats for the same piece of mathematics that you have already been told, with reasons, doesn't work in floating point.
which seems to be working fine
Seems to. What evidence do you have that the float actually got rounded? As opposed to got displayed as rounded? Which is not what the OP asked for.
And of course all that code seems to do is round 0.01 to two decimal places, which again is not what the OP asked for.
For any remaining fans of this 'technique', please explain the behaviour of the following code:
     public static void     main(String[] args)
          int     count = 0, errors = 0;
          for (double x = 0.0; x < 1; x += 0.0001)
               count++;
               double     d = x;
               int     scale = 2;
               double     factor = Math.pow(10, scale);
               d = Math.round(d*factor)/factor;
               if ((d % 0.01) != 0.0) // if 'd' really has been rounded this should be zero
                    System.out.println(d % 0.01);
                    errors++;
          System.out.println(count+" trials "+errors+" errors");
     }

Unplanned delivery cost picking rounding off value in sap miro

Dear Experts,
I have configured unplanned delivery costs to be posted to separate GL account. I have set the default tax code also. In OBYC i have set the frieght and transportation GL account against UPF transaction key. Now even though the user is not entering any value in unplanned delivery cost field, system is automatically taking the rounding off values(manually entered by user to match the vendor invoice) from MIRO line item and is posting to the freight account.
Query -2 - while reversing the already posted MIRO document in MR8M the rounding of value which has been taken automatically in unplanned delivery cost is showing in the error message as :
"Balance is not equal to zero: 0.35- inr"
please refer below screen shot for the error message
Please suggest.
Regards
Chinmaya

please read my blog it explains how to close a question, just replying "closed" does not do really this job
How to close a discussion and why

Rounding Off TotalLC for Sales Order and Delivery

Experts,
Needs help, I'm using SBO2005B Korean Language. Korean money which is Won is so small that they don't have decimal. I need to round off all the linetotal into 0 decimal.
Example: if the linetotal is 45,900.80 is should display 45,901
or 32,765.40 it will display 32,756
thank you
Whiteman

Dear,
Please go to the administration->system initialization-> general settings -> display tab, you can set the Decimal setting in the field of "Decimal Places (0..6)"for either amount and price. Simply set it as 0.
You can also define a decimal setting for Korean Wan only, go to administration->set up-> financials->currencies, define a currency code for Korea Wan and set the decimals for it in the decimal field
following information about changing Decimal places for your reference
When decreasing the Decimal Places (under Administration -> General Settings -> Display for amounts, prices, exchange rates, quantities,
percentages, and units) you might come across with an error message when updating previous documents or when adding documents based on previous
documents.
just for you informaition In 2007 version the user will not be allowed to reduce the Decimal Places only to increase.
I also attached a note1102900 for your reference.
Wish the information is useful for you.
Regards
Apple

Issue in MODVAT Clearing Account and Rounding off of Excise.

I have one issue in MODVAT Clearing Account and Rounding off of Excise.
Example:
Material cost    100Rs.
Excise value
1. BED             10.5 Rs
2. ECes             2.1 Rs
3. HEces          1.3.Rs
At the time of GR
Material Ac Dr          100
     To GR/IR                        100
At the time of Excise Capture
We done the rounding of Excise value
RG23 A BED         11
RG23 A Eces          2
RG23 A HEces        1
   To MODVAT            14
At the time of IR . System create IR with reference of PO
GR/IR DR      100
MODVAT         13.9
    To Vendor         113.9
So here you can see that there is a difference of 0.1 in MODVAT account and hence we are crediting Vendor with the lesser amount here with 0.1 RS.
So we cannot reconcile the MODVAT Account
Less Payment to vendor by 0.1 Rs
So is there any solutions on that.
regards
Shayam
Edited by: Shayam_210 on Jan 3, 2011 7:08 AM
Edited by: Shayam_210 on Jan 3, 2011 7:09 AM

Hi,
Check the rounding setting in below:-
SPRO > Logistics - General > Tax on Goods Movements > India > Basic Settings > Maintain Company Code Settings
SPRO > General Settings > Currencies > Define rounding rules for currencies
Regards,
Gaurav

Round off error?

Similar Messages

Maybe you are looking for