Vous êtes sur la page 1sur 42

Sales and Operations Planning

Release 510

ADDONX.SCMSOP

Copyright
Copyright 2007 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, OpenPower and PowerPC are trademarks or registered trademarks of IBM Corporation. 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. MaxDB is a trademark of MySQL AB, Sweden. SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

(C) SAP AG

ADDONX.SCMSOP

Icons in Body Text


Icon Meaning Caution Example Note Recommendation Syntax Additional icons are used in SAP Library documentation to help you identify different types of information at a glance. For more information, see Help on Help General Information Classes and Information Classes for Business Information Warehouse on the first page of any version of SAP Library.

Typographic Conventions
Type Style Example text Description Words or characters quoted from the screen. These include field names, screen titles, pushbuttons labels, menu names, menu paths, and menu options. Cross-references to other documentation. Example text EXAMPLE TEXT Emphasized words or phrases in body text, graphic titles, and table titles. Technical names of system objects. These include report names, program names, transaction codes, table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE. Output on the screen. This includes file and directory names and their paths, messages, names of variables and parameters, source text, and names of installation, upgrade and database tools. Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation. Variable user entry. Angle brackets indicate that you replace these words and characters with appropriate entries to make entries in the system. Keys on the keyboard, for example, F2 or ENTER.

Example text

Example text <Example text>

EXAMPLE TEXT

(C) SAP AG

ADDONX.SCMSOP

Sales and Operations Planning ................................................................................................. 5 Configuring the SAP xSOP System ....................................................................................... 7 Using the SAP GUI or SAP Netweaver Business Client .................................................. 8 Loading Master Data......................................................................................................... 9 Loading Characteristic Value Combinations................................................................... 11 Loading Transactional Data............................................................................................ 15 Standard Key Figures ..................................................................................................... 17 Configuring Analytics ...................................................................................................... 26 Process Management .......................................................................................................... 34 Document Management....................................................................................................... 37 Sales and Operations Planning Process ............................................................................. 38 Creating the Basic Structures of the Process................................................................. 39 Modeling Strategic Plans ................................................................................................ 40 Analyzing, Adjusting and Reconciling Plans................................................................... 41 Management Review of the Overall Situation ................................................................ 42

(C) SAP AG

ADDONX.SCMSOP

Sales and Operations Planning


SAP xApp Sales and Operations Planning (SAP xSOP) supports a process in which various enterprise areas can reconcile and synchronize their plans, such as demand, sales, and procurement plans. The aim of this process is to create an enterprise-wide demand and procurement plan that corresponds to the strategic aims of the enterprise. In this way, the enterprise can achieve an increase in efficiency. The following graphic shows the sales and operations planning process: Sales and Operations Planning

Pr oduct Launch
Strateg. Planning Demand Planning

SOP Process
Procurement Planning Reconciling Demand and Supply

SOP Meeting
Manage ment Revi ew & Analy sis

Market Planning Product Planning Resource Planning

Quantitativ e Forecasting Capacity Planning Input v s. Marketing/SalesStock Planning Demand Reconciliation Procurement Planning Logistics

Product Mix Constraint Management Supply & Demand Reconciliation

Key Figure Ev aluation Plan v s. Actual Forecast Error Margin Management Cause Analyse

Document Management Document Management


Attach Docum ents Check Docum ents

Task and Action Item Management Task and Action Item Management
Define Task s Track/Updat e Tasks Confirm Tasks

SOP Analytics SOP Analytics


Key Figures & Metric s Comparison & Simulation Dem and Analytic s

Define Action Items

Track/Updat e Action Items

Complete Action Items

Supply Analytics

Inventory Analytic s

Financial Analytic s

S O P U I P resse nta ti o n L ayye r S OP re e n tati a er S O P U I I I I nte rf a ce L ay er U n te ac e La ye r S O P A p pl i c at i n L ayye r S O P A pp l i ca ti o n L a e r o B B usi ness Proce sses Processe s Pr ocess Pr ocess Com Pr om ponent ocess C p onent C ponent n n om M I 2 F B B P O I F2 PO M O fi e f cce n e f ace s I nterf ces t ra M n F F I I 2 A2X

S O P I n teggr ati onn L ayye r O S P I n te ra ti o L a er D ocu e D cument o m nt M agement an Manage m t en Sys em/ I e r ace s t n t fa S ystem/ nterf ces T rans. D at rans . ata a I nterf aces ac es Master D ata D I nterf aces n a I terf ces

E t na SS xternal x e r l ystem n e f ace s I nterf ces t ra X I I nterf c es I nterf a aces

A2X

S M _B A SI S C

T ransact. D ataA ccess Layer r ( TD ) rans act. ata c cess Laye T D L) L at S a torage ayers D ataStorag eLLayers
O d e r Da t r a Tm i e Se r s i e t B WI n o P r o v d e r f i

SS M B asi sMaster C B M aster D ataO bj c s ata b j ects e t


P l n n n g Ob e c a i j t t u u r S r c t e ( P O) S

Ma n a g m e t e n ( O D M)

D a t Mg m a T ( S DM)

Integration
You can use data from various SAP systems with SAP xSOP. You can transfer data from the following systems into the SAP xSOP system: SAP Enterprise Resource Planning (SAP ERP) SAP Supply Chain Management (SAP SCM) SAP NetWeaver Business Intelligence (SAP NetWeaver BI)

You can also load data from an external CSV file into the SAP xSOP system. You can download transactional data back into an SAP SCM system. Furthermore, a delta download of transactional data to an SAP NetWeaver BI system is available. For more information, see the Configuration Guide for SAP xSOP.

(C) SAP AG

ADDONX.SCMSOP

Features
You can use SAP xSOP to analyze and compare plans from various enterprise areas and for various business scenarios, as well as to check alternative plans. SAP xSOP supports the following activities, for example: Creating analyses Simulating plans Process Management Document management

SAP xSOP provides predefined analyses and key figures, as well as data aggregation tools, for checking, adjusting, and reconciling individual plans. The SAP xSOP analyses offer both an overview of the data for multiple plans as well as a detailed view of the data for individual plans. You can also adjust the analyses to meet your individual requirements and create your own key figures. After reconciling individual plans, you can create an enterprise-wide demand and procurement plan in a management review meeting. The meeting is supported by an overview analysis. Thus, different departments, such as Marketing, Finance, Production and Logistics, can work with the same overall plan and thus also the same data. Furthermore, SAP xSOP enables you to track processes. You can create process steps with tasks and action items, check their completion statuses, and manage associated documents, such as Microsoft PowerPoint presentations and Excel sheets.

(C) SAP AG

ADDONX.SCMSOP

Configuring the SAP xSOP System


