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

Similar Messages

CRM 5.0 IPC Group Condition

Friends,
We have a requirement to implement a group condition in CRM IPC 5.0. We have it implemented in R/3 and it works fine. We have replicated the code in the IPC and it is being hit. The code is quite simple. We copy to subtotal 1 a the net line value if the condition ZDC1 exists on the line. We then want the group basis calculation to only include the totalling of those lines that had ZDC1.
As I mentioned, this works fine in R/3. In CRM it is including the value of all the lines regardless of whether there is a ZDC1 condition or not. The Java code is getting hit and doing the transfer of the value to subtotal 1 at the right time.
Is there something else we should be setting up in the custom fromula for a group condition? I see in the IMG in CRM where I can add formula and implementation attributes. Is this something I need to do to get the group condition to work correctly?
Regards.
KB

We put code in to write the condition out to a log file to ensure that the correct values were being calculated. Once we did this, the condition started working. No clue why.

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.

Get Delivery date(EKET-EINDT) in MM Pricing routine(group condition)

Hi All,
I have created an MM pricing routine RV65A092 in VOFM. So when creating PO(ME21n), this routine will trigger..
Now the problem is I need EKET-EINDT for grouping condition. It was mentioned to call program SAPLMEPO and get EKET data.
Please help me how to get delivery date in that routine which is filled in Item level during PO creation
Thanks
Ram

Hi Ram,
For SD you have the SAP Note 531835 - Using field PSTYV in the condition access. For MM is simmilar, although you must use the enahncements. Instead use the userexits that note says, use the enhancement LMEKO001 (EXIT_SAPLMEKO_001) to populate fields ZZ in KOMK and LMEKO002 to populate KOMP.
I hope this helps you
Regards
Eduardo

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

Use of group conditions in subtotal KZWIW

Hi,
I have a specific trouble in the use of group condition in sales order and billing.
Condition Z001 is a group condition and should also update field kzwi2 as base information for condition Z002
Condition Z002 is not a group condition and is calculated based on informations stored in kzwi2.
When creating a document, the field kzwi2 is not updated directly (because Z001 is a group conditions) and the price should be redeterminated manually in order to allow the document to be considered as complete.
Is there any settings that can avoir the manual recalculation of the price?
Many thanks in advance,
Nathalie Winand

Hi Nathalie:
See Note 1022966 - FAQ for the 'Subto' column (KZWIW) in the pricing procedure
Perhaps it will help you
Regards
Eduardo

Regarding group condition

hi friends
1.wht is header condition and group condition?
2. what r the condution types for header and group conditions?
3. give me some examples for useful of header condition and group conditon?
plz reply me
thanks in advance

Dear Venkata Ramana
1) Header Conditions
Header conditions are entered manually in order processing. Automatic pricing does not take header conditions into account; you can not create condition records for them in the standard system. R/3 includes the following header conditions:
- Percent discount (HA00)
- Absolute discount (HB00)
- Freight (HD00)
2) Group Conditions
Please check this help link
[Group Conditions |http://help.sap.com/saphelp_47x200/helpdata/en/1c/8c8b518d8c11d199a30000e8a5bd28/frameset.htm]
thanks
G. Lakshmipathi

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

Group condition calulation error

Hi Gurus
I am facing a problem while applying a group condition as discount at item level. Tried to search in the existing threads but no luck.
We have marked a discount condition as group condition with quantity scales.
Now if there are multiple line items in the sales order for the same material with different quantities, there is a strange system behaviour.
The line item with highest quanity gets the discount calulated with a conditon round diff populated (KOMV-KDIFF) with negative value in the sales order. Now when billing document is created for this sales order the same line item gets the condition round diff (KOMV-KDIFF) populated with positive value. This in turn results a difference in net value of sales order and billing document.
Pls advise what could be the possible cause and solution.
Thanks in advance,
Gaurav

Hi Nikhilesh
Thanks for ur early reply.
Yes there is a 1:1 relationship between sales order and invoice. Example is detailed below:
Line item Material Qty     Amount (GBP)
10           STL       6531   2220.54
20           STL       6770   2301.80
Now in the sales order, when the discount condition YGID is calulated on the above items @ 4.5%, discount value for line # 10 comes to 99.92 and discount value for line # 20 comes to 103.59 with -0.01 value in KOMV-KDIFF field.
Thereafter when billing document is created for this sales order, value in line # 10 for the discount remains same i.e. 99.92 but for line # 20 the discount value comes as 103.58 with +0.01 value in KOMV-KDIFF field.
This results in a difference in net values of sales order and billing document.
Regards
Gaurav

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

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

Group Condition types & routines - pricing

Do we have to code the group condtion routines all the time? If I just have the group condition box checked without any routine coded, I am seeing that SAP is grouping all the items in the sales order using the same access. Please let me know. Thanks.

Hi,
This depends on your requirement. If you have defined the condition at the material pricing group level, then no need. The routine is used only if you want the condition to be read differently for each item (with the scale base value being total of all the items).
You can find some help in the below link:
http://help.sap.com/saphelp_erp2005/helpdata/en/de/7a8534c960a134e10000009b38f83b/frameset.htm
There are some helpful SAP Notes if you need further clarifications:
39034     Group condition routine
854978     Function of cumulated scale base values (in SD)
109708     Scale processing for group conditions
Hope this helps.
Regards
Nikhilesh

Item level Group Condition

Hello,
I have created one Item level condition type ZZXX and set "group condition" check box and maintained condition records with fixed amount.
In the sales order, i have given 3 line items (different materials). system determined the condition type ZZXX and distributed amount to 3 materials with different values.
Could you please let me know how a Item level group condition distributes amount among 3 line items?
Thanks in advance.
B Regards,
Bhaskar.K

Must be the Material Group is same in all the three different material in 3 line Items.
Best Regards,
Ankur

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

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

Group condition.

Similar Messages

Maybe you are looking for