310 BPP en in Complete

EHP4 for SAP ERP 6.0

September 2010

English

Indirect Sales with Extended Rebate Processing (310)

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermany

Business Process Documentation

SAP Best Practices Indirect Sales with Extended Rebate Processing (310): BPD

Contents

1 Overview................................................................................................................................ 5

2 Prerequisites.......................................................................................................................... 5

2.1 Master Data and Organizational Data.............................................................................5

2.2 Roles............................................................................................................................... 5

2.3 Preliminary Steps............................................................................................................6

2.3.1 Changing Condition Record Valid From Date..........................................................6

3 Process Overview Table.........................................................................................................7

4 Process Steps........................................................................................................................ 8

4.1 Creating Rebate Agreements (Optional).........................................................................8

4.2 Creating Requirements Data.........................................................................................10

4.3 Creating Sales Request................................................................................................12

4.4 Creating Sales Confirmation by Manual Data Entry or Automatic Import......................13

4.4.1 Procedure – Manual Data Entry.............................................................................14

4.4.2 Procedure – Automatic Data Import (Optional)......................................................15

4.5 Updating Sales Data.....................................................................................................17

4.6 Updating of Indirect Sales.............................................................................................18

4.7 Updating Billing Documents..........................................................................................19

4.8 Checking Sales Volume in Rebate Agreements............................................................20

4.9 Maintaining Periodic Partial Settlements.......................................................................21

4.10 Executing CO-PA Reports on Indirect Sales..............................................................23

4.11 Analyzing the Sales Data Using SIS Reports............................................................24

5 Follow-Up Processes............................................................................................................26

6 Appendix.............................................................................................................................. 26

6.1 Reversal of Process Steps............................................................................................26

6.2 SAP ERP Reports.........................................................................................................27

© SAP AG Page 2 of 29


Indirect Sales with Extended Rebate Processing

1 OverviewProducers require their distributors to report on actual indirect sales by each of their various customers. In addition, sales have to be broken down by individual materials.

The pendulum list is used between a wholesaler and a producer. The wholesaler agrees to provide the producer with sales data from their 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. Customer-related data can be obtained without using CRM and is then analyzed by a report from the Sales Information System. In this business process procedure, sales data for chocolate is collected via the pendulum list and then analyzed.

Furthermore rebate agreements are concluded between the producer and the indirect customers based on the indirect sales volume.

2 Prerequisites2.1 Master Data and Organizational DataIn 310 the main organization, which is related to Indirect Sales with Extended Rebate Processing, are shown in the table. For detailed about where to set these organizations in the IMG, refer to the configuration guide.

Organization Value

Company code 1000

Sales organization 1000

Distribution channel 10

Division 10

Based on the organization, you need to make the appropriate master data settings. The following table shows the master data which is used in 310. For detail about how to implement the master data listed below, refer to the configuration guide.

Master Data Value

Material Master (Food – Trading Goods) GK-200, GK-201

Customer Master (Wholesaler - Food) WE1001

Customer Master (Objects - Food) WE1002

Customer Master (Object Owner - Food) WE1003

2.2 Roles

UseThe following roles must have already been installed to test this scenario in the SAP NetWeaver Business Client (NWBC). The roles in this Business Process Procedure must be assigned to the user or users testing this scenario. You only need these roles if you are using the NWBC interface. You do not need these roles if you are using the standard SAP GUI.

PrerequisitesThe business roles have been assigned to the user who is testing this scenario.

Business role Technical name Process step



Sales Administrator SAP_NBPR_SALESPERSON-S

Changing Condition Record Valid From Date

Employee (Professional User)

SAP_NBPR_EMPLOYEE-S Assignment of this role is necessary for basic functionality.

Billing Administrator

SAP_NBPR_BILLING-S Creating Rebate Agreements

CPWD: Sales Administrator

SAP_NBPR_SALESPERSON_CPWD-S

Creating Requirements Data



Creating Sales Request



Creating Sales Confirmation by Manual Data Entry or Automatic Import

Procedure – Manual Data Entry

CPWD: ALE Administration

