sop5.1 docu en

5/16/2018 Sop5.1 Docu En - slidepdf.com

http://slidepdf.com/reader/full/sop51-docu-en 1/42

Sales and Operations Planning

Release 510

A

D

D

O

N

X . S C

M

S O

P



(C) SAP AG ADDONX.SCMSOP 2

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 bechanged without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietarysoftware components of other software vendors.

Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of MicrosoftCorporation.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 PowerPCare trademarks or registered trademarks of IBM Corporation.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registeredtrademarks 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 aretrademarks or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, WorldWide 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 fortechnology 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 andservices mentioned herein as well as their respective logos are trademarks or registeredtrademarks of SAP AG in Germany and in several other countries all over the world. All otherproduct and service names mentioned are the trademarks of their respective companies.Data contained in this document serves informational purposes only. National productspecifications may vary.

These materials are subject to change without notice. These materials are provided by SAPAG and its affiliated companies ("SAP Group") for informational purposes only, withoutrepresentation or warranty of any kind, and SAP Group shall not be liable for errors oromissions with respect to the materials. The only warranties for SAP Group products andservices are those that are set forth in the express warranty statements accompanying suchproducts and services, if any. Nothing herein should be construed as constituting anadditional warranty.




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 anyversion of SAP Library .

Typographic Conventions

Type Style Description

Example text Words or characters quoted from the screen. These include fieldnames, screen titles, pushbuttons labels, menu names, menu paths,and menu options.

Cross-references to other documentation.

Example text Emphasized words or phrases in body text, graphic titles, and tabletitles.

EXAMPLE TEXT Technical names of system objects. These include report names,program names, transaction codes, table names, and key concepts of aprogramming language when they are surrounded by body text, forexample, SELECT and INCLUDE.

Example text Output on the screen. This includes file and directory names and theirpaths, messages, names of variables and parameters, source text, andnames of installation, upgrade and database tools.

Example text Exact user entry. These are words or characters that you enter in thesystem exactly as they appear in the documentation.

<Example text> Variable user entry. Angle brackets indicate that you replace thesewords and characters with appropriate entries to make entries in thesystem.

EXAMPLE TEXT Keys on the keyboard, for example, F2 or ENTER.




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................................................................... 41Management Review of the Overall Situation ................................................................ 42





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

The following graphic shows the sales and operations planning process:


Document Management

Document Management Tas k and Act ion It em Management

Tas k and Act ion It em Management

Product Launch SOP Meeting

Strateg. PlanningProcurementPlanning

•Market Planning•Product P lanning•Resource Planning

Demand PlanningReconciling Demand

and Supply

ManagementRevi ew

& Analysis

•Quantitativ e Forecasting•Input v s. Marketing/Sales•Demand Rec onciliation

•Key Figure Ev aluation•Plan vs. Actual•Forecast Error•Margin Management

•Cause Analyse

•Product Mix•Constraint Management•Supply & DemandReconciliation

•Capacity Planning•Stock P lanning•Procurement Planning•Logistics

Define

Tasks

SOP Process

Track/Update

Tasks

DefineAction Items

Track/UpdateAction Items

Confirm

Tasks

CompleteAction Items

AttachDocuments

CheckDocuments

S O P U I I n t e r f a c e L a y e r

SO P U I I n t e r f a c e L a y e r

S O P A p p l i c at io n L a y e r

S O P A p p l i ca t i o n L a y e r

Off i ceInterfaces

OfficeIn te rf aces

Data StorageLayers

Data StorageLayers

O rd e r D a ta

M a n a g em ent( O D M )

Tim e Ser ies

Dat a M g m t(T S D M )

A2X

n

MIF 2

IF

n

MIF 2

IF

BusinessProce sses

BusinessProcesses

ProcessComponent

n

MIF2

BPO

ProcessComponent

n

MIF2

BPO

n

MIF2

BPO

ProcessComponent

n

MIF2

BPO

ProcessComponent

n

MIF2

BPO

n

MIF2

BPO

ProcessComponent

Transact.DataAccess Layer(TDL)

Trans act.DataAccess Layer (T DL)

BW I nfo P r o vi d e r

S O P U I P r e s e n t at i o n L a y e r

S O P U I P r es e n t a t i o n L a y e r

SCM Basis MasterDataObjects

SCM BasisMasterData Objec ts

Pla n n in g O b jectStr uc ture ( P O S)



