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

Similar Messages

  • How to create scales for conditions for rebate agreements?

    Does anybody know any function modules or bapis to create scales for rebate agreement conditions.I want to create entries in konm table where scales for conditions get stored.Also pls tell me how to link contributory volume by programaticaly?
    Thanks in advance

    Part of my question is answered .I could find parameter in BAPI_PRICES_CONDITIONS to create scales for conditions.But do anyone have any idea how to link contributory volume to conditions? i have conditions and also contributory volume? can anybosy send me some material which explains the contributory volume..atleast functionally?

  • Rebate Agreement Query

    Dear Gurus,
    I have a customer XYZ, which have sales area 1000-10-10 and also extended on 1000-10-20 division, rebate check is mark on both the extended sales areas.
    My material 40000000 is associated with division 20.
    When I generate the agreement it ask me the sales area I enter there 1000-10-10, although material is associated with division 20, and create a record with material 40000000 with accural rate 5%.
    I notice that when i generate the invoice system call the rebate agreement condition type. that is fine and acceptable to me.
    But i just have the query that why system ask me the sales area at starting of rebate agreement and if I enter different sales area that not associated with the material, than standard system performs the rebate ? as yes it perform.. is it standard functionality..
    Looking forward for the gurus response.
    Regards,

    Hi
    Maybe I can give you a standard example that will help clarify this for you.
    You create a 0003 rebate in sales area 0001 01 00
    The rebate condition assigned to the agreement type is Bo03
    When you save the agreement the system writes this condition record
    into table KOTE003 with the key Bo03 0001 01 01 customer and agreement number
    with validity dates.
    If you then create a sales document (without requirement 024) you will see in
    the pricing analysis how all the conditions were found and the values that
    were used to find them. The division is taken from the document header not
    the item in standard. So if I have a valid agreement in sales area 0001 01 01
    and I create a sales order in header sales area 0001 01 00. There will be no rebate
    condition found in the document. If you go to the pricing analysis to the rebate
    condition you will see that the system was trying to find a condition record for Bo03
    in table KOTE003 with 0001 01 00 (from the sales order) but the valid entry is in
    0001 01 01.
    In your case if the condition is found in the KOTE* table it is because you have
    an entry in the table for that combination otherwise you would get message
    'Condition record is missing' against your condition in VA01
    Hope this helps you further
    Kind regards
    Brian

  • Rebate condition in rebate agreement cannot be maintained (greyed out)

    Hi.
    We have setup rebate processing in CRM 7.0.
    We get our invoice to the billing due list and it fills then the extract. But we fail in setting up the rebate agreemnt in the webui.
    Partner and material are entered. On the position (material) we try to add one of the conditions of the maintenance group we customized. Both condition types can be selected but none of them will work.
    What happens: we click on "new" select the condition type and get then presented with the view but with all fields greyed out (as in display mode).
    As there are a lot of obligatory fields we get up to 8 messages. After "fill in required entry fields" it says "maintain rebate material".
    Whatever that means.
    The material we use is a finished product.
    Has somebody ever seen this or some idea. Couldn't find oss messages on this.
    Thanks.
    Regards,
    Thorsten

    Hi Klaas,
    If I remember well, in the standard price determination there is a conditional formula that only shows rebate conditions in the invoice, therefore you should not see rebate conditions in the sales order.
    That is standard functionality.
    For a Customer I took out the formula condition in the pricing so he could actually see the rebate condition in the sales order, the reason was to had access to this information before end of month invoicing. The problem is that in case of changes in rebate agreement or in case of retrospective agreements the rebate condition is only updated in the invoice, not in the sales order.
    Best Regards,
    Franck

  • Condition Types in Rebate Agreement

    Hi,
    Please help me with the condition types in RFQ  rebate agreement and their descriptions.
    Thanks in Advance
    Vikram

    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?

  • 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

  • Rebate Agreement Upload: Condition data

    Hello Gurus,
    My client system is undergoin SAP to SAP implementation, which requires conversion of all the Rebate Agreements. We are providing the SAP table data extracts to the technical team for the conversion.
    The conditions for the Rebate agreements are stored both in condition table KONH/ KONP and Condition table for Rebate: KOTE001. What is the significance and difference between data in the two tables??
    Is it possible that data in KOTE001 is sent along with general rebate agreement data and KONH KONP data is later migrated while doing Sales Pricing conversion..
    Please advise. Reward pts for useful answers.
    Thanks, C Mehra.

    This is how I bridged the gap. May not be best solution intown but this meets the requirement.
    I created a implicit enhancement on the FM:MM_ARRANG_NEW_ARRANG_INSERT and added the following code.
    Logical Position:    \FU:MM_ARRANG_NEW_ARRANG_INSERT\SE:END\
    CONSTANTS:
         lc_action  TYPE c VALUE 'I' .
    DATA:
         lv_subrc   TYPE sy-subrc .
    ** Core logic
    IF sy-subrc EQ 0 .
    **  Insert the records to the table KOTE001
      PERFORM db_update IN PROGRAM rv13e001
            TABLES t_new_vakedb
            USING lc_action lv_subrc .
      IF lv_subrc NE 0.
        sy-subrc = lv_subrc .
      ENDIF.
    ENDIF.

  • Settling Rebate Agreements with Validity Start Date not Start of the Month

    Hello Experts,
    I am currently trying to settle a rebate agreement with validity dates November 20, 2011 to December 31, 2011. However, after the credit memo is created, I noticed that the Service rendered date is today's date, but I expected it to be the same as my Settlement Date = November 30, 2011 (a month-end). Please advise if this is normal. If not, please advise how to correct the automatic entry of dates.
    Thanks,
    M

    Hi
    Kindly let us know what is the rebate agreement type that has been used for which you are facing problem and for which rebate agreement type you are getting the month end date.Check wheather scale basis is B(Value scale) has been maintained or not for the rebate agreement for which you are getting problem.So check the differences between the two rebate agreement types.As The service rendered date of the invoice line item is used to determine the validity of a rebate condition record
    Regards
    Srinath

  • Rebate Agreement Replication CRM to R3 and vice-versa

    Hi All,
    We have a requirement of creating Rebate Agreement and maintaining the conditions in the same.
    When we create an order (in R3 or CRM) the values has to be populated from the rebate agreement.
    Scenario A:
    The setup of rebate is completed in R3, we have downloaded the conditions from R3 to CRM and when we are creating the order in CRM the rebates are not getting recognized. Upon analysis we found that we have to download the rebate agreements too and the respective object is REBATE_DNL_AGR.
    (Rebates are working fine for Pricing in R3.)
    Scenario B:
    We have tried an workaround of creating rebate agreements in CRM and uploading them to R3, object used is REBATE_AGRMNTS but no success.
    (In this case rebates are working fine for Pricing in CRM.)
    We are facing issues in replicating the Rebate agreements from CRM to R3 and vice versa.
    When we do the initial load R3AS of below objects, they are not progressing and not appearing in queues too. Status is always running
    CRM to R3 for rebate agreement – REBATE_AGRMNTS
    R3 to CRM  for rebate agreement - REBATE_DNL_AGR
    If you have any inputs, pls share. Thanks
    Regards,
    MK

    Hi  Kalyan,
    Did you achieve scenario B ?. You also mentioned that for scenario B , it works fine with pricing in CRM. Was the billing happening in CRM or ECC in that case ?.
    Did the scenario A worked ?.

  • What is the DataSource for 'Rebate Agreement' (Data comes KONA,KONP&KONH) ?

    Hi all,
       What is the DataSource name for 'Rebate Agreement', please?
       This data comes KONA, KONP & KONH tables. 
    Thanks,
    Venkat.

    Hello Venkat,
    you can extract it from 2LIS_13_VDKON Extraction of SD Billing Conditions
    http://help.sap.com/saphelp_nw2004s/helpdata/en/17/cd5e407aa4c44ce10000000a1550b0/frameset.htm
    Sarhan.

  • 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

  • Accruals not updated for Changed Rebate agreement when VBOF  performed.

    Hi Pals,
    Need your assistance in solving an incident  . our client has changed the  valid to date  of the  rebate agreement on 29.04.2014  in VBO2  from 28.02.1014 to 31.12.2014, later it was observed that  the rebate accruals for the blling documents generated after 28.02.104 to till date were not updated even after running the report VBOF. There are 15000 invoices after 29.04.2014 , hence it is difficult to check which invoices carries my rebate condition type.
    hence pls advice on
    1. how to find out the invoices for the changed agreement .
    2. How to update the accruals for the invoices that were created after  28.02.2014 to till date.
    An early reply would be highly appreciated.
    Br
    Krishna.K

    Dear krishna
    i tried your scenario--so after changing the validity for my Material rebate agreement type--i ran VBOF(SDBONT06)--so system has shown the updated billing doc with rebate which was not having any rebate condition earlier.
    Have you tried by retrieving all the billing docs created after service render date of 28th Feb14.
    Please take all the billing docs created after this date from VBRK table and you check some random billings docs whether rebate condition type is active with condition record or not.
    (other wise you try with by executing condition record numbers in KONV(doc condition number--then followed by VBRK)
    pl update us..
    Phanikumar

  • How to use Vendor Hierarchy in Vendor Rebate Agreements

    Hi Friends,
    I need to use vendor hierarchy in vendor rebates agreements.
    Here are some inputs from my end so far I have done:
    Customizing Settings for vendor hierarchy and rebate agreement (agreement type 3000 and condition types A003/ A004) have been done.
    While creating the PO after creating rebate agreement (MEB1) I am able to see all higher partner functions (2A,2B,2C,2D) at header level in PO under partners.
    I have (say ) 3 vendors V1, V2, V3 (V1 being highest) set up in vendor hierarchy (MKH1).
    My requirement is; if my company make any rebate agreement with vendor at any node below the highest in the vendor hierarchy then that business volume should be taken in consideration for rebate purpose with the vendor at higher level while making any agreement with him.
    I request you to please let me know how to set up this.

    Hi lvshaolong,
    Thanks a lot for your reply.
    I believe I have not misunderstood the business scenario.
    But may I request you to tell me the process steps for the senario you told which is "Normally , you define condition with highest node in hierachy and then you can refer to it when you do biz with the lower nodes". How vendor rebate process takes place this scenarion (I mean process flow).
    This might help me to find some solution further.
    More input from my end:
    When I am creating the PO against a vendor included in the vendor hierarchy(after agreement), rabate condiion A003  or A004 is not appearing in pricing and hence during BV comparison,system does not find any data to update.
    Regards,
    Munish

  • 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 accruals invoice reports

    Hi Team,
    As per my client requirement we need to prepare the below  rebate agreement accruals invoice report.
    Rebate agreement
    Rebate recipent
    Customer
    Invoice date
    Invoice
    Invoice Item Number
    Rebate Material
    Rebate material net quantity
    Invoice price
    Rebate accural  condition ( % or $)
    Total Rebate amount
    GST
    20000
    123456 (payer)
    1000
    01.01.2014
    987654321
    110
    ABC
    20
    10.00 $
    $ 10.00
    $ 10.00
    20000
    123456 (payer)
    1000
    01.01.2014
    987654321
    140
    ZYX
    5
    5.00 $
    $ 0/50
    $2.50
    We have prepared the report using rebate tables and achieved the results but we missed below one logic here.i.e.
    Business want to maintain the rebate accruals condition records for few customers accounts in the rebate agreement although it’s not related to rebate receipts account.
    Example: rebate agreement: 20000
    Rebate receipt: 123456 (Payer account)
    Rebate condition records
         1)    Customer & material combination – customer # 1000 and material # ABC – 5.0 % - appearing the reports –Status : Working appearing the reports Customer # 1000 Payer is -123456
    2)       Customer # 9999 and material # ZXY – 5.0% - Not appearing the report – Status: Failed
    Customer # 9999 is Payer – 88888 – both accounts are don’t have any PF relationship with rebate receipts # 123456
    When Rebate Condition records are maintaining for Rebate receipt related to customer (SP) account & material combination level in this scenario – Reports working fine .However, few scenarios like business need to maintain rebate accrual condition records for other payer customer accounts in the same agreement in this scenario – Reports is not pulling the invoice accruals due to logic missing our early logic given based on the rebate recipient customer level. I am excepting a technical logic with functional details in this.
    Could you please help me.
    Cheers,
    Jackon Robert

    Hi Omer,
    Proposal:
    Setup your rebate condition as amount = 0 and accruals = $
    The system will do the accounting movements for the accruals as usual
    When doing the final settlement in SD, nothing will be credited to the customer as the rebate condition is zero BUT the accruals will be reversed (as usual when doing the final settlement).
    That should work because it is standard SAP logic.
    On the other hand, it is a pity not to be able to credit the customer if you already have the rebate agreement created in the system.
    Are you 100% positive about this legal issue in your business environment?
    I did a few rebate projects in FMCG and it is standard practice to send credit memo to the rebate recipient: The Customer (Payer in SAP).
    Nobody ever said it was a problem, because practically speaking it is just one more credit note to the same customer that was invoiced beforehand!
    Best Regards,
    Franck Lumpe
    Freelance SAP Consultant

Maybe you are looking for