SAP_NBPR_IT_ADMIN_CPWD-S Procedure – Automatic Data Import




Procedure – Automatic Data Import



Check the log



Updating Sales Data



Updating of Indirect Sales


SAP_NBPR_BILLING-S Updating Billing Documents


SAP_NBPR_BILLING-S Checking Sales Volume in Rebate Agreements


SAP_NBPR_BILLING-S Maintaining Periodic Partial Settlements



Executing CO-PA Reports on Indirect Sales



Analyzing the Sales Data Using SIS Reports

2.3 Preliminary Steps

2.3.1 Changing Condition Record Valid From Date

Procedure

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

Option 1: SAP Graphical User Interface (SAP GUI)

SAP ECC menu Logistics Sales and Distribution Master Data Conditions Select Using Condition Type Change



Transaction code VK12

Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role

Business role Sales Administrator

(SAP_NBPR_SALESPERSON-S)

Business role menu Sales Pricing Pricing Conditions Change Condition Record

2. In the Condition type field, enter JEXP.

3. Choose Enter.

4. In the Key Combination dialog box, choose Material and choose Enter.

5. On the Change IN: A/R BED % (JEXP): Selection screen, enter Sales Organziation 1000, Distribution Channel 10 and enter Materials as GK-200 and GK-201 in the Material field and choose Execute.

6. For these entries, change the Valid From dates to first date of last year, for example, 01.01.2010.

7. Choose Save. Confirm any messages that appear with Enter.

8. Repeat the above step for the condition type JECS and JHCS.

9. Choose Back to return to the SAP Easy Access screen (SAP GUI)

Or

Choose Exit (Shift+F3) and confirm the Business client message with Yes to return to SAP Home (SAP NetWeaver Business Client).

3 Process Overview Table

Process stepExternal process reference

Business condition

Business role

Trans-action code

Expected results

Creating Rebate Agreements


VBO1Creating Rebate Agreements

Creating Requirements Data


/n/BEV4/PLANCreating Requirements Data

Creating Sales Request


/n/BEV4/PLGNCreating Sales Request


Procedure – Manual Data Entry


/n/BEV4/PLER Creating Sales Confirmation by Manual Data Entry or Automatic Import

Procedure – Manual Data



Entry




/n/BEV4/PLEA



Updating Sales Data


/n/BEV4/PLKM Updating Sales Data

Updating of Indirect Sales


RBT_ENH_ACT Updating of Indirect Sales

Updating Billing Documents


VBOFUpdating Billing Documents

Checking Sales Volume in Rebate Agreements


VBO2

Checking Sales Volume in Rebate Agreements

Maintaining Periodic Partial Settlements


RBT_ENH_VB7

Maintaining Periodic Partial Settlements



KE30




MCSI


Clearing Collection

Accounts Receivable (157)

See scenario no. 157


Closing Operations SD

Sales: Period End Closing Operations (203)



4 Process Steps 4.1 Creating Rebate Agreements (Optional)

Use



Based on an agreement, which was concluded between the indirect customer (for example: an owner of an object) and the producer, 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 producer using the pendulum list.

This step is only needed if it is the first time you run this scenario.

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


SAP ECC menu Logistics Sales and Distribution Master Data Agreements Rebate Arrangement Create

Transaction code VBO1


Business role Billing Administrator

(SAP_NBPR_BILLING-S)

Business role menu Sales Rebate Process Create Rebate Agreement

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

Field name Description User action and values Comment

Agreement type Extended rebate indirect sales

YWE2

3. Choose Enter.

In some cases here a dialog box appears. In the Organizational Data dialog box, make the following entries: (When the dialog box doesn’t appear, you can ignore following steps.)


Sales Organization

1000

Distribution Channel

10

Division 10

4. Choose Copy.

5. On the Create Ex Rebates - IndSale : Overview Agreement screen, make the following entries:


Rebate recipient Customer WE1003

Currency INR

Settlement Periods

Monthly settlement

AM

Validity period For example, 01.01.2011

First day of current year



to For example, 31.12.2010

Last day of current year

6. Choose Conditions (F9).

7. On the Create Ex. Rebates - IndSale : Overview Material Rebate (BO02) screen, make the following entries and choose Enter:


