Volume Based Rebate condition entries in MIGO

Hi ,
I configured the Volume Based Rebate condition.
I made condition as copying A001 (Std.) . Conditon class: Expense reimbursement, Cal. Type: Qty. and Accrual.
Assign 26 requirement, Accounting key & accrual key as B02 & B01. Assign GL accounts in OBYC.
When I am doing MIGO
Inventory Dr say 1200-
Rebate Dr 100-
GR/IR Cr 1300
In this case at this point it should hit Inventory account or not. I don't want to hit Inventory. Actually I may or may not take this rebate or may not take full rebate.
How to do this.
Regards

Hello,
It will hit inventory A/c, if you don't want it you should create a new account using Rev A/c Det and assign it.

Similar Messages

Rebate Condition Type based on Calculation

I am trying to create a rebate condition that is based on the calculation of Average Invoice Price of group of products. However, I am not able to select the Calculation type based on Formula. Please let me know if someone has come across the same issue.

For example, Rebate of $2/unit of Product A is given to a customer only if
Averrage Invoice Price of Product A, Product B and Product C is greater than $135

Filtering table entries based on conditions

Hi there,
I would like to filter out some of the entries of the tables based on condition, how can I do that? I"m currently working on ICWC.
Thanks,
Jared

HI Jared81,
Use SELECT Statement..
 SELECT SINGLE zzemp_type
 FROM pa9000
 INTO l_employee_type
 WHERE pernr = l_pernr
 AND begda LE sy-datum
 AND endda GE sy-datum.
IF sy-subrc = 0 .
endif.
or use
READ table statement
READ TABLE i_ltype INTO w_ltype WITH KEY leave_code = g_leavetype_selected.
 IF sy-subrc = 0.
 g_leave_cat = w_ltype-leave_cat.
 g_leave_type = w_ltype-leave_code.
Append w_ltype to i_ltype.
 ENDIF.
Rgds,
Jothi.
*reward all helpful answers.

Sales Volume in rebate management

Rebate is based on validity period and sales volume,we can define the validity period but where we will give this total sales volume.
amit

When you first create a rebate agreement, the system prompts you to specify a rebate agreement type. The rebate agreement type you specify determines which data the system automatically proposes for the corresponding rebate agreement. For example, the system can propose
·        which condition types you can use in an agreement
·        which validity period the system automatically proposes for an agreement
·        which status is required before an agreement can be processed for payment.
·        which rebate agreement types are defined in Customizing for Sales and Distribution.
Agreement Types in the Standard Version
The standard version of the SAP System includes the following rebate agreement types (the table shows the corresponding condition types):
Agreement type          Basis of rebate        condition type
0001                       Customer/material        (% rebate)BO01
                            Customer/rebate group    (% rebate)BO01
0002                      Customer/material     (quantity dependent)
                                                                          BO02
0003                          Customer                       (% rebate)
                                                                          BO03
0004                       Customer hierarchy          (% rebate)
                                                                          BO04
                          Cust. hierarchy/material       (% rebate)
                                                                          BO05
0005                   Sales volume independent         BO06
Hope this classification will help.
Regards,
Siddharth.

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 condition in rebate agreement cannot be maintained (greyed out)

Hi.
We have setup rebate processing in CRM 7.0.
We get our invoice to the billing due list and it fills then the extract. But we fail in setting up the rebate agreemnt in the webui.
Partner and material are entered. On the position (material) we try to add one of the conditions of the maintenance group we customized. Both condition types can be selected but none of them will work.
What happens: we click on "new" select the condition type and get then presented with the view but with all fields greyed out (as in display mode).
As there are a lot of obligatory fields we get up to 8 messages. After "fill in required entry fields" it says "maintain rebate material".
Whatever that means.
The material we use is a finished product.
Has somebody ever seen this or some idea. Couldn't find oss messages on this.
Thanks.
Regards,
Thorsten

Hi Klaas,
If I remember well, in the standard price determination there is a conditional formula that only shows rebate conditions in the invoice, therefore you should not see rebate conditions in the sales order.
That is standard functionality.
For a Customer I took out the formula condition in the pricing so he could actually see the rebate condition in the sales order, the reason was to had access to this information before end of month invoicing. The problem is that in case of changes in rebate agreement or in case of retrospective agreements the rebate condition is only updated in the invoice, not in the sales order.
Best Regards,
Franck

Volume based price adjustments in PO

Hi SAP experts,
Are you aware of any functionality (other than vendor rebates) that allows you to get volume discounts at the vendor level (multiple contracts)? We would like to systematically get volume based price adjustment in the PO based on purchasing volume at the vendor level (crossing multiple contracts).
Thanks and regards, Jose Oyon.

Hi Jose,
Sorry i am not aware about this kind of functionality
Regards,
Manish

Rebate conditions