SO P I n t e g r a t i o n L a y e r

SO P I n t e g r a t i o n L a y e r

DocumentManagement

System/ Interfaces

DocumentManagement

S ys tem/In terf aces

External SystemInterfaces

ExternalSystemInte rfaces

A2X

X I In te r facesX

I Interfaces

S CM_B A S IS

Master DataInterfaces

MasterDa taInterfaces

Trans. DataInterfaces

Trans .DataInterfaces

SOP Analytics

SOP Analytics

Key Figures

& Metric s

Comparison

& Simulation

SupplyAnalytics

InventoryAnalytics

Demand

Analytics

FinancialAnalytics

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 deltadownload of transactional data to an SAP NetWeaver BI system is available.

For more information, see the Configuration Guide for SAP xSOP.




Features

You can use SAP xSOP to analyze and compare plans from various enterprise areas and forvarious business scenarios, as well as to check alternative plans. SAP xSOP supports thefollowing 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 bothan overview of the data for multiple plans as well as a detailed view of the data for individualplans. You can also adjust the analyses to meet your individual requirements and create yourown key figures.

After reconciling individual plans, you can create an enterprise-wide demand andprocurement plan in a management review meeting. The meeting is supported by anoverview analysis. Thus, different departments, such as Marketing, Finance, Production andLogistics, 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 withtasks and action items, check their completion statuses, and manage associated documents,such as Microsoft PowerPoint presentations and Excel sheets.




Configuring the SAP xSOP System

You can configure SAP xApp Sales and Operations Planning (SAP xSOP) according to yourindividual 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 SAPsystems or external files, as well as creating new master data and CVCs in the SAPxSOP 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




Using the SAP GUI or SAP Netweaver Business Client

You can use two different types of user interface with SAP xApp Sales and OperationsPlanning (SAP xSOP): SAP GUI or SAP Netweaver Business Client. The business client is adesktop-based integration platform, which allows you to seamlessly use classic SAP GUI-based 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 userinterface software, see SAP Note 1021856. The basic differences between the two userinterfaces are outlined below.

Features

SAP GUI

In the classic SAP GUI environment you can access both SAP GUI and Web Dynprotransactions. SAP GUI transactions are displayed in the SAP GUI session. A separate webbrowser window opens for Web Dynpro transactions.

Two types of application menu are available: the SAP Easy Access menu and a user-specificmenu. If you have assigned roles to the user, the user-specific menu is displayed based onthe roles assigned. For more information, see Roles in SAP xApp Sales and OperationsPlanning.

SAP Netweaver Business Client

In the SAP NetWeaver Business Client, all transactions are displayed on one standard userinterface. The SAP GUI transactions and Web Dynpro transactions appear in the main screenarea. 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 toall of the standard transactions available for your role are displayed. You can also use thesession tab area to navigate between all transactions that you have already called up in the

current session.




Loading Master Data

In SAP xApp Sales and Operations Planning (SAP xSOP), you can upload and maintainmaster 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 SAPxSOP 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 thesections 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 datasource 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 aresource has been transferred from an SAP ERP system into an SAP SCM system, forexample, you should specify the name of the logical ERP system. As a prerequisite foruploading capacity utilization data, you must first map products to product subfamilies. Formore information, see the section "Uploading and Maintaining Product-Product SubfamilyMapping". 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 changesyou make will have no effect on an SAP SCM or other system. You can also copy individualmaster data objects.

You must create certain master data in SAP xSOP, since you cannot upload characteristicvalues for the characteristics "Product Family", "Product Subfamily", "Region", and "BusinessUnit" (which form the master data). Creating characteristic values is a prerequisite foruploading or mapping characteristic value combinations in later steps.

To maintain master data, choose Master Data Maintain Master Data . Enter the masterdata 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




In SAP xSOP, you mainly consider and maintain aggregated data. Therefore, you must createa product hierarchy. You can create product subfamilies using the master data maintenancein the SAP xSOP system or upload them from a source system. You can either uploadmappings for products and product subfamilies, or create them in the SAP xSOP system. Todo 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, chooseMaster Data Master Data Processing in the Background Delete Master Data in the

Background . You cannot delete master data that is used in existing characteristic valuecombinations.




Loading Characteristic Value Combinations

