Extended Rebate Processing

PDF download from SAP Help Portal:

http://help.sap.com/erp2005_ehp_04/helpdata/en/5a/5b9b3c0f4da40ee10000000a11405a/frameset.htm
Created on August 29, 2016

The documentation may have changed since you downloaded the PDF. You can always find the latest information on SAP Help
Portal.

Note
This PDF document contains the selected topic and its subtopics (max. 150) in the selected structure. Subtopics from other structures are not included.

2016 SAP SE or an SAP affiliate company. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose
without the express permission of SAP SE. The information contained herein may be changed without prior notice. Some software products marketed by SAP
SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are
provided by SAP SE and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP
Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set
forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional
warranty. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE in
Germany and other countries. Please see www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.

Table of content

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 1 of 8

Table of content
1 Extended Rebate Processing
1.1 The Process of Extended Rebate Processing
1.1.1 Direct and Indirect Rebate Agreement
1.1.1.1 Rebate Recipient
1.1.1.2 Creating a Rebate Agreement
1.2 Performing Extended Rebate Settlement
1.3 Updating Indirect Sales
1.4 Updating Indirect Plan Sales

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 2 of 8

1 Extended Rebate Processing

Use
The Extended Rebate Processing component is an enhancement of the mySAP ERP rebate processing.
You can use Extended Rebate Processing to process business transactions that are typical for and occur frequently in the consumer goods industry (for
example, the beverage industry). This includes indirect sales, which are frequent practice in the beverage industry.
Indirect sales are sales activities in which the rebate-relevant sales do not take place directly between the rebate granter and the rebate recipient. In the terms
of mySAP ERP, this means the system does not use customer billing documents to update sales.
In the Extended Rebate Processing component, the system can model and settle rebates for each specific article. The system allocates the defined rebate
levels to the individual articles and provides a wide range of analyses in SAP CO-PA.
The ERP system only supports a single rebate recipient for each agreement. The Extended Rebate Processing component has been enhanced to support
multiple rebate recipients in a rebate agreement. This applies especially to customer hierarchies.
The Extended Rebate Processing component enables you to settle rebate agreements periodically. Individual periods are settled like individual agreements.

Implementation Notes
The Pendelum List Indirect Sales component is an enhancement of Extended Rebate Processing . The pendulum list enables you to process indirect sales.
The Pendulum List component provides tools for automatic data import.
This documentation describes the special features of the extended rebate , compared to the Rebate Processing application component. For more
information, see the Rebate Processing application component.

Integration
Extended Rebate Processing is integrated in SAP Profitability Analysis (CO-PA). SAP Profitability Analysis supports the article-specific update of the
customer rebate, for example. The system provides detailed information directly after settlement.

Features
A variable key in the rebate information structure provides more flexibility during rebate settlement. When the rebate information structure is updated,
certain data from the billing documents can be added to the variable key. The system copies this data to the billing document when it generates the
credit memo. This enables you, for example, to add the articles that resulted in the rebate to the credit memo, instead of the material for settlement. The
partners from the billing documents can also be copied, which makes it possible to allocate multiple rebate recipients to a single condition.
Periodic settlement of rebate agreements. Instead of periodic partial settlement, in which the system takes the entire validity period of a rebate into
consideration, you can now perform partial settlements in which the system only takes the individual periods for the settlement into account. As a result,
individual periods are settled like individual agreements. This applies especially to the use of scales and fixed amounts.
Processing of indirect rebate agreements. The use of pro forma billing documents makes indirect data available for rebate processing. You can use
special pricing procedures and condition formulas to use plan data for forming accruals and actual data for rebate settlement.
Forgo Credit Memo Requests The system immediately creates billing documents (credit memos) upon settlement.

Constraints
Make sure that you use either the Extended Rebate Processing component or the mySAP ERP Rebate Processing component.
To use the Extended Rebate Processing component, you have to activate the new mySAP ERP rebate processing.

1.1 The Process of Extended Rebate Processing

