Problem in rebate agreement type 0005

Hi
I created a rebate agreement of type 0005 and maintained amount Rs 5000 for a customer
while creating billing document the condition type BO06 was determined in the billing doc but without anu value
the analysis shows that condition record has been found
I have checked the pricing date and all other parameters but still not able to figure out the mistake
Kindly help me in this regard
Thanks and Regards
SunilIyer

Hi SunilIyer
If you are working with the standard rebate agreement 0005 and condition type BO06
You will be working with a sales independant agreement and a fixed amount condition.
For a fixed amount there is no posting of accruals because it is already known what the
liability is in the agreement.
If accruals are required most customer's would post a manual accrual from the agreement
for the fixed amount of the agreement condition.
In your billing document you will see the Bo06 condition is determined and the agreement is
known but the condition value will always be 0.00 for a fixed amount.
This is correct and expected
Hope this helps explain the system behaviour
Kind regards
Brian

Similar Messages

Rebate agreement types

Dear all,
1. What are sceanrios in which we use agreement type 0005(Sales independent volume}?
2. How to create the record for VBO1 for customer /volume rebate(0001) as the condition inforamtion is not available. . Here the condition type group is assigned to two conditiontables(First one is customer and material and the second one is Custome/Volume rebate. Every time it is taking the first condition by default?
Regards,
Keyur. p

Hi.
If you are using 0005(Agreement type )has a condition type group 0005 with one condition type BO06 has one standard table in the acesssequence thas the fileld customer since it is independent of the sales volume..But as you said that you have 2tables customer/materail/indepent volume type linked to this condition type correspondingly to the rebate agreement type.This means you need to check if the exclusive indicator is not checked in the acessseuqence for the first as it allows to only get the default value when you make the condition record.
This can be one of the reason why it is displaying the default value when you make the record.
Please check this out
Thanks
Saurabh

Problem with Rebate agreement

We have a problem with Rebate agreement settlement.
Generally when the finall settlement of Rebate is completed ( with status D - D means final settlement ), the liability should be zero. However, after we made final settlement, still some amount is showing as liability when we looked at the sales volume of the rebate agreement.
Please help us to fix the issue.
Thanks in advance for the help.

Hello,
Please review the Note 392683.
Regards,
Raghavendra YN

Problems in Rebate agreement

The problem is that After final rebate settlement there is still open accrual.
And in another agreement the p&l effect in SAP is much more higher than the difference of accrued and paid amounts.
I revised already the agreement conditions and I didn't find out anything....
Where can be the Problem?
Thanks in advance and regards
William

Dear Tirumalasetti,
This may be due to there is holiday in that calendar on the date of the Rebate agreement period end date.
So please change the Rebate agreement period end date or change holiday to working day in that calendar on that date.
I this will help you,
Regards,
Murali.

Problem with Rebate Agreement Sales Volume

Hi,
I executed the rebate recalculation via SDBONT06 for a total of 93 agreements on 04.08.2014 and therefore the sales volume was updated and there was no message in VBO3 as well.
But today when i am checking the agreements all of them are showing message "Sales Volume is not Current"
I have gone through all the threads on SCN for this.
there have not been any changes in payer, sales org, agreement or agreement conditions.
I dont see any customizing also changed.
Please help asap as to what can be the reason for this message all of a sudden.
Regards,
Aayush Jain
SAP SD Consultant

Hi Aayush
When you rebuild the rebate index table VBOX all agreement conditions will be set to retroactive again. I guess someone has run RV15B001 on your system in the meantime ?
The "Sales Volume is not current" message is issued when the rebate condition is flagged as retroactive (KONP-KSPAE) SDBONT06 resets that when it has completed a successful update
So just run SDBONT06 again, all of you 93 agreements are updated so the report will only reset the KONP-KSPAE field on the conditions in that case.
Hope it helps you further
Kind regards
Brian

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

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 scales

Hi,
We in our company has implemented rebate agreements. We have monthly offtake rebate as one of the rebate agreement type. The scales are as
0-50 nil
51-100                 Rs. 375/MT
101-200                Rs.425/MT
201-500                Rs. 500/MT
> 500                     Rs. 600/MT
Total billed qty for a month is 250 MT.
Currently it is calculating as 250MT*Rs.500 = Rs. 125000 as the rebate amount.
But the system should calculate as below
first      50MT -    50MT*0 = 0
second 50MT          50*375 = 18750
for 100 MT         100*425 =42500
last 50 MT            50*500 = 25000
total rebate amount = Rs.86250
I tried with scale type D - graduated to-interval but it is not accepting this scale type.
Please help me to solve this problem.

Hi,
Scales are ignored when calculating accruals, but will be calculated at rebate settlement.
You can check the manual on rebate set up and management that rithvika posted in another thread:
Rebate Scales - Graduated to Interval scale
Or OSS note 392711
https://service.sap.com/sap/support/notes/392711
best regards
Michael

Rebate Agreement Calendars

Our business has five main Rebate Agreement (Arrangement) Calendars :
October to September
July to June
April to March
August to July
January to December
There are additionally, some other validity periods that we might use, such as six-monthly, however the above five calendars probably account for 80-90% of our Rebate Agreements.
The problem :
We want to be able to use Rebate Agreement Calendars to automatically extend Agreements for a further 12 months. However, my understanding is that each Rebate Agreement Type is only designed to work with a single Calendar, therefore we would have to create a further four copies of an Agreement Type, each with a different calendar assigned. E.g. :
RA Type Calendar Description
ZR01 R1 October to September
ZR02 R2 July to June
ZR03 R3 April to March
ZR04 R4 August to July
ZR05 R5 January to December
and the same for all other Agreement Types we use. This would result in a ridiculous amount of duplicate/needless configuration.
We have unlocked the screen field to be able to change the Arrangement Calendar in VBO1/VBO2. However, we still have to set a default Calendar in config, via txn VB(2, and that default flows through to the RA on creation. Although it is then possible to overtype the Calendar, only the default appears in a picklist, which is confusing to the user. In addition, even if we overtype it, if we then extend the RA via VB(D, the Calendar maintained on the individual RA will be ignored, with the Calendar taken from config again.
I find it hard to believe that we are the only company wanting to use Rebate Agreement (Arrangement) Calendars in this way, is there something obvious I'm missing ?
Many thanks, Paul.

Hi Jo Jo,
I had implemented Rebate in my company and had similar problem.
After doing Trial & Error on Sales Volume & Verification level screen I found:
In Sales Volume :
After u201CPayu201D of Accruals, remaining value comes. If the credit note created is not passed to A/C, the value does not get reduced. Also, unless the Invoice/Billing Doc. is passed to A/c. the value here shows 0 (ZERO)
Items that show accruals of 0 are invoice line items that applied retroactively. Since the rebate agreement did not exist when they were created, no accrual could be made.
In Verification level:
Total accruals, document and item wise come.
So the difference may be due to some of the docs that are not passed to Accounting or may be due to retroactive agreement.
Hope it adds value to your question.
Regards,
Tushar Karwa

Plant determination from Rebate Agreement

After creating rebate agreement type, I went to make a sales order. But the problem is, the plant didnt appear. How can I make it automatically appear in may sales order?
Thanks.

The system should default Plant AAA, but if you want to change, it is very much possible. Select the line Item & double-click on the same & goto Shipping Tab page & change the plant.
Alternatively, before entering the material in sales Order, enter Delivering Plant. (Even this may work. You will need to check this)
Regards,
Rajesh Banka
reward points if helpful.

Multiple rebate condition types in one invoice

I had defined multiple rebate condition types as Y000, Y001 and Y002, which are montly offtake rebate, distance rebate and yearly offtake rebate.
Y000 and Y001 can be in the same validity period and also will be applicable to the same invoicee.
When i create a rebate agreement for customer for Y000 and go for the settlement of the rebate it is happening fine.
But for the same customer, i had defined Y001 as a rebate agreement type for the same period and materilal.
The sales volume is not updated in the rebate agreement. Evenif I do VBOF the sales volume is not updated.
the error that comes while doing VBOF is :
"7000158055 Document number RCFL 7000158055 2011 was already assigned
7000158053 Document number RCFL 7000158053 2011 was already assigned
7000158052 Document number RCFL 7000158052 2011 was already assigned
7000158054 Document number RCFL 7000158054 2011 was already assigned"
Please help me to solve this problem.
Mrs. Swati Pawar

Hello Swati,
the suggestion of JP is correct.
I explain it better.
- the document type of FI document created from SD depends on the customizing of billing type field TVFK-BLART. If it is blank, then by default is 'RV'.
- if the number range assigned to the account document type is External, then the FI document gets the same number of the SD invoice.
- transaction VBOF creates FI document referred to SD invoice. If it has external number range, and an FI document already exist with same number (created when SD invoice has been released to accounting), then the errof F5152 occurs.
SOLUTION:
in the selection screen of VBOF there is the field FI-Doc-type. Here you should specify the FI document type that should be created by execution of VBOF, and of course it must have number range internal.
Please try this.
Best regards,
Ivano.

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

PROBLEM IN REBATES

HI
I HAVE CREATED A REBATE AGREEMENT AND ALSO A SUBSEQUENT ORDER DELIVERY AND INVOICE
BUT THE VALUES FOR THE CONDITION TYPE BO03 ARE NOT APPEARING IN THE INVOICE
SCALE BASIS =B VALUE SCALE
CHECK DESCENDING
SCALE TYPE = CAN BE MAINTAINED IN CONDITION RECORD
I HAVE DEINED SCALES IN REBATE AGREEMENT
FROM 10000   1%
    20000          2%
    50000          3%
REGARDS

Hi,
Rebate is a long term agreement between company and customer for buying certain products or for a certain volume and it is calculated on the basis or the no of billing documents say after creating four or five billing documents it is calculated
Note Rebates are not given on each billing document.We make four or five billing documents and then calulate the total rebate value and settled as credit note to the customer
If you want to set up rebate processing in a certain client, you must
u2022 Define Condition types for rebate (Tables T685, T685A, T685T)
Condition types must belong to condition class C (end-of-period rebate)
u2022 Define condition tables for rebate(Tables E*)
u2022 Define Access sequences for rebate (Table T682*)
The access sequences have to belong to category 1 (rebate-relevant accesses)
u2022 Maintain the condition types in pricing procedure.(Tables T683, T683S), rebate basis in the SubTo field (Condition subtotal) contains entry 7 (value takeover in field KOMP-BONBA).
u2022 Define pricing procedure determination.(Tables T683V )
u2022 Account Determination For Rebates will include: Define account key
Define account determination types
Assign account keys
Maintain account determination procedure
Define access sequences
Assign G/L accounts
Create accounts for the accrual if required.
Maintain the G/L account assignment and ensure that the G/L account is used in second place for accruals.
u2022 Define Rebate agreement types (Tables T6B1, T6B1T)
u2022 Define Condition type groups (Tables T6B2, T6B2T, T6B2F)
u2022 Assign Condition Types/Tables To Condition Type Groups (Table T6B2F)
u2022 Assign condition type groups to rebate agreement types (Table V_T6B1_ZU)
u2022 Number ranges for rebate agreement categories (should be maintained manually)
u2022 Order types B1 and B2 (Tables TVAK, TVAKT)x
u2022 Item categories B1N (Tables TVAP, TVAPT)
u2022 Assignment of item categories to item category groups (Table T184, B1, B2)
u2022 Billing types B1 and B2 (Tables TVFK, TVFKT)
u2022 Copy sales order to billing document (Table TVCPF, B1* and B2*)
u2022 Activate Rebate Processing at sales org , billing document and customer master data(payers view)
For more information on process please go through the below link;
http://help.sap.com/saphelp_47x200/helpdata/en/4a/ac853478616434e10000009b38f83b/frameset.htm
Hope this will help you.

Re:Rebate Agreement Setup for CRM 2007

Hello Friends,
Essentially, when we are setting up Rebate agreement types in ECC in customizing, We need to specify a Settlement document type.
Given that with CRM 2007, the rebate agreement will not be used for settlement is there any thing that they can do to not specify the Settlement document type. Since we have to specify a Settlement document type, can anyone one give guidance regarding customizing/configuring the Settlement Document Type?. Also that it should not create the Accounting document.
Thanks,
Julie

check the number range in ECC for this Reabte.
Can you give me the BDOC error which is triggered and The out bound queue also sholud be in error.
Check the out bound queue and try and reprocess that i think it wll have the dump in ECC system.
please check that dump and take corrective actions.
thanks
Kumar

No range for Rebate agreement

Hi,
Can any one explain how to maintain difference no range for different rebate agreement type. i am using two agreement type .ie B001 and B003,my client want different no range for both agreement type.
In customization there is no such provision exist.
Please guide me for the same.
Hemant

Hi,
Your can assign the number range for rebate in t code VB(1. Here create 2 separate groups for your rebate agreement type.
I hoe this helps you.
Regards,
Abhee

Problem in rebate agreement type 0005

Similar Messages

Maybe you are looking for