In SAP Sales and Operations Planning (SAP xSOP), SAP delivers the planning objectstructure 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 thecombinations of the possible values for characteristics, from a source system into the SAPxSOP system or create them yourself in the SAP xSOP system. A CVC is, for example, theproduct family "cosmetics" and the product subfamily "shampoo" in the region "Europe". Thefollowing 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 valuecombinations are exactly the same in SAP xSOP and in the other SAP systems.

2. The number of characteristics, characteristic values and characteristic valuecombinations 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 CSVformat into the SAP xSOP system, or create them manually in the SAP xSOP system. Formore information, see the "Loading CVCs" and "Maintaining CVCs" sections. The two casesdiffer from each other in how you map the characteristics from an SAP system to thecharacteristics in the SAP xSOP system.

• In the first case, you can define the mapping of characteristics from the SAP systemto the SAP xSOP characteristics in Customizing for SAP xSOP before you load theCVCs. In this case, the system replaces the characteristics from the source systemwith 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 CVCsand SAP xSOP CVCs from an external flat file after you have uploaded or created theCVCs in the SAP xSOP system. For more information, see the "Loading CVCMapping" and "Maintaining CVC Mapping" sections.

Uploading CVCs

Choose Master Data Upload CVCs . Enter the source type and source ID and chooseStart CVC Transfer . You must have already created data sources in Customizing for

SAP xSOP under Analytics Configure xSOP Analytics or in the SAP NetWeaverBusiness Client under xSOP Administrator Analytics Analytics Configuration . For more

information, see the Implementation Guide (IMG).




You are presented with an overview of the characteristic values combinations, from which youcan choose the required objects. You can also export the CVCs into a Microsoft Excel file orinto the Business Explorer Analyzer (BEx Analyzer). Note, that you must save your data afterloading 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, chooseMaster 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 thatexists in the system. This means the data that you have already loaded into the SAP xSOPsystem 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 alist 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 newCVCs, you can also copy rows from this list. You can export the CVCs into a Microsoft Excelfile or into the BEx Analyzer.

Mapping Characteristics in Customizing

If the number of characteristics, characteristic values, and CVCs in SAP xSOP and your otherSAP system match exactly, you can define the mapping for the characteristics from your SAPsystem and xSOP system in Customizing for SAP xSOP before you upload the CVCs bychoosing the above named transaction Configure xSOP Analytics . The characteristic valuesremain unchanged. For more information, see the Configuration Guide for SAP xSOP underIntegration with cFolders and also the Implementation Guide.

Example

The following example shows which CVCs in the source system correspond to which CVCs inthe SAP xSOP system once you have uploaded the CVCs.

CVCs in the SAP System

Z_BUNIT Z_REGION 9ASOPPRDGRP 9AMATNR 9ALOCNO 9ARNAME

Business unit 1 Region 1 Product Group 1 Product 1 Location 1 Resource: 1


CVCs in SAP xSOP

9ASOPUNIT 9ASOPREG 9ASOPPRFAM 9ASOPPRDSF 9ASOPLOC 9ASOPRESC






Uploading CVC Mapping

If the characteristic values or number of CVCs in the SAP xSOP system do not match thosein the other SAP system, you must upload the CVC mappings from an external file. Note, thatin this case you cannot map the characteristics by using the the customizing transactionConfigure xSOP Analytics (which was described above).

Before you upload CVC mappings, you must upload the CVCs into the SAP system (asdescribed above) or create them directly in the SAP xSOP system. You can define whichCVCs in a source system correspond to which CVCs in the SAP xSOP system. In this way, aCVC 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 canbe mapped to multiple CVCs from a source system. The reverse mapping, n:1, is notpossible.

Choose Master Data Upload CVC Mapping . You can only upload CVC mappings usingan 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 isrestricted to seven.




Example The following example shows how you define the CVC mapping in an external file. It alsoshows the result that you get in the SAP xSOP once you have uploaded the CVC mappings.

CVCs in the SAP System

0COUNTRY 9ALOCNO 9AMATNR

France Paris 1 Shampoo

France Paris 2 Shampoo

CVCs in the SAP xSOP System


Western Europe Region 1 Hair Care Product subfamily 1 Paris Resource: 1

Structure of External File

Data sourceID


0COUNTRY 9ALOCNO 9AMATNR

WesternEurope

Region 1 Hair CareProductsubfamily 1

Paris Resource: 1 FranceParis1

Shampoo

WesternEurope

Region 1 Hair Care Productsubfamily 1

Paris Resource: 1 France Paris2

Shampoo

