business process procedure

V2.470

July 2004

English

Extended Rebate Processing with Pendulum List (G73)

SAP AGNeurottstr. 1669190 Walldorf

Business Process Procedure

Germany

© SAP AG of 19

SAP Best Practices Extended Rebate Processing with Pendulum List (G73): BPP

Copyright

© Copyright 2004 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, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBM Corporation 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.

MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, 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 in several other countries all over the world. 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 of 19


Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

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 of 19


Abbreviations

R Required entry field

(used in the end-user procedures)

O Optional entry field


C Conditional field


© SAP AG of 19


ContentsExtended Rebate with Pendulum List..................................................................................................6

1 Purpose............................................................................................................................................ 6

1.1 Organization and Master Data...................................................................................................6

2 Business Process............................................................................................................................. 6

2.1 Creating Rebate Agreements.....................................................................................................6

2.2 Creating Requirements Data......................................................................................................9

2.3 Creating Sales Requests.........................................................................................................10

2.4 Creating Sales Confirmation - Entering Data Manually............................................................11

2.5 Updating Sales Data................................................................................................................12

2.6 Updating of Indirect Sales........................................................................................................13

2.7 Checking Sales Volume in Rebate Agreements.......................................................................14

2.8 Maintaining Periodic Partial Settlements..................................................................................16

2.9 Working with Pendulum List Reporting in BW..........................................................................17

© SAP AG of 19


Extended Rebate with Pendulum List

1 PurposeProducers (in this case, breweries), require their distributors to report on actual indirect sales by each of their different customers in addition.

The pendulum list is used between the wholesaler and the brewery. The wholesaler agrees to provide the brewery with sales data from its customers.

The system combines the data determined for each wholesaler in a pendulum list. You can use the pendulum list to request confirmation for the listed assortments.

Based on the indirect sales volume, rebate agreements will be concluded between the brewery and the indirect customers.

1.1 Organization and Master DataIn order to perform this business scenario, you need to install certain mater data.

Organization In G73, the main organization related to extended rebates with the pendulum list are shown in the table below. For detailed information regarding where you can set these organizations in the IMG, refer to the configuration guide.

Organization Value

Company code BP01

Sales organization BP01

Distribution channel 01

Division 01

Master DataBased on the organization, the following master data settings need to be made. For more information about this, refer to the configuration guide.

Master Data Value

Material Master B10010; B20010; B20020; B20030

Customer Master (Wholesaler) C10110

Customer Master (Object) C6502

Customer Master (Object Owner) C6503

2 Business Process

© SAP AG of 19


2.1 Creating Rebate Agreements

UseBased on an agreement, which was concluded between the indirect customer (for example: an owner of an object) and the brewery, a rebate agreement has to be created in the system. The rebate agreement is based on the indirect sales volume, which has to be reported by the wholesaler to the brewery using the pendulum list.

Procedure

1. Access the transaction choosing one of the following navigation options:

SAP R/3 menu Logistics Sales and Distribution Master Data Rebate Agreements Rebate Agreement Create

Transaction code VBO1

2. On the Create Rebate Agreement screen, make the following entries:

Field name Description R/O/C User action and values Comment

Agreement type

Extended rebate indirect sales

YGE2

3. Choose Enter.

In some cases here a dialog box appears. On the Organizational Data dialog box enter the following values:


Sales Organization

BP01

Distribution Channel

01

Division 01

4. Choose Copy.

5. On the Create Ex. Reb -.Indir Sale : Overview Agreement screen, make the following entries:


Rebate recipient

Customer C6503

Currency EUR

Settlement Periods

Monthly settlement AM

Validity For example, 01.01.2004

© SAP AG of 19


period

to For example, 31.12.2004

6. Choose Conditions.

7. On the Ex. reb.Indir Sale: Overview Material Rebate screen, enter the following values:


First Item:

Material B10010

Amount Rebate amount 0,50 -

Unit currency EUR

per 1

