cancel
Showing results for 
Search instead for 
Did you mean: 

Rebate Configuration

Former Member
0 Kudos

Hi all,

I am new to SAP. I am having a problem setting up rebate. Could anyone give me step by step configuration for rebate

Thanks

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi

check this link

http://www.erpgenie.com/publications/saptips/052005.pdf

Rebates

u2022 Rebates are special kinds of discounts that are going to be paid to the customers.

u2022 Rebates are accumulated over a period of time based on quantity sold or amount of goods sold.

u2022 They are treated as u201CExpense Reimbursementu201Cwhen it comes to classification in SAP.

u2022 They are credited to the customer- payer based on certain sales volume within certain specified time period.

u2022 In order to configure rebates in SAP, following settings need to be done in configuration settings:

1. Check u201CRebate Processing Activeu201D should be activated while defining the sales Organization.

2. Check u201CRebatesu201D should be activated for Customer-Payer.

3. Check u201CRelevant for Rebatesu201D should be activated while defining the billing document type Ex.: F2.

1. Define Agreement Types:

Menu path: IMG / Sales & Distribution / Billing / Rebate Processing / Rebate Agreements / Define Agreement Types / Define Agreement Types

There are 5 standard agreement types:

u2022 0001 u2013 Group rebate

u2022 0002 u2013 Material rebate

u2022 0003 u2013 Customer rebate

u2022 0004 u2013 Hierarchy rebate

u2022 0005 u2013 Independent of the sales volume.

We are going to copy the 0002 and create our own material rebate u2013 ZS02. And we will go to details and see the following screen shot.

The rebate agreement type you specify determines which data the system automatically proposes for the corresponding rebate agreement. For example, the system can propose

u2022 which condition types you can use in an agreement

u2022 which validity period the system automatically proposes for an agreement

u2022 which status is required before an agreement can be processed for payment.

u2022 which rebate agreement types are defined in Customizing for Sales and Distribution.

A rebate agreement is an agreement with the customer to which condition records are allocated. This guarantees that rebate agreements, like price agreements, depend on a large number of different criteria (for example, customer, material, rebate group) and can be handled in various ways. Different calculation types and scale bases can be used. Rebate agreements can also be entered and changed later, that is, after the start date of the validity period.

When maintaining and configuring rebate agreements, you have to consider the following:

u2022 Agreement types

u2022 Condition type groups

u2022 Number ranges

The description of the fields is given below:

Proposed Valid from Dates:

u2022 Specifies the beginning validity date that the system automatically proposes when you create a rebate agreement of this type.

u2022 If you want the system to propose the current date, leave the field blank. Otherwise, enter one of the values predefined for your system.

Proposed Valid to dates:

u2022 Proposed value for how long a condition should remain valid.

u2022 The system proposes this value for the Valid to date when you create condition records.

Payment Method:

u2022 Assign the payment method that is going to be used for rebate settlement. Ex.: cash, check etc.

Default Status:

u2022 Specifies the default status that the system automatically proposes when you create a new rebate agreement.

u2022 Examples

o If, for example, you want to pre-release all your rebate agreements so that they can be processed in batch after their validity periods expire, you can assign the status "B" as the default. The agreements need not be released individually released for settlement.

o If, on the other hand, you want to check each rebate agreement before it is settled, then you can leave the field blank

Condition Type Group:

u2022 Specifies a grouping of condition types and condition tables for use during rebate processing.

u2022 As a rule, the condition type group consists of only one rebate condition type. However, if your rebate processing requires it, you have the following possibilities:

o You can assign more than one condition type to a group

o You can enter the same condition type in a group more than once and use different condition tables, or key combinations, for each instance

u2022 This allows you to break down the rebate settlement within an agreement. Using more than one condition type within a group would allow you to post, for example, part of a rebate settlement to an account for advertising costs and part to an account for administrative costs.

Verification Level:

u2022 The value of this field specifies how the rebate agreements totals should be displayed.

Different Validity Periods:

