Rounding issue in pricing

HI,
system is showing different condition values(condition type PNTP) in sales order and Invoice..
Eg. material cost in Material master is 16.59 $ per 1000 PCS
here our ordering quantity is 10,000 pcs
in sales order it is taking amount as 16.59 per 1000 pcs and for 10,000 condition value is 165.90 $
but in invoice it is taking amount as 0.02 per 1 pc ( rounding the 16.59 to 1 pc i.e 16.59/1000 = 0.01659 = 0.02) and hence for 10,000 qunatity it is showing condition value as 0.02*10,000 = 200 $
here i am getting around 30$ different.. can you please help me in solving this issue...
are there any SAP notes available for this?
thanks,
sudhir

Hi,
Go to VK11 and save the condition record as 0.01659 for your condition type.
Or save the condition record as 16.59 per 1000.
Then go to V/08 and select your pricing procedure.
Over there remove the rounding of the condition type.
Also go to V/06 select your condition type and go to detail.
Over there just remove the rounding rule.
Now try to create the sales order and check the pricing.
One question do you want rounding should be done in the last of the pricing?
Regards
Raj.
Edited by: Raj Aryan Malhotra on Jul 16, 2009 1:25 PM

Similar Messages

Rounding Issue with Pricing Conditions

Currently we have in place a pricing hierchery that consists of two pricing conditions. ZP for base price and ZD for a +-differential. Both conditions begin with 00. ZP00. ZP01, ZP03, ZP04. If a ZP01 exists it overrides a ZP00. If a ZP03 exists it overrides ZP00,ZP01, etc. So basically the higher the number means it overrides anything underneath it. The ZD conditions are setup exactly the same way. I am currently running into a round issue. We settle all transactions in USD however the manual and differentials are often based on prices that go out more than 2 decimal places. SAP is treating the calculation for the ZP and ZD as two separate calculations. It rounds each of them and then combines for a total price. So if the base price ZP02 is $2.245 multiplied by quantity 3,999 = $8,977.755 which it rounds to $8,977.76 and the differential ZD02 is $.0235 this = $93.9765 which it rounds to $93.98 for a total price of $9,071.74. However if you add the ZD02 + the ZD02 you get a total unit price of $2.2685. This multiplied times the quantity 3,999 = $9,071.731 which is correct. But because SAP does each calc separately the price comes out to $9,071.74 or off 1CT. I have seen various solutions on how to fix this from user exits to creating additional conditions that takes both ZP and ZD conditions and calculates them as one but I was hoping someone had come up with something better? Or if there was a preferred method?

Currently we have in place a pricing hierchery that consists of two pricing conditions. ZP for base price and ZD for a +-differential. Both conditions begin with 00. ZP00. ZP01, ZP03, ZP04. If a ZP01 exists it overrides a ZP00. If a ZP03 exists it overrides ZP00,ZP01, etc. So basically the higher the number means it overrides anything underneath it. The ZD conditions are setup exactly the same way. I am currently running into a round issue. We settle all transactions in USD however the manual and differentials are often based on prices that go out more than 2 decimal places. SAP is treating the calculation for the ZP and ZD as two separate calculations. It rounds each of them and then combines for a total price. So if the base price ZP02 is $2.245 multiplied by quantity 3,999 = $8,977.755 which it rounds to $8,977.76 and the differential ZD02 is $.0235 this = $93.9765 which it rounds to $93.98 for a total price of $9,071.74. However if you add the ZD02 + the ZD02 you get a total unit price of $2.2685. This multiplied times the quantity 3,999 = $9,071.731 which is correct. But because SAP does each calc separately the price comes out to $9,071.74 or off 1CT. I have seen various solutions on how to fix this from user exits to creating additional conditions that takes both ZP and ZD conditions and calculates them as one but I was hoping someone had come up with something better? Or if there was a preferred method?

Price Rounding Issue - AFS Pricing