Hi all.
I am exploring rebate management concept. Ive got stuck here. I have created rebate conditions in CRM.
I have also loaded the customizing settings for these from R/3 backend system. But the pricing conditions are not getting correctly determined.
Has anyone worked on this before?
Please help me.
Seema

Seema.
Going by your words that you have maintained all teh settings in ERP you need to do some tehnical settings as below...
Before you do this i suggest you once again check all the customizing settings in ERP.
you have to create the function module 'CND_MAP_CONV_FUNC_T685A_KRUEK' in the function group 'CND_MAP_GNRL_INTF_OW'.
See the interface details below:
You can also implement the interface directly by copying the module 'CND_MAP_CONV_FUNC_T682Z_QUSTR'
Interface of the module 'CND_MAP_CONV_FUNC_T685A_KRUEK'
Import
Parameter Name
IV_SOURCE_FIELD check the 'Pass Value' checkbox.
Export
Parameter Name
EV_TARGET_FIELD check the 'Pass Value' checkbox.
You must change the following existing entries in the CND_MAPC_CNV_FLD table.
Field Name Content
MAPPING ASSIGNMT 'A'
LOCAL TABLE 'PRCC_COND_CT'
LOCAL FIELD 'KRUEK'
REMOTE TABLE 'T685A'
REMOTE FIELD 'KRUEK'
CONVERSION TYPE 'C'
CONVERSION FUNC 'CND_MAP_CONV_FUNC_T685A_KRUEK'
Field Name Content
MAPPING ASSIGNMT 'A'
LOCAL TABLE 'REBC_COND_CT'
LOCAL FIELD 'KRUEK'
REMOTE TABLE 'T685A'
REMOTE FIELD 'KRUEK'
CONVERSION TYPE 'C'
CONVERSION FUNC 'CND_MAP_CONV_FUNC_T685A_KRUEK'
Save your changes.
You must re-download the Customizing of the condition types again from ERP.
Only then, the KRUEK field of the condition types for bonus is filled correctly in the PRCC_COND_CT und REBC_COND_CT CRM Customizing tables.
Hope this helps.
 Julius Pereira

Rebate condition type

Dear Experts,
I have created a condition type for material rebate and the same has been assigned to condition type grp in turn condition type grp is assigned to rebatye agreement type....besides the same(cond type) is included in the pricing procedure.....the issue is even after maintaining the cond record the values are not flowing moreover when I see to the condition type details in the order level( I
deliberately made the rebate cond type to flow in sales order) few settings got changed like scale type,calculation type,..etc...how come the settings may change other than what I have maintained...I could see my own settings exist in V/06 for the rebate cond type.....what would be the reason?.....thanks in advance.......

Hi,
1st see in condition detial,maintain
Processing priority - Automatic entry has priorit or No limitation
Second,in price procedure V/08, if you maintained any requirement in requirement coloumn in front of rebate condition then remove that.
Kapil

Rebate Condition

Hi,
We maintain the basis value as a scale value in purchase rebate agreement. When we create a rebate agreement wrt PO the rebate condition occurs in PO only if the PO value is equal or more than the basis value in rebate agreement. But the client dont buy all items at once equal to the basis value, they buy less in many PO's and only if they reach the purchase equal or more than basis value then the rebate will be paid. Please let me know how to handle this scenario.
Thanks,
MM

Hi
The type of rebate that you are applying is a volume rebate whcih gets applied only once you reach a certain limit.
Its all depedndent on the way you configure the Condition type. The condition type should be of
Cond. class C Expense reimbursement, this will ensure that the rebate is calculated for the total value procured, and counts each PO raised on the Vendor against whom the rebate arrangement is maintained.
Thanks & Regards
Kishore

Multiple rebate conditions

Hi folks:
I hope you can shed some light on this issue I am dealing with.
We are trying to use rebate agreements in the following situation, but it does not seem to work:
The company negotatiates a deal whereby a client gets a Credit Note with a global discount if it meets 2 targets during a specific period:
Material Group 1 Target volume 1 = 100 KG
Material Group 2 Target volume 2 = 200 KG
If sales to the client exceed both targets, at the end of the period a Credit Note is issued for 10% of the overall sales to the client during the period. If one or none of the targets are met, there is no global discount for the client.
We are trying to implement this via a Rebate Agreement with 3 rebate conditions:
Condition 1 = ZB01 (Customer/Material Group rebate); scale starting at 100 KG; 1% (for the sake of this example, just consider 1% as an arbitrary value to ensure that the condition will be <> 0 if the sales for Material Group 1 exceed 100 KG)
Condition 2 = ZB01 (Customer/Material Group Rebate); scale starting at 200 KG; 1% (for the sake of this example, just consider 1% as an arbitrary value to ensure that the condition will be <> 0 if the sales for Material Group 2 exceed 200 KG)
Condition 3 = ZB02 (Customer rebate); no scale; 10 % (global discount specified in the agreement)
Our idea was to configure the pricing procedure in such a way that the first two conditions would be statistical (that is, would not alter the value of the Credit Note) and the third condition would be considered only if the other two were both <>0.
So far we have not found a way to make the first two conditions not affect the value of the Credit Note. We tried marking ZB01 as statistical. We also tried using Condition Exclusion Groups. In all cases, the two conditions affect the value of the Credit Note.
Has anybody dealt with a similar situation? Any ideas?
Thanks,
Sebastian

