Price going negative due to group condition

Hi All,
We have some item lines in order which are grouped together for Pricing group condition. i.e., what ever the price value of the group condition type, it is being shared among all the group items.
When ever we add new item lines of the same group, price of all the item lines in order which are in same group are got affected. But, we have a problem when some item lines in group are already billed.
Since some item lines in group are already billed, the price value of these items could not be changed. So, to compensate this value, the last item in group is going negative. i.e., Price of last item line in group is shown as negative (eg. -699.00).
How to avoid this scenario? Why is the price going negative?
Thank you,
Regards,
Rajesh.

I didnt think the pricing engine in SAP would pick up items which are already billed.
Anyhow, you can try using group condition routine for that condition type to group only those items which are not billed so far. You can explore KONH, KONP tables to get the fields to query or check on for finding out if line item is billed. Also refer to already existing routines (1,2,3) in the system on how to use 'xvakey'. You may need an ABAPer to help you with it.

Similar Messages

  • 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

  • Meaning of group condition KGRPE

    Hi all,
    The problem is related to the condition type MWST, used to calculate VAT.
    We are facing the problem that sometimes (seems random) the VAT is wrongly calculated; even if the amount is correct (for Italy is 20%) the condition value is wrong (it is not the 20% of the Net total price). Checking in KONV the record corresponding to the wrong MWST, the value missing is insert in field KDIFF (negative value) instead of being completely shown in KWERT field.
    Executing a re-pricing of the position the amount of MWST is correctly populated, but going back on the full document pricing and executing a re-pricing the issue come out again.
    Our developers suggested to remove the Group condition flag on the MWST and in fact everything is working correctly without that flag. Could u kindly explain us how this flag is working exactly? Which characteristic of material is considering it?
    Thanks

    Hi,
    The purpose of group condiiton indicator is to calcualte the basis for the scale values more than one item in sales order.
    For example in sales order you have two line items and these two are belongs to same material group XY.
    If you have maintained the order as 1st item 100 order qty and second item has 200 qty.
    The scales you have maintained as: From 1pc-- 2% tax;From 300 pc--5% tax.
    If you set this indicator active in condition type then the system will consider the basis 300 qty and charge the tax as 5% as a whole in the sales order.
    Don't delete the indicator directly for standard MWST,if you want to delete copy the existing and rename it and use as per your requirement.
    I dont think there would any effect on FI posting if you remove.
    Whatever is the amount in the condition type in pricing would be posted to FI.
    It is mainly for populating the Condition value among the multiple items.
    Thanks,
    Venkat

  • 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

  • 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 - consequence

    What are the consequences of setting a conditon type to group condition? We are not using "RoundDiffComp" or "GrpCond.Routine" for the specific conditon type.
    Kind regards

    We are not using scales at the moment in our pricing. We need to have system to accept 0,- price for a given condition type and material. At the moment, system is not accepting this. Have searched OSS and in a note there was a reference to acheive this using group condition or creating a new VOFM with code and set this in the pricing procedure for the given condition type.
    So, my question is which one is the best to use.........maybe VOFM if we in the futere will use scales - or am i wrong?

  • Group Conditions

    Respected Gurus,
    This time I am back with different story, a part issue and a part way out!!
    In case of group conditions, the scaling price is always taken on the sum/cumulative value  of the two conditions, after the purchase order is saved.
    I figured this happens to save some extra bucks for the organization, as the next possible scale which contains more discounts is getting picked up in the process.
    Am I right?
    Jaideep

    >
    Edit Szabo wrote:
    > Hi Jaideep,
    >
    > if you have a quantity scale, then the system calculates the total quantity from the quantities of each PO item and looks for a price  according to your predefined scales.
    >
    > Please read note 854978 additionally.  
    >
    > Regards,
    > Edit
    And if we have a discount scale or a price scale, something similar happens?
    Jaideep

  • Re ;- Group condition (k020)

    Hi Gurus ...
           I would like to give a discount to the customer based on price group.,, when i try to enter discount in vk11 ,system come up with a message ---" CONDITION CANNOT BE CREATED IN DIVISION ABC "
    Can any one tell me the solution ......
    thank you in advance ...........

    hi ram..
    abc is only  my division ,and i am able to create va01/vl01n/vf01 with the combination of sales org/ dist chanel/ division (abc) .every thing is ok except group condition ....  
    when i try to enter discount in vk11 ,system come up with a message ---" CONDITION CANNOT BE CREATED IN DIVISION ABC "
    thank you for ur response.....

  • Re: Group Condition

    Hi Gurus,
    Can anyone tell me what is the use of Group Conditions in Condition type PBOOand FRA1
    Thanks in advance

    Hi,
    Group condition is a condition that relates to several several items of the document. In case of group condition, the values (prices, quantities etc.) of the relevant items are added and the total used as the base for the condition. This allows more favorable values to be taken as the basis for the scale computation.
    You can assign a routine for this group condition, in which you can maintain your own logic for grouping by simple ABAP coding.
    Umakanth R

  • RZ20: Effective price becomes negative(please correct)

    Hi All,
    The PO is error in process and RZ20 shows this message "Effective price becomes negative(please correct)"- Did any body get same error?, what could be the reason.
    Thnaks.

    Rahul,
    Please check the shopping cart value. It might me negative.
    If not, check the if any pricing conditions are applied for the PO (Ex. Discounts, Rebates, etc) that could bring the price down to negative.
    Regards,
    Jagadish

  • About the group condition in conditions(urgency)

    hi,everybody
        About the group conditions,SAP said that it can appeared in PO header and  caculated the price in some items.I tried it,it don't application in some items,but applied all items in PO document.so how can I only use it to some items that I want,but not all items!
        thanks all.
        urgency

    Dear Albert,
    Hi alrert,
    You can do this by,
    Solution1: in group conditons "GrpCond.routine", you can give the how system should distribute the Group condition value. here by Standard SAP, we have 1- overall document, 1- Across all condition 3 - material pricing grp, 30 - brazil routine.
    Here if your ABAP team is strong then ask them define the routine as per your requirement.
    Solution 2: Define that condition type header as well as item level in M/06, then manually alter them in PO.
    Solution 3: Create a seperate PO with excluding those items which you do not want to distribute.
    Thanks,
    Krishna Reddy

Maybe you are looking for