Use
You use Extended Rebate Processing (for example, in the beverage industry) to process and settle rebate conditions that are defined in written or oral
agreements.
Extended Rebate Processing helps you ensure that the information from the rebate agreement in the ERP system is processed correctly. The corresponding
settlements with your customers are performed on time and with the appropriate amounts.

Prerequisites
The following prerequisites must be met for you to use Extended Rebate Processing :
You have to activate rebate information structure S469 and information structure S136 in Customizing.
You have to activate the billing document type for rebate processing.
You have to set the Rebate flag for the rebate recipient.
You have to activate Extended Rebate Processing in Customizing for billing.
You have to define whether or not each customer is relevant for rebates in the sales area data of the customer master. This means rebate processing
must be active in the payers billing screen.

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 3 of 8

If you want to use customer-specific rebate groups (for example, house brand beer, trading goods, and so on), you will have to define them in
Customizing. You can then assign these customer-specific rebate groups to a material in the material master (tab Sales: sales org. 2 ).
If you want to use a rebate-relevant product hierarchy, you will have to define it in Customizing. You can then assign this rebate-relevant product
hierarchy to a material in the material master (tab Sales: sales org. 2 ).

Process Flow
1. First enter the rebate agreements with the rebate conditions you wish to grant.
2. When the system generates rebate-relevant billing documents (Customizing: Define Billing Types ), the system determines all the valid rebate
conditions, based on the assigned pricing procedure. The system updates rebate information structure S469. Rebate information structure S469 is the
basis for rebate settlement.
3. The system uses rebate information structure S469 to save the rebate basis, the accruals, and the payment amount for each condition and variable key.

Note
If you want to define retroactive rebate agreements, you can use transaction VBOF to include billing documents that you entered in the past. The
system then updates the rebate information structure for the conditions of this agreement.
4. Rebate settlement generates credit memos based on rebate information structure S469. The system updates the payments and release of accruals in
rebate information structure S469, taking the variable key into account.
5. To enable rebate processing for indirect sales, the rebate information structure also has to be set up for the rebate conditions of indirect agreements.
The system sets up the rebate information structure with the aid of pro forma billing documents, which are generated as the result of reported sales. The
indirect sales must be supplied to the system through a previously defined, customer-specific information structure (Customizing: Generate Update of
Indirect Sales ). Indirect sales data can be retrieved using the component Pendulum List Indirect Sales . If you want to create accruals, you will have
to use this SIS structure to supply the system with the planning data as well.
6. Extended Rebate Processing is supplied with structure BON_ENH_S1 to enable the system to determine which data has already been updated. You
have to append structure BON_ENH_S1 to the customer-specific information structure. The system saves the values that have already been updated in
the fields of structure BON_ENH_S1.
7. Because the information structure for indirect data is a customer-specific structure, the reports for creating the pro forma billing documents are supplied
as templates. If you need to modify the reports for generating the pro forma billing documents to meet your needs, Extended Rebate Processing
provides a report that generates the appropriate update routines for the actual and planning data, based on your own definitions (field assignment in
Customizing).

Extended Rebate Procedure

Note
Each billing document triggers an update. The system updates the rebate information structure in accordance with the key field settings in Customizing.
Each item in a billing document is uniquely assigned to a variable key.

1.1.1 Direct and Indirect Rebate Agreement

Use
You use the rebate agreements to process and settle agreements with a business partner for rebates granted over a specific period of time in Extended
Rebate Processing .
A rebate agreement can be concluded with a customer in a sales area (rebate recipient) or with a vendor in a sales organization (rebate granter). A rebate
agreement can consist of several individual agreements (condition records) that refer to various criteria. A single agreement, for example, could refer to the
combination customer and material or customer and product hierarchy .

Features
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 4 of 8

There are two different types of rebate agreements:

Direct rebate agreements
Indirect rebate agreements
The direct rebate agreement is an agreement that is based on direct sales. Direct sales are sales that you make directly with a customer and save as billing
documents in the system.

