Higher decimal places in SD pricing

Hi All.
I would like the system to accept up to 3 decimal places when creating quotation, sales order and invoice in SD. I created a new currency under t-code OY03 and customized it under t-code OY04. It works fine for newly entered values. The problem is that for values which already existed in the system i am getting rounding-off errors. All the figures in the old invoices and accounting reports have been changed e.g. $13.20 becomes $1.320 across the the whole system.
How do create an alternative formula and assign it to my pricing condition type ZR00 in the pricing procedure so as to remove the rounding-off error?
Regards,
Joseph

Hi Joseph,
This is not good practice to change the decimals places for the currency to which documents are already posted. you also would have got warning message when you changed the decimal places.. It would affect all the posted documents in the system.. It would be a hectic job to bring back to normal.
I had similar experience but in my case, there was NO Payment taken place.So, deleted all the MIRO and reversed MIGO and manually changed the PO value and posted it with correct value.
you had better to create new currency with required decimal places ( for eg: USD - 2 decimals and make USDN - 3 decimals as such) and use it whenever required.
With Regards
S.Siva

Similar Messages

Decimal Places for Pricing conditions in Purchase info record

Hi guys:
In the material master, Moving average price/std price 2 decimal places, purchase info records -pricing conditions we have option of 2 decimal places.
Is there any we can increase the number of decimal places .?
Thanks
sweth

Hi,
you can either have high prices or high accuracy, but not both together (because field length stays fixed).
Don't think about a modification - to much changes would be necessary. I never have seen a situation, where you needed more than about 6 significant digits (= not '0'): high prices don't have decimals.
So you usually change a factor: Maintain prices for higher or smaller units to get into the correct range. Or you might use different currencies in different situations. You can also maintain prices per 100 or 1000 units (in case of cheap products).
If nothing else is possible, you might use two conditions: one without decimals, second one only decimals, the sum of both can be a very precise high price.
Better to use the option price unit if you want exact value in place.
Kuber

Decimal places

Decimal places are defined in the general settings.
They are currently set to 2 decimal places.
We have the required for 5 customers to be priced and invoiced at 3 decimal places.
Is this possible?

Hi Lisa,
Please also notice the following information
When you tick the option: Rounding By: Currency from the Administration-System Initialisation-Document Setting window.
You could assign different rounding /decimal place per different currency
( Administration-Definition-Financial-Define Currencies)
Hope this can be helpful.
Best Regards
Helen Sun

Condition type decimal point issue in pricing

Hi
I have a import pricing Procedure as shown
The condition types JEDB and JSED were calculated on 0.16 EUR,
Like JEDB 2% of 0.16EUR= 0.0032
and JSED 1% of 0.16EUR= 0.0016
it is taking the first two digits of the value, ie 0.00 only
Please confirm how to come with the corrected values,
Thanks,

Yes it is intended for TM but you can do the manual changes as recommended in the note and for technical coding, you can copy that logic. Else, have a look at this note:-
Note 38881 - Pricing with different decimal places
G. Lakshmipathi

Decimal places in Measurement tab for Land

We lease-in Land in Acres. Typical land sizes require area to be defined in decimal units e.g 18.963 ACR or 256.755 ACR.
However, in the measurement tab for creating Land the amount column is rounding off all decimal values to whole numbers. Like in the above example what gets entered is 18 ACR and 256 ACR respectively.
I did not find any decimal options while defining the measurement type. Any clues how to go about resolving this issue?
Hamdan

Hello Hamdan,
You need to define new custom or change the existing unit of measurements assigned in respective dimensions. In this node you specify the number of decimal places you wish to have on particular unit. for example usually ACERS have 3 to 4 decimals as the unit is too high and the rent amount can differ a lot if we omit the decimals.
SPRO -> SAP Netweaver -> Check Units of Measurement
On the next screen select the dimension and click on the unit of measurement. create or edit the unit and specify the rounding decimals and other attributes as needed.
Assign this Unit of measurement to the measurement types in REFX and the Measurement types of the object types, which I am sure you know already.
Enjoy,
Jag

Decimal places in currencies from flat files

Hi experts,
I am facing a problem in the way BI is managing decimal places when I extract them from tex files. I have read a lot of post and make a lot of changes and the problem persits. Here is my problem. I am uploading data from text files. These files come from 6 different source systems. All developments are already in production so changing the way they send the data it would be the most expensive solution at this point.
For all currencies ratios I receive in the file could contain these 3 kind of values:
5.45
3.2
4
Decimal indicator is "." but it is not always present and sometimes is follow 1 decimal pla or 2, which is ogial to expect depending of the nature of the value. I haven't been able to make it work for all the cases.
I have set "." in RSCUSTV1 as decimal separator. I tried number format "direct entry" in the extraction Tab of data source. I have tried all possible combinations in the tab fields with data type CURR, DEC, even CHAR and Internal or External format, and any configuration I have made works only for some cases and not for the others. I don't know what else I can look at. Your help will be highly appreciated and rewarded with points.
Regards,
Raimundo Alvarez

