Table values to have more decimal places

Dear Experts,
In one of the LIS table S022 , the value is updating up to one decinal place only. We want this value to have atleast 2 or 3 decimal places . How to make it effective.

Hi
As u have not mentioned for which field the value is updating with 1 decimal its difficult to say but I assume it is related to time. As per the field attributes in the table structure for S022 for all time and capacity related fields the decimal places defined as 1 only hence the data is updating with 1 decimal place.
U can check this in SE11 by entering S022 in the fields tab.
In order to increase the decimal places in table u need the Help of ABAPer with Access key
Regards
Brahmaji

Similar Messages

"value cannot have more than 0 decimal places" error

CRM gurus,
Whenever I try to create a Counter, I receive the following warning which doesn't allow me to do anything further..
"value cannot have more than 0 decimal places"
I first received this when I tried to assign a counter to a product in an Installed Base. So when I tried creating a counter here, I got the above message. I then tried to assign a counter to the product in the product master data, and I still received the same error message. I then tried creating a counter from the "Maintain Counter" screen (Transaction Code: crm_mpk_admin), and still received the same error message.
In this effort I created my own custom Counter Category, and Attributes. Nothing helped.
Could someone throw some light on this concept and tell me where am I going wrong.
Thanks and regards,
-Pras

Hi
I think its a program error, you need to Implement the source code corrections.
Please refer SAP Note : 855670
Regards,
Johnny.
Reward if it helps.

More DECIMAL places for MM price-Not Global

