Revenue Planning (172) - uacnlinks.orguacnlinks.org/sap/.../03/PERT_172_Revenue-Planning.pdf · Revenue Planning (172) SAP AG ... KEPM Update Sales Plan Quantities by Customer

EHP4 for SAP ERP 6.0

March 2010

English

Revenue Planning (172)

SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany

Business Process Documentation

SAP Best Practices Revenue Planning (172): BPD

© SAP AG Page 2 of 20

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, Clear Enterprise, SAP BusinessObjects

Explorer, 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 SAP France in the United States and in other countries.

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.



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.



Contents

1 Purpose ................................................................................................................................... 5

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

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

2.2 Roles ................................................................................................................................ 7

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

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

4.1 Copying Last Year’s Sales Data ...................................................................................... 8

4.2 Displaying Data .............................................................................................................. 10

4.3 Increasing Sales and the Dependent Values by 5 Percent ........................................... 11

4.4 Downloading Sales Quantities ....................................................................................... 12

4.5 Editing and E-mailing the Spreadsheet .......................................................................... 13

4.6 Uploading Sales Quantities for AOP Update ................................................................. 14

4.7 Reviewing Quantities for AOP Update before Distribution ............................................ 15

4.8 Distributing Product Group Quantities Top-Down to Customer/Product Level ........ Error! Bookmark not defined.

4.9 Reviewing Updated Sales Plan Quantity by Customer/ Product to Agree Distribution . 16

4.10 Updating Sales Plan Quantities by Customer/ Product to Agree Distribution ...... Error! Bookmark not defined.

4.11 Transferring Sales Quantities to Sales and Operations Planning .............................. 16

4.12 Valuation ..................................................................................................................... 18

4.13 Executing Plan Assessment Cycle for Profitability Analysis ...................................... 18

4.14 Executing the Profitability Report ............................................................................... 19



Revenue Planning

1 Purpose In this business scenario, a manufacturer of many product groups runs an SAP system in one sales organization. The organization has one central controlling department that calculates and plans the sales quantities and the revenues.

This document gives business users detailed step-by-step instructions about the business process.

2 Prerequisites

2.1 Master Data and Organizational Data

Default Values

Essential master and organizational data was created in your ERP system in the implementation phase, such as the data that reflects the organizational structure of your company and master data that suits its operational focus, for example, master data for materials, vendors, and customers.

The business process is enabled with this organization-specific master data, examples are provided in the next section.

Additional Default Values

You can test the scenario with other SAP Best Practices default values that have the same characteristics.

Check your SAP ECC system to find out which other material master data exists.

Using Your Own Master Data

You can also use customized values for any material or organizational data for which you have created master data. For more information on how to create master data, see the Master Data Procedures documentation.

Use the following master data in the process steps described in this document:

Master / org. data Value Master / org. data details

Comments

CORPRATE CENTER

Company Code 1000

Customer 200151

402000

403000

404000

GEN COTTON MILL

UNICO

CAP

UFL

Plant 1000

Product




Comments

Product Group

Sales Org. 1000

UN ICO

Company Code 2000