u2022 Controls whether condition records within a rebate agreement must have exactly the same validity period as the agreement itself.

u2022 If we need to vary we check this field.

Manual Accruals Order Type:

u2022 Assign Sales document type that system automatically proposes when the user performs manual posting for accruals. Ex.: R4/B4 - Rebate Req. for Manual Accruals.

u2022 If the business agreed to pay Rs. 2000/- to the customer for displaying the product in the showcase within specified period, then the business has to post manual accruals in rebate agreement screen. Then the system automatically creates credit memo request by using document type R4/B4 which was assigned here.

Manual Accruals:

u2022 This indicator specifies that manual accruals can be posted for this agreement type.

u2022 It is useful to be able to post accruals manually in the following situations:

o Lump sum payment processing

o Manual accruals correction

u2022 The manual accruals function allows you to carry out the following for a particular condition record in a rebate agreement:

o Build accruals

o Reverse accruals partially or in full

u2022 If you want manual accruals then we check this field.

Arrangement calendar:

u2022 The arrangement calendar defines the end of the validity period of rebate arrangements and controls their extension.

Payment procedure:

u2022 The value of this field specifies whether manual payments are allowed or not allowed for these agreement types, if they are allowed then to which extent manual payment should be allowed.

u2022 When manual payment is carried out, the system automatically creates a credit memo request for the specified amounts. When the system carries out final settlement, all partial payments are taken into account.

Partial Settlement:

u2022 Assign sales document type that the system automatically uses for partial settlement. Ex.: R3/B3 u2013 Partial rebate settlement request.

u2022 The customer requests partial settlement of a rebate agreement. You specify the amounts to be paid on the manual payment screen in the rebate agreement. The system then creates a credit memo request for these amounts using the document type specified here. The request must be approved before the actual credit memo can be created.

Reverse Accruals:

u2022 This indicator allows the system to reverse accruals automatically at the time of settlement.

u2022 The system reverses accruals for the amount of the manual payment. If the cumulative accruals are not sufficient, the system reverses the accruals amount which exists.

Settlement Periods:

u2022 Define factory calendar in which the periodic settlements can be defined and assigned to the rebate agreement.

Final Settlement:

u2022 Assign the sales document type that the system automatically proposes for final settlement. Ex.: B1 u2013 Rebate Credit memo request.

Minimum Status:

u2022 Set the minimum status for rebate agreement for final settlement by which the system or user can understand the status of the rebate agreement. Ex.: B u2013 Agreement Released for Settlement.

u2022 Minimum value of the rebate agreement for final settlement

u2022 Specifies the minimum status that a rebate agreement must have before the settlement can be calculated.

u2022 During the processing of a final settlement, the system checks whether the rebate agreement is assigned the minimum status.

Correction:

u2022 Assign Sales Document type that the system automatically uses for correcting rebates. Ex.: B2 u2013 Rebate Correction request.

2. Condition technique for Rebate Processing:

Menu path: IMG / Sales & Distribution / Billing / Rebate Processing / Condition technique for rebate Processing

a. Create condition table:

Here we create the condition table for the rebate processing. Ex.: 001 u2013 Customer/Material.

b. Maintain Access Sequence:

Here we have a look at the access sequence that we are going to use. Ex.:BO02.

c. Define Condition Types:

Here we look at the condition Type for the Rebates BO02.

u2022 Access Sequence: BO02.

u2022 Condition Class: C u2013 Expense Reimbursement.

u2022 Calculation Type: C u2013 Quantity.

u2022 Plus/Minus: X u2013 negative.

u2022 Scale basis: C u2013 Quantity scale.

u2022 Check value: A u2013 Descending.

u2022 Rebate Procedure: Blank u2013 Dependent on Sales Volume.

u2022 Rebate - Accruals Correction Procedure: blank u2013 Always Corrected.

d. Maintain Pricing Procedure:

Here we go our pricing procedure u2013 ZSAA01 and include the condition type BO02 along with the discount condition types.

Important settings:

u2022 Requirement: 24 u2013 Only in billing document.

u2022 Subtotal: 7

u2022 Acct. Key: ERB.

u2022 Accruals: ERU

3. Condition technique for Rebate Processing:

Menu path: IMG / Sales & Distribution / Billing / Rebate Processing /Account determination for rebates.

Here only thing interests us at this time is to u201CAssign G/L accountu201D.

We will then select the u201CAccounting Keyu201D

Go to u201Cnew entriesu201D and make the entries as shown below.

With this we have completed the account determination for rebates.

4. Activate Rebate Processing:

Menu path: IMG / Sales & Distribution / Billing / Rebate Processing / Activate Rebate processing.

To activate rebates 3 settings are done which distributed between Functional consultants as well as end users:

u2022 Functional Consultants activate rebates at Sales organization Level and at Billing Document level.

u2022 End users activate Rebates at the customer-payer.

a. Select billing documents for rebate processing:

b. Activate rebate processing for sales organizations:

These 2 settings are to be only done if we have not done before at the sales organization definition level and billing document definition level. If we do it initially then it will be reflected here.

5. Create Rebate Agreement:

Menu path: SAP Easy Access / Logistics / Sales and Distribution / Master data / Rebate Agreements / Rebate Agreement / Create.

T. Code: VB01

Press enter and following screen is generated, enter the values as shown.

Press u2018Copyu2019 and the following screen get generated.

Specify the Rebate Recipient which can be sold to party or Customer u2013 Payer.

Click on the u201CConditionsu201D and following screen will be generated.

We can maintain this condition record with u201Cscalesu201D also.

Sales Order:

We go to VA01 and raise the sales order using the Customer that we assigned above and when we go to the conditions tab at the Item Level, we will not see the condition type for rebate BO02. This will be only seen in the Billing document u2013 F2 because of the requirement u2013 24.

We check the incompletion log and save the document.

Delivery:

We go ahead and create delivery in VL01N as we do in sales order and do PGI.

Billing Document:

We go to VF01 and create a billing document with reference to the delivery document number. We enter the billing document and go to Item level and we will see that the BO02 condition type will get activated.

So rebate has to be 50 * 8000 = 400000

Checking Sales Volume:

We go to T.Code: VBO2, to check the sales volume.

This Transaction code is to change the u201CAgreement Typeu201D, we enter the Agreement number that we created before and Press enter.

u201CThe Sales Volume for Agreement 38 is not currentu201D will be generated.

Report Run:

We go to T.Code: SE38 and run the report program SDBONT06.

 Specify the Program name and click on u201CExecuteu201D.

 Enter the u201CAgreementu201D number and click on u201CExecuteu201D.

 Click on Add Up values.

Then we again go back to the T.Code: VBO2

Then we click on Sales Volume Icon , following screen will be generated.

We can see that the rebate is calculated as Rs. 400000.

Then we click on the Verification Level, following screen will be generated.

We go back and click on the Pay Icon , following screen will be generated and we enter the amount here.

We save it and Credit memo Request Number will be generated.

We go to VF01 and raise a Credit Memo.

regards

Answers (4)

Answers (4)

Former Member
0 Kudos

Thanks prashant, your answer was useful

Former Member
0 Kudos

Dear Vishal,

Pls go through the following link, it will explain you.

http://www.erpgenie.com/publications/saptips/052005.pdf

Also go through the following link

http://www.saptechies.com/how-to-create-and-process-rebate-agreement/

Thanks

former_member184555
Active Contributor
0 Kudos

Hi

Please check the below link for a pdf document on Rebate processing..

http://www.erpgenie.com/publications/saptips/052005.pdf

Thanks,

Ravi

Former Member
0 Kudos

Hi Vishal,

Here is the link which gives you all details about rebate configurations..

http://help.sap.com/saphelp_46c/helpdata/en/5d/363eb7583f11d2a5b70060087d1f3b/content.htm

http://www.erpgenie.com/publications/saptips/052005.pdf

Regards,

Raghav