Group Condition at Header on Scale basis

Hi,
I want to know, how system assign the corresponding condition amount of header to individual item .
in our system
e.g in our system we have condition ZD22 for packainf and forwading charges as fixed amount and scale is qty
i have add Rs 300 at header and in my PO there are 3 item having qty, 100 ,100 and 2500 after adding condition amount at header as 300 when i checked the on individual item i found for first two item it 75.89 each and for third item the amount is 148.22
I want to know how system divides the header amount to individual item if scale is qty.
regards,
zafar

Hi
Kindly note this scenario
Condition value XXXX    180
Marked as Header + Group Condition
PO
Item 1       qty   1           Price 300
Item 2       qty   1           Price 100
Item 3       qty   1           Price 50
Ratio = Based on value =Qty*Value
300:100:50   = 6:2:1
Therefore XXXX distributed to items as   120 , 40,20

Similar Messages

Pricing condition type with Scale basis "G"

Hi,
Did anybody tried to use scale basis "G"?
I created formula for scale base where I calculate xkwert. The value seems correctly transferred to kstbs (scale base value) in sales order pricing, but the amount of the condition is not recalculated accordingly.
Thanks
Carlo
I solved the problem today. Thanks all.
Message was edited by: Carlo Noventa

Hi Tushar
You need to create your own formula or routine in Transaction VOFM.
Put this routine in front of your condition type in Pricing procedure.
Also in maintain condition types keep your scale basis as 'G'
Reward if this help.
Regards
Karan

GROUP CONDITION ROUTINE IN PO

Hi all,
in M/06 I have put flag GROUP CONDITION and I have choosen GROUP CONDITION ROUTINE 3 (material Pricing group).
Calculation Type= Quantity
Scale basis= Quantity
I have created 2 condition records for 2 materials with scales.
These 2 materials have the same material price group.
Why when I do purchase order the system doesn't accumulate the item quantities?
If I do the same configuration in SD the system sum the quantities and get the right scales for each material.
Does the group condition routine 3 valid only for SD documents (Sales Order) and not for MM documents (Purchase Order)?
Thanks a lot
Best regards
Alba Battolini
Moderator message: Thread locked because of violating forum rules: subject in capital letters. Please read and follow the forum rules
Edited by: Jürgen L. on Mar 9, 2012 4:38 PM

HI,
Condition type for Planned delivery cost, like FRA1, FRB1,ect, have Acc. key& Accrual key like FRE, FR1 in PO pricing procedure(calculation schema)
Deselected the indictor of Statistics.
By doing it will included the deliverycost into the net price by removing Statictis indicator.
Regards
KK

Set up pricing - Group condition doesnt works

Hi Gurus,
Please provide me your inputs.
Can SAP determine the sales price as described in the below two cases.
Case 1:
Sales price for material M1, from 01.01.2011 u2013 31.07.2011
Quantity         Price
0                         100
25      90
100      75
Sales price for material M1, from 01.08.2011 u2013 31.12.9999
Quantity      Price
0      105
25      94
100      78
Sales order (note the difference in pricing date)
Total quantity = 38, second scale should be used
Item      Material      Pricing date      Quantity      Price
10      M1      31.07.2011      17      90
20      M1      31.08.2011      21      94
Many Thanks for your answers
Sharan

Dear Sumanth,
Thanks a lot for your answer. I am relatively new to this subject. Please elaborate your answer for me to maintain the settings in copy control.
The scenario is - New condition type ZPR0 is created with group condition. And the scales are maintained as mentioned in the problem.
Lets say Order is created on date - 23/11/2011 with two lines
Line 1 - Material M1 - Quantity 17 - Pricing date 31.07.2011(Maintained at item level)
Line 2 - Material M1 - Quantity 21 - Pricing date 31.08.2011(Maintained at item level)
With scales maintained, because of the pricing date , system picks up individual scales and it doesnt accumulates the quantity. How to tell system to accumulate quantity and then check scale based on the pricing date.
Thanks for your help again,
Sharan

Group condition.

