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

Similar Messages

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

How Rounding Off condition works?

Hi
My client has 2 pricing procedures for different sales organizations.
In one pricing procedure, rounding off is taking place successfully, where as for other it is not working.
At first place, I want to understand how this condition works, and do we write any routine etc for the same?
need to understand the functionality in order to analyse the procedure, and effect.
Thanks
Trupti

need some input,
you want to know Rounding Off for PRICING PROCEDURE??
or you want to know Rounding Off for condition type??
If you want to know Rounding Off for condition type then go to V/06 select your condition type
in Control Data 1, there is Rounding rule
If you select '_', values are rounded off according to business standards:
10.454 -> 10.45
If you select'A', values are always rounded up:
10.459 -> 10.46
If you select 'B', values are always rounded down:
1045.9 -> 1045 L

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

DIscount condition types mapping to value field (+/-)

Hi,
1)While mapping SD condition types to Copa value fields, do we need to check the transfer +/- symbol for all discount condition types...
or when do we need to check it..
2) In our case we have some 4 to 5 discount condition types mapped to copa... If we check that symbol, as discount will always be negative system is posting discount values in negative in copa. At the time of report execution, since we give formula as Sales Less discount and discount is already negative in system it is getting added... so we are planning to change formula as sales + discounts... is that approach is right?
Reg
Karthik

Hi Ajay,
Thanks for your quick reply... generally for which condition types do we need to check this indicator in ke4i... for all discount condition types and rounding off condition types... is that right? Because as I told we have some 4 to 5 discount condition types and we have ticked for only one discount condition type which is mostly used...
Reg
Karthik

Incorrect value for condition type P101 in Stock Transport order

Hello Friends,
We have a scenario where in transfering material from one plant to another using the STO way , the excise duty from the sending plant should be loadded on the inventory of the receiving plant.
In this scenario the excise duty X% is calculated on the condition type P101 (which is the standard price or the moving average price from the material master accounting view)
Giving below a sample cas e for the error occuring:-
- Suppose a material M1 has stock of 5,00,000 EA of total value 2,03,707.16 inr , thus the moving average price calculated by the system is 0.41 inr per unit.
- When i try to create the Stock transport order for this material the P101 condition value now appears as 2,05,000 inr for same 5,00,000 Quantity
If we check the difference between the material master value and condition value their is a difference of 1292.84
As mentioned the excise duty(X%) is now getting calcuated on 2,05,000 . When we do post goods issue against the delivery created for the stock transport order the inventory value posted is from the material master i.e 2,03,707.16 , but the excise value are calculated on 2,05,000 in the Purchase.
This difference in value between the condition P101 in PO and the actual inventory posting value is resulting in incorrect calcuation of the excise duty.
can some help me regarding this issue.
regards,

Dear Gundam,
This might accured due to the rounding off problem, so please chek the rounding off condition type is available in the invoice or not.
If not plaese maintain the rounding off condition type sames as in the sales order then try.
I hope this will help you,
Regards,
Murali.

Condition type for condition record

Hi SAP All
             i configure the one round off condition type that type to give value is some points wise like that 0.10,0.30.0.65....but system not acceptation this values how to maintain.
     the round off condition type we r given manually or system will give na plz provide some more explanation regarding this one
   the solution help for me i will give points
regards
Raju

Hi,
If your basic requirement is just to round up condition values, you may use the following:-
You can tackle this by using standard routine in your pricing procedure.
In the 'Caltype' column in pricing that is "Condition formula for alternative calculation type", you need to add routine number "17 Rounding as perT001R", before those excise conditions which you want rounded.
Additionally, in table T001R such rounding data should be maintained.
For this goto SPRO - SAP NetWeaver - General Settings - Currencies - Define rounding rules for currencies
here maintain: Co, Code + Currency = 100
This will solve your problem
Regards
Dhananjay

Rounding Off Value is not copying from Sales Order to Invoice

Hi Experts,
In Pricing Procedure i maintained DIFF- Rounding Off Condition type with the following Combinations.
Print:X
Requirement:13
Cal Type: 16
Bas Type: 4
When i create sales order the system is calculating Rounding Off after saving the sales order.The requirement is that it should shows the rounding off value before saving the sales order.Secondly when i make invoice the rounding off value is not copying from the saved sales order.After i save the invoice in VF02 the rounding off value is coming .
Regards
Subhasish

Cond type DIFF has cond catgory L Generally new when copying. So the value from sales order will not be copied, it will be redetermined in invoice.
Also rounding off cond is to round the total value which can change in invoice based on the invoice qty.

Rounding off quotation value

hi all
i have created a quotation, and in quotation output i want the total value to be rounded of to nearest rupee how i have to do it?
regards
rag

Dear Tarun,
You can maintain DIFF Rounding off condition type in your pricing procedure to do the rounding off the total quotation value.
The DIFF condition type you need to keep after total value and assign account key to that.
Maintain Requirement as 13     Rounding as perT001R
             CalType as        16     Rounding the total
             BasType as         4     Net Value Plus Tax for that DIFF condition type in your quotation pricing procedure.
I hope this will help you,
Regards,
Murali.
Edited by: Murali Mohan.Tallapaneni on Dec 6, 2008 10:26 AM

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

Invoice Amount Rounding Off

Good Day.
Is it possible to have my selling price have 2 decimal places, but the Invoice amount will be rounded of to hundreds, only for a specific currency?
Example:
Price: 123.45 Yen per 1 pc
Invoice Amount: 123.00 Yen <-- rounded off, does not require decimal place
Let me know.
Best regards,

hi
not a problem.
you need to maintain prices for your product with 2 decimals in VK11 so that this brings 2 decimal pricing in sale order.
for rounding off in invoicing activate 'round off' condtion type to the nearest yen either up or down.
hope this is useful to u.
suresh

VAT Condition Type

Hi All,
Is there any set off condition type for VAT (JVRD)?
regards,
Mohan.
Edited by: Mohan on Jul 9, 2009 10:43 AM
Edited by: Mohan on Jul 13, 2009 12:39 PM

closed

Need help with rounding of wage types in IT0008

Hi,
We have a requirement to round off wage type 1003 - Monthly Salary in IT0008. The amount entered in this wage type has to be rounded to the nearest 10's for India, 100's for Japan and 1000's for South Korea. For all other countries it should be rounded to the nearest whole number.
I have tried this by setting up the Rounding Type to A/B/C and Rounding Divisor to 10/100/1000 in the wagetype characteristics table T511 for each of the above scenarios respectively but nothing worked.
If we cannot find a way to set this up through configuration, we are planning to use the user exit in IT0008 to achieve this functionality. So anay ABAPER's also might pitch in for help...
This is an existing wage type and we just need to apply rounding this time. Need expert advice pls...
Thanks,
Priya

Actually A/B/C and 10/100/1000 should work but it start rounding off from decimal points. For example if you will put 1000 for round off then it will round off to 10.
Btw since you are going with user exit, you can do it. What you need to do is read the wage type and indirect valuation module (as indirectly valuated wage type don't give you amount so you need to read module variant and valuate the wage type) and then write the code for round off.
Let me know if you need some more clarification on this.

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

Round off Condition type

Similar Messages

Maybe you are looking for