Hello Friends,
We are facing an issue in sales order pricing & its subsequent effect in invoice. We use AFS pricing, where different grid sizes have its basic price.
We have a basic price condition which come thru a master record, and this can be overridden by a manual price condition.
When such manual condition is entered, it applies to all the quantity of the line item irrespective of the number of grid sizes.
So suppose I had 6 grid sizes in the line item (which also results into 6 schedule lines) list price will be shown across all the grid sizes, see DOC1
But when I enter a manual price EUR 7, it applies to the total quantity that is 6. So the net value in this case will be EUR 7, See DOC2
By calculation, 7/6 = 1.166666666666667
So when now I create the invoice, the value gets rounded for all the grid sizes & it becomes 1.17
Here when system calculate the net value it will sum up 1.17, six times & the resultant net value is EUR 7.02, see DOC3
As a result most of the time there is difference between the order value & the invoice value.
Please suggest what action should be taken.
Regards,
Dhananjay Borate

Dear Dhananjay Borate,
You can avoid this issue working this the following options:
Every Condition Type, in the "Control Data Box 1" have the option to apply a "Rouding Rule" with three different options:
Empty.
                     In the standard rounding rule '_', values are rounded off according to business standards:
                         10.454 -> 10.45 DEM
                         10.455 -> 10.46 DEM
"A"
                    In rounding rule 'A', values are always rounded up:
                        10.459 -> 10.46 DEM
                        10.451 -> 10.46 DEM
"B"
                   In rounding rule 'B', values are always rounded down:
                      1045.9 -> 1045 LIT
                      1045.1 -> 1045 LIT
Also you can use, in the "Gruop Condition ", the Rounding difference comparison.
         Indicator that controls whether rounding difference is settled for group conditions with a group key routine. If the indicator is set, the system compares the condition value at header level with the total of the condition values at item level. The difference is then added to the largest item.
Use the Conditons Types:
PDIF - Diff.value (own)
DIFF - Rounding Offwith the Conditions that apply to your needs. The standard gives this ones as examples: [Requirement: Routine 13 - Rounding as perT001R], [Condition Formula 16] and [Basis Type 4]
Regards,
Johnattan.

Net price rounding issue in PO

Hi,
Please note that I am facing net price rounding issue in PO.
For. e.g.
In a PO line item of Qty 25 PC of base price 6 INR, there is a discount of 3.64 INR.
So gross price = 150 INR (25*6)
Net value = 150 - 3.64 = 146.36
No net price = 146.36 / 25 = 5.8544
When we round of two decimal places 5.85 INR (since INR is two decimal curr)
When we show in PO output we will show like below
Material X 25 5.85 146.25 (this is calculated by multiplying qty with net price of 5.85 INR)
So there becomes a difference of .11 INR due to rounding issue.
Net value in PO and PO output are differing. Net price of material & net value should match exactly in PO & PO output
without any differences.
Please throw your views.
Note: can we make discount condition statistical & take it to separate G/L account during GRN?
Regards,
Partha

Hi,
As per the note 80193 rounding, I defined a condition type NETP and it captures the rounding difference.
So now netprice (after discount) * quanity = netvalue (after discount) relationship matches.
But my concern is that the rounding difference is not getting captured in G/L accounts (neither in GR/IR clearing account nor in separate accounts).
Please throw your comments.
Partha

Issue in Pricing Formulae

Hi Sap gurus,
I am facing one issue in pricing. I am getting this error in my effective pricing condition.
"Inactive via formulae of incorrect". Can any body please give me some lights on the issue?
Thanks.
chetali

Hi Chetali,
As per your error mssage I came to know that this is related to some routine issue which is assigned to that 'effective pricing condition'
So, Please check the settings related to the requirement ,alternative calculation type and alternative condition base value routines of that condition type.
Also check the logic involed in the routines with the ABAPer help.
I hope it will help you
Regards,
Murali.

Issue on Pricing

HI SAP Gurus,
Could any one help me out with an Issue on Pricing
The need is
Our company sells consumer goods through our website store. We introduced a coupon system. The coupn system is that if u r a coupn member (means employees of the organisation) and if u put ur coupon no then the customer will be entitled for a discount of fixed Percentage.
How i put the values of coupn in pricing procedure,
Could any one help me out in this procedure
Thanks in advance
EDIE
Edited by: Edie Edie on Jan 8, 2008 11:24 PM