Hi,
I have a requirement as below: I have a group condition(ZR09 which is scale based) which has to be calculated as follows: For every line item the net value is added and finally the condition ZR09 is applied. Now the problem is I have certain cases where the condition ZR09 is inactive(Because of exclusions). Currently the value of ZR09 is calculated based on whole line item net value.
The requirement is if for a particular line item the group condition ZR09 is inactive then the corresponding net value of the line should not be considered for calculating the group condition. I have written a scale based formula for this and assigned in the condition type. It works fine during creation of the sales order but when I add a new line item to an existing sales order the problem comes and the calculation of group condition is done based on certain other values.
Did any one faced this situation earlier. Again I think this issue can be solved by some customizing(Which I am not sure of). Can anyone suggest a work around for this?
Regards,
Murari.

Hi
See Note 315792 - Group conditions of the same amount on item. It suggest how to create a VOFM and set it in V/06 for this condition in group key routine to avoid this kind of problems.
I hope this helps you
Regards
Eduardo

Scale type D for group conditions

Hi all,
I am creating a new group condition and am trying to make it scale type D - graduated-to-interval scale. However because this is a group condition, SAP is giving me an error (Scale type 'D' cannot be used for group condition 'X').
What is the best solution to this?
I would like to give discounts based on:
Sales quantity:
1-100 = 15% off
101-200 = 25%
201-300 = 35%
301-400 = 45%

Hello
This is b'coz your condition type with active Group condition Indicator. That means, here the system calculates the basis for the scale value from more than one item in the document.
So, the scale D maintain in Scale basis for those condition type, does not go with it and throws an Error.
Thus, if you want to scale functionality for condition type with group condition indicators use GrpCond.routine to maintain routine.
Routine number for creating group key identifies a routine that calculates the basis for the scale value when a group condition occurs in pricing.
For instance.
Check routine 3-Mat.Pricing Group. This is an example of a structure of group key formula. A structure of group key formula can be used to influence the basis the system uses when reading the scale of a group condition. The formula is assigned to a group condition type in customizing.
Formula '3' adds up the quantities / values of all of the line items in the sales document that have the same material pricing group (field KONDM) as the current sales document line item.
A company defines a particular discount (condition type Z001) with scales based on weight. When a sales order line item is priced that is eligible for the Z001 discount, the user would like the system to read the scale with not just the weight of the current line item, but the combined weight of all items in the sales document that have the same material pricing group as the current line item. To accomplish this, the user defines condition type Z001 as a group condition and assigns structure of group key formula '3' to it in customizing.
I hope this assist you.
Thanks & Regards
JP

Can a scales-based condition be defined as group condition?

We have a scales-based condition, applying to certain items. A formula has been created, which basically loops through all items equipped with this condition, calculating the value based on the accumulated quantity of all items up to the one currently calculated. The condition rebate is then applied if the "max" value hasn't been exceeded.
The formula itself works fine as long as the condition is not defined as a group condition. If it is set as such, the condition value is overwritten due to the sum quantity of all items exceeding the scale maximum... the client insists on the condition being a group condition, whereas I think this destroys the purpose (calculate rebate for items up to the last one before max is reached). Any suggestions?

