SD - Rebate Agreement configuration

We have been trying to configure rebate agreements for retroactive discounts to be given for a month - which is to be based on the total off take invoiced value for each customer.
In the Condition type we need to -
1)  Use value scales - eg upto Rs.125000/- invoiced value
2)  The margin is a %age of the invoiced amount e.g. 9.5%
3) The Value scales are as under:
     upto 125000/-               9.5%
     125001 to 260000        11.5%
     AND SO ON..................
4)  Till now we had used a condition type which would give volume based discounts as under:
     upto 10 units               nil
     11 to 20 units              125/- per unit
     21 to 30 units              275/- per unit
5)  Now the scheme has changed and we need to configure a new condition type as per s.no. 3
6)  In the current condition type - ZFVB which we were using for s.no.4, the values were as under:
Access sequence = BO03
a)  Condition Class = 'C'
b)  Calcut type = 'C'
c)  Scale basis = 'C'
d)  Check Value = 'A'
e)  Unit of measure = REB (this was assigned in the mat master)
f)  Text Determination = '02'
Thanks in advance
anjali

Hi
I tried working out with these changes suggested - it still does not work.  Actually - the earlier condition had used REB as the Unit of measure and this was also maintained in the material which were eligible for rebate through the reb agreement.
Now, with the current config as suggested by you - the UOM field in the condition type is not accepting any values.  So maybe there should be some link between the reb agreement with Payer and material that is being missed out by us.
thanks
anjali

