Condition Type Rounding Rule

Hi all,
All my condition types have rounding rule as Commercial. When the client was checking calculation after billing in the accounting document; for VAT condition type, it is rounding below.
For example; VAT amount is 2164.989; it should round as 2164.99, but it is rounding as 2164.98. The client is very particular about this.
But the same rounding rules have been used for all the condition types and the client does not have any problem with rounding for those; can somebody explain is there any additional setting required. This is very urgent as they have gone live and they are not entering backlog orders because of this problem.
Thanks and Regards,
Adithya
Edited by: Adi1976 on Feb 12, 2012 11:54 AM

Hi
try with rouding rule A (Round Up) in condition type. Txn code: M/06.
regards
Srinivas

Similar Messages

Condition Types in Price Determination Process

Hi
Can any one explain me about in Detail about the VARIOUS TABS that work in the CONDITION TYPE of PRICE DETERMINATION PROCESS
Thanks & Regards,
Senmani.

hi
hi
control data 1 :
Condition Class is a grouping that lets you control each condition type differently.
For example, the condition type "taxes" defines that the taxes in a document must be recalculated if the country of the ship-to party changes.
Condition category (examples: tax, freight, price, cost)
A classification of conditions according to pre-defined categories (for example, all conditions that relate to freight costs).
Condition category basically identifies the type pf cost the Condition type is being used for & can be used for .
Calculation type
Determines how the system calculates prices, discounts, or surcharges in a condition. For example, the system can calculate a price as a fixed amount or as a percentage based on quantity, volume, or weight.
The calculation type can be set when generating new condition records. If this does not happen, the calculation type maintained here is valid for the condition record
Rounding rule
The rule that determines how the system rounds off condition values during pricing. The last digit will be rounded.
Example
In the standard rounding rule '_', values are rounded off according to business standards:
10.454 -> 10.45 DEM
10.455 -> 10.46 DEM
In rounding rule 'A', values are always rounded up:
10.459 -> 10.46 DEM
10.451 -> 10.46 DEM
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.
Structure condition
controls whether the condition type should be a duplicated condition or a cumulated condition.
This control is only helpful when you use bill of materials or configurable materials.
Aduplicated condition is duplicated into all assigned items.
A cumulated condition contains the net value of all assigned items.
control data 2 :
promotions
Specifies that the condition type in question is only valid for Promotions.
Use
Conditions for which this indicator has been set can only be maintained via the 'Promotion' menu - not via the Purchasing menu.
Accrual (e.g. Freight)
Indicates that the system posts the amounts resulting from this condition to financial accounting as accruals.
Use
If you mark this indicator, the condition appears in the document as a statistical condition.
Before Release 4.0 variant conditions (VA00) had to be created with the condition category 'O'
Problem: It was not possible to indicate a 'Variant condition' at the same time as 'Internal costing condition' and 'Freight'.
Solution: For this reason more indicators are being set up in 4.0 for the condition type:
'Variant condition' (KVARC)
'Internal costing condition' (KFKIV)
The characteristic values O and I for the condition category must no longer be used.
For more information, see the note 93426.
inv.list condi
Condition for invoice list
Marks the condition type as relevant for internal costing.
Quantity conversion
This field controls the quantity conversion during determination of the condition basis.
The field is only relevant for calculation rule 'C' (quantity- dependent.
It is relevant if the sales quantity unit and the condition quantity unit are identical (and is different to the basis quantity unit).
Deactivated: The condition basis quantity is converted via the quantity to the stockkeeping unit. This means that the condition quantity is determined for planned factors. This means that a change to the conversion factors in the delivery or the order are not taken into account.
Rounding errors can occur during quantity conversion.
Activated: If the sales quantity unit and the condition quantity unit are identical, the quantity of the document item is used, i.e. the actual quantity.
Condition for inter-company billing
Conditions for Internal Costing, for example PI01 and PI01 were defined before Release 4.0 by KNTYP = I (Price for internal costing).
Problem: It was not possible to indicate 'Freight condition' at the same time as 'Internal costing condition' and 'Variant condition'.
Solution: Therefore a new indicator 'Internal costing condition' (KFKIV) has been set up. You can use this to indicate a freight condition as an internal costing condition. For more information, see note 93426.
Scale :
Scale basis indicator
Determines how the system interprets a pricing scale in a condition. For example, the scale can be based on quantity, weight, or volume
Checking rule for scale rates
Indicates whether the scale rates must be entered in ascending or descending order.
Scale Type
Indicator that controls the validity of the scale value or percentage:
From a certain quantity or value (base scale)
Up to a certain quantity or value (to-scale)
Alternatively, it is possible to work with interval scales. Interval scales must be stored in the condition type, that is, the scale type "interval scale" cannot be changed in the condition record. The reason for this is technical restrictions resulting from the programming within pricing.
Formula for scale base value
Formula for determining the scale base value.
Use
You can use this formula to specify calculation methods that are not provided in the standard system.
reward points if helpful
thanks and regards
ravikant dewangan

Rounding up off values using Different Condition types

Dear All,
There is a requirement from the client where they want to round up the values in all the condition type values.For Example:
ZPR0- 1525
ZCOM(15%)- 228.75(It Should be 229.00)
NBT(Tax2%) 25.93(It Should be 26)
Similarly all the values for the condition should be calculated as the above mentioned scenario .Kindly suggest
Thank You!
Chakradhara

1.In V/06 goto the respective conditions type and in rounding rule field maintain A
2.goto pricing procdure in v/08 in calculation type field maintain routine 17 against the condition type s
3.in OB90 maintain 100( rounding unit) against your company code then check the results.
Thanks
Srinu.

Condition type value rounding

Hi Experts
I want to know about rounding of decimal in PO conditions. We have customised condition type like ZFRE in % and it is found that when PO is created i see that ZFRE value is rounded i.e suppose if value is coming as 3.97 then the system takes automatically 4 and if value is 39.37 then the value becomes automatically 39. The decimal places dont appear in PO. I thought it is because of condition type configuration.
The ZFRE condition type has setting as:
rounding rule - commercial(standard)
It is not set as rounding up or rounding down. How the values are not geting rounded?
Thanks
Dinakar

Hi
From the above suggestion you cant round off the condition type as said. Use t.code OB90 and for your company code and currency and maintain 100 in the field 'Unit to be rounded up to'. But it is client level setting. Be careful while setting this.
Then go to your pricing procedure and assign Routine-17-Rounding as perT001R in Altcaltype field. Then create order. Your requirement will be solved.
Reward if helpful

Regarding rounding rule in condition

hi all,
i am facing an issue related pricing condition,
i have created one condition type- ZROU(round off rule).
this means supoose, i have net price in the PO is 23.60. if i put this condition and i put .40, then total price should be 24. and its comming while creating the Po.
but when iam creating Migo, in accounting document, the price should be taken as 24 but it is taking 23.60. why this condition type effect is not reflecting to MIGO & MIRO.
i need the solution urgently, pls help.
regards,
susanta

Hi,
Create Condition Type "ZROU" as a Positive discount condition. In M/06 keep
Cond. class - A (Discount or surcharge)
Calculat.type - B (Fixed amount)
Use it with Base Price in Pricing
For e.g. In MM Pricing (M/08)
Step 10 - PB00 (Base Price) = 23.60 INR
Step 20 - ZROU (Rounding Value) = 0.40 INR
Step 30 - Net Value = 24.00 INR (From 10 To 30)
If you donot want it as Discount condition then use it as delivery cost condition and mark "Accrual" and do posting to a separate GL. by creating and assigning a new A/c key under Accrual column of Pricing (M/08)
Ans in OBYC > Assign GL as "Rounding Off Difference" for that new A/c Key

Rounding of condition type

Pls guide me to set rounding for perticuler condition type into pricing procedure of PO

Hi
You can round off the value to nearest in condition type.
Go to SPRO and Select the condition type and in that under control data you can use rounding rule (as A and B..).
Regards,
Manish

Problem of DIFF (Rounding Off) Condition Type in Sales Pricing Procedure

Hi All,
This problem is related to Sales Order. The system is not picking up a condition type in the pricing procedure.
For example when I am raising a sales Order where the Trade Price is being calculated with the help of a Alternative Calculation Type , Subtotal 1 , X in the the Print column and Posting Key ERL are assigned to it.Here in the end the condition type DIFF is not getting populated in the pricing though it is maintained in the pricing procedure. When I am checking in the pricing analysis the error message and its detailed description which is shown as follows -
DIFF 011 Condition ignored (requirement 013 not fulfilled)
The requirement 1. was assigned to this condition in the pricing procedure. This requirement was not met in the preliminary condition step, and so the condition was excluded from further processing.
You can use Additional information to display the requirements used.
Now considering the above scenario please suggest to attain my requirement.
Thanks & Regards
Priyanka

Dear Priyanka,
The "reqt" field in the pricing procedure basically tells d system that the routine mentioned in this field is a sort of prerequisite without fullfilling of which the associated condition type will not get xecuted.
In ur case u have selected "1" which is for condition types A001, B001 etc used in "material listing / xclusion" function.
For condition type DIFF, the correct value is "13" i.e "Rounding as per T001R".
So just replace "1" with "13", things will b fine.
Please close the thread if answered.
regards
Param

Condition type: DIFF-Rounding Off

Dear Colleagues,
The condition type DIFF-Rounding off is not woring in sales order.
Config details as follows.
1. OB90->Respective Company Code, Currency & rounding unit of '5' is being set in this transaction.
2. Define condition type DIFF via Transaction V/06. This condition type is maintained as "Group and Item Condition".
3. Included the condition type DIFF in the pricing procedure:setting are as per standard Reqt = 13, Caltype = 16, BasType = 4.
Two issues noticed:
1) In the sales order: DIFF is determined at item level and header level as well but value of DIFF shows "Zero".
2) Crdit memo: DIFF was not determined.
In both the cases Net value + Tax was in decimals, supposed to round off.
Could anyone help what needs to be done or missing data.
What exactly the functionaly of DIFF condittion type... Does it round of Net value + Tax or each condition value .
Thanks & Regards,
Vamsi P.