Result: CVC Mapping in SAP xSOP


WesternEurope



Shampoo

WesternEurope



Shampoo

Maintaining CVC Mapping

You can display and delete CVC mappings that you have already loaded into the SAP xSOPsystem. To do this, choose Master Data Maintain CVC Mapping .

In the selection area, specify the characteristic values and the source system ID. The systemthen displays the list of CVC mappings in the overview area. You can delete CVC mappingsor export them into a Microsoft Excel file or into the BEx Analyzer. You can also display CVCsfor which no mapping has been defined.




Loading Transactional Data

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

Prerequisites

The transactional data is saved in an xSOP version. You have created this version underAnalytics 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, SAPSCM or SAP NetWeaver BI system, you must have mapped an existing version of the sourcesystem to an existing SAP xSOP version.

Furthermore, you have assigned a combination of the region and business unit characteristicsto the version. Only the transactional data that belongs to this combination of region andbusiness unit is loaded from the system. This also gives you a filtering option for your versiondata. In this way, you can, for example, display all versions for a particular combination ofregion and business unit by using the analytics application Version Overview . For moreinformation, see Configuring Analytics.

In the assignment area of version maintenance, you are also shown when the transactionaldata 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, thesereferences are also displayed. Choose the master data and key figures for which you want toupload 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 valuecombination (CVC), the values in the BI InfoCube exist for all periods in the same unit ofmeasure 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 dataview to the data source. For more information about defining datasources, see theConfiguration Guide for SAP xSOP under Integration with SAP SCM . Enter the correspondingdatasource ID in the transaction for uploading transactional data.

As a prerequisite, you must also have uploaded mappings for xSOP CVCs to SNP CVCs froman external file. For more information, see Loading Characteristic Value Combinations.Restrict the SNP characteristics to 9ARNAME, 9ALOCNO, and 9AMATNR. Do not assign theSNP 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 newlydefined datasource.

SAP delivers a series of predefined key figures. For more information see Standard KeyFigures.




Downloading Transactional Data

You can download transactional data from SAP xSOP back into an SAP SCM system. To dothis, choose Transactional Data Download Transactional Data . Enter the correspondingversion as well as the master data and key figures whose transactional data you want to loadinto 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 bechanged in the SCM system (temporary or calculated key figures, for example, cannot bechanged).

As a prerequisite, you must have mapped the SAP xSOP CVCs to the SAP SCM CVCs. Formore 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 storedin the form of time series. For more information, see the documentation for Time Series DataManagement. As a prerequisite, you must have configured mapping between SAP xSOP andSAP 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. Alsoenter 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 transactionaldata to run as a background job. To do this, choose Transactional Data Loading in the Background and then choose the relevant transaction.




Standard Key Figures

For SAP xApp Sales and Operations Planning (SAP xSOP), SAP delivers a series ofstandard key figures whose calculations are predefined. You can display the key figures andtheir 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 theImplementation Guide (IMG).

Features

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



(C) SAP AG ADDONX.SCMSOP

Technical Name Name Calculation (If Key Figure Is Calculated)

SOP_DELV_ACT Actual Delivery Quantities

SOP_PROCUR_ACT Actual Procurement

SOP_PRDCTION_ACT Actual Production

SOP_SALES_ACTC Actual Sales (Value) Actual Sales Quantity * Price

SOP_SALES_ACT Actual Sales Quantity

SOP_AVG_BDGT_DEV Average Financial PlanDeviation Average (Financial Plan Deviation)

SOP_AVG_CAP_AVLAverage CapacityAvailable

AVG (Capacity Available)

SOP_AVG_DAY_SUP Average Days' Supply AVG (Days' Supply)

SOP_AVG_INVNT_CAverage Inventory(Value)

AVG (Inventory (Value))

SOP_AVGINVNT_DEV Average InventoryDeviation AVG (Inventory Deviation)

SOP_AVG_INVTURNAverage InventoryTurnover

AVG (Inventory Turnover)





SOP_AVGTURNS_DEVAverage Inventory

Turnover Deviation

AVG (Inventory Turnover Deviation)

SOP_AVG_MRGN_DEVAverage MarginDeviation

AVG (Margin Deviation)

SOP_AVGPROD_DEVAverage ProductionDeviation

AVG (Production Deviation)

SOP_AVG_PRO_INVAverage ProjectedInventory

AVG (Projected Inventory)

