Limiting decimal places

is there a way to limit the number of decimal places that appear in an output?

Yes, truncate it manually or by some input method limiter.
If you are reading a spreadsheet file and outputting that to the console, then you can simply check the value of the string, and determine how many numbers come after the "." charactor. That will give you an index in the string.
Using that index you can then simply create a new string including the whole number, decimal, and only those points that you want.
You can also do the reverse and expand the decimals from, let's say 1 decimal (like 10.2) to a 2-digit decimal (like 10.20) by simply adding the needed places in the string after the last charactor.

Similar Messages

Limiting decimal places in results

Some of my measurements from VIs are coming back with an exceedingly long string of decimal points. Is there a way to have TestStand globally trim it down globally or individually for the report?
Thanks,
jvh
Solved!
Go to Solution.

Asbo wrote:
That was embarassingly straightforward Unfortunately, this field is disabled for ATML reporting (which I'm going to use as an excuse for not knowing about it) - the NumericFormat parameters still gets passed into the support DLL, but it doesn't affect anything. Anyone know a slick way of globally setting the numeric format for ATML reports?
I think the ATML report data is simply XML. XML is more of a database than a document, so a number would be recorded in the file as it's datatype (double,I32 etc...)
I suspect you would need to modify the ATML stylesheet in order to change the way the floating point values are presented in a browser...
Now is the right time to use %^<%Y-%m-%dT%H:%M:%S%3uZ>T
If you don't hate time zones, you're not a real programmer.
"You are what you don't automate"
Inplaceness is synonymous with insidiousness

Limiting AS distance to two decimal places

I am just about there getting the Google Maps API talking to my SQL database. For my search results I have the SQL:
SELECT *, ( 3959 * acos( cos( radians(" .$POST["latitude"] .") ) * cos( radians( lat ) ) * cos( radians( lng ) - radians(" .$POST["longitude"] .") ) + sin( radians(" .$_POST["latitude"] .") ) * sin( radians( lat ) ) ) ) AS distance FROM VenuesGeocodes1 HAVING distance < 100 ORDER BY distance LIMIT 0 , 30;
Which works great, but displays the distance with 15 decimal places which is complete overkill.
How can I limit that to just two decimal places? I thought I just needed to change distance to distance (10,2), but it didn't like it.
If anyone can let me know what it should be that would be much appreciated.
Thanks.

Thanks Rob - I also got it to work using ROUND in the query:
SELECT *, ROUND( 3959 * acos....

Decimal Places for Currencies

Impact on the processes of change at MM decimals for Currencies.
We want to use foreign currency to 6 decimals anand two decimal places for the currency of society

Dear José Luis Flores ,
Please always make sure your business process not reach the limitation of overflow during
the conversion as the Price it is always with 11 characters with 2 Decimal place (9,2) in standard.
All together 13 characters.
If this limitation was reached, you will received the dump message. This is normal and you had to
make sure it suits your business requirement in the beginning to avoid any changes later . You
had to plan it before do this type of customizing in very beginning.
Thanks
Ian

Changing of decimal places from 2 to 6 digits

Hi,
Currently, our PO price and GR/GI quantities are being limited to two (2) decimal places only. However, we want to maintain it into six (6) digits so that we can have a more accurate PO price and GR/GI quantities in our record.
We tried to do this in Tcode OY04 but the system issued as the following warning messages:
1. In a productive system, you must not delete the currencies in use or change the decimal places. This could make amounts in document already posted incorrect or invalid.
2. In the R/3 System tables currency fields are stored as decimal figures with a variable number of decimal places. The decimal point is not stored in the field in the database. Instead, each currency field refers to a currency key field. In this transaction you assign the number of decimal places to this currency key uniquely.
Can you please explain to me the warning messages further?
Thank you.

Hi Jack,
Please never try to change the decimal places in PRD system, you will be in deep deep trouble.
Let me give one example , If the current decimal is set to 2 digit and you are going to change it 3 digit, then USD 100.00 will become USD 10.000 for the already posted document.
Please not that, the decimal places are not sotred in the database, when you run a tcode to see any posted data the system queries the currency table and see the value for the decimals, if it finds 3 in OY04, it simply places the decial point afer 3 digit from right, if the decimal is set to 4m it will simple place the decimal point after 4 digit from right.
Hope this clears your doubt.
Best Regards
Hari K.

11g Client - Inconsistencies at the 16th decimal place

In TOAD, SQLPlus, & ODBC clients numbers returned from a query are correct (max 3 decimal places)
In Discoverer & from a report, the numbers are off at the 16th decimal place...
EG:
7.081 becomes 7.0810000000000004
7.090 becomes 7.0999999999999994 (which is exceptionally weird because the rounding doesn't work)
7.200 becomes 7.2000000000000002
Any idea what would cause this?
How can I query from SQLPlus (or TOAD) to confirm whether or not those extended decimal places actually exist in the table?

Alan3 wrote:
Maybe I should have added this little tidbit...Please be as verbose as possible (feasible). Show queries etc. - use copy and paste.
The particular table in question is an interface table that has been in place for 4+ years.
The columns in question are of data type NUMBER.
We just switched the PC that runs this interface to Win7 with an 11g client.Describe the interface. E.g. In what program language is it written?
Now we see the extended decimals with Discoverer (on any PC) and the interface report (an old report built from developer 6) as well, but not from SQL, etc...How is changing one pc client related to the Discoverer and Reports reports? Has the database server been upgraded also? (full version from select * from v$version; )
Do you see the same change for "old" data (from before the switch).
I want to know if there is a setting in SQLPlus or the DB client that limits the display of the decimal places that I can alter to determine if the extended decimals actually show up... (they shouldn't be there at all)Both sqlplus and db may affect the outcome, e.g.
SQL> desc test
Name                                      Null?    Type
A                                                  NUMBER
B                                                  NUMBER(38,5)
SQL> show numw
numwidth 10
SQL>
SQL> select * from test;
         A          B
     12345      12345
123456789 123456789
    123,45     123,45
123,456789 123,45679
     1,234      1,234
1,23456789    1,23457
6 rows selected.The same values was inserted to both columns of test. With scale = 5 for its datatype, B values are rounded (4th and 6th row).
SQL> set numw 5
SQL> select * from test;
    A     B
12345 12345
123,5 123,5
123,5 123,5
1,234 1,234
1,235 1,235
6 rows selected.The numwidth setting affects sqlplus formatting.
Edited by: orafad on Jan 5, 2011 9:44 PM

Formatting decimal places in the X Axis

I’m having trouble limiting the number of decimal places in my X Axis on a 2 Axis plot.
I am running a script file (SUD) that sets all the other parameters in the Plot. The “Report “ file is called up and then the script controls the functions.
This is only a small section of the code. I haven’t found a command to set the Decimal place in the “help” page.
ie: Call GraphObjOpen("2DAxis1_XAxis1")
    D2AxisXFormat    = " "
    D2AxisXAng       = 0
    D2AxisXRelPos    = "bottom"
    D2AxisXFont      = ""
    D2AxisXSize      = 2
    D2AxisXColor     = "blue"
    D2AxisXColorRGB = 50266112
    D2AxisXAutoColor = 0
    D2AxisXBold      = 0
    D2AxisXItal      = 0
    D2AxisXUndl      = 0
    D2AxisXStrOut    = 0
    D2AxisXFrame     = 0
Call GraphObjClose("2DAxis1_XAxis1")
And:
When I open the “Curve and Axis Definition” window of the graph on the report page ,and set the “Format:” function to display “d.dd” It seems the script is overwriting the format that I set.
This is what I have now and would like to display only 2 decimal places in the X Axis. Can you help?
Thanks!
SJD
Solved!
Go to Solution.
Attachments:
X-Axis Decimal places.jpg ‏17 KB

Thanks Brad for you quick response.
It kind of worked... I think I might have something else going on. Not sure what though.
With the changes made in the script you suggested, the X-Axis has changed to two digits but now it displays " 1.dd "
Any thoughts where else I might have gone wrong?
Thanks again
SJD
Attachments:
2013-03-13_151027.JPG ‏12 KB

Formatting Numeric Only with Variable Decimal Places

Acrobat Pro 9, Windows XP
I'm creating a form that has a number of text box form fields that are to be numeric only per the form requestor. However, for any given field of this type the number of decimal places that can be entered can vary from 0-3 and the requestor does NOT want any unnecessary decimals to appear in the final output (e.g., a "1.2" entry should not appear as "1.200"). The standard number formatting properties always show all the decimal places so I know it's not that route. No calculations will be performed with any of these entries -- the form requestor merely is entering data and then printing it out so that it's legible for the end-user.
I know that the following line of JavaScript in the Custom Keystroke property limits the entry to numeric only, but how should I tweak the syntax to allow a decimal entry:
event.rc = (!event.change || /^\d$/.test(event.change))
I probably also need a script to format for decimal places, but I don't know where to look in the JavaScript for Acrobat API Reference or in the MDN JavaScript Reference.
Thanks in advance for any assistance.

Good question. To keep it simple (because there are about 300 form fields in this document), if they choose to add extra decimal zeros, then who am I to argue with their entry. So in your example for a given form field, if they enter "1.200" then I expect that they want "1.200" to display.
OK, but earlier you said:
"However, for any given field of this type the number of decimal places that can be entered can vary from 0-3 and the requestor does NOT want any unnecessary decimals to appear in the final output (e.g., a "1.2" entry should not appear as "1.200")."
This seems inconsistent. Can you clarify? The point is the code and where it's placed depends on this. It could be implemented either as a custom Validate or Format script, in addition to a Keystroke script.

Config settings for Decimal places in Master Inspection Characteristics

Hi,
can any body tell me where to do the configuration settings for decimal places in master inspection characteristics
i want my limits to be 1.234
i want 3 decimals after point
Regards,
Raj

Hi,
Please go through the below link.
http://www.freesaptutorial.com/how-to-create-master-inspection-characteristic-in-sap-qm-module/
While creating the MIC in QS21 after entering the control indicators you will get Quantitative data screen.
In that screen you can enter the decimal places, UOM, target, lower limits etc
Regards
Hari

Too many decimal places to fit in JTextField

I'm putting a Double value into a JTextField (by adding it to ""), and occasionally the value has too many places to fit in the text field.
Suggestions on limiting the number of decimal places (least significant digits)?
Thanks.

Have a look on this one
http://java.sun.com/j2se/1.5.0/docs/api/index.html?java/text/DecimalFormat.html

Number formatting with either 2 decimal places or none

Hello,
I'm using Acrobat 8 in XP and not familiar with Javascript.
I have some dollar amount fields where I need it to be number formatted, and limited to 2 decimal places but leave the user the ability to enter only an integer.
ie, go to two decimal places if any of
> .
> .0
> .00
> .000(...)
are present but leave it off if none are present.
I assume I need a custom format script but I've not been able to learn enough to figure it out yet.
If anyone can give me some code I can edit and paste, that would be great. Any help is appreciated.

> Have a String as "3.0000000"
String s = "3.0000000";
System.out.printf("%.2f", Double.parseDouble(s)); // 3.00
Formatting - Numbers and Currencies
~

Lost Decimal Places when extracting value from ODS into Cube

Hi,
In short, we wish to transfer data from an ODS to a custom cube. One of the Key Figures is becoming an integer in the process.
Both the ODS and Cube use the same InfoObject which is defined as a Number with a Data Type of FLTP.
If I set a break-point in the update rules, I can see that it is reading the value into the communication structure correctly. Yet, when I browse the data in the Cube, it seems to have lost the decimal places in the update.
More details:
We have a custom ODS and cube which needs to store a Unit Price to four decimal places. In creating the InfoObject for Unit Price, we could not use a Data Type of Currency (Type = Amount) as this is limited to 2 decimal places.
Instead, I used a Data Type of FLTP (Floating Point) and a type of Number. All decimal places are loading correctly into the ODS, but are being lost when transferred to Cube.
Many thanks
Adrian

Hi Simon and Emmanuel,
Thanks for the suggestions.
Unfortunately the Query is returning the same integers as LISTCUBE.
Also, my key figure has the same definition in both the ODS and cube (uses the same InfoObject), and there is no transformation - just transfer.
I'd prefer not to create another currency. It could get a bit messy if I'm having to include the figure in calculation with other figures that use the real currency.
I had thought of making the key figure a standard type of Currency and multiplying the value by 100 before storing them in the cube - then I would simply divide the figures by 100 in the query. But again, not ideal.
I have logged a OSS note with SAP to see if there is any known issue with transferring a floating point number between the ODS and Cube.
Thanks
Adrian

Does anyone have any idea how do i key in number that contains 20digit, 17 decimal places?

I need to key in a number that contains at least 17 decimal places using numeric digit control and i need to use expression note as well. Can anyone help?

After laying down a numeric control right click on it and select "Format and Precision..." to change the number of decimal places. You can also right click and change the "Representation" of the numeric control. By default it will be a DBL which is a 64 bit decimal number with an approximate range of 10**(-308) to 10**308. This is about 15 decimal digits of precision. I know SGL will only give you 10**(-38)to 10**38, which is about 7 decimal digits of precision. Neither of these will cut it for what you are trying to do.
I would recommend using the Extended Precision (EXT) representation. According to the linked document La
bVIEW's implementation of the Extended Precision follows the IEEE 80-bit spec(on Windows OSes). Supposedly even the IEEE 128-bit spec(not implemented on the Windows OSes)only gets you 19 decimal places but I am not sure what the limitations of LabVIEW's implementation are. (I found a good table in the LabVIEW help title, "Numeric Data Types Table".)
I was able to successfully get 17 digits after the decimal point but that was with a leading 0 only before the decimal point. I think you may just be approaching the limit of how a number can be represented in this programming language.
Anyone else?
-scraggs99

QM- DECIMAL PLACES

Dear friends
System is not accepting decimal places entered in Target values, Upper limit & lower limit of MIC in QS21. Only whole numbers are accepted. Also what is the meaning of upper plausibility limit & lower plausbility limits and what are their uses. Please guide.
Selva

Selva
your target is 100 and upper plaus limit 2 --- system will accept upto 102 and if you enter 102.1 Rejected
Lower plaus limit 1 -
> less than 99 -
rejected
Let me know if it is not clear
thanks
Sami

Error while updating decimal places in general settings

Hii All
         I have got an error while updating Decimal places in General Settings
Cannot update while another user is connected to the company i have checked, there is no other user logged in, i could add other settings but the problem is only with Decimal Places
Note : there are no postings yet, a fresh database for a new client
         what could be the possible reason
                                                             thanks
                                                                     RIYAZ

Hiii All
      As a forum rule, i have initially gone through with the existing threads and then i was force to post a thread,
          would be helpfull if there is any other way..
                                            Thanks
                                                     RIYAZ

Limiting decimal places

Similar Messages

Maybe you are looking for