Create a hidden item lets say P1_MYITEM and set its default value to *2*
Just amend the IR SQL query to add a where clause like below
//remember the default value of item is 2 and this will evaluate to false and return no data initially
where 1 = :P1_MYITEMBefore setting your filters and refreshing the report just set the value of the item P1_MYITEM to *1* (make sure you set the item's value into session state using Page Items to Submit property)
So ideally the dummy where clause will now evaluate to true and the data will be shown

Condition types and scale basis

Hi
Can any one tell me for conditions types and scale basis for maintaining condition records
thanx in adv

dear
Scales in nothing but a range of order quantity, according to the pricing element depending upon the range of quantity prices way be increased/decreased, higher discounts, low freight changes can be offered.
Ex: when per one item is 100/- if customer placed the order for
Range          price
100/-
95/-
90/-
Check --value:
We can specify the changing rule for scale rates as ascending or descending.
Scale type:
This indicator controls the validity of the scale value or percentage from certain quantities or value up to certain quantity or value, alternatively it is possible to work with internal scales that must be stored in the condition type that is the scale type the interval scale cant be change in the condition record due to technical reasons ex: condition type PR02 graduated scale.
Scale formula:
We can specify the formula for determining the scale base value; we can provide formulas that has not been provided in the standard system. Ex: condition type KP003 to support mixed pallet surcharges can be used
Condition scales:
We can maintain scales for each and every condition type so that we can determine pricing condition value depending upon the range of order quantity.
Ex: If we maintain condition record for PR00 for material one as a Rs.1000/- for one material then we can maintain scale for this material like below.
     Quantity          Price
0-10     1000.00
11-20     999.00
21-30     998.00
31-40     997.00
Configuration settings:
Go to VK11; maintain condition record for PR00,
Select line item and click on scale icon on the application tool bar &
Maintain scale rates accordingly, save it & exit.
Got to VA01 and raise scales order, validity periods to scale. Check the condition value
rewards if it helps
siva
Message was edited by:
        siva narayana

Scale base value condition pricing

Hello I am creating a pricing condition ZPC1 that will only be applied to about half the items on the sales order but will be Scaled base need to be on the total number of items ordered weather the condition is applied to that item or not .
For example
The scale will be
0 -500       $1 per case
501 - 100 .50 per case
item 1    500 case order    will have pricing condition ZPC1
item 2    500 case order    will NOT have pricing condition ZPC1
I want the Scale price to be $.50 per case on item 1 not $1 per case.
The condition type is set up as
Scale basis C Quantity scale
Thanks James

Dear James
Go to V/06, Selct your condtion type ZPC1, open controls.
In Scales Change Check value from Descending to Ascending, save.
Now go to vk11 and maintain the condition record,
enter line item , select, click on scale, put your range and amount.
Save it, Either overwrite previous one or go to vk12, delete previous entry and then go ahead with the steps mentioned above.
Regards
Pavan

Scale basis in condition type?

Hi
I want to know the exact functionality of Scale basis in a condition type.
Basically what does scale basis, scale formulae, check value ,scale type etc mean?
Explanation with an example would be highly appreciated.
Also we do maintain scale basis at condition record level, then whats the difference between the two?
Thanks

Hi ! Christino,
Q) functionality of Scale basis in a condition type?
A) The entry made here decides whether the condition value calculated is on the base of per quantity(say per pc or per no.) or per weight(say per Kg or per pound) or per volume(say per litre or per ml or per cm^3)
Q) What does scale formulae, check value ,scale type etc mean?
A) Scale Formulae - is a setting(ABAP/4 code you write) to make condition value to be calculated any other than those mentioned in the above answer.
->Check value field once set helps in deciding whether the scales you mentions have to be in a ascending or descending in scales rate
(ex.for Material A 1pc to 50pc price is $100
                         51pc to 200pc price is $99
                        201pc to 500pc price is $98, is an example of ascending scale rate. descending is opposite)
-> Scale type is setting the validity of the scale (say the scale rate starts from a particular point of quantity or value)
Q)Also we do maintain scale basis at condition record level, then whats the difference between the two?
A) at the condition record level it just a reflection of what scale basis you have set in customizing of Condition type.
Hope this helps. Do provide your feedback.
Regards,
PATHIK
Message was edited by:
        Pathik Pandya

Header group condition

Hi,
What is the impact of enabling a group condition for a header condition (fixed amt)?
When group condition is not enabled and when I enter for e.g. 10 INR in condition
header then it gets applied to all the PO line items. If 10 line items are there then 10 * 10 = 100 INR comes
in header
When group condition is enabled the value 10 INR gets apportioned to 10 line items.
What are the other impacts of enabling the group condition?
Regards,
Partha

Hi
Yes you are correct, if you you enable or flagged the condition as group then system will equally distribute the value among the line item of the PO equally
Rg

Condition types header condition and group condition