First Item:

Material GK-200

Amount Rebate amount 0.55-

Unit currency INR

per 1

UoM Unit of measurement NOS

Second Item:

Material GK-201

Amount Rebate amount 1.1-

Unit currency INR

per 1

UoM Unit of measurement NOS

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

8. Choose Save. The system message Ex Rebates – IndSale X created is displayed.

9. Note down the number of the rebate agreement:

10. Choose Back to return to the SAP Easy Access screen.

Or


ResultRebate agreement is created.

4.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 is 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 following steps of the business procedure to show how the user manually determines the data requirements.





SAP ECC menu Logistics Sales and Distribution Pendulum List Indirect Sales Requirements Data Create

Transaction code /n/BEV4/PLAN


Business role CPWD: Sales Administrator (SAP_NBPR_SALESPERSON_CPWD-S)

Business role menu Sales Indirect Sales New Creation of Sales Request Data

2. On the Initial Screen Maintenance of Request Data screen, make the following entries:


Sales Org. 1000

Distr.Channel 10

Division 10

Wholesaler WE1001

3. Choose Recreate (F5).

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


Object Number WE1002

Customer WE1003

Valid from For example,

01.09.2011

First day of a month

If request has already been created for this month, use the next month.

Valid to For example,

30.09.2011

Last day of a month


Request Date For example,

30.09.2011

Last day of a month


Period ID 01

Output 01



If the error message Error occurred when determining period identifier (Msg. no. /BEV4/PLPEND068) displays, means the factory calendar YW is not activated. We change any value on Change Factory Calendar: Details screen (transaction code: SCAL choose Factory calendar and choose Change. On next screen mark YW and choose Change), for example, we set the Holiday Calendar ID to 01 for calendar YW, choose Save, after that we delete 01 from the Holiday Calendar ID field and choose Save again, and then the step works.

5. Choose the line of requirements data you have created before.

6. Choose (NWBC: More…) Goto Items. Choose Enter if warning message appears.

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


First Item:

Origin A

Key Field GK-200

Incl./Excl. 1

Requires Confirmation

1

Second Item:

Origin A

Key Field GK-201

Incl./Excl. 1

Requires Confirmation

1

8. Choose Save.


Or


ResultRequirements Data is created.



4.3 Creating Sales Request

UseThe producer creates a document about the required sales data in the system in the Creating Requirements Data section. In this step a sales request is created, which can then be sent to the wholesaler as a reminder.

Procedure



SAP ECC menu Logistics Sales and Distribution Pendulum List Indirect Sales Sales Request Request Run

Transaction code /n/BEV4/PLGN



Business role menu Sales Indirect Sales Report Generation of Request

2. On the Generate Request data screen, make the following entries:


Sales Organization:

1000

Distribution Channel:

10

Division: 10

Wholesaler: WE1001

Object: WE1002

Customer: WE1003

Request Date:

The request date can be gathered from the corresponding

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



requirement you created in the section Creating Requirements Data

Create Output Mediums

Remove 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.