SOP_BUDGET_C Financial Plan (Value) Financial Plan (Units) * Price/Unit

SOP_BUDGET Financial Plan (Units)

SOP_BUDGET_DEV Financial Plan Deviation Demand Plan (Value) - Financial Plan (Value)

SOP_BUDGET_PRD Budgeted Production

SOP_CAPACT_AVAILCapacity Available(Hours)

SOP_CAPACT_FACTR Capacity Factor

SOP_CAPACT_USAGECapacity Utilization(Hours)

Capacity Factor * Production Plan





SOP_COST Cost/Unit

SOP_DAYSOFSUPPLY Days' SupplySee description for macro function COVER_CALC() in thedocumentation for Supply Network Planning (SNP).

SOP_DMND_ACCTRGT Demand Accuracy Target

SOP_DMNDPLAN Demand Plan

SOP_DMNDPLAN_C Demand Plan (Value) Demand Plan * Price/Unit

SOP_DMNDPLAN_ACC Demand Plan Accuracy ((Demand Plan - Actual Sales Quantity) / Actual Sales Quantity)1 / n

SOP_DMNDPLANBIAS Demand Plan Bias 100 % * (Demand Plan - Actual Sales Quantity) / Demand Plan

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 Std Dev. of % Values (Actual Sales Quantity / Demand Plan)

SOP_AVG_CAP_USAGGlobal CapacityUtilization

AVG (Capacity Factor * Production Plan)





SOP_FCST_HISTRCL Historical Forecast

SOP_INVENT_DEV Inventory Deviation Projected Inventory (Units) - Target Inventory

SOP_TURNS_DEVInventory TurnoverDeviation

Turnover - Target Inventory Turnover

SOP_DMNDPLAN_LAG Lagged Demand Plan

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

SOP_MARGIN_DEV Margin Deviation Margin - Target Margin

SOP_MARKET_PLAN Marketing Plan

SOP_MAX_PRO_INVMaximum ProjectedInventory

MAX (Projected Inventory)

SOP_MAX_BDGT_DEVMaximum Financial PlanDeviation

MAX (Financial Plan Deviation)

SOP_MAX_DAY_SUP Maximum Days' Supply MAX (Days' Supply)

SOP_MAX_MRGN_DEVMaximum MarginDeviation

MAX (Margin Deviation)





SOP_PRICE Price/Unit

SOP_SALESACT_PRY Prior Year Actual Sales Actual Sales Quantity offset by 12 months

SOP_PROCURPLAN Procurement Plan

SOP_PRODUCT_DEV Production Deviation Actual Production - Production Plan

SOP_PRODUCTPLAN Production Plan

SOP_INVENT_PROJ Projected Inventory

SOP_INVENT_PROJCProjected Inventory(Value)

Projected Inventory * Cost/Unit

SOP_SALESPLAN Sales Plan

SOP_SALESPLANC Sales Plan (Value)

SOP_SUPPLYPLANC Supply plan (value) Total Supply Plan * Cost/Unit

SOP_DAYSUPPTRGT Target Days' Supply

SOP_INVENT_TRGT Target Inventory





SOP_MARGIN_TRGT Target Margin

SOP_TURNS_TRGCTgt Inventory Turnover(Value)

SOP_TURNS_TRGT Tgt Inventory Turnover

SOP_TOT_MARGINC Total Margin SUM (Margin)

SOP_TOT_REVENUEC Total Revenue SUM (Demand Plan (Value))

SOP_SUPLPLN_TOT Total Supply Plan Production Plan + Procurement Plan

SOP_TRADE_PROMO Trade Promotion

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

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




There are two types of key figure on the lowest aggregation level: saved key figures andcalculated key figures. Key figures can be aggregated to higher aggregation levels using thefollowing methods. In SAP xSOP, aggregation means that planning data is generated on anaggregated level by adding key figure values from more detailed levels, or by creating anaverage.