Unit Unit of measurement CT

Second Item:

Material B20010


Unit currency EUR

per 1


Third Item:

Material B20020


Unit currency EUR

per 1


Fourth Item:

Material B20030


Unit currency EUR

per 1


Make sure that the accruals amounts are similar to the rebate amounts. If not, adjust the accruals amounts to the rebate amounts.

8. Save your entries. The system message Ex Reb – Indir Sale X created is displayed.

© SAP AG of 19


9. Note down the number of the rebate agreement: ______________

2.2 Creating Requirements Data

UseIn this step you determine which data is required from which wholesaler and the corresponding objects within a certain period of time. In this case the periods for which the sales data are requested are always one month, and the request date is the last day of a month. This data is partly entered into the system via eCATT during the installation and in the subsequent step of the business procedure to show how the user determines requirements data manually.

Procedure


SAP R/3 menu Logistics Sales and Distribution Pendulum List Indirect Sales Requirements Data Create

Transaction code /BEV4/PLAN

2. On the Initial Screen Maintenance of request data screen, make the following entries:

Field name Description User action and values Comment

Sales Org. BP01

Distri.Channel 01

Division 01

Wholesaler C10110

3. Choose Recreate.

4. On the Recreate Request Data screen, make the following entries:


Object Number C6502

Customer C6503

Valid from 01.01.2004

Valid to 31.12.2005

Request Date 31.01.2004

Period ID 01

Output 01

5. Choose Enter.

© SAP AG of 19


If a data record exists already for the entered key, choose another validity date. The request date must fit the validity period and is always at the end of a reporting period.

6. Select the line you created before and choose Items.

7. On the Recreate Item Data screen, make the following entries:


Origin A

Key Field B10010; B20010; B20020; B20030

incl excl 1

Requires C 1

8. Choose Enter and save your entries.

2.3 Creating Sales Requests

UseThe brewery creates a document about the required sales data in the system in step 2.2. In this step a sales request is created which can be sent to the wholesaler as a reminder.

Procedure


SAP R/3 menu Logistics Sales and Distribution Pendulum List Indirect Sales Sales Request Request Run

Transaction code /BEV4/PLGN

2. On the Initial Screen Maintenance of requirements data screen, make the following entries:


Sales Organization:

BP01

Distribution Channel:

01

Division: 01

Wholesaler: C10110

Object: C6502

© SAP AG of 19


Customer: C6503

Request Date:

The request date can be gathered from the appropriate requirement, you created in section 2.2, for example: 31.01.2004

Monthly –always last day of a month from the current reporting period

Create Output Mediums

Delete the flag

3. Choose Execute.

4. On the Generate Request Data screen a log is displayed, which provides information about the wholesaler, object, customer, material, request data, and the order number is displayed.

5. In order to forward the request data to the wholesaler, you can either print this list and send it by post – choose List Print – or you can save the data on a file and send it via e-mail – choose List Save/Send File.

2.4 Creating Sales Confirmation - Entering Data Manually

PrerequisitesThe brewery has received the requested sales volume information from the wholesaler via mail, telephone, letter, or fax.

UseOnce the brewery has received the sales volume information from the wholesaler, the data will be entered manually into the system as a sales confirmation.

Procedure


SAP R/3 menu Logistics Sales and Distribution Pendulum List Indirect Sales Sales Confirmation Manual Data Entry

Transaction code /BEV4/PLER

2. On the Initial Screen Manual Entry of Reported Sales screen, make the following entries:


Sales Org. BP01

Distr. Channel

01

© SAP AG of 19


Division 01

Wholesaler C10110

Rep. Interval from

Enter here the start date of the request period from section 2.3. For example: 01.01.2004

to Enter here the end date of the request period from section 2.3. For example: 31.01.2004

Unit of Measure

PC

3. Choose New in the upper left corner of the screen.

4. On the Enter Reported Sales screen enter the following data for the first combination of wholesaler C10110, object C6502, customer C6503 (which is the object owner) and material B10010:


Quantity 1500

5. Choose Material in order to get the data entry screen for the remaining materials: B20010, B20020, B20030.

6. Enter the following quantities per material:

B20010 – 3000 PC B20020 – 5000 PC B20030 – 1500 PC

7. Save your entries.

2.5 Updating Sales Data

UseAfter the sales data has been entered in the brewery’s system, the data has to be updated and as a result PLPA orders will be created in the system. Furthermore, the data will be updated in table S473, which is the basis for further processing of extended rebates with indirect sales.

Procedure


SAP R/3 menu Logistics Sales and Distribution Pendulum List Indirect Sales

© SAP AG of 19


Sales Confirmation Update

Transaction code /BEV4/PLKM

2. On the Update Entered Sales screen enter the following data:


Sales org BP01

Distribution Channel

01

Division 01

Wholesaler C10110

Display only errors

x

3. Choose Execute.

4. On the Pendulum List: Create Indirect Orders screen, you will get information about the updated data (wholesaler, object, customer, material no., reported on – date, document number of the indirect order).

5. Go back.

2.6 Updating of Indirect Sales

UseAn update of indirect sales for rebate processing takes place, based on confirmation sales data of the pendulum list module. The program BON_ENH_UPDATE is used to update indirect sales for the extended rebate processing by creating indirect billing documents. Based on the indirect billing documents, the info structure S469 (table in extended rebate module) will be updated. This info structure provides the rebate basis.

Procedure 1. Access the transaction choosing one of the following navigation options:

SAP R/3 menu Logistics Sales and Distribution Billing Rebates Extended Rebate Processing Update of Indirect Sales

Transaction code RBT_ENH_ACT

2. On the Update of Indirect Sales screen, make the following entries:


Month Here enter the month, you used as period in section

© SAP AG of 19


2.4.For example 01.2004

Sold to Party C6503

Sales org BP01

Distr Channel 01

Division 01

Test Mode Delete flag

3. Choose Execute. An indirect billing document will be created in the background.

4. After a successful update run, the following message appears: Indirect billing document XXXXXXXX created.

5. Note the invoice number: _____________

6. Choose Continue.

7. Go back.

ResultOnce the indirect billing documents were created automatically, the rebate related info structure S469 is updated with the appropriate sales volume data, which are the basis for the extended rebate processing.

2.7 Checking Sales Volume in Rebate Agreements

UseThe updated sales confirmation data from the pendulum list module are now visible as sales volume in the rebate agreement you created in step 2.1. Starting with the rebate agreement, you always get the latest information about the sales volume, which was generated between the object owner C6503 and the wholesaler C10110. You get an overview of the relevant billing documents and the condition base value.

PrerequisitesIt is required, that the sales volume has to be current. The sales volume is not current if, for example, the rebate agreement was created retroactively. That means that you create a rebate agreement for which the validity start date lies in the past. The system then should take into account all the rebate-relevant billing documents that were created between the validity start date and the date you created the rebate agreement. As long as you do not run an update for the previous billing documents, you will get the following message whenever you enter the rebate agreement both in display and in change mode: The sales volume for agreement is not current. In that case, you have to run an update. The following steps will lead you through that process:

1. Access the transaction choosing one of the following navigation option:

© SAP AG of 19


SAP R/3 menu Logistics Sales and Distribution Billing Rebates Update Billing Documents

Transaction code VBOF

2. On the Update billing document screen, make the following entries:

Field name User action and values Comment

Agreement Enter the number of the rebate agreement, for which the sales volume has to be updated.

Validity end date before

31.12.9999



Division 01

Posting date Today’s date

FI-Doc.type ZP

Error Set flag

Processing Choose Drill-down

Control Choose none of the possibilities

3. Choose Execute.

4. If errors occur during the update run, check the log.

Procedure


SAP R/3 menu Logistics Sales and Distribution Master Data Rebate Agreements Rebate Agreement Change