I have read the many postings on decimals. However, I have not seen the exact scenario I'm inquiring about.
I want to increase the decimal places from 2 to 4 for the cost of materials we purchase (i.e. supplier price), but I do NOT want to set this as a global aspect for the company when dealing with numbers/currency.
It's not just a simple matter of setting a different unit of measure, because let's say we order a reel of capacitors - the reel may come in qty of 1,000 or 2,500 (only one example). So, we really need to set price by (ea). The problem is that many of our parts price at .0014 (example) and in SAP that shows a cost or price [depending on where you're looking] of zero. Plus, the Purchasing agent sends a PO with incorrect price information.
It would be very helpful if anyone could tell me how to increase the number of decimal places for specific fields as opposed to globally.
Thanks you!!

The right tool to do that is the pice unit. This is in the system for ecatly that purpose, to provide more precision in prices. It has nothing to do with unitz of measure that is used for logistical purposes.
If you have a price 0f 0.0014 each you can set a price unit of 1000 and will have a price of 1.40 for 1000. You still can have only 500 or even 1 on stock. the calculation done if you receive your 2500 will be 2500 * 1,40 / 1000 which is of course the same as 2500 * 0,0014
best regards, Udo

Double value truncated to two decimal places without rounding the value.

I want to truncate double value to two decimal places without doing the rounding of the value.
Is there any method which can directly do the truncation.

There's many ways to achieve this such as using
BigDecimal's setScale method or type-casting. This is
the way I like to do it:double d = -5.239;
d = d > 0 ? Math.floor(d * 100) / 100.0 : Math.ceil(d
* 100) / 100.0;
Your division by 100 may cause an rounding error, because there are numbers which no finite binary representation. That's splitting hairs! I know ;-)

JPY value shifted to two decimal places in the EBAN Table

Hi folks,
We are in SRM 4 SP13 and ECC 4.6 C Classis Scenario.
When a SC is raised in JPY currency ,the total value is carried to PR in the backend correctly.
But in the EBAN table under the PRIES field ,the total value is shown as the 1/100 of the value.
This is happening only with JPY currency( no decimal values).
So the report based on this total value is not showing the correct value of the SC.
Please let me know if I need to implement any changes or note to be applied.
Thanks in advance,
Rajesh

Hi Masa ,
Thanks for the reply.
I displayed the PR through ME53N in the backend. It displays the correct value in the valuation field.
But whencheck the same in the EBAN table under PRIES it is showing 1/100 fo the value.
We have a customised report which picks up this value from this table.
Regards,
Rajesh

After upgrade the cairo package, some places have more blank places

but only when locale isnt en_US. like zh_CN.UTF-8 will have such problem.
i downgrade cairo then this disappear.
any others have such problem or any idea?
Last edited by jarryson (2008-09-26 15:18:21)

i cant post two pic in one post and i dont know why ....
Last edited by jarryson (2008-09-26 15:19:55)

Save data with more than 6 decimal places in SAP MDM 5.5

Hi there,
I need some help concerning saving data with about 20 decimal places (e.g. 0,00452961328622164) in MDM. I declared the datatyp "REAL", there are only 6 decimal places possible.
How can I save this Data? Maybe exponential function?
Please help.
Thank you
Thomas Pfab

currency takes you to 14 decimal places, if you want to have it as a little work around....you can always take out that symbol if it is annoying.(ohhh and decimal is multilingual too in currency, probably not a good hack!)
or without even knwoing what your requirement is? try normalizing the value, How many more decimal places can you hit?
One 100 1. "ten to the zero"
tenth 10-1 0.1 "ten to the minus one"
hundredth 10-2 0.01. "ten to the minus two"
thousandth 10-3 0.001. "ten to the minus three"
ten thousand 10-4 0.0001. "ten to the minus four"
hundred thousandth 10-5 0.00001. "ten to the minus five"
millionth 10-6 0.000001 "ten to the minus six"
ten millionth 10-7 0.0000001. "ten to the minus seven"
hundred millionth 10-8 0.00000001. "ten to the minus eight"
billionth 10-9 0.000000001. "ten to the minus nine"
ten billionth 10-10 0.0000000001. "ten to the minus ten"
hundred billionth 10-11 0.00000000001. "ten to the minus eleven"
trillionth 10-12 0.000000000001 "ten to the minus twelve"
ten trillionth 10-13 0.0000000000001. "ten to the minus thirteen"
hundred trillionth 10-14 0.00000000000001. "ten to the minus fourteen"
and put that field label indicating the 10th power. Like "Accuracy in 10 POW -9"
Just a wild guess.well thats how we usually show data in catalogues too!
(or)
separate the integer and decimal portions into two fields and store it in the repository.(split on ',')
-Sudhir.

Decimal Places in Pivot table

Hi Gurus,
When I create a pivot table with a measure and I choose "Show Data as ...
percent of something (for example section) I get the result with 1 Decimal Place.
How to modify it for 2 or more Decimal Places?
Thanks
Laszlo

Hi Laszlo!
We have found and discussed the answer already, but to more people can see it I write it.
When You have the results already, You can use the 'Advanced' page to see the XML source. There you can modify the code carefully. Change the section:
<saw:dataFormat xsi:type="saw:percent" minDigits="2" maxDigits="2" scale="2"/>
Change maxDigits to the number of decimal digits You wanted.
Although we found the answer on the course, I found later this page - also could help:
http://blog.trivadis.com/blogs/andreasnobbmann/archive/2008/07/15/quot-percent-of-quot-in-obiee-s-pivot-tables.aspx
Best regards,
Tamas

Changing Decimal places in table TCURX

Hi There
We have a business requirement to change the decimal places in table TCURX from 3 Decimals to 5 Decimal places. No previous postings have been made in foreign currencies.
If no transaction data has been posted in foreign currencies yet, will this have an impact?
What will the impact be?
Regards

Hi,
Refer to this SAP text:
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. Example: If you have set currency USD to have two decimal places and you post an amount of 100 USD, an amount of 10000 USD is stored in the currency field in the database. Not until this
amount is processed further or is output does the system use the currency key from the reference field to determine the number of decimal places via this table. In this way the table content can be interpreted correctly for further processing or formatted for output with the correct punctuation. If after posting you changed the number of decimal places for USD, for example, to 3, the existing field content of 10000 would be interpreted for futher processing or output as 10 USD (10.000). This would mean that the contents of tables across the system would, for all currency fields containing an amount in USD,
be interpreted incorrectly by 10 per cent. To change the number of decimal places for a currency already in use, you must convert all the tables in the R/3 System that contain currency fields, so that the data integrity remains. This cannot, however, for both organizational reasons and under the runtime
aspect be carried out in a productive system. The following changes to the TCURX table can
thus lead to the loss of data integrity if you make the changes in a productive system or transport them into a productive system:
o Change to the number of decimal places of an existing currency
o Deletion of an entry from the TCURX table (corresponds to changing the decimal places to the standard value of two decimal places)
o Insertion of an entry in the TCURX (corresponds to changing the standard value of
2 decimal places to a different value), if this is a currency code that already exists
Uncritical changes are any made to this table during the Customizing of a new installation or the insertion of TCURX even during operations, if the currency codes have just been entered in the TCURC table using transaction OY03, signifying that no postings to these currency codes can have been carried out yet.
Regards,
Eli

Storeing values in floate data type upto two decimal places

Hi
I want a float type field in my table but want to store value up to two decimal places.
so what syntax i need to follow plz suggest.
thanks

it is not possible to store with Number datatype. if you are using the data to sho report, then change its format (like 45 to 45.00). if you want to store 45.00 in database, then you have to modify the datatype for that column. for this follow the following path
1. Add a column of datatype Varchar2.
2. Copy all the value of your number field to it.
3. Drop the old column.
4. However make sure that if you have used that column somewhare in arithmetic calculation, the modify it and use to_number function to do arithmetic opration.

Decimal places diferent in BO SUM function than from DB

Hi,
I have a column from a Netezza database with 2 decimal places, if I apply a sum() function in BO (report) the decimal places are 4.
The strange part is that if i do exact the same query in a DB2 database the decimal places are always two (like in DB) even if i use a sum function in report.
There is some configuration regarding the database i'm using to set the decimal places in the report level to be the same than in DB?
Edited: I've been studing the problem and I found using a odbc instead of a jdbc makes all the columns have 2 decimal places, and the sum problem doesn't happen. Now my issue is the division. How is possible that with the exact same values with two decimal positions, in BO and exporting to excel the last decimal place is different in some cases
Example:
Lets say A/B with A=13549678065,560000 and B= 21629484348,690000. With Netezza result is 62,6444803173527 and Db2 62,6444803173528
Thanks for your time.

I've never seen this particular problem before. Quite strange. It sounds more like an OLAP or SQL Server issue, not BPC.
I'm not aware of any configuration on SQL server that allows you to control the decimal separator.
I had a similar problem in the past, when my customer refused to follow the install guide instructions, and insisted that the server be set to non-US English regional settings. If I recall, the issue had to do with date formats not decimal separators. They ended up un-installing and re-installing the entire OS (with US English setup, the second time around), and then it worked fine. This was back on 5.0, and perhaps the situation has changed since then. There's a section in the master / install guide that covers the server-side language & regional settings in some detail.
But before you look at that, try something easier -- is it possible that the cube is somehow corrupted? Do you get any errors when you process the application? Perhaps there is some data in the fact table with an invalid member ID.
Do you get the same result in your Excel report when you use both EVDRE and EVGET?
And if you browse the cube data in SQL Mgmt Studio (logging into the Analysis Services cube) do you see aggregated data there?
Regards,
Tim

Decimal places for JPY currency in change documents

Hi Gurus,
For opportunities in SAP GUI the change documents for JPY show incorrect numbers.
The number is divided by 100 (two decimal places added).
Checked the CDPOS table and found the values already divided (two decimal places added).
SPRO->General Settings->Currencies->Set decimal places for currencies is set for 0 decimals for JPY.
Is there any way I can get correct values in the change documents?
Please advice. Any hint is useful.
Thx,
Martin Kuma

Hi Naren,
Thank you for the tip, however the TCURX table is changed via customizing and should be changed only during the system initialization.
What I would like to do, is to assure that the system displays the values in change documents correctly. It should apply the currency conversion for the data displayed the same way it does for all the tables.
Do you have any idea, how should I do this?
Regards,
Martin Kuma

Decimal places display at the time of results recording

Dear All,
Please i faced one problem, At the time of results recoridngi/.e,
In my insp. plan i defined Quantitative specification as 70.0 with '1' decimal place in Qunatitative data. but after results recording it displaying one more decimal place excessi.e., as 70.00. How can i solve this problem, due to what this problem is occure. Please if any, solve its urgent.
Regards,
Vijaya

Dear Vijaya,
While entering Inspection Characteristics.. There is a field called DecPlaces on the right. its the 24th field on the item table.
The field comes after
Method, Insp Method plant, Version, Sampling Procedure, Sample Unit of Measure, Base Sample Quantity, SPC Criterion, Modification Rule, Test Eqpmt, Test Equip Short Text, Par Sample, DecPlace, Unit of Measure, Target Value, Lower spec Lmt, Upper Spec Lmt... and so on...
Regards
Vijay

Change decimal places in a KF

Hi,
I have a KF Amount with Data Type = CURR.
This KF has a data element associated ( automatically associated when is created) with Lenght 17 and Decimal places 2.
The KF is used in a ODS as Data Field.
Now the user want to update the field, with 5 decimal places.
I tried, but I couldn't change the Data Element. I read a thread that the Data Type has to be change to FLOAT instead of CURR, but when I see the Data Element it changed to Lenght = 16 and Decimal places = 16, and I cant set the decimal places.
So, Could someone help me?
Thanks, Federico

Hi Federico,
The table 'TCURX' determines how many decimal places the Key figure display the values. Mostly they are of 2 decimal places but in the query you can changing in the properties of the key figures to display 5 places. But you would typically not see all correct values. It will just do a rounding with 5 decimal places.
Hope this helps.
Best Regards,
Hima

Changing number of decimal places for Unit of Measure

Hi All,
I have a requirement to convert a quantity in one unit of measure to another (custom) unit of measure.
The issue is that the custom unit of measure has 4 decimal places (customer requirement). I found function module MD_CONVERT_MATERIAL_UNIT which does the trick for regular, 3 decimal places, UoM's. It won't output 4 decimal places since the output data type is EKPO-MENGE, which has 3 decimal places.
Does anyone have experience with trying to convert material's UoMs into 4 or more decimal places?
Thanks!

round_f_to_15_decs round variable of type f to 15 decimals
Sometimes type F (float) is used to represent exact data (Amounts, Quantities):
if values are to big to be represented as Packed (> 31 decimals)
to significally improve performance of calculations, e.g. in statistical reports
G_DECIMAL_PLACES_GET
REPORT Z_ROUNDING .
DATA: float TYPE f,
 amount TYPE p DECIMALS 2,
 correctamount TYPE p DECIMALS 2,
 chars(5) TYPE c value '1.005'.
CLASS cl_abap_math DEFINITION LOAD.
correctamount = chars.
WRITE: / 'Exactly:', chars,
 / 'Correct Amount:', correctamount.
float = chars.
amount = float.
skip 2.
WRITE: / '==== Usual Processing:',
 / 'Float:', float,
 / 'Decimals 3:', float DECIMALS 3,
 / 'Decimals 2:', float DECIMALS 2,
 / 'Amount:', amount.
float = cl_abap_math=>round_f_to_15_decs( float ).
amount = float.
skip 2.
WRITE: / '==== Correct Processing:',
 / 'Float:', float,
 / 'Decimals 3:', float DECIMALS 3,
 / 'Decimals 2:', float DECIMALS 2,
 / 'Amount:', amount.

Table values to have more decimal places

Similar Messages

Maybe you are looking for