EHP4 for SAP ERP
6.0
December 2010
English
Extended Rebate
Processing with
Customer (288)
Building Block Configuration Guide
SAP AG
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany
© SAP AG
Page 1 of 11
SAP Best Practices
Extended Rebate Processing with Customer (288): Configuration Guide
Copyright
© Copyright 2010 SAP AG. 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 AG. The information contained herein may be changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software
components of other software vendors.
Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z,
System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390,
OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+,
POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System
Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA,
AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks
of IBM Corporation.
Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks
of Adobe Systems Incorporated in the United States and/or other countries.
Oracle is a registered trademark of Oracle Corporation.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks
or registered trademarks of Citrix Systems, Inc.
HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web
Consortium, Massachusetts Institute of Technology.
Java is a registered trademark of Sun Microsystems, Inc.
JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology
invented and implemented by Netscape.
SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP
products and services mentioned herein as well as their respective logos are trademarks or registered
trademarks of SAP AG in Germany and other countries.
Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions,
Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well
as their respective logos are trademarks or registered trademarks of Business Objects S.A. in the United
States and in other countries. Business Objects is an SAP company.
All other product and service names mentioned are the trademarks of their respective companies. Data
contained in this document serves informational purposes only. National product specifications may vary.
These materials are subject to change without notice. These materials are provided by SAP AG 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 AG
Page 2 of 11
SAP Best Practices
Extended Rebate Processing with Customer (288): Configuration Guide
Icons
Icon
Meaning
Caution
Example
Note
Recommendation
Syntax
External Process
Business Process Alternative/Decision Choice
Typographic Conventions
Type Style
Description
Example text
Words or characters that appear on the screen. These include field
names, screen titles, pushbuttons as well as menu names, paths and
options.
Cross-references to other documentation.
Example text
Emphasized words or phrases in body text, titles of graphics and tables.
EXAMPLE TEXT
Names of elements in the system. These include report names,
program names, transaction codes, table names, and individual key
words of a programming language, when surrounded by body text, for
example, SELECT and INCLUDE.
Example text
Screen output. This includes file and directory names and their paths,
messages, source code, names of variables and parameters as well as
names of installation, upgrade and database tools.
EXAMPLE TEXT
Keys on the keyboard, for example, function keys (such as F2) or the
ENTER key.
Example text
Exact user entry. These are words or characters that you enter in the
system exactly as they appear in the documentation.
<Example text>
Variable user entry. Pointed brackets indicate that you replace these
words and characters with appropriate entries.
© SAP AG
Page 3 of 11
SAP Best Practices
Extended Rebate Processing with Customer (288): Configuration Guide
Contents
1
Purpose .............................................................................................................................. 5
2
Preparation ......................................................................................................................... 5
2.1
3
Prerequisites ............................................................................................................ 5
Configuration ...................................................................................................................... 5
3.1
Activating Rebate Processing for Sales Organization ............................................. 5
3.2
Assigning Allowed Customer Group for Customer Hierarchy .................................. 6
3.3
Creating Customer Hierarchy................................................................................... 6
3.4
Defining Agreement Types....................................................................................... 8
3.5
Assigning Condition Type Groups to Rebate Agreement Types ............................. 9
3.6
Settings for Agreement Types YGE1 ....................................................................... 9
3.7
Setting up Variable Key for Rebate Settlement (Agreement Type: YGE1) ........... 10
3.8
Activating Extended Rebate Processing ................................................................ 11
© SAP AG
Page 4 of 11
SAP Best Practices
Extended Rebate Processing with Customer (288): Configuration Guide
Extended Rebate Processing with Customer
1 Purpose
This configuration guide provides the information you need to set up the configuration of this
building block manually.
If you do not want to configure manually and prefer an automated installation process using
SAP Best Practices Solution Builder and other tools, refer to the SAP Best Practices Quick
Guide.
2 Preparation
2.1 Prerequisites
Before you start installing this building block, you must install prerequisite building blocks. For
more information, see the building block prerequisite matrix
(Prerequisites_Matrix_[xx]_EN_CO.xls; the placeholder [xx] depends on the SAP Best
Practices version you use, for example, CPW refers to the SAP Best Practices for Consumer
Products and Wholesale Industries Package: Prerequisites_Matrix_CPW_ENCO.xls). This
document can be found on the SAP Best Practices documentation DVD in the
folder ../../CP_WSD_CO/Documentation.
3 Configuration
3.1 Activating Rebate Processing for Sales
Organization
Use
The purpose of this activity is to activate the rebate processing for the sales organization
1000.
Procedure
1. Access the activity using one of the following navigation options:
Transaction code
OVB1
IMG menu
Sales and Distribution  Billing  Rebate Processing 
Activate Rebate Processing
2. In the Choose Activity dialog box, choose the activity Activate rebate processing for sales
organizations and choose Enter.
3. On the Change View “Sales Organizations – Rebate”: Overview screen, make the
following entry:
Field name
Rebate proc. active
Description
User action and values
Note
Set flag for the sales
organization 1000
4. Choose Save.
© SAP AG
Page 5 of 11
SAP Best Practices
Extended Rebate Processing with Customer (288): Configuration Guide
5. In the Rebate: Re-create Billing Index dialog box, choose No.
Result
You have activated the sales rebate processing for the sales organization 1000.
3.2 Assigning Allowed Customer Group for Customer
Hierarchy
Use
The purpose of this activity is to assign the possible higher-level account groups to the
account groups permitted for each customer hierarchy type.
Procedure
1. Access the activity using one of the following navigation options:
Transaction code
OVH2
IMG menu
Sales and Distribution  Master Data  Business Partners 
Customers  Customer Hierarchy  Assign Account Groups
2. On the Change View “Allowed Acct. Grp. Assign. for Cust. Hier.”: Overview screen, make
the following entry:
Cust
H
Type
Name
(EN)
Name
(ES)
Acct
Group
Desc
riptio
n
(EN)
Descrip
tion
(ES)
HglvAcc
tGr
Descrip
tion
(EN)
Description
(ES)
A
Stand
ard
Hierar
chy
Jerar
quía
Están
dar
YG01
Custo
mer
CP
Cliente
CP
0003
Payer
Responsable
de Pago
A
Stand
ard
Hierar
chy
Jerar
quía
Están
dar
YG01
Custo
mer
CP
Cliente
CP
0012
Hierarch
y Node
Nodo de
jerarquía
A
Stand
ard
Hierar
chy
Jerar
quía
Están
dar
YG01
Custo
mer
CP
Cliente
CP
YG01
Custom
er CP
Cliente CP
3. Choose Save.
Result
You have assigned the allowed customer group for customer hierarchy.
3.3 Creating Customer Hierarchy
Use
The purpose of this activity is to create a customer hierarchy.
Procedure
© SAP AG
Page 6 of 11
SAP Best Practices
Extended Rebate Processing with Customer (288): Configuration Guide
1. Access the activity using one of the following navigation options:
SAP ECC menu
Logistics  Sales and Distribution  Master Data  Business
Partner  Customer Hierarchy  Edit
Transaction code
VDH1N
2. On the Process Customer Hierarchy screen, make the following entries:
Field name
Description
User action and values
Customer hierarchy type
A
Validity date
Today’s date
Customer
GC-100
Sales organization
1000
Distribution channel
10
Division
10
Note
3. Choose Execute.
4. The following message appears: Hierarchy type A: There are no active assignments for
Today’s date.
5. On the Maintain Customer Hierarchy, Standard Hierarchy, Date: YYYY.MM.DD screen,
choose Create assignment.
6. In the Assignment area (right side of the screen), make the following sets of entries:
Field name
Description
User action and values
Note
Higher-level customer
Cust.
GC-100
Sales organization
1000
DistrChannel
10
Divis.
10
Customer
Cust.
GC-101
Sales organization
1000
DistrChannel
10
Divis.
10
7. Choose Transfer.
8. Choose Save.
9. Repeat step 5 – 8 with the following data:
Field name
Description
User action and values
Note
Higher-level customer
Cust.
GC-100
Sales organization
1000
DistrChannel
10
Divis.
10
© SAP AG
Page 7 of 11
SAP Best Practices
Extended Rebate Processing with Customer (288): Configuration Guide
Customer
Cust.
GC-102
Sales organization
1000
DistrChannel
10
Divis.
10
Result
You have created the customer hierarchy.
3.4 Defining Agreement Types
Use
The purpose of this activity is to define an agreement type for Building Block 288 - Extended
Rebate Processing with Customer.
Procedure
1. Access the activity using one of the following navigation options:
Transaction code
VB(2
IMG menu
Sales and Distribution  Billing  Rebate Processing 
Rebate Agreements  Define Agreement Types
2. On the Choose Activity dialog box, choose activity Define Agreement Types and then
choose Enter.
3. On the Change View “Rebate Agreement Types”: Overview screen, choose New Entries
and make the following entries:
Agreement
YGE1
Description
Ex Rebates – DirSale
Rappel Ampl–VentDir
Proposed valid-from
3
Proposed valid-to
2
Cond.type group
0004
ManAccrls Order type
B4
Manual accruals
Select
Payment procedure
A
Partial settlement
B3E
Reverse accruals
Select
Settlement periods
AM
Final settlement
B1E
Correction
B2
TextDetermProc.
03
Text ID
1000
4. Choose Save.
© SAP AG
Page 8 of 11
SAP Best Practices
Extended Rebate Processing with Customer (288): Configuration Guide
Result
You have defined agreement type YGE1.
3.5 Assigning Condition Type Groups to Rebate
Agreement Types
Use
In this configuration step, you assign rebate agreement type YGE1 to the standard condition
type group 0004. Condition type groups consist of condition types and condition tables for
rebate processing.
Procedure
1. Access the activity using one of the following navigation options:
Transaction code
VB(5
IMG menu
Sales and Distribution  Billing  Rebate Processing 
Rebate Agreements  Condition Type Groups  Assign
condition type groups to rebate agreement types
2. On the Change View “Allocation of Condition Type Group/Agreement”: Overview screen,
choose agreement type YGE1 and enter 0004 as the condition type group.
3. Choose Save.
Result
While assigning condition type group 0004 to agreement type YGE1, the following conditions
can be handled within a rebate agreement: B004 Customer Hierarchy and B005 Customer
Hierarchy/Material.
3.6 Settings for Agreement Types YGE1
Use
In this activity, you define the agreement types that are relevant for extended rebate
processing.
Procedure
1. Access the activity using one of the following navigation options:
Transaction code
SPRO
IMG menu
Sales and Distribution  Billing  Rebate Processing 
Extended Rebate Processing  Settings for Agreement Types
2. On the Change View “Extended Rebate Processing: Settings for Agreement Types”
screen, make the following entries for agreement type YGE1.
Field name
Description
User action and values
W/VAKEY
Check (Indicates whether the enhanced rebate
procedure is used for this agreement type.)
Indirect
Uncheck
Periodic
Check (Use this indicator to determine which
© SAP AG
Note
Page 9 of 11
SAP Best Practices
Extended Rebate Processing with Customer (288): Configuration Guide
time period is taken for the rebate settlement. If
this indicator is set, then only the sales volume or
sales for each settlement period are included for
the rebate settlement.)
Contract
Uncheck
3. Choose Save.
Result
The agreement type that is relevant for extended rebate processing is defined.
3.7 Setting up Variable Key for Rebate Settlement
(Agreement Type: YGE1)
Use
The variable key is an add-on to the rebate info structure S469. The rebate info structure
contains all rebate relevant information based on the rebate relevant invoices. Here you
maintain the composition of the variable key for the rebate processing of each agreement
type, and the assignment of the values to the corresponding fields in the credit memo. When
the rebate info structure S469 is updated, the values from the communication structures are
copied into the variable keys in the order specified by the counter. When the credit memo is
created, the corresponding values are copied from the variable key into the indicated target
fields of the structure KOMFKGN. When the rebate is settled, the system generates a line for
each variable key in the S469 of the credit memo instead of generating a line for each
condition.
Procedure
1. Access the activity using one of the following navigation options:
Transaction code
SPRO
IMG menu
Sales and Distribution  Billing  Rebate Processing  Extended
Rebate Processing  Set up Variable Key for Rebate Settlement
2. On the Change View “Extended Rebate: VAKEY Structure”: Details screen, choose New
Entries and enter the following values:
Field name
Description
User action and values
Agreement type
YGE1
Counter
10
Doc structure
MCVBRK
Document field
KUNAG
Target field
KUNAG
Constant
blank
Note
3. Choose Save.
Result
You created a variable key for agreement type YGE1 concerning the customer number. This
var. key enables you to perform a settlement according to the customer who was responsible
for the sales.
© SAP AG
Page 10 of 11
SAP Best Practices
Extended Rebate Processing with Customer (288): Configuration Guide
3.8 Activating Extended Rebate Processing
Use
To use the extended rebate processing the info structures S469 and S136 needs to be
activated.
Procedure
1. Access the activity using one of the following navigation options:
Transaction code
OMO1
IMG menu
Logistics - General  Logistics Information System (LIS) 
Logistics Data Warehouse  Updating  Updating Control 
Activate Update
2. In the Choose Activity dialog box, choose Sales and Distribution and Choose (F2).
3. On the Updating – Sales and Distribution: Info Structures screen, choose information
Structure S136 and choose Parameters… (F2).
4. In the Parameters dialog box, choose Synchronous updating (1).
5. Choose Copy (Enter).
6. Choose Information Structure S469 and choose Parameters… (F2).
7. In the Parameters dialog box, choose Synchronous updating (1).
8. Choose Copy (Enter).
9. Choose Save.
Result
The rebate information structures S136 and S469 can now be updated, when the system
generates rebate-relevant billing documents. This rebate information structure is the basis for
rebate settlement.
© SAP AG
Page 11 of 11