Further, you can refer following SAP notes for your understanding and reference:
- Note 0022963
: Rounding problems in condition basis
- Note 0080183
: Rounding
- Note 0130742
: Roundings in subtotal lines
- Note 0154789
: Roundings in subtotal lines, part 2
- Note 0311135
: Rounding errors of condition value
- Note 0886532
: Pricing: Displaying and rounding numbers
- Note 1481061
: Rounding Customizing in SD
Regards
JP

Condition type for rounding-off

Dear all,
Is there any pricing condition for rounding off the PO values,
For example if the total PO Value is comes Rs 5990/- & i want to make it Rs 6000/-.In the same way i want to deduct some amount to make the rounding off like total PO Value comes as Rs 10015/-, & i want to make it Rs 10000/- by applying the same condition.
Or Can i create a new condition type for this type of scenerios.
Quick reply will be highly appreciated.
Thanks & Regards
Prasant sekhar

in condition type u have a filed for rounding off
so use the relveant option from f4 help in that field and u can round of the value as u want to be
go to tcode m/06
and select ur conditoin type and click on the detail button and do the relevant settings

Rounding Rule upto 3 Decimal Places in Tax Condition(SABRIX)

Hi,
We are Using SABRIX for Tax determination and need to round up Condition Type XR1- XR6 to round upto 3 Decimal Places.
Do we need to To Change ALT Calc Type- 301306or Alt Cond Base Value -- 16 or have to change Currency decimal Places in transaction OY04/OY03.
Kindly Suggest.
Thanks
Amit