You can configure SAP xApp Sales and Operations Planning (SAP xSOP) according to your individual requirements. This includes the following activities: Deciding on the use of the SAP GUI or SAP Netweaver Business Client Loading master data and characteristic value combinations (CVCs) from other SAP systems or external files, as well as creating new master data and CVCs in the SAP xSOP system Loading transactional data from other SAP systems or external files Configuring the various analyses according to your needs

For more information, see the following sections: Using the SAP GUI or SAP Netweaver Business Client Loading Master Data Loading Characteristic Value Combinations Loading Transactional Data Standard Key Figures Configuring Analytics

(C) SAP AG

ADDONX.SCMSOP

Using the SAP GUI or SAP Netweaver Business Client


You can use two different types of user interface with SAP xApp Sales and Operations Planning (SAP xSOP): SAP GUI or SAP Netweaver Business Client. The business client is a desktop-based integration platform, which allows you to seamlessly use classic SAP GUIbased transactions alongside new applications that have been developed with Web Dynpro. For more information about installing the business client and the special features of this user interface software, see SAP Note 1021856. The basic differences between the two user interfaces are outlined below.

Features
SAP GUI In the classic SAP GUI environment you can access both SAP GUI and Web Dynpro transactions. SAP GUI transactions are displayed in the SAP GUI session. A separate web browser window opens for Web Dynpro transactions. Two types of application menu are available: the SAP Easy Access menu and a user-specific menu. If you have assigned roles to the user, the user-specific menu is displayed based on the roles assigned. For more information, see Roles in SAP xApp Sales and Operations Planning. SAP Netweaver Business Client In the SAP NetWeaver Business Client, all transactions are displayed on one standard user interface. The SAP GUI transactions and Web Dynpro transactions appear in the main screen area. This is the so-called canvas or application content area. In the left-hand screen area (the home area) you find a user-specific, role-based menu. In the upper screen area, links to all of the standard transactions available for your role are displayed. You can also use the session tab area to navigate between all transactions that you have already called up in the current session.

(C) SAP AG

ADDONX.SCMSOP

Loading Master Data


In SAP xApp Sales and Operations Planning (SAP xSOP), you can upload and maintain master data from other SAP systems, such as SAP Supply Chain Management (SAP SCM), or from external CSV files. You can also create and delete master data directly in the SAP xSOP system. You can upload data in a dialog or schedule it to be loaded in the background.

Prerequisites
You have made the settings as described in the Configuration Guide for SAP xSOP under the sections for setting up RFC connections and integration with SAP SCM.

Features
Uploading Master Data You can upload the following master data: Locations Products Resources Resource capacity Capacity utilization

To upload data in a dialog, choose Master Data Upload Master Data . If you want to schedule the loading of data as a background job, choose Master Data Master Data Processing in the Background Upload Master Data in the Background . Enter the data source and define the master data that you want to upload. If you wish to upload resources, you must also specify the logical system of the resource. If a resource has been transferred from an SAP ERP system into an SAP SCM system, for example, you should specify the name of the logical ERP system. As a prerequisite for uploading capacity utilization data, you must first map products to product subfamilies. For more information, see the section "Uploading and Maintaining Product-Product Subfamily Mapping". You can check successfully uploaded data using the report /SCMSOP/SOP_TSDM_DATA_READ. Enter the key figure SOP_CAPACT_FACTR. Maintaining Master Data In SAP xSOP, you can create new master data and change or delete existing master data. You can only maintain data locally in the SAP xSOP system. This means that any changes you make will have no effect on an SAP SCM or other system. You can also copy individual master data objects. You must create certain master data in SAP xSOP, since you cannot upload characteristic values for the characteristics "Product Family", "Product Subfamily", "Region", and "Business Unit" (which form the master data). Creating characteristic values is a prerequisite for uploading or mapping characteristic value combinations in later steps. To maintain master data, choose Master Data Maintain Master Data . Enter the master data object type (such as location) and the object name. Then choose Show Objects. You are presented with a list of the chosen master data objects, which you can maintain. Uploading and Maintaining Product-Product Subfamily Mapping

(C) SAP AG

ADDONX.SCMSOP

In SAP xSOP, you mainly consider and maintain aggregated data. Therefore, you must create a product hierarchy. You can create product subfamilies using the master data maintenance in the SAP xSOP system or upload them from a source system. You can either upload mappings for products and product subfamilies, or create them in the SAP xSOP system. To do this, choose Master Data Upload Product - Product Subfamily Mapping or Maintain Product - Product Subfamily Mapping. To upload the data, specify an external CSV file that contains the product families in the first column and the products in the second column. You can also upload mappings in the background. Choose Master Data Master Data Processing in the Background Upload Product - Product Subfamily Mapping in the Background . Deleting Master Data in the Background You can delete master data that is no longer required in the background. To do this, choose Master Data Master Data Processing in the Background Delete Master Data in the Background . You cannot delete master data that is used in existing characteristic value combinations.

(C) SAP AG

ADDONX.SCMSOP

10

Loading Characteristic Value Combinations


In SAP Sales and Operations Planning (SAP xSOP), SAP delivers the planning object structure 9ASOP, which contains the following characteristics that are relevant to SAP xSOP. Region Business unit Product family Product subfamily Location Resource

Die number of characteristics in SAP xSOP is predefined. You cannot add or delete any characteristics. You can upload the characteristic value combinations (CVCs), which are the combinations of the possible values for characteristics, from a source system into the SAP xSOP system or create them yourself in the SAP xSOP system. A CVC is, for example, the product family "cosmetics" and the product subfamily "shampoo" in the region "Europe". The following describes how you can load or create CVCs in SAP xSOP

Features
To load or create CVCs in SAP xSOP, there are basically two scenerios: 1. The number of characteristics, characteristic values and characteristic value combinations are exactly the same in SAP xSOP and in the other SAP systems. 2. The number of characteristics, characteristic values and characteristic value combinations are not the same in SAP xSOP and in the other SAP systems. In both cases, you load the CVCs from an SAP system or from an external flat file in CSV format into the SAP xSOP system, or create them manually in the SAP xSOP system. For more information, see the "Loading CVCs" and "Maintaining CVCs" sections. The two cases differ from each other in how you map the characteristics from an SAP system to the characteristics in the SAP xSOP system. In the first case, you can define the mapping of characteristics from the SAP system to the SAP xSOP characteristics in Customizing for SAP xSOP before you load the CVCs. In this case, the system replaces the characteristics from the source system with the SAP xSOP characteristics. For more information, see the section "Mapping Characteristics in Customizing". In the second case, you you must upload the mapping for your source system CVCs and SAP xSOP CVCs from an external flat file after you have uploaded or created the CVCs in the SAP xSOP system. For more information, see the "Loading CVC Mapping" and "Maintaining CVC Mapping" sections.