Similar Messages

  • Rebates agreements (extremely urgent)

    Dear SAP experts,
    I need your help in rebate agreements (RA).
    I have setup the condition tables for RAs to accept Sales Area, ship-to, and EAN (MARA-EAN11) as combination. Together with material determination table, it does a mapping/substitution whenever I create a sales order which works like a charm to map to the access sequences and conditions I have created.
    However, there is an issue with this setup. Each EAN can actually map to multiple MARA-MATNR (material numbers) depending on the MATNR lifecycle (i.e. 1 EAN to M MATNR).
    For instance, EAN 123456 can have material abc assigned to it today, but due to a product being pulled out of market, business reuses that EAN 123456 and assigns it to another MATNR later on. To ensure that the right EAN-MATNR combination happens at a time, the material determination table (MDT) was used as an approach.
    However, when I create RAs with condition type Sales Area, ship-to, and EAN (MARA-EAN11)  combination, the "material for settlements" field is required as input. As the "material for settlements" field is KONP-BOMAT with check table MARA, it is not possible for me to put in EAN for the material as it requires a MARA-MATNR field.
    One of the options I was thinking was to do a conversion using MDT prior to creation of RA. Note however that when the MDT data changes, there will be inconsistencies with what's happening in real life versus what was mapped: the RA's take the conversion from EAN -> MATNR based on the contents of the MDT at the point of RA creation, and do not get updated automatically even when other MATNR get assigned to the same EAN.
    My questions as follows:
    1. What is really the materials for settlement field? How does this field impact the creation of credit memos? How does this impact the settlements process?
    2. I would need to create an output report based on the rebates generated on EAN level. My understanding is that SAP is working on the MATNR level. Is there any way to go about this given the situation described above?
    3. Given that the data in the MDT changes against the FPC, is there any way to ensure that the EAN is the "key field" used for data processing in place of the MATNR field in the RA "material for settlement" field?
    4. Any advice on how EAN will impact RA creation, order, delivery, shipping, invoicing?
    Thanks a lot for your help in advance.

    hi
    Rebates Processs in SAP is divided into three components
    1) Configuring Rebates
    2) Setting Up Rebates
    3) Managing rebate agreeeements and payments
    Pre-requsiistes- Check the following:
    1.The payer partner needs toi have the rebate field checked in the customer master on the sales area-billing doc tab.
    2.The Billing type must be marked as relevant for rebates.
    3.The Sales Organisation must be marked as relevant for rebates.
    Condition Technique :
    Rebates, use the condition technique, but distinguish themselves from pricing in applying to transactions over time, versus on a transaction basis. Rebates have their wn field catalog and their own condition table naming convention.So you could have two condition table "001" one for pricing and one for rebates, which could have different key fields. You need to use the technical names A001 For pricing and KOTe001 for rebates when you use the query type using transaction SE 16..
    Use create access sequence (AS).  Enter 1 in field category for rebate specific.  AS after going thru the right path of maintaining access sequence for rebates.
    The big difference between the rebate and the pricing access sequence is that there is no exclsuion flag available for rebate related AS. This means multiple tables for an access sequence can be aplied at the same time.
    Rebate related condition types are identified by codnition class -C.
    After defining and creating condition types for rebated include them in the pricing proceedure. The requirement should be 24 here which implies that the accruals are calculated on the basis of invoice/bill.
    The other fields- alctyp and altcbv does not allow you to manipulate how a rebate is calculated. Also, remove the requiremnt 24, if u want to see reabtes at order time.
    Now payment of rebates:
    Payments can be maunal or in full settlement. When you do manual payments, it defines how much can be paid out during a partial settlemetn.  You use partial settlement only when rebate agreement is defined for a full year but the paoyouts are supposed to happen on a monthly, quarterly or anyother specified period.
    These accurals are based on sales volume and when they are posted billing is created int eh follwoing manner. Provision for accruals is debited and Sales revenue is credited. When rebate credit memo is created
       Customer account/ is debited and
       Accrual provision account is credited.
    Also, please note that when rebates are created without dependent ona material but on customer/material you need to refer to a material for settlement.
    Rewards point it helps

  • Final Settlement for Extended Rebate - agreement status not updated

    Hi,
    When doing final settlement via the Extended rebate, a CM is generated, but the status of the agreement is not updated to D.  Any configurations needed or steps to be done? I thought it should be automatically updated by the system..
    Thanks,

    Hello
    Refer following links with SAP Note for reference/understanding:
    - The sales volume for Rebate agreement  is not current
    - Sales volume not current in Rebates
    - 456458 - FAQ: How does SDBONT06 work
    Thanks & Regards
    JP

  • Rebate Agreement manual accruals not updating in agreement

    Hello,
    I am configuring extended rebate agreements and am working with the MANUAL ACCRUAL functionality. 
    I can create a manual accrual from the agreement and sales order type B4 is created and billed as type B4.  I can see the impact correctly to the G/L and provisional accounts.  When i go back to the agreement in VBO2, I DO NOT see any error messages saying the agreement is not up to date, but i also don't see the accrual increase under the Sales Volume or Verification views. 
    I only see billing document that came through regular customer invoices where i accrued.  If i look under Rebate Payments menu ---> Rebate Documents, i see the manual accrual documents.  My question is...if i accrued 500$ through regular invoicing...and then we do a manual accrual for addition 200$, where do i see a total accrual of 700$?  All i seeunder verification is the original 500$?  Is this just standard behavior? 
    Note:  i've checked agreement config and manual accruals are checked on...info structures set to "1 Syncronous Updating" and agreement is up to date per VBOF. 
    Regards

    Hi Neeraj,
    When you post manual accruals via a billing document which is posted in FI, the table S060 will be updated with the amount for the condition record (field S060-RUWRT) this field holds a total value of accruals this can include manual accruals, postings form relevant billing document lines and accruals that were reversed via a partial payment. When the final settlement is carried out all of these are calculated and the accruals condition in the final settlement will reverse completely all accruals related to an agreement at that time.
    However, Rebate payments have to be made to a customer based on REAL sales volumes. If there is no sales volume then no payment would be due.
    Regards,
    Raghavendra

  • Rebate agreement conditions

    Dear All ,
    I am facing a problem in configuration of the Scenario..
    Can any one help me
    Scenario 1:
    The business wants the average net sales to be a controlling factor for the rebate program. The business will pay the rebate to the customer only when the customer purchases a certain specified quantity of product at a certain specified price. If the customer purchases it at a lower price, the business will not provide any rebate to the customer, even though the customer has achieved the specified quantity.  
    Scenario 2:
    The business wants to have the scenario like for the distribution channel, customer, Product hierarchy, if the customer purchases anything from any product hierarchy, anything more than 6 ton will get a rebate of 2 THB. For purchase between 6 ton to 10 ton, the rebate will be 3 THB; for 10 ton to 20 ton, 8 THB and from 20 ton tol 30 ton, 10 THB and for which the SO date is from 1-31 and billing date from 1-31. So how can i maintain the rebate Scale so that the scenario can work..
    Thanks in advance

    Hi Francois!
    Have you managed to find Business Content extractors to these rebate agreements? I should also find a solution to this question.
    I would be delighted to hear your experiences you have had with this data extraction!
    Best regards
    Sari

  • Extended Rebate Agreements

    HI All Gurus,
    We are using the SAP ECC 5.0 Version.
    My Client Requires certain features which can be handled through Extended rebate agreements.
    As per the documentation.
    Can Anyone help in how to activate the Extended Rebate Agreements.
    Thanks in Advance
    Sachin Dhiman

    Thanks a lot Alex,
    I have done the same.
    And now the extended Rebate Agreement link is available.
    Can you send me some document that gives me the steps for configuring the same.
    Here my client Requires Rebate agreements to be setteled retrospectively and the COPA to be updated at SKU Level i.e. Material level.
    As far as I have read about extended rebate agreement,
    this kind of requirement can be handled using variable key.
    If you have further input on this, kindly let me know.
    Anyways Thanks a lot for this help.
    regards
    Sachin Dhiman

  • Rebate Agreement against Payer (HeadOffice)

    Dear Experts,
    I have a scenario where one of my customer is having several branches and one head office. I customer master against each branch customer we have maintained the main customer number in Head office field and sort key as '004'.
    The head office acts as the payer where as branch customers are maintained as Bill to Party.
    We need to create a rebate against the head office so that when ever a new SO is created against any of the branch customer the rebate agreement should flow.
    Please let me know what should be configuration changes to be made.
    Thanks
    Ranjit Simon

    Hi Ranjit,
    In Customer Master, at company code data view you would have assigned main customer in head office field, the one use of this assignment is, @ SD- billing would have created for branch office, but system will allow collections only under head office, this assignment is for FI related activites.
    For sales and distribution discounts and rebates to flow from head office assignement to branch office, then you need to create customer hierarchy in sales and distribution (under TCODE VDH1N and VDH2N).
    then create discounts and rebate for Head office, that will automatically flow to branch office customer transactions.
    There is a separate account group exist to create head office and under which we can assign sold-to-party as branch office.
    Regards,
    Vairavan.

  • Rebate Agreement :SDBONT06

    Hi ,
    I am using ECC 6.0 and have configured rebate agreement . In VBO2 in am getting an Information massage "The sales volume for agreement  is not current". I run the program "SDBONT06" (Transaction Code:VBOF)for updating the sales volume for the agreement.But still this massage comes and the sales volume showing 0. Am i missing any thing.Kindly advice ...
    Thanks In Advance.
    Regards,
    Abhijit...........

    Hello experts
    I have a problem using report SDBONT06:
    have one invoice with 3 items, all 3 items have the same contition of
    rebate. The diference is that the "access Sequence in analyse of
    pricing " of item 1 is different of access sequence of item 2 and 3.
    Note: The access sequence of the contition type includes 4 tables of
    access. Item 1 find access in table 1 and item 2 and 3 find access in
    table 3.
    The invoice that i refer before save the 3 contitions in all 3 items,
    but when i run the report SDBONT06 i get the information "condition
    deleted" of item 2 and 3 of invoice.
    This report can not delet the rebate conditions in same invoice if the
    access in all different items are different.
    Steps for Reconstruction    
    Agreement: 1000000017 - Agreement type ZBM2
    Billing document: 1601000024:
    Item 10 - Analysis: Condition type ZP1A - "Condition record has
    been found" - access 01(ZBS1)
    Item 20 - Analysis: Condition type ZP1A - "Condition record
    exists, but has not been set" - access 03 (ZBS1)
    Item 30 - Analysis: Condition type ZP1A - "Condition record
    exists, but has not been set" - access 03 (ZBS1)
    Can any one tell me why the report delet the conditions of item 20 and 30?
    Thanks
    Lina

  • Rebate Agreement Calendars

    Our business has five main Rebate Agreement (Arrangement) Calendars :
    October to September
    July to June
    April to March
    August to July
    January to December
    There are additionally, some other validity periods that we might use, such as six-monthly, however the above five calendars probably account for 80-90% of our Rebate Agreements.
    The problem :
    We want to be able to use Rebate Agreement Calendars to automatically extend Agreements for a further 12 months. However, my understanding is that each Rebate Agreement Type is only designed to work with a single Calendar, therefore we would have to create a further four copies of an Agreement Type, each with a different calendar assigned. E.g. :
    RA Type Calendar Description
    ZR01 R1 October to September
    ZR02 R2 July to June
    ZR03 R3 April to March
    ZR04 R4 August to July
    ZR05 R5 January to December
    and the same for all other Agreement Types we use. This would result in a ridiculous amount of duplicate/needless configuration.
    We have unlocked the screen field to be able to change the Arrangement Calendar in VBO1/VBO2. However, we still have to set a default Calendar in config, via txn VB(2, and that default flows through to the RA on creation. Although it is then possible to overtype the Calendar, only the default appears in a picklist, which is confusing to the user. In addition, even if we overtype it, if we then extend the RA via VB(D, the Calendar maintained on the individual RA will be ignored, with the Calendar taken from config again.
    I find it hard to believe that we are the only company wanting to use Rebate Agreement (Arrangement) Calendars in this way, is there something obvious I'm missing ?
    Many thanks, Paul.

    Hi Jo Jo,
    I had implemented Rebate in my company and had similar problem.
    After doing Trial & Error on Sales Volume & Verification level screen I found:
    In Sales Volume :
    After u201CPayu201D of Accruals, remaining value comes. If the credit note created is not passed to A/C, the value does not get reduced. Also, unless the Invoice/Billing Doc. is passed to A/c. the value here shows 0 (ZERO)
    Items that show accruals of 0 are invoice line items that applied retroactively. Since the rebate agreement did not exist when they were created, no accrual could be made.
    In Verification level:
    Total accruals, document and item wise come.
    So the difference may be due to some of the docs that are not passed to Accounting or may be due to retroactive agreement.
    Hope it adds value to your question.
    Regards,
    Tushar Karwa

  • Rebate agreements / Rebate condition type

    Hi Experts,
    Can anyone tell me how to process Rebate agreements/Rebate condition types in pricing procedure.Please help me by giving step to step description for rebate condition type and where to maintain condition records and how they function.
    Thanks in advance experts,
    Kanna Palle.

    Hi ,
    find some notes on rebates.
    in the billing document, the rebates are calculated as per the the accrual rates in rebates condition records. My question if the invoice is for Rs 100 and accrual rebate amt in invoice is rs 2. will the customer pay Rs 98 against this invoice of full Rs 100.
    Ans --> Customer need to pay Rs 100 only , rebate amount will paied to the customer after completion of the rebate duration in between there will be partial settlement.
    2) what happens during manual accruals. why a credit memo request is generated during manual accruals. what happens to accruals as per condition records.
    Ans--> Manual Accruals
    Use
    Posting accruals manually can be useful in different situations such as:
    Lump sum payments
    Accruals correction
    You can control at which time and for which amount the accruals should be posted.
    You can build accruals for a particular condition record or reverse them in part or in full.
    When you save the rebate agreement, the system will automatically create a credit memo request. The system uses this document to create a credit memo. When the credit memo is released, the accruals are posted to FI.
    If you have posted accruals manually, but these have not been passed on to financial accounting, the manual accruals and manual payments in the rebate agreement are blocked.
    3) what happens during partial settlement. do the accruals already poested gets reduced to the extent of amount of partial settlement. do manaul accruals have any role to play during partial settlement
    Ans->Partial Settlement
    Use
    You can also partially settle a rebate agreement during its validity period. The amount to be paid can be limited in Customizing for Sales. Payments can be:
    limited to the cumulative accruals of the condition record
    limited to the amount that would be paid if final settlement were presently carried out
    unlimited
    You carry out partial settlement by using the manual payment screen within rebate agreement processing. On this screen you can specify the amount to be paid for each condition record.
    The system will automatically create a credit memo request for the amounts specified.
    It will also reverse the accruals with the credit memo if the rebate agreement type is configured accordingly. If the payment exceeds the recordu2019s accumulated accruals, the system will only reverse the accruals which are actually there.
    The system gives you the opportunity to carry out additional partial settlements when previous partial settlements remain open in the form of credit memo requests or credit memos. The system always takes open documents into account when determining the maximum amount which you can pay.
    When the system carries out final settlement for a rebate agreement, it takes all partial payments into account.
    4) what happens during final settlement. do manual accruals have any role to play during final settlement i.e. do they get reversed and what happens to accurals posted as per rebate condition records.
    Ans-->Final settlement
    Use
    When you carry out final settlement of a rebate agreement, the system automatically
    calculates the rebate based on the sales volume statistics or the lump sum
    deducts any previously paid rebates
    It then creates a credit memo request, and proposes the end date of the agreement validity period as the billing date.
    The system also reverses any accruals that have been posted.
    Depending on Customizing, when the system creates a credit memo request, the document is automatically blocked for billing. After approving the credit memo request, the person responsible can remove the billing block. You can then create the final credit memo.
    When you want to search for credit memo requests during sales order processing, you can use the match code F "Credit memo request for rebate".
    You can carry out final settlement of rebate agreements
    automatically
    Manually
    as a background task (in batch)
    Settling Single Rebate Agreements
    You can carry out settlement directly from within a rebate agreement.
    Before you save the rebate agreement you can still carry out changes to the credit memo request:
    The credit memo request is only saved when you save the rebate agreement.
    Carrying out Final Settlement as a Background Task
    If the volume of your sales rebate processing is high, you can collectively process rebate settlements as a background task.
    The following reports are available:
    RV15C001
    RV15C002
    Your system administrator can use these reports to generate a list of rebate agreements, based on various selection criteria, such as rebate recipient, status of the agreement, and so on.
    Background processing can then be carried out later. I.e., after the regular posting periods.
    After a list is generated, the rebate agreements can be analyzed or processed for payment.
    For more information about settling rebates as a background task, see your system administrator.
    Best regards,
    venkataswamy.y

  • Creating a Rebate agreement doc for multiple co codes

    Hi,
    To enable settling one rebate agreement across multiple company codes.
    We have a scenario, to accomodate on Rebage agreement type for multiple company codes,
    and to do the settlement for the billing documents created in these multiple company codes.
    I think it is a standard processes, but how to execute this to get the results,pls suggest.
    Regards
    AK

    Hi Franck,
    Thanks for your prompt feedback,
    Further to the issue I would like to clarify couple of other issues related to
    the processing of one Rebate agreement for multiple company codes.
    1. This is a client requirement, which need to be addressed through
    enhancements since standard possibility is ruled out, we have tried with this scenario but sales area is a mandatory entry while creating the agreement type (Tcode-VBO1).
    2.  If it is feasible could you please provide the configuration steps for the scenario or any enhancements related to this scenario for implementing.
    Kindly explain what do you mean by IMHO?
    Regards
    AK

  • Problem during settlement of an enhanced rebate agreement

    Hi,
    I am trying to configure enhanced rebate agreement in my company. I think I've completed all prerequisites to start using this functionality: the enterprise extension EA-ISE is active, the info structure S136 and S469 were configured by using transaction OMO1, a VARKEY was assigned to an agreement type, table TMC2F has the required entries, etc.
    As a matter of fact, when I create a billing the corresponding records in table S469 are inserted with the corresponding VARKEY (which only include de material number). However when I run the transaction RBT_ENH_VB7 to execute a final settlement  of the agreement the material registered in VARKEY field of table S469 are not being transfered to the memo credit. Instead of these, the memo credit is created with the material of settlement.
    ¿What part of the configuration is missing? I have execute several times the transaction RBT_ENH_REBUILD but the result is the same.
    Thanks in advance for any help you could provide me
    Best regards
    Andres

    Hi,
    I found the cause of my problem. The standard functionallity of extended rebate agreement was ignoring the record of table S469 because in transaction OMO1 the period split was defined as Day. The standard functionallity only consider "Month" as a period.
    After modify this setting the memo credit created in a final settlement contain several lines associated to the records of table S469
    Problem solved

  • Alphanumeric number range of Rebate agreements

    Hi,
    Question on using u2018Alphanumericu2019 number range of Rebate agreements. We would like to use alphanumeric number range for our rebate agreements so that we can build certain logic such as year\customer\type for easy reporting & grouping. For instance first digits for year, next 3 digits for customer code and so on. We are using SAP 4.7.
    Question - Are there any disadvantages of using alphanumeric number range for Rebate agreements. Does it cause any performance issues. I hope it is not. What we read & noticed that Rebate related transactions & reports are performance intensive.   Hence I would like to double check with forum if anyone using alphanumeric number range for Rebate agreements & any issues encountered.
    Any feedback on above would be really appreciated.
    thanks
    Sunil

    Hi,
    I dont think there will be any impact on performance if you use an alphanumeric number range instead of a number. Anyhow,  you have to use a number range. You are only enabling this by coding(may be) instead of just configuration.
    The only thing you have to remember is that there should not be any buffering issue in number range. Otherwise your own number range (alphanumeral) will work as good as any other number range.

  • Re:Rebate Agreement Setup for CRM 2007

    Hello Friends,
    Essentially, when we are setting up Rebate agreement types in ECC in customizing, We need to specify a Settlement document type.
    Given that with CRM 2007, the rebate agreement will not be used for settlement is there any thing that they can do to not specify the Settlement document type. Since we have to specify a Settlement document type, can anyone one give  guidance regarding customizing/configuring the Settlement Document Type?. Also that it should not create the Accounting document.
    Thanks,
    Julie

    check the number range in ECC for this Reabte.
    Can you give me the BDOC error which is triggered and The out bound queue also sholud be in error.
    Check the out bound queue and try and reprocess that i think it wll have the dump in ECC system.
    please check that dump and take corrective actions.
    thanks
    Kumar

  • Plant specific rebate agreement.

    Hi Gurus.
    My customer is ordering material  2-3 depots & 1-2 factories.
    Can we  configure it as when customer orders material from "X" depot only he should be liable for  rebate.
    whereas rebate agreement is already created on customer, but it doesn't have any Plant(Factory/Depot) option.
    Regards,
    Antaa21

    Hi Viv_EU.
    Thanks for your reply but after changing the Access sequence "BO03" with plant added, what will happen to  existing Invoices,
    will those get updated?
    or it will be applicable for rebate agreement & invoices created henceforth?
    Reg,
    Antaa21.

Maybe you are looking for