Modify existing rebate condition and exclusion

Hi
We are rebate agreements for customers. Currently I want to modify rebate condition in one of rebate agreement.
Scenario: let us June 10th 2010 onwards, the rebate % is 3% for Profit center 'xxxx' & customer 'yyyy' instead of 1%. And 3% needs to accrued on billing docs going forward. How to set up this.
I tried to modify existing rebate condition using VBo2 as follows: went into rebate agreement using VBo2, changed rebate % for condition record with effective from 06/11/2010 and Saved.  problem when I ran VBOF program, system posted reversal accrual for old rebate condition 1%. Old condition record validity from 01/01/2009 Valid to 12/31/2011.
I have one more question. We want to set up rebate condition for all materials exclude some of them. we have thousands of materials for which we need to calculate rebates. but we want to exclude some materials in the rebate agreement. How to set up such exclus
any ideas really appreciated
thnx

The key of your condition table (the one supporting your condition record in the agreement) is evidently Profit Center / Customer.  So for any combination of profit center and customer, you can maintain a rate and validity period. 
You are attempting to maintain two separate records having the same key.  As you have experienced, the system does not allow it.
The simple solution is to expire that rebate agreement and start a new one with the updated validity period and conditions.
As for excluding certain materials, you need a more detailed key in your condition table.  Something else from the material master seems appropriateu2014Commission Group for example.  Maintain commissionable materials in group 01 and non-commissionable ones in group 02.  Then a key combination of Commission Group / Profit Center / Customer  would work well for you.
Regards,
Ken