Uploading CVCs Choose Master Data Upload CVCs . Enter the source type and source ID and choose Start CVC Transfer . You must have already created data sources in Customizing for SAP xSOP under Analytics Configure xSOP Analytics or in the SAP NetWeaver Business Client under xSOP Administrator Analytics Analytics Configuration . For more information, see the Implementation Guide (IMG).

(C) SAP AG

ADDONX.SCMSOP

11

You are presented with an overview of the characteristic values combinations, from which you can choose the required objects. You can also export the CVCs into a Microsoft Excel file or into the Business Explorer Analyzer (BEx Analyzer). Note, that you must save your data after loading the CVCs. If you want to schedule the loading of CVCs as a background job, choose Master Data Master Data Processing in the Background Upload CVCs in the Background . Maintaining CVCs You can also create and delete CVCs directly in the SAP xSOP system. To do this, choose Master Data Maintain CVCs . If you want to create CVCs in the system, enter characteristic values in the Characteristic Value Combination: Add screen area, and then save. You can only enter master data that exists in the system. This means the data that you have already loaded into the SAP xSOP system or have created manually. If you want to delete CVCs, enter the characteristic values in the Characteristic Value Combination: Selection screen area, and then refresh the overview. You are presented with a list of the characteristic value combinations, from which you can choose and delete objects. When you delete CVCs. the associated transactional data is also deleted. To create new CVCs, you can also copy rows from this list. You can export the CVCs into a Microsoft Excel file or into the BEx Analyzer. Mapping Characteristics in Customizing If the number of characteristics, characteristic values, and CVCs in SAP xSOP and your other SAP system match exactly, you can define the mapping for the characteristics from your SAP system and xSOP system in Customizing for SAP xSOP before you upload the CVCs by choosing the above named transaction Configure xSOP Analytics. The characteristic values remain unchanged. For more information, see the Configuration Guide for SAP xSOP under Integration with cFolders and also the Implementation Guide. Example The following example shows which CVCs in the source system correspond to which CVCs in the SAP xSOP system once you have uploaded the CVCs. CVCs in the SAP System Z_BUNIT Business unit 1 Business unit 1 Z_REGION Region 1 Region 1 9ASOPPRDGRP Product Group 1 Product Group 1 9AMATNR Product 1 Product 2 9ALOCNO Location 1 Location 1 9ARNAME Resource: 1 Resource: 1

CVCs in SAP xSOP 9ASOPUNIT Business unit 1 Business unit 1 9ASOPREG 9ASOPPRFAM Region 1 Region 1 Product Group 1 Product Group 1 9ASOPPRDSF Product 1 Product 2 9ASOPLOC 9ASOPRESC Location 1 Location 1 Resource: 1 Resource: 1

(C) SAP AG

ADDONX.SCMSOP

12

Uploading CVC Mapping If the characteristic values or number of CVCs in the SAP xSOP system do not match those in the other SAP system, you must upload the CVC mappings from an external file. Note, that in this case you cannot map the characteristics by using the the customizing transaction Configure xSOP Analytics (which was described above). Before you upload CVC mappings, you must upload the CVCs into the SAP system (as described above) or create them directly in the SAP xSOP system. You can define which CVCs in a source system correspond to which CVCs in the SAP xSOP system. In this way, a CVC from an SAP SCM system can correspond to a different CVC in the SAP xSOP system, for example. The relationship here is 1:n. This means that one CVC in the xSOP system can be mapped to multiple CVCs from a source system. The reverse mapping, n:1, is not possible. Choose Master Data Upload CVC Mapping . You can only upload CVC mappings using an external CSV file. For more information about the structure of the CSV file, choose CSV File Format Info. The maximum number of characteristics from an external SAP system is restricted to seven.

(C) SAP AG

ADDONX.SCMSOP

13

Example The following example shows how you define the CVC mapping in an external file. It also shows the result that you get in the SAP xSOP once you have uploaded the CVC mappings. CVCs in the SAP System 0COUNTRY France France 9ALOCNO Paris 1 Paris 2 9AMATNR Shampoo Shampoo CVCs in the SAP xSOP System 9ASOPUNIT Western Europe 9ASOPREG Region 1 9ASOPPRFAM Hair Care 9ASOPPRDSF Product subfamily 1 9ASOPLOC Paris 9ASOPRESC Resource: 1

Structure of External File Data source ID 9ASOPUNIT 9ASOPREG 9ASOPPRFAM 9ASOPPRDSF 9ASOPLOC 9ASOPRESC 0COUNTRY 9ALOCNO Western Europe Western Europe Region 1 9AMATNR Hair Care Product subfamily 1 Product subfamily 1 Paris Resource: 1 France Paris Shampoo 1 Paris Shampoo 2

Region 1

Hair Care

Paris

Resource: 1

France

Result: CVC Mapping in SAP xSOP 9ASOPUNIT 9ASOPREG 9ASOPPRFAM 9ASOPPRDSF 9ASOPLOC 9ASOPRESC Western Europe Western Europe Region 1 Hair Care Product subfamily 1 Product subfamily 1 Paris Resource: 1 France Paris Shampoo 1 Paris Shampoo 2

Region 1

Hair Care

Paris

Resource: 1

France

Maintaining CVC Mapping You can display and delete CVC mappings that you have already loaded into the SAP xSOP system. To do this, choose Master Data Maintain CVC Mapping . In the selection area, specify the characteristic values and the source system ID. The system then displays the list of CVC mappings in the overview area. You can delete CVC mappings or export them into a Microsoft Excel file or into the BEx Analyzer. You can also display CVCs for which no mapping has been defined.

(C) SAP AG

ADDONX.SCMSOP

14

Loading Transactional Data


In SAP xApp Sales and Operations Planning (SAP xSOP) you can upload transactional data from other SAP systems, such as SAP Supply Chain Management (SAP SCM), SAP ERP and SAP NetWeaver Business Intelligence (SAP NetWeaver BI) or from external files. Transactional data comprises the key figure values for key figures. You can also download transactional data back into an SAP SCM system. A delta download of the data is available for the SAP NetWeaver BI system.

Prerequisites
The transactional data is saved in an xSOP version. You have created this version under Analytics Version Maintenance . Choose Change and then Create Version. You can also copy or delete existing versions. To be able to load transactional data from an SAP ERP, SAP SCM or SAP NetWeaver BI system, you must have mapped an existing version of the source system to an existing SAP xSOP version. Furthermore, you have assigned a combination of the region and business unit characteristics to the version. Only the transactional data that belongs to this combination of region and business unit is loaded from the system. This also gives you a filtering option for your version data. In this way, you can, for example, display all versions for a particular combination of region and business unit by using the analytics application Version Overview. For more information, see Configuring Analytics. In the assignment area of version maintenance, you are also shown when the transactional data for this combination of region and business unit was last changed.

