Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
2010
Rebate Processing v0
www.rglconsultancy.nl
Rebate Processing
CONTENTS:
1)
2)
3)
4)
5)
6)
7)
8)
Introduction
Data to be used during this process
Overview of master data and customizing settings
Create Rebate Agreement
Create sales orders, deliveries, transfer orders and billing documents
Settle Rebate Agreement
Create rebate Credit Memo
Run the profitability report
Page
2
2
2
10
15
25
31
34
38
1 / 42
Rebate Processing v0
www.rglconsultancy.nl
1) Introduction
In this document the setup requirements of a rebate process and all the steps involved in a rebate process will
be demonstrated.
Data
Description
Sales organization
Distribution Channel
Division
Plant
Warehouse number
Shipping point
Agreement type
Rebate recipient
Settlement material
Settlement material
Sold-to party
Sold-to party
Material
Material
Material
Operating concern
Type of Profit. Analysis
1020
20
00
1100
011
1100
0004
6000
170
180
6002
6006
Y-352
Y-353
CH_5103
IDEA
Costing based
Berlin, Germany
Retail chains
Cross-divisional
Berlin plant
Warehouse, Berlin
Shipping point, Berlin
Hierarchy rebate
Customer
Settlement material for rebate credit memo for gloss paints
Settlement material for rebate credit memo for primer
Customer
Customer
Paint 5 L can
Paint 10 L can
Primer coat black 2 L Can
Global IDES
Enter customer no.(6000) and sales area(1020/20/00) as selection criteria and then click on
This gives the following information:
2 / 42
Rebate Processing v0
www.rglconsultancy.nl
Customers 6002 and 6006 are on hierarchy level 3 and all customers are relevant for rebate,
which is a process requirement.
This rebate relevant property of the customer is set in the billing view of the customer master as shown below:
Also the sales organisation and the billing document type must be relevant for rebate processing and this is set
in customizing:
Menu Path
Transaction Code
Also the billing document types which will be used for billing the deliveries must be relevant for
rebate. These are also set in customizing:
IMG Sales and Distribution Billing Rebate Processing Active Rebate
Menu Path
Processing Select billing documents for rebate processing
Transaction Code
OVB0
3 / 42
Rebate Processing v0
www.rglconsultancy.nl
Next we do some checking on the pricing procedure to be used and the customizing settings of the rebate
agreement. The cust. pricing procedure = 1, see screenshot below .
Sales order type OR will be used for the sales orders. We check its document pricing procedure in
customizing:
Menu Path
Transaction Code
4 / 42
Rebate Processing v0
www.rglconsultancy.nl
5 / 42
Rebate Processing v0
www.rglconsultancy.nl
Of importance here is condition type BO05, which will be used in the rebate agreement which will be created in
next paragraph. . Notice table no. 5 which has been assigned to this condition.
Again we go a bit further down into the customizing tree to look for the access sequence of condition type
BO05.
Menu Path
Transaction Code
6 / 42
Rebate Processing v0
www.rglconsultancy.nl
It may look like all accesses are the same, but that is not the case. On field level there is a difference on field
customer hierarchy which is shown below.
For each customer hierarchy we have an access no. The first 2(10 and 20) are as follows:
We now take a look at pricing procedure RVAA01 in customizing to check for the settings made for condition
type BO05.
Menu Path
Transaction Code
7 / 42
Rebate Processing v0
www.rglconsultancy.nl
Transaction Code
Via both ways you will be prompted with the following pop-up:
You will need to go thru each table to look for an account assignment.. For this case the assignments are in table
5 Acct Key and are as follows:
8 / 42
Rebate Processing v0
www.rglconsultancy.nl
At last we check if the customizing setting is in place to transfer the rebate conditions values to CO-PA.
Menu Path
Transaction Code
In the pop-up window enter your operating concern and keep the default type of Profit. Analysis
(costing-based).
Then click on button
We see that value field VV090 has been assigned to the rebate conditions in std. SAP.
9 / 42
Rebate Processing v0
www.rglconsultancy.nl
10 / 42
Rebate Processing v0
www.rglconsultancy.nl
The system will already have filled-in some default data from the configuration of the agreement type.
Maintain at least the Rebate recipient and optional the fields Description and External description.
Then click on the button
Click on button
11 / 42
Rebate Processing v0
www.rglconsultancy.nl
12 / 42
Rebate Processing v0
www.rglconsultancy.nl
13 / 42
Rebate Processing v0
www.rglconsultancy.nl
Enter the settlement materials, here material no. 170 and 178.
Now the setup of the rebate agreement is complete and we can click on button
At the screen bottom we see and make a note of the rebate agreement number:
14 / 42
Rebate Processing v0
www.rglconsultancy.nl
15 / 42
Rebate Processing v0
www.rglconsultancy.nl
Enter the necessary selection criteria in order to narrow down the selection to the 2 sales orders.
Click on button
16 / 42
Rebate Processing v0
www.rglconsultancy.nl
17 / 42
Rebate Processing v0
www.rglconsultancy.nl
If we check the document flow of for example delivery 80017323 then we see that indeed all expected steps are
performed:
18 / 42
Rebate Processing v0
www.rglconsultancy.nl
Enter the sales organisation and a date range then click on button
Click on button
Position the cursor on the group number, and then click on button
19 / 42
Rebate Processing v0
www.rglconsultancy.nl
The billing document contains lines with zero values because the materials used for this test are batch
management which resulted in zero lines in the delivery on line level, see below:
20 / 42
Rebate Processing v0
www.rglconsultancy.nl
For this reason, the billing document contains an item without a batch entry and which has a billing quantity of
zero, and a further item for each batch with the corresponding billing quantity.
Select line item 2 in the billing document, then click on button
.
21 / 42
Rebate Processing v0
www.rglconsultancy.nl
Things which can be noticed further here are the account keys ERB and ERU with their respective accounts, and
the rebate agreement no. 194.
You can see that the pricing condition has been calculated according to the rebate agreement. The amount
corresponds to the provision percentage rate determined in the rebate agreement (Condition values section). The
condition is only for statistical purposes and does not influence the value of the billing item. A provision is
posted for the value of the condition (Control data section).
In the condition record for the rebate agreement, the sales volume valid for a rebate is increased by the value in
the Rebate basis line.
Choose
Choose
22 / 42
Rebate Processing v0
www.rglconsultancy.nl
In Financial Accounting, both revenue and receivables have been posted, along with the provision for the value
of condition type BO05. Account 89000 is the balance sheet account and account 884010 is the sales deduction
account.
.
Click on button
Two documents exist for the profitability analysis because it is updated for each item in the billing document.
Double click on the first document of the profitability analysis.
23 / 42
Rebate Processing v0
www.rglconsultancy.nl
You can see here all the relevant data from the billing document.
Characteristics exist for all dimensions that can be used for analysis purposes in Profitability Analysis. These
characteristics values are derived from the customer and material master data and from SD partner roles (such as
sales representatives), or from CO-PA-specific characteristics.
Choose tab Value fields.
The value fields contain detailed information about billing quantities, revenue, rebates and detailed product cost
components that were derived from the Sales and Distribution and Product Cost Planning areas. Note that the
list of value fields continues over several screens.
Click on button
Click on button
Click on button
24 / 42
Rebate Processing v0
www.rglconsultancy.nl
If you get a pop-up like below, then you are using a SAP system which is using the New rebate procedure:
What this message is saying is that this agreement 194, does not contain any sales volume yet,
although we know we have created 2 billing documents which includes sales volume.
Click on button
to continue.
25 / 42
Rebate Processing v0
www.rglconsultancy.nl
Click on button
We can see that indeed we have only zero values in the Sales Volume view.
This new rebate procedure is described in SAP note 105681 , of which the content has been included in an
appendix at the end of this document.
To populate/update the agreement with this sales volume from the billing documents call up following tx :
Menu Path
Transaction Code
Note that normally associated program SDBONT06 should be scheduled to run on regular intervals to
automatically perform this update.
26 / 42
Rebate Processing v0
www.rglconsultancy.nl
For this single agreement I have selected above criteria and first ran in test mode , see flag set at the bottom. If
the program finds relevant billing documents it will show each number at the bottom of the screen while it is
being processed. If the test is successful then ran again without the test flag set.
Then start again with tx VBO2.
Enter agreement no. followed by
Then click on button
which now will show the sales volume, see next screen:
27 / 42
Rebate Processing v0
www.rglconsultancy.nl
The rebate agreement displays the values currently accrued for each condition and the total values.
At the bottom of the screen we see that the customer(6000) is entitled to receive 6770,86 euro rebate, while
5375,90 euro has been reserved(accrued) for him.
Click on button
We will now final settle this agreement, although this is normally done at the end of the validity period or
partially during the validity period. Go to menu Rebate payments Final settlementUsing payment screen.
28 / 42
Rebate Processing v0
www.rglconsultancy.nl
If you normally do not have the intention to change anything in the rebate agreement prior to settling and you
want to perform settling of more than one agreement at the same time, then perform following tx:
Menu Path
Transaction Code
By using associated program RV15C001 you can schedule the settlement of rebate agreements in the
background on a convenient time.
Display the agreement with tx VBO3.
The control data section is now:
29 / 42
Rebate Processing v0
www.rglconsultancy.nl
We see that only final settlement was performed and therefore only documents related to final settlement can be
seen.
Click on button
30 / 42
Rebate Processing v0
www.rglconsultancy.nl
You can see that the credit memo request has been created for the rebate recipient 6000 (entered in the rebate
agreement). The items in the credit memo request are created using the settlement material entered in the
condition records for the rebate agreement.
Select the second item and click on button
31 / 42
Rebate Processing v0
www.rglconsultancy.nl
We see that condition type BO05 appears twice. In the first line, it contains the payment amount calculated from
the sales volume(see page 27). The second line contains the provision amount posted up to now. When you
create the credit memo, the provision in Financial Accounting is written off by this amount. In Profitability
Analysis, once the credit memo has been created, the system updates the difference between the payment and
provision amounts in the rebate value field.
Remove the billing block in the header of the credit memo request then go to menu>Sales document>Billing
32 / 42
Rebate Processing v0
www.rglconsultancy.nl
or if you want you can first check the billing document contents prior to saving.
When saved the R/3 System issues the billing document number:
If we check the document section of the rebate agreement again we can see that the credit memo request was
replaced by the credit memo document, which shows what was accrued and what was settled.
33 / 42
Rebate Processing v0
www.rglconsultancy.nl
In the pop-up window enter your operating concern and keep the default type of Profit. Analysis (costingbased).
Click on button
Select a rebate report by double clicking on the line with the report name.
Here I selected: IDES-170 Rebate
Prior to billing of the 2 deliveries the report was ran.
Enter the period from and to then click on button
Click on button
=>
34 / 42
Rebate Processing v0
www.rglconsultancy.nl
In the top line, you can see that sales organization 1020 and distribution channel 20, which have been
determined for this report. You can page through the characteristics as you require. The value fields displayed
are for the Inv. quantity, Revenue and Acc. bonus.
Double-click on line 03 Paints. The system displays product hierarchy 1.
35 / 42
Rebate Processing v0
www.rglconsultancy.nl
You now see product hierarchy 2 which contains gloss paints articles Y-352 and Y-353.
In the Acc. bonus value field, you can see the amounts that are accrued as rebates.
Note the value of 3474,80 euro for material Y-353.
We now check the report after the credit memo was posted.
36 / 42
Rebate Processing v0
www.rglconsultancy.nl
We see that the difference between the accrued rebate and the rebate payment of material Y-353 was posted on
material 170, the settlement material. For material Y-352 nothing was posted on material 170 because the
accrued value and the rebate value are the same.
Double-click on settlement material 170.
You will than see customer number 6000, the central office. The difference between the rebate provision and
rebate payment has been offset for this customer.
Click on button
Double-click on the article Y-352 or Y-353 to see an overview of the customers in the RIWA company that
ordered this article.
37 / 42
Rebate Processing v0
www.rglconsultancy.nl
If the program determines a different result concerning rebate conditions, the rebate
conditions are updated.
38 / 42
Rebate Processing v0
www.rglconsultancy.nl
o If these changes affect accruals, an additional accounting document is created for the specified
posting date which adjusts the provisions.
o If changes occurred, statistical data (S060) is also adjusted. This occurs for the date of services
rendered that is in the same period which was also posted before.
o If errors occur during pricing, the billing document cannot be updated (see error log).
o If the net value of a billing document changes (for example, when you enter a rebate condition
which excludes a non-rebate condition retroactively), the billing document is
also not updated.
What effect do the parameters of the program have ?
Agreements
You can restrict processing to certain agreements or agreement intervals.
Posting date
You can specify the posting date for the document corrections. This date is, for example, used
for the transfer to Financial Accounting. However, for the update of the statistics (S060) the date of
services rendered is used.
Test
If you set these parameters, the system neither changes billing documents nor creates
accounting documents.
Log
You can use this parameter to control whether a log should be issued or not.
Changed agreements
You can use this option to control whether the program should only take billing documents for
changed agreements into account.
How does the program recognize whether changes were performed concerning an agreement?
If you maintain rebate agreements or change the corresponding conditions, when you change data
which may affect documents, the system indicates the respective condition records (field KONPKSPAE). This is performed when you create retroactively valid agreements or change the following
fields:
Validity period
Deletion indicator
Accruals amount
39 / 42
Rebate Processing v0
www.rglconsultancy.nl
If the update of all billing documents for the condition records of an agreement was performed
successfully, the indication is then cancelled and as a result, when these condition records are passed
through later, they are no longer taken into account.
You can recognize whether an agreement was marked as changed when during the call of the
agreement or when data for the agreement is output the system displays message:
VK780 "The sales volumes for agreement & is not current".
How shall I use parameter 'Changed agreements'?
Normally, you should set this parameter, since an improved runtime is achieved with a restriction to
changed agreements.
You should only deactivate the parameter if changes which are relevant for rebate occurred outside
rebate agreement maintenance. These are, for example:
Pricing procedure
o Add/delete rebate condition types
o Formulas/requirements for rebate condition types
o Reference step of a volume rebate condition type
Access sequences
o Add/change/delete accesses
o Requirements
o Exclusive indicator
Condition type
o
If parameter 'Changed agreements' is not set, in this case you should attempt to restrict the agreements
manually as much as possible.
Also consider that for the above changes you may have to set up the rebate index (VBOX) again, no
matter if you use the new rebate procedure or not. Thus, the previous process has not been changed
concerning this point.
When should I use the program for the update?
Basically you should always update billing documents when you change data which is relevant for
rebate.
You should note, however, that depending on the data volume the program may require considerable
runtimes. You should find a compromise with which the update is performed often enough, however,
not too often.
40 / 42
Rebate Processing v0
www.rglconsultancy.nl
Pricing error
The billing document is blocked
The net value of the billing document would change
Error during the transfer to accounting
and others
In this case you must first correct the error situation (for example, correct the settings) and then
perform the update again.
1. Restrictions and risks
During the final settlement of rebate agreements, the system first checks whether the agreement
is indicated as changed. In this case, no final settlement is possible. You must update the billing
documents first.
The most critical factor when you use the new rebate procedure is the runtime of the document
update. You should always be aware of the fact that changes ot agreements require an update of
the billing documents (in particular before the final settlement).
Depending on the situation, table S136 may become quite large. In it, the system creates an
entry for each determined condition record and for each billing document.
The system cannot check whether changes were performed outside agreement maintenance. In
this case, before the final settlement you should check whether the billing documents must be
updated (see the remarks concerning parameter 'Changed Agreements').
Problems may occur if the update of the billing documents is not possible for one of the above
reasons.
Since it may be difficult to solve error situations, you should avoid this. For example, when you
perform changes in the system (for example, to the calculation schema or to account determination)
you should always be aware that this may affect the update of billing documents in the system.
41 / 42
Rebate Processing v0
www.rglconsultancy.nl
If you are not able to solve the respective error situation, as a last option you can cancel the
billing document and bill the preceding document again.
In particular, you should avoid rebate conditions influencing (for example, excluding) other
non-rebate conditions (for example, Immediate discounts). In this constellation, documents could
never be updated if the net value would change. If such dependencies are used, the new rebate
procedure cannot be used.
Since the billing documents relevant for the sales volume are updated when you use the new
rebate procedure and if necessary, accruals are adjusted, you no longer have to create rebate
correction documents (B2).
In addition, you should note that the statistics update is client-specific. To avoid confusion the
procedure should be activated in all used clients.
2. Use of the procedure for existing data
Basically you can also use the new procedure for existing data. In this process, consider the following:
When you activated statistics structure S136, you must set it up again for existing billing
documents. You can do this via the standard function for the statistical setup of billing
documents (Transaction OLI9). 'Redetermination of the update group' and 'Update documents'
are not required.
Then copy the set up version to version '000' (Transaction OLIX).
For the already existing agreements there should be no rebate correction documents (B2) which
already performed an accruals correction. Otherwise, the accruals would be updated again
during the following update run of the billing documents and as a result would be corrected
more then once (the update run does not take existing rebate correction documents into
account!).
You may have to cancel existing rebate correction documents.
42 / 42