5. To forward the request data to the wholesaler, either you print this list and send it through the mail by choosing (NWBC: More… List Print, or you can save the data on a file and send it via e-mail by choosing (NWBC: More… List Save/Send File….


Or


ResultSales Request is created.

4.4 Creating Sales Confirmation by Manual Data Entry or Automatic Import

PrerequisitesThe producer has received the requested sales volume information from the wholesaler either as a data file or in written or verbal form via telephone, letter or fax.

UseOnce the producer has received the sales volume information from the wholesaler, the data is entered into the system. There are two possible ways how to enter the data, depending on the format the data is made available by the customer. If the data is provided within a data file, it can be loaded automatically into the system. If the sales volume information is provided via telephone, letter or fax, the data has to be entered manually into the system. The entered data is named as sales confirmation.



In the following both ways of data entry are described. When you execute this Business Process you have to go for one of these.

4.4.1 Procedure – Manual Data Entry



SAP ECC menu Logistics Sales and Distribution Pendulum List Indirect Sales Sales Confirmation Manual Data Entry

Transaction code /n/BEV4/PLER



Business role menu Sales Indirect Sales Manual Entry Confirmation

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


Sales Org. 1000

Distr. Channel

10

Division 10

Wholesaler WE1001

Rep. Interval from

Enter here the start date of the request period from the section Creating Requirements Data

To Enter here the end date of the request period from the section Creating Requirements Data

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

Unit of Measure

NOS

3. Choose Enter (F5) in the upper middle corner of the application bar.

4. On the Enter Reported Sales screen, enter the following data for the first combination of wholesaler WE1001, object WE1002, customer WE1003 (which is the object owner), and material GK-200.


Quantity 1500

Unit of Measure

NOS

When the system is able to identify the sales request data you want now enter the confirmed sales volume data for, the object no., customer no., material no. and the ‘reported on’ dates are already there. Otherwise you have to enter it like described in step 4 and 5.

5. Enter Report.Day, Rep. Month and Report.Year.



6. Choose Next Material (F6) and repeat the step 4 - 5 for material GK-201.

7. Choose Save.


Or


4.4.2 Procedure – Automatic Data Import (Optional)

PreresuisitesAs a prerequisite you have to put the data file SalesVolDataFood01.TXT from \Misc\Food_and_Beverage\XX (XX is the name of country) in the documentation DVD, which includes the sales volume data of the indirect customers, into a special directory of your application server: \\<servername>\sapmnt\<system name>\SYS\global



SAP ECC menu Logistics Environment, Health and Safety Basic Data and Tools Tools Data Transfer Upload File

Transaction code CG3Z


Business role CPWD: ALE Administration

(SAP_NBPR_IT_ADMIN_CPWD-S)

Business role menu Monitoring Upload file

2. On the Upload File: Parameters dialog box, enter the following entries:


Source file on front end

<the path of the inbound file>

for example:

C:\ SalesVolDataFood01.TXT

Target file on application server

\usr\sap\<system name>\sys\global\SalesVolDataFood01.TXT

The target sever, for example, \usr\sap\RDE\sys\global\SalesVolDataFood01.TXT

Transfer format for data

BIN

3. Choose Upload (Shift + F2). If file has been uploaded, choose Overwrite file.

4. The system show message File xxxx\ SalesVolDataFood01.TXT transferred to /usr/sap/<system name>/SYS/global/ SalesVolDataFood01.TXT on the bottom of the screen.



Whenever you want to create your own data file, make sure that your file follows the recommendation listed in the files: PLDDEBMATS.TXT and PLDMAT_S.TXT. You can find above files and the sample of SalesVolDataFood01.TXT from the folder \Misc\Food_and_Beverage\XX (XX is the name of country) in the documentation DVD.

Procedure

1. To start the automatic data import, access the transaction choosing one of the following navigation options:


SAP ECC menu Logistics Sales and Distribution Pendulum List Indirect Sales Sales Confirmation Automatic Import

Transaction code /n/BEV4/PLEA



Business role menu Sales Indirect Sales Reported Sales Import

2. On the Import Customer Sales screen, make the following entries:


File Name SalesVolDataFood01.TXT

File Path \usr\sap\<system name>\sys\global\

The target sever, for example, \usr\sap\RDE\sys\global\

If you want to run a simulation first, you have to set the flag Import Simulation and Simulation Order Creation. For the real run, you need to delete this flag. We recommended running a simulation first.

3. Choose Execute.

4. Check the log by using one of the following navigation options:


SAP ECC menu Logistics Sales and Distribution Pendulum List Indirect Sales Sales Confirmation Display Import Logs

Transaction code /n/BEV4/PLUP



Business role menu Sales Indirect Sales Logs Sales Pendulum Lists



5. Choose Execute.

6. Choose your log from the Transfer Number dialog box.

7. On the Display Sales Log screen you can expand the sub trees to see the whole log.


Or


After a successful real run a key in the TXT file changed from SB to SV (for example, DEBSB to DEBSV or MATSB to MATSV) once this key changed, it is no longer possible to read this file again. If you want to execute this procedure again, you have to use the original file. Make sure that you always use the correct reporting periods.

ResultSales Confirmation is imported.

4.5 Updating Sales Data

UseAfter the sales data has been entered in the producer’s system, the data has to be updated and as a result PLPR orders are created in the system. While generating this document the info structures S474 and S941 are updated. In this scenario only amounts are confirmed –but no revenues.

WARNING: During the installation of the 303 building block, you are asked to maintain the info structure S941. However, if you already had an existing S941 info structure before the installation of 303, you were asked to proceed with the installation using a new number for the info structure and all subsequent steps that referenced S941. If you used a number other than S941, you need to proceed throughout the 310 BPD using the same info structure number you chose in 303. It is important that you use the same info structure as maintained in 303. If this is not done correctly, errors occur and the BPD cannot be completed successfully.



SAP ECC menu Logistics Sales and Distribution Pendulum List Indirect Sales Sales Confirmation Update

Transaction code /n/BEV4/PLKM



Business role menu Sales Indirect Sales Update

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




Sales org 1000

Distribution Channel 10

Division 10

Wholesaler WE1001

Display Only Errors X

Simulation Order Creation X

If you want to run a simulation first, you have to set the flag Update Simulation. For the real run, you need to delete this flag.We recommended to run a simulation first.

3. Choose Execute.

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


Or


ResultSales data is updated.

4.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) is updated. This info structure provides the rebate basis.

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


SAP ECC menu Logistics Sales and Distribution Billing Rebate Extended Rebate Processing Update of Indirect Sales

Transaction code RBT_ENH_ACT



Business role menu Sales Indirect Sales Update of Indirect Sales

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


Month For example: if in chapter 4.4 you enter 01.01.2010 as from and 31.01.2010 as to date, then enter 2010.01 here

09.2011

<month, you used as period in section Creating Sales Confirmation by Manual Data Entry or Automatic Import>

Sold to Party

WE1003

Sales org 1000

Distr Channel

10

Division 10

Test Mode Delete flag

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

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

5. Note the invoice number: Indirect billing document 90000136 created

6. Choose Continue.


Or


Result



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

4.7 Updating Billing Documents

UseThe updated sales confirmation data from the pendulum list module is now visible as sales volume in the rebate agreement you created in the section Create Rebate Agreement. Starting with the rebate agreement, you always get the latest information about the sales volume, which was generated between the object owners WE1003 and the wholesaler WE1001 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 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 lead you through that process:

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


SAP ECC menu Logistics Sales and Distribution Billing Rebate Update Billing Documents

Transaction code VBOF




Business role menu Sales Rebate Process Rebate: Update Billing Documents

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


Agreement <Number of the rebate agreement, for which the sales volume has to be updated>

Validity end date before

31.12.9999

Sales organization

1000

Distribution channel

10

Division 10

Posting date <Today’s date>

FI-Doc.type ZP

Error Set flag




Processing Choose Drill-down

Control Choose none of the possibilities

Test Deselect

Changed agreements

Deselect

3. Choose Execute.

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


Or


ResultBilling Documents are updated.

4.8 Checking Sales Volume in Rebate Agreements

Procedure



SAP ECC menu Logistics Sales and Distribution Master Data Agreements Rebate Agreement Change





Business role menu Sales Rebate Process Change Rebate Agreement

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

3. Choose Enter.

4. On the Change Ex Rebates – IndirSales X: Overview Agreement screen, choose the following menu path: (NWBC: More …) Rebate Payments Sales Volume

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



6. For further information choose Back and choose following menu path: (NWBC: More… ) Rebate Payments Verification Level.

7. On the next screen choose Scope of Statement.

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

9. On the Change Ex Rebates – IndirSale X: 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 Updating of Indirect Sales is displayed.

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


Or


ResultSales Volume in Rebate Agreements is checked.



4.9 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 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 1. Access the transaction choosing one of the following navigation option:


SAP ECC menu Logistics Sales and Distribution Billing Rebate Extended Rebate Processing Extended Rebate Settlement

Transaction code RBT_ENH_VB7




Business role menu Sales Rebate Process Settlement Extended Rebate Agreement

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


Rebate Agreement

<number of the rebate agreement, you created in the section Create Rebate Agreement>

Validity end date before

31.12.9999

Sales organization

1000

Distribution channel

10

Division 10

Settlement period

AM

Settlement date

<the last day of the month that should be settled (refer to period from the section Updating of



Indirect Sales)>

Rebate Settlement Status

open Deselect Released

Actions Carry Out Partial Settlement

3. Choose Execute.

4. Choose the Messages in the upper right part of the screen. Check the information for the period, which settled in the step before.

5. A rebate credit memo should have been created. Note the invoice number: 90000137



6. The created rebate credit memo is displayed in the rebate agreement. To check this, navigate to the rebate agreement by choosing one of the following navigation options:


SAP ECC menu Logistics Sales and Distribution Master Data Agreements Rebate Agreement Change





Business role menu Sales Rebate Process Change Rebate Agreement

7. On the Change Rebate Agreement screen, enter the number of the rebate agreement, which was created in section Creating Rebate Agreements and choose Enter.

8. Starting from the Change Ex Rebates – IndirSale X: Overview Agreement screen, choose the following menu path: (NWBC: More… ) Rebate Payments Rebate Documents.

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

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


Or


ResultA billing document is created.



4.10 Executing CO-PA Reports on Indirect Sales

Use By executing the report provided for this scenario, you can analyze your indirect sales figures (which you created before with PLPR orders) by wholesaler. Key figures shown are sales quantity and revenue.

In this scenario, only quantities are reported to the manufacturer by the wholesaler. In reality, this is the most probable case as reporting both sales quantities and revenues would enable the manufacturer to draw conclusions regarding the pricing policy of the wholesaler. Nevertheless, the report YWINDSAL offers both key figures because the pendulum list functionality supports both quantity and revenue transfer.

PrerequisitesPendulum list data must have been entered into the system.

Procedure1. Access the activity using one of the following navigation options:


SAP ECC menu Accounting Controlling Profitability Analysis Information System Execute Report

Transaction code KE30


Business role CPWD: Sales Administrator

(SAP_NBPR_SALESPERSON_CPWD-S)

Business role menu Sales Indirect Sales Execute profitability report

2. If the Set Operating Concern dialog box appears, enter 10IN (or your personalized operating concern), choose costing based, and choose Continue.

3. On the Run Profitability Report: Initial Screen, mark report YWINDSAL and choose Execute.

4. On the Selection: Indirect Sales screen, make at least the following mandatory entries:


To Fiscal Year

<according to your needs, for example, current fiscal year>

From Fiscal Year

<according to your needs, for example, current fiscal year>

To Period 012




From Period 001

5. Specify the remaining selection criteria as desired.

6. Choose Execute (F8).

7. If a dialog box displays a warning that selection may take a while, choose Yes.


Or


Result Sales quantities and, if they have been provided, also revenues are displayed for every wholesaler.

The report enables you to analyze the data by various criteria such as, for example, customer or product. To choose a desired characteristic, just double-click it in the Navigation column. You can also combine two characteristics, for example evaluate the business data by customer for every single product. To do so, choose Product in the Navigation column, then position the cursor on one of the reporting lines displayed and drag-and-drop that line onto characteristic Customer in the Navigation column. An additional line appears under Product, and you can scroll through the existing products using the up/down arrows displayed in the two columns to the right of the Navigation column. You can undo the selection by choosing the new line and then choosing Cancel selection from the context menu.

Note that if you specified a characteristic (value or range) on the selection screen of the report, this characteristic is not available for drilldown in the report.

4.11 Analyzing the Sales Data Using SIS Reports

Use Based on info structure S941, you can analyze your indirect sales figures by wholesaler.

WARNING: During the installation of the 303 building block, you are asked to maintain the info structure S941. However, if you already had an existing S941 info structure before the installation of 303, you were asked to proceed with the installation using a new number for the info structure and all subsequent steps that referenced S941. If you used a number other than S941, you need to proceed throughout the 310 BPD using the same info structure number you chose in 303. It is important that you use the same info structure as maintained in 303. If this is not done correctly, errors occur and the BPD is not able to be completed successfully.

PrerequisitesPendulum list data must have been entered into the system.

Procedure1. Access the activity using one of the following navigation options:


SAP ECC menu Logistics Sales and Distribution Sales Information



System Standard Analyses User-defined analysis

Transaction code MCSI



Business role menu Sales Indirect Sales Call Standard Analyses of Sales

2. From the Info Structure dialog box, double-click the relevant info structure (S941 or your personalized info structure).

3. On the Standard analysis for info structure S941: Selection screen, make the following entries:

Field Description User action and values Comment

Sales Organization

1000

Distribution Channel

10

Division 10

Sold-to-Party

WE1003

Month 01.2010 to 12.2010 Months of currenty year

4. Choose Execute.

5. You get information about the sales quantities from indirect sales on sales organization level.

6. Double-click the characteristic Dom. Sales Org. As a result; the sales quantities are displayed on the next lower level, Distribution Channel. By double-clicking the characteristic again (in that case, Direct Sales), the next deeper level is displayed, and so on. You can drill down the sales quantities to the following level: Sales Org., Distr. Channel, Division, Sold-to party, Ship-to Party, Wholesaler, Material, Vol. Rebate group, Plant, Month.


Or


Result



This SIS analysis always give the latest information regarding the indirect sales volume, which is available in the info structure once the pendulum list confirmation data is entered in the system and updated.

5 Follow-Up ProcessesYou have finished all the activities that are part of the business process described in this document.

To accomplish the subsequent activities of this business process, and using the master data from this document, carry out the process steps described in one or more of the following scenarios.

Accounts Receivable (157)

UseIn this activity you will post the incoming payment.

ProcedureUsing the master data from this document, complete all the activities described in the Business Process Documentation of the scenario: Accounts Receivable (157) (Chapters Post Payments using Automatic Payments Program, Post Incoming Payment from Customer Manually, Automatic Clearing of open items in customer accounts, Manual Clearing of Open items in customer accounts).

Sales: Period End Closing Operations (203) (Optional)

Use

This scenario describes the collection of periodic activities such as day ending activities, or legal requirements.

ProcedureUsing the master data from this document, complete all the activities described in the Business Process Documentation of the scenario: Sales: Period End Closing Operations (203) (Chapters Review Incomplete SD Documents (deliveries), Review Sales Documents blocked for billing, Review Log of collective invoice creation).

6 Appendix

6.1 Reversal of Process StepsIn the following section, you will find the most common reversal steps, which enable you to reverse some of the activities described in this document.

Sales Order Entry

Transaction code (SAP GUI) VA01

Reversal: Delete Sales Document

Transaction code (SAP GUI) VA02



Business Role Sales Administrator

(SAP_NBPR_SALESPERSON-S)

Billing

Transaction code ( SAP GUI) VF04

Reversal: Cancel Billing document

Transaction code ( SAP GUI) VF11



Business role menu Sales Billing Cancel Billing Document

Comment Go to transaction VF11, enter the relevant billing document number, press Enter and save your result. An invoice cancellation document has been created balancing the original invoice.

6.2 SAP ERP Reports

UseThe table below lists the reports that you can use to obtain additional information on this business process.

You can find detailed descriptions of the individual reports in the following BPD documents, which provide a comprehensive compilation of all important reports:

Financial Accounting: SAP ERP Reports for Accounting (221)

Logistics Processes: SAP ERP Reports for Logistics (222)

Note that the descriptions of some reports, that are an indispensable part of the process flow, may be located directly in the section where they belong.

Reports

Report titleTransaction code (SAP GUI)

Business role (NWBC)

Business role menu (NWBC)

Comment

Outbound delivery monitor

KE30

CPWD: Sales Administrator (SAP_BPR_SALESPERSON_CPWD-S)

Indirect Sales Execute profitability report on indirect sales

Sales quantities and, if they have been provided, also revenues are displayed for every wholesaler

Sales Data Using SIS Reports

MCSI

CPWD: Sales Administrator (SAP_BPR_SALESPERSON_CPWD-S)

Indirect Sales Analyses of Indirect Sales

The latest information regarding the indirect sales volume