Hi All,
can any one tell me why the same header condition type is coming in billing document twice.The condition type has two deifferent parameters.
In first condition type:
condition class :DISCOUNT /SURCHARGE
calculation type :A percentage
condition control:A Adjust for qty variance
condition origin:A Automatic pricing
In second condition type:
condition class :DISCOUNT /SURCHARGE
calculation type :A percentage
condition control:C CHchanged manually
Condition origin:A HEADER CONDITION.
Even though only one conditon type is maintained.
Regards, Rajneesh

hi,
pl check at V/06 if you have maintained the conditon type as both header and group condition.
regards
sadhu kishore

Issue with Scale base routines in Pricing

Hi All,
This is regarding one issue I am facing in Invoice creation.
It happens randomly in some invoices (impact is in <5 % of invoices) that a discount condition value is incorrectly calculated when created through batch job.
This issue is not replicable in any of the lower environments.
When we cancel the invoice in produciton system and recreate it, the values are calculated correctly and we failed to replicate it even in production to find the root cause.
Here are the details:
We have a custom condition type which is a group condition (header as well as item) which is set in percentage where customer is supposed to get a discount (for eg. 1 % on the net price)
We have a Scale Base value routine which fetches the ‘scale base value’ from a custom table and assigns it to the item on the invoice (XKOMV-KSTBS).
All further calculation happens in standard SAP code where it checks the scales maintained in the condition record and applies the correct rate so the discount is applied accordingly.
Our pricing routine is working fine and is passing correct value to the scale base field.
The issue is in standard SAP code which applies the discount.
For all the impacted invoices, we have correct scale base values (fetched in our routine) but the corresponding discounts (KONV-KBETR and KONV-KWERT) are zero.
Only the last item in all the invoices shows a large negative value which is wrong .
Please guide me in finding the root cause.
Regards
Ritu

Hi,
These requirements should be met to fetch the condition record in the document.
1 = Different Payer
If this requirement is assigned to the condition type, the sold-to-party and payer should be different, so it will be picked up in the document.
2 = Item with Pricing
The item category of the item should be relevent for pricing.
3 = Foreign currency doc
The company code currency is derived from sales org in a sales document. But we can change the document currency in the sales document header also. And condition also can be maintianed in different currency. If this requirement is assigned, the company code currency and document currency should be different.
4 = Cost
If this requirement is set, the item should be relevent for cost determination (setting in item category)
5 = No Condit Exclusion
If this requirement is set, it will not consider the condition, if any condition exclusion is maintianed for it.
Prase

Group conditions in price conditions

In a pricing condition, group conditions may be checked off to include in a group.
How specifically do they belong to a group as per the requirements? What group are they referring to?
"Group condition
Indicates whether the system calculates the basis for the scale value from more than one item in the document.
Use
For a group condition to be effective, the items must belong to a group. You can freely define the group to meet the needs of your own organization. The items can, for example, all belong to the same material group.
Example
A sales order contains two items. Both items belong to the material group 01.
Material Quantity Material group
A 150 01
B 100 01
The group condition indicator is set in the definition of the condition type for material group discounts. The condition record for material group 01 includes the following pricing scale:
Scale quantity Discount
from 1 pc -1%
from 200 pc -2%
Neither item alone qualifies for the 2% discount. However, when the items are combined as part of a group condition, the combined quantity creates a basis of 250 pieces. This basis then exceeds the scale value of 200 pieces, which is necessary to qualify for the higher discount."

Hi Anabela
New groups can be defined in VOFM if required, in addition to those supplied by SAP.
A simple example of a group would be the pre-defined group 1 - All items.
This group can be used for instance to define a value based discount which you want to apply to all items in the order, based on the total order value. Group conditions are similar to header conditions, but have the advantage that they can be automated with condition records, which is not possible for header conditions.
So, you would set up a group condition, possibly with scales, to re-ward customers for larger orders. Because it is a group condition, the discount would be based on the total order value and then applied to all of the items in the order.
Another option would be to use group 3 - material pricing group. This would let you apply the group condition to all of the materials in a pricing group. For instance, if you wanted to set up scales for similar materials so that your customer gets the same price breaks across a number of order lines, regardless of the mix of materials bought.
HTH
James

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.

Group Condition at Header on Scale basis

Similar Messages

Maybe you are looking for