EHP4 for SAP ERP 6.0 March 2010 English. Revenue Planning (172) Business Process Documentation. SAP AG Dietmar-Hopp-Allee Walldorf Germany

Transcription

1 EHP4 for SAP ERP 6.0 March 2010 English Revenue Planning (172) Business Process Documentation SAP AG Dietmar-Hopp-Allee Walldorf Germany

2 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 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, 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. SAP AG Page 2 of 20

3 Icons Icon Meaning Caution Example Note Recommendation Syntax External Process Business Process Alternative/Decision Choice Typographic Conventions Type Style Example text Example text EXAMPLE TEXT Example text EXAMPLE TEXT Example text <Example text> Description 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. Emphasized words or phrases in body text, titles of graphics and tables. 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. 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. Keys on the keyboard, for example, function keys (such as F2) or the ENTER key. Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation. Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries. SAP AG Page 3 of 20

4 Contents 1 Purpose Prerequisites Master Data and Organizational Data Roles Process Overview Table Process Steps Copying Last Year s Sales Data Displaying Data Increasing Sales and the Dependent Values by 5 Percent Downloading Sales Quantities Editing and ing the Spreadsheet Uploading Sales Quantities for AOP Update Reviewing Quantities for AOP Update before Distribution 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 Updating Sales Plan Quantities by Customer/ Product to Agree Distribution... Error! Bookmark not defined Transferring Sales Quantities to Sales and Operations Planning Valuation Executing Plan Assessment Cycle for Profitability Analysis Executing the Profitability Report SAP AG Page 4 of 20

5 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 s documentation. Use the following master data in the process steps described in this document: Master / org. data Value Master / org. data details CORPRATE CENTER Company Code 1000 Customer Plant 1000 Product Comments GEN COTTON MILL UNICO CAP UFL SAP AG Page 5 of 20

