Rebate Processing - Customer Rebates

Hello,
We have implemented customer rebates .
We are using the standard condition for the rebates BO03
for the same.
Here we want to pass on the rebate once a certain value
is reached, but the rebate condition appears even when
the value is not reached and even though there are no
billing documents created during the validity period
The rebate condition is fulfilled even when the value is
not reached.
Kindly help me out.
Best Regards,
Ketan A. Thakker

Ketan,
Rebate conditions accumulate sales until they are reach the level at which the rebate should be paid. You would therefore expect to see the BO03 condition in every invoice that is relevant for rebates, as on each invoice it adds to the accumulated business volume.
You should be able to see the value of the rebate accumulating in the rebate agreement.
I'm not sure what you mean by the rebate condition being fullfilled. If your agreement has a target volume in it you cannot have reached this without raising some invoices.
Regards
Peter

Similar Messages

  • How to process Customer Open Items? If that Customer is also an Vendor.

    Hi All,
    I need some help for  the below configuations,
    1. How to process Customer Open Items? If that Customer is also an Vendor to the Company. ( How to adjust these open amounts)
    1. How to process Vendor Open Items? If that Vendor is also an Customer to the Company. ( How to adjust these open amounts)
    Thanks
    Chandra

    Hi Chandra,
    In addition to all the above, if the Customers and Vendors are in different company codes, then, you would have to also do the following configuration.
    Execute transaction code <b>OBYA</b>, when prompted, type in 1st coy code, say A and then 2nd coy code, say B. This would take you to the "<b>Maintain FI Configuration: Automatic Posting - Clearing Accounts</b>" screen.
    In the first frame, where you have
    Posted in : A
    Cleared Against : B
    Under Receivable
    Debit Posting Key : <b>01</b>
    Account Debit : Account Number (The account can be a G/L account, a customer account or a vendor account)
    Under Payable
    Credit Posting Key : <b>31</b>
    Account Credit : Account Number (The account can be a G/L account, a customer account or a vendor account).
    In the second Frame
    Posted in : B
    Cleared Against : A
    Under Receivable
    Debit Posting Key : <b>01</b>
    Account Debit : Account Number (The account can be a G/L account, a customer account or a vendor account)
    Under Payable
    Credit Posting Key : <b>31</b>
    Account Credit : Account Number (The account can be a G/L account, a customer account or a vendor account).
    So, if you are using the Customer/Vendor approach, company A must be set up as both a Customer(Use Txn Code <b>XD01</b>) and a Vendor(USe Txn Code <b>XK01</b>) in Company B and vice versa.
    Once you have completed this set-up, you can then use transaction <b>F.13</b> and/or <b>F13E</b> to carry out your automatic clearing.
    However, if you intend to use the G/L approach, then the account numbers would be Inter-coy G/L account for each coy code as defined in the chart of accounts.
    I hope the above helps.
    Do not forget to award the points please.
    Regards,
    Jacob

  • Preference Processing & Customs Declaration

    Hello Team,
    I am looking out for link between Preference Processing & Customs Declaration
    I checked that the preference duty is calculated based on the tick namely Document Exist available in Import Declaration but how the preference indicator in Material affect the declaration in
    Import Customs Declaration
    Export customs declaration
    Thanks & Regards
    Rahul

    Hello Dave,
    Thanks for the reply. I am talking about the tab Authorization in GTS Product master. If i check document exist indicator in Product Master, it will flow in Inbound Declaration and the preference duty will be calculated with less value (%) than regular duty.
    As per your reply i have few queries
    1)  Is the above understanding is correct?
    2)As per my understanding the preference indicator you mean is the Preference Flag (30, 60, 66 etc) If it is other than that, Where we are maintaining the Preference indicator in GTS Master data
    3) Where we are maintaining the Preference Indicator in ERP master data
    4) Which indicator gets priority GTS or ECC
    5) My material is relevant for Preference and the entry is generated by system in GTS Product master with Preference indicator as 60. How the GTS import declaration uses those information?
    6) How to configure the system which will behave based on the preference indicator in GTS product master system and will calculate the Preference duty than the regular duty in Import declaration?
    Thanks & Regards
    Rahul

  • Processing Customer IDoc

    I am processing inbound customer Idoc. When I am testing from we19 with  some values in E1KNB1M and E1KNKKM , it is processed successfully. If the initial Idoc doesn't have those segments I am populating it in the program with the same value and that time
    Idoc processing fails.
    Status Message ::: In company code M100 , lockbox 12 does not exist
    / Risk category 1 control area 6000 has not been created
    comes.
    Anyone face such types of problem?
    Regards,
    Tanmay

    Take the Error IDoc, without changing anything, process again thru WE19, on debug mode.
    Here you can find where is the problem, May this will help you.
    aRs

  • How to process Customer format parameters with Payment Medium Workbench

    Hi
    I have one bank transfer scenario PC00_M99_FPAYM requiring supplying a payment using the French format FR_ETEBAC_CRT_DOM but the execution date of the bank transfer should be replaced by the banku2019s value date. I planned to enter this required date using the Customer format parameters when running PMW.
    The issue I tried to solve is described here below.
    How to extract the Customer format parameters assigned to the payment medium format FR_ETEBAC_VRT_DOM when processed by the Payment medium Workbench in order to fill the Customer specific user-defined fields (ZREF01 to ZREF10 in structure FPAYHX)?
    I noticed the event type 06 authorizes function modules similar like FI_PAYMEDIUM_SAMPLE_06 but the customer format parameters are only available at low level in function module FI_PAYM_MEDIUM_OPEN (example gc_format_params_c)
    Can someone help on this matter?  That would be great.
    Thanks in advance,
    Henri.

    Just sharing my findings and proposed solution.
    This worked
    The expected date is the value date/payee's bank.
    This date is created by the bank transfer program prior to be processed by Payment Medium Creation Tool (SAPFPAYM)
    According to functional investigation it sounds like the bank transfer program does not allow working with the value date/payee's bank.
    The investigation has been done in the Payment Medium Creation Tool. It allows adding the required value date/payee's bank into a customer format parameter.
    Required configuration and development:
    - Clone the current sap format FR_ETEBAC_VRT-DOM into a new Customized format ZFR_ETEBAC_VRT-DOM
    - Clone the corresponding DMEE object FR_ETEBAC_VRT-DOM into a new DMEE object tree type PAYM ZFR_ETEBAC_VRT-DOM
    - Create a new data structure: ZFR_Bank_Transfer with field CRVAL Value Date at Payee's Bank (comp type PRQ_CRVAL)
    - Assign customer structure ZFR_Bank_Transfer to payment format ZFR_ETEBAC_VRT-DOM and declare field CRVAL as required field
    - Build function module ZFI_PAYMEDIUM_06_FR in charge to extract value date/payee's bank from the customer structure and move it to the customer specific user-defined field ES_FPAYHX_CREF-ZREF01
    -  in new DMEE object tree type PAYM ZFR_ETEBAC_VRT-DOM Replace Source field FPAYH-ZALDT by FPAYHX-ZREF01 in the header record

  • How to Process Customer Orders

    My Question is Using the AdventureWorks2012 Database how would you create a Stored Procedure that will Allow a customer to buy multiple items and the store proc process the whole things and nsert all the necessary information in the Sales.OrderHeader and
    OrderDetail Table.Ex:Like an E-Commerce Store procedure that proces Customer Orders friend told me to ue a TVP to store the items and some eSelect Blah Blah Blah..but can somone please give me an exemple of work me Thought it Please.
    Thank you for Your help !

    Do you want to provide the items as array, a table?
    Create a user-defined data type with a single column.
    Develop a procedure with a table variable as an input parameter.
    Declare a table variable of the type of the user defined data type.
    Loading 10 records into the table variable and pass the table 
    variable to the stored procedure.
    create type tt_example AS TABLE
     (spid int)
    go
    create procedure usp_example
     @spids tt_example READONLY
    AS
     SELECT *
     FROM @spids
    GO
    declare @spids tt_example
    insert into @spids
    select top 10 spid
    from sys.sysprocesses
    exec usp_example @spids=@spids
    Best Regards,Uri Dimant SQL Server MVP,
    http://sqlblog.com/blogs/uri_dimant/
    MS SQL optimization: MS SQL Development and Optimization
    MS SQL Consulting:
    Large scale of database and data cleansing
    Remote DBA Services:
    Improves MS SQL Database Performance
    SQL Server Integration Services:
    Business Intelligence

  • Lockbox processing - customer invoice

    Hi Gurus,
    i have a query on Lockbox processing of an invoice created using F-22 tcode.
    How will we tell the system that this particular invoice ( or say particular customer ) is going to pay this amount to a lockbox maintained in the system?
    I have maintained the configuration for Lockbox using tcodes OB10 ( define lockbox accounts for house banks ), OBAY( define control parameters ), OBAX( Define posting data) .
    i have a sample BAI2 file to be uploaded for the lockbox processing using tcode FLB2.
    regards,
    ficoguy.

    when you send the invoice to the customer, you have to inform your customer the lockbox to which he needs to send the payment.
    As you have already informed him lockbox details, along with his payment to the lockbox he will generally forward the invoice details and checks to the lockbox.
    in the lockbox file, you will see the bank details and invoice number.

  • Processing Customer Master in MDM into SAP

    Hi,
         I have a requirement where I am processing DEBMAS (Customer Master) in MDM and posting in to SAP. Can somebody give me a detailed Step-By-Step procedure to go about Posting this Inbound DEBMAS Idoc to SAP from MDM?
    Thanks,
    Venkat.

    Hi,
    Generally we CIF Customers from ECC to APO , this way all of the information is passed to APO.
    and maintain this customer in ECC View V_CIFVMISD.
    If it is a VMI customer then you need to put some additional info like VMI customer number on VMI tab and need to extend material to customer location.
    If you are creating manually customer in APO then make sure it is assigned to model 000.
    Thanks,
    Pavan Verma

  • How to make a dalog process custom events when blocked by modal dialog

    Hi,
    I would like to understand the way modal dialogs block other dialogs so that I can properly solve an issue I'm having with two modal dialogs, one blocking the other.
    I have an application, netbeans platform based, that opens a JDialog, NewDiskDlg, with it's modal property set to true. This dialog is responsible for starting a thread that will process a given number of files, from time to time, depending on some conditions, this thread will send events to the NewDiskDlg.
    When this thread is started, the NewDiskDlg creates a new JDialog, also with the modal property set to true. Both dialogs have the same parent, the main window. And this works as I expected, the second dialog, ActiveScanningDlg, opens on top of the NewDiskDlg and, until the thread stops, the dialog stays visible.
    When the thread stops an event is sent to this two dialogs signaling that the job has been completed, and here is my problem. The second dialog, the one that is visible when the event arrives, receives the event and executes the dispose() method, releasing control to the NewDiskDlg in the back, but the NewDiskDlg does not receive the event and does not process it correctly.
    I understand the no input can be sent to a blocked window, but does that include calling upon the window's methods?
    I've been looking for some help on this but my search terms are not good enough to provide me with any useful information. I've also read the topic on the focus system that is present in the Java Tutorial but I feel that that is not what I should be looking at.
    The following code is a snippet of the important parts that I described:
    NewDiskDlg has the following methods to process the events
        public void readingStarted(ReadingEvent evt) {
            SwingUtilities.invokeLater(new Runnable() {
                public void run() {
                    scanningDlg.showCentered();
        public void readingFile(ReadingEvent evt) {
            //DO NOTHING
        public void readingStopped(ReadingEvent evt) {
            Lookup.getDefault().lookup(MediaReader.class).removeListener(this);
            if (!showAgain) {
                dispose();
        public void readingAborted(ReadingEvent evt) {
            JOptionPane.showMessageDialog(this, "", "", JOptionPane.ERROR_MESSAGE);//TODO: i18n on the error messagens
            Lookup.getDefault().lookup(MediaReader.class).removeListener(this);
        }ActiveScanningDlg processes the events like this:
        public void readingStarted(ReadingEvent evt) {
            //DO NOTHING
        public void readingFile(ReadingEvent evt) {
            jpbReadingProgress.setString(evt.getCurrentFileName());
        public void readingStopped(ReadingEvent evt) {
            Lookup.getDefault().lookup(MediaReader.class).removeListener(this);
            dispose();
        public void readingAborted(ReadingEvent evt) {
            readingStopped(evt);
        }This is an example on how the events are sent:
        private void fireReadingFile(ReadingEvent evt) {
            for (ReadingListener l : listeners) {
                l.readingFile(evt);
        }

    Hi,
    You have to check the Tolerance limits set for the following tolerance keys. In case if any where the limit is breached the systems blocks the Invoice as 'R - Invoice verification'. Please check the limits set for all these keys.
    AP - item amount variance (if you have activated the item check)
    DQ and DW - for Quantity variance
    PP - price variance with the order price
    ST - date variance
    VP - Moving average price variance
    Regards,
    Kathir

  • Anyone processed Customer ref contract using IDOC ORDERS05?

    Within CRM I can successfully create Sales orders using the IDOC type ORDERS05. However, the last thing that I need to do is ensure that any Customer reference contracts appear in the doc flow of the generated order, and this is where the difficulty begins...
    There are a number of BADI's available which allow me to populate the table contents, and I think I need to populate the CRMXIF_BUSTRANS_ITEM-DOC_FLOW itab with the Customer reference contract data, but the structure for this itab is so complicated. I was wondering whether anyone has performed the same function as I can't believe that I'm pioneering here. The Customer reference contract is being supplied by IDOC in segment E1EDP02 with a qualifer of 005.
    Any help would be greatly appreciated.
    Blue

    Hi,
    This issue is been resolved.
    One of my friend helped me with resolving this issue..
    Once the below mentioned configurations were done on SPRO, the Sales Order was created with reference to Contract and the Qty was reflected when tried to create a new Order referring the same contract.;
    u2022     SPRO --> SD  -->Sales  --> Sales Documents  --> Sales Document Header  --> Define Sales Document Types  --> Field : Outline agreement message; from blank to u201CBu201D.
    u2022     SPRO  -->SD  -->Sales  --> Sales Documents  --> Sales Document Header  --> Maintain Sales Document Types for AFS  --> Field : Outline agreement message; from blank to u201CAu201D

  • Stuck at delivery when processing customer downpayment

    Dear frindeds,
    I am processing downpayment flow and stuck at delivery step after completing sales order, invoice downpayment and posting downpayment.
    I was hit with error msg" Item category Z090 is not defined, so item 000010 will be disregarded". but when I check the configuration, the item category does exist.
    Please advise.
    Thanks,
    Linda

    Hi Linda,
    Check the determination for item category Z090..  This may be a possible reason.
    let us know..
    Regards,
    SB

  • Rogue Process - custom notification for users?

    Does ZEN 7 Rogue Process Management have the ability to customize the message the user receives when it kills the rogue process?
    I know AD GPO have this, but was wondering if ZEN 7 Rogue Process Mgmt did as well.
    IF not, then we'll have to use GPO.

    Shaun Pond,
    > and is against the license agreement in most cases
    It will certainly make the software unsupported, but any software
    vendor would have a hard time making a case against anyone doing such
    modifications in legally licensed software, unless the object of the
    modification is to break licensing rules.
    Thus, I would argue against using a resource editor because a vendor
    may refuse support, but as long as you are aware of that, then I see no
    problems.
    - Anders Gustafsson (Sysop)
    The Aaland Islands (N60 E20)
    Novell has a new enhancement request system,
    or what is now known as the requirement portal.
    If customers would like to give input in the upcoming
    releases of Novell products then they should go to
    http://www.novell.com/rms

  • Rebate Processing -  Value Difference -Verfication level and Sales  Volume

    Dear All ,
    We are using standard rebate process - Customer Rebates   and we have encountered the following issue .
    1. The Rebate agreement was created on 01/12/2010 with validity from 01/12/2001 , valid through 31/03/2010.The Rebate recipient was not activated for Rebate  in the month of DEC 2009 and was activated  on 15/01/2010 . We have executed VBOF  and found that the Accruals are calculated from 15/01/2010 till date which is 25,010 USD ( for the invoices which are created from 15/01/2010) but it is not taken into consideration of the invoices which are created in the month of December 2009.
    We have checked and calculated manually the accruals which is amounting to 35,575 USD for the period ( 01/12/2009 to 14/01/2010) . This accrual  amount is not updated for the agreement .
    Can any one give inputs on this issue.
    Thanks in advance .
    Regards
    Veera
    Edited by: veera PV on Mar 6, 2010 11:07 AM
    Dear All ,
    I have executed the VBOF  couple of times and the sales volume is updated correctly  now - 51,277.20 USD . but when i selected the agreement  and clicked on verfication level it is not showing up all the invoices   and the value shown is 43,025.10 USD . There is  difference of 8252.10.
    Now the issue is how do i get all the invoices in the verfication level.
    Can any one give inputs on this  .
    Thanks in advance to all of you.
    Regards
    Veera
    Edited by: veera PV on Mar 6, 2010 11:08 AM

    Hello,
    please check this thred Re: VBOF Issue related to updating Old Invoices after activating Rebate Check.
    Best regards,
    Ivano.

  • Business process&rebates

    sd folks,
                  plz provide documentation of business process in sd and rebates .
             i've seen sap help.but i can't under stantd. how 2 configure in system.plz provide config material.
                   it's
              msr

    Hi Raju.,
        REBATE AGREEMENTS:
    A special discount paid retroactively to a customer once he reaches sales volume in a given period of time.
    Structure:
    You can define the following data in a rebate agreement:
    • Validity period
    • Status (whether the agreement is released for settlement)
    • Rebate recipient (the party who receives the credit memo)
    • Currency
    • Method of payment (cheque, bank transfer etc)
    Data Defined In Condition Records:
    • Basis for rebate (customer, customer/ material, rebate group, etc)
    • Validity period (the validity must lie with in the validity of rebate agreement)
    • Cond rate
    • Material for settlement
    • Accrual rate
    • Other control data, such as pricing scale type
    Prerequisites for Rebate Processing:
    • Sales orgn: must be relevant for rebate processing
    • Payer: must be relevant for rebate processing
    • Billing type: (invoice, credit memo etc) must be relevant for rebate processing
    Material for Settlement:
    You may have to create rebates that do not depend on a material, but instead, e.g. on:
    • A Customer
    • A Customer Hierarchy
    • A Group of Materials
    You will then need to refer to a material for settlement. The system uses this material when you pay out the rebate. It does not matter which material type & mat application type you use.
    When you create the cond record with in the rebate agreement, the system automatically asks you to enter the no of material for settlement.
    Rebate based on Group of Materials:
    A rebate group consists of materials to which you want to apply the same rebate. You system administrator can define rebate group in Customizing for Sales according to the need o f the orgn.
    You can assign a material to a rebate group in the MMR: view- Sales, field- Rebate Grp. When you create a cond record, you must enter a settlement material.
    Rebate Agreement Types:
    Agreement Type Basis for Rebate Cond Type
    0001 Customer / Material % Rebate BO01
    Customer / Rebate Group % Rebate BO01
    0002 Customer / Material Quantity Dependent BO02
    0003 Customer Percent rebate BO03
    0004 Customer hierarchy Percent rebate BO04
    Customer hierarchy / Material Percent rebate BO05
    0005 Sales Volume Independent BO06
    SPRO- IMG- SD- BILLING- REBATE PROCESSING:
    • Define rebate agreements
    • Condition type groups
    o Define cond type groups
    o Assign cond types to cond type groups
    Maintain access sequence&#61607;
    Define&#61607; condition types
    Assign conditon types to conditon type groups&#61607;
    Maintain&#61607; pricing procedure
    o Assign condition type groups to rebate agreement types
    • Activate rebate processing
    o Select billing documents for rebate processing3
    o Activate rebate processing for sales organisations
    o Activate at customer level.
    Define Agreement Types:
    Copy & rename: 0002 & go to Details
    • From
    • To
    • Reverse accruals: flag it on
    • Manual Accrual Doc Type: Doc Type (R4) & Billing Doc Type: B4
    • Verification level: payer, material
    • Partial payment: Doc Type (R3) & Billing Doc Type: B3
    • Rebate credit memo: Doc Type (R1) & Billing Doc Type: B1
    Define Condition Type Groups:
    Copy & rename: 0002. Give the same code as given to agreement type.
    Assign Condition Type to Condition Type Group:
    In this activity one needs to assign the cond type from the pricing procedure to the cond type group found on the rebate agreement type. The sequence no column represents the fields in the cond table that determines what the system is to use as the basis for rebate. In this e.g., 1 determines that the cond type should use the fields customer & material. The cond type group 0002 will use pricing cond type BO02. Before assigning cond type to cond type group, you have to create a cond type.
    Cond Technique for rebate processing:
    Create cond table
    Maintain access sequence
    Define cond type: BO02 is the cond type used in pricing, copy & rename.
    Assign cond type to cond type group: BO02 to 0002
    Maintain pricing procedure: assign cond type BO02 to pricing proc, after total discount & before freight. Assign Subtotal: 7, Account Key: ERB, Accruals: ERU (keeping reserve money from customer money), & Requirement: 24 (rebate will get affected in billing doc & not in sales doc)
    The cond type BO02 must use cond class ‘C’- expense reimbursement.
    The rebate procedure in BO02: indicates if the cond is dependent or independent of sales volume
    The accruals correction proc indicates if accruals must be corrected when this cond type is accessed.
    Assigning Cond Type Groups to Agreement Type:
    Here you are presented with a list of agreement types as created in the system & you can assign the relevant cond type group
    Activate Rebate Processing: at
    • Sales orgn level: activate rebate processing for sales organisations
    • Billing Document: select billing doc for rebate processing
    • Customer: active rebate in CMD Sales Area Data, Billing Tab Page.
    Billing Document Types
    F2 Standard Invoice F1 Order Relate invoice
    BV Cash Sale B1, B2, B3, B4 Rebate invoices
    G2 Credit Memo L2 Debit Memo
    S1 Invoice Cancellation S2 Cancel Credit Memo
    IV Inter Company Sales
    Create Rebate Agreements: VBO1
    Easy Access- Logistics- SD- Master Data- Agreements- Rebate Agreements- Create
    Agreement type: 0002 & press enter. In the over view screen fill the following details:
    • Rebate recipient: payer no
    • Currency
    • Validity Period
    • Agreement Status: open
    • Then Go To Conditions Icon & Fill
    • Material, Rebate Amount, Accruals & save
    • Then create sales order, delivery, picking, goods issue & invoice
    • After this in  Go to Conditions (item).&#61614;order to see rebate in sales order cycle Go to: VF01 You can check rebate in VF01 before saving or else you can also see in VF02.
    Rebate Settlement: VBO2
    Change the agreement status to ‘B’ (released for settlement), while we are creating rebate agreement it is open, hence change from open to ‘B’.
    Rebate&#61472;&#61614;Rebate Payments &#61472;&#61614;Then, from main menu bar go to  Using Payment Screen. You will come across a check box (flag it and&#61472;&#61614;Settlement  save)
    Rebate credit memo no will be generated (Doc Type: G2)
    Go to VA02, give the rebate credit memo request no & remove billing block & save the document. Go to VF01 & create credit memo request (enter & save).
    Retroactive Rebate Processing:
    You can create rebate agreement for which the validity period start date lies in the past. The system takes in to account all the rebate relevant billing documents that were created between the validity start date & the date you created the rebate agreement. In addition to the credit memo request, the system creates a correction sales doc (type B2) automatically for this amount.
    Create the rebate agreement in the usual way. The system recognizes that the rebate agreement is retroactive.
    Deleting Rebate Agreements:
    In the change rebate agreement (VBO2) screen, enter the no of the rebate agreement that you want to settle. And press enter
    Select  Delete’, the system prompts you to confirm the deletion.&#61614;‘Agreement
    Press enter to delete the rebate agreement.
    Result: the rebate agreement receives status ‘C’ (settlement created)
    Automatically Renewing Rebate Agreements:
    Your system administrator is responsible for defining in Customizing for agreement type a calendar for extending rebate agreements. You can set for each rebate agreement whether it is to be renewed automatically or Reactivate or Remove in the change rebate&#61472;&#61614; Rebate Calendar &#61614;not. Select Extras mode.
    Renewing Rebate Agreements:
    • Enter the screen rebate agreements: renewing: Logistics- SD- Master Data- Agreements- Rebate Agreement- Extend & Choose Enter
    • The system issues a list of all rebate agreements which were renewed and which the system could not renew are listed in the log.
    REWARD if helpull
    Thanks & Regards
    Narayana

  • What is the pupose of  rebate agrrement? configuaration process

    what is the pupose of  rebate agrrement? configuaration process

    Hi Deva,
    As he rightly said, you need to understand the basic sd module functionlity, else make a small search in forum.
    I dont want to dispoint you this time, going forward do it. For your reference find the complete config process of rebate.
    What do you mean by Rebate: - Rebate is a special kind of discount, which is paid retroactively to a customer once he achieves or reaches the sales volumes, in a given period of time.
    Rebate agreement: - A Rebate agreement is an agreement between the business and a customer. The rebate is only relevant if the customer purchases the required sales volume. In rebate agreement, you specify who receives the rebate payment and on what criteria rebate is based. Ex. Customer, customer and material etc,.
    Rebate agreement type: - The rebate agreement type determines which data the system is to automatically propose for rebate agreement.
    Structure:
    You can define the following data in a rebate agreement:
    •     Validity period
    •     Status (whether the agreement is released for settlement)
    •     Rebate recipient (the party who receives the credit memo)
    •     Currency
    •     Method of payment (cheque, bank transfer etc)
    Data Defined In Condition Records:
    •     Basis for rebate (customer, customer/ material, rebate group, etc)
    •     Validity period (the validity must lie with in the validity of rebate agreement)
    •     Cond rate
    •     Material for settlement
    •     Accrual rate
    •     Other control data, such as pricing scale type
    Prerequisites for Rebate Processing:
    •     Sales orgn: must be relevant for rebate processing
    •     Payer: must be relevant for rebate processing
    •     Billing type: (invoice, credit memo etc) must be relevant for rebate processing
    For performance reasons, you should deactivate rebate processing if it is not necessary.
    Material for Settlement:  – In case of customer rebate where there is no material linked, a dummy material is give as material for settlement.
    You may have to create rebates that do not depend on a material, but instead, e.g. on:
    •     A Customer
    •     A Customer Hierarchy
    •     A Group of Materials
    You will then need to refer to a material for settlement. The system uses this material when you pay out the rebate. It does not matter which material type & mat application type you use.
    When you create the cond record with in the rebate agreement, the system automatically asks you to enter the no of material for settlement.
    Manual accruals: – Instead of posting accruals from the billing documents, manually we can post accruals through the debit memo. If you activate this field if you want to be able to post manually for this agreement type.
    Reverse accruals:- Whatever manual accruals we have given can be reversed through the reverse accruals. Mark this field if you want accruals to be reversed when a manual payment is made for a rebate agreement of this type. The system uses reverses accruals for the amount of the manual payment. If the cumulative accruals are not sufficient, the system reverses the accruals amount, which exists.
    Relationship to Pricing
    •     Rebates differ from other kinds of discounts in that they are based on sales volume over time and are paid retroactively.
    •     However, the system processes rebates in much the same way as other kinds of pricing elements.
    •     Rebate data is saved in condition records. 
    •     Controlling for rebate processing is carried out via condition types, pricing procedures and access sequences.
    •     This control data is defined in Customizing for Sales and Distribution.
    Rebate based on Group of Materials:
    A rebate group consists of materials to which you want to apply the same rebate. You system administrator can define rebate group in Customizing for Sales according to the need o f the orgn.
    You can assign a material to a rebate group in the MMR: view- Sales, field- Rebate Grp. When you create a cond record, you must enter a settlement material.
    Rebate Agreement Types:
    Agreement Type     Basis for Rebate          Cond Type
    0001     Customer / Material     % Rebate     BO01
         Customer / Rebate Group     % Rebate     BO01
    0002     Customer / Material      Quantity Dependent     BO02
    0003     Customer     Percent rebate     BO03
    0004     Customer hierarchy     Percent rebate     BO04
         Customer hierarchy / Material     Percent rebate     BO05
    0005     Sales Volume Independent          BO06
    SPRO- IMG- SD- BILLING- REBATE PROCESSING:
    •     Define rebate agreements
    •     Condition type groups
    o     Define cond type groups
    o     Assign cond types to cond type groups
    &#61607;     Maintain access sequence
    &#61607;     Define condition types
    &#61607;     Assign conditon types to conditon type groups
    &#61607;     Maintain pricing procedure
    o     Assign condition type groups to rebate agreement types
    •     Activate rebate processing
    o     Select billing documents for rebate processing3
    o     Activate rebate processing for sales organisations
    o     Activate at customer level.
    1. Define Agreement Types:
    Copy & rename: 0002 & go to Details
    •     From
    •     To
    •     Reverse accruals: flag it on
    •     Manual Accrual Doc Type:           Doc Type (R4) & Billing Doc Type: B4
    •     Verification level: payer, material
    •     Partial payment:               Doc Type (R3) & Billing Doc Type: B3
    •     Rebate credit memo:               Doc Type (R1) & Billing Doc Type: B1
    2. Define Condition Type Groups:
    Copy & rename: 0002. Give the same code as given to agreement type.
    3. Assign Condition Type to Condition Type Group:
    In this activity one needs to assign the cond type from the pricing procedure to the cond type group found on the rebate agreement type. The sequence no column represents the fields in the cond table that determines what the system is to use as the basis for rebate. In this e.g., 1 determines that the cond type should use the fields customer & material. The cond type group 0002 will use pricing cond type BO02. Before assigning cond type to cond type group, you have to create a cond type.
         Cond Technique for rebate processing:
    •     Create cond table
    •     Maintain access sequence
    •     Define cond type: BO02 is the cond type used in pricing, copy & rename.
    •     Assign cond type to cond type group: BO02 to 0002
    •     Maintain pricing procedure: assign cond type BO02 to pricing proc, after total discount & before freight. Assign Subtotal: 7, Account Key: ERB, Accruals: ERU (keeping reserve money from customer money), & Requirement: 24 (rebate will get affected in billing doc & not in sales doc)
    •     The cond type BO02 must use cond class ‘C’- expense reimbursement.
    •     The rebate procedure in BO02: indicates if the cond is dependent or independent of sales volume
    •     The accruals correction proc indicates if accruals must be corrected when this cond type is accessed.
    4. Assigning Cond Type Groups to Agreement Type:
    Here you are presented with a list of agreement types as created in the system & you can assign the relevant cond type group
    5. Activate Rebate Processing: at the following levels.
    •     Sales orgn level: activate rebate processing for sales organisations
    •     Billing Document: select billing doc for rebate processing
    •     Customer: active rebate in CMD Sales Area Data, Billing Tab Page.
    Billing Document Types
    F2     Standard Invoice     F1     Order Relate invoice
    BV     Cash Sale     B1, B2, B3, B4     Rebate invoices
    G2     Credit Memo     L2     Debit Memo
    S1     Invoice Cancellation     S2     Cancel Credit Memo
    IV     Inter Company Sales          
    NOTE: - You cannot activate Rebates for Billing document type – F5 & F8, since they are proforma invoices.
    Create Rebate Agreements: VBO1
    Easy Access- Logistics- SD- Master Data- Agreements- Rebate Agreements- Create
    Agreement type: 0002 & press enter. In the over view screen fill the following details:
    •     Rebate recipient: payer no
    •     Currency
    •     Validity Period
    •     Agreement Status: open
    •     Then Go To Conditions Icon & Fill
    •     Material, Rebate Amount, Accruals & save
    •     Then create sales order, delivery, picking, goods issue & invoice
    •     After this in order to see rebate in sales order cycle Go to: VF01&#61614; Go to Conditions (item). You can check rebate in VF01 before saving or else you can also see in VF02.
    Rebate Settlement: VBO2
    •     The system uses the accumulated amounts in the rebate agreement to create a rebate settlement.
    •     The system generates a rebate credit memo request for the rebate payment amount specified.
    •     There are 3 statuses available for rebate agreements 
    1.     Status A refers to an open rebate agreement.
    2.     Status B means the rebate is released for settlement.  
    3.     Status C means you have actually executed the settlement. The System creates a credit memo request for the accrual amount.
    •     You can display the sales volume and drill-down in the rebate agreement. 
    •     You can carry out a final settlement for the rebate agreement either: 
    a.     Manually
    b.     Automatically
    c.     In the background (batch programs: RV15C001 and RV15C002)
    •     Accruals are reversed as soon as the rebate agreement is settled by credit memo.
    Process of Rebate settlement:
    •     Use VBO2 and type in the agreement Number. Change the Agreement Status to B and click on Final Settlements->Automatic. On doing so, a Credit Memo Request gets created.
    •     Status is set to C. Save it.
    •     A credit Memo Request Number is generated.
    •     Go to VA02 and type in the Credit Memo Request number generated. Remove the Billing Block and Save it.
    •     Use VA02 to go to Sales Document and Click on Billing. On Saving it, the Credit Memo Request is now Billed
    •     Go to VBO3 and see the Agreement Status. It would have been set to D, which means that final settlement of agreement has been carried out.
    Important:-
    1. 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.
    2. 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. The system can use the sold to party or ship to party as we as payer as the rebate recipient. You cannot use alternative partner as the rebate recipient, such as alternative payer for the CMD of the sole to party.
    Reward points,
    Vamsi P

Maybe you are looking for