Similar Messages

  • Can the Extension Builder be Used to Modify Existing InDesign Menus and Panels

    Hi,
    I am using the CS5 SDK to create new panels and menus for InDesign.
    I would like to know if there is a way to modify InDesign's existing native panels and menues. For example, I might want to display additional information about assets in a Library panel.
    TIA,
    mlavie

    Sorry,  no direct way. You could theoretically build your own panel and then supercede the menu for ID's panel. Nobody's tried it that I know of; and, frankly, I wouldn't recommend it as it could easily break something in ID.
    Bob

  • Modify ME55 selection conditions and ALV output

    Hi guys,
    I need to modify ME55 transaction, i mean to modify the data selection and ALV report to add new columns, is it possible with some enhancement or should i copy the program RM06BF00?
    The problem that i faced when copying ME55 transaction is that copy ALV output is not the same in the standard one, is it possible to copy the class LCL_FACTORY?
    Any link or idea would be helpful, thank u in advance.
    Sofiane.

    hi,
    You have to copy the standard program SAPMV75A to ZSAPMV75A, change them accordingly.

  • WMST for rebate conditions

    Hi All,
    I need some help on how I can added condition MWST to my rebate settlement pricing procedure. I have 3 rebate conditions and the business requirement is the tax needs to be calculated on the rebate conditions once the settlement has been done.
    Thanks,
    Clive

    Hi,
    For 1st Point :
    You can check in table Konh (condition record header details) you can give in this table the condition type used by rebate agreements and in the variable key you can give * your sales org name* can get here the required details.
    For 2nd Point ;
    You can check in table vbrk - knumv ( doc condition) get all the details form this table and pass to konh to identify the rebate condition types  used.
    Collect the related records numbers go back to table vbrk pass those condition records in vbrk and can find the invoice which used rebate conditions.
    Regards
    vK

  • Rebate condition type accrued as statictical condition

    Hi Gurus
    I want to accrue the rebate from one customer and pay to the different customer as decided by sales guys. Please help how to handle in rebate management. Thanks in advance.

    Hi,
    You can asign account key to rebate condition and also speciefy G/L account.
    Because when you create sales order that time system recognise where to post values.
    This will not post any entry but it realise where to post.
    Kapil

  • Manual rebate condition exclusion not refreshed after redetermination of it

    Hi Experts.
    I am working with CRM 4.0.
    Lately, we realized there is an error occurring in the price deternination:
    The condition exclusion for manual rebate condition is not refreshed after redetermination of the product. There is missing a price validation before saving the document with the new product.
    Step-to-step description of the error:
    1)     I am creating an order in trx. CIC0 or CRMD_BUS2000115 and determine the product (sector A).
    2)     Now I assign a manual rebate (condition Z...) of 20 % on item level.
    3)     On header level I replace the product to one of another sector (B).
    4)     I check the pricing conditions of the new product on item level. The same rebate of 20 % is maintained.
    This is an error, because the condition exclusion for products of sector B allows rebates only until 5 %.
    Can anybody help me, please.
    Best regards,
    Cristina

    This is not standard due to information of SAP OSS.

  • Take an existing text file and modify values

    I’m looking to take an existing text file and modify certain values inside of it. Then save it to a new file, with all the same formatting as the original. The file format is not uniform and can change.
    Basically the file is:
    Random numbers and letters of unknown length for an unknown number of lines.
    Label="Test_#"
    Description
    String
    X=123
    Y=456
    Z=-789
    20 lines of strings with numbers in them
    Label="Test_#2"
    Description
    String
    X=-1232
    Y=4562
    Z=7892
    Then it repeats a set number of times.
    I want to modify the X Y and Z = values for each Test_#.
    I’ve managed to import the important values into a numeric array and I have a different array with values that will replace the existing ones. I’m having troubles replacing the existing ones. There are no zeros before or after the existing numbers so they are all different lengths.
    If anyone has any sample code that does anything similar please post it. I’m sure someone has done something like this in the past. 
    Solved!
    Go to Solution.

    I just thought I would throw this out there.  Can you make the .txt file tokenized?  This would make searching for specific parameters much easier.
    Reese, (former CLAD, future CLD)
    Some people call me the Space Cowboy!
    Some call me the gangster of love.
    Some people call me MoReese!
    ...I'm right here baby, right here, right here, right here at home

  • Create job and modify existing jobs in OM

    Dear all
    how to create job and modify existing jobs in OM?
    thanks
    Jeeva

    […] (as I understand it), pdf's are not a viable solution as these print jobs feature a very high resolution (1200 dpi).
    I would expect the output from Finale to be mostly in the form of font characters—so a PDF you create by printing-to-file should be resolution-independent. If you have +Adobe Acrobat+, that can be verified quite easily in Document Properties, which will list all embedded fonts, but you should also be able to tell by zooming ’way in with Preview: if the score still looks sharp when greatly enlarged (and the file takes up less than a few hundred kilobytes per page), you can be sure it will print well on any suitable device. (If you print-to-file as PostScript instead of PDF, the resulting document can be downloaded directly into any PS printer, but it will likely be several times larger than a PDF version.)

  • Conditions mutually exclusive in the Pricing Procedure

    Hello,
    I want to define two conditions in the pricing procedure, but I don't want them to be determined at the same time in the billing document. One of them has an access sequence and it isn't always determined, and the other one doesn't have access sequence and is always determined, but I want that the last to be active only when the first one isn't. Is there any way to do this without developing a condition to put it in the requirement field?
    Thank you,
    Silvia

    Try to use the Condition Exclusion For Groups Of Conditions in the pricing customizing.
    Create 2 groups, one assigned to the first condition and the other to the second, then assign the exclusion procedure to the you pricing schema.
    The exclusion procedure should be D, that means:
    Exclusive procedure: If a condition type from the first group exists
    in the document, all conditions types that are found in the second
    group are set to inactive.
    Pls. reward points if helpful
    Regards
    Roberto

  • Problem in modifying existing records in dbtab

    Hi Experts,
    I am doing a report where I have created two dbtab's , one for data getting saved and
    other for fetching data and modifying exsiting records..
    For eg - let ZABC be the table where I need to insert or update records and ZXYZ is the table where
    I need to fetch and modify existing records.
    Now my probelm is :
    In case of inserting new records (multiple records ) into my dbtab ( ZABC ) its working ,
    but modifying existing records in another dbtab (ZXYZ ) its not wroking !! plz advice !!
    If my select querry for modifying exsiting records is:
    SELECT *  FROM ZXYZ  INTO TABLE ITAB WHERE MATNR EQ S_MATNR.
    *****then its inserting a newline along with the existing records.
    but when my querry is,
    SELECT single *  FROM ZXYZ  WHERE MATNR EQ S_MATNR.
    then its modifying the existing records, but only the first record.
    Loop at itab.
    if sy-tabix  = 1.
    zabc-matnr = matnr.
    zabc-idnrk  = idnrk.
    zabc-budat = s_budat.
    zabc-menge = menge1.
    ZXYZ-menge = ZABC-Menge + MENGE1.
    ZXYZ-BALC  = ZXYZ-Menge   -   MENGE1.
    ELSEIF sy-tabix  = 2.
    zabc-matnr = matnr.
    zabc-idnrk  = idnrk.
    zabc-budat = s_budat.
    zabc-menge = menge2.
    ZXYZ-menge = ZABC-Menge + MENGE2.
    ZXYZ-BALC  = ZXYZ-Menge  -  MENGE2.
    ELSEIF sy-tabix  = 3.
    zabc-matnr = matnr.
    zabc-idnrk  = idnrk.
    zabc-budat = s_budat.
    zabc-menge = menge3.
    ZXYZ-menge = ZABC-Menge + MENGE3.
    ZXYZ-BALC  = ZXYZ-Menge   -  MENGE3.
    ENDIF.
    INSERT ZABC.
    IF SY-SUBRC EQ 0.
    MODIFY ZXYZ.
            IF SY-SUBRC = 0.
              MESSAGE : I002 WITH 'RECORD CREATED'.
                ENDIF.
    ENDIF.
    Please advice
    Karthik
    Edited by: Karthik R on Aug 24, 2009 9:42 PM

    Hi,
    This is because in the second case you are not selecting records into an internal table.
    As a result only the first record which satisfies the where condition is fetched.
    Check if the program goes into the loop when you write second select query.
    KR Jaideep,

  • Freight Conditions and Commission Rate - New Requirement

    Hi All,
    There is new requirement about Freight condition and Commission Rate. Please see below for details:
    I got the requirement lets say:
    They want 3 different types of freight like 1st Freight - based on unit/qty, 2nd freight - Fixed Amount, and 3rd Freight - based on kilometer, out of this 3 any one will applicable in sale order at a time depends how they want to charge. they have existing pricing procedure.
    I hope the above freight related part clear to you all.
    Now the commision part:
    Here they are giving commisions whatever rate decided to the commission agent, here also for commission agent they want 3 different types 1st will be Fixed Amount, 2nd will be based on percentage and 3rd will be normal way.
    Please help and advice how to achieve this type of requirement.

    hi
    Condition Exclusion 
    The system can exclude conditions so that they are not taken into account during pricing in sales documents.
    Material 4711 costs 150 USD. Some customers receive a discount of 10 USD per 100 pieces.
    However, a specific customer can buy the material for 100 USD. Since this is a particularly good price, the customer should not also have a discount of 10 USD per 100 pieces. Therefore, this discount is to be excluded from pricing.
    To do this, you must follow two steps:
    You must set a condition exclusion indicator for the price. You can do this in two ways: If you want to set the condition exclusion indicator a follows then you specify it:
    - for all condition records of a condition type (e.g. with condition type PR00) when defining a condition type in SD Customizing
    - for an individual condition record (e.g. only for material 4711) in the detail screen of a condition record (in the Condition exclusion field)
    You must set a condition for the discount in the pricing procedure in Customizing for sales. If this condition is set, the discount is not valid if the condition exclusion indicator is set. Condition 2 is available in the standard R/3 System.
    The condition exclusion indicator is not valid for condition supplements.
    This means that if a condition record contains condition supplements they will be taken into account during pricing.
    Condition Exclusion Group u2013 
    In any normal situation there could be more than one condition type in a pricing procedure offering a discount to a customer. Should the discounts be automatically determined, there is the risk that the customer will receive all the relevant discounts and thus purchase the product for a lower price than he should.
    By using u2018condition exclusion groupsu2019 you can ensure that the customer does not receive all the discounts, but instead only receives the best of the available discount condition types.
    Menu path u2013 IMG - Sales & Distribution - Basic functions u2013 pricing u2013 condition exclusion u2013 condition exclusion for groups of conditions (OV31).
    A condition exclusion group is merely a grouping of condition types that are compared to each other during pricing and result in the exclusion of particular condition types within a group or entire groups. It is important to note that the condition types you want the system to compare must exist in the pricing procedure and must have valid condition records created for them.
    If for example, a sales order is created using the pricing procedure that the exclusion group is assigned to, you can see that the condition offering the most favorable discount to the customer is represented in the pricing procedure.
    For instance, condition type K007 has offered a discount of 10% off the sale price or a real value of $30, while another condition type K005 has offered a real value discount of $10. The system then takes the best discount for the customer between the two, which is K007 and makes the other discount K005 inactive. This can be seen by double clicking on the condition type K005, where you can find a entry saying u2018Inactive A condition exclusion itemu2019.
    There are four possible methods of using condition exclusion groups u2013 
    A u2013 best condition between the condition types
    B u2013 best condition within the condition types
    C u2013 best condition between the two exclusion groups
    D u2013 exclusive
    E u2013 least favorable within the condition type
    F u2013 least favorable within the two exclusion groups
    Configuring u2018Condition Exclusion Groupsu2019
    First step is to define a u2018condition exclusion groupu2019 by using a four character alpha numeric key.
    Next step is to assign the relevant condition types to the exclusion groups such as discount condition types, freight condition types.
    After completing the assignment of the condition types to the exclusion group, proceed with assigning the condition exclusion group to the relevant pricing procedure.
    After selecting the pricing procedure for which you want the condition exclusion to be active, select the folder u2018Exclusionu2019 where you can assign the relevant condition exclusion procedure to the relevant condition exclusion group.
    When using the condition exclusion group to find the best condition record in a condition type u2013 only use one condition type per exclusion group. The most important thing to remember here is to u201Cdeactivateu201D the Exclusive Indicator on the access sequence assigned to that condition type. Otherwise, the system will merely find the first condition record and stop searching for other records.

  • Rebate condition type

    Dear Experts,
    I have created a condition type for material rebate and the same has been assigned to condition type grp in turn condition type grp is assigned to rebatye agreement type....besides the same(cond type) is included in the pricing procedure.....the issue is even after maintaining the cond record the values are not flowing moreover when I see to the condition type details in the order level( I
    deliberately made the rebate cond type to flow in sales order) few settings got changed like scale type,calculation type,..etc...how come the settings may change other than what I have maintained...I could see my own settings exist in V/06 for the rebate cond type.....what would be the reason?.....thanks in advance.......

    Hi,
    1st see in condition detial,maintain
    Processing priority - Automatic entry has priorit or No limitation
    Second,in price procedure V/08, if you maintained any requirement in requirement coloumn in front of rebate condition then remove that.
    Kapil

  • Multiple rebate conditions

    Hi folks:
    I hope you can shed some light on this issue I am dealing with.
    We are trying to use rebate agreements in the following situation, but it does not seem to work:
    The company negotatiates a deal whereby a client gets a Credit Note with a global discount if it meets 2 targets during a specific period:
    Material Group 1        Target volume 1  =  100 KG
    Material Group 2        Target volume 2  =  200 KG
    If sales to the client exceed both targets, at the end of the period a Credit Note is issued for 10% of the overall sales to the client during the period. If one or none of the targets are met, there is no global discount for the client.
    We are trying to implement this via a Rebate Agreement with 3 rebate conditions:
    Condition 1 = ZB01 (Customer/Material Group rebate); scale starting at 100 KG; 1% (for the sake of this example, just consider 1% as an arbitrary value to ensure that the condition will be <> 0 if the sales for Material Group 1 exceed 100 KG)
    Condition 2 = ZB01 (Customer/Material Group Rebate); scale starting at 200 KG; 1% (for the sake of this example, just consider 1% as an arbitrary value to ensure that the condition will be <> 0 if the sales for Material Group 2 exceed 200 KG)
    Condition 3 = ZB02 (Customer rebate); no scale; 10 % (global discount specified in the agreement)
    Our idea was to configure the pricing procedure in such a way that the first two conditions would be statistical (that is, would not alter the value of the Credit Note) and the third condition would be considered only if the other two were both <>0.
    So far we have not found a way to make the first two conditions not affect the value of the Credit Note. We tried marking ZB01 as statistical. We also tried using Condition Exclusion Groups. In all cases, the two conditions affect the value of the Credit Note.
    Has anybody dealt with a similar situation? Any ideas?
    Thanks,
    Sebastian

    Hi Sebastian,
    really a very niceissue to think some time ,
    Any way for the two condition types zb01&zb02,there is an exclussion indicator while creating the Acess sequences for the two condition types .Check that and tried.Correct me if it is wrong.
    If it helpfull Rewards me the points.
    Rgds
    Siva Yepuri

  • Rebate conditions with mulitple validity dates

    Hello,
    I have an urgent requirement.  My customer wants to define different rebate rate by date in one agreement like normal pricing condition types.
    for an example,
    The validity date of the agreement is
    1/1/2008 ~ 3/31/2008
    Rebate conditons are as follows,
    Material A  $2 per 1unit,  1/1/08 ~2/28/08
    Material A  $3 per 1unit,  3/1/08 ~ 3/31/08
    I would appreciate with your help.  I will give you high point!

    Hi,
    Thanks for your answer.
    When I tried to create a new condition record with different validity date, the system gave me a message "VK 104, the condition is being processed in current session".  and then removed the record from the screen.  It's because of the same condition key exists.
    I think it's related to the difference on condition tables.  When I checked a condition table for PR00, the attribute was "with validity period" but a rebate condition table had none in attribute.
    Do you have any idea?

  • Condition Type - Exclusion settings

    Does anyone have a good explanation of the differences between the condition type exclusion settings?
    A - Invoice List
    O - Event
    U - Metal Price
    V - Sls Prc. Calc. Surch.
    X - Net Price

    Hi,
    this field is used to exclude any discount type from the pricing evenafter maintaining condition records existing. u may ask the question like why to exclude after the condition records are maintained for that.
    observe the below scenario;
    one pump is costing Rs. 1500/- to all normal customers and offering 5% trade discount on certain termas and conditions
    but there are few customers who take in a bulk quantity and has good reputation and payment history with the company and getting the same pump for Rs.1200/- as net price.
    now company wants to exclude these special customers getting 1200/- from this discount of 5%.
    inspite of  base price conditon type and discount condition type existing in active mode in the pricing procedure system will not consider 5% discount when we billed to this special customer.
    How?
    maintain the condition records to these special customers basing on the someother condition table like customer classification field or anything that differentiate from normal customer and give the value net value in condition records details screen. then system restricts this discount.
    the pre-requisite is this discount conditon type should not be included in conditon supplement table.
    i never happened to see the other options u mentioned in question.
    i hope u understand the scenariio
    regards,
    sadanandam kasarla

Maybe you are looking for