Customer 10000005 ABUEGO NIG LTD {MR. BIGG'

Plant 2000

Product

Product Group

Sales Org. 2000

CAP

Company Code 3000

Customer 200004 CHEMMY FOODS LIMITED

Plant 3000

Product

Product Group 0000300001

0000300002

0000300003

0000300004

0000300005

Dulux Regular

Dulux Trade

Caplux

Industrials

Accessories

Sales Org. 3000

UFL

Company Code 4000

Customer . 100000 COTSGAS INSTALLATION LTD

Plant 4100

Product FSS0001

FSS0002

FSS0003

FSS0004

FSS0005

FSS0006

FSS0007

KINGSWAY BEEF S/ROLL

GALA TINKIES PEANUT

GALA TINKIES FRUITY

GALA TINKIES STRAWBERRY

GALA BEEF S/ROLL*105

KINGSWAY SAUSAGE ROLL*105

KINGSWAY SAUSAGE ROLL*26

Product Group <select product group>

Sales Org. 4100

SWAN

Company Code 4010

Customer 11000960 MACJAN GLOBAL SERVICES

Plant 4010

Product B1701

B1705

B1710

B1715

B1716

APPLE DRINK 12 X 50CL

ORANGE DRINK 12 X 50CL

P/APPLE DRINK 12 X 50CL

WATER 12 X 150CL

WATER 6 X 150CL




Comments

Sales Org. 4010

GCL

Company Code 5000

Plant 5100

Product FGDCM0004

FGDCM0006

FGDCM0007

FGDCM0008

B GRITS

NA HOMINY 50 KG

BRAB 50 KG

BRABU 25 KG

BRABUS 10KG

Sales Org. 5000

2.2 Roles

Use

The following roles must have already been installed to test this scenario in the SAP NetWeaver Business Client (NWBC). The roles in this Business Process Documentation 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.

Prerequisites

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

Business role Technical name Process step

Employee (Professional User)

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

Enterprise Controller SAP_NBPR_CONTROLLER-M All steps

Strategic Planner SAP_NBPR_STRATPLANNER-S MC89

3 Process Overview Table Process step External

process reference

Business condition

Business role

Transaction code

Expected results

Copy Last Year’s Sales Data

Enterprise Controller

KEPM

Display Data Enterprise Controller

KEPM

Increasing Sales and the Dependent Values by 5 Percent


KEPM

Download Sales Quantities


KEPM

Edit and E-mail the Spreadsheet


KEPM



Process step External process reference

Business condition

Business role

Transaction code

Expected results

Upload Sales Quantities for AOP Update


KEPM

Review Quantities for AOP Update before Distribution


KEPM Review Quantities for AOP Update before Distribution

Top-down Distribution of Product Group Quantities to Customer/Product Level


KEPM

Review Updated Sales Plan Quantity by Customer/ Product to Agree Distribution


KEPM

Update Sales Plan Quantities by Customer/ Product to Agree Distribution


KEPM

Transfer Sales Quantities to Sales and Operations Planning


KE1E

Valuation Enterprise Controller

KEPM

Allocate R&D, Shared Services, Sales & marketing and Non Operating Cost Center expenses to Profitability Analysis


KEUB

Execute Report Enterprise Controller

KE30

4 Process Steps

4.1 Copying Last Year’s Sales Data



Use

In this step, you copy the sales data of the last year, which serves as the basis for the planning process.

If no data exists for the previous year, you can still perform this process step. No data will be created and in the next process step you have to enter manually same data to continue with the following process steps.

Procedure

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

Option 1: SAP Graphical User Interface (SAP GUI)

SAP ECC menu Accounting Controlling Profitability Analysis Planning Edit Planning Data

Transaction code KEPM

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

Business role Enterprise Controller

(SAP_NBPR_CONTROLLER-M)

Business role menu Profitability Analysis Planning Planning Framework: Overview

2. If the Set Operating Concern dialog box appears, enter your Operating concern (for example 10NG) and choose Enter.

3. If the Set Planner Profile dialog box appears, choose Cancel.

4. On the Planning Framework: Overview screen, expand the structure in the Planning Levels screen area until you can see all entries.

5. Right-click the entry YB100 and choose Change Planning Package.

6. On the right side of the screen make following entries.

Characteristic From / to

Company Code <select company code>

Period/year Plan period/year from.. to (eq. from 001.2014 to 012.2014

Plant <select plant>

Procurement Choose a valid entry (for example E )

Record type F

Sales Org. <select sales organization>

Unit Sales qty PC

Version 2

7. Choose Save.

8. To copy the planning data from the actual data, expand the structure YB100 and double-click YB100 – Sales Planning. Expand Copy in the Planning Methods screen area. Double-click on function YB100 – Sales Planning.



If the Planning Methods screen area is empty, double-click on the entry YB100 – Sales Planning in the Planning Levels screen area.

9. The Planning Framework: Information window appears: Choose Continue, and then Update run from the Planning Framework: Overview dialog box, which subsequently appears.

Result

The actual data is copied to the planning period (with a period shift of 12; for example, 01.2013 is copied to 01.2014). If no actual data exists for the previous year, no data is copied.

If no actual data exists for the previous year, no data is copied. Nevertheless this process step is executed correctly.

4.2 Displaying Data

Use

In this step you have a look on the plan data which you have created in the previous process step. You check if same data for product group are available in the requested plan version.

If you get the message that no data has been entered yet, you have to add manually same Revenue and sales quantity for a product group in this step.

Procedure









2. If the Set Operating Concern dialog box appears, enter your Operating concern (for example 10NG) for the operating concern and choose Enter.

If the currency is different from NGN:

1. Expand Planning level YB100 Sales Planning.

2. Double-click YB100 Sales Planning.

3. Expand Display Planning Data in the Planning methods section.

4. Right click YB100 Sales Planning and choose Change Parameter Set.

5. Enter your local currency in the currency field (for example NGN).

6. Choose Save.

7. Repeat these steps for the planning method Display planning data.



3. On the Planning Framework: Overview screen, choose the Planning Levels screen area, and in the Planning Levels selection tree, choose the planning level YB100 Sales Planning. Then, double-click the planning package YB100 Sales Planning.

4. To display the planning data, expand Display planning data in the Planning Methods screen area and double-click the parameter group YB100 Sales Planning.

The subsequent steps in the planning cycle are based on the Product Group .

When you get the information window on the screen: No data has been entered yet, no historical data is available for this Product Group. You have to perform the following steps, to have example data:


2. Right-click the entry YB100 and choose Change Planning Package.

3. On the right side of the screen make following entries.

Characteristic From / to

Company Code <select company code

Period/year Plan period/year from.. to (eq. from 001.2014 to 012.2014


Procurement Choose a valid entry (for example E )

Record type F

Sales Org. <select sales organization>

Unit Sales qty PC

Version 2

4. Choose Save.


6. Expand Enter Planning Data in the Planning methods section.

7. Double click YB100 Sales Planning.

8. Enter the following plan data in the planning sheet:

Product group Product Customer Revenue Sales Quantity

Select product group Leave empty Leave empty Any value Any value

9. Choose Save.

4.3 Increasing Sales and the Dependent Values by 5 Percent

Use

You generate a 5 percent increase in the planning data by using the Revaluation planning function.

Procedure











2. On the Planning Framework: Overview screen, choose the YB100 Sales Planning from the Planning Level screen area. Then double-click planning package YB100 Sales Planning.

3. To increase the planning data for the actual planning period by 5 percent, expand Revaluation and choose YB100 Sales Planning in the Planning Methods screen area and then select the parameter group YB100 Sales Planning with a double-click.

4. The Planning Framework: Information window appears: Choose Continue, and then Update run from the Planning Framework: Overview dialog box, which subsequently appears.

4.4 Downloading Sales Quantities

Use

During the AOP process the sales quantities for the product group are planned by the product group managers. The managers plan the values offline from the SAP System in an excel spreadsheet.

In this process step the cost controller activate the excel integration and download the plan data in a spreadsheet.

Procedure









2. On the Planning Framework Overview screen, expand planning level YB100.

3. Right click YB100 and choose Change.

4. Enter E (In-house production) in the Procurement field and choose Save.

5. Double-click Planning package YB100.



6. Expand Enter planning data in the bottom left portion of the screen.

7. Right click YB100 Sales Planning and choose Change Parameter Set.

8. Set the flag for Activate the excel integration in the area of integrated excel.

9. Choose Save.



12. Expand Enter Planning Data in the Planning methods section.

13. Double-click YB100 and choose Enable macros.

14. To generate the file description choose one of the following options


Menu bar Settings Formatting

Option 2: SAP NetWeaver Business Client (SAP NWBC) über Benutzerrolle

Menu bar More Settings Formatting

15. Click on Generic file and enter a name for the file. To save the file description and the file layout, click on Save File Description and Save Excel Layout.

16. In Microsoft Excel, from the menu bar, choose File Save Copy As and use the file name budget_yyyy_pppppppppp.xls, where yyyy is the budget year and pppppppppp is the product line. Save the file under C:\budget\budget_yyyy_pppppppppppppp.xls .

17. Open the saved Excel file independently and delete the Total row. Before being able to delete the row, you may have to unprotect the sheet. To perform this task, use Tools/ Protection/ Unprotect sheet in Excel, delete the row and save the file.

Result

The file has been successfully downloaded to Microsoft Excel.

4.5 Editing and E-mailing the Spreadsheet

Use

During the AOP process, the product group manager updates and e-mails the Excel spreadsheet to the cost controller.

The product group manager plans the sales quantity on the product group level.

The product group is the third level of the product hierarchy.

The product hierarchy is grouping the materials. Each material is assigned to the product hierarchy in the material master data.

In our process we have made a copy from the last year sales data to give the product group manager a proposal on product group level.

If no sales data from the previous year exists the same sales quantities are added manually on product group level (see process step 4.2 Displaying Data).

Notes for Editing the Spreadsheet



Do not use Delete, Paste, Sort functions in Excel.

Add new records at the bottom of the spreadsheet.

A second worksheet can be used for calculations, graphs.

Data can be kept at customer product level for accuracy, or alternatively updated by product group and distributed later.

Do not delete items to get rid of quantities, instead, enter 0.

Sheet 1 must be saved as budget_yyyy_pppppppppppppp.txt to enable upload where yyyy is the budget year and pppppppppppppp is the product line.

Result

The Excel spreadsheet is now saved in the correct format for upload.

Example

The spreadsheet includes the following production groups

Product group Product Customer Revenue Sales Quantity



4.6 Uploading Sales Quantities for AOP Update

Use

This activity uploads sales quantities for AOP update.

Procedure

Before starting this section, save file budget_yyyy_pppppppppppppp.xls as .txt (text / tab delimited)



SAP ECC menu Accounting Controlling Profitability Analysis Planning

Integrated Planning Upload from Excel Execute

Transaction code KE13N




Business role menu Profitability Analysis Planning Flexible Upload

2. On the Flexible Upload screen, make the following entries:

Field name Description User actions and values Comment

Operating Concern 10NG



Type of Profitability Analysis

1

Planning layout YG100

Import single file (if importing a single file)

X

Import file directory (if importing multiple files)

Blank for this test

Path or file Enter path and filename, if single file is chosen, else enter path to directory only (for example c:\budget\aop\copa\2014_00003000001.txt)

File description Choose Enter to default it.

Decimal notation 1,234,567.89

Separator in CSV files ;

3. Choose Execute.

4.7 Reviewing Quantities for AOP Update

Use

This activity reviews quantities for AOP update before distribution.

Procedure









2. On the Planning Framework Overview screen, expand planning level YB100 and double-click Planning package YB100.

3. On the Planning Methods subscreen, expand the Display planning data folder. Double-click YB100.

Result

The sales quantity is updated as per file.

1. Choose Save.



4.8 Reviewing Updated Sales Plan Quantity by Customer/ Product to Agree Distribution

Procedure









2. If the Set Operating Concern dialog box appears, enter your Operating concern (for example 10NG) for the operating concern and choose Enter.

3. On the Planning Framework: Overview screen, choose the Planning Levels screen area and in the Planning Levels selection tree, choose the planning level YB100 Sales Planning. Then double-click the planning package YB100 Sales Planning.

4. To display the planning data, expand Display planning data in the Planning Methods screen area and double-click the parameter group YB100 Sales Planning.

4.9 Transferring Sales Quantities to Sales and Operations Planning

Use

This activity transfers sales quantities to sales and operations planning (SOP).

Prerequisites

The transfer to SOP requires detailed planning on product/article level in CO-PA. The step “4.8 Distributing Product Group Quantities Top-down to Customer/Product Level” is therefore required before proceeding.

Procedure



SAP ECC menu Accounting Controlling Profitability Analysis Planning

Integrated Planning Transfer Quantities to SOP

Transaction code KE1E






Business role menu Profitability Analysis Planning Transfer Plan Data to SOP

2. On the Transfer Plan to SOP – Initial Screen, make the following entries:

Plan Data

From period <001.yyyy>

To <012.yyyy>

Version 2

Record type F

SOP

Version 002

Text AOP budget quantity

Transfer changes only X (Test run can be used initially, if desired)

Make sure you provide the data in the correct format Period: Format MMMYYYY (for example 0012008) CO Version Plan Data: 2 (without zeros) SOP Version: 002 (provide leading zeros)

3. Choose Selection criteria. Plant or product group may be entered for partial selections.

4. Choose Execute.

Ensure that there were no errors in the transfer.

Result

The quantity is transferred to sales and operations correctly and there is no error in transfer.

To generate a SOP report per material, choose one of the following navigation options:


SAP ECC menu Logistics Production SOP Planning For Material Display

Transaction code MC89


Business role Strategic Planner

(SAP_NBPR_STRATPLANNER-S)

Business role menu Production SOP Material Display Plan for Material

On the Display Plan: – Initial Screen, make the following entries:

Material




Inaction Version Select

Version 002

The SOP version 002 is created with this step.

4.10 Valuation

Prerequisite

The valuation in this process step based on material cost estimation.

To have the relevant data for valuation, the scenario document Standard Cost Calculation (178) has to be performed before you go on with the next step.

In the Demo environment from SAP Best Practices Baseline Package the cost estimation for the actual planning period are created with the scenario document 154 Prerequisite Process Steps

Procedure









2. If the Set Operating Concern dialog box appears, enter your Operating concern (for example 10NG) and choose Enter.

3. On the Planning Framework: Overview screen, choose YB100 Sales Planning from the Planning Level screen area. Then double-click planning package YB100 Sales Planning.

4. To valuate the planning data, expand Valuation in the Planning Methods screen area and then double-click the parameter group YB100 Sales Planning.

5. The Planning Framework: Information window then appears: Select Continue, and then Update run from the Planning Framework: Overview dialog box, which subsequently appears.

4.11 Executing Plan Assessment Cycle for Profitability Analysis

Prerequisite

The plan assessment in this process step based on data from the cost center planning.

To have the relevant data for plan assessment, the scenario document General Cost Center Planning (175) has to be performed before you go on with the next step.



Procedure



SAP ECC menu Accounting Controlling Profitability Analysis PlanningSystem

Transfer Cost Center Planning/Process Planning

Transaction code KEUB




Business role menu Profitability Analysis Transfer of Overhead Execute Plan Assessment Cycle for Profitability Analysis

2. On the Execute Plan Assessment: Initial Screen, make the following entries:

Enter the period (for example 001 to 012).

Enter the fiscal year (for example 2008).

Select Detail List and deselect Test run.

Enter the cycle YB01.

Choose Execute.

4.12 Executing the Profitability Report

Procedure



SAP ECC menu Accounting Controlling Profitability Analysis Information

System Execute Report

Transaction code KE30




Business role menu Profitability Analysis Reporting Execute profitability report

2. On the Run Profitability Report: Initial Screen, double-click YBR1040 Plan/Actual Comparison.

3. On the Selection: Plan/Actual comparison screen, enter the fiscal year (for example 2007), the periods (choose periods where actual data exists) and choose Execute (F8).

4. Confirm the warning dialog box.

The customer-specific Information Reports opens, showing the actual and the plan values for several key figures.

5. On the Execute Drilldown Report screen:



Choose Prd.Gp (product group) and click on the magnifying glass icon to view by characteristic values for example, ProdHier01-2 in the navigation area.

The report shows the key figures for a specific hierarchy.

You can go to the next hierarchy by choosing Next characteristic value.

Documents

Revenue Planning (172) - uacnlinks.orguacnlinks.org/sap/.../03/PERT_172_Revenue-Planning.pdf · Revenue Planning (172) SAP AG ... KEPM Update Sales Plan Quantities by Customer