Hi,
Tax % for customer is decided in SABRIX, Where does TaX calculated?? In SABRIX or in SAP.
Thanks
Amit
Edited by: AMIT GUPTA on Mar 31, 2010 10:54 AM

Round up in condition type

Hi everyone,
I am able to round up in condition type for second digit. but I want to know how we can round up for first digit.

ROUNDING UP MEANS IF THE DISCOUNT IS 4.3, ITS ROUND TO 5, IN ROUND DOWN IS IF 4.7 MAKES 4/-, IN COMMERICAL IF THE DISCOUNT IS 4.3 IT MAKES 4/- AND IF THE DIOSCOUNT IS 4.7 ITMAKES 5/-
HOPE U GOT IT..
REWARD IF IT HELPS
KIRAN

Substitution rule for SD Condition type

We have a pricing procedure ZPOS in which we have SD condition type ZM10 for 7% additional special levy on the basic billing.
The account key ERS is assigned to the condition type and a GL is assigned to the account key in VKOA settings.
Based on different invoice types, the special levy amount should hit different GL accounts via a substitution rule without creating multiple condition types.
Please respond if anyone has a solution to this scenario.

Hello,
You can use business transaction event for G/L account changing while posting FI documents.
But you can use SD exit while transfering SD invoice to FI document.
Please try this exit below,
SDVFX004 - User exit G/L line in transfer to accounting - EXIT_SAPLV60B_004
I hope this exit more useful than substitution.
Regards,
Burak

