Vendor Rebate process and settings
This document covers –
Overview of SAP Vendor Rebates and Process Flow
Master data, Transaction data and Configuration settings
What are the inputs required to setup vendor rebate functionality
Options we can leverage through SAP Vendor Rebate
Vendor rebate overview
These discounts are stored in the system as “Rebate arrangements”
These Rebates arrangements are having validity and we can extend the validity of such an arrangement to cover a longer time-span or “until further notice”. For example, an arrangement created for one calendar year can be automatically replaced by a new, identical one that is valid for the following calendar year.
Levels for Vendor Rebates
In this case rebate arrangements are created based on purchasing organization/vendor/material/company code combination. But Purchasing organization should be assigned to company code.
Plant based rebates –
In this case rebate arrangements are created based on purchasing organization/vendor/material/company code combination. In this case it is not required to have Purchasing organization assigned to company code. We need to use this rebate type as in EL purchasing organizations are assigned to plant.
Conditions and Discounts
During a certain period if purchase value of certain materials exceeds the defined limit then discounts will come into picture.
Quantity based conditions (Scales) –
During a certain period if purchase quantity of certain material exceeds the defined limit then discount will come into picture.
These discounts are in the form of percentage, quantity or fixed value etc. depending on
Calculation type in condition type and business requirements
Note: Apart from Value and quantity scales there are other options as well e.g. Gross weight, Net weight, volume, distance etc.
Inputs for Vendor Rebate Arrangement
Master data change – Vendor Master Update
Master data New– Rebate Arrangement – Overview (Screen 1) (MEB1)
Master data New– Rebate Arrangement – Condition record (Screen 2)
Condition record for rebate condition types (A001) –
Transactional data – Business volume comparison (MEU2)
User can compare business data with vendor and make changes in business volume figures before settlement.
Transactional data – Rebate settlement (MEB4)
Vendor rebate options –
Rebate Arrangement at Vendor/multiple materials – If a vendor is supplying range of materials belonging to different material group for different plant then only one rebate condition record needs to maintained for range of materials.
Option of quantity scale vs. value scale – Option to have rebate scales based on quantity procured during specified period.
AP payment procedure to vendor in case of rebates – Payments to the vendors are made by deducting rebate amount from total due.
Message to vendor about settlement – 1. Rebate Arrangement creation 2. Rebate settlement run
Required Configuration data
1. Assign rebate condition type to rebate agreement type
2. Number range assignment to rebate agreement type
4. Condition type marked with “Accruals” – This is required to get rebate condition type with value in PO as statistical condition type.
Hi Sanjay, nice documentation on rebate .
An info you may include is :
You can create your own rebate conditions & assign them in the pricing procedure ,
also you can have two rebate conditions types active i.e in case vendor rebate is applicable for particular amount as well as for quantity...
A000 is already present in the pricing procedure.
Good piece of work on rebate.
One question: Shall We have to include rebate condition type in our pricing procedure.
I am testing the screnio inspite of maintaining the above step. Rebate condition type not reflecting in condition of PO.
Appreciate your feedback.
I am Sagar not Sanjay
Answer to your question -
You have to include condition type in your pricing procedure.
And do remember to mark Accruals check box in condition type. Then only it will appear in PO.
My aplogies. Thanks for help.
Thanks for sharing .. It is valuable in MM and similiar with SD
Please maintain menu path/T-Code against configs (like Custom Agreement Type, Assign rebate condition type to rebate agreement type etc.) described.
Very good information. Hoping someone can help. We have an arrangement with conditions at a vendor material group level. In trying to perform a business volume comparison, the vendor is paying a rebate on a material group that we did not accrue against. Probably a master data issue, and we have a condition record created for the material group being paid against, (again, just no actual accrual), but I am unable to enter the vendor business volume because our condition is zero. Documentation says this should be doable, but until now no success.
Anyone experience this and come up with a solution?
how can I get a rebate condition to work for
a rebate applicable at
1) material level first
2) material group level - only if rebate at material level is not found.
I want to use just ONE rebate condition
however using one access sequence with 2 steps does not work.
(the material rebate condition works;
the material group level brings up the % rebate however the value is null on the condition record on the pricing schema).
Using two separate conditions cannot be used on one rebate agreement type on the config setting.
What options do I have?
Hi Sagar & others,
I am new here but I have following question regarding this vendor rebates.
I created a rebate-agreement on March 4th 2015, but the agreement actuall already runs from 1jan-31dec, so how can I still include the finished and settled po's from 1jan- now ?
If not possible to include, I will never reach the agreed targets. Because the amount is still zero, it is also not possible (yet) to manually overrule the amount in MEU2
Any info is appreciated,
Moderator message: Please post general questions in the forum. Only questions specific to content of this document should be posted in the comment section here.
Very good Document.....
I am facing some challenges in partner determination in rebate agreement. I did set up in Partner determination for vendor rebate & assign partner schema to agreement type, still facing error ? "condition granter XXXX is not maintained for comp code XXX"
is their any other setting is require ?