HI guys and Thanks for your help.
I could solve my problem. There were some issues already fixed (a combination of the external property in the tab fields, the configuration for decimal separator and a problem with the currency). The main one was giving me the headache that I am trying to import a currency but I was not receiving the currency from the source because is always the same (Colombian Pesos). This one has an special configuration in table TCURX that was making the decimal places be wrong. I solved requesting the currency from the source even if it was a constant value.
Thanks for your help,
Rai.

Decimal places in database

Hi all,
Please can you make B1 do all calculations and store all data in the database to the maximum number of decimal places, and then let users pick to how many decimal places to view on screen?
At the moment, if I only pick 2 decimal places, the database saves and calculates values to 2 decimal places, so in long marketing documents causes mis-pricing of things like tax/VAT.
Current option is to set everything to 6 decimal places, and use round(xxx,2) in PLD, but this makes the user's B1 screen in marketing docs etc very very ugly
Thanks
Rajiv

Hi there,
Firstly, thank you for looking into this, it is appreciated. VAT is at 17.5%:
Invoice contains:
Item A x1
Price 2.22
VAT 0.3885 (4dp)
VAT 0.39 (2dp)
Item B x1, Item C x1, and Item D x1 - all like Item A
In this scenario, VAT on Items A,B,C, and D.
With 4 dp - 0.3885 x4 = 1.554 -> 1.55
With 2 dp - 0.39 x 4 = 1.56 -> 1.56
So there is a difference of one penny in this mock scenario.
Hence, all calculations should be done and stored to the full 6dp within the database, however, the end user should be able to choose how many dp to view "on screen" as it were.
Does this make things clearer?
Rajiv

Rounding up to a particular decimal place

Hi,
I'm bringing a field into my report that uses up to eight decimal places. I'm tasked with rounding things up to the fifth decimal. Rather than rounding when the number is five or higher, it should always round up if it is above one.
So for example:
2.03827893 rounds up to 2.03828000
11.40032180 rounds up to 11.40033000
Any ideas on the best approach for achieving this within a Crystal formula?
Any help would be greatly appreciated.
Thank you.

Hi Bob,
Right click on the field and select "Format Field"
In "Number" tab, select "Custom Style" then click on "Customize"
In the Roundig box you can select the Rounding type.
--Praveen G

Query regarding decimal places for currencies

Dear all,
SAP standard allows 2 decimal points as default for any condition value. However, based on the entries in TCURX table we can set number of decimal places with reference to specific currencies.
In our system there is no entry in TCURX table against USD currency. Still the system is taking 3 decimal places against the expected 2 decimal places.
Is there somewhere hardcoded this for US or are they any additional settings impacting this? Please help
Regards,
Rajesh

Hi All,
I have been trying to set 3 decimal places. I got the reference to Note # 38881.
This is what I did:
1. Create a new currency US$ and set the decimal places to 3
2. Maintained the prices using VK11.
3. Changed the customers' sales area currency to US$
But when I created the sales order although the system determined the prices in 3 decimals i got the following information message which keeps on showing during the entire sales order creation:
Pricing error: Mandatory condition ZMAC is missing
Message no. V1801
Details are as below:
The obligatory condition ZMAC does not exist. The document is therefore considered to be incomplete from the point of view of pricing.
The cause can be, for example, that a condition record does not exist for condition ZMAC or that a field overflow has occurred when the condition rate was calculated.
Procedure
Check why the condition could not be found. Use the pricing analysis function on the pricing screen to do this. If necessary, add the missing condition manually to the document.
I believe I am missing some configuration that should be done in pricing, not sure what. As this question has been flagged answered, hope someone would be able to help me.
Thanks & Regards,
Rajesh Singh

Increase decimal places in Gross Unit of Measure

Hello Everyone,
I had an issue regarding Decimal places for a specific Unit of measure.
My Base unit of measure is maintained in Ea. For this the material is maintained with a gross maintained in Kg's. Now to record 2.5 grams i have to menition .0025 Kg but system does not accept up to 4 decimal places. system only accepts up to 3 decimal places. Even increasing the decimal places in CUNI does not make the system to accept 4 Decimal places.
So what is the solution to this.
Any help is highly appreciated.
Sincerely,
Aji

HI
I dont think that we can increase the length of the decimal places filed in all cases. Refer note 95869.
Regards
Abhijit Gautam

BUG: Inputting decimal places into new duration preferences (Premiere Pro 2014.2)

