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.

Similar Messages

Rebate Agreement saved even if the cust. or payer is not active for Rebate

Dear All,
In my Rebate scenarion, Customer is Payer. When i an creating the Rebate Agreement & entering the Payer number , system is giving the warning message but allow me to create the Rebate agreement.
I want system to restrict to create Rebate agrrement if the payer or customer is not entitled for rebate.
Thanks to All

There is no IMG setting for this message. I suggest you should take help from ABAPer to change the message type from warning to error.

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

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

Dear all,
I have a problem, please kindly help me on my issue.
For the rebate process, my client requires for their customers once the time period is over he dont want to raise the credit memo reuqest on the behalf of credit memo client want to replace the goods at free of cost to their customers.
Kindly help me in this issue

Hi Ashwini,
Rebate Agreements are created for a Customer, the Partner role of the Customer can be Payer or Sold To, depending on the document where the Rebate is calculated.
Rebate Agreements are governed by Agreement Types.
Rebate Agreements can be created using the menu path-
Logistics -> Sales and Distribution -> Master Data -> Agreements
-> Rebate arrangement -> Create
If you need more details, Please give ur mail id. I can send you a document to your mail.
regards,
Raj

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, Open Accrual

Hi All,
In our organization, we use rebate agreement extensively. Most of the agreements are for one year validity period.
My problem is that when we finally settle the agreement and issue credit memo for final settlement some accrul is left open. Generally we make sure that at the time of settlement the accrued amount is equal to the final settlement value. This is done by doing the manual posting of accrual.
In case some agreement has some open accrual, when Agreement are in "C" or "D" status, how can i make the open accrual as "zero". this is also due to audit pupose we don't want any open accrual against an agreement.
Thanks in Advance.
Deepak

Thnaks a lot for the message.
First, what are system calculation rules ?
Second, Suppose now there are some issue bcos of which the accrual are open than what is the way to eliminate the accrual from the agreement once it is in C/D status.
Thanks

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

Cannot perform final settlement of a rebate agreement

Dear experts,
When I try to perform final settlement of a rebate agreement, error "Final settlement is not possible. (There are still open documents)" encountered.
Is it due to there are some open billing documents related to the payer of the agreement?
If yes:
I have checked there is a billing document (cancel of credit memo) not yet released to account, which created half a year before.
And it is not possible to open the financial period back to half year ago.
Is there any way to delete this billing document?
Thanks.

Hi
So as the system is giving error , just run VBOX to update the old documents
As you said that there are open documents then just either reverse those documents and then do final settlement or just forward it to FI those open documents
Another option is go to VBO2 and maintain manually the agreement status as B and save the rebate agreement then the credit memo for final settlement will be released
Regards
Srinath

Rebate Agreement Accruals

I have this peculiar requirement.
We are using Rebate Agreements for Sales Volumes with Rebate Condition Scales.
We should NOT be paying the customer through the AR credit memo, because of Legal Issue.
So we have developed a nice solution, which includes not to post any Settlement Credit Memos (by removing the account determination). But to settle it through AP.
Doing this has left us with a lot of Accruals during sales.
I need help, in how to reverse the Accruals?
Thanks
Omer

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

Maximum Royalty check in during Create Rebate Agreement( vbo1 transaction)

Hi experts,
There is need to implement a maximum royalty check for a particular material.
This maximum percentage is stored in the material master itself.( Say 10 %)
When a Rebate Agreement is created / changed a particular amount is entered against a pricelist.
Now the check to be implemented is that the amount entered against each material should not exceed the maximum percentage defined for that material.
Additionally this check should handle the scale check.
Is this check can be done through a BADI / Exit or functionally.
Any idea on how to handle this would be of great help.
Regards,
Gowri

Hi All,
I am closing the trend. I was able to achieve the above check with the help of the badi
SD_COND_SAVE_A.
Gowri

Rebate agreement with customer hierarchy

Hi,
I want to use customer hierarchy for customer rebates where in the accrual rate with scales shall be maintained only the high level customer. Invoice values of all the subordinate customers should e accrued using this rebate agreement.
Have learnt about extended rebate agreement functionality wherein such a scenario can be adopted.
Looking for a solution immediately to meet the week end deadline for POC.
Regards,
Rajesh Mohapatra

Thanks Veera !!
In this case my rebate receiptant is one only.
I am trying to use a customer hierarchy node (scaled down customer code w/o partners, recon account etc.) and made it relevant for Rebates & Price determination.
All the customers in the hierarchy are also relevant for Rebates.
But the condition record maintained with hierarchy node is not getting picked up the billing document as system is looking for the subordinate payer instead of the hierarchy node.
Not using the same node as Rebate Receiptant. Incase of using wrt the below link, am getting error as "Customer for function PY may not have account group 0012".
Ref : http://help.sap.com/saphelp_ides/helpdata/en/5d/363ec3583f11d2a5b70060087d1f3b/content.htm
Regards,
Rajesh Mohapatra

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

Rebate Agreement / Billing

Is it possible to create Rebate Agreement in crm and Billing in ecc? also with an eye to the rebate settlement..

Hi Manish
System will ask to recreate the billing index if any billing documents are there for that sales organization.So you have to run the report RV15B001 which will be for the payer also.
It will update the old billing documents of that sales organization also
Regards
Srinath

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 Agreement against Payer (HeadOffice)

Similar Messages

Maybe you are looking for