• 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 valuesaccording 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 weightedaverage (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

Product subfamily: microchips 2 100

Product subfamily: networks 5 200

The calculation is as follows: Costs in January = (100*2 + 200*5) / 300 = 4

• Aggregated by average: The system aggregates the data for various aggregationlevels by calculating the average.

Example

The system aggregates the target inventory turnover, for example, according to theaverage (for each period).

Target inventory turnover for January

Product family: technology 1,9

Product subfamily: microchips 2

Product subfamily: networks 1,8




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 thedata on every aggregation level. The system uses the aggregated (saved) key figurevalue 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 oraggregrated by average or weighted average.

A calculation service is assigned to each calculated key figure in the data matrix. Thisservice tells the system how the key figure is calculated.

Example

The system aggregates the key figure cost , for example, according to the weightedaverage (the weighting factor is the demand plan). The cost key figure is then usedfor calculating the supply plan (value) for each period. The calculation is as follows:Supply plan (value) = total supply plan / costs.

Costs inJanuary

Demand plan inJanuary

Total supplyplan

Supply plan (value)

Product family:technology

4 300 200 50

Product subfamily:microchips

2 100 50 25

Product subfamily:networks

5 200 150 30




Configuring Analytics

SAP xApp Sales and Operations Planning (xSOP) provides a series of analyses that you canuse to analyze and adjust your plans. SAP delivers these analyses preconfigured. Thismeans that it is predefined which key figures appear in which analytic views and charts. Youcan, 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 levelwith 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 chosencombination of region and business unit. All versions that you have mapped inversion maintenance for a particular region and business unit are displayed. Theoverview contains data for important key figures, such as total revenue and totalmargin.

If you enter a process step when accessing the version overview, the associatedtasks, action items and documents of the chosen region and business unit are alsodisplayed. You can also see the date of the most recent change to the transactionaldata of the version.

From the Version Overview , you can call up the Version Details directly by clicking ona version.

• Version Details

The Version Details offer an overview of the data for a particular version. You candisplay the most important key figures for the product families, product subfamilies,and so on, of this version. For individual characteristic value combinations, you canalso display periodic data in specific analytic views (for example, demand andsupply). 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 Demand analytics

o Supply analytics

o Inventory analytics

o Financial analytics

o Capacity analytics

The individual analyses offer a wider selection of key figures. Furthermore, they offer youmore graphical analytic options than the version-oriented analyses.

In addition to the individual analyses, there is an overall analysis, which contains a selectionof key figures and charts from the individual analyses.




Configuring the Analyses

With the exception of the Version Overview , all analyses are structured in a similar way. In theupper screen area you are presented with an overview of the most important key figurevalues for the characteristic value combinations of the chosen version. The characteristicvalue 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 isdisplayed in the middle screen area. This key figure data is arranged in tab pages in theanalytic views (such as demand and supply). In the lower screen area, key figure data isdisplayed in charts.

You can configure the analyses according to your own requirements. This means you candefine:

• 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. Alsocreate aggregation relationships for the aggregation level hierarchy and define time bucketprofiles. Assign the key figure groups, aggregation relationships and time bucket profiles tothe analyses, analytic views and analytic charts as follows:

• Analytics: You assign an aggregation relationship, a key figure group, a time bucketprofile and analytic views to each analysis

• Analytic views: You assign a key figure group, a time bucket profile, the sequencefor 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 cannavigate from this analytic view. If you do not assign a time bucket profile to theanalytic view, the system uses the time bucket profile that you have assigned to theanalytic ID.

• Analytic Chart Group: For each analytic view, you can assign a chart group, whichwill be displayed as a tab page in the chart area of the screen. You can groupmultiple analytic charts in one chart group and display them on one tab page. Youcan use the sequence number to define in which order the tab pages are displayed inthe 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 canuse the sequence number to define in which order the charts are displayed on thechart group tab pages.

If you do not assign a time bucket profile to the analytic chart, the system uses thetime bucket profile that you have assigned to the analytic view. If you also do notassign a time bucket profile to the analytic view, the system uses the time bucketprofile that you have assigned to the analytic ID.

For the Version Overview , you can only define which key figures are displayed and whichtime 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 ofthe analysis from which the system is to determine the key figure group and time bucketprofile. 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).




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




xSOP Planner

Role: /SCMSOP/PLANNER

You can use this role to perform all the activities you require as a planner in the area of salesand operations planning.

Activities in Sales and Operations Planning

You can display and edit data in the following screens in SAP xAPP Sales and OperationsPlanning (xSOP):

Screen Mode

Process Management

All Planning Tasks Edit

My Tasks Edit

Analytics

Version Maintenance Edit

Version Overview Edit

Version Detail Edit

Demand Analytics Edit

Supply Analytics Edit

Inventory Analytics Edit

Financial Analytics Edit

Capacity Analytics Edit

Overview Analytics Edit




xSOP Manager

Role: /SCMSOP/MANAGER