An indirect rebate agreement is an agreement that is based on indirect sales. Indirect sales are sales between two third parties that are saved merely as
auxiliary billing documents in the system. These auxiliary billing documents are simply used as a technical aid. They are not passed on to customers.

Note
For example, sales that a beverage wholesaler conducts with an operators restaurant. The beverage producer supplies the beverage wholesaler.

Auxiliary billing documents (that contain only rebate conditions) are generated using Extended Rebate Processing .

Example
In purchasing, a rebate agreement can be defined for:
A specific vendor or
A combination of vendor and material.
As soon as the customer exceeds a previously defined sales target, the system credits the customer with a previously defined percentage of sales.

1.1.1.1 Rebate Recipient

Use
For Extended Rebate Processing you must specify a rebate recipient. The specified rebate recipient defines the customer to whom a rebate (as defined in a
rebate agreement) is paid during settlement. You have to assign the following partner functions to the rebate recipient in the customer master:
Sold-to party
Ship-to party

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 5 of 8

Bill-to party
Payer
If a customer hierarchy is involved, you can use variable keys (VAKEY). You use these variable keys to instruct the system to generate credit memos for
payers who have achieved an agreed sales level. The system can create several rebate recipients based on a single rebate agreement.
For more information, see the Implementation Guide (IMG) for Extended Rebate Processing in the documentation Set up Variable Key for the Rebate
Settlement .

1.1.1.2 Creating a Rebate Agreement

Procedure
To create a rebate agreement, proceed as follows:
On the SAP Easy Access screen, choose:
Logistics Sales and Distribution Master Data Agreements Rebate agreement Create.
The Create Rebate Agreement screen appears
Enter the required agreement type.
Choose Continue.
The Organizational Data screen appears.
Enter the necessary data.
Choose Enter.
The Create <Agreement Type>: Overview Agreement screen appears.
Enter the necessary data.
In Extended Rebate Processing , the rebate agreement has been supplemented with the following fields compared to the standard SAP rebate processing.
Field
w. VAKEY (with variable key)

Comments
This flag indicates whether Extended Rebate Processing should be used for this
agreement type. Additional key fields enable the system to perform rebate
settlement based on the rebate origin.

ind. Settlement (indirect settlement)

This indicates the type of rebate agreement:

indirect agreement type
direct agreement type
The system determines sales and planning data based on a customer-specific
information structure. The system generates indirect billing documents based on the
sales and planning data, and updates the information in rebate information
structure S469. After the update has taken place, there are no longer any
differences between direct and indirect agreements.
Periodic and indirect settlements represent an exception to this rule: The system will
only perform periodic partial settlement for indirect agreements if confirmations exist
for the respective settlement period. The Indirect settlement field only serves
statistical purposes for non-periodic settlements.
If you do not set the Periodic settlement flag, it does not make sense to set this flag
either.

periodic Sett. (Periodic settlement)

This flag determines which periods the system takes into account in rebate
settlement.
If the flag is set, the system only takes the sales from the respective settlement
periods into account during rebate settlement.
If the flag is not set, the system takes all sales transacted to date independently of
the settlement period and all executed payments into account during rebate
settlement.

Contract data

This flag indicates whether or not contract data can be maintained for an agreement
type. The system displays the Contract Type , Contract Number and Movement
type fields for an agreement.
The contract data is passed on to SAP FI.
Use Customizing for the rebate agreement to define whether the contract data fields
in the agreement are ready for input or not.

You can go from this screen to the following tables:

Sales table
Statement table (itemized statement)
The system outputs the data as defined in the VAKEY in both lists. Please take the following considerations into account in the sales list for periodic
agreements:
The system displays the sales for the settlement period.

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 6 of 8

The system only displays intervals in which sales have to be settled.

The settlement period appears in the validity period of the agreement.
The system settles individual periods as individual settlements.
The system displays the validity for each condition.
Save your entries.

1.2 Performing Extended Rebate Settlement