hi warwick,
we r not using condition records, so no acess sequence, we r manualy updating the conditions value in the pricing.
Is there any way to create a service material and put in the item level of Sales order with the name coupn, so 2 items in sales order, 1 is the main item and 2nd the coupon
1st item we put the price, 2nd item we put the percent discount for coupons, because we dont want to see this coupon discount in first item pricing
thanks in advance
Edie

Unit price rounding issue

I'm from Australia. We have stock items some have 10% GST and some don't have. there is a rounding issue on SAP since 2005A. For example, we input $9.55 pre GST price ($10.50 is gst inclusive). When processing invoice, the gross price will display $10.51, a user has to change it to $10.50 manually. The more quanaity, the more rounding error. We check with our supplier, only temporary patch on it. Can standard SAP fix the rounding issue ?
Thanks
KC

normaly It will not happen .
have any add-on and FMS in same filed ? if not then make FMS to copy same data from Base document.
Thanks
Manvendra Singh Niranjan

I have an issue with pricing condition ZPRO (basic price )

Hello gurus
I have an issue with pricing condition ZPRO (basic price ).
users created a sales order, and the basic price ZPRO which is mannual is added twice ,now i want to put a check so that condition tpye zpro is not accepted twice by the system. please let me know how can i restrict system from accepting condition type zpro twice during sales order.
regds
Edited by: sapuser09 on Jul 26, 2011 8:44 AM

Hi,
Solution for this is very simple. Don't make any changes to the sales order user exit. Use condition exclusion for the condition type.
Do customization in the following path of IMG
Sales and distribution---- > Basic Functions--- > Pricing--
> Condition exclusion -- > Condition exclusion for groups of conditions
First In Define condition exclusion groups you have to define condition exclusion group (ZXXX)
Then in Assign condition types to the exclusion groups you have to assign condition type to the exclusion group (ZXXX ZPRO)
Then in Maintain Condition exclusion for pricing procedures select the pricing procedure where you have the problem and click Exclusion box present in Dialog structure box
You will be faced with Change view exclusion overview screen Click new entries
You will be faced with New entries overview of added entries screen.
Take serial no as 10 Condition exclusion procedure as B (Best condition with in condition type) In the exclusion group1 add the exclusion group ZXXX.
Save it and create order.
In the order pricing you will again observe that ZPRO appearing twice but only one will be active.
Changing user exit for this issue is not at all required and it must be only the last resort Try replicating the issue in your sand box system. As I had mentioned it will be picked twice but only one will be active.
Hope this helps.
Edited by: mokirala tilak on Aug 10, 2011 10:19 AM

Pricing Conditions Rounding Issue

Currently, our system has two pricing condition types. ZP,ZD. The ZP conditions represent a base price and the ZD represent a differential(- discount or + surcharge). Both are based on the same hierarchy. ZP00,ZP01,ZP02.ZP03,ZP04. A ZP01 overrides a ZP00 and ZP03 overrides ZP00, ZP01,ZP02 and so on and so forth. All transactions are settled in USD. However, most of the time the ZP, ZDs are based on prices that extend out more than two decimal places. I am experiencing and issue because SAP calculates the ZP and ZD separately and is rounding each. For example the ZP or base price in this case is $2.245. This times quantity of 3,999Gal = $8,977.755. SAP rounds this to $8,977.76. SAP then calcs. the differential ZD $.0235X3,999Gal = $93.9765. SAP rounds to $93.98. This is a total price of $8,977.76+$93.98 =$9,071.74. However the unit price is ZP $2.245 + ZD $0.0235 = $2.2685. If you take this price multiplied by the quantity $2.2685 X 3,999Gal = $9,071.7315. So the actual total price is off by 1ct because SAP treats the ZP and ZD as two separate calculations. I have seen various ideas on how to fix, from creating another pricing condition, to user exits. I was wondering if there was a preferred method? Or if there is a simpler solution?

Good Evening,
1. Please review OSS NOTE 80183 regarding Rounding.
   Values calculated in pricing are always rounded to the amount of
   decimal places which the used document currency owns. As subsequent
   processing steps setup on this rounded value rounding differences can
   occur in the calculation of the price per unit or in subtotal line.
   To bypass such effects note 80183 describes possible solutions to
   reduce / bypass this effect.
   A few problems in rounding after applying note 80183, variant 2 have
   been recorded where it was recommended to use the formulas 919 and
   920 on all discounts and surcharges that appear before NETP and the
   problem was solved.
