Decimal issue in condition type

Hi All,
Present Calculation`s
Our SAP system in Sales Order
Mat - xxxx   Qty 12, Price 4,08 with 7,5 % discount
                   7,5% -    0,306
                  Net price -3,774
Calculation - 12 (Qty)*3,774=45,288         It gives 45,29 for invoice amount
Requirement :
customer calculation with 2 decimals
Price       4,08
7,5%        0,31
Net Price   3,77
Should calculate   12(Qty)*3,77=45,24
customer compares 45,24 with 45,29 and gets a difference of 5 cent hence he is not accepting the invoices because of the differences.
How can we make the decimal 0,306 to reach 0,31?
Note : In condition type the rounding rule commericail.We tried all the options but did not yield results. Your help i highly appreciated

Dear Friend,
One option is rounding rule in Condition Type, which is somethimg you have already tried. Just make sure that for all Condition Type mentioned here, the rounding rule is Commercial.
Now the real issue in you case is not Round Rule, but is is realted to Decimal Places.
You can set Decimal places at OY04 (IMG - SAP NetWeaver - General Settings - Currencies - Set Decimal Places for Currencies)
Here you will have to set the Decimal Places to 2 against Currency type (INR incase of India).
But please note that this setting is applicable on Currency & will have impact on all the places where the said Currency is used in system.
Hope this helps...
Thanks,
Jignesh Mehta

Similar Messages

Decimal places for condition type .

Dear sir,
I have a condition type like JCV1,ZADC & same are included in purchase order.These are the manual condition type.
I have created a purchase order & on condition tab page in once i enter 10 % for jcv1 condtion type ,system is showing that 10.000 .So i want that system should display 10.00 so please guide me how solve this .

Hi,
Check your decimal settings in your user id transaction SU01
Thanks
Diwakar

Currency conversion issue for condition type

Hello,
I am creating two invoice document.
1. Customs Invoice (ZCDS)
2. Inter company invoice.(IVA)
both the invoices should be similar. Same pricing procedure is used to create both the documents but in Customs invoice YUMU condition type is not getting converted whereas in IVA the condition type is getting converted. Can anyone tell me the possible reason for this?
ZCDS
IVA
Regards,
Jagjeet

Hi Jagjeet,
For IVA invoice type -(For condition type- YUMU)
Below highlighted part of code is changing KSTEU from 'E' to 'C' for IVA invoice using std prog RVIVAUFT.
For ZCDS Invoice Type -(For condition type- YUMU)
Program RVIVAUFT is not called since ZCDS is not trigerried using Output type unlike IVA.
Hence KSTEU is not getting updated from 'E' to 'C' in case of ZCDS.
To solve your problem write code in User exit - userexit_pricing_copy to change konv-ksteu to 'C' for YUMU condition type at runtime.This will definately solve your problem.This will ensure you get correct/same condition value for IVA and ZCDS...:)
Regards,
Vikas Mulay.

Pricing condition type pr00 not accepting the decimals.

Hi all,
i have a problem here at my client side, my client they are asking to have the price to be entered manually at the order level, my problem is   the conditon type PR00 is accepting only two decimal..    how to extend the decimal for the condition types.
for eg: Material 36.703.600    has price of 5.413, i am able to enter only 5.41, suppose if i enter the actual values it is saying the
" Input must be in the format __,___,___ V"
It says for decimal point update
"" (decimal point) (applies to numeric fields)
The decimal point occurs here (setting in the user master record)."
Which user master record i have to update.
kindly guide me on this
kumaresh

hi,
My problem is my client user wants to enter the price manually in PR00, since they are dealing with locksets and switches and also the do the shippment for outside the country . basically EU
the price are in euro   for eg 1 euro = 69.80 INR
for a material " 36.703.600" =   5.4135
they wanted to maintain for atleast three decimals
how to do it
regards
kumaresh

How to Avoid Duplicate Pricing Condition Types In Sales Order and Billing

Hi SAP Gurus
I have a requirement in Pricing (Sales and Distribution). We have issue duplicated condition types in Sales order and it causes wrong posting in to accounts.
I want make them inactive duplicated Condition type in Sales order and Billing Documents.
Please advice me how to make inactive status to duplicated Condition types
Thanks in Advance.
Ravikanth

Hi
You can use Exclusion Group
You can define 2 Groups and include 1 condition type in each
and define exlusion procedure
A   Best condition between condition types
B   Best condition within the condition type
C   Best condition between the two exclusion groups
D   Exclusive
E   Least favorable within the condition type
F   Least favorable betweent the two exclusion groups
you can use Exclusive to set your condition type or as per your requirement
Regards
Jitesh

Shipment Cost: Group Condition Type calculated on a special weight...

Here is the scenario: A shipment (truck) combines multiple deliveries, grouped on a stage when same destination (happens often).
A condition per LB is to be calculated on the cumulated weight per destination (per stage) BUT not simply on the gross weight, but on the heavier of 2 special weights: the business here uses a special formula according to the packaging, and it gives 2 weights (stored in Z fields of LIKP), an actual weight and a cubic weight.
The purpose is to identify for each delivery the heavier weight and to use cumulated the weight across the deliveries to the same destination to calculate the per CWT cost.
This is my first issue: the condition type is defined at Delivery calculation base, Calculation Type Multi-dimensional, and as a group condition). How do I define to use the cumulated of each delivery heavier weight ? In the Scale for condition type view, I used the scale basis D Gross Weight (which is not right..), there is also a field for a Scale Base Value formula, I wondered if that is what I should use..
My 2d issue: once the cost is calculated, I have to re-distribute it on the deliveries as per the proportion of their heavier weight compared to the total weight used for the calculationShould that be an alternate Condition Base Value formula in the pricing procedure (where xkwert would be.the heavier weight.would that be then a new Z field to be filled in by the user exit determing the heavier value) ??
Thanks a lot, it is a tough one, I know...who is the best ever shipment cost pricing consultant ? !

Hi Guys
Unfortunately I do not think that you will get an answer now. Either your question is not simple or we do not know.
So in the interest of keeping the Forum tidy and easier to surf through could you please close your thread and either try one of the other forums or try another post. I do not think that most people will bother to look this far back anymore.
Sorry I cannot help as I would if I could.
Regards
Frenchy.

Duplicate condition type at item and header level

hi all,
please help me to implement this
issue:
PO condition type for header and item should be checked for duplication.
atanu

Hi
I am not sure whether we can do this with IMG.
Need to use User exit MM06E005 (do not be confused with the description of this enhancement..you can use it)
Best regards
Ramki

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

Change decimal points in SD Condition type from 2 to 3, for EU

Hello,
We have a slight problem with the amounts. We are using resource related billing in the project and to track some expenses, there are some condition types created. Since the currency is maintained as EU, the decimal places are maintained as 2 decimals in OY04 and we dont want to change that.
We face an issue, when SAP Converts condition value from 3 to 2 decimals
For example, when in Contract we have an Condition Value of 100.025, this is converted to 100.03 and tax is applied on this amount.
When we create an invoice and subsequently a Credit Memo request, that will contain more than one item, and the sum of all items will have to sum up to 100.03, but this is never the case, as with the application of tax rate, the value comes to something like 100.02 or 100.04..
With 3 decimal points, this amount adds upto correct value.
So our ideal solution will be the have the Condition Values as 3 decimals and the Net value in 2 decimals.
Is there something that can be done for this?
Hoping for a quick response.
Regards
Maddy

SAP stores the 3 decimal value in XKOMV-kbetr and Xkomv-kwert is calculated based on this 3 decimal values...
I had a similar scenario with currency conversion and rounding issue in sales Order and Invoice processing, in VOFM routines... so I used a Floating point value and converted to character value and then used that 3 decimal value for calculation.

Tax condition types issue in sales order

Hi Friends,
I am bit lost with the following issue. I have searched sdn and other SAP forums for this. There were similar issues discussed but they didnu2019t solve my issue. There was exactly similar issue but it was unanswered. So I am posting the issue here to get some inputs.
This is the Indian tax scenario. I have configured pricing procedure where I have JVAT and JCST. If the company is selling to customer in the same state where company is located letu2019s say region 05 JCST 2% applicable. If the customer is outside region 05 then 5% JVAT should applicable.
=> In the pricing procedure it was like
150 0 JVAT
160 0 JCST
Both will be calculate on the gross value.
=> I have created two new tax classifications for customer master.
JCST   2   Tax liable outside region 05
JVAT 3    Tax liable inside region 05
So in the customer master I have both JCST and JVAT. I have created a customer with region 05 and in customer master under Billing document tab I have entries like below
Country    Name   Tax Category   Name   Tax classification Description
IN              India        JCST                IN: CST              2                  Tax liable outside region 05
IN              India        JVAT               IN: VAT              0                  Tax Exempt
=> I have created condition record for JCST with the following key combination
Country u2013 IN
Region of dlv. Plant u2013 05
Region u2013 05
TaxClass1-Cust. -- 2
TaxCl.Mat u2013 1
Amount u2013 2 percentage
Tax code u2013 A1 (TAXINN A1 2% Output tax)
=> With the above condition records maintained for JCST and maintaining tax classification as 2 for JCST and 0 for JVAT, I assume in Sales order SAP should calculate tax JCST 2 percentage. But in sales order SAP is not considering JCST and JVAT. For JVAT it makes sense as it does not have condition records. But I didnu2019t get the reason for not getting JCST. When I checked analysis and click on JCST condition type it says condition record is missing. Surprisingly when I click on the access details it shows u201CTaxClass1-Cust. as 0u201D it didnu2019t show as 2 as maintained in the customer master.
When I change the Tax classification for JVAT from 0 to 1 or from 0 to 3 in the customer master, in the analysis when I click on access details for JCST it shows tax classification maintained for JVAT that is as 1 or 3 so it seems SAP is not considering JCST in customer master at all. Why is that so?
The access (condition table) for JCST and JVAT are same.
Any inputs?

Hai SAP_2006,
We are also having similar requirement and inform the USER to maintain
In our customer master we gave like
Customer master:
Sales area data
Billing documents
JTX1     Tax Jurisdict.Code d     1     Full Tax 12.5%
JTX2     Tax Jurisdict.Code d     1     Full Tax 12.5%
JTX3     Tax Jurisdict.Code d     1     Full Tax 12.5%
JTX4     Tax Jurisdict.Code d     1     Full Tax 12.5%
To get LST we maintain
Country u2013 IN
Region of dlv. Plant u2013 05
Region u2013 05
TaxClass1-Cust. -- 1
TaxCl.Mat u2013 1
Amount u2013 12.5 percentage
Tax code u2013 A2 (TAXINN A1 12.5% Output tax)
To get CST
Country u2013 IN
Region of dlv. Plant u2013 05
Region u2013 06
TaxClass1-Cust. -- 1
TaxCl.Mat u2013 1
Amount u2013 12.5 percentage
Tax code u2013 A2 (TAXINN A2 12.5% Output tax)
In case if they want CST 2%, then user has to go
Sales order header Biiling
Alt tax Classification : Shouls change the Blank to 2 in the 1 box out of 4.
for that we maintained condition record as
Country u2013 IN
Region of dlv. Plant u2013 05
Region u2013 06
TaxClass1-Cust. -- 2
TaxCl.Mat u2013 1
Amount u2013 12.5 percentage
Tax code u2013 A3 (TAXINN A3 2% Output tax)
This doesn't require to change customer master regularly and default system finds LST or CST 12.5 unless they change to 2% system will not change automatic. So CST 2% Vs CSTfull tax risk is also avoided.
Regards,
Mani

Excise duty condition type and Purchase Order Print Issue

Dear Friends,
We have a issue related to Purchase order print out.
We are maintaining TAXINN.
We have implemented CIN and we are maintaining Excise Conditions i.e. Basic Excise in JMOP
In FV11 we are maintaining values for JMOP with plant and material Group combination.
In Purchase Order Tax calculation is happening correctly.
But issue is to find the value of taxes for Purchase Order Print.
We are using function module CALCULATE_TAX_FROM_NET_AMOUNT
and passing values of Company Code, Country, Currency, and Base amount to get the entries in condition types.
But we are not getting any entry even after passing the values.
How we can get these values in JMOP.
Regards
Kant

Why do you want to calculate the taxes during the PO Print when you are getting correct values in PO itself?
Modify your print program with pulling values directly from EKPO/ EKKO Tables and display it to Spool.
check with ur ABAP Person

PO Condition Type Issue

Hi All,
I have encounter a PO condition type issue, hope to get someone to enlighten me.
I have create both cuztomize condition type ZOT2 AND ZOT3.
With config in Control data 1
Cond. Class - A Discount or Surcharge
Calculat. type - B Fixed Amount
Cond. category - B Delivery cost
Group Condition
Select for Group cond. & RoundDiffComp
GrpCond.routine - 1 Overall Document
ZOT2 in header condition should be divided into item via value.
ZOT3 in header condition should be divided into item via quantity.
Both condition type havemanually enter with value 300
In the test PO I have created 3 materials:-
Material     Quantity     Net Price     Item Net
A     100     1,615.00     161,500.00
B     100          16.15         1,615.00
C     1000          16.15       16,150.00
In the Item view calculation for both condition type as stated below:-
ZOT2 - 270.27 : 2.70 : 27.03 (Ratios base on Value 100:1:10)
ZOT3 - 270.27 : 2.70 : 27.03 (Rations base on Quantity 1:1:10) the amount result should be 25: 25: 250 but the result I get from the system for condition type ZOT3 is the same as ZOT2.
Please advise how to reticfy the configuration. Thank you.

Eugenia Foong Pui Mun wrote:
Hi Shiva,
>
> I have try to config with the info you have suggested, but it does not seem to get the expected result.
Hi Eugenia...
I tested scenario with values you have mentioned. It works perfect both ways. Pls follow this....
1. Pls avert the changes I had suggested in my prev reply for changing the condition types. (group condition active, round diff condition & group cond routine, keep them as they are)
2. While you enter value in header with condition type ZOT2. the value gets properly distribute by the ratio 100:1:10 and thats perfect......Now
3. While you enter the values for condition type ZOT3 in the header...Pls note that your Total Qty is 1200 and the total condition value is 300 this means per unit qty the value is 300/1200 =0.25...
Now while you enter the values for ZOT3 in the header, enter 300 in the Amount column and 1200 in the Per column, meaning that the total of 300 shoud be divided into 1200 units irrespective of quantities per Line Item
Now check the results and you will have the distribution ratio 1:1:100
NB:For ZOT3 (Qty base) to work the UoM for all the line items must be similar
Pls check and revert
Regards
Shiva
Edited by: Shivaspatil on Nov 24, 2011 12:42 PM

Pricing condition type Issue YPR0--- ZPR1

Hi All,
WE have a pricing issue, for example we have a condition type YPR0 and we use a pricing procedure which i will call ZME600, we are basically creating a new condition type to be called ZPR1 to replace YPR0, now in the copy control, delivery document to billing, for item category YBHP, the price type setting is ''G ''which means copy pricing elements unchanged and redetermine taxes, if we use this option, when we upload new price list, create a billing document, it will change the price on all open sales orders rather than keep the original price, so option is, change the pricing type setting to a ''D'' which basically copies all pricing elements unchanged, will this be a better solution? what happens when we start using new condition type ZPR1 to replace YPRO, the system will no longer recognise YPR0, if there any options to work around this, some have suggested linking YPR0 to ZPR1 in the pricing procedure??

Hi,
Please check V/06 conditiontype functionlality of tht condition type. There it might have been activated for both header level and item level. that is the reason it is printing in both levels. Please do needful setting there..
Regards
Sankar

Condition type price issue

Hello,
I have a item level condition type ZMAT. This condition type will be applicable when you order a material XXX with qty 5 and there will be 10% discount. Suppose we create an order with material XXX and qty 3, still this condition type ZMAT is appearing in condition tab with amount the discount amount as ZERO.
I don't want to appear this condition type in case if the material XXX is having qty less then 5 in an order. Please help me how to fix this issue.
Thanks,
Shreekant

In your pricing routine, check if qty is less than 5 then set sy-subrc = 4.

Issue in using custom discount condition type in pricing agreement at Service Contract line item level

Hello
We are facing an issue while using a Z discount condition type in price agreement at service contract line item level.
A Z Condition type has been created in ECC and assigned to the pricing procedure. This pricing procedure is downloaded in CRM and determined in the service contract.
A condition maintenance group using this Z condition type is created in CRM and assigned to service contract item category.
Condition records are created in CRM for this condition type/condition maintenance group for specific products along with sales org and discount percentage.
But when the price agreement(using this condition type) is used at the item level of a service contract, the system throws errors (related to product/unit of measure and sales org, even though no issues seem to be there)and thus the price agreement is not allowed to be used.
If anyone has worked on such kind of scenario, please get in touch, I will share more details for the same.
Regards
Ankit Arora

Dear Ankit,
Once the pricing procedure is downloaded, please maintain the document pricing procedure at service contract header level, and maintain the customer pricing procedure at business partner sales area billing data.
In spro, maintain the pricing procedure for the combination of sales area, document pricing procedure, customer pricing procedure.
Please crosscheck whether the condition table is active or not.
Regards,
Maddy

Decimal issue in condition type

Similar Messages

Maybe you are looking for