So, I checked the release notes for the newest version of Premiere Pro CC (2014.2). I was happy to see the ability to switch between frames and seconds when choosing the default durations of transitions and still images.
Immediately found a bug. Decimal places don't work correctly after switching units.
Open Preferences.
Switch Video Transition Default Duration units from the default Frames to Seconds. Try to insert a decimal place using the keyboard. It doesn't work.
Hit OK to close the Preferences, with Video Transition Default Duration now set to seconds
Open preferences again and change the units back to frames. Now try to input decimal places. No matter where the text cursor is, the decimals just get added to the end of the form field.
This seems to affect all three form fields (not just Video Transition, but Audio and Still Frame as well).
Really weird bug, and I'm not sure how you guys at Adobe missed this one...
Anyone else having this bug? I'm on Windows 7.
If so, can someone please file an official bug report? I'm at work and low on time, but I felt like I needed to bring this up to make sure I'm not the only one in this boat.

I've reproed this issue and logged a bug report.
A workaround is to toggle the Unit setting, click Okay to close Preferences, then reopen Preferences and adjust the Value. Sorry for the inconvenience.
I urge you to submit your own bug report (Adobe - Feature Request/Bug Report Form). The more customers who report an issue, the higher the odds that a fix will make it into the next release...

Decimal place support in BOM for R11i

Hi, does anyone can enable higher precision upto 9 decimal place in BOM, existing only 6 decimal place support in component quantity but ct would need more. Does R11i (11.5.4) support more than 6 decimal place in BOM? if it can, how to setup.
Thanks in advance.
Rex

HI Indraneel,
Both are important. When you upload any data and create PO,So this will be important .Similarly oy04 also.It is not allowed to change this manually.This is maintained as per the country currency.
Regards,
Madhu.

Adding Decimal Place

Dear Guru
I want to add 5 digits after decimal in my pricing condition types.Pls suggest how to make this settings
Thanx
MK

Dear MK,
The transaction OY04 is the correct to define decimal places based on currency. However, before you
made the changes, please kindly make sure you don't have existing or not completing purchasing document
in your system as this will affect the document that may create inconsistency later.
BR,
Ian

Price per unit is getting round off to two decimal places.

Hi Gurus,
In the Billing output, the Price per unit is getting round off to two decimal places.
How can we avoid this or allow 4 decimal places for such cases.
In the same pricing procedure, we have two pricing condition types PR02 and ZR01.
When PR02 is being used,it doesnt rounds off Price per unit.e.g .578888 = .578888
But when ZR01 is being used the system rounds off price per unit.e.g.578888 = .58
Please suggest where is the setting for it.
Thanks
Montee

Hi,
Which currency you are using? If its INR, then it will do only for 2 decimal places.
The solution for ur problem can be ractified by changing the scales :
Also check OSS 80183
Thanks,
Raja

Need only two decimal places, but BigDecimal isn't working

Hello again. This time I've got a problem with getting only two decimal places. I tried using BigDecimal but when I compile it, I get an error "cannot find symbol class BigDecimal" and a "cannot find symbol variable BigDecimal".
Grrr... I just want my value to have only 2 decimal places before it ends up in my text field.
Any help will be appreciated.
- Phonse
if (ostuff1.equals("amt tendered"))
                 finalamt = total1 * 1.12;
                 change = cash1 - finalamt;
           BigDecimal finalamt2 = new BigDecimal(finalamt);
              finalamt2 = finalamt2.setScale(2, BigDecimal.ROUND_DOWN);
              BigDecimal change2 = new BigDecimal(change);
              change2 = change2.setScale(2, BigDecimal.ROUND_DOWN);
              finalamt = doubleValue(finalamt2);
              change = doubleValue(change2);
                 addItem(String.format("Amount Tendered:          "+"P "+finalamt));
                 addItem(String.format("Change:                     "+"P "+change));
               }

@ georgemc
Isn't it better to import whole packages instead so
you can have everything available when you call them?
I mean, it's kinda hard to import individual classes
everytime you need to call them.No. You can get conflicts when importing complete packages. If you importjava.awt.*;
java.util.*;and then declareList list;the compiler does not know which List you meant, java.util.List or java.awt.List.
Offtopic @ prometheuzz
LOL. When I was a kid still playing my Playstation I
wanted to have a career in computers when I got to
college. Now I'm 14 and a 3rd year high school
student and I just got a reality check -- computers
just isn't for me. And alot of those professionals
say Java is the "easiest" programming language. O_O
Meh. I'll just follow my other dream of becoming a
chef. Just seems like my parents won't like it...
Bleh... Two more years... Two more years...Sure, but if you like programming, work (hard) for it. Most people have to work hard in order to become good at something, no one is born as a programmer. This goes for becoming a chef as well.

Higher decimal places in SD pricing

Similar Messages

Maybe you are looking for