2. In transaction V/06 there is a field under header 'Control data1'
   which can effect how the system rounds off condition values during
   pricing:
   ->> Rounding rule
       The rule that determines how the system rounds off condition
       values during pricing. The last digit will be rounded.
Example
o In the standard rounding rule '_', values are rounded off according
   to business standards:
   10.454 -> 10.45 DEM
   10.455 -> 10.46 DEM
o In rounding rule 'A', values are always rounded up:
   10.459 -> 10.46 DEM
   10.451 -> 10.46 DEM
o In rounding rule 'B', values are always rounded down:
   1045.9 -> 1045 LIT
   1045.1 -> 1045 LIT
   In this example, the currency of the condition rate is Italian Lira.
   The Italian Lira does not have any places after the point.
3. Also check if the condition type is set as item condition as well
   as group condition in transaction V/06. What this means is that
   the system will calculate the value of the condition on header level
   and compares it with the sum of item values in the document.
   Any rounding difference (KONV-KDIFF) detected, will be populated
   in the line item with greatest value or in first line item if all are
   of equal value.
   In other cases where there is no adjustment because there is no
   rounding difference when comparing the header value and the sum of
   item values.
   ->> Solution to this scenario -
       If you remove the 'group condition' setting, the system will then
       calculate amount for the items directly and you will not get the
       rounding. You must decide which setting is more suited for your
       business. This is not a bug, but works as per designed.
       EXAMPLE: MWST - tax condition (a group condition)
                Item 10     16%   of 100.90 = 16.14
                Item 20     16%   of 100.90 = 16.14
                                       Total = 32.28
I hope this helps you!
Kind Regards,
Martina McElwain
SD Forum Moderator

Pricing Rounding Issue.

Hi Team,
I want to round my Amount and condition value to Integer level(Remove decimal and following two values)
E.g. my PR00 has value 110 for quantity 11 so my condition value will be 110*11 =1210. If i want to apply 1.9% discount on this using condition type ZXXX it would calculate it as 22.99. I want this value to be rounded off to 23 or 22 hence removing the last two digits on the right of decimal.
Also since SAP calculates % on the condition value as in above case it calculates 1.9 % on 1210, I have a requirement where 1.9% should be calculated on amount per unit in this case on 110 and then multiply it with the qty.
I hope I am clear with my explanation, and in case you need further infi, pls let me know.
Regards,
Anupam

Hi,
Check these notes,
Note 80183 - Rounding
Note 315792 - Group conditions of the same amount on item
Note 166952 - Rounding when distributing header conditions
I hope this helps you,
Regards,
Eduardo

Issue with Pricing in Invoice.

Hi,
I have one condition ZIST in my pricing. Whenever I create the invoice manually through VF01, all the items are showing up proper values of ZIST, however header is not showing the proper value (Header is showing the value which is suppose to be at the header minus correction value with respect to rounding off). But when I click on ACTIVATE button on the header pricing screen, system updates the correct value of ZIST.
If I dont click on activate button then Invoice gets saved with wrong ZIST value at the header.
I dont know how should I tackle this issue, Do I need to write a code somewhere to carru out the pricing again to update the right value of ZIST.
Edited by: sanjay kulkarni on Sep 22, 2009 4:00 AM

Thanks for ur response.
Actually in my case netwr value is correct and all the line items are also in good shape, problem is only with header level pricing, that too only one condition is showing wrong value and that needs ACTIVATE to click to get updated with correct value.
In my case its very diffucult to replicate the senario and the one example we have for testing is a huge invoice. Also my pricing procedure has many routines hooked to diffrent condition tyeps. Hence it would be tedious job to debug and see each and every routine from the pricing.
Still, I would try to do it. But I would appreciate if you can let me know what did your developer do wrong in the routines so that I would also concentrate on the same line.

Issue in pricing routine

Hi,
I have an issue while writing code in the pricing routine. while calculating KBETR if the value is 1.035 it is rounding off to 1.04.
Since KBETR has only two decimals it is rounding-off but client wants 1.035 only.
Please help me.
Regards,
Anvesh Gummadapu.

