Is it possible to rank with group condition?

Is it possible to rank with group condition? for example I have following dataset.
RANK() OVER (partition BY PC.POLICY_NUMBER, PC.TRANSACTION_TYPE, COV_CHG_EFF_DATE order by PC.POLICY_NUMBER, COV_CHG_EFF_DATE, PC.TIMESTAMP_ENTERED) AS RNK,
POLICY_NUMBER    TRANSACTION_TYPE  COV_CHG_EFF_DATE  TIMESTAMP_ENTERED                        Rank
10531075PQ                           01           01/FEB/2009              15/SEP/2009 01:16:09.356663 AM       1
10531075PQ                           01           01/FEB/2009              15/SEP/2009 01:16:09.387784 AM       2
10531075PQ                           02           15/OCT/2009             16/OCT/2009 04:40:24.564928 PM       1
10531075PQ                           02           15/OCT/2009             16/OCT/2009 04:40:24.678118 PM       2
10531075PQ                           10           15/OCT/2009             16/OCT/2009 04:45:20.290117 PM       1
10531075PQ                           10           15/OCT/2009             16/OCT/2009 04:40:29.088737 PM       2
10531075PQ                           09           15/OCT/2009             16/OCT/2009 04:40:29.088737 PM       1 (expected 3)
10531075PQ                           06           17/OCT/2009             17/OCT/2009 04:45:20.290117 PM       1
10531075PQ                           07           17/OCT/2009             17/OCT/2009 04:40:29.088737 PM       1 (expected 2) I want to group rank based by transaction IDs. For ex, '09' and '10' as one set and '06' an '07' as another set. Instead of rank from start, I want rank continue for any occurance of '09' or '10'. In the above example, for the following row, I am expecting rank 3 as there are 2 transaction '10' already exist for same COV_CHG_EFF_DATE.
10531075PQ 09 15/OCT/2009 16/OCT/2009 04:40:29.088737 PM 1 (expected 3)
I wonder if it possible with Rank or another other analytical function. I am not looking for exact working code, but will appreciate if someone give me idea/tips. Sample table, and test data if anyone want experiment
drop table PC_COVKEY_PD;
create table PC_COVKEY_PD (
POLICY_NUMBER varchar(30),
TERM_IDENT varchar(3),
COVERAGE_NUMBER varchar(3),
TRANSACTION_TYPE varchar(3),
COV_CHG_EFF_DATE date,
TIMESTAMP_ENTERED timestamp
delete from PC_COVKEY_PD;
commit;
insert into PC_COVKEY_PD values ('10531075PQ', '021', '002', '01', to_date('01/FEB/2009','DD/MM/YYYY'), cast('15/SEP/2009 01:16:09.356663 AM' as timestamp));
insert into PC_COVKEY_PD values ('10531075PQ', '021', '001', '01', to_date('01/FEB/2009','DD/MM/YYYY'), cast('15/SEP/2009 01:16:09.387784 AM' as timestamp));
insert into PC_COVKEY_PD values ('10531075PQ', '021', '004', '02', to_date('15/OCT/2009','DD/MM/YYYY'), cast('16/OCT/2009 04:40:24.164928 PM' as timestamp));
insert into PC_COVKEY_PD values ('10531075PQ', '021', '004', '02', to_date('15/OCT/2009','DD/MM/YYYY'), cast('16/OCT/2009 04:40:24.264928 PM' as timestamp));
insert into PC_COVKEY_PD values ( '10531075PQ', '021', '005', '10', to_date('15/OCT/2009','DD/MM/YYYY'), cast('16/OCT/2009 04:40:24.364928 PM' as timestamp));
insert into PC_COVKEY_PD values ('10531075PQ', '021', '002', '10', to_date('15/OCT/2009','DD/MM/YYYY'), cast('16/OCT/2009 04:40:24.464928 PM' as timestamp));
insert into PC_COVKEY_PD values ( '10531075PQ', '021', '004', '09', to_date('15/OCT/2009','DD/MM/YYYY'), cast('16/OCT/2009 04:40:24.564928 PM' as timestamp));
insert into PC_COVKEY_PD values ('10531075PQ', '021', '004', '06', to_date('22/NOV/2011','DD/MM/YYYY'), cast('17/OCT/2009 04:40:24.564928 PM' as timestamp));
insert into PC_COVKEY_PD values ('10531075PQ', '021', '004', '07', to_date('22/NOV/2011','DD/MM/YYYY'), cast('17/OCT/2009 04:40:24.664928 PM' as timestamp));
commit;
SELECT POLICY_NUMBER,
       TERM_IDENT,
       COVERAGE_NUMBER,
       TRANSACTION_TYPE,
       COV_CHG_EFF_DATE,
       TIMESTAMP_ENTERED,
        RANK() OVER (partition BY PC.POLICY_NUMBER, PC.TERM_IDENT, PC.TRANSACTION_TYPE, PC.COV_CHG_EFF_DATE
                order by PC.POLICY_NUMBER, PC.TERM_IDENT, PC.COV_CHG_EFF_DATE, PC.TIMESTAMP_ENTERED) AS RNK
FROM PC_COVKEY_PD PC
ORDER BY PC.POLICY_NUMBER, PC.TERM_IDENT, PC.COV_CHG_EFF_DATE, PC.TIMESTAMP_ENTERED ;Edited by: 966820 on 30-Oct-2012 19:26

Hi,
966820 wrote:
I want to group rank based by transaction IDs. For ex, '09' and '10' as one set and '06' an '07' as another set. So, whenever you see '09', you want to treat it as '10', and whenever you see '06', you want to act as if it were '07'.
You can use CASE to map '09' to '10', and '06' to '07'. like this:
,       RANK () OVER ( PARTITION BY  policy_number
                              ,             term_ident
                ,            CASE  transaction_type
                                WHEN  '06'  THEN  '07'
                                WHEN  '09'  THEN  '10'
                                        ELSE  transaction_type
                           END
                ,            cov_chg_eff_date
                ORDER BY      timestamp_entered
                 )     AS rnkWhen you "PARTITION BY x", there's no point in saying "ORDER BY x" in the same analytic clause.
Thanks for posting the CREATE TABLE and INSERT statements.
Thanks, too, for posting your query, though, as mentioned already, it's unreadable. When posting any formatted text (and code should always be formatted), type these 6 characters:
\(small letters only, inside curly brackets) before and after each section of formatted text, to preserve spacing.
See the forum FAQ {message:id=9360002}                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       

Similar Messages

  • 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

  • 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

  • MWST-group condition rounding difference between invoice and credit memo

    Hi Experts,
    I have an issue with MWST rounding issue.
    Before jumping into the actual problem these are the prerequisites
    SAP Version: ECC6.0
    Condition type: MWST, with group condition tick enabled!
    US Scenario (No Implication of CIN)
    Scenario: - From Billing document  to Credit memo invoice.
    When a invoice is referenced to the credit memo, there is a difference in the rounding value.
    E.g.: Invoice tax value: 387.34 when completely referenced to credit memo become;s  387.31.
    Please throw some light on it!

    Hi,
    Check Note 315792 - Group conditions of the same amount on item and related notes.
    Perhaps Note 80183 - Rounding will help you too.
    Regards,
    Eduardo

  • Is it possible to access a group of (sequentia​l) registers with a single URL?

    I'm testing out datasockets to an A-B RSLinx OPC server. At the moment, it appears as though each register in the PLC has to be accessed with an individual URL. Is it possible to access a group of (sequential) registers with a single URL? I suspect i may have to cluster a bunch of individuals together

    goog,
    For each data member, you will need a unique URL. There is not a way to bundle them into one URL.
    Randy Hoskin
    Applications Engineer
    National Instruments
    http://www.ni.com/ask

  • Group condition with varying keys

    Hi every one,
    How to declear group condition with varying keys.
    gajanan

    Hi Rudrag,
    What Karan has mentioned is absolutely correct.
    To simpify it,
    Suppose you have two materials M1 and M2 for which you want to give customer/material specific discount.
    Create one material pricing group (e.g, 01) in customising, assign the Material Pricing group 01 to both the material in their respective material master in Sales org 2 view.
    In V/06, open the condition type K005, activate the "Group condition" check box and assign "Routine 3" in the "Gorup condition routine" check box by selecting the value from the drop down.
    Now create condition record for Condition type K005 in t.code VK11 for the two materials for one specific customer.
    For example, for cudtomer C1 and Material M1, discount is Rs.10 per Piece(PC).
    Go to scale and specify in the scale that if 10 Pieces then discount is Rs.15 per piece.
    Similarly, for Custome C2 and Material M2 maintain a condition record for discount is Rs.20 per piece.
    Go to scale and maintain and specify that, if 10 pieces order then discount will be Rs.25 per piece.
    Now create a Sales order for the Customer C1 with the two material M1 and M2 with quantity 4 pieces and 6 pieces respectively.
    System will add up the quantities of both the material as 4+6=10 pieces.
    Even though, there respective order quantities are 4 pieces and 6 pieces , but still both the item will avail the discount for 10pieces level beacuse of the group condition settings.
    But, the rate of the discount will taken from there individual condition record.
    That means, M1 will get discount of Rs.15 per piece. So for  4 pieces discount will be Rs.60.
    Similarly, M2 will get discount of Rs.25 per piece. So for 6 pieces  discount will be Rs.150.
    If there is no setting for group condition then, M1 would have got discount of Rs.40 and M2 would have got discount of Rs.90.
    I hope this is clear.
    Regards
    Pradyumna

  • Is it possible to use dynamic 'with key' conditions of 'READ itab' ??

    Hi~
    I want to try to set  'with key'  conditions dynamically..
    READ TABLE itab WITH KEY <...>.
    In this <...> phrase, the condition keys could be 2 or 3( don't know at yet this point)
    so i want to make it dynamic with importing data.
    Is it possible?
    Please help me!
    thank you in advance~

    Hey,
    You could write 2 READ statements instead of trying to write a dynamic READ statement.
    IF CONDITION FOR 2 KEYS IS MET.
    READ TABLE WITH KEY1 = (value1) KEY2 = (value2).
    ELSE.
    READ TABLE WITH KEY1 = (value1) KEY2 = (value2) KEY3 = (value3).
    ENDIF.
    ~Kiran

  • Pricing issue-With reference to group condition

    Hi Friends,
    Below are the details of the issue i have,
    Letu2019s say we have 3 service line items in a service order
    Line item 1-Do not charge the customer (controlled through accounting indicator)
    Line item 2-Charge customer (controlled through accounting indicator)
    Line item 3-Charge customer (controlled through accounting indicator)
    Now we have maintained group condition in pricing. So if line item 1 has 20 min, 2-30 min and 3-40 min of service the pricing will be as under,
    System adds 203040=90 min in total and than search for the scales accordingly (due to the group condition check) as the condition type is also scale based. But we donu2019t want to charge for the line item 1 due to some business rule. Thus the system should not consider line item 1(20 min) and add only 30+40=70 and look for the scales accordingly. Once the right scale has been found, it should divide the same in line item 2 and 3 equally. eg- if the scale returned was 60, it should be divided as 30 each between line item 2 and 3 and not as 20 between all 3 line items. We tried to make the scale of line item 1 to zero on certain business rule by creating a new routine. The problem now is, after getting the right scale the system divides it between the 3 line items instead of 2. Let us know if you have any solution to resolve this issue.
    Highly appreciate your help
    Sameer

    Hi Sameer,
    not sure which type of routine you did try to use. You should check whether a group key routine could help you to control the items, which should be grouped. Another option could be to prevent automatic determination of the group condition on the first item by a specific requirement formula (e.g. this could check the item categroy or the account indicator).
    Best Regards,
    Michael

  • If..then..else statement in SQL with 'generalized' conditions in the if sta

    it is possible to write something approaching an if..then..else statement in SQL with 'generalized' conditions in the if statement.
    Attached is the query for the payment register, in which I've written a series of decode statements, one for each possible value of the payment code. The query works OK - however, its specific and as the number of paycodes expand (and they do), the report won't pick up the new paycode until the code is changed. More importantly, the report won't be correct until someone 'discovers' that a paycode is missing, which might take months.
    If I were writing the equivalent of this series of decode statements in Focus, it would be something like this:
    DEFINE.......
    PAYMED/D12.2 = IF PAYMENT_CD LE 18
                   THEN PAYMENT_AMT
                   ELSE 0 ;
    PAYIND/D12.2 = IF PAYMENT_CD GE 19 AND PAYMENT_CD LE 49
                   THEN PAYMENT_AMT
                   ELSE 0 ;
    PAYEXP/D12.2 = IF PAYMENT_CD GE 70
                   THEN PAYMENT_AMT
                   ELSE 0 ;
    PAYREC/D12.2 = IF PAYMENT_CD GE 50 AND PAYMENT_CD LE 69
                   THEN PAYMENT_AMT
                   ELSE 0;
    END
    IN SQL/PLUS:
    SELECT ACCOUNT_NAME,
    LOCATION_1,
    CLMNT_LAST_NAME,
    CLAIM_NBR,
    DATE_OF_INJURY,
    DATE_CHECK_REGISTER,
    PAYEE_NAME_1,
    PAYMENT_CD,
    SERV_OFC,
    CPO_CHECK_NBR,
    PAYMENT_FORM,
    DECODE(PAYMENT_CD, 20, PAYMENT_AMT, 21, PAYMENT_AMT,
    22, PAYMENT_AMT, 23, PAYMENT_AMT, 25, PAYMENT_AMT,
    26, PAYMENT_AMT, 27, PAYMENT_AMT, 28, PAYMENT_AMT,
    29, PAYMENT_AMT, 30, PAYMENT_AMT, 31, PAYMENT_AMT,
    32, PAYMENT_AMT, 33, PAYMENT_AMT, 34, PAYMENT_AMT,
    35, PAYMENT_AMT, 36, PAYMENT_AMT, 37, PAYMENT_AMT,
    39, PAYMENT_AMT, 40, PAYMENT_AMT, 41, PAYMENT_AMT,
    42, PAYMENT_AMT, 43, PAYMENT_AMT, 44, PAYMENT_AMT,
    45, PAYMENT_AMT, 46, PAYMENT_AMT, 47, PAYMENT_AMT,
    48, PAYMENT_AMT, 49, PAYMENT_AMT, NULL) INDEMNITY,
    DECODE(PAYMENT_CD, 0, PAYMENT_AMT, 1, PAYMENT_AMT,
    2, PAYMENT_AMT, 3, PAYMENT_AMT, 4, PAYMENT_AMT,
    5, PAYMENT_AMT, 6, PAYMENT_AMT, 7, PAYMENT_AMT,
    8, PAYMENT_AMT, 9, PAYMENT_AMT, 10, PAYMENT_AMT,
    11, PAYMENT_AMT, 12, PAYMENT_AMT, 13, PAYMENT_AMT,
    14, PAYMENT_AMT, 15, PAYMENT_AMT, 18, PAYMENT_AMT,
    17, PAYMENT_AMT, NULL) MEDICAL,
    DECODE(PAYMENT_CD, 70, PAYMENT_AMT, 71, PAYMENT_AMT,
    72, PAYMENT_AMT, 73, PAYMENT_AMT, 74, PAYMENT_AMT,
    75, PAYMENT_AMT, 76, PAYMENT_AMT, 77, PAYMENT_AMT,
    78, PAYMENT_AMT, 79, PAYMENT_AMT, 80, PAYMENT_AMT,
    81, PAYMENT_AMT, 82, PAYMENT_AMT, 83, PAYMENT_AMT,
    84, PAYMENT_AMT, 85, PAYMENT_AMT, 86, PAYMENT_AMT,
    87, PAYMENT_AMT, 88, PAYMENT_AMT, 89, PAYMENT_AMT,
    90, PAYMENT_AMT, NULL) EXPENSES,
    DECODE(PAYMENT_CD, 50, PAYMENT_AMT, 51, PAYMENT_AMT,
    52, PAYMENT_AMT, 53, PAYMENT_AMT, 54, PAYMENT_AMT,
    55, PAYMENT_AMT, 56, PAYMENT_AMT, 57, PAYMENT_AMT,
    58, PAYMENT_AMT, NULL) RECOVERIES,
    DECODE(PAYMENT_FORM, 'N', PAYMENT_AMT, NULL) NONCASH,
    DATE_FROM_SERVICE,
    DATE_THRU_SERVICE
    FROM &INPUT_TABLES
    WHERE &SECURITYCOND
    DATE_OF_PAYMENT BETWEEN :START_DATE AND :END_DATE
    ORDER BY LOCATION_1, CPO_CHECK_NBR
    As you can see, this is both much easier to write and covers the possibility of expansion of paycodes (expansions always fit in these defined ranges).
    My question is, then, is it possible to write something like this in SQL and, if so, could you give me some sample code? (I'm one of those people who learn best from looking at the code as opposed to a set of instructions)

    Here is one way you could do it.
    Create a table that has columns like:
    Payment_code varchar2(2),
    Effective_Date Date,
    Payment_type varchar2(20),
    Expiration_Date Date)
    Payment type for example could be
    I- indemnity
    M- medical
    R- recovery
    E- expenses
    Let the table name for example be PAYMENT_CODE.
    The select query would look like
    SELECT ACCOUNT_NAME,
    LOCATION_1,
    CLMNT_LAST_NAME,
    CLAIM_NBR,
    DATE_OF_INJURY,
    DATE_CHECK_REGISTER,
    PAYEE_NAME_1,
    PAYMENT_CD,
    SERV_OFC,
    CPO_CHECK_NBR,
    PAYMENT_FORM,
    DECODE(p.payment_type,'E',PAYMENT_AMOUNT,0) expenses,
    DECODE(p.payment_type,'I',PAYMENT_AMOUNT,0) indemnity,
    DECODE(p.payment_type,'M',PAYMENT_AMOUNT,0) Medical,
    DECODE(p.payment_type,'R',PAYMENT_AMOUNT,0) recoveries,
    DECODE(PAYMENT_FORM, 'N', PAYMENT_AMT, NULL) NONCASH
    FROM &INPUT_TABLES,
    PAYMENT_CODE P
    WHERE P.PAYMENT_CODE = SOMEINPUT_TABLE.PAYMENT_CODE
    and other conditions
    The idea is to group all the payment codes into a few groups to reduce the clutter. If there is ever a change to the payment code, you could modify the table and it will be reflected in your select query.

  • Is it possible to limit a group of customers to create a kind of order

    Hi,
      I went to divide our customer into tow groups, one group can create sales order with a kind of order type,and another group can create sales order with other type? in other words,I don't want a group of customers create a special type of sales order.Is it possible?
    Thanks.
    Regards
    lance

    You can block a sales order for a sales area. Now you are grouping your customers in two groups regardless of sales areas i believe. If not, you can do it by blocking the order type for that sales area.
    But if you are grouping your cust regardless of sales area, then i think you will have to look for a user exit at create order(va01) and check for the relevant  group(from the cust master)when u enter the customer. if it satisfies the condition then allow to proceed otherwise prohibit from further processing giving the relevant error msg saying" Customers with group say X cannot be used for order type say OR"
    Thanks
    Vishal

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

  • Issue with Freight condition with scales

    HI Experts
    We have requirement like below.
    When customer send an order
    o     if the order contains materials for a minimum quantity the system should not apply freight condition
    o     if the order contains materials for less than minimum quantity the system should apply freight condition
    For example: sales condition freight has scale
         scale qty     unit     amount     unit
    From     0     PC     18,3     u20AC
         4     PC     0     u20AC
    e.g.1  customer send order that contain 9 PC, so system NOT apply freight condition
    material     quantity
    x1     1
    x2     1
    x3     2
    x4     5
    e.g.2  customer send order that contain 2 PC, so system apply freight condition
    material     quantity
    x1     1
    x2     1
    For this we have maintained Group condition and maintained scales up to 3 Order quantity 18 EUR . If order quantity is greater than 4 condition should not apply.
    But Now our issue is when ever Material determination is occurring in Order our condition is going to fail. For example  order quantity is 2 with TAPA item(parent item) and so substitute Item also 2 quantity (Tan item). In this case system is reading order quantity as 4 and our condition is 0. But actual quantity is 2 condition should apply in Order.
    Could you please suggest us where we can control this kind of scenario.
    Regards, Lakshmikanth

    Done through user exit

  • Error message: No pymt possible because items with a debit

    Folks,
    My vendor line items are
    Rs 1000- credit memo dated 05/25/2006 pay terms net 30
    Rs 50-   credit memo dated 06/10/2006 pay terms net 30
    Rs 300-  credit memo dated 08/10/2006 pay terms net 30
    Rs 5000  invocie     dated 09/01/2006 pay terms net 30
    getting error in F110 when run on 10/07/2006 :No pymt possible because items with a debit

    Hi
    Please check the grouping key on the vendor master record.
    It could be just that the line items are grouped according to due date and are not able to offset each other.
    The grouping key is on  the automatic payment transactions block.
    Hope this helps.

Maybe you are looking for

  • Itunes 11, can't find shared library

    Have to say.... so far I'm not very happy with itunes 11. A lot of what used to be intuitive is now cryptic. I guess along that line... I have a sizable library of music & vids on my main system that used to be easily accessible from my macbook's itu

  • PreparedStatement in two servlets

    Hello, I've got a doubt concerning PreparedStatement with JDBC. If I have the same statement in two different servlets, is my SQL compiled just once in the DBMS ? So, if I create a new Instance of PreparedStatement that was previously created in anot

  • Inspections for Iron incoming and out going materials.

    Hello Experts, I am implementing SAP QM fro hpp iron industry, My requirement is user wants the inspections with respect to quantity basis of finished goods. They don't want all specifications to be recorded in the system. They want to accept the ins

  • Smart album date range broken?

    With earlier versions of iPhoto I've set up smart albums for date ranges, and then exported everything in the smart albums for archiving.  When I upgraded to Mavericks and iPhoto 9.5.1, several (but not all) of these appeared as empty.  I didn't worr

  • Manual for Symphony app

    I have just purchased and installed the music-notation app 'Symphony 2.6.4' on my iPhone 3G (iOS 4.2.1). The users' manual referred to in the AppStore and elsewhere seems no longer to be available from <http://www.xeapps.com/symphony-manual.pdf>, the