Hi Sebastian,
really a very niceissue to think some time ,
Any way for the two condition types zb01&zb02,there is an exclussion indicator while creating the Acess sequences for the two condition types .Check that and tried.Correct me if it is wrong.
If it helpfull Rewards me the points.
Rgds
Siva Yepuri

Rebate Accounting Entries.

Dear Sd gurus,
I have done whole senarion of rebate bt i wan tto know std accounting entries in rebate process like wht goes cr or dr like accurals g/l etc.
and want to know abt manual accuals doc & rebate correction req doc.
hope u will solve my issues.
Regards

Hello,
The Accruals will be posted to the G/L account which is maintianed against the account key ERU and the rebate (deduction) will be posted against the G/L account maintianed for accounting key ERB.
Manual Accruals:
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.
To post accruals manually:
Select Logistics --> S&D --> Master data -->Agreements --> Rebate agreement -->Change. Enter the number of the rebate agreement or determine the number by selecting a matchcode.
Press ENTER. Goto -->Manual accruals (overview screen)
Enter the accruals to be posted in the field beside each rebate condition record as follows: negative amount: to build accruals, positive amount: to reverse accruals
It is not possible to reverse more accruals than actually exist for a condition record.
Rebate Correction:
Instead of trying to figure out the manual accrual difference, you can also use the correction document. IMG -->SD -->Billing>Rebate processing>Compare Rebate Basis And Correct Accruals. Enter the agreement number, and execute. Instead of doing a manual accrual, just click on the button, which will automatically create a B2 correction document.
Prase

Enhancement to update sale volume for rebates

Dear All,
We have a senerio for sale voume rebate process that only above 50000 sale value will add up in sale volume in rebate agreement for accrual process.
Can we do this through standerd or through enhancement?
please help.
Regards'
Kumar

Hi Mukul,
Mark your condition type VALUE SCALE and Check Value as A.
Update condition record in Rebate agreement. Then in Scale section mark it applicable as FROM 50,000 INR with respective Rate.
And it will work as per your requirement.
When you will do Settlement of the Rebate Agreement it will create Credit Memo only if Value is more than 50000 INR.
Regards,
MJ.

Extracting from table based on conditions from two internal tables

Hi,
     i to have select few records from a table based on conditions from two different internal tables. How can I achieve this.?
ex:
      select objid from HRVPAD25 into table t_pad25
                                                where PLVAR = 01
                                                            OTYPE = E
                                                            OBJID = itab1-sobid
                                                            sobid = itab2-pernr.
How can this be written? can i use "for all entries..." addition with 2 tables?

Hi Maansi_SAP,
you can use exactly one internal table in the FOR ALL ENTRIES clause. Consider this alternative:
data:
itab_sobid_hash like itab1 with unique key sobid,
ls_pad25 like line of t_pad25.
sort itab1.
delete adjacend duplicates from itab1 comparing sobid.
itab_sobid_hash = itab1.
select objid
into ls_pad25
from HRVPAD25
for all entries in itab2
where PLVAR = '01'
    and OTYPE = E
    and sobid = itab2-pernr..
read table itab_sobid_hash with table key sobid = ls_pad25-objid.
check sy-subrc = 0.
append ls_pad25 to t_pad25.
endselect.
You may decide if itab1 or itab2 is better used as hashed table. Make a performance test.
The critics will tell you that SELECT ... ENDSELECT is not performant. That was very true, back in last milleniums's 90ies
Regards,
Clemens

Need clarification on Rebate condition account keys

Hi Guys,
I need some clarification on Rebate condition account keys .Question is why rebate condition type has two account keys eg.ERB & ERU and why not we make it seperately as other conditions .APPreciate your comments on this .
Thanks and regards
Amar

ERB: is the account key for Rebate Rate
ERU: *is the account key for the Accrual Rate*
As you know both these Account Keys are assigned to the Rebate Condition Type in the pricing procedure. All the Rebate &
Accruals are posted in the separate G/L Account for the Rebates. So, ERB for rebate this account key posted to revenue a/c
ERU is price this is posted amount to accrual a/c
To further explain it.
ERB acct key which is used to record the sales deductions amount.
System will keep the track of billing documents relevant for rebate processing. System automatically posts the accruals so that accounting has an overview of the accumulate value for the rebate..the value will posted in the G/L account based on ERU.
Hope it can assist you.
Thanks & Regards
JP

Volume Based Rebate condition entries in MIGO

Similar Messages

Maybe you are looking for