Features
Uploading Transactional Data You can upload transactional data from another SAP system, such as SAP SCM, SAP ERP, or SAP NetWeaver BI, or from an external CSV file. To do this, choose Transactional Data Upload Transactional Data. First, enter a version. If you have defined references to versions from source systems, these references are also displayed. Choose the master data and key figures for which you want to upload the transactional data. You can also restrict the date range of the transactional data. If you wish to load data from SAP NetWeaver BI, make sure that for each characteristic value combination (CVC), the values in the BI InfoCube exist for all periods in the same unit of measure or currency. If you wish to load data from Supply Network Planning (SNP) from an SAP SCM system, make sure that you have assigned the SNP planning area, the planning book and the data view to the data source. For more information about defining datasources, see the Configuration Guide for SAP xSOP under Integration with SAP SCM. Enter the corresponding datasource ID in the transaction for uploading transactional data. As a prerequisite, you must also have uploaded mappings for xSOP CVCs to SNP CVCs from an external file. For more information, see Loading Characteristic Value Combinations. Restrict the SNP characteristics to 9ARNAME, 9ALOCNO, and 9AMATNR. Do not assign the SNP characteristics to the xSOP characteristics in Customizing for SAP xSOP (under xSOP Analytics Configure Analytics . In this transaction, map the corresponding SNP key figures from the SAP SCM system to the required xSOP key figures, and specify the newly defined datasource. SAP delivers a series of predefined key figures. For more information see Standard Key Figures.

(C) SAP AG

ADDONX.SCMSOP

15

Downloading Transactional Data You can download transactional data from SAP xSOP back into an SAP SCM system. To do this, choose Transactional Data Download Transactional Data . Enter the corresponding version as well as the master data and key figures whose transactional data you want to load into the SAP SCM system. You can download transactional data into the SCM applications Supply Network Planning (SNP) and Demand Planning (DP). You can only load data into key figures that can be changed in the SCM system (temporary or calculated key figures, for example, cannot be changed). As a prerequisite, you must have mapped the SAP xSOP CVCs to the SAP SCM CVCs. For more information, see Loading Characteristic Value Combinations. Performing Delta Download of BI Transactional Data from TSDM You can carry out a delta download of transactional data from Time Series Data Management (TSDM) into an SAP NetWeaver BI system. In TSDM, SAP xSOP transactional data is stored in the form of time series. For more information, see the documentation for Time Series Data Management. As a prerequisite, you must have configured mapping between SAP xSOP and SAP NetWeaver BI. Choose Transactional Data Perform Delta Download of BI Transactional Data from TSDM . Enter a target file in which the delta data is to be temporarily stored. You use this target file to load the data into the corresponding InfoCube in the SAP NetWeaver BI system. Also enter the SAP Netweaver BI source system, so that the system can identify the delta data. Loading Transactional Data in the Background You can schedule transactional data loading as well as the delta download of BI transactional data to run as a background job. To do this, choose Transactional Data Loading in the Background and then choose the relevant transaction.

(C) SAP AG

ADDONX.SCMSOP

16

Standard Key Figures


For SAP xApp Sales and Operations Planning (SAP xSOP), SAP delivers a series of standard key figures whose calculations are predefined. You can display the key figures and their calculations in Customizing for SAP xSOP by choosing xSOP Basis Configure Data Matrix . You can also create your own new key figures. For more information, see the Implementation Guide (IMG).

Features
In the table below, you can see a list of the standard key figures and their calculations that are delivered by SAP.

(C) SAP AG

ADDONX.SCMSOP

17

Technical Name SOP_DELV_ACT SOP_PROCUR_ACT SOP_PRDCTION_ACT SOP_SALES_ACTC SOP_SALES_ACT SOP_AVG_BDGT_DEV

Name Actual Delivery Quantities Actual Procurement Actual Production Actual Sales (Value) Actual Sales Quantity Average Financial Plan Deviation Average Capacity Available Average Days' Supply Average Inventory (Value) Average Inventory Deviation Average Inventory Turnover

Calculation (If Key Figure Is Calculated)

Aggregation Type Aggregated sum Aggregated sum Aggregated sum

Actual Sales Quantity * Price

Recalculation on each different aggregation level Aggregated sum

Average (Financial Plan Deviation)

Recalculation on each different aggregation level Recalculation on each different aggregation level Recalculation on each different aggregation level Recalculation on each different aggregation level Recalculation on each different aggregation level Recalculation on each different aggregation level

SOP_AVG_CAP_AVL

AVG (Capacity Available)

SOP_AVG_DAY_SUP

AVG (Days' Supply)

SOP_AVG_INVNT_C

AVG (Inventory (Value))

SOP_AVGINVNT_DEV

AVG (Inventory Deviation)

SOP_AVG_INVTURN

AVG (Inventory Turnover)

(C) SAP AG

ADDONX.SCMSOP

18

Technical Name SOP_AVGTURNS_DEV

Name Average Inventory Turnover Deviation Average Margin Deviation Average Production Deviation Average Projected Inventory Financial Plan (Value) Financial Plan (Units) Financial Plan Deviation Budgeted Production Capacity Available (Hours) Capacity Factor Capacity Utilization (Hours)

Calculation (If Key Figure Is Calculated) AVG (Inventory Turnover Deviation)

Aggregation Type Recalculation on each different aggregation level Recalculation on each different aggregation level Recalculation on each different aggregation level Recalculation on each different aggregation level Recalculation on each different aggregation level Aggregated sum

SOP_AVG_MRGN_DEV

AVG (Margin Deviation)

SOP_AVGPROD_DEV

AVG (Production Deviation)

SOP_AVG_PRO_INV

AVG (Projected Inventory)

SOP_BUDGET_C SOP_BUDGET SOP_BUDGET_DEV SOP_BUDGET_PRD SOP_CAPACT_AVAIL SOP_CAPACT_FACTR SOP_CAPACT_USAGE

Financial Plan (Units) * Price/Unit

Demand Plan (Value) - Financial Plan (Value)

Recalculation on each different aggregation level Aggregated sum Aggregated sum

Capacity Factor * Production Plan

Aggregated sum

(C) SAP AG

ADDONX.SCMSOP

19

Technical Name SOP_COST Cost/Unit

Name

Calculation (If Key Figure Is Calculated)

Aggregation Type Aggregated by weighted average (Weight: Demand Plan)

SOP_DAYSOFSUPPLY SOP_DMND_ACCTRGT SOP_DMNDPLAN SOP_DMNDPLAN_C

Days' Supply Demand Accuracy Target Demand Plan Demand Plan (Value)

See description for macro function COVER_CALC() in the documentation for Supply Network Planning (SNP).

Recalculation on each different aggregation level Aggregated sum Aggregated sum

Demand Plan * Price/Unit

Recalculation on each different aggregation level

SOP_DMNDPLAN_ACC

Demand Plan Accuracy

((Demand Plan - Actual Sales Quantity) / Actual Sales Quantity) * Recalculation on each different 1/n aggregation level 100 % * (Demand Plan - Actual Sales Quantity) / Demand Plan Recalculation on each different aggregation level Recalculation on each different aggregation level Recalculation on each different aggregation level Recalculation on each different aggregation level Recalculation on each different aggregation level

SOP_DMNDPLANBIAS

Demand Plan Bias

SOP_DMNDPLAN_DEV

Demand Plan Deviation

Actual Sales Quantity - Demand Plan (Units)

SOP_DMNDPLANMEANC Demand Plan Mean

Avg. of % values (Actual Sales Quantity / Demand Plan) (Units)

SOP_DMNDPLAN_VAR

Demand Plan Variance Global Capacity Utilization

Std Dev. of % Values (Actual Sales Quantity / Demand Plan)

SOP_AVG_CAP_USAG

AVG (Capacity Factor * Production Plan)

(C) SAP AG

ADDONX.SCMSOP

20

Technical Name SOP_FCST_HISTRCL SOP_INVENT_DEV

Name Historical Forecast Inventory Deviation Inventory Turnover Deviation Lagged Demand Plan Margin

Calculation (If Key Figure Is Calculated)

Aggregation Type Aggregated sum

Projected Inventory (Units) - Target Inventory

Recalculation on each different aggregation level Recalculation on each different aggregation level Aggregated sum

SOP_TURNS_DEV SOP_DMNDPLAN_LAG SOP_MARGIN

Turnover - Target Inventory Turnover

Demand Plan * Price/Unit - Demand Plan * Cost/Unit

Recalculation on each different aggregation level Recalculation on each different aggregation level Aggregated sum

SOP_MARGIN_DEV SOP_MARKET_PLAN SOP_MAX_PRO_INV

Margin Deviation Marketing Plan Maximum Projected Inventory Maximum Financial Plan Deviation Maximum Days' Supply Maximum Margin Deviation

Margin - Target Margin

MAX (Projected Inventory)

Recalculation on each different aggregation level Recalculation on each different aggregation level Recalculation on each different aggregation level Recalculation on each different aggregation level

SOP_MAX_BDGT_DEV

MAX (Financial Plan Deviation)

SOP_MAX_DAY_SUP

MAX (Days' Supply)

SOP_MAX_MRGN_DEV

MAX (Margin Deviation)

(C) SAP AG

ADDONX.SCMSOP

21

Technical Name SOP_PRICE SOP_SALESACT_PRY SOP_PROCURPLAN SOP_PRODUCT_DEV SOP_PRODUCTPLAN SOP_INVENT_PROJ SOP_INVENT_PROJC SOP_SALESPLAN SOP_SALESPLANC SOP_SUPPLYPLANC Price/Unit

Name

Calculation (If Key Figure Is Calculated)

Aggregation Type Aggregated by weighted average (Weight: Demand Plan)

Prior Year Actual Sales Procurement Plan Production Deviation Production Plan Projected Inventory Projected Inventory (Value) Sales Plan Sales Plan (Value) Supply plan (value)

Actual Sales Quantity offset by 12 months

Aggregated sum Aggregated sum

Actual Production - Production Plan

Recalculation on each different aggregation level Aggregated sum Aggregated sum

Projected Inventory * Cost/Unit

Recalculation on each different aggregation level Aggregated sum Aggregated sum

Total Supply Plan * Cost/Unit

Recalculation on each different aggregation level Aggregated by weighted average (Weight: Demand Plan) Aggregated sum

SOP_DAYSUPPTRGT SOP_INVENT_TRGT

Target Days' Supply Target Inventory

(C) SAP AG

ADDONX.SCMSOP

22

Technical Name SOP_MARGIN_TRGT SOP_TURNS_TRGC SOP_TURNS_TRGT SOP_TOT_MARGINC

Name Target Margin Tgt Inventory Turnover (Value) Tgt Inventory Turnover Total Margin

Calculation (If Key Figure Is Calculated)

Aggregation Type Aggregated sum Aggregated sum Aggregated by average

SUM (Margin)

Recalculation on each different aggregation level Recalculation on each different aggregation level Aggregated sum Aggregated sum

SOP_TOT_REVENUEC SOP_SUPLPLN_TOT SOP_TRADE_PROMO SOP_TURNS

Total Revenue Total Supply Plan Trade Promotion Turnover

SUM (Demand Plan (Value)) Production Plan + Procurement Plan

Annual Sum (Actual Sales (Units))/Projected Inventory (Units)

Recalculation on each different aggregation level Recalculation on each different aggregation level

SOP_TURNSC

Turnover (Value)

Annual Sum (Actual Sales (Value))/Projected Inventory (Units)

(C) SAP AG

ADDONX.SCMSOP

23

There are two types of key figure on the lowest aggregation level: saved key figures and calculated key figures. Key figures can be aggregated to higher aggregation levels using the following methods. In SAP xSOP, aggregation means that planning data is generated on an aggregated level by adding key figure values from more detailed levels, or by creating an average. Aggregated Sum: The system adds the key figure values. Example The system aggregates the key figure Demand plan, for example, by totals formation (according to period). Demand plan for January Product family: technology 300

Product subfamily: microchips 100 Product subfamily: networks 200

Aggregated by weighted average: The system aggregates the key figure values according to another key figure value that has been chosen as the weighting factor. Example The system aggregates the key figure cost, for example, according to the weighted average (for each period). The weighting factor for the aggregation is the demand plan key figure. Costs in January Demand plan in January Product family: technology 4 300 100 200

Product subfamily: microchips 2 Product subfamily: networks 5

The calculation is as follows: Costs in January = (100*2 + 200*5) / 300 = 4 Aggregated by average: The system aggregates the data for various aggregation levels by calculating the average. Example The system aggregates the target inventory turnover, for example, according to the average (for each period). Target inventory turnover for January Product family: technology 1,9

Product subfamily: microchips 2 Product subfamily: networks 1,8

(C) SAP AG

ADDONX.SCMSOP

24

The calculation is as follows: Target inventory turnover in January = Average (2 + 1.8) =(2 + 1.8) / 2 = 1.9 Recalculation on each different aggregation level: The system recalculates the data on every aggregation level. The system uses the aggregated (saved) key figure value on the given level for the calculation. A recalculation is needed if a key figure in the calculation formula is used that is also recalculated on each aggregation level or aggregrated by average or weighted average. A calculation service is assigned to each calculated key figure in the data matrix. This service tells the system how the key figure is calculated. Example The system aggregates the key figure cost, for example, according to the weighted average (the weighting factor is the demand plan). The cost key figure is then used for calculating the supply plan (value) for each period. The calculation is as follows: Supply plan (value) = total supply plan / costs. Costs in January Product family: technology Product subfamily: microchips Product subfamily: networks 4 Demand plan in January 300 Total supply Supply plan (v plan alue) 200 50

100

50

25

200

150

30

(C) SAP AG

ADDONX.SCMSOP

25

Configuring Analytics
SAP xApp Sales and Operations Planning (xSOP) provides a series of analyses that you can use to analyze and adjust your plans. SAP delivers these analyses preconfigured. This means that it is predefined which key figures appear in which analytic views and charts. You can, however, also configure the analytics yourself. The available analyses and how to configure them, are described below.

Features
Available Analyses The following analyses are available in SAP xSOP. The analyses start on aggregated level with an overview of all versions and then become more detailed: Version Overview The Version Overview gives you an overview of all the versions for a chosen combination of region and business unit. All versions that you have mapped in version maintenance for a particular region and business unit are displayed. The overview contains data for important key figures, such as total revenue and total margin. If you enter a process step when accessing the version overview, the associated tasks, action items and documents of the chosen region and business unit are also displayed. You can also see the date of the most recent change to the transactional data of the version. From the Version Overview, you can call up the Version Details directly by clicking on a version. Version Details The Version Details offer an overview of the data for a particular version. You can display the most important key figures for the product families, product subfamilies, and so on, of this version. For individual characteristic value combinations, you can also display periodic data in specific analytic views (for example, demand and supply). Furthermore, data is also presented in charts. You can call up the associated individual analyses directly from the analytic views. Individual Analyses Individual analyses are available in the following areas: o o o o o Demand analytics Supply analytics Inventory analytics Financial analytics Capacity analytics

The individual analyses offer a wider selection of key figures. Furthermore, they offer you more graphical analytic options than the version-oriented analyses. In addition to the individual analyses, there is an overall analysis, which contains a selection of key figures and charts from the individual analyses.

(C) SAP AG

ADDONX.SCMSOP

26

Configuring the Analyses With the exception of the Version Overview, all analyses are structured in a similar way. In the upper screen area you are presented with an overview of the most important key figure values for the characteristic value combinations of the chosen version. The characteristic value combinations are listed in an aggregation level hierarchy, which you can expand. If you select a characteristic value combination in the upper screen area, further key figure data is displayed in the middle screen area. This key figure data is arranged in tab pages in the analytic views (such as demand and supply). In the lower screen area, key figure data is displayed in charts. You can configure the analyses according to your own requirements. This means you can define: which analytic views and charts are displayed which key figures are displayed in which analytic views and charts in which time bucket profile the key figure values are displayed

To do this, in Customizing for xSOP, choose xSOP Analytics Configure xSOP Analytics or in SAP Netweaver Business Client, choose xSOP Administrator Analytics Analytics Configuration . In this IMG activity, first arrange key figures into key figure groups. Also create aggregation relationships for the aggregation level hierarchy and define time bucket profiles. Assign the key figure groups, aggregation relationships and time bucket profiles to the analyses, analytic views and analytic charts as follows: Analytics: You assign an aggregation relationship, a key figure group, a time bucket profile and analytic views to each analysis Analytic views: You assign a key figure group, a time bucket profile, the sequence for display, and an ID to link to the individual analyses, to each analytic view. The analytic ID is optional. You determine the analytic screen to which you can navigate from this analytic view. If you do not assign a time bucket profile to the analytic view, the system uses the time bucket profile that you have assigned to the analytic ID. Analytic Chart Group: For each analytic view, you can assign a chart group, which will be displayed as a tab page in the chart area of the screen. You can group multiple analytic charts in one chart group and display them on one tab page. You can use the sequence number to define in which order the tab pages are displayed in the analytic view. Analytic charts: You can define the charts that are displayed in the analytic view. You can assign a key figure group and a time bucket profile to each chart. You can use the sequence number to define in which order the charts are displayed on the chart group tab pages. If you do not assign a time bucket profile to the analytic chart, the system uses the time bucket profile that you have assigned to the analytic view. If you also do not assign a time bucket profile to the analytic view, the system uses the time bucket profile that you have assigned to the analytic ID. For the Version Overview, you can only define which key figures are displayed and which time bucket profiles are used. You make these settings in the above mentioned IMG activity, under Basic Settings. You can enter a reference to another analysis by specifying the ID of the analysis from which the system is to determine the key figure group and time bucket profile. We recommend that you enter the reference to the Version Details (delivered by SAP) because this supports the process flow of an SOP process. For more information, see the Implementation Guide (IMG).

(C) SAP AG

ADDONX.SCMSOP

27

(C) SAP AG

ADDONX.SCMSOP

28

Roles for SAP xAPP Sales and Operations Planning (xSOP)


For information about the individual roles in SAP xAPP Sales and Operations Planning (xSOP), see the following documentation: xSOP Planner xSOP Manager xSOP Administrator

(C) SAP AG

ADDONX.SCMSOP

29

xSOP Planner
Role: /SCMSOP/PLANNER You can use this role to perform all the activities you require as a planner in the area of sales and operations planning. Activities in Sales and Operations Planning You can display and edit data in the following screens in SAP xAPP Sales and Operations Planning (xSOP): Screen Process Management All Planning Tasks My Tasks Analytics Version Maintenance Version Overview Version Detail Demand Analytics Supply Analytics Inventory Analytics Financial Analytics Capacity Analytics Overview Analytics Edit Edit Edit Edit Edit Edit Edit Edit Edit Edit Edit Mode

(C) SAP AG

ADDONX.SCMSOP

30

xSOP Manager
Role: /SCMSOP/MANAGER You can use this role to perform all the activities you require as a manager in the area of sales and operations planning. Activities in Sales and Operations Planning You can display and edit data in the following screens in SAP xAPP Sales and Operations Planning (xSOP): Screen Process Management Overview My Process Steps All Tasks My Tasks All Action Items My Action Items Analytics Version Maintenance Version Overview Version Detail Demand Analytics Supply Analytics Inventory Analytics Financial Analytics Capacity Analytics Overview Analytics Edit Edit Edit Edit Edit Edit Edit Edit Edit Edit Edit Edit Edit Edit Edit Mode

(C) SAP AG

ADDONX.SCMSOP

31

xSOP Administrator
Role: /SCMSOP/ADMINISTRATOR You can use this role to perform all the activities you require as an administrator in the area of sales and operations planning. Activities in Sales and Operations Planning You can display and edit data in the following screens in SAP xAPP Sales and Operations Planning (xSOP): Screen Master Data Upload Master Data Maintain Master Data Upload CVCs Maintain CVCs Maintain CVC Mapping Upload CVC Mapping Upload Product - Product Subfamily Mapping Maintain Product - Product Subfamily Mapping Upload Master Data in the Background Delete Master Data in the Background Upload CVCs in the Background Upload Product - Product Subfamily Mapping in the Background Transactional Data Upload Transactional Data Download Transactional Data Perform Delta Download of BI Transact. Data from TSDM Upload Transactional Data in the Background Perform Delta Download of BI Transact. Data from TSDM in the Background Process Management Overview Edit Edit Edit Edit Edit Edit Edit Edit Edit Edit Edit Edit Edit Edit Edit Edit Edit Edit Mode

(C) SAP AG

ADDONX.SCMSOP

32

All Process Steps My Process Steps All Tasks My Tasks All Action Items My Action Items Analytics Analytics Configuration Version Maintenance Version Overview Version Detail

Edit Edit Edit Edit Edit Edit

Edit Edit Edit Edit

(C) SAP AG

ADDONX.SCMSOP

33

Process Management
In SAP xApp Sales and Operations Planning (SAP xSOP), you can track your SOP process by defining process steps, tasks and action items. You can assign persons responsible as well as monitor due dates and the completion status. In this way, you ensure that your SOP process is successfully carried out before a management review meeting for the overall plan, and that any action items that arise from the meeting are completed.

Features
Objects in Process Management You first create process steps for the individual steps of your SOP process and assign tasks and action items to them. Action items are assigned directly to process steps in the way that tasks are. In other words, the action items are not assigned via tasks. The objects differ as follows: Process step: A series of tasks that must be completed in the run-up to an SOP meeting, or action items that are agreed during the meeting. For a process step, among other things, you can define the following: o o o o Region and business unit (required) Responsible person Due date (required) Tasks and action items

You always define a process step for a particular region and business unit. You can also assign documents to the process step. For more information see Document Management. Task: An activity that must be completed by the responsible person in the run-up to an SOP meeting. As opposed to the action items, a task is a future activity that you plan in advance, alongside the process steps. For a task, among other things, you can define the following: o o o o o o Responsible person Due date (required) Completion status Long text (freely definable) Analytic application External user

If you define an analytic application, the user is given a link to this analysis in the task overview of his tasks. In this way, he can directly call up the relevant analyses for his tasks.

(C) SAP AG

ADDONX.SCMSOP

34

The External User is a responsible person who does not have a user in the SAP xSOP system. The due date of the task must not fall after the due date of the process step. Action item: An activity, that can, for example, be defined during an SOP meeting. This activity differs from a task in that it is more of an unplanned reaction to a current situation. For an action item, among other things, you can define the following: o o o o o Responsible person Due date (required) Completion status Long text External user

The due date of an action item must fall after the due date of the process step, since it is a measure created in response to the process step. If the due date is to fall before the end of the process step, then you must create a task instead. You can copy process steps and tasks. If you copy a process step, you can choose the tasks that are also to be copied. Tasks can only be copied individually. Since action items tend to be one-off activities, there is no provision for copying them. Displaying and Maintaining Process Management There are a various options for displaying and maintaining process management objects: Process Management Overview You are presented with an overview of all process steps, tasks and action items for a particular month. Here, you can create and maintain new process steps with tasks and action items. Above all, you can use this transaction to define the basic structure of the process at the start of an SOP process. For more information, see Creating the Basic Structures of the Process. All Process Steps / Tasks /Action Items: You can use these three transactions to display all process steps, tasks or action items in a particular period for a specific combination of region and business unit, and for all responsible persons. My Process Steps / Tasks /Action Items: You can use these three transactions to display and maintain all process steps, tasks, or action items for which you are responsible. If you choose My Process Steps, you are presented with a list of process steps that are assigned to you. If you click on a process step, the system displays all the associated tasks and action items, regardless of whether you are responsible for them or not. In the transactions My Tasks and My Action Items, the associated documents are also displayed in the the overview (documents are always assigned to the process step).

(C) SAP AG

ADDONX.SCMSOP

35

You can see a complete overview of all tasks, action items, and documents for a particular process step by using the Version Overview. Note Note, that the authorizations for creating process steps, tasks, and so on, as well as for accessing the various views depend on the role that has been assigned to you. Thus, the xSOP planner, for example, cannot create or delete tasks, and can only edit the completion status. Only the administrator can define responsible persons; the manager does not see this field. In the process management overview, a manager only sees the process steps that he is responsible for. For more information, see Roles in SAP xApp Sales and Operations Planning (SAP xSOP).

(C) SAP AG

ADDONX.SCMSOP

36

Document Management
In SAP xApp Sales and Operations Planning (SAP xSOP), you can assign documents to the process steps that you created. SAP xSOP supports all popular file formats, such as Microsoft Office Word, Powerpoint, and Excel. You can also assign notes.

Integration
You can set up SAP xSOP to be integrated with the document management system SAP PLM Collaboration Folders (cFolders). For more information, see the Configuration Guide for SAP xSOP under Integration with cFolders. You store the documents in cFolder and assign them in SAP xSOP. SAP xSOP establishes a link to the documents stored in cFolders. You can call up cFolders directly from the screens where you assign documents in SAP xSOP. For more information, see the documentation for your cFolders system.

Prerequisites
In cFolders, you have stored the documents that you want to assign.

Features
When you create or maintain a process step (see Process Management), you can assign a document that you have already stored in cFolders, to the process step. On the screen for creating or maintaining a process step, choose Documents. If you have not yet stored any documents in cFolders, you can call up the cFolders system by choosing Document Management. If documents already exist, choose Assign. In the assignment view, you can also store notes and assign them to the process step.

(C) SAP AG

ADDONX.SCMSOP

37

Sales and Operations Planning Process


SAP xApp Sales and Operations Planning (SAP xSOP) supports the complete SOP process. In this process, you reconcile various plans from different departments and for different business scenarios and create an overall plan.

Process
The following describes an example SOP process and how SAP xSOP supports it. 1. Creating the Basic Structures of the Process You define the process steps and tasks that are valid long-term and beyond one process cycle. You can use and reuse these structures as a basis for the individual process cycles. For more information, see Creating the Basic Structures of the Process. 2. Modeling strategic plans You model the various plans, which serve as a basis for your overall plan, for a process cycle in the SAP xSOP system. For more information, see Modeling Strategic Plans. 3. Analyzing, Adjusting and Reconciling Plans You check you plans in the SAP xSOP analytic applications, adjust them if necessary, and reconcile the different plans with each other. The result is that you are given suggestions for an overall plan that will be decided on during the management review meeting. For more information, see Analyzing, Adjusting, and Reconciling Plans. 4. Management Review of the Overall Situation At the end of the SOP process, the participants of a management review meeting decide on the overall plan, which will form the basis for the work carried out in the different departments of your company. For more information, see Management Review of the Overall Situation.

(C) SAP AG

ADDONX.SCMSOP

38

Creating the Basic Structures of the Process


When you start an SOP process in SAP xApp Sales and Operations Planning (SAP xSOP), you define the basic structures of the process. This means that you define the process structure that is valid in the long-term and beyond a process cycle, and that is only subject to minor changes.

Process
To create the basic structures, choose Process Management Overview (SAP NetWeaver Business Client), or Process Management Process Management Overview (SAP GUI). On this screen, you are presented with an overview of all process steps, tasks and action items. You can also create and edit these objects here. For more information see Process Management. Then proceed as follows: 1. Create process steps Decide the general steps for your SOP process and create the process steps in SAP xSOP Process Management. Process steps can be, for example, the modeling of strategic plans and the analysis and adjustment of the plans. You always define the process steps for a particular region and business unit. You can later copy these process steps for the individual process cycles (monthly, for example) and assign a new due date or make other adjustments. 2. Assign tasks Create tasks for each process step. Most tasks in an SOP process are recurrent tasks. Although changes can be made, certain data such as responsibilities, however, usually remains the same in the long-run. You can also copy and adjust the tasks for the process cycles at a later date. 3. Assign documents Assign documents to the process step. You can assign general documents that are valid long-term and do not relate to a specific process run - such as descriptions of the overall process, guidelines, and annual targets.

(C) SAP AG

ADDONX.SCMSOP

39

Modeling Strategic Plans


Before you start a new process cycle and can analyze and reconcile your various plans, you must model these plans for the new cycle in SAP xApp Sales and Operations Planning (SAP xSOP).

Process
To model your plans proceed as follows: 1. Update master data Ensure that all the master data for the current process cycle is available in the SAP xSOP system, and that it is up-to-date. If you want to introduce a new product, for example, the master data of this product should exist in SAP xSOP. For more information, see Loading Master Data and Loading Characteristic Value Combinations. 2. Check the versions In Version Maintenance, check that all the required version are available in the SAP xSOP system. You can create new versions in the system or copy existing versions from previous process cycles. Recommendation We recommend that you create as few versions as possible. It is sensible, for example, to create versions for different business scenarios, which each contain all the different plans, such as demand plan or supply plan, for the particular scenario. This provides a good means of comparing the business scenarios. You can, for example, model the effect of a price increase or cost reduction for various points in time and to differing extents in business scenarios and thus also in versions. As a basis for the various scenarios, you can also copy the version with the reconciled overall plan of the previous process cycle, for example, and compare the versions with the new business scenarios. 3. Loading Transactional Data Ensure that the required transactional data from an SAP system or an external file is loaded into the versions that you want to use in this process. You can use SAP SCM, SAP ERP, or SAP NetWeaver BI as source systems. For more information, see Loading Transactional Data.

(C) SAP AG

ADDONX.SCMSOP

40

Analyzing, Adjusting and Reconciling Plans


Once you have modeled your plans and the data for the current process cycle is available, you can use the analytics applications in SAP xApp Sales and Operations Planning (SAP xSOP) to analyze, adjust and reconcile your plans.

Prerequisites
You have configured the analytic applications according to your individual requirements. For more information about the various analyses and their configuration, see Configuring the Analyses.

Process
To analyze, adjust and reconcile your plans, proceed as follows: 1. Analyze individual plans Call up the individual plans in the individual analyses (for example, the demand analysis for the demand plan, or the supply analysis for your supply plan). In the upper screen area, you can expand the aggregation structure of the aggregated characteristics (such as product family) to view the lower levels of the hierarchy (such as product subfamily, locations and resources). In the middle screen area, the detailed key figure data for the characteristic value combinations then appears. In the lower screen area, your data is presented in chart form. 2. Adjust the plans If you wish to make adjustments, you can change the values of individual key figures in the demand and supply plans (such as the Demand Plan key figure). To do this, in the key figure view in the middle screen area of the individual analysis, choose Change. The changeable key figures are then ready to be edited. Note that only data on and below the product family level can be changed. This means you cannot change data on the top level of the aggregation hierarchy, in other words the region and business unit level. The system breaks down the key figure values to the lower aggregation levels. The dependent key figures are updated. 3. Reconcile the plans You can display the various plans that you have saved in a version as part of a business scenario, for example, in the the Version Details analytics. In the middle screen area, the most important key figures of the different plans (such as demand and supply) are displayed. In this way, you can compare and reconcile the plans. If you need more detailed information to reconcile the plans, you can open and compare them in multiple individual analytics. 4. Choose plans for management review When you have reconciled the plans within a version (such as the plans for a business scenario), you can compare the plans from the different versions (and therefore different scenarios) with each other. You can make this comparison in the Version Overview, where the most important data for the different versions is displayed. After you have compared the versions, you can choose the versions and the possible overall plans that you want to present and discuss in the management review.

(C) SAP AG

ADDONX.SCMSOP

41

Management Review of the Overall Situation


The aim of a process cycle in SAP xApp Sales and Operations Planning (SAP xSOP), is to create an overall plan that forms the basis for the work carried out by different departments within your enterprise. At the end of the process cycle, there is a management review meeting, where the overall plan is decided.

Prerequisites
You have created a process step for the management review meeting and assigned the required documents, such as Microsoft PowerPoint presentations. For more information, see Creating the Basic Structure of the Process and Process Management.

Process
To define the overall plan in the management review meeting, proceed as follows: 1. Compare the plans available for selection In the meeting, call up the Version Overview. In this analytics application you are presented with an overview of the aggregated data for the different versions and thus the overall plans available for you to choose. You also have access to the associated documents and information about the assigned tasks. If you require more detailed data, you can call up the Version Details from this screen. From there, you can jump to the individual analytics. In the upper area of the Version Details screen, the same most important key figures are displayed as in the Version Overview. You can expand the data from lower aggregation levels, and display the most important key figure values. During the meeting, you can still change certain key figure values using the version details screen and the individual analyses. 2. Decide on an overall plan The participants of the meeting decide on an overall plan. If the participants cannot reach a decision, or if further activities are needed, you can also create action items directly in the Version Overview or in the Version Details. 3. Retransmit the overall plan data to the source systems When the participants of the meeting reach a decision, the data from this plan can be sent back to certain source systems. You can download data into an SAP SCM system or carry out a delta download of SAP BI transactional data from the Time Series Data Management (TSDM) into an SAP NetWeaver BI system. For more information, see Loading Transactional Data. As an alternative, or in addition to this, you can communicate the results of the meeting to the planners and other relevant people. These communications are also supported by the SAP xSOP process management (by using action items and tasks, for example).

(C) SAP AG

ADDONX.SCMSOP

42