You can use this role to perform all the activities you require as a manager in the area ofsales and operations planning.



Screen Mode

Process Management

Overview Edit

My Process Steps Edit

All Tasks Edit

My Tasks Edit

All Action Items Edit

My Action Items Edit

Analytics



Version Detail Edit

Demand Analytics Edit

Supply Analytics Edit

Inventory Analytics Edit

Financial Analytics Edit

Capacity Analytics Edit

Overview Analytics Edit




xSOP Administrator

Role: /SCMSOP/ADMINISTRATOR

You can use this role to perform all the activities you require as an administrator in the area ofsales and operations planning.



Screen Mode

Master Data

Upload Master Data Edit

Maintain Master Data Edit

Upload CVCs Edit

Maintain CVCs Edit

Maintain CVC Mapping Edit

Upload CVC Mapping Edit

Upload Product - Product Subfamily Mapping Edit

Maintain Product - Product Subfamily Mapping Edit

Upload Master Data in the Background Edit

Delete Master Data in the Background Edit

Upload CVCs in the Background Edit

Upload Product - Product Subfamily Mapping inthe Background

Edit

Transactional Data

Upload Transactional Data Edit

Download Transactional Data Edit

Perform Delta Download of BI Transact. Datafrom TSDM

Edit

Upload Transactional Data in the Background Edit

Perform Delta Download of BI Transact. Datafrom TSDM in the Background

Edit

Process Management

Overview Edit




All Process Steps Edit

My Process Steps Edit

All Tasks Edit

My Tasks Edit

All Action Items Edit

My Action Items Edit

Analytics

Analytics Configuration Edit



Version Detail Edit




Process Management

In SAP xApp Sales and Operations Planning (SAP xSOP), you can track your SOP processby defining process steps, tasks and action items. You can assign persons responsible aswell as monitor due dates and the completion status. In this way, you ensure that your SOPprocess 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 tasksand action items to them. Action items are assigned directly to process steps in the way thattasks are. In other words, the action items are not assigned via tasks. The objects differ asfollows:

• Process step:

A series of tasks that must be completed in the run-up to an SOP meeting, or actionitems that are agreed during the meeting.

For a process step, among other things, you can define the following:

o Region and business unit (required)

o Responsible person

o Due date (required)

o Tasks and action items

You always define a process step for a particular region and business unit. You canalso assign documents to the process step. For more information see DocumentManagement.

• Task:

An activity that must be completed by the responsible person in the run-up to an SOPmeeting. As opposed to the action items, a task is a future activity that you plan inadvance, alongside the process steps.

For a task, among other things, you can define the following:



o Completion status

o Long text (freely definable)

o Analytic application

o External user

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

tasks.




The External User is a responsible person who does not have a user in the SAPxSOP 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 activitydiffers 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 Completion status

o Long text

o External user

The due date of an action item must fall after the due date of the process step, sinceit is a measure created in response to the process step. If the due date is to fallbefore 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 tasksthat are also to be copied. Tasks can only be copied individually. Since action items tend tobe 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 aparticular month. Here, you can create and maintain new process steps with tasksand action items.

Above all, you can use this transaction to define the basic structure of the process atthe start of an SOP process. For more information, see Creating the Basic Structuresof 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, andfor 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 thatare assigned to you. If you click on a process step, the system displays all theassociated tasks and action items, regardless of whether you are responsible forthem or not.

In the transactions My Tasks and My Action Items , the associated documents arealso displayed in the the overview (documents are always assigned to the processstep).




You can see a complete overview of all tasks, action items, and documents for a particularprocess 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 onlyedit the completion status. Only the administrator can define responsible persons; themanager does not see this field. In the process management overview, a manageronly sees the process steps that he is responsible for. For more information, seeRoles in SAP xApp Sales and Operations Planning (SAP xSOP).




Document Management

In SAP xApp Sales and Operations Planning (SAP xSOP), you can assign documents to theprocess steps that you created. SAP xSOP supports all popular file formats, such asMicrosoft 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 SAPPLM Collaboration Folders (cFolders). For more information, see the Configuration Guide forSAP xSOP under Integration with cFolders .

You store the documents in cFolder and assign them in SAP xSOP. SAP xSOP establishes alink to the documents stored in cFolders. You can call up cFolders directly from the screenswhere you assign documents in SAP xSOP. For more information, see the documentation foryour cFolders system.