Hi Anvesh,
Table for decimal decimal places in currency is TCURX .
If ur currency does not supports 3 decimal places then may be u need to create a Z version of that currecny with 3 decimal places.
Please check SAP documentaion [Special Output Formats |http://help.sap.com/saphelp_470/helpdata/en/9f/dba1ef35c111d1829f0000e829fbfe/content.htm] &
[Defining Currencies|http://help.sap.com/saphelp_40b/helpdata/en/08/51410a43b511d182b30000e829fbfe/frameset.htm]

Rounding error in pricing

Hi All,
We have one issue for Russia in Pricing
We have one condition type for Base price and the value is 515.30 $ and
Surcharge is 15% o the Base price which willl be 515.30*15/100 which equals to 77.295
The total is Baseprice + Surchage which was calculated as 515.30+77.295 = 592.595 ( but rounded as 592.60) which is showing a difference
If customer orders for 10 parts, then there will be 2 $ variace between the amount calclated and showed in SAP
Can you please let me know why this is displayed with rounding , is this standard behavious and if so, where was it controled.
thanks
santosh

I dont think this will be treated as an issue by the client. It is general that in exports, there will always be some difference in decimals. Considering all these things only, client would have arrived at their selling price. If I am correct, this would be addressed by having a separate G/L account for Gain or Loss in foreign exchange.
Check one such thread where a similar topic was discussed some time back.
[Re: Exports|Re: Exports]
May be you can check with your FI counter part also on this.
thanks
G. Lakshmipathi

Rounding Issue Excise Invoice and Accounting document

Hi
I have made and Excise Invoice with following values
Base Price                          4110
BED    10%                           411
CESS   2%     on BED               8
HEC     1%      on BED              4
In the Excise Table J_1IEXCDTL also values for BED is updated as 411, CESS as 8 and HEC as 4
But in Accounting Documetn following values gets updated
Base Price                          4110
BED    10%                           411
CESS   2%     on BED               8.22
HEC     1%      on BED              4.11
So at times there is a difference in both Excise Invoice and Acocunting Document. We want same values should appear in Excise Invoice and Accounting Document. Since EXCISE does not accept value in paise, we need to round off the value to the nearest rupee and accordingly update the accounting document.
My Pricing procedure mentions Cal Type as 17 Rounder off as per T001 R for BED / CESS /HEC...
Please guide...
Regards
Sanjeev

Dear Sanjeev,
Check whether there is a Condition type DIFF in the pricing procedure, and also in the invoice (conditions)
Check whether there is any account key assigned to it, in the pricing procedure.
Thanks & Regards,
Hegal K Charles

Issue during pricing in invoice

Hello everyone,
I have a question regarding pricing during invoicing.
We have a tax condition type used to calculate VAT on free goods sale. As we want tax to be computed based on 'sales order reason' entered during sales order, i created a new condition table with one of the fields as 'order reason' AUGRU assigned from structure KOMV. This table is assigned to existing access sequence and the tax based on order reason is correctly picked up during the order creation.
But this tax condition is missed during the billing creation. The copy control settings are set such that tax conditions are redetermined during billing. Hence the system is trying to redetermine the tax based on order reason. As it is failing to find the order reason during billing, the retrieval of condition record is failing.
I guess the issue is because the order reason is maintained at header level in order but at item level in invoice. In the field catalog of access seq, as i assigned AUGRU to header structure KOMV, the system is failing to find the order reason during invoice as its maintained at item level. I tried to assign AUGRU to item structure KOMP but that field is not available in KOMP.
Please let me know how to get around the problem.
Thanks,
Kits008

I have a full cycle testing.
Now, I understand where is problem occurred.
For sales order pricing, the order reason can pass to KOMK from order header and can be used in pricing determination procedure.
But for billing document, the order reason in "VBRP-AUGRU_AUFT", if you carry out a new pricing , then the system caused a problem like the post.
I suggest you implement the user exit (USEREXIT_PRICING_PREPARE_TKOMK (module pool SAPLV60A, program RV60AFZZ))
If you have further problem, please reply the post.
Flex Yang
FI/CO, MM, SD Certificated

Rounding issue in pricing

Similar Messages

Maybe you are looking for