Calculator continually gives wrong calculation

I was recently using my iPhone 5S to calculate grades for students on a test. Overall total points were 120 and I would subtract 42 points from 120 and my calculator would give me 77 each time. I cannot understand why it gave me this answer 3 times in a row. Anyone else having the same problem? Also how can I contact Apple so they know their calculator isn't functioning correctly?

With all due respect, it is far more likely you are inadvertently tapping the wrong numbers that it is the calculator app is randomly giving you the wrong results, particularly with a function that simple. But ... I'm not looking over your shoulder. You can report issues to Apple here: http://www.apple.com/feedback/

Similar Messages

R/3 archiving - wrong calculated field on 2LIS_02_ITM extractor

Hello.
An info and a question for who developed an archiving with r/3..
We have found an issue related with the R/3 archiving and LIS_02_ITM.
A calculed field (Delivery Quantity Variance in %); (field name = MABW) (you can see it at http://help.sap.com/saphelp_nw04/helpdata/en/58/f6383fdb800804e10000000a114084/frameset.htm )gives wrong data.
The MABW is calculated using MSEG infos.
MSEG infos were archived (and deleted), so, the calculation goes bad and returns wrong value.
In front of the archiving process, we potentially will find problems due to the standard extractor behaviour.
Have you ever noticed the same behaviour because of the wrong calculation onto the fields?
thank you in advance for your cooperation...!
Dieguz
The details are the following :
We have a R/3 PRODUCTION system (called MP0), connected with three BW
ones (MP2,
MP4, AP4).
Someone performed an R/3 data archiving, using an archiving tool
(IXOS).They archived the data with a one-to-one object approach :
FI_DOCUMNT archived 18 months from clearing date.
MM_MATBEL archived 24 mesi from posting date
SD_VBRK archived 24 mesi from posting date
RV_LIKP archived 24 mesi from posting date
SD_VBAK archived 24 mesi from posting date
MM_ACCTIT 18 months from posting date
OIG_SHIPMNT 24 months from posting date
MM_INV_BEL 24 months from posting date
RL_TA 12 months from posting date
RL_TB 12 months from posting date
In the R/3 system, after the archiving, those documents were deleted.
Our BW systems extract data using custom extractors and standard ones.
- 2LIS_02_*
- 2LIS_03_BF
- 2LIS-11_*
- 2LIS-17_*
- 2LIS_13_*
- 0FI_AR_4
- 0FI_GL_4
- 0FI_AP_4
- 0EC_PCA_3
- 0CO_OM_CCA_9
We have found problems with 2LIS_02_ITM;
During the delta extraction, we found records related with Purchase
Order, with GR archived, that have MBAW field (Delivery Quantity
Variance in %
) with "-100" value; the correct value should be "0" (because the
Purchase Order was completed).
MP0 is a 40B R/3 SYSTEM SP 83, PLUGIN 2004.1
Thank you in advance for you cooperation
best regards
Diego

Hi Waldemar,
LOEKZ (Deletion indicator in purchasing document) is not available in standard extract structure we have append that field with append structure in RSA 6.
BUKRS is available in standard extract structure :
In lo-cockpit open extract structure and select BUKRS(Company code) field transfer to left side .
2. click data source maintenance check BUKRS field .
you will get BUKRS field in 2lis_o2_ITM
Thanks
Sree

Delivery date in the PR is wrongly calculated

Hi,
This is a severe issue we are facing, delivery date in PR is wrongly calculating. consider this example:
sales order was created on 31.08.2007 and the planned delivery time assigned in MMR is 9 days, GR processing time is 1 day. Due to some reasons we have created PR on 17.09.2007 but the system is showing the delivery time as 17.10.2007 the release date is on 05.10.2007
Can any body tell me how system calculates delivery date in PR and wat are the factors influence this calculation and also the reason for this unusaual behavior of the system?
Many thanks for your quick reply.
Sri

Please request one Abaper to solve this problem.
You cannot due nothing as the problem is in Code.
Regards
William

Wrong calculated profit/loss in f.01 financial statement

i have created new finanical statment version in ob58.
and i am using that in f.01 financial statement,
but calculated profit coming wrong
why it is coming wrong,
& how it is calculating.

Hi Thiru
In OB58, double-click on your newly created Financial Statement Version and then click on Fin. Statement Items
This includes all your accounts that are linked to your FSV. You can change the order or add / remove the accounts from this setting and then save your FSV.
We surely can't say WHY is your profit wrong, but this might suggest you HOW it calculates and can be corrected.
Let me know if it helps.
Regards
Zubin

Prob. in Implement User Exit for wrong calculation of Surcharge during MIRO

Dear All,
In our system the calculation of Surcharge is wrong during MIRO.
So i write this issue to the SAP, the below solution is provided by them :
Use the user exit 'J_1I7_USEREXIT_PROCESS_TKOMV' to redetermine
the additional VAT condition type value. This user exit will be
called after the FM 'J_1I4A_TAX_CONDITIONS', where the
redetermination of the VAT will take place on the basis of
the changed excise duties.
So, userexit can be implemented by CMOD and SMOD, but this userexit actually a Function Module.
But now the problem is how can i implement the 'J_1I7_USEREXIT_PROCESS_TKOMV' function Module.
Regards,
Nitin Garg

Dear,
Thanks. I already make a enhacement in this function Module and write the below code:
ENHANCEMENT 1 ZMIRO. "active version
DATA : WA_XKOMV TYPE KOMV.
DATA : WA_KBETR TYPE KOMV-KBETR,
IDX TYPE SY-TABIX.
LOOP AT XKOMV WHERE KSCHL = 'ZSUR'.
IDX = SY-TABIX.
WA_KBETR = XKOMV-KBETR / 10.
READ TABLE XKOMV INTO WA_XKOMV WITH KEY KSCHL = 'JVRD'.
XKOMV-KWERT = WA_XKOMV-KWERT * WA_KBETR / 100.
MODIFY XKOMV INDEX IDX TRANSPORTING KWERT.
ENDLOOP.
ENDENHANCEMENT.
ZSUR is a custom surcharge condition type. But still surcharge is wrong calculated.
Nitin Garg.

Age in years and length of service wrongly calculated

I have BI 7.0 implemented by SAP itself , they installed only the business content without any customization
in HR For The Cube HeadCount 0PAPA_C02 the key figure Age in Years 0AGE_NC is calculating in a wrong way it is subtracting from 1999
and the field length of service in years 0SRVCLEN_NC is subtracting from 1999 for dates less than 1999 and from 2199 for date more than 1999
i have searched alot for this but i can't find any solution

the problem was in the 0CALDAY , it should be set before the calculation
so i set it to today and everything become fine

Why java gives wrong answer

float f=40.3f;
System.out.println(f%4);
The answer for above must be 0.3 but java gives 0.29999924
WHY????
(This answer is ok for small calculations but it may give wrong answers for large calculations)

float f=40.3f;
System.out.println(f%4);
The answer for above must be 0.3 but java gives
0.29999924
WHY????
(This answer is ok for small calculations but it may
give wrong answers for large calculations)Use BigDecimal with MathContext or roll your own Fraction class- this way any repeating decimal is represented exactly.
Message was edited by:
snic.snac

HT5616 my iPhone i cloud verification email id i give wrong so what i can do the email changing?

my iPhone i cloud verification email id i give wrong so what i can do the email changing?

First off try and go into your IPhone manually through My Computer and cut photos or anything you can through the device to be able to free space up so that you can continue to do what you want to do with ITunes. This way you will be able to create a backup or do what you have to do to manage your information, photos and texts on your device a little better.

DAX Dynamic Banding | Calculated Member based on Calculated Field

Good morning,
I've created a Power Pivot model that measures the blood glucose levels of clinical patients at specific times of the day. The requirement is that this metric, let's call it GlucoseLevel, is always averaged as it wouldn't make sense to sum up the values.
To meet this first requirement, I set the "Summarize By" property of the GlucoseLevel column to "Average".
The second requirement is to band the GlucoseLevel values so that groups of people can be measured by this band rather than by the individual measure values. I created a banding table in Excel and then imported it into the Power Pivot model. The banding table
has three columns (BandName, MinValue and MaxValue) and has the following values:
VERYLOW: Min Value = 0; Max Value = 3.99
OK: Min Value = 4; Max Value = 6.99
WARNING: Min Value = 7; Max Value = 10.99CRITICAL: Min Value = 11; Max Value = 30.00
It is at this point where I face my challenge. I have a GlucoseLevel measure and I have a banding table. Great. The challenge is: How do I create a calculated, dynamic
member that will look at my GlucoseLevel measure (at whatever level), do a lookup to my banding table, and then return the "BandName" column from the Banding table at that specific level? So to clarify what I mean by level: I want to be able
to view the bandings at Year level, or a Month level, or even at a week level. Then depending on what level I am at, my measure should have a Band associated to it.
I've tried to solve this issue in a couple of ways:
Attempt 1
Create a calculated column in my fact table that contains a nested IF statement to manually band my GlucoseLevel values. This works fine if I view my data at the lowest level of granularity, however
it does not work if I start looking at my data at the day, week, month etc. levels
Attempt 2
1.) Create a calculated field (not a calculated column) that averages my GlucoseLevel measure. This is cool because it will average my measure at whatever level I am viewing it at. Let's call
this field Bob...
2.) Band my measure Bob by creating another calculated field (called PatientBand). This field uses my banding table (described earlier) in conjunction with my calculated field Bob. This works perfectly, except for one big flaw: Excel sees this banding field
as a measure, and not as something that I can use as a column / row...
So my question is: Can I trick Excel into viewing my PatientBand calculated field as an attribute, and not as a measure? And if not, how do I get around this challenge? Here is the DAX formula that I used to create my second calculated field "PatientBand":
PatientBand:=CALCULATE(
VALUES (Bandings[BandName]);
FILTER (
Bandings;
Test[Bob] >= Bandings[MinValue]
&& Test[Bob] <= Bandings[MaxValue]
Thanks!

So there are 2 ways that I can think of for doing that.
1) if you are only using MDX clients like Excel or Reporting services you can create a text based measure that returns the banding name. (Note that this sort of approach does not work at the moment with PowerView as it only displays numeric measures). This
would effectively let you show a label next to a reading as opposed to moving the reading under a given banding column.
Banding Name :=
CALCULATE (
VALUES ( Bands[BandName] ),
FILTER (
Bands,
[Average of GlucoseReading] >= Bands[BandMin]
&& [Average of GlucoseReading] <= Bands[BandMax]
&& NOT ( ISBLANK ( [Average of GlucoseReading] ) )
2) This next approach will show the results exactly as you had them in your sample screenshots. It just takes a slight bending of the DAX. I'm using a SUMX here, not because I want to sum anything, but because the "X" version of SUMX basically loops over
every row in the specified table and sums the expression in the second parameter. I have setup the second parameter so that it only returns a single value for the average if it is in the appropriate banding.
Banded Average:=IF (
HASONEVALUE ( Bands[BandName] ),
SUMX(
'Bands',
IF (
NOT ( ISBLANK ( [Average of GlucoseReading] ) )
&& [Average of GlucoseReading] >= MIN ( Bands[BandMin] )
&& [Average of GlucoseReading] <= MIN ( Bands[BandMax] ),
AVERAGE(Readings[GlucoseReading]),
BLANK()
,AVERAGE(Readings[GlucoseReading])
http://darren.gosbell.com - please mark correct answers

"Interest on Arrears calculation" vs "Item Interest Calculation"

Hi all,
Could anyone explain me the difference between "Interest on Arrears calculation" and "Item Interest Calculation" and in what cases they are used.
Thanks,
DSK.

Item Interest Calculation
    In this activity you make the general settings for the individual
    interest indicators for the item interest calculation
     These include settings for selecting the items and for
    calculating the interest. You can also enter specifications for interest
    postprocessing, output control, and for posting.
Account Balance Interest Calculation
     In this step you make general specifications for each interest indicator
     for the account balance interest calculation. These include
     determination of the period, the interest determination, the subsequent
     processing of interest, the output control for printing forms as well as
     the terms of payment
Regards
Arun

Unable to send or recieve mail pop up continually says wrong user I'd or password.

UNable to send or recieve mail pop box continually says wrong user I'd or password both chiecked ok.

If the server says they are wrong then they are wrong. Check the provider's website for iPhone setup instructions.

Wireless keyboard gives wrong letters

wireless keyboard gives wrong letters

[shameful mode on]
Sorry. I don't have my Mac in front of me.
I'm using windows right now.
[shameful mode off]

CALCULATE_TAX_ITEM gives wrong values for Scess and HScess in PO Print

Dear Friends,
I am working with PO Print in smartforms hare the Fm CALCULATE_TAX_ITEM is gives wrong values for Scess and HEcess if I put the Gate pass (Basic Excise Duty) Manually.
And one more Issue is as if I check any line item condition taxes than imediatly when I see the print the all line items Scee and HEcess displays same which I have saw.
If there is a single line item in PO than there is no issue any way.
kindly suggest to resolve the issue.
Regards,
D Tarun Kumar

Hi,
I had the same issue, that taxes on invoice tab of PO was not printed correctly on PO form by calling CALCULATE_TAX_ITEM.
If you want to have the same tax value as komp-mwsbp, that use following form routine call before FB CALCULATE_TAX_ITEM.
perform j_1b_save_tax_fields(saplmepo) using ekko ekpo lfa1.
This is used in transaction me23n also.
Kind regards,
Tülay

Share with notification give wrong list item url

Hi Experts,
I am facing an issue with SharePoint notification email when sharing list item with users, the notification email gives wrong list item URL, in fact it gives strange URL like this (http://mycollection/sites/lists/list1/01_000)
the strange thing that list item url is correct when sending share with notification if you apply it to document library, but it is not working well if you apply it to custom list!!
can any body tell me whats wrong with SharePoint ?

Was it ever enabled.
Is this a restored list\library ?
Do we have any workflow on same
If this helped you resolve your issue, please mark it Answered

Have downloaded 5s iPhone. Instructions for activating iCloud gives wrong email address to verify account. How can I get around this problem and get my phone set up with iCloud

Have downloaded 5s iPhone. Instructions for activating iCloud gives wrong email address to verify account. How can I get around this problem and get my phone set up with iCloud

elhoseny wrote:
... Instructions for activating iCloud gives wrong email address to verify account..
The Apple ID and Password that was Originally used to Activate the iDevice is required
If you do not have that information you will not be able to use the Device.
Activation Lock in iOS 7 > http://support.apple.com/kb/HT5818

Calculator continually gives wrong calculation

Similar Messages

Maybe you are looking for