6 Master / org. data Value Master / org. data details Comments Product Group Sales Org UN ICO Company Code 2000 Customer ABUEGO NIG LTD {MR. BIGG' Plant 2000 Product Product Group Sales Org CAP Company Code 3000 Customer CHEMMY FOODS LIMITED Plant 3000 Product Product Group Sales Org UFL Company Code Dulux Regular Dulux Trade Caplux Industrials Accessories Customer COTSGAS INSTALLATION LTD Plant 4100 Product Product Group FSS0001 FSS0002 FSS0003 FSS0004 FSS0005 FSS0006 FSS0007 Sales Org SWAN Company Code 4010 <select product group> 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 Customer 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 SAP AG Page 6 of 20

7 Master / org. data Value Master / org. data details Sales Org GCL Company Code 5000 Plant 5100 Product Sales Org FGDCM0004 FGDCM0006 FGDCM0007 FGDCM0008 Comments B GRITS NA HOMINY 50 KG BRAB 50 KG BRABU 25 KG BRABUS 10KG 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. Technical name Process step Employee (Professional User) SAP_NBPR_EMPLOYEE-S Assignment of this role is necessary for basic functionality. 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 Display Data Increasing Sales and the Dependent Values by 5 Percent Download Sales Quantities Edit and the Spreadsheet SAP AG Page 7 of 20

8 Process step External process reference Business condition Business role Transaction code Expected results Upload Sales Quantities for AOP Update Review Quantities for AOP Update before Distribution Review Quantities for AOP Update before Distribution Top-down Distribution of Product Group Quantities to Customer/Product Level Review Updated Sales Plan Quantity by Customer/ Product to Agree Distribution Update Sales Plan Quantities by Customer/ Product to Agree Distribution Transfer Sales Quantities to Sales and Operations Planning KE1E Valuation Allocate R&D, Shared Services, Sales & marketing and Non Operating Cost Center expenses to Profitability Analysis KEUB Execute Report KE30 4 Process Steps 4.1 Copying Last Year s Sales Data SAP AG Page 8 of 20

9 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. Accounting Controlling Profitability Analysis Planning Edit Planning Data 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 Company Code Period/year Plant From / to <select company code> Plan period/year from.. to (eq. from to <select plant> Procurement Choose a valid entry (for example E ) Record type Sales Org. Unit Sales qty Version 2 7. Choose Save. F <select sales organization> 8. To copy the planning data from the actual data, expand the structure YB100 and doubleclick YB100 Sales Planning. Expand Copy in the Planning Methods screen area. Doubleclick on function YB100 Sales Planning. PC SAP AG Page 9 of 20

10 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, is copied to ). 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. Accounting Controlling Profitability Analysis Planning Edit Planning Data menu Profitability Analysis Planning Planning Framework: Overview 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. SAP AG Page 10 of 20

11 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: 1. Expand Planning level YB100 Sales Planning. 2. Right-click the entry YB100 and choose Change Planning Package. 3. On the right side of the screen make following entries. Characteristic Company Code Period/year Plant From / to <select company code Plan period/year from.. to (eq. from to <select plant> Procurement Choose a valid entry (for example E ) Record type Sales Org. Unit Sales qty Version 2 4. Choose Save. 5. Double-click YB100 Sales Planning. F <select sales organization> 6. Expand Enter Planning Data in the Planning methods section. 7. Double click YB100 Sales Planning. PC 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. SAP AG Page 11 of 20

12 Accounting Controlling Profitability Analysis Planning Edit Planning Data menu Profitability Analysis Planning Planning Framework: Overview 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. Accounting Controlling Profitability Analysis Planning Edit Planning Data menu Profitability Analysis Planning Planning Framework: Overview 2. On the Planning Framework Overview screen, expand planning level YB 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. SAP AG Page 12 of 20

13 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. 10. Expand Planning level YB100 Sales Planning. 11. Double-click YB100 Sales Planning. 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 ing the Spreadsheet Use During the AOP process, the product group manager updates and s 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 SAP AG Page 13 of 20

14 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. Result 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. 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 Select product group Leave empty Leave empty Any value Any value Select product group Leave empty Leave empty Any value Any value 4.6 Uploading Sales Quantities for AOP Update Use This activity uploads sales quantities for AOP update. Before starting this section, save file budget_yyyy_pppppppppppppp.xls as.txt (text / tab delimited) Accounting Controlling Profitability Analysis Planning Integrated Planning Upload from Excel Execute KE13N 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 SAP AG Page 14 of 20

15 Type of Profitability Analysis Planning layout Import single file (if importing a single file) Import file directory (if importing multiple files) Path or file File description 1 YG100 X Blank for this test Enter path and filename, if single file is chosen, else enter path to directory only (for example c:\budget\aop\copa\2014_ txt) Choose Enter to default it. Decimal notation 1,234, Separator in CSV files ; 3. Choose Execute. 4.7 Reviewing Quantities for AOP Update Use This activity reviews quantities for AOP update before distribution. Accounting Controlling Profitability Analysis Planning Edit Planning Data menu Profitability Analysis Planning Planning Framework: Overview 2. On the Planning Framework Overview screen, expand planning level YB100 and doubleclick Planning package YB 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. SAP AG Page 15 of 20

16 4.8 Reviewing Updated Sales Plan Quantity by Customer/ Product to Agree Distribution Accounting Controlling Profitability Analysis Planning Edit Planning Data menu Profitability Analysis Planning Planning Framework: Overview 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. Accounting Controlling Profitability Analysis Planning Integrated Planning Transfer Quantities to SOP KE1E SAP AG Page 16 of 20

17 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 ) 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. Result Ensure that there were no errors in the transfer. 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: Logistics Production SOP Planning For Material Display MC89 menu Strategic Planner (SAP_NBPR_STRATPLANNER-S) Production SOP Material Display Plan for Material On the Display Plan: Initial Screen, make the following entries: Material Plant <select plant> SAP AG Page 17 of 20

18 Inaction Version Select Version Valuation Prerequisite The SOP version 002 is created with this step. 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 Accounting Controlling Profitability Analysis Planning Edit Planning Data 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. 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 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. SAP AG Page 18 of 20

19 Accounting Controlling Profitability Analysis PlanningSystem Transfer Cost Center Planning/Process Planning KEUB 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 Executing the Profitability Report Accounting Controlling Profitability Analysis Information System Execute Report KE30 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: SAP AG Page 19 of 20

20 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. SAP AG Page 20 of 20