PrerequisitesIn 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 adocument that you have already stored in cFolders, to the process step. On the screen forcreating or maintaining a process step, choose Documents . If you have not yet stored anydocuments in cFolders, you can call up the cFolders system by choosing Document Management . If documents already exist, choose Assign . In the assignment view, you canalso store notes and assign them to the process step.




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 differentbusiness 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 oneprocess cycle. You can use and reuse these structures as a basis for the individualprocess 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 aprocess 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 givensuggestions for an overall plan that will be decided on during the management reviewmeeting.

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 meetingdecide on the overall plan, which will form the basis for the work carried out in thedifferent departments of your company.

For more information, see Management Review of the Overall Situation.




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 processstructure that is valid in the long-term and beyond a process cycle, and that is only subject tominor changes.

Process

To create the basic structures, choose Process Management Overview (SAPNetWeaver Business Client), or Process Management Process Management Overview

(SAP GUI). On this screen, you are presented with an overview of all process steps, tasksand action items. You can also create and edit these objects here. For more information seeProcess Management.

Then proceed as follows:

1. Create process steps

Decide the general steps for your SOP process and create the process steps in SAPxSOP Process Management. Process steps can be, for example, the modeling ofstrategic plans and the analysis and adjustment of the plans. You always define theprocess steps for a particular region and business unit.

You can later copy these process steps for the individual process cycles (monthly, forexample) 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 recurrenttasks. 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 arevalid long-term and do not relate to a specific process run - such as descriptions ofthe overall process, guidelines, and annual targets.




Modeling Strategic Plans

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

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 SAPxSOP system, and that it is up-to-date. If you want to introduce a new product, forexample, the master data of this product should exist in SAP xSOP.

For more information, see Loading Master Data and Loading Characteristic ValueCombinations.

2. Check the versions

In Version Maintenance , check that all the required version are available in the SAPxSOP system. You can create new versions in the system or copy existing versionsfrom previous process cycles.

Recommendation

We recommend that you create as few versions as possible. It is sensible, forexample, to create versions for different business scenarios, which each contain allthe 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 intime 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 thereconciled overall plan of the previous process cycle, for example, and compare theversions with the new business scenarios.

3. Loading Transactional Data

Ensure that the required transactional data from an SAP system or an external file isloaded 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.




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 (SAPxSOP) to analyze, adjust and reconcile your plans.

Prerequisites

You have configured the analytic applications according to your individual requirements. Formore information about the various analyses and their configuration, see Configuring theAnalyses.

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 demandanalysis for the demand plan, or the supply analysis for your supply plan).

In the upper screen area, you can expand the aggregation structure of theaggregated characteristics (such as product family) to view the lower levels of thehierarchy (such as product subfamily, locations and resources). In the middle screenarea, the detailed key figure data for the characteristic value combinations thenappears. 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 figuresin 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, chooseChange . The changeable key figures are then ready to be edited. Note that only dataon and below the product family level can be changed. This means you cannotchange data on the top level of the aggregation hierarchy, in other words the regionand business unit level.

The system breaks down the key figure values to the lower aggregation levels. Thedependent key figures are updated.

3. Reconcile the plans

You can display the various plans that you have saved in a version as part of abusiness 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 demandand 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 andcompare 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 abusiness scenario), you can compare the plans from the different versions (andtherefore different scenarios) with each other. You can make this comparison in theVersion Overview , where the most important data for the different versions isdisplayed.

After you have compared the versions, you can choose the versions and the possibleoverall plans that you want to present and discuss in the management review.




Management Review of the Overall Situation

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

Prerequisites

You have created a process step for the management review meeting and assigned therequired documents, such as Microsoft PowerPoint presentations. For more information, seeCreating 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 arepresented with an overview of the aggregated data for the different versions and thusthe overall plans available for you to choose. You also have access to the associateddocuments 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 themost important key figure values. During the meeting, you can still change certain keyfigure 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 cannotreach a decision, or if further activities are needed, you can also create action itemsdirectly 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 besent back to certain source systems. You can download data into an SAP SCMsystem or carry out a delta download of SAP BI transactional data from the TimeSeries Data Management (TSDM) into an SAP NetWeaver BI system. For moreinformation, see Loading Transactional Data.

As an alternative, or in addition to this, you can communicate the results of themeeting to the planners and other relevant people. These communications are alsosupported by the SAP xSOP process management (by using action items and tasks,for example).