Transaction code VBO2

2. On the Change Rebate Agreement screen, enter the number of the rebate agreement, which was created in section 2.1

3. Choose Enter.

4. On the Change Ex Rebates – DirSales X: Overview Agreement screen, choose the following menu path: Rebate Payments Sales Volume

5. A listing of all rebate relevant sales volumes appears up to today’s date.

6. For further information choose Back and choose Verification Level.

7. On the next screen choose Scope of statement.

© SAP AG of 19


8. A dialog box Set verification level appears. Leave the input field blank and choose continue.

9. On the Change Ex Rebates – DirSale 6: Overview Agreement screen you get a list about the current sales volume on billing document level.

10. Check if the billing document you created in section 2.6 is displayed.

11. In order to get different views on the current sales volume, choose Scope of Statement again and select another verification level.

2.8 Maintaining Periodic Partial Settlements

UseIn this process the rebate agreement, based on indirect sales, should be settled partially periodically. In periodic partial settlement, you can refer to specific periods for settlement. This means that only the amount accumulated up to the settlement date is taken into account, even if partial payment is made only later. In this building block, a monthly periodic settlement takes place.

You want to carry out partial settlement for January. You know, however, that revenues will occur in February, although their date of services rendered is in January. You can now carry out periodic partial settlement in the middle of February. Enter a calendar year as the settlement period with the end of each month as the settlement dates. Enter January 31 as the concrete settlement date. The revenues in February, with a date of services rendered that falls in January, are included in the settlement. New revenues in February are not included.

Procedure


SAP R/3 menu Logistics Sales and Distribution Billing Rebates Extended Rebate Processing Extended Rebate Settlement

Transaction code RBT_ENH_VB7

2. On the Settlement of Extended Rebate Agreements screen, make the following entries:

Field name User action and values Comment

Rebate Agreement Enter the number of the rebate agreement, you created in section 2.1

Validity end date before

31.12.9999



Division 01

Settlement period AM

Settlement date Enter here the last day of the month, that should be settled (refer to period

© SAP AG of 19


from section 2.6)

Rebate Settlement Status

open

Actions Carry Out Partial Settlement

3. Choose Execute.

4. A rebate credit memo should have been created. Note the invoice number: __________

5. The created rebate credit memo is displayed in the rebate agreement. In order to check this, navigate to the rebate agreement (Transaktion VBO1). Starting from the Change Ex Rebates – DirSale X: Overview Agreement screen, choose the following menu path: Rebate Payments Rebate Documents.

6. On the dialog box Select Rebate Document Types, choose Enter.

7. The previously created rebate credit memos will be displayed on the Partial Settlement for Rebate Agreement X screen. By choosing the invoice numbers, you can navigate to the original documents.

2.9 Working with Pendulum List Reporting in BW

PurposeSAP Business Information Warehouse (BW) reporting offers many possibilities to analyze data. In this document, we show several examples on how to analyze data in BW.

PrerequisitesPossibile analyses depend on the data, which has been uploaded into BW from the source systems. Make sure that data has been updated to BW.

Procedure

1. Carry out the following activities in the BW system:Access the transaction choosing the following navigation option:

SAP Menu Expand the Favorites folder

2. Choose the entry Pendulum List ( or the name that you assigned to the query).

3. The internet browser of your PC is started. If the Enter Network Password dialog box appears, enter your SAP BW user name and password and choose OK.

4. The Variables entry view of the report opens in the Internet browser.

5. For Customer Group ( this entry is manadtory) enter 02.

© SAP AG of 19


6. For the other variables make the selections you want or leave the fields empty as these entries are not mandatory.

7. Choose Execute.The Pendulum List report is displayed.

8. To show the values for one customer only, choose a customer in the table area, then choose Keep Filter Value.

9. The report displays the figures per article according to the product hierarchy. To expand a hierarchy node, choose the icon (triangle) left of the node . The figures for the next lower level node are displayed.

© SAP AG of 19