JMOD condition type value should be always rounded up instead of commercial

Hi Helpers,
I need one clarification from you all based on your expertise,
1. JMOD condition type value should be always rounded up instead of commercial.
2. i have been already made rounding up in the condition type JMOD in the transaction V/06. but unfortunatly not working.
3. after that we found that there is configuration change in spro (company code setting in the indai taxation-CIN) in the Logistic general> tax on goods movement>india> basic setting> company code setting for the commercialrounding, but the same is already ennabled with SD rounding IND.
Need your expertise on this.How shall we make it round up always for JMOD condition value. below is an example for your further analysis.
Example: if values UTXJ is : 8,913.40 and JMOD will be calculated based on UTXJ as 10% thats is 891.34.
Actually this should be 892 as per the requiremen.t

I just recently rolled off a project in Europe that had an issue similar to this. We were having rounding issues as a result of % discounts.
However, we did come up with a solution that is provided by SAP.
Please review OSS note 80183 on SAP rounding and the solutions provided within the note.
I hope this helps.
Kind Regards,
Jason

Rounding Condition Types

Hi guys
I have a requirement that in my pricing procedure I want the condition type which can round off the total vale if it is having any fraction value in the sales order. I have used some condition type like RNTP & RNTM, DIFF but couldnu2019t able to get right answer.
So please provide me right information relating too all the above Condition Types.

Dear Chandra
Try with this
For the net value field, give Routine 16 in the Alt. Cal. Type in the pricing procedure. Addition to the above setting also add Routine 17 to Netvalue.
thanks
G. Lakshmipathi

Round off Condition type

Hi
I have maintained Condition type for Rounding off (ZROU) for the sales order value as header condition.Whatever the value calculated as Round off value is proportionally distributed amoung the line items and getting posted as line item wise.i.e if round off value is 0.40 paise same value is distributed amoung the line items let say 0.20 paisa for 1 st line item 0.20 for second.But i need posting has to be as header level only i.e 0.40 paise and not like 0.20paise twice.can anybody help me in this issue

Hi Karthikeyan,
This is not possible. SAP can store all conditions at item level only, even if it is entered at header. So if you enter a header condition, it splits it at item level, and stores it at the item level.
See SAP Note 876617 (point 3):
3. How is an 'actual' header condition distributed to the pricing result of the individual document items?
This depends on further Customizing settings of the condition type, in particular on the calculation type (field KRECH) and on whether the group condition (field KGRPE) is set or not.
Example:
For a header condition with calculation type 'Fixed Amount', the amount entered on the header condition screen is duplicated in each item if the condition is not set as a group condition.
However, if the condition is set as a group condition, the amount entered on the header is distributed proportionally (that is, in the relationship of the relevant condition bases at item level) and a rounding difference adjustment may be carried out (compare section 7).
Hope this helps,
Regards
Nikhilesh

Condition Type Rounding Rule

Similar Messages

Maybe you are looking for