AC625 Executive Information System (EIS) 3 Business Planning
AC625 Executive Information System (EIS) 3 - Business Planning SAP AG 1999 SAP AG
R/3 System
Release 4.6B
June 2000
Material number 5003 7838
Copyright
Copyright 2000 SAP AG. All rights reserved. Neither this training manual nor any part thereof may be copied or reproduced in any form or by any means, or translated into another language, without the prior consent of SAP AG. The information contained in this document is subject to change and supplement without prior notice. All rights reserved.
SAP AG 1999
Trademarks:
Microsoft ®, Windows ®, NT ®, PowerPoint ®, WinWord ®, Excel ®, Project ®, SQL-Server ®, Multimedia Viewer ®, Video for Windows ®, Internet Explorer ®, NetShow ®, and HTML Help ® are registered trademarks of Microsoft Corporation.
Lotus ScreenCam ® is a registered trademark of Lotus Development Corporation.
Vivo ® and VivoActive ® are registered trademarks of RealNetworks, Inc.
ARIS Toolset ® is a registered Trademark of IDS Prof. Scheer GmbH, Saarbrücken
Adobe ® and Acrobat ® are registered trademarks of Adobe Systems Inc.
TouchSend Index ® is a registered trademark of TouchSend Corporation.
Visio ® is a registered trademark of Visio Corporation.
IBM ®, OS/2 ®, DB2/6000 ® and AIX ® are a registered trademark of IBM Corporation.
Indeo ® is a registered trademark of Intel Corporation.
Netscape Navigator ®, and Netscape Communicator ® are registered trademarks of Netscape Communications, Inc.
OSF/Motif ® is a registered trademark of Open Software Foundation.
ORACLE ® is a registered trademark of ORACLE Corporation, California, USA. INFORMIX ®-OnLine for SAP is a registered trademark of Informix Software Incorporated.
UNIX ® and X/Open ® are registered trademarks of SCO Santa Cruz Operation.
ADABAS ® is a registered trademark of Software AG
The following are trademarks or registered trademarks of SAP AG; ABAP/4, InterSAP, RIVA, R/2, R/3, R/3 Retail, SAP (Word), SAPaccess, SAPfile, SAPfind, SAPmail, SAPoffice, SAPscript, SAPtime, SAPtronic, SAP-EDI, SAP EarlyWatch, SAP ArchiveLink, SAP Business Workflow, and ALE/WEB. The SAP logo and all other SAP products, services, logos, or brand names included herein are also trademarks or registered trademarks of SAP AG.
Other products, services, logos, or brand names included herein are trademarks or registered trademarks of their respective owners.
Controlling Level 3
Level 2
AC412 2 days Cost Center Accounting: Extended Functionality AC410 Cost Center Accounting
3 days
AC415
AC420 AC040
2 days
Activity Based Costing
5 days
AC510 3 days Cost Object Controlling for Products
Cost Management and Controlling AC505
3 days
Product Cost Planning AC605
5 days
Profitability Analysis AC610 Profit Center Accounting
SAP AG 1999
2 days
Overhead Orders
2 days
AC615 2 days Executive Information System (EIS) 1 Reporting
AC515 3 days Cost Object Controlling for Sales Orders AC530 2 days Actual Costing / Material Ledger AC650
2 days
Transfer Prices AC620 2 days Executive Information System (EIS) - Setting up the System
AC625 1 day Executive Information System (EIS) 3 Business Planning
Course Prerequisites
AC615 - EIS Reporting (recommended)
AC620 - EIS Setting up the System
SAP AG 1999
Target Audience
SAP AG 1999
Participants
Members of the project team responsible for planning and analyzing corporate strategy
Members of the project team responsible for the installation and support of planning tools
SAP consultants and partners
Duration: 1 day
Introduction
Contents:
Course goal
Course objectives
Course content
Course overview diagram Main business scenario
SAP AG 1999
© SAP AG
AC625
1-1
Course Goal
This course will enable you to:
Plan in EC-BP
Understand the generation, processing and
distribution of plan data Explain and use various planning functions and data
SAP AG 1999
© SAP AG
AC625
1-2
Course Objectives
At the conclusion of this course, you will be able to:
Execute plan data modeling
Enter and transfer plan data
Execute interactive planning
Execute automatic planning
Create reporting for plan data
SAP AG 1999
© SAP AG
AC625
1-3
Course Content
Preface Unit 1
Introduction
Unit 5
Plan Data Processing
Unit 2
EC-BP Functions
Unit 6
Forecast
Unit 3
Modeling the Planing Structure Plan Data Entry
Unit 7
Simulation Calculations
Unit 8
Reporting
Unit 4
SAP AG 1999
© SAP AG
AC625
1-4
Course Overview Diagram
Unit 1: Introduction Unit 2: EC-BP Functions Unit 3: Modeling the Planning Structure Unit 4: Plan Data Entry Unit 5: Plan Data Processing Unit 6: Forecast Unit 7: Simulation Calculations Unit 8: Reporting
SAP AG 1999
© SAP AG
AC625
1-5
EC-BP Functions
SAP Enterprise Controlling (EC)
Strategic planning at aggregated level for divisionalized groups
Planning with EC-BP
Main business scenario
SAP AG 1999
© SAP AG
AC625
2-1
EC-BP Functions: Unit Objectives
At the conclusion of this unit, you will be able to:
Understand the position of the BP component within the EC module
Explain the significance of EC-BP for enterprise planning
SAP AG 1999
© SAP AG
AC625
2-2
EC-BP Functions: Course Overview Diagram
Unit 1: Introduction
Unit 2: EC-BP Functions Unit 3: Modeling the Planning Structure Unit 4: Plan Data Entry Unit 5: Plan Data Processing Unit 6: Forecast Unit 7: Simulation Calculations Unit 8: Reporting
SAP AG 1999
© SAP AG
AC625
2-3
SAP Enterprise Controlling (EC)
EC-BP
Business Planning
EC-EIS
Executive Information System
EC-CS
Consolidation
EC-PCA
Profit Center Accounting
SAP AG 1999
EC-BP Business
Planning provides efficient support when you are creating enterprise plans at a high level of aggregation. A key feature is the flexible representation of customer-specific plan sections and their interrelationships. This includes especially the linking between the P&L, balance sheet and cash flow plan, and also the efficient support of simulations with user-defined planning models.
In EC-EIS you can define enterprise-specific data structures. EC-EIS is the executive information system of the R/3 System and combines information from various sub-areas of R/3 and external data.
The subcomponent EC-CS covers general consolidation functions. It can be used for both external accounting and internal reporting. Besides the legally required consolidated financial statements, you can also consolidate at company level, business area level and profit center level. Its advantages lie in its rule-based reconciliation between the values from the external and internal consolidations.
EC-PCA allows
a subdivision of the enterprise independent of all other organization terms. Profit centers are the master data of a management view. To avoid additional data entry, you can make appropriate assignments in the transaction systems, for example materials, projects, cost centers.
© SAP AG
AC625
2-4
Divisionalized Enterprise Structure
SAP AG 1999
In organizations with decentralized structures, the local units in the group can plan their business using a locally installed EC-BP.
However, to simultaneously monitor the development of group-wide critical success factors, the data and data structures are transferred automatically from the decentralized systems to the central EC-BP. Appropriate interfaces and data collection routines are used for this.
In divisionally structured enterprises the access rights are especially significant. EC-BP provides a well-developed authorization concept.
© SAP AG
AC625
2-5
Strategic Planning at Aggregated Level for Divisionalized Groups
Group Management Top Down
Bottom Up
Business units, companies, divisions, plants SAP AG 1999
In many enterprises producing plans at an aggregated level is a protracted process due to slow data flow and communication. In EC-BP the easy data transfer, the creation of several different plans and the communication features accelerate this process significantly.
© SAP AG
AC625
2-6
Planning with EC-BP
Complete enterprise plan
EC-BP
Operative plan sections Quantity plan
Finan. budget
Personnel plan
NonSAP systems
R/2
External data
Plan data sources
SAP AG 1999
From Release 4.0a you can plan with EC-EIS, from Release 0.11acres with EC-BP. You can use interactive planning functions in dialog and also automatic functions in background processing. You can use these functions to process plan data for any characteristics and key figures in an aspect. EC-BP enables processing of plans at aggregated level.
The generic functions of EC-BP let you select any planning objects. This way you can combine cross-application business relationships in one or more plan sections, for example routings, aggregated human resources plans, financial plans etc..
You can process these plans further in EC-BP with planning functions like seasonal distribution and revaluation.
EC-BP supports the transfer of plan data from the R/3 transaction systems and also from non-SAP systems.
© SAP AG
AC625
2-7
EC-BP: Functions
Flexible definition of planning structures
Multidimensional planning
Comprehensive planning functions (seasonal distribution, forecasting, ...)
Supports various planning strategies (bottom-up, top-down, mixed top-down/bottom-up)
Excel interface
SAP AG 1999
© SAP AG
AC625
2-8
Main Business Scenario
International manufacturer of pharmaceuticals
Has implemented all R/3 modules
Requires EC-BP for strategic planning at aggregated level
Wishes to use EC-BP to forecast the business development based on actual data
Uses EC-BP to carry out simulations, what-if-analyses and target value searches in order to evaluate different courses of action
SAP AG 1999
A major international pharmaceuticals group recently decided to implement all SAP R/3 modules.
Interviews with management have shown that a strategic planning system at an aggregated level is required. It must be usable by top management, product managers and the plant managers.
A user-friendly tool is desired with which important P&L and balance sheet factors and other business key figures can be planned and calculated.
Ideally the data will be available in real time and in a multidimensional structure. This will allow various views of the existing data quickly and easily.
Furthermore, there should be a close connection to other SAP modules, the dataset should be configured efficiently, maintenance should be reduced to a minimum, and access authorizations should work effectively.
© SAP AG
AC625
2-9
Enterprise Structure
Enterprise
A P h ar m& C a he m.
Segment
4 0 0 0C h e m .
Bus. Unit
Division
4 1 P ac k . M a t er .
Prod. Line
B S e rv i ces
6 0 0 0P h a rm a
43 Med. Subst.
61 1 Mo n o
6 1 A n al g e t i c s
61 2 Co mb o
8 0 0 0S er vi ce s
6 2 D i ab e t i c s
62 1 Hu m. B as . I n s.
8 1 P h a r m aM ar k . R es .
62 2 An im . B as. In s .
SAP AG 1999
© SAP AG
AC625
2-10
EC-BP Functions: Summary
BP is the fourth component of the EC module, alongside EIS, CS and PCA
EC-BP enables Excel-supported, multidimensional planning using various strategies and functions
SAP AG 1999
© SAP AG
AC625
2-11
Modeling the Planning Structure
Aspect
Multidimensional data structure
Master data hierarchy
Characteristic attributes
Key figure model
Calculation of basic key figures
Currency model
Different versions
Excel In-Place
Data slices
Rolling planning
SAP AG 1999
© SAP AG
AC625
3-1
Planning Structure: Unit Objectives
At the conclusion of this unit, you will be able to:
Explain the EC-BP data structure and data supply
Understand the key figures and currency models, and also the different versions
Discuss the use of characteristic attributes and master data hierarchies in the planning process
SAP AG 1999
© SAP AG
AC625
3-2
Modeling the Planning Structure: Course Overview Diagram
Unit 1: Introduction Unit 2: EC-BP Functions Unit 3: Modeling the Planning Structure Unit 4: Plan Data Entry Unit 5: Plan Data Processing Unit 6: Forecast Unit 7: Simulation Calculations Unit 8: Reporting SAP AG 1999
© SAP AG
AC625
3-3
The Aspect
Aspect table CF880
Fixed characteristics
Characteristics
Year Period Plan/Act Version Bus. Unit
1999 01 1999 02 2000 01
. . .
Basic key figures Revenue Wage costs costs Revenue
0 0 1
A01 Pharma. Analgetics 4330 B01 Chem. Med. subst. 1500 A02 Serv. Research 1000
1
A03 Pharma. Diabetics
. . .
2001 04
Division
Database table
150 60 30 . . . . . .
. . .
1000
30
Ex.: Structure of an aspect Ex.: Contents of an aspect (transaction data)
. . . . . .
. . .
SAP AG 1999
The aspect is a self-contained part of the summarized information of an enterprise.
All the data stored in any one aspect should be relevant to the same business activity because it will later be used as the basis for the reports.
The structure of an aspect consists of characteristics (categories such as country, division, etc.) and basic key figures ( sales, number of employees, etc.). In addition to the key figures that are stored in the database, you can also calculate (derive) key figures that are not saved, for example, contribution margin per unit .
© SAP AG
AC625
3-4
Multidimensional Data Structure
Report
p u o r g r e m o t s u C
. d n i s s e c o r P e l a s le o h W li ta e R
New York Chicago Palo Alto
Company
Chem. Pharma Services
Business Unit SAP AG 1999
Characteristics determine how the dataset is classified. Country, division, and customer group are just some examples of characteristics. Note that time categories (fiscal year, period, etc.) are also seen here as characteristics. The master data includes the permitted values of a characteristic (characteristic values). Combinations of characteristics or characteristic values are often referred to in the documentation as objects.
If there are three characteristics, the relationship between them can be illustrated using the above graphic. The result is a cube, the sides of which represent the various characteristics (company, business unit and customer group in this example). Each characteristic is sub-divided into several characteristic values. The slices represent combinations of characteristic values. One possible evaluation object might be the business unit Pharmaceuticals and company Palo Alto.
There are many key figures in your application that might be relevant to the evaluation process. Key figures are not just values and quantities; they can also be calculations of values, etc., based on formulas that you have defined.
© SAP AG
AC625
3-5
Data Supply
Aspect
Aspect structure
Transfer rules
Period
Bus. Unit
Division
...
Revenue CM1
...
<
I-III
Sender structures
Data sources
R/2
NonSAP
Transaction systems
PC data
External data
SAP AG 1999
The data structures that are transferred into EC-BP may differ from the aspect structure.
You use transfer rules to define how the aspect fields are to be filled from the sender fields.
EC-BP provides several tools for filling the aspects with data, including ABAP queries or application-specific collection programs for transferring data from external systems. You can also import data as a file or use your own collection programs.
Application-specific collection programs are included in the standard package for the following applications (among others): R/2 - RF, RK-E, RK-S, RK-P R/3 - FI-LC, FI-GL, CO-PA, CO-CCA.
© SAP AG
AC625
3-6
Relationship: Aspect - Field Catalog - Master Data
Aspects
Field catalog
Financials
Field attributes
Master data Subgroup Pharma. & chemicals
Company
HR
Subgroup Plan costs
Company Pharma Market Research Corp.
Revenue
Stock prices
Business Unit
Diabetics Package Mat.
SAP AG 1999
When an aspect is generated, the newly defined fields are updated to a field catalog, which therefore always contains all the fields from all the aspect data structures. If a field is stored in the field catalog, it can be used in further aspects but no longer changed. In other words, it has the same meaning throughout EC-BP. The field catalog is therefore aspect-independent.
The field catalog identifies a field as an independent object in EC-BP with a unique use in all aspects. It contains attributes for the fields which determine how the fields are used in reporting. These attributes are given default values when the aspect is generated and can be maintained by the user in maintenance views. The field catalog aids integration since it is aspect-independent.
The characteristics of an aspect data structure refer to master data tables, which contain the permitted values, texts and possible characteristic attributes for the characteristic. The values can be entered manually or via data transfer if they have not already been transferred from feeder systems.
© SAP AG
AC625
3-7
Master Data Hierarchy
Characteristic Division
External hierarchy Master data 41 Pack. Mat. 43 Med. Subst. 61 Analgetics 62 Diabetics 81 Market Res. 91 Services
Group Pharma Analgetics Diabetics Med. Subst. Services Market Res. Others Pack. Mat.
Non-chargeable nodes X Y Z
Group Pharma. Others
Non-chargeable nodes Chargeable nodes SAP AG 1999
You can define hierarchical relationships between the characteristic values for characteristics used in EC-BP. You can also define several different variants of a hierarchy which you can display in reports. Hierarchies are valid for one characteristic. This means that, in any one hierarchy, you can only order the characteristic values of one characteristic. However, you can also map alternative hierarchies onto a characteristic (different hierarchy variants).
Each characteristic value contained in the hierarchy represents a hierarchy node. Nodes which have further dependent nodes are called structure nodes. If a node has no dependent nodes, it is called an end node.
A node whose characteristic value appears in the master data is called a chargeable node.
A node whose characteristic value does not appear in the master data is called a non-chargeable node.
It is not possible to maintain external hierarchies for characteristics without master data tables.
!!! Note that each characteristic value contained in the master data hierarchy must either be a chargeable or non-chargeable node. Deleting a piece of master data automatically deletes the corresponding chargeable hierarchy node. If this hierarchy node is a structure node, all its dependent nodes are deleted too.
© SAP AG
AC625
3-8
Characteristic Attributes
single-level single-level
multi-level multi-level Chem. Pharma. & Chem.
Pharma. & Chem.
Group
Retail
Pharma.
Services
Characteristic
Diabetics
Attribute Attribute for ... SAP AG 1999
Attributes can be assigned to characteristics. There are two types of characteristic attributes: Navigation attributes and attributes for currency/unit fields.
Navigation attributes are used just as the characteristics of an aspect. As with other characteristics, you can use them to drill down in a report.
The advantage of characteristic attributes is that the information is stored in the master data instead of in the transaction data. If, for example, you wish to simulate a reorganization of the enterprise at a later date, the change in the master data affects the report immediately without the database having to be converted.
You get to the attributes via characteristic maintenance with "Goto --> Attributes". If attributes already exist for a characteristic, these are displayed.
To create a characteristic attribute, you first have to generate the characteristic that will later be used as the characteristic attribute (for example division). Then you switch to maintenance of a characteristic (for example product line) and assign the characteristic attribute (division) to it.
From Release 4.5A multi-level attributes are possible.
© SAP AG
AC625
3-9
Key Figures
Key figure
REV_EMP
Description
Revenue per employee
Key figure formula Keyfigure REV_EMP
Formula =
REVENUE/EMPLOYEE
SAP AG 1999
Key figures:
- Are formed from the basic key figures of the aspect, already defined key figures, and constants, - Are uniquely defined for all aspects, - Can be combined into groups, - Are treated as basic key figures in reporting.
Unlike basic key figures, the value of a calculated key figure is not saved in the database. A key figure is calculated by the system when a report containing this key figure is executed.
Every calculated key figure has a unique name, valid for all aspects. However, each calculated key figure is assigned to a specific aspect since it can be broken down into the key figures of an aspect. If the detailed key figures are also available in another aspect, the calculated key figure can also be made visible in this aspect.
You can create derived key figures for a view aspect and use the basic key figures from the relevant aspects in the formula.
The aggregation and display of key figures in reporting can be chosen just as with basic key figures.
© SAP AG
AC625
3-10
Key Figure Model
Profit
Net sales
Gross sales
Variable sales costs
Sales deductions
Contribution margin
Profit as % of sales Fixed
Revenue
costs Return on Investment
Cash
Revenue Turnover of capital
Current assets
Receivables
Fixed assets
Inventories
Invested capital
SAP AG 1999
You can build up whole key figure trees by reusing existing key figures in other key figure formulas
You can form key figure groups and assign key figures to a key figure group. This key figure group can then be used when defining a report in order to simplify key figure selection. The grouping of key figures into areas such as 'liquidity' and 'cost effectiveness', and so on, allows a better overview of key figure maintenance and reporting.
© SAP AG
AC625
3-11
Calculation of Basic Key Figures
Basic key figures Fixed assets assets Current assets Invested capital
Interactive planning Automatic planning: • Copy • Change • Forecast • Top-down
or
Basic key figures
Calculated basic key figure
Fixed assets Invested capital Current assets
SAP AG 1999
From Release 4.5A, the calculation of basic key figures is possible.
You can determine interactively whether to use the basic key figure or calculate it using other basic key figures.
You can also create key figure trees for calculated basic key figures.
© SAP AG
AC625
3-12
Currency Model
Data storage
Planning Currency
Group currency
Country currency
Foreign currency . . .
. . .
SAP AG 1999
Planning can be carried out in different currencies, for example, group currency or country currency. Each key figure in the data retention has only one currency. This may be converted for planning.
© SAP AG
AC625
3-13
Different Versions
Plan Version
Actual
1
optimistic
2
pessimistic
3
seasonal
4
trend
.
.
.
.
.
.
SAP AG 1999
Using the three-character, alphanumeric key, you can maintain as many planning versions as you wish for example, optimistic, pessimistic etc..
© SAP AG
AC625
3-14
Excel In-Place
SAP AG 1999
The Excel that is implemented in the R/3 environment has all the regular Excel functions.
Using Excel In-Place, you can retain local or private plan versions.
Data transfer is possible both from R/3 into Excel In-Place and vice versa.
© SAP AG
AC625
3-15
Data Slices
Name
" 1 e c li S "
Table
User
Restrict data area
BU 6000 Div 611..621
cf880
SAP AG 1999
Data slices are part of the authorization concept. Tables and users are assigned to a data slice. The data area of the tables can also be restricted.
Before allowing any access to a data area, the system checks the relevant authorization.
© SAP AG
AC625
3-16
Rolling Planning
Plan
Planning time period N
D J
F M A M J
J
A S
O N
D J
F M A M
2000
J J
A S
O N
D J
F
A S
O N
D J
F
2001
or also N
D J
F M A M J
J
A S
O N
D J
2000
F M A M
J J
2001
SAP AG 1999
EC-BP allows rolling planning. A short period in the past can be planned onto longer periods in the future. You can also plan over to the next fiscal year.
© SAP AG
AC625
3-17
Modeling the Planning Structure: Summary (1)
The aspect is the central concept in EC-BP. It subdivides the EC-BP data into independent business evaluation areas
The EC-BP data has a multidimensional structure and can be transferred from R/3, R/2 and from other systems
Master data can be created in a hierarchy
Key figure trees can be produced with basic key figures and calculated key figures
SAP AG 1999
© SAP AG
AC625
3-18
Modeling the Planning Structure: Summary (2)
You can carry out planning in various currencies
You can store several planning versions
Excel In-Place enables private plan versions with simple data exchange from, and to EC-BP, and offers the regular functions
You can use EC-BP for rolling planning
SAP AG 1999
© SAP AG
AC625
3-19
Plan Data Entry
Interactive planning Planning layout
Parallel currencies in planning
Authorization concept
Planner profile
Ratio planning Automatic planning
Plan data supply
Updating plan data : directly or automatically with rules
Currency conversion with data transfer
SAP AG 1999
© SAP AG
AC625
4-1
Plan Data Entry: Unit Objectives
At the conclusion of this unit, you will be able to:
Understand planning layouts and planner profiles
Explain the data structure and authorization structure in EC-BP
Generate plan data interactively and automatically
Recognize the transfer options for plan data
Explain currency conversion with data transfer
SAP AG 1999
© SAP AG
AC625
4-2
Plan Data Entry: Course Overview Diagram
Unit 1: Introduction Unit 2: EC-BP Functions Unit 3: Modeling the Planning Structure
Unit 4: Plan Data Entry Unit 5: Plan Data Processing Unit 6: Forecast Unit 7: Simulation Calculations Unit 8: Reporting SAP AG 1999
© SAP AG
AC625
4-3
Main Business Scenario
Plan data for the Business Unit Pharmaceuticals is to be generated from the previous year's actual data. A planning layout will be used for this.
The divisions are responsible for planning. Authorizations are to be granted accordingly.
Data generated in various decentralized R/3 components is to be transferred to EC-BP for central group planning. The currencies are to be converted from the relevant country currencies to the group currency.
SAP AG 1999
© SAP AG
AC625
4-4
Defining a Planning Layout
Planning Layout
Header - general data selection Lead column
Key figure columns
Unit
SAP AG 1999
Note: transaction data (in this case, plan data) can also be maintained without a layout.
By defining a customized planning layout you can adapt the screen output to the specific requirements of your company. The exact information which the planner needs for the current planning session is available. Layouts, which have been defined for the entry of actual data, can also be used for planning.
The planning layout determines the structure of the screen where you enter the plan data. This covers the positioning of the fields and their description. The user determines which characteristics and key figures are to be planned for which timeframe, by assigning the characteristics and key figures to the rows and columns of the layout or the general data selection (header).
Characteristics, which are the same for all planning objects, are defined in the general selections (header block).
The "version" and "plan/actual indicator" fields are treated as normal characteristics when you define the layout. Thus you can display a second plan version or actual data, or plan more than one version.
You can enter fixed values or variables for the characteristics in the planning layout. If you enter variables, you will get a system message when planning requesting you to replace the variables.
© SAP AG
AC625
4-5
Planning Layout (with several lead columns)
Plan/Act Indic. Fiscal year Period Company code Div 01M otorcycles 02 Paints 03L ightbulbs 04 Food 05E levators 06 Hightech 07S ervice 08A ccessories 09 Vehicles 10A utospares 11A ccessories Total
1 Plan data 2000 F/year 2000 1 to 1 2 1000 IDES AG
Region Revenue 000001 000002 000003 000004 000005 000001 000002 000003 000004 000005 000001
Unit Salesvolume 2,000.00 DEM
Unit 20 pc
200,000.00 DEM 200,000.00D EM 40,000.00 DEM 450,000.00D EM 1,000.00 DEM 100,000.00 DEM 60,000.00D EM 70,100.00 DEM 640,000.00D EM 200,000.00D EM
30 pc 200 pc 70 pc 60 pc 10 pc 100 pc 10 pc 20 pc 300 pc 200p c
1,963,100.00 DEM
1020 pc
SAP AG 1999
You create entry layouts in Customizing using the Report Painter.
You create a layout with lead columns by double-clicking on the lead column field in the initial screen of the Report Painter and establishing a characteristic for this column. In this case, there are no fixed rows - they are established by the characteristic values that the user enters. The key figures appear here automatically in the columns.
Up to nine lead columns can be created. Data records can also be deleted in a layout with lead columns. The data is deleted only internally at first. Then during posting, it is deleted from the database.
Variables can be used for all characteristic values (in rows, columns and general selections). This applies for both types of layout.
If you have selected an interval in the header, you can scroll through all combinations of header characteristics, for which transaction data exists.
© SAP AG
AC625
4-6
Planning Layout (with key figures)
P l a n / A c tI n d i c . F isc al y ear P e r io d Company c od e
1 2 000 1 to 100 0
Revenue Motorcycles Paints Lightbulbs Food Elevators Hightech Service Accessories Vehicles Auto spares Accessories Automobiles Total
Calculated key figure
P la nd a t a F / ye ar 20 00
Formula
12 I D E S AG
Unit Profit margin (= Prof./Rev.) 2,000.00D EM 0.10 200,000.00 DEM 0.025 200,000.00D EM 40,000.00 DEM 450,000.00D EM 1,000.00 DEM 100,000.00 DEM 60,000.00 DEM 70,000.00 DEM 600,000.00 DEM 200,000.00 DEM 300,000.00 DEM
2,230,000.00 DEM
0.05 0.01 0.11 0.20 0.10 0.33 0.05 0.25 0.125 0.20
Prof. Margin * Cap. turnover rt.(=RoI)
0.09 0.11 0.06 0.02 0.15 0.17 0.11 0.38 0.09 0.22 0.12 0.22
365,800.00
SAP AG 1999
Calculated key figures may also be included in the planning layout.
Within the planning layout you can use formulas to calculate further values from key figures or other formulas. If you use inverse formulas and change the 'ready-to-input' status of certain fields you can carry out these calculations in the reverse direction.
© SAP AG
AC625
4-7
Parallel Currencies in Planning
Planning Layout Local1 Version 001 Year 2000
Layout Currency: -
B u s in e s s Un i t 60 00 80 00 .. ..
Q uanti ty R ev enue 1, 000 D E M1 0 , 0 0 0 2, 500 U S D2 6 , 0 0 0
D i sc ou n t D E M1 , 0 0 0 U S D2 , 0 0 0
SAP AG 1999
By using characteristic-related currencies, you can simultaneously plan various key figures in different currencies within one planning layout.
© SAP AG
AC625
4-8
Authorization Concept
Enterprise
Segment
A Ph ar m& C a h e m.
4 00 0Ch em .
Bus. Unit
Division
41 P ac k . Mat er .
Prod. Line
B S er vi ce s
6 00 0Ph ar ma
43 Med. Subst.
611 Mon o
6 1 A n al g e t i c s
612 C ombo
8 00 0S er vi ce s
6 2 Di ab eti cs
621 H u m. Bas. I ns.
8 1 P h a r m aM ar k . R e s .
622 A n im. B as. I ns.
= SAP AG 1999
Within the authorization concept the access rights may be restricted to certain branches of the enterprise structure.
© SAP AG
AC625
4-9
Decentralized Enterprise Planning - Authorizations
SAP AG 1999
In organizations with decentralized structures, the local units in the group can plan their business using a locally installed EC-BP.
However, to ensure an overview of the development of group-wide critical success factors, the data and data structures are transferred automatically from the decentralized systems into the central EC-BP.
© SAP AG
AC625
4-10
Planner Profiles
User group
Layout
Sales volume
Revenue
Sales deductions
Sales
Controlling
Personnel costs
Material overhead costs
Other expenses
SAP AG 1999
Planner profiles are important for interactive planning.
You can use planner profiles to assign specific rights to certain user groups. You can also assign the layouts to be processed and their sequence.
When creating planner profiles, you can determine if the selected layouts are to be displayed and processed as Excel sheets.
© SAP AG
AC625
4-11
Ratio Planning
Layout Q ua n ti ty 100 100 100
R ev enue
Price
1,000.00 900.00 800.00
Quantity, revenue
10.00 9.00 8.00
Layout Q uanti ty R ev enue 100 1,000.00 100 900.00 (blue: figures) 100basic key 800.00
Quantity, revenue
Price 10.00 9.00 8.00
Layout Q ua n ti ty 100 100 100
R ev enue 1,000.00 900.00 800.00
Price
Quantity, revenue
10.00 9.00 8.00
(blue: basic key figures) "A
B" = Entry of A leads to calculation of B
SAP AG 1999
The fixed assignment of 3 factors in ratio planning is new from Release 4.5A. Thus when quantity or price is entered, the revenue is determined. Also, if the revenue is changed, the price is affected.
The 2 basic key figures are always saved to the database.
© SAP AG
AC625
4-12
Automatic Planning
Actual/plan data Copy Change Forecast Top-down
Plan 1997 Version 1 Division A Actual 1997 Division A Division B
Plan data Plan 1998 Version 1 Division A
SAP AG 1999
Either plan or actual data may be used as a reference for automatic planning.
Automatic planning functions: serve to process large volumes of data in a planning run. Thus, at the beginning of a planning period, for example, you can copy the entire previous year's plan data or the actual data, and then process it further online. You can use these functions either directly or in the background. The following planning functions are available : - Copying, - Seasonal distribution, - Revaluation.
Additional planning functions such as currency conversion, aggregation and restructuring can be carried out using the standard EC-EIS transfer tools.
Selections and parameters for automatic planning runs can be saved using variants and then scheduled for background processing.
© SAP AG
AC625
4-13
Collection Reports
Planning EC-BP CO-PA CO-OM CO-PC HR IM PS
R/2
FI-GL EC-CS ABAP
FI-SL EC-PCA
Flex. Excel upload Import file RF RK-S ABAP
RK-E RK-P
BP - database SAP AG 1999
In divisionally structured enterprises, it is possible to transfer plan data from decentralized EC-BP Systems to the central EC-BP; plan data can also be transferred from other R/3 components.
To supply EC-BP with transaction data from other SAP modules, you can use the general connection to the ABAP query and also the application-specific collection programs.
Depending on the SAP component from which the data is to be collected, the collection programs are either delivered immediately and supply a given structure, or they are generated during Customizing. In the latter case, the sender structure is also dependent on the Customizing settings.
To achieve better integration with Excel, EC-BP offers the "flexible Excel upload". This is a userfriendly function for transferring data from an Excel sheet into EC-BP aspects. In contrast to using the function 'Import file', the Excel sheet does not require a standard structure.
© SAP AG
AC625
4-14
Plan Data Supply
Aspect Data in the same R/3 System
Aspect structure R/3System
Standard interfaces
Individual programs
Transfer rules
Sender structure
File
CPI-C / RFC
Source system non-SAP
Source system R/2 or R/3 SAP AG 1999
There are various methods for transferring data from SAP and non-SAP sources to EC-BP.
Data can be transferred from within the R/3 system (where EC-BP is running) to the aspects using standard interfaces or your own programs. Data from other R/3 or R/2 systems can be transferred via CPI-C. Data from non-SAP systems can be transferred via CPI-C / RFC or from a file to the R/3 system.
© SAP AG
AC625
4-15
Aspect Summarization
Aspect CF002
Aspect CF001
Aspect Summarization Sender structure
Sender structure eg. -currency conversion -summarization -reorganization...
Transfer rules
Transfer rules
Aspect CF003 SAP AG 1999
Aspect summarization is a form of data transfer within EC-BP Systems.
Aspect summarization can be used to transfer data from different aspects into a summarization aspect. The aspect summarization can also be applied within an aspect.
You can achieve the following using aspect summarization:
- Combine data from different aspects into a summarization aspect - Transfer data from one version to another - Execute currency translations - Transfer transaction data from an old aspect to a new one - Reassign transaction data for modified master data (characteristic values have changed, but the transaction data is still stored for the old characteristic values).
The program generated uses the interface to transfer transaction data. The sender structure and transfer rules must be maintained for this program.
During the transfer of transaction data, the generated aspect summarization program is treated as a normal sender program.
© SAP AG
AC625
4-16
Updating Plan Data : Directly or Automatically with Rules
Reference Reference data Customer Customer group Revenue Bike shop 2-wheeled 100 Bikeworld 2-wheeled 200 Same aspect
Customer Cust. group Bike shop 2-wheeled 100 Bikeworld 2-wheeled 200
Direct updating :
Transfer rules Grouping
Different aspect
Customer Cust. group -2-wheeled 300
Updating with rules: Conversion
Customer Cust. group Bike shop Cycles 100 Bikeworld Cycles 200
SAP AG 1999
With automatic planning you can update the generated plan data either directly in the same aspect or, using the transfer rules, you can update it in the same or a different aspect.
Using the transfer rules you can execute extensive additional functions. You can carry out currency translations, restructuring, summarize the data further, or calculate formulas.
The diagram above illustrates the following possibilities: - Direct updating of the data, without changes to the structure. - Grouping data: for example, all customers of the customer group 2-wheeled are aggregated and assigned to the customer group 2-wheeled. - Reassigning the data: for example, all customers are assigned to another customer group (cycles).
© SAP AG
AC625
4-17
Currency Conversion With Data Transfer
Currency table Bank rate: To:
US$ DEM
As at:
12.15.1999
Sndr record:Rev.:
10,000
Currency:
US$
Date:
12.15.1999
Currency conversion: Date-specific conversion : date of conversion fixed date date from transfer record
Base currency: fixed from sender record
1:1.682
Receiver r ecord: R ev.:
15,970
Currency:
DE M
Date:
12.15.1999
C o n v e r s io n
SAP AG 1999
During automatic data transfer, amounts can be translated into the currency of the key figure. The currency of the key figure is derived either from the version or from the reference currency. For currency translation, you need to enter a translation type for the data transfer rules. The translation date you specify also plays a role in the translation:
- The current date - A specific pre-defined date (target date) - The end of the fiscal year, beginning or end of the period - A date taken from a field of the sender structure (type 'D' fields)
If you create a translation type, enter an exchange rate type. You can choose between a normal or an inverse exchange rate (inverse calculation of records that have already been translated), between a fixed and variable translation date, and between a fixed and variable base currency.
With a variable translation date, you must specify a field in the sender structure from which the translation date is determined. This must be a type 'D' field.
With the variable base currency, you must specify a sender structure field that contains the base currency. This field must be of type "C" and length 5. The currency key must also be entered in the table TCURC.
© SAP AG
AC625
4-18
Plan Data Entry: Summary (1)
Interactive updating of plan data can be done directly or by u sing planning layouts
Using authorizations, you can determine which users can process which data areas in the SAP-System
You can use planning profiles to assign various authorizations and planning layouts to specific users in specific sequences
In automatic planning, you can copy, change or convert data records
SAP AG 1999
© SAP AG
AC625
4-19
Plan Data Entry: Summary (2)
When updating with rules, you can group or convert data
EC-BP enables easy quantity-price planning
As part of ratio planning, you can calculate key figures using formulas and inverse formulas
The data can be supplied from both R/3 and non-R/3 Systems
SAP AG 1999
© SAP AG
AC625
4-20
Exercises Unit: Plan Data Entry Topic: Interactive Planning At the conclusion of this exercise, you will be able to:
Create planning layouts
•
Create planner profiles
For planning within an enterprise, you assign authorizations according to the planning responsibilities. You also create planning layouts. Both of these are combined in planner profiles.
1-1
Create two planning layouts in aspect 880 with the names “T-LA a” and “T-LA < group number>b”. The key figures “Quantity” and “Sales” and also the formula “Price” (=sales/quantity) should be in the columns of the first layout. The characteristics “Segment”, “Business unit”, “Division” and “Product line” should be used as lead columns. In the second layout, the lead column should contain the same characteristics; enter the key figures “Sales” and “Return on Investment” in the columns.
1-2
Carry out interactive planning with both layouts in turn. Select division “61” and business unit “6000” for this. Why is the price non-chargeable? In the second layout, what is the difference between free and form-based planning?
1-3
Create a planner profile “T-P”.
1-4
Set the planner profile and call up the interactive planning again.
© SAP AG
AC625
4-21
Unit: Plan Data Entry Topic: Automatic Planning
At the conclusion of this exercise, you will be able to: •
Copy data automatically
The actual data from the previous fiscal year serves as a basis for the plan data for the current fiscal year and must, therefore, be copied.
2-1
© SAP AG
Copy automatically version 1 of the actual data from 1999 within aspect 880 as version “1” plan data for the year 2000.
AC625
4-22
Solutions Unit: Plan Data Entry Topic: Interactive Planning
1-1
Creating planning layouts: Environment → Configuration menu → Business planning → Planning layouts → Create. Choose aspect 880, a new layout name of your choice and choose “Create”. Double click on “Lead column” and choose the characteristic “Product line”. Then generate other lead columns using the menu option “Edit Column New lead columns...”. Set up the three additional key columns for the other three characteristics. Then double click on “Column 1”and select the required key figures. Maintain the fixed characteristics version, plan/actual, period and year either in the columns or for the entire layout using “Edit Gen. data selection Gen. data selection”.
1-2
1-2 Interactive planning: Planning → Interactive → Change plan data. In the form only the basic key figures “Quantity” or “Sales” can be entered since “Price” and “Return on investment” are either formulas or calculated key figures. In the free layout, the only master data displayed is that where data has been posted. The formbased layout displays all master data.
1-3
1-3 Creating the planner profile: 1-3-1 Environment → Configuration menu → Business planning → Planner profile. Choose –“New entries” and enter the name in column 1 (“Profile”). Enter a description of your choice in column 2 (“Description”). In column 3, choose an authorization group (“Auth.group”) by clicking on the arrow on the right of the field or the F4 key. Section: “Business planning”: on the top part of the screen (“Navigation”), click on the second level (magnifying glass symbol, “-- > Business planning”). Click on “New entries” and enter aspect 880 in column 1(“Aspect”). 1-3-2 Section: “Business planning layouts”: on the top part of the screen (“Navigation”), click on the third level (magnifying glass symbol, “-- > Business planning”). Click on “New entries” and enter a number in column 2 (“Item”). Enter the layout in column 3 (“Layout”). If necessary, click on the field (“Overw”) in column 5. Also, if necessary, activate “Integrated Excel” in column 6. 1-3-3 Section “Default parameters”: select the first layout by clicking in the first column. On the top part of the screen (“Navigation”) click on the fourth level (magnifying glass symbol, “-- > Default parameters“). Enter the appropriate values in the rows “Period from” and “Period to”, choose “Free” at “Entry” on the bottom part of the screen and then choose “Overview screen” or F5. The normal planning layout now appears. Now go back two levels by clicking twice on the green “Back” key, saving the values if required.
1-4 © SAP AG
Setting the planner profile: Planning AC625
Interactive
Set planner profile. 4-23
Unit: Plan Data Entry Topic: Automatic Planning
2-1
Automatic copying: Planning Automatic Copy. Using the tab strips you can specify the characteristics and basic key figures to be copied. Click on “Test run” to execute the copying function without posting any data. 2-1-1 Entry under “Plan data”: for Aspect (880) select version “1”, period from “001.2000” and period to “012.2000”. 2-1-2 Entry under “Reference data” (central part of screen): select the appropriate values here also. 2-1-3 Entry under “Extras”: choose “Log”. Choose “Test run” if you want to execute one. 2-1-4 Entry under “Update”: choose “Overwrite”. 2-1-5 Click on “Characteristics” on the top part of the screen and select the characteristics “Segment”, “Business unit”, “Division” and “Product line”. Click on “Key figures” and select all basic key figures using “Select all” at the bottom of the screen. 2-1-6 Click on “Selection” on the top part of the screen. On the following screen you can restrict the characteristics area; however, in this case do not restrict the area. 2-1-7 Click on “Save” on the top part of the screen. This takes you back to the initial screen for automatic copying. 2-1-8 Start the copying operation: Choose “Execute” or press F8.
© SAP AG
AC625
4-24
Plan Data Processing
Contents:
Interactive planning with Excel In-Place
Revaluation of plan data
Characteristics combination
Object-dependent parameters
Seasonal distribution
Top-down planning
Bottom-up planning
Mixed top-down/bottom-up planning
SAP AG 1999
© SAP AG
AC625
5-1
Plan Data Processing: Unit Objectives
At the conclusion of this unit, you will be able to:
Revaluate plan data
Distribute plan data seasonally and
top-down Explain mixed top-down/bottom-up planning within EC-BP
SAP AG 1999
© SAP AG
AC625
5-2
Plan Data Processing: Course Overview Diagram
Unit 1: Introduction Unit 2: EC-BP Functions Unit 3: Modeling the Planning Structure Unit 4: Plan Data Entry
Unit 5: Plan Data Processing Unit 6: Forecast Unit 7: Simulation Calculations Unit 8: Reporting
SAP AG 1999
© SAP AG
AC625
5-3
Plan Data Processing: Business Scenario
Because of the positive economic trends, the plan values for revenue and profit in the Pharmaceuticals Business Unit are to be raised by 1%
An additional investment budget of 100 m. DM is to be distributed evenly over all Business Units
15 m. DM is to be invested in the Insulin product, most of this amount will be allocated at the beginning of the fiscal year
SAP AG 1999
© SAP AG
AC625
5-4
Interactive Planning with Excel In-Place
SAP AG 1999
Apart from the familiar graphical features, Excel In-Place allows you to modify graphics or tables, to change plan data this way, and to then update the data in EC-BP. Excel is thus integrated in the R/3 environment.
© SAP AG
AC625
5-5
Revaluation of Plan Data
fit + Pro
6% R even
ue + 1 1%
e ca Outsid
pital -
Actual data, plan data
3%
Plan data
Version 1
Version 2, 3, ...
SAP AG 1999
Plan or actual values for various key figures can be revalued simultaneously by specifying individual percentage changes for them; These combinations can be defined as 'revaluation factors'.
Using 'object-dependent parameters', you can restrict the revaluation to a small area of the multidimensional data structure, for example to a specific Business Unit.
If a calculation rule exists for a basic key figure, you can decide whether to have it calculated or not.
© SAP AG
AC625
5-6
Characteristics Combination
• If several characteristics and/or key figures are affected by automatic planning...
• •
Revaluation key Seasonal distribution Forecast profile
Characteristics combination Char. A
Revaluation key 1
1
Char. B
Revaluation key 2
2
.
.
.
.
.
.
SAP AG 1999
Many characteristics and/or key figures may be processed in automatic planning. Where these are not to be planned using the same revaluation factor (or seasonal distribution or forecast profile), you can assign different revaluation factors (or seasonal distribution or forecast profiles) to the various characteristic values.
© SAP AG
AC625
5-7
Object-Dependent Parameters
Simultaneous planning of various d ata areas with data different parameters.
Example: Revaluation key Segment Business Unit Segment Business Unit
A 4000, 6000 B
Revaluation key "optimist."
Revaluation key "pessimist."
8000
SAP AG 1999
Using object-dependent parameters in an automatic planning run, you can plan several characteristics with different planning parameters such as revaluation factors or distribution keys.
Object-dependent parameters allow you to restrict or specify the characteristics subject to planning.
© SAP AG
AC625
5-8
Seasonal Distribution
J ASOND
J
F M A M J
J
A S
O N
D J
F M A M
J J
J ASOND
J
F M A M J
J
A S O N
D J
F M A M
J J
Distribution key
1246321
SAP AG 1999
With 'seasonal distribution' you can use a 'distribution key' to distribute plan or actual values from a specific time period. You can redistribute the total value as you wish over the individual periods of the planning period.
© SAP AG
AC625
5-9
Top-Down Planning
Enterprise
A P h ar m& C a he m.
Segment
4 00 0Ch e m .
Bus. Unit
4 1 P ac k . M at e r .
Division
B S e rvi c es
6 0 0 0P h a rm a
43 Med. Subst.
6 1 An al ge t i c s
8 0 0 0S e r v i c e s
6 2 D i ab e t i c s
8 1 P h a rm a M a r k . R e s .
Investment 4 Prod. Line
0% 61 1 Mo n o
60 % 61 2 Co mb o
62 1 Hu m. B as . I n s.
62 2 A n im . B as. Ins .
Reference: Revenue 611 Mono : 40% 612 Combo: 60% SAP AG 1999
With top-down distribution you can distribute either nonassigned values or the total value of a level to the level(s) below it.
As a reference for the distribution, you can use the relevant key figures (for example, sales, payroll costs,...) or a specific key figure (for example, sales only).
© SAP AG
AC625
5-10
Bottom-Up Planning
Enterprise
A P h ar m& C a he m.
Segment
Bus. Unit
Division
Prod. Line
4 00 0Ch e m .
4 1 P ac k . M at e r .
B S e rvi c es
6 0 0 0P h a rm a
43 Med. Subst.
61 1 Mo n o
6 1 An al ge t i c s
61 2 Co mb o
8 0 0 0S e r v i c e s
6 2 D i ab e t i c s
62 1 Hu m. B as . I n s.
8 1 P h a rm a M a r k . R e s .
62 2 A n im . B as. Ins .
SAP AG 1999
EC-BP enables bottom-up aggregation.
© SAP AG
AC625
5-11
Bottom-Up Planning: Individual Steps Bus. Unit
Auto Air
Cost of sales
105 + 5 50 + 10
3. Planning step: Strategic Business Unit Product Line
Cost of sales
Product Line
35 + 10
Product Line
10 + 50
Product groups 1-3 Enterprise
02
20
03
5
02
5
03
10
02
10
Enterprise
01
10
01
15 .
Cost of sales
Cost of sales
Cost of sales
.
Product Line
30 + 20
2. Planning step: Enterprise
Cost of sales
Product Line
Product Line
Cost of sales
1. Planning step: Enterprises 1-3 for product groups 1-3 SAP AG 1999
At each level of planning you can use interactive online planning and/or automatic planning. The system ensures that the data is consistent on all levels since the data is transferred from the lower levels to the higher levels. Example: you wish to plan a P&L account "cost of sales" for companies and product groups. Because of the large number of companies, only the most important are planned at the lowest level. Planning for all other companies will be at the level of the product groups or the strategic business units.
In the first step you plan product groups 1, 2 and 3 for companies 01, 02 and 03.
In the second step you plan the cost of sales for all other companies at the product group level by entering data directly for groups 1, 2 and 3. The system then displays the cost of sales planned in the first step, and those that have been added for all groups, and the quantities planned at product group level in step two.
In the third step, you reconcile the plan at the level of the strategic business units.
The data is then aggregated automatically.
© SAP AG
AC625
5-12
Mixed Top-Down/Bottom-Up Planning
Enterprise
A P h ar m& C a he m.
Segment
Bus. Unit
Division
Prod. Line
4 0 0 0C h e m .
4 1 P ac k . M a t er .
B S e rv i c e s
6 0 0 0P h a rm a
43 Med. Subst.
6 11 M o no
6 1 A n al ge t i c s
6 12 C ombo
8 0 0 0S er vi c e s
6 2 D i ab et i c s
8 1 P h ar m aM a r k . R e s .
621 Hum. Bas. Ins. 622 Anim. Bas. Ins.
SAP AG 1999
EC-BP supports mixed top-down/bottom-up planning. This function is very important in enterprises today.
© SAP AG
AC625
5-13
Plan Data Processing: Summary
Automatic planning in EC-BP allows easy revaluation of plan and actual data
Currency conversion and summarization is done using data
transfer Data can be distributed seasonally or top-down Top-down, bottom-up, and also mixed top-down/bottom-up planning is possible
SAP AG 1999
© SAP AG
AC625
5-14
Exercises Unit: Plan Data Processing Topic: Revaluation, Distribution and Top-Down Planning
At the conclusion of this exercise, you will be able to:
Create distribution keys and carry out seasonal distributions Create revaluation factors and carry out revaluations
Carry out top-down planning
An enterprise's actual data is to be used to generate plan data with a specific seasonal distribution. A second plan data version is to be generated resulting from percentage adjustments to some of the actual data. In a third version, the revenues of the divisions are to be allocated to the product lines using a top-down procedure.
3-1
Create a distribution key with the name “TD”.
3-2
Distribute the data from aspect 880, fiscal year 1999, version 1 seasonally within the same aspect to fiscal year 2000, version “2”; compare the data records using the report “T-Report 5”.
3-3
Create two different revaluation factors with the names “a” and “b”.
3-4
Using one of the two revaluation factors, revaluate the data from aspect 880, fiscal year 1999, version 1 within the same aspect as fiscal year 2000, version “3”.
3-5
Define two planning aid accesses for revaluations using both of the revaluation factors created. The first access will distribute the revenue from product lines 611 and 612 according to the first revaluation factor; the second access will distribute the revenue from product lines 611 and 612 according to the second revaluation factor.
3-6
For Version “4”, any value you wish for the planned revenue for division 61 inenter fiscalmanually year 2000.
3-7
Using a top-down procedure, distribute the planned revenue for division 61 in fiscal year 2000, version “4”, to the product lines according to the distribution of the actual data in fiscal year 1999, version 1.
© SAP AG
AC625
5-15
Solutions Unit: Plan Data Processing Topic: Revaluation , Distribution and Top-Down Planning
3-1
Planning
Planning aids
3-2
Planning Automatic Change: after determining the aspect, the characteristics and basic key figures, enter the distribution key you have created in the relevant field and start the operation.
3-3
Planning
3-4
Planning Automatic Change: after determining the aspect, the characteristics and basic key figures, enter the revaluation factor you have created in the relevant field and start the operation.
3-5
Environment Configuration menu Business planning Object dependent parameters Define planning help: create the new accesses using “New entries”. Environment Configuration menu Business planning Object dependent parameters Derive revaluation factor: create a new “step” with the desired
Planning aids
Distribution key
Create.
Revaluation factors
Change revaluation.
characteristics (segment, business unit, division and product line), and then choose “Maintain rule values”. In the table, enter the access you have created, the required master data, and one of the revaluation factors you have created. Save your entries. Then carry out the revaluation as described above, specifying the object-dependent parameter. 3-6
Plan data Transfers Maintain record: enter the values for the characteristics. Note: the “Product line” field may not be filled since only the “Division” node should be charged.
3-7
Planning Automatic Top-down: enter the desired values when going through the configurations for characteristics, key figures and the distribution key, and start the operation.
© SAP AG
AC625
5-16
Forecast
Contents:
Forecast
Forecast profile and characteristics combination
Interactive forecast
SAP AG 1999
© SAP AG
AC625
6-1
Forecast: Unit Objectives
At the conclusion of this unit, you will be able to:
Use the forecast function in EC-BP
Explain the concept of the forecast profile and characteristics combination
SAP AG 1999
© SAP AG
AC625
6-2
Forecast: Course Overview Diagram
Unit 1: Introduction Unit 2: EC-BP Functions Unit 3: Modeling the Planning Structure Unit 4: Plan Data Entry Unit 5: Plan Data Processing
Unit 6: Forecast Unit 7: Simulation Calculations Unit 8: Reporting
SAP AG 1999
© SAP AG
AC625
6-3
Forecast: Business Scenario
The Chemicals Business Unit sales for the year 2001 are to be forecast using the actual data from fiscal year 1999 and the plan data for 2000
Another forecast is to increase the commercial value of the COMBO product group by 10%
SAP AG 1999
© SAP AG
AC625
6-4
Forecast
? Past
?
?
?
Future
• •
Forecast profile Characteristics combination
Automatic forecast
Fiscal year, period
Fiscal year+, Period+
SAP AG 1999
The forecast is another automatic planning function. Starting with actual or plan data, you can determine future values using mathematical methods.
© SAP AG
AC625
6-5
Forecast Profile and Characteristics Combination
Exp. smoothing (Wtd) average Trend model • Seasonal model • ... •
Forecast profile Forecast strategy Factors Weighting group Previous periods Periods per season
If several characteristics and/or key figures are affected by the forecast...
• •
Statist. factors for selected strategy Relative weighting of individual periods
Characteristics combination Char. A
Forecast profile 1
1
Char. B
Forecast profile 2
2
.
.
.
.
.
.
SAP AG 1999
The forecast strategy determines the mathematical procedure used for the forecast.
The factors depend on the selected procedure and therefore, on the forecast strategy.
The weighting group applies with a certain forecast strategy. It weights the the individual reference data periods.
© SAP AG
AC625
6-6
Interactive Forecast Manual correction Edit Planning functions Forecasting
Forecast
SAP AG 1999
With the interactive forecast, you can manually change the graphically displayed plan data. This can take place by accessing the graphically displayed plan data directly.
© SAP AG
AC625
6-7
Forecast: Summary
You can carry out the forecast in EC-BP either interactively or automatically
You can set up forecast profiles where further forecast parameters are specified
In the interactive forecast you can manually change the graphs of the forecast values and then update the resulting data
SAP AG 1999
© SAP AG
AC625
6-8
Exercises Unit: Forecast Topic: Forecast
At the conclusion of this exercise, you will be able to: •
Use the forecast functionality of EC-BP.
An enterprise's actual data is to be used to generate plan data with a specific seasonal distribution. A second plan data version is to be generated resulting from percentage adjustments to some of the actual data. In a third version, the revenues of the divisions are to be allocated to the product lines using a top-down procedure.
4-1
Create a forecast profile with the name “TP”.
4-2
Create a forecast for the fiscal year 2001, version “1”, using the actual data from fiscal year 1999, version 1.
© SAP AG
AC625
6-9
Solutions Unit: Forecast Topic: Forecast
4-1
Planning Planning aids Forecast profile Change. Choose a strategy (for example, no. 14) and enter the necessary parameters.
4-2
Planning Automatic Forecast: after determining the aspect, the characteristics and basic key figures, enter the forecast profile you have created in the relevant field and start the operation (as with automatic copying).
© SAP AG
AC625
6-10
Simulation Calculations
Contents:
Simulation
Target value search
What-if-analysis
SAP AG 1999
© SAP AG
AC625
7-1
Simulation Calculations: Unit Objectives
At the conclusion of this unit, you will be able to:
Carry out key figures and structure simulations
Generate and change plan data automatically and interactively
SAP AG 1999
© SAP AG
AC625
7-2
Simulation Calculations: Course Overview Diagram
Unit 1: Introduction Unit 2: EC-BP Functions Unit 3: Modeling the Planning Structure Unit 4: Plan Data Entry Unit 5: Plan Data Processing Unit 6: Forecast
Unit 7: Simulation Calculations Unit 8: Reporting
SAP AG 1999
© SAP AG
AC625
7-3
Simulation Calculations: Business Scenario
How great would the effect be on the Pharmaceuticals BU if the diabetics products were assigned to the Chemicals BU?
What effect would a 2% increase in Operating Expenses in the Pharmaceuticals BU have on RoI?
What is the maximum amount that can be invested, if the expected profits of the Pharamaceuticals BU are to rise by at least 6%?
SAP AG 1999
© SAP AG
AC625
7-4
Simulation
Key figure tree Profit
Contribution margin
Sales Sales
Fixed Fixed costs
Profit as % of sales Return on Investment
Net sales
Gross sales
Variable sales costs
Sales deductions
Cash Cash Sales Sales Turnover of capital
Current assets
Receivables Receivables
Fixed assets
Inventories
Invested capital
Calculated key figures, Formulas
Layout ...
...
Variable sales costs
+ 5%
...
...
Return on Investment
...
?
SAP AG 1999
Using calculated key figures and formulas, you can simulate the effects of changes in price, quantity, structure and currency etc.
© SAP AG
AC625
7-5
Target Value Search
Key figure tree Profit
Contribution margin
Sales Sales
Fixed costs
Profit as % of sales Return on Investment
Net sales
Gross sales
Variable sales costs
Sales deductions
Cash Cash Sales Turnover of capital
Current assets
Receivables Receivables
Fixed assets
Inventories
Invested capital
Calculated key figures, Formulas
Layout ...
. ..
Variable sales costs
?
...
...
Return on Investment
...
= 10%
SAP AG 1999
In contrast to simulation calculations, the target value search allows you to define the 'result' of a calculation.
© SAP AG
AC625
7-6
Structure Changes
Chargeable structure
Changeable structure
6000
A 6000
A 62
62
622
622
Characteristic Attribute for ... SAP AG 1999
Using attributes, you can display a chargeable structure, and also illustrate the enterprise structure.
Attributes are stored in the master data table. If there are any changes in the displayed structure, you can change the attribute assignments quickly and easily.
© SAP AG
AC625
7-7
Difference: Characteristic - Attribute
Characteristic
Attribute •
Stored in master data table • Non chargeable • Variable relationship with other figures
•
Stored in aspect Chargeable • No relationship with other figures •
Selection
Report SAP AG 1999
When creating reports, you can choose to use characteristics or attributes. Because of their variety, attributes are suitable for portraying simulations. Characteristics illustrate the basis for the chargeable structures.
© SAP AG
AC625
7-8
What-If-Analysis
Chargeable structure Updated
Current view
6000
A 6262
A 81
A 62
622 622
A 81
622
SAP AG 1999
By changing the assignment of an attribute, you can model a change in the enterprise structure, and determine how this affects, for example financial factors.
© SAP AG
AC625
7-9
Simulation Calculations: Summary
Using calculated key figures and formulas in EC-BP, you can simulate the effect of value changes on the enterprise
You can carry out target value searches
The characteristic attributes in EC-BP enable what-if-analyses by changing the structures
SAP AG 1999
© SAP AG
AC625
7-10
Exercises Unit: Simulation Calculations Topic: Attributes
At the conclusion of this exercise, you will be able to: •
Carry out simulation calculations using attributes.
You are to use a simulation to determine the effects of a change in the company structure on the business key figures.
5-1
Create a report with the name ”T-Repa”. Select the characteristics “Segment”, “Business Unit”, “Division” and “Product Line” and the key figures “Sales”, Operating Profit” and “Return on Investment”. The report should not contain any hierarchy and should refer to the plan data from Version 1 of fiscal year 2000.
5-2
Create a second report with the name “T-Repb” similar to the first report but instead of the “Segment”, “Business Unit” and “Division” select the corresponding attributes “T-Attr. Segment”, “T-Attr. Business Unit” and “T-Attr. Division”.
5-3
Execute both reports. Perform a drilldown as far as the product line. Is there any difference between the two?
5-4
Now simulate a structure change: change the assignment of the product line “Combo” from the “Analgetics” division to the “Diabetics” division.
Note: Change the corresponding attributes.
5-5
© SAP AG
Execute both reports again. Where are there differences and what are the reasons for these? AC625
7-11
Solutions Unit: Simulation Calculations Topic: Attributes
5-1
Report Create: enter the name of the report. Choose “Basic Report”. Then enter the year 2000 and the limiting periods 01 and 12 and also the plan/actual key figure 1. In the window “Characteristics” select all four required characteristics. Do the same for the key figures.
5-2
Proceed as described above but, instead of the characteristics, select the appropriate attributes.
5-3
Execute the reports using Report Execute report. No differences are apparent when drilling down to the product line level.
5-4
Master data Characteristic values Maintain: Select aspect 880 and the characteristic “Product Line”. Assign product line “612” to division “62” instead of division “61”.
5-5
Execute both reports again. If you drill down to the product line level, it becomes apparent that the changes affect only the attribute-based, report. structure In contrast the first report shows that the various chargeable nodes ofsecond the enterprise are independent of each other.
5-6
© SAP AG
Execute the reports using Report Execute report. No differences are apparent when drilling down to the product line level.
AC625
7-12
Reporting
Contents: Plan/actual comparison Report types Comments
SAP AG 1999
© SAP AG
AC625
8-1
Reporting: Unit Objectives
At the conclusion of this unit, you will be able to:
Recognize the reporting options in EC-BP
Understand the use of comments and exceptions
SAP AG 1999
© SAP AG
AC625
8-2
Reporting: Course Overview Diagram
Unit 1: Introduction Unit 2: EC-BP Functions Unit 3: Modeling the Planning Structure Unit 4: Plan Data Entry Unit 5: Plan Data Processing Unit 6: Forecast Unit 7: Simulation Calculations
Unit 8: Reporting
SAP AG 1999
© SAP AG
AC625
8-3
Reporting: Business Scenario
Within the Pharmaceuticals & Chemicals
segments, a plan/actual comparison is to be carried out. The fiscal years to be considered are 1998, 1999 and 2000. The results, including appropriate comments, are to be delivered to group management by e-mail.
SAP AG 1999
Your project team is to construct an executive information system for your company using the SAP EC-Executive Information System.
When your project team has determined from which data sources or systems future users would like to have their information requirements met, you can start structuring your data basis.
You have to define the database tables which will later include the data and form the basis for reports which will be called up within EIS.
You have several ways of designing your database so that later the information will be used optimally.
For data that cannot be collected using standard methods, you can create various types of entry layouts.
From the point of view of business planning you define planning layouts and if necessary, have the system generate plan data.
You use specific techniques to make your future reporting more effective.
© SAP AG
AC625
8-4
Plan/Actual Comparison
Exceptions Plan
Actual
Absol.dev.
Dev.%
Sales
140,000.00
150,000.00
10,000.00
7 .1
Profit
25,000.00
30,000.00
5,000.00
20.0
.
.
.
.
.
. .
. .
. .
.
. .
.
Comment
SAP AG 1999
In EC-BP you can display actual and plan data in tabular or graphical form.
You can easily create exceptions for individual cells or entire columns.
Comments may be transmitted as messages.
© SAP AG
AC625
8-5
Report Types
Basic report Fast generation of a report
Selection of variables
Selection of characteristics
Selection of key figures
Form report For individually prepared reports with
Form-based layout
Special formatting (colors, dividing lines, etc.)
SAP AG 1999
While end users can view pre-defined reports, graphics, and texts in the report portfolio, the object of drilldown reporting is to display different business views where the user selects appropriate combinations of characteristics and key figures. The underlying principle of drilldown reporting is that basic reports can be generated quickly and easily, whereas for more complex reports, all the necessary functions are available. This means that you can generate the reports in different ways.
Basic reports: Users often choose this procedure when they start a spontaneous, ad-hoc search for a business matter in the dataset, and they do not know beforehand where and what they are searching for. It is relatively easy to set up this kind of report.
Form reports: These are more complicated to set up and are more specific. This procedure is often chosen for official reporting and is particularly suited for printing of reports.
A distinction is made between reports that are defined spontaneously (basic reports), and reports that are based on pre-defined forms. The latter are called form reports. Form reports are based on forms with either one coordinate or two, depending on their complexity.
A form is not required for a basic report. When you define a basic report, you select the characteristics you wish to report on, and also the key figures and variables of interest.
A drilldown report always refers to the business objects in an aspect.
© SAP AG
AC625
8-6
Comments Aspect Country
Comment
Country
Region
---
Comment
---
DE Germany ES Spain
Comment
Comment
........... ..... .........
Report name Country
Revenue
Costs
Quantity
Germany
1,000,00
300,000
1,000
S p ain
2, 300 ,0 00
270,000
1,600
:
:
:
:
:
France
USA
:
: Footnote: ........... ..... ......... ........... ..... ......... SAP AG 1999
You can add comments when creating plan data interactively.
In EC-BP you can create comments in different languages for the following areas:
- Reports - Field-catalog fields - Key Figures - Master data (only applies to BP/EIS-generated characteristics) - Transaction data.
You can add comments on transaction data while you are executing reports.
© SAP AG
AC625
8-7
Reporting: Summary
Using calculated key figures and formulas in EC-BP, you can simulate the effect of value changes on the enterprise
You can carry out target value searches
The characteristic attributes in EC-BP enable what-if-analyses by changing the structures
SAP AG 1999
© SAP AG
AC625
8-8