Use
The system uses Extended Rebate Settlement, to settle rebate agreements.

Activities
The system determines which rebate agreements to consider for settlement, based on the selection parameters you have entered.
The system determines the sales and resulting rebate amount for each individual rebate agreement. It logs and displays the results. You can use parameters
to control how the results are displayed and which steps are to be performed.
For Extended Rebate Settlement you can choose from the following processing steps:

Performing Final Settlement

Rebate settlement is performed as of the validity end date of the respective rebate agreement (any settlement date in the selection screen is ignored).
The system takes partial payments for non-periodic agreements into account during rebate calculation.
For periodic agreements , the system initially settles each settlement period as a partial settlement by generating a credit memo for the respective end date
(date of services rendered = end date of the settlement period). The credit memo results in a payment for that period and releases the corresponding accruals.
The system releases any remaining accruals during final settlement.
The system displays all settled sales in the sales list.
The system changes status B to status D (agreement has been settled).

Note
The system usually generates an item for each condition record in the rebate credit memos. Therefore, a rebate settlement material is required for each
condition record.
The rebate can be based on:
Material group
Customer group
Customer hierarchy
Material

Performing Partial Settlement

Rebate settlement is only performed up to the settlement date you have specified in the selection screen (parameter block Periodic partial settlement ). If a
non-periodic agreement is involved, the system generates a partial payment, which is then taken into account during final settlement.
For periodic settlement, the system initially settles each individual period as a separate agreement. This applies especially to the use of scales and fixed
amounts.
The sales list only contains data for the selected settlement period. The rebate agreement status remains set to B .

Issuing Sales Volume Only

The rebate amounts pending for payment are displayed here; No settlement (update in the system) is performed.

Cancelling Final Settlement

The billing documents that the system generated during final settlement (only accruals were released in the case of periodic settlement) are reversed and the
status is reset to B (agreement released for settlement). In the sales list, the system then displays sales that are still to be settled.

Issuing Proof
In addition to the sales list, the system issues itemized proof for each selected rebate agreement. We recommend only setting the Issue proof indicator for
background processing.
You can go from the Rebate Agreements for <DATE> (sales list) screen to the following areas:
Rebate agreement
Rebate recipient
Statement table (itemized statement)
Log

Note

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 7 of 8

You can only correct a periodic rebate settlement if:

The corresponding period contains sales
The period has been settled
The credit memo to be corrected comes from the previous period
If you want to subsequently report sales for indirect data, the system creates a new billing document in the amount of the difference determined from
the previous period.
You can subsequently report indirect sales for the previous period if the previous period has already been settled.
You cannot enter subsequent reports for periods that precede this.
If final settlement has been performed for an order, you cannot enter any subsequent reports.
You can cancel a final settlement. In this case, the system reverses the last created billing documents and resets the status.

1.3 Updating Indirect Sales

Use
You use this function to start the report for updating indirect sales for rebate processing. The system updates indirect sales by creating billing documents that
contain only rebate conditions. The system determines the rebate basis for each condition and updates it in rebate information structure S469.

Note
The report does not create any accruals.

Prerequisites
To update indirect sales, you have to make the following settings in Customizing:
Settings to create indirect billing documents
Generate update of indirect sales (assign fields to the customer-specific SIS structure)
Generate the report Update for actual data

Activities
The system creates billing documents in the background. These billing documents form the rebate basis.

Note
The system issues an error message if no update routines are available.

1.4 Updating Indirect Plan Sales

Use
You use this function to start the report for updating indirect plan data for rebate processing. The system updates the indirect planning data by creating billing
documents that only contain rebate conditions. The system generates accruals for each condition and updates them in rebate information structure S469.

Note
The report does not modify the rebate basis.

Prerequisites
You have to configure the necessary settings in Customizing under Settings to create indirect billing documents .

Activities
The system creates billing documents in the background. The system then forms the corresponding accruals based on these billing documents.

Note
The system issues an error message if no update routines are available.

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 8 of 8