Vous êtes sur la page 1sur 253
AP210 Demand Planning AP210AP210 DemandDemand PlanningPlanning ? ? SAP AG SAP AG 2001
AP210 Demand Planning
AP210AP210
DemandDemand PlanningPlanning
? ?
SAP AG
SAP AG 2001

??SAP APO ??Release 3.0A ??April 2001 ??Material number: 50041878

Copyright
Copyright

Copyright 2001 SAP AG. All rights reserved.

No part of this publication may be reproducedor transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.

All rights reserved.

? SAP AG 2001

Trademarks:

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

??Microsoft ® , WINDOWS ® , NT ® , EXCEL ® , Word ® , trademarks of Microsoft Corporation.

??IBM ® , DB2 ® , OS/2 ® , DB2/6000 ® , Parallel Sysplex ® , MVS/ESA ® , RS/6000 ® , AIX ® , S/390 ® , AS/400 ® , OS/390 ® , and OS/400 ® are registered trademarks of IBM Corporation.

??ORACLE ® is a registered trademark of ORACLE Corporation.

??INFORMIX ® -OnLine for SAP and INFORMIX ® Dynamic Server TM are registered trademarks of Informix Software Incorporated.

??UNIX ® , X/Open ® , OSF/1 ® , and Motif ® are registered trademarks of the Open Group.

??HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C ® , World Wide Web Consortium, Massachusetts Institute of Technology.

??JAVA ® is a registered trademark of Sun Microsystems, Inc.

??JAVASCRIPT ® is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.

??SAP, SAP Logo, R/2, RIVA, R/3, ABAP, SAP ArchiveLink, SAP Business Workflow, WebFlow, SAP EarlyWatch, BAPI, SAPPHIRE, Management Cockpit, mySAP.com Logo and mySAP.com are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other products mentioned are trademarks or registered trademarks of their respective companies.

PowerPoint ® and SQL Server ® are registered

Curriculum Advanced Planner and Optimizer (APO)
Curriculum Advanced Planner and Optimizer (APO)

Level 2

SAP R/3

LO050

5 days

PP - Planning & control of discrete & repetitive manufacture

Level 2

SAP R/3

LO060

5 days

PP PI

Process Manufacture

? SAP AG 2001

Level 2 Level 3 SAP APO SAP APO AP210 3 days Demand Planning AP215 3
Level 2
Level 3
SAP APO
SAP APO
AP210
3 days
Demand Planning
AP215
3 days
AP010
2 days
Supply
SAP APO Overview
Network Planning
AP205
2 days
AP220
3 days
Master Data
Integration
Production Planning /
Detailed Scheduling
AP230
2 days
Global Available
BC555
2 days
to Promise
liveCache
Administration

??The level 2 course, AP010, is the first of the SAP Advanced Planner and Optimizer training courses and provides an overview of the individual SAP APO components. It is also a prerequisite for the advanced level 3 SAP APO training courses.

??The level 3 courses improve on the knowledge base provided by AP010 and deepen your subject area knowledge of the individual SAP APO components. The five level 3 courses consider the following areas in detail:

Demand Planning, Integration, Supply Network Planning, Production Planning and Detailed Scheduling, and Global Available to Promise.

??System administrators have the opportunity to take the course BC555 "LiveCache Administration" which forms part of the Basis Administration Training curriculum.

Course Prerequisites
Course Prerequisites

Prerequisites

Course Prerequisites Prerequisites ? AP010 SAP APO Overview Recommended ? LO935 Flexible Planning ? BW220 Business
? AP010 SAP APO Overview
?
AP010 SAP APO Overview

Recommended

? LO935 Flexible Planning ? BW220 Business Information Warehouse – SAP – OLTP Extraction
? LO935 Flexible Planning
? BW220 Business Information Warehouse –
SAP – OLTP Extraction

? SAP AG 2001

Target Group
Target Group
Target group ? Project team ? members who are responsible for configuring Demand Planning, and
Target group
?
Project team ? members who are responsible for
configuring Demand Planning, and creating demand
plans
Duration
?
? 3 Tage

? SAP AG 2001

??Notes for the user

??The training materials are not teach -yourself programs. They complement the course instructor's explanations. Your material includes space for noting down this additional information.

??There may not be enough time to do all the exercises during the course. The exercises are intended to be additional examples. Participants can also use them to deepen their knowledge after the course.

Company Profile, Precision Pump Company
Company Profile, Precision Pump Company

Precision Pump Company

Profile, Precision Pump Company Precision Pump Company ? The Precision Pump Company was launched in 1971,
? The Precision Pump Company was launched in 1971, and is the market leader, selling
?
The Precision Pump Company was launched in 1971, and is the
market leader, selling a large variety of hi-tech standard pumps. It has
?
been indexed in the New Yorker stock index NASDAQ 100 since 1998.
Products
? The company’s product catalog includes turbo-molecular
pumps, rotational pumps, and membrane pumps
(to produce ultra high vacuums)
?
Customers
? From the electronics industry, semiconductor
industries, chemical technology, pharmaceutical
technology, and industrial technology, up to and
including vehicle manufacturers, and universities.

? SAP AG 2001

??The Precision Pump Company was launched in 1971, and is the market leader, selling a large variety of hi-tech standard pumps. Its product catalog includes turbomolecular, centr ifugal, rotational, and membrane pumps. The customer base is wide-ranging. It consists of the electronics, and semiconductor industries, chemical, and pharmaceutical companies, and others in the process industry, but also includes vehicle manufacturers, and universities. The company recently became ISO certified and has been indexed in the New Yorker stock index NASDAQ 100 since 1998.

??Especially in the rapidly growing business area of turbomolecular pumps, the company has shown a clear rise in revenue over the past fiscal year: in the semiconductor industries countless steps, from wafer manufacture, to the final chip, can only be made under high vacuum conditions. In this area, there must be an ultimate pressure of < 10-10 mbar (i.e. ultrahigh vacuum).

??During the current fiscal year, the company is planning to enter the booming DVD growth market. DVDs are a form of rewritable optical memory media. They are distinguished from the CD by their large memory capacity. Coating equipment needed to create these rewritable DVDs also use vacuum technology.

??Via intensive 'co-engineering' with manufacturers, Precision Pump Company has optimized a large number of products to match these special requirements.

Plants and Distribution Centers 25002500 DCDC RotterdamRotterdam 30003000 NewNew YorkYork 1000 1000 Hamburg Hamburg
Plants and Distribution Centers
25002500 DCDC RotterdamRotterdam
30003000 NewNew YorkYork
1000 1000 Hamburg Hamburg (main (main plant plant and and company company
headquarters) headquarters)
24002400 DCDC MilanMilan
23002300 BarcelonaBarcelona
38003800 DenverDenver

? SAP AG 2001

PlantPlant

DCDC

??This slide shows the central section of the Precision Pump Company’s supply chain. All the locations shown exist as plants in the connected OLTP (R/3) system:

??Three production plants:

1000

– Hamburg

2300

– Barcelona

3000

– New York

??Three Distribution Centers(DC)

2400

– Milan

2500

– Rotterdam

3800

– Denver

Sales from Sales Organizations Italy and Holland
Sales from Sales Organizations Italy and Holland

2503 Norwegian Import & Export

2502 Miller & Son, London 2500 DC Rotterdam P-102, P-103, P-104 P-102, P-103, P-104 80
2502 Miller & Son,
London
2500 DC Rotterdam
P-102, P-103, P-104
P-102, P-103, P-104
80 %
1000 Hamburg (headquarters)
20 %
20 %
P-102, P-103, P-104
80 %
2300 Barcelona
P-102, P-103, P-104
2400 DC Milan
1320 Naples
Export
2402 Jashanmal

? SAP AG 2001

% 2300 Barcelona P-102, P-103, P-104 2400 DC Milan 1320 Naples Export 2402 Jashanmal ? SAP

Trading, Dubai

??This slide shows the distribution of finished products P-102, P -103 and P-104.

??DC 2400 can obtain finished products P-102, P-103, and P-104 from both plants 1000 (Hamburg) and 2300 (Barcelona). Quota arrangement controls the amount obtained from each plant, in this case 80% from plant 2300, and 20% from plant 1000.

??DC 2500 can obtain finished products P-102, P-103, and P-104 from both plants 1000 (Hamburg), and 2300 (Barcelona). Quota arrangement controls the amount obtained from each plant, in this case 80% from plant 1000, and 20% from plant 2300.

??Pumps P -102, P -103, and P -104 are delivered to customers 2502, and 2503 from DC 2500 (Rotterdam).

??Pumps P -102, P -103, and P -104 are delivered to customers 1320, and 2403 from DC 2400 (Milan).

Customers
Customers

? Customers of sales organization 1000 (Germany), distribution channel 10, division

00:

? 1000 Becker, Berlin (transportation zone DE-D000010000)

? 1032 Institute of environmental research, Munich (transportation zone DE-D000080000)

? 1320 Becker, Cologne (transportation zone DE-D000050000)

? 1031 Global Trade AG, Frankfurt (transportation zone DE-D000060000)

? 1030 DELA , Energy Trading Company mbH, Darmstadt (transportation zone DE-

D000060000)

? 1410 Pilar on the Neckar, Heidelberg (transportation zone DE-D000060000)

? 1321 Becker, Stuttgart (transportation zone DE-D000070000)

? Customers of sales organization 2400 (Italy):

? 2401 Naples Export, Naples (Italy)

? 2402 Jashanmal International Trading Co, Dubai (United Arab Emirates)

? Customers of sales organization 2500 (Holland):

? 2502 Miller & Son Trading Ltd., London (GB)

? 2503 Norwegian Import & Export Group, Oslo (Norway)

? Customers of sales organization 3000 (USA)

? 3140 Rainbow Chemical, Boston

? SAP AG 2001

Product Group
Product Group
   

Product group

 

Pumps

 
   

APO

 

APO

 

APO

 

Pump

Pump

   

Pump

   

Pump

Precision 101

Precision 102

Precision 103

Precision 104

P-100

P-102

 

P-103

 

P-104

(T-F1xx)

(T-F2xx)

(T-F3xx)

(T-F4xx)

Pump P-100 only maintained in R/3 and can be transferred to APO for Master Data integration demo

Legend:

(Demo material number for SD, consulting) (training material number (xx = 00 - 20) for training)

? SAP AG 2001

Course Overview
Course Overview

Contents:

? Architecture & Integration

? InfoCubes

? Demand Planning Configuration

? Interactive Planning

? Forecasting Techniques

? Promotion Planning

? Demand Planning Release

? SAP AG 2001

Course Objectives
Course Objectives
? Configure Demand Planning in APO ? Create planning books and macros ? ? ?
?
Configure Demand Planning in APO
?
Create planning books and macros
?
?
?
in APO ? Create planning books and macros ? ? ? At the conclusion of this

At the conclusion of this course, you will be able to:

Create demand plans using univariate forecasting, causal analysis, and composite forecasting

Utilize marketing and sales tools such as promotion planning, lifecycle management, and "like" modeling

Release demand plans to the liveCache of APO (Supply Network Planning and Production Planning / Detailed Scheduling).

? SAP AG 2001

Course Content
Course Content
Preface Unit 1 Course Overview Unit 6 Forecasting Unit 2 InfoCubes Unit 7 Promotions &
Preface
Unit 1
Course Overview
Unit 6
Forecasting
Unit 2
InfoCubes
Unit 7
Promotions & Lifecycle
Planning
Unit 3
Configuration
Unit 8
Mass Processing
Unit 4
Planning Books & Macros
Unit 9
Conclusion
Unit 5
Interactive Planning

? SAP AG 2001

Course Overview Diagram 11 1 Course Overview 1 2 22 InfoCubes 3 33 Configuration 4
Course Overview Diagram
11
1
Course Overview
1
2 22
InfoCubes
3 33
Configuration
4 44
Planning Books and Macros
555
Interactive Planning
666
Forecasting
777
Promotions &
Lifecycle Planning
8 88
Mass Processing
999
Conclusion

? SAP AG 2001

Business Scenario ? The Precision Pump company will implement APO Demand Planning and use it
Business Scenario
? The Precision Pump company will implement APO
Demand Planning and use it to execute their
monthly finished product forecasting.
? Consistent planning allows you to enter the forecast
data on different planning levels and automatically
consolidate the data in the master forecast.
? SAP AG 2001

??Demand Planning is the application component in the Advanced Planner and Optimizer (APO) that allows you to forecast market demand for your company's products. The result of APO Demand Planning is the demand plan.

??Demand Planning is a complex, powerful, and flexible tool that supports your company's demand planning process. User-specific planning layouts and interactive planning books not only allow you to include different departments, you can also use them to include other companies in the forecast creation process. With APO Demand Planning you can use statistical forecasting methods and advanced macro techniques to do the following: - Create forecasts from sales history, based on many different causal factors; - Test predefined, and user-defined forecast models, and forecast results; - And use a consensus-based approach to consolidate the demand plans of different departments. You can use forecast overrides and promotions to add marketing intelligence and management adjustments. The seamless integration with APO Supply Network Planning supports an efficient Sales and Operations Planning (S&OP) process.

Demand Planning Concept
Demand Planning Concept
Location Aggregated actual data Product hierarchy Sold-to party Sales organization Region
Location
Aggregated actual data
Product hierarchy
Sold-to party
Sales organization
Region
? Incoming order value ? Quantities ? Values ? Invoice ? Quantities ? Values ?
? Incoming order
value
? Quantities
? Values
? Invoice
? Quantities
? Values
? …
? Values ? Invoice ? Quantities ? Values ? … BW R/3 Excel Non-SAP system Future

BW

R/3

Excel

Non-SAP system

Future demand

forecast

Future demand forecast
? Statistical forecasting ? Collaborative forecasting ? Promotions
? Statistical forecasting
? Collaborative forecasting
? Promotions

? SAP AG 2001

??The APO DP library of statistical forecasting and advanced macro techniques allows you to create forecasts based on sales history as well as any number of causal factors, and use a consensus -based approach to consolidate the results.

??Marketing intelligence and management adjustments can be added by using forecast overrides and promotions.

??Aggregated actual data can be extracted from the R/3 system in exactly the same way as it can be imported from BW, Excel, and legacy systems.

The Demand Planning Lever Effect
The Demand Planning Lever Effect

Demand Planning

Supply Network Planning

Supply Network Planning

Supply Network Planning
Production Planning

Production

Planning

Production Planning

? SAP AG 2001

The Demand Planning Lever Effect Demand Planning Supply Network Planning Production Planning ? SAP AG 2001

??Small changes made during Demand Planning cause large changes to be made during Production Planning. The aim of Demand Planning therefore is to create sales quantity forecasts that are as accurate as possible.

Influencing Factors in Demand Planning
Influencing Factors in Demand Planning

Company 1

Company 2

Customer

Central Regional Central Regional Store Promotion Promotion Store D/C Store Promotion Promotion D/C Season
Central
Regional
Central
Regional
Store
Promotion
Promotion
Store
D/C
Store
Promotion
Promotion
D/C
Season Season
Sales Sales Force Force
Price Price
Price Price
Weather Weather
Advertisement Advertisement

? Understanding demand in a dynamic business environment

? Multiple sources of demand plan data such as: internally created forecasts based on history, forecasts from customers, or point of sale (POS) data direct from retailers

? Managing all significant factors that influence demand

? Tracking and management of product lifecycles

? SAP AG 2001

??The complexity and competitive nature of today's business environment requires organizations to consider many variables when developing a sales and operations plan.

??Multiple sources of demand plan data (e.g. manufacturer forecast is based on a distributor’s sales history, and/or point of sales direct from retailer.)

??Factors influencing demand (sales force size, R&D expenditures, advertising expenditures, price, promotions, seasonality.)

??Demand data can be exchanged with sales organizations, customers, and suppliers over the Internet (Collaborative Demand Planning).

Range of Planning Functions
Range of Planning Functions
Planning Horizon Demand Planning (DP) Supply Network Planning (SNP) Production Planning (PP) Detailed Scheduling (DS)
Planning Horizon
Demand Planning (DP)
Supply Network Planning (SNP)
Production Planning (PP)
Detailed Scheduling (DS)
Deployment
Transportation Planning
? SAP AG 2001

??Planning horizons vary depending on the tools used within APO and their application. In an extreme case, demand planning might typically consider a 1-3 year planning horizon where TLB will have a horizon of days.

??The seamless integration with APO components Supply Network Planning (SNP), and PP/DS supports an efficient S&OP process.

APO Application Architecture
APO Application Architecture
OLTPOLTP (R/3)(R/3) APOAPO Supply Chain Cockpit LIS, CO-PA HR, FI Demand Planning Historical Planned Indep.
OLTPOLTP (R/3)(R/3)
APOAPO
Supply Chain Cockpit
LIS, CO-PA
HR, FI
Demand Planning
Historical
Planned Indep.
data
Requirements
Customer
orders
PP / DS
Supply
Key
Global
Production
Network
Performance
ATP
Scheduling
Planning
Key figures
(KPIs)
Inventory
Deployment
management
Transportation
Transportation Planning
processing

? SAP AG 2001

??Aggregated actual data can be transferred to APO from OLTP, BW (Business Information Warehouse), Excel, and Legacy systems, and saved in InfoCubes. This data is the basis for forecasting. The demand plan is created as a result of the forecast.

??You release the demand plan to Production Planning, which creates planned independent requirements for Supply Network Planning (SNP), and PP/DS. You can also transfer the demand plan to the operating system (OLTP) as planned independent requirements.

??The seamless integration with Supply Network Planning (SNP), and PP/DS supports an efficient S&OP process.

Alert Monitor Integration
Alert Monitor Integration
Exception messages from forecasting techniques and self- defined macro alerts DP PP/DS APO Alert Repo-
Exception messages
from forecasting
techniques and self-
defined macro alerts
DP
PP/DS
APO
Alert
Repo-
sitory
SNP
Others
alerts DP PP/DS APO Alert Repo- sitory SNP Others Cockpit Problem Resolution Screen Example: Production

Cockpit

DP PP/DS APO Alert Repo- sitory SNP Others Cockpit Problem Resolution Screen Example: Production Planning /
DP PP/DS APO Alert Repo- sitory SNP Others Cockpit Problem Resolution Screen Example: Production Planning /

Problem Resolution Screen

Example:

Production Planning / Detailed Scheduling

Supply Network

Planning

Screen Example: Production Planning / Detailed Scheduling Supply Network Planning Alert Monitor ? SAP AG 2001

Alert Monitor

? SAP AG 2001

??Exception messages in APO are generally known as alerts.

??In Demand Planning you can define your own alerts using macros.

??The Alert Monitor can be accessed from either the DP planning table, or the Supply Chain Cockpit (SCC).

??Exceptions detected are automatically collected in the alert repository, and evaluated in the Alert Monitor.

??To display information in the Supply Chain Cockpit (SCC), you must first preselect all the objects for which you want to receive alerts in the Alert Monitor profile.

??The Alert Monitor profile functions as a filter for viewing specific sets of alerts. You must create a separate profile for each alert selection. Furthermore, you must enter the name of the Alert Monitor profile you want to use in the Supply Chain Cockpit user profile.(See APO documentation: Supply Chain Cockpit). If no Alert Monitor profile name is specified in the SCC profile and no work area is assigned to the alert selection, no alerts will be displayed in the monitor.

APO Integration - Business Warehouse
APO Integration - Business Warehouse
Demand Planning ForecastForecast ReportingReporting Sales history, Business APO Price, Costs, Information Data
Demand Planning
ForecastForecast
ReportingReporting
Sales history,
Business
APO
Price, Costs,
Information
Data Mart
Warehouse
Forecast

Demand Planning specific data

? Forecast & planning scenarios

? Causal factors

? Lifecycle patterns

? Seasonal patterns

? Promotional patterns

Central Data Pool

?

Summarized data

?

POS, order, and shipment data

?

Syndicated POS data

?

Cost information

?

? SAP AG 2001

??SAP's Business Information Warehouse (SAP BW) is contained in the APO scope of supply and is completely integrated with it.

??If you are going to execute extensive reporting, it is a good idea to set up an independent BW server, and only transfer the data that is relevant for planning to the APO system.

??As data structures in BW and APO are identical, you can also evaluate APO data with the BW frontend.

Evaluations in APO
Evaluations in APO

? Using the BW Business Explorer you can evaluate:

? Order data from the liveCache

? Aggregated data in InfoCubes

data from the liveCache ? Aggregated data in InfoCubes Business Explorer ? SAP AG 2001 Extraction

Business Explorer

? SAP AG 2001

Extraction
Extraction
Extraction

Extraction

structure

   

RemoteCube

Extraction structure     RemoteCube
Extraction structure     RemoteCube

DP InfoCube

Planning area liveliveCacheCache
Planning
area
liveliveCacheCache

??You can also evaluate data from APO using the BW frontend.

??It is not only the aggregated actual data from the InfoCubes that are evaluated, but also all of the order and time series objects from the liveCache.

??The prerequisites for 'liveReporting' orders and time series are as follows: a planning area in APO; an extraction structure for the planning area; an infosource, and an SAP RemoteCube that reflects the liveCache data.

Data Structure: InfoCubes
Data Structure: InfoCubes
Data Structure: InfoCubes Aug. Sept. W32 W33 W34 W35 W36 W37 W38 W39 W40 W41 Time
Aug. Sept. W32 W33 W34 W35 W36 W37 W38 W39 W40 W41 Time series Product
Aug.
Sept.
W32
W33
W34
W35
W36
W37
W38
W39
W40
W41
Time series
Product
Product hierarchy
Period
Regions Regions
Regions
Regions

InfoCubes are used to store actuals from OLTP systems in APO

? SAP AG 2001

??An InfoCube consists of a number of relational tables that are arranged according to the star schema:

a large fact table in the center, surrounded by several dimension tables. Dimension tables are independent of one another. The fact table connects the dimensions with the key figures.

??InfoCubes are used in BW and Demand Planning as central data containers They consist of key figures, attributes, and time characteristics.

??A key figure is a numerical value that is either a quantity or a monetary amount; for example, projected sales value in dollars or projected sales quantity in pallets.

??Characteristics are the objects by which you aggregate, disaggregate and evaluate business data.

??Time characteristics define the periods in which you view, plan and store data.

??The multidimensional nature of the InfoCubes allows for powerful data analysis capabilities using the Demand Planning selection and drill up / drill down functions.

Defining a Planning Area
Defining a Planning Area

Collaboration

Interactive Planning

Planning book I Planning book II Planning Areas Time series Orders liveliveCacheCache liveliveCacheCache Actuals
Planning book I
Planning book II
Planning Areas
Time series
Orders
liveliveCacheCache
liveliveCacheCache
Actuals
Business
Core
Extraction
Explorer
Interface

? SAP AG 2001

??A planning area is the central data structure of Demand Planning and Supply Network Planning. It groups together the parameters that define the scope of planning activities. It also determines where and how the planning results are saved.

??In Demand Planning and Supply Network Planning, data is divided into planning areas, and subdivided into versions. Consequently, the data that you save in planning version 1, planning area 1 does not overwrite the data in planning version 1, planning area 2.

??The planning area contains characteristics, and key figures for planning, and must be initialized for every planning version.

??A key figure is a numerical value that is either a quantity or a monetary amount; for example, projected sales value in dollars or projected sales quan tity in pallets.

??Characteristics are the objects by which you aggregate, disaggregate and evaluate business data.

??Key figure data can be read from different InfoCubes or time series objects.

??Key figure planning data is stored in time series objects in the liveCache.

The Planning Table
The Planning Table
Selection APO - Product Total APO - Location Total ID Object Text Design Graph Capacity
Selection
APO - Product
Total
APO - Location
Total
ID
Object
Text
Design
Graph
Capacity Leveling
Object 1
Text 1
Title view
W 24
W 25
W 26
W 27
W 28
Object 2
Text 2
Key figure 1
Object 3
Text 3
Key figure 2
Object 4
Text 4
Key figure 3
Selection profile
Key figure 4
User
Key figure 5
Selection ID
Header information
Selected objects
Planning book
Right mouse button:
Data views
additional settings
Standard selections
Macros

? SAP AG 2001

??The APO modules Demand Planning and Supply Network Planning have a standard user interface. It consists of two significant components: the selection range and the work area.

??The selection range (Shuffler) is the window, where you choose the InfoObjects to be planned.

??In the Shuffler, you can save commonly used selections, and load existing selections. To open the Shuffler, choose the symbol selection window.

??The selection profile displays all the selection IDs which have been assigned for the planner. The planner can access commonly used selections quickly using the selection IDs.

??In the data view area, you choose your planning books, and views. You can define a filter for available planning books and views.

Planning & Reporting
Planning & Reporting

? Consistent planning (top down, middle out, bottom up)

? Slice & dice

? Drill downs & ups

? Multiple demand plans to be simulated

? Standard forecast accuracy analysis

? SAP AG 2001

Aug. Sept. W32 W33 W34 W35 W36 W37 W38 W39 W40 W41 time sequence 203
Aug.
Sept.
W32
W33
W34
W35
W36
W37
W38
W39
W40
W41
time sequence
203
124
Regions
Material
Product Groups
Period
Customer
W33 W34 W35 W36 W37 W38 W39 W40 W41 time sequence 203 124 Regions Material Product

??Planning supports online simulation in multiple planning scenarios, consistent planning throughout your enterprise (top down, middle out, or bottom up), drilling up and down, aggregation and disaggregation, and slice-and-dice techniques.

??Consistent planning means that planning data on all planning levels can be consistently held (automatic aggregation and disaggregation).

Statistical Toolbox
Statistical Toolbox

? Univariate Forecasting

? Moving average

? Models (constant, seasonal trend, seasonal)

? Exponential smoothing

? Seasonal linear regression

? Holt-Winters

? Croston's method (for sporadic demand)

? Causal Analysis

? Multiple linear regression

? Composite forecasting

? Weighted average of multiple models

? SAP AG 2001

Analysis ? Multiple linear regression ? Composite forecasting ? Weighted average of multiple models ? SAP
Analysis ? Multiple linear regression ? Composite forecasting ? Weighted average of multiple models ? SAP

??The product portfolio of a company covers a variety of products in different stages of their lifecycle and with different demand types.

??APO Demand Planning offers a "toolbox" of proven forecasting methods. The system allows you to choose the best method for a specific demand type.

??Composite forecasting extends the idea of pick-the- best; with this technique you combine two or more methods.

??Croston's method allows you to model "lumpy" (sporadic) demand.

??The statistical forecasting toolbox provides all the features you require to efficiently create accurate forecasts, including everything from data analysis via time series models through multiple linear regression.

Lifecycle Management & Like Modeling Actual data of the old product Forecasting of the new
Lifecycle Management & Like Modeling
Actual data of the old product
Forecasting of the new product
Sales
Like
Lifecycle
Time

? SAP AG 2001

??You use lifecycle planning and "Like" modeling to forecast the launch (phase- in) and discontinuation (phase-out) of a product.

??A product's lifecycle consists of different phases: launch (phase-in), growth, maturity, and discontinuation (phase-out). This process models launch, growth and discontinuation phases.

??For all characteristic value combinations, you can use either a "like" profile, a phase- in profile, or a phase-out profile, or any combination of these.

??If the phase-out profile period is within the history horizon of the master forecast profile, the system adjusts history input values, displays the adjusted values in the original history and corrected history key figures, and writes the adjusted values in the corrected history.

??If the phase-in profile period is within the future horizon of the specified master forecast profile, the system adjusts baseline (original) forecasts, and writes the adjusted values in the corrected forecast key figure.

Promotion Planning
Promotion Planning
Forecast simulation Sales Total sales: Profit Total profit: Promotion 1 Promotion patterns ’95 ’96 ’97
Forecast simulation
Sales
Total sales:
Profit
Total profit:
Promotion 1
Promotion patterns
’95
’96
’97
’98
-10%
Price
Planner
Planner
Quantity

? SAP AG 2001

??Promotions can have a major impact on consumer behavior.

??In APO Demand Planning, you can plan promotions or other special events independently of the rest of your forecast.

??Use Promotion Planning to record either one-time events, such as the millennium, or repeated events such as quarterly advert ising campaigns. Other examples of promotions are trade fairs, coupons, free-standing inserts, competitors' activities, market intelligence. Examples of events that also have an impact on consumer behavior are upward/downward economic trends, and acts of nature, such as hurricanes, and tornadoes.

??Promotional uplifts can be defined in units or percentages by common promotion patterns. The effect of a promotion pattern that occurred in the past can be automatically detected using sales history or estimated by the planner. A promotion pattern can be archived in a promotion catalog; it can therefore be reused if a promotion of the same type is repeated. A copy function in the promotion catalog also supports "like" modeling of "like products," "like regions", and so on. There are several techniques available to determine the impact of a historical promotion. One such technique is multiple linear regression with or without a trend or seasonality.

Release of Sales Quantities as Planned Independent Requirements
Release of Sales Quantities as Planned
Independent Requirements

Demand Planning

Key figure: sales quantity Macros Alerts
Key figure: sales quantity
Macros
Alerts

Key figure: feasible sales quantity

? SAP AG 2001

Production Planning

SNP PP/DS
SNP
PP/DS

Planned independent requirementsAlerts Key figure: feasible sales quantity ? SAP AG 2001 Production Planning SNP PP/DS Production quantities

Production quantitiesKey figure: feasible sales quantity ? SAP AG 2001 Production Planning SNP PP/DS Planned independent requirements

??Once the various stakeholders in the forecast have reached a one-number, consensus plan, you release the demand plan as a planned independent requirement.

??You release the demand plan from Demand Planning (DP) via either the demand planner or the SNP planner.

??This release causes planned independent requirements to be created in the order liveCache. These anonymous demands form the basis of SNP, or PP/DS, where BOM explosion, capacity planning, and sourcing are carried out for the complete supply network.

??After feasibility of the planned sales quantities in SNP or PP/DS has been checked, the results can be transferred back to Demand Planning. Macros are used to analyze the differences between the demand plan and feasible quantities and alerts are generated if large differences occur.

Conclusion
Conclusion
Conclusion You are now able to: ? Define the basic concepts of Demand Planning and its

You are now able to:

? Define the basic concepts of Demand Planning and its integration with other APO components

? Describe the basic architecture of Demand Planning within APO

? SAP AG 2001

InfoCubes
InfoCubes

Contents:

? Administrator Workbench

? InfoCubes defined

? Creating InfoCubes

? Settings to load data to InfoCubes

? SAP AG 2001

Unit Objectives
Unit Objectives
? Describe the tasks and functions of the Administrator Workbench ? ?
?
Describe the tasks and functions of the
Administrator Workbench
?
?
tasks and functions of the Administrator Workbench ? ? At the conclusion of this unit, you

At the conclusion of this unit, you will be able to:

Describe how InfoCubes, characteristics, and key figures are set up

Describe the methods used to populate InfoCubes with data from R/3, Excel, and BW

? SAP AG 2001

Course Overview Diagram
Course Overview Diagram
111 2 2 3 33 4 44 555 666 777 8 88 999 Conclusion
111
2
2
3 33
4 44
555
666
777
8 88
999
Conclusion

Course Overview

22
22
44 555 666 777 8 88 999 Conclusion Course Overview 22 InfoCubes Configuration Planning Books and

InfoCubes

Configuration

Planning Books and Macros

Interactive Planning

Forecasting

Promotions & Lifecycle Planning

Mass Processing

? SAP AG 2001

Business Scenario ? In preparation for the use of demand planning, the Precision Pump Company
Business Scenario
? In preparation for the use of demand planning, the
Precision Pump Company will create the data
structures that will store the historical data
? The data structures will then be populated with
actual data
? SAP AG 2001
Demand Planning
Demand Planning

Aggregated actual data

Aggregated actual data
? Incoming order value ? Quantities ? Values ? POS data ? Nielsen / IRI
? Incoming order
value
? Quantities
? Values
? POS data
? Nielsen / IRI data
? SAP AG 2001
Location Product hierarchy
Location
Product hierarchy
/ IRI data ? SAP AG 2001 Location Product hierarchy R/3 Excel Non-SAP system Future demand

R/3

Excel

Non-SAP system

Future demand

forecast

Future demand forecast
? Statistical forecasting ? Collaborative forecasting ? Promotions
? Statistical forecasting
? Collaborative forecasting
? Promotions
Sold-to party Sales organization Region
Sold-to party
Sales organization
Region

??Administrator Workbench is the tool you use to create InfoObjects and InfoCubes, and to load data from a source system to the InfoCubes. APO Release 3.0 contains the complete Business Information Warehouse (BW), Release 2.0.

??You use InfoCubes to store actual data and archive old planning data. If you have an external data warehouse such as the SAP Business Information Warehouse (BW), you transfer data relevant for planning to the Demand Planning InfoCubes (DP data mart).

??Aggregated actual data can be extracted from the R/3 system in exactly the same way as it can be imported from BW, Excel, and legacy systems.

??POS (Point of Sales) data is consumer sales data. This can be procured from firms like Nielsen or IRI (Information Resources Inc.).

Extracting Transaction Data
Extracting Transaction Data
InfoCubes Update rules InfoSource Transfer rules Transfer rules Transfer Transfer structure structure Transfer
InfoCubes
Update rules
InfoSource
Transfer rules
Transfer rules
Transfer Transfer structure structure
Transfer Transfer structure structure
Transfer Transfer structure structure
Transfer Transfer structure structure
Transfer Transfer structure structure
Transfer Transfer structure structure
Extraction Extraction source source structure structure
Transaction data
Transaction data
OLTP System 1
OLTP System 2
DataSource

? SAP AG 2001

??A DataSource is an infrastructure which allows information to be transported between OLTP systems and the APO Data Mart. This infrastructure consists of various DDIC structures, which have specific transformation rules between one another. DataSources thus regulate the data flow from the extraction source structure in the source system to the communication structure in the SAP BW, which then provides the data. DataSources can provide both transaction data (this data is stored in InfoCubes), and master data (attributes, texts, and hierarchies - this data is stored in separate transparent tables). DataSources for transaction data and master data have almost an identical structure.

??DataSources describe how many pieces of information are available concerning a particular business transaction or transaction type (such as Cost Center Accounting). There are therefore many DataSources in an operative SAP BW environment that describe the individual activities within the applications to be analyzed.

??When a DataSource is generated, the transfer structure, and communication structure are generated in the APO Data Mart system. Transfer structures always exist as a pair in both a source system, and the associated APO Data Mart system. Data is transported in its original application format from a source system into an APO Data Mart, via the transfer structure. From there transformation rules are used to transfer the data to the communication structure of the InfoSource. The communication structure is independent of the source system and contains all the InfoSource fields that it represents in the APO Data Mart.

Administrator Workbench
Administrator Workbench

? Central tool for maintaining

? Source systems of aggregated order data (R/3, Excel, BW, non-SAP systems)

? InfoAreas

? InfoObjects (characteristics and key figures)

? InfoSources

? InfoCubes

? Data load scheduling and monitoring

? Used by APO and BW

? SAP AG 2001

??The Administrator Workbench is the central location for maintaining InfoCubes, InfoObjects, and all system extraction tools for retrieving external data.

??The APO data mart uses the same extraction tools as SAP's BW; so it has the same capability to tie together R/3 and non-R/3 systems, other data warehouses, and application data files, as well as, use third party extraction tools.

InfoObjects and InfoObject Catalogs
InfoObjects and InfoObject Catalogs

CharacteristicsInfoObjects and InfoObject Catalogs ? Texts and attributes ? Hierarchies ? Navigation attributes ? Specific

? Texts and attributes

? Hierarchies

? Navigation attributes

? Specific characteristic types:

?Time characteristics such as "fiscal year" Time characteristics such as "fiscal year"

?Unit characteristics such as "currency" or "local currency" Unit characteristics such as "currency" or "local currency"

such as "currency" or "local currency" Key figures: numeric fields in amounts and quantities that

Key figures: numeric fields in amounts and quantities that are constantly being updated (such as "turnover", and "sales quantity")

? Values / quantities

? Currency / units of measure

InfoObject Catalogs? Values / quantities ? Currency / units of measure ? Organize characteristics and key figures

? Organize characteristics and key figures

? SAP AG 2001

??'InfoObject' is the gener ic term for the key figures and characteristics of the APO DataMart. It comes with both standard BW InfoObjects, and standard APO InfoObjects (starting with '9A'). When you are creating your own InfoObject, you can decide whether to create an APO InfoObjec t, or a BW InfoObject. For characteristics it is not important whether you create APO characteristics, or BW characteristics. For key figures, you should create APO key figures if you will want to fix values or quantities to this key figure at a later stag e.

??InfoCatalogs can be user-defined. They are used to organize characteristics and key figures.

??Navigation attributes are used for grouping and selecting actual and planning data. Typical navigation attributes are for example, MRP controller, or customer group who do not represent a separate planning level but are used for grouping.

InfoArea
InfoArea

? InfoAreas are user-defined work areas used to maintain, monitor, and organize:

? InfoObjects

? InfoCubes

? Update rules

? InfoCube content queries

InfoArea Key figure Catalog Characteristic Catalog InfoCubes InfoObjects
InfoArea
Key figure
Catalog
Characteristic
Catalog
InfoCubes
InfoObjects

? SAP AG 2001

??Within the Business Information Warehouse, InfoAreas are used to group objects:

??Each InfoCube is assigned to an InfoArea. ??InfoObjects can also be assigned to different InfoAreas via InfoObject catalogs.

Data Structure: InfoCubes
Data Structure: InfoCubes
Aug. Sept. W32 W33 W34 W35 W36 W37 W38 W39 W40 W41 time series Regions
Aug.
Sept.
W32
W33
W34
W35
W36
W37
W38
W39
W40
W41
time series
Regions
Product
Product hierarchy
Period
Regions

? SAP AG 2001

??InfoCubes are the data repository for Demand Planning.

??The architecture of an InfoCube is based on what's known as a "star schema" which consists of fact tables and dimension tables.

??The multidimensional nature of an InfoCube allows the user to slice and dice the data in many different ways.

InfoCube
InfoCube

? Central data store for reports, evaluations and data used in forecasting

? Contains two types of InfoObjects

? Key figures

? Characteristics (grouped in dimensions)

? Key figures ? Characteristics (grouped in dimensions) ? 1 fact table with multiple dimension tables
? Key figures ? Characteristics (grouped in dimensions) ? 1 fact table with multiple dimension tables

? 1 fact table with multiple dimension tables

? 3 dimensions are predefined by SAP ?Time ?Unit ?Data packet

? SAP AG 2001

table with multiple dimension tables ? 3 dimensions are predefined by SAP ? Time ? Unit

??Key figures are currency, quantity or number fields such as sales revenue or sales quantity.

??A characteristic is an object on which you aggregate and report data. Examples of characteristics are region, product, customer (unit characteristics) and month, week, day (time characteristics).

??When deciding which characteristics to include in your InfoCube for Demand Planning, consider that:

??Characteristics define the levels to which you can aggregate data

??Characteristics define the levels at which you can maintain data

??In addition to the three dimensions that are generated automatically (time, unit, Info Package), your InfoCube contains user-defined dimensions. In Demand Planning, one of these user-defined dimensions is "version".

??Create BW InfoCubes only, as APO InfoCubes are only used internally.

Fact Table
Fact Table

? A fact is a figured quantity such as quantity, revenue, discount, sales overhead. It is a key figure used in evaluations generated by the Data Warehouse.

? The fact table below shows the table design used in the data mart. Fact tables usually contain numeric data.

P

C

T

Order qnt. Turnover

Forecasts

Promotions

500.000 250 $ 500 20
500.000 250 $ 500 20

500.000250

250

$

500

20

100.000 50 $ 100 5
100.000 50 $ 100 5

100.00050

50

$

100

5

… … …
… … …

… …

Fact Table

? SAP AG 2001

??The fact table contains the key figure data for each unique combination of characteristic values. The referencing of the fact table takes place using the artificially entered dimension key (DIM-ID). As artificial keys are formed for the connection between the dimension and fact table, changes to the master data table can take place relatively problem-free, without having to rebuild the (natural) key every time. In the evaluation, a resulting quantity is first formed by the selections in the dimension tables. This quantity is then selected directly by the artificial key from the fact table.

Dimensions
Dimensions

? Dimensions are used to group characteristics logically

? A dimension table contains a primary key, a dimension number, and characteristics

Customer dimension

C

Customer #

Region

13970522 West

13970522

West

Product Service Line dimension

Time dimension

P

Product #

Product group …

T

Time

Fiscal year

2101004 Display 10 1998

2101004

Display

2101004 Display 10 1998

10

1998

? SAP AG 2001

??Dimensions are a way to organize the characteristics of an InfoCube.

??From a technical point of view, the characteristics of the dimension table form the "edges" of the data cube that is stored as the InfoCube in the data mart. The dimensions are connected with the fact table using the DIMs. The data in the fact table is accessed by selecting characteristics and their characteristic values from the dimension tables and by generating a corresponding SQL statement that is used to access the fact table.

Star Schema
Star Schema
? Combinations of Fact and Dimension Tables Customer dimension C Customer # Region … 13970522
? Combinations of Fact and Dimension Tables
Customer dimension
C
Customer #
Region
13970522
West
P C
T
Order qnt.
Turnover
Forecasts
Promotions
250
$ 500.000
500
20
50
$ 100.000
100
5
Fact table
P
Product #
Product group …
T
Time
Fiscal year
2101004
Display
10
1998
Product Service Line dimension
Time dimension

? SAP AG 2001

??InfoCubes produce a multi-dimensional data model on the database server of the APO data mart. In this way, the facts are collected in separate fact tables and the dimensions grouped into separate dimension tables. Both table types are connected with one another in a relational way. Individual dimension characteristic values can in turn be subdivided by master data tables. In this way, master data, classification and hierarchy data tables as well as dimension tables are finally grouped in a star - like formation around one central fact table. During the analysis, first the data from the surrounding smaller tables is collected together in order to reduce the reading time in the large fact table.

??This database schema "Star Schema" guarantees high reporting efficiency and provides a flexible solution that can be easily adjusted to changing business requirements.

??When creating an InfoCube you concentrate on the key figures and characteristics that you require in planning. You must then group together your characteristics in dimensions, including a time dimension, and a quantity dimension. Using your entries the system automatically generates a Star Schema in the database.

Source System
Source System

? All systems which provide data for extraction into the data mart

? Types of source system

? SAP R/2 Systems

? SAP R/3 Systems (From Release 3.0D)

? External systems (third party tools or files)

? Data is extracted and transformed using the InfoSource for the source system

? SAP AG 2001

??Each source system represents a logical system.

??In a test system, you can use the same source system several times to upload data; you don't need to create a source system every time you upload data.

??Each source system represents one physical source of data.

Data Extractors: LIS Example
Data Extractors: LIS Example

TypesTypes ofof extractorextractor

Extractors: LIS Example TypesTypes ofof extractorextractor Application-specificApplication-specific

Application-specificApplication-specific

ApplicationApplication non-specificnon-specific
ApplicationApplication non-specificnon-specific
GenericGeneric extractorsextractors Database table/view SAP Query
GenericGeneric
extractorsextractors
Database
table/view
SAP Query

Data sourceextractorsextractors Database table/view SAP Query BWBW ContentContent extractorsextractors FI CO HR LO

BWBW ContentContent extractorsextractors
BWBW ContentContent
extractorsextractors
FI CO HR LO Cockpit Transparent Table
FI
CO
HR
LO Cockpit
Transparent
Table
GenericGeneric extractorsextractors LIS FI SL CO PA
GenericGeneric
extractorsextractors
LIS
FI SL
CO PA
Transparent Table
Transparent
Table
Enhancements Enhancements
Enhancements Enhancements

Enhancements

Enhancements

Enhancements Enhancements
Enhancements Enhancements

? SAP AG 2001

??Transaction data that is transferred to InfoCubes via extractors can come from a number of different modules. Multiple extraction mechanisms are necessary for this purpose, and for historical development reasons. The next few slides will provide an example of transaction data extraction from LIS.

Updating Information Structures
Updating Information Structures
APO System InfoCubes Update rules Communication structure Communication structure Transfer rules TransferTransfer
APO System
InfoCubes
Update rules
Communication structure
Communication structure
Transfer rules
TransferTransfer structurestructure
Transfer structure
Transfer structure
R/3 OLTP
Transfer structure
Transfer structure
Transfer structure
Transfer structure
Extraction source structure
Extraction source structure
Extraction source structure
Extraction source structure
S5nn
S5nnBIW1 S5nnBIW2
S5nn
S5nnBIW1 S5nnBIW2
OLTP 1: LIS info structure
OLTP 1: LIS info structure
OLTP 2: LIS info structure
OLTP 2: LIS info structure

? SAP AG 2001

??Above you see the flow of data from the source system into the Demand Planning data mart. You carry out this transfer using tools in the Admin Workbench.

LIS Extraction
LIS Extraction
LIS Extraction 8. Load transaction data into the InfoCube 7. Define loading process 6. Maintain InfoCube
LIS Extraction 8. Load transaction data into the InfoCube 7. Define loading process 6. Maintain InfoCube
LIS Extraction 8. Load transaction data into the InfoCube 7. Define loading process 6. Maintain InfoCube
8. Load transaction data into the InfoCube 7. Define loading process
8. Load transaction data into the InfoCube
7. Define loading process
6. Maintain InfoCube and update rules 5. Maintain transfer rules 4. Maintain communication structure 3.
6. Maintain InfoCube and update rules
5. Maintain transfer rules
4. Maintain communication structure
3. Replicate/assign DataSource
2. Generate DataSource in the OLTP
1. Set up LIS environment

? SAP AG 2001

??The following scenario provides an example of how actuals are loaded onto the APO system from an R/3 information structure. This is simply one of the ways the data mart can be configur ed for Demand Planning. You can find details on the APO Administrator Workbench in the SAP Business Information Warehouse documentation under Administrator Workbench.

??This procedure is valid from R/3 release 3.1H.

Setting up the LIS Environment
Setting up the LIS Environment
BWBW integrationintegration forfor LISLIS infoinfo structuresstructures Information structure Display settings S5nn
BWBW integrationintegration forfor LISLIS infoinfo structuresstructures
Information structure
Display settings
S5nn
Set up LIS environment
Generate DataSource
Delete environment/DataSource
Delta update in LIS
Activate/deactivate
Generate update

? SAP AG 2001

??You must first define several settings so that LIS info-structures can be used as source tables.

??You first have to configure the LIS environment for the associated info structures.

??To do this, choose 'Administrator Workbench' => 'Source Systems' => (choose appropriate source '

system and click the right mouse button) 'Customizing for extraction

=> 'Logistics' => 'Logistics Information System' => 'Connect information structures'.

=> 'Generated DataSources'

??Alternatively, you can call up transaction 'SBIW' in the R/3 system, or start report 'RMCSBIWC' in the menu.

Process: First Delta Update
Process: First Delta Update
R/3 OLTP system APO S5nn InfoSource 2LIS_01_S5nn LIS Update Process S5nnBIW1S5nnBIW1 TMCBIW Control table
R/3 OLTP
system
APO
S5nn
InfoSource
2LIS_01_S5nn
LIS
Update
Process
S5nnBIW1S5nnBIW1
TMCBIW
Control table
S5nnBIW2
BIW Status
'2'
R
Delta update
1.

? SAP AG 2001

??If you start the delta update from OLTP into APO, tables S5nnnBIW1 and S5nnBIW2 are used.

??The info structure is active in OLTP. Data from S5nnBIW1 is loaded into the BW for the first delta update.

??During the first delta update in APO, the LIS update process in the OLTP system updates both the LIS info structure itself, and the table S5nnBIW2 that is then used for the second delta update request in the BW.

??At the start of every delta update request, table S5nnBIW1 is automatically exchanged with table S5nnBIW2 to avoid data inconsistencies during upload. During a delta update in the BW, the indicator "BIW status" in table "TMCBIW" is automatically switched from 1 (for table S5nnBIW1) to 2 (for table S5nnBIW2).

??The data from a delta table remains in the table until the next delta upload, so that a reload is possible up to that point.

Summary of Source System and InfoCubes
Summary of Source System and InfoCubes
InfoArea 1 InfoArea 2 InfoCube InfoCube Update rules InfoSource Communication structure Transfer structure Source
InfoArea 1
InfoArea 2
InfoCube
InfoCube
Update rules
InfoSource
Communication structure
Transfer structure
Source System
R/3
Excel
Legacy
BW

? SAP AG 2001

??Above you see the flow of data from the source system into the Demand Planning data mart. You carry out this transfer using tools in the Admin Workb ench.

??The data is passed from the source system to the InfoSource in the DP data mart via an extract structure. In the extract structure, data from an R/3 application, for example, is prepared for the InfoSource.

??An InfoSource is a provider structure in the Admin Workbench. It contains data that from a business point of view logically belongs together. The InfoSource metadata defines which InfoObjects are contained in the InfoSource, as well as the descriptions and technical information of the InfoObjects. In the Admin Workbench you assign the InfoSource to an application component.

??The system generates the transfer structure and the communication structure from the InfoSource metadata. The data is passed through these two structures into the InfoCube from the InfoArea.

InfoSource
InfoSource

? Supplies the data mart with data from a source system that belongs logically together from a business point of view

? Types of InfoSources:

? Transaction data

? Master Data, texts, hierarchies

? Transfer structures and communication structures are generated from the InfoSource

? SAP AG 2001

??The InfoSource allows the APO system to:

??transfer the extracted data from the extraction structure into the SAP R/3 OLTP

??transfer the data to the APO transfer structure using the OLTP transfer structure

??convert the data using the APO transfer rules, and

??transfer the data to the APO communication structure.

??The InfoSource prepares the data to be stored permanently in the InfoCube.

??For the delta upload, in addition to the LIS info structure, two more tables are needed as extractors in the OLTP system.

Update Rules
Update Rules

? Link InfoSource to the InfoCube

? Map the characteristics and key figures between the InfoSource and the InfoCube

? Two methods:

InfoArea 1 InfoCube
InfoArea 1
InfoCube

? Based on key figures from the communication structure (standard)

? Using a routine

Communication Communication structure structure
Communication Communication structure structure

? SAP AG 2001

??A number of operations can be performed within the update rules.

??InfoObjects can be transferred from the communication structure into an InfoCube.

??Constants can be used for InfoSource actuals.

??More complex calculations can be made using ABAP/4 routines. The ABAP editor is directly embedded in the update rule maintenance - a User Exit does not need to be defined.

??Routines can be used to access customer -specific tables and APO-generated tables (master data

tables, hierarchy tables

changes; all that requires maintaining are the table contents.

).

Because of this, update rules do not need to be used for fast information

??Currency conversion for key figures.

Info Package
Info Package
InfoSource
InfoSource

?

Info Package

? Control parameters for loading data

? Control of data target

? Controlling the InfoCubes to be updated

? Update parameters

? Scheduling & monitoring of jobs

? SAP AG 2001

??An Info Package is created for each InfoSource.

??The Info Package contains all of the upload process control parameters as well as appropriate scheduling and monitoring functions.

??From the Info Package you can control which InfoCubes are populated in each load.

Data Mart: Unit Summary
Data Mart: Unit Summary
Data Mart: Unit Summary ? SAP AG 2001 You are now able to: ? Describe the

? SAP AG 2001

You are now able to:

? Describe the tasks and functions of the Administrator Workbench

? Describe how InfoCubes, characteristics, and key figures are set up

? Describe the methods used to populate InfoCubes with data from R/3, Excel, and BW

Exercises Unit: InfoCubes Topic: Administrator Workbench At the conclusion of this exercise, you will be
Exercises Unit: InfoCubes Topic: Administrator Workbench At the conclusion of this exercise, you will be
Exercises Unit: InfoCubes Topic: Administrator Workbench At the conclusion of this exercise, you will be

Exercises

Unit:

InfoCubes

Topic:

Administrator Workbench

At the conclusion of this exercise, you will be able to:

?? Identify the dimensions that are defined for an InfoCube

?? Identify the characteristics that are defined for an InfoCube

?? Identify the key figures and data types that are defined for an InfoCube

The course scenario is as follows:

Sales data from customer orders and invoices has been updated in the R/3 information structure S628. These data records have been transferred to the APO SALES InfoCube and are to be used as the actual data for demand planning.

You will be allocated a group number ## for all exercises in this course. Ask your instructor.

1-1

Explore the structure of the SALES InfoCube in the Administrator Workbench .

1-2

What dimensions have been defined in the SALES InfoCube and which characteristics are assigned to each individual dimension?

In the following table, note down the dimensions and characteristics from the SALES InfoCube:

Dimension

Dimension Characteristics
Dimension Characteristics
Dimension Characteristics
Dimension Characteristics
Dimension Characteristics
Dimension Characteristics

Characteristics

Dimension Characteristics
Dimension Characteristics
Dimension Characteristics
Dimension Characteristics
Dimension Characteristics
Dimension Characteristics

1-3

What key figures are defined for the SALES InfoCube? What data type do they have?

Key figure

Long description

Key figure type

Data type

1-4

Display the contents of the SALES InfoCube and analyze the characteristic combinations and entries for the key figures.

1-5

Call up the BW Business Explorer Analyzer, to evaluate the data that is saved in the SALES InfoCube. Log on to the APO system and open the query SALES DATA for the SALES InfoCube. Exit the query and Business Explorer Analyzer without saving.

Solutions Unit: InfoCubes Topic: Administrator Workbench You will be allocated a group number ## for

Solutions

Unit: InfoCubes Topic: Administrator Workbench

You will be allocated a group number ## for all exercises in this course. Ask your instructor.

1-1

Explore the structure of the SALES InfoCube in the Administrator Workbench .

Demand Planning? Workbench

Environment ?

Current Settings ?

Administrator

You are now in the Modeling screen for Data Targets

Expand the SALES InfoArea by pressing the “+” in front of the InfoArea

Right click on the SALES InfoCube: Display data model

 

Stay in the Administrator Workbench for steps 1-2 to 1 -4.

1-2

What dimensions have been defined in the SALES InfoCube and which characteristics are assigned to each individual dimension?

Dimensions are represented by the three triangle icon.

When you expand a dimension, you see the characteristics assigned to it

In the following table, note down the dimensions and characteristics from the SALES InfoCube:

Dimension

Characteristics

Planning version

APO Planning version

Sales

Sales organization, division, sold-to party

Product

Product hierarchy, APO product, APO location

Time

Calendar year/month

Data packet

Change run ID, record type, request ID

Unit

Unit of measure, currency key

1-3

What key figures are defined for the SALES InfoCube? What data type do they have?

Right click on the SALES InfoCube: Change

Choose the <Key figures> tab.

Choose <Detail view>.

Key figure

Long description

Key figure

Data type

type

INORDQTY

Incoming order qty

Quantity

QUAN

INORDVAL

Incoming order value

Amount

CURR

INVQTY

Invoiced sales qty

Quantity

QUAN

INVVAL

Invoiced sales value

Amount

CURR

1-4

Display the contents of the SALES InfoCube and analyze the characteristic combinations and entries for the key figures

Right click on the SALES InfoCube: Manage

Select the <SALES> InfoCube at the top of the screen

Choose <Display Contents> or F6

Choose <Field selct. for output>

Select the characteristics that you want to analyze

Do not select SID characteristics that contain the dimension table internal key

Choose <Execute>

Choose <Execute>

Review the data in your InfoCube.

Exit the Administrator Workbench

1-5

Call up the BW Business Explorer Analyzer, to evaluate the data that is saved in the SALES InfoCube. Log on to the APO system and open the query SALES DATA for the SALES InfoCube.

To call up the BW Business Explorer Analyzer: Start? Business Explorer Analyzer

Activate the macros and press the “open” icon in the blue Business Explorer tasks bar.

Log on to your APO system.

Select the “Queries” pushbutton.

Expand the SALES InfoArea, and select the query SALES DATA for the SALES InfoCube. Press OK.

Programs ?

BW ?

SAP

You are given an aggregated view of the invoiced sales quantity and invoiced sales value of the three sales organizations. By clicking the right mouse button over key figures or characteristics you can display data in terms of products, sold -to parties, or months.

Exit the query without saving, and log out of the SAP Business Explorer Analyzer.

Demand Planning Configuration
Demand Planning Configuration

Contents:

? Planning object structures

? Characteristic Value Combinations

? Planning Areas

? Proportional Factors

? Releasing the Demand Plan

? SAP AG 2001

Unit Objectives
Unit Objectives
? ? ? ? ? ?
?
?
?
?
?
?
Unit Objectives ? ? ? ? ? ? At the conclusion of this unit, you will

At the conclusion of this unit, you will be able to:

Configure planning area settings Create planning networks Provide an explanation of consistent planning Describe alternative disaggregation methods Maintain proportional factors Release sales data

? SAP AG 2001

Course Overview Diagram
Course Overview Diagram
111 2 22 3 3 4 44 555 666 777 8 88 999 Conclusion
111
2 22
3
3
4 44
555
666
777
8 88
999
Conclusion

Course Overview

4 44 555 666 777 8 88 999 Conclusion Course Overview InfoCubes 33 Configuration Planning Books

InfoCubes

33
33

Configuration

Planning Books and Macros

Interactive Planning

Forecasting

Promotions & Lifecycle Planning

Mass Processing

? SAP AG 2001

Business Scenario ? After the Precision Pump Company has created its InfoCubes for saving actual
Business Scenario
? After the Precision Pump Company has created its
InfoCubes for saving actual data, they now have to
define the planning areas, and make the
characteristics, and key figures available for
planning.
? SAP AG 2001
Demand Planning Configuration
Demand Planning Configuration

Planning table

Demand Planning Configuration Planning table Planning book Characteristics Key figures Planning area Characteristics:

Planning book

Characteristics
Characteristics
Key figures
Key figures

Planning area

Planning book Characteristics Key figures Planning area Characteristics: • Region • Sales area •

Characteristics:

Region

Sales area

Product hierarchy

Sold-to party

Location

? SAP AG 2001

Key figures:

Demand Plan

Actual sales

Overrides

Promotions

Production quantity

Version:

000 Active version

Sim1 Simulation 1

Sim2 Simulation 2

??In Demand Planning and Supply Network Planning, data is divided into planning areas, and subdivided into versions. Consequently, the data that you save in planning version 1, planning area 1 does not overwrite the data in planning version 1, planning area 2.

??The planning area contains characteristics, and key figures for planning, and must be initialized for every planning version.

??A key figure is a numerical value that is either a quantity or a monetary amount; for example, projected sales value in dollars or projected sales quantity in pallets.

??Characteristics are the objects by which you aggregate, disaggregate and evaluate business data.

??Key figure data can be read from different InfoCubes or time series objects.

??Key figure planning data is stored in time series objects in the liveCache.

??To save planning data in an InfoCube, create an extraction structure for the planning area, and connect it to the InfoCube.

Assigning Characteristics to a Planning Area
Assigning Characteristics to a Planning Area

Planning table

Assigning Characteristics to a Planning Area Planning table Planning book Characteristics Key figures Planning area Key

Planning book

Characteristics
Characteristics
Key figures
Key figures

Planning area

Key figures
Key figures
Version
Version
Characteristics
Characteristics

? SAP AG 2001

??Demand Planning characteristics define the levels on which the demand plans are created, changed, aggregated, and disaggregated. For example, your Master Data could include all the products, product families, regions, and customers that your company is going to plan with APO Demand Planning, plus all the appropriate combinations of these (for example, which customers buy which products, in which regions). You map these levels in a non-hierarchical selection tree. From a technical point of view, specify which characteristic values can be planned for the characteristics in your planning area. Demand Planning or Supply Network Planning master data includes all the allowed values of a characteristic. These are called the characteristic values. Characteristic values are specific names. Thus the characteristic "Location", for example, can have the values London, Delhi, or New York.

??You can only use a planning area that is shared by both Demand Planning, and Supply Network Planning, if Demand Planning in your company is done on a "product" level or "product plus location" level. If Demand Planning is done on other levels, such as on a brand or regional level, separate planning areas are required. A planning area used for Supply Network Planning can only contain Standard SNP characteristics.

??Characteristics that are used both in Demand Planning, and Supply Network Planning can be used in one planning area.

Master Planning Object Structure
Master Planning Object Structure

Planning area

Characteristics

Aggregates
Aggregates

Aggregates

Aggregates

Master planning object structure

SNP characteristics DP characteristics

Characteristic value combinations Navigation attributes
Characteristic value combinations
Navigation attributes

? SAP AG 2001

structure SNP characteristics DP characteristics Characteristic value combinations Navigation attributes ? SAP AG 2001

??A master planning object structure contains characteristics that can be planned for one or more planning areas. In Demand Planning characteristics can be either standard characteristics and/or characteristics that you created in the Administrator Workbench. Characteristics define the levels to which you can plan and save data. Particular characteristics are required for Supply Network Planning, characteristics-based planning, and als o dependent demand forecasting. These characteristics can be included in the master planning object structure.

??For demand planning, the InfoCube must be used to generate characteristic combinations for the planning area.

??The aggregates in APO are not identical to those in the Business Information Warehouse (BW), but they do have the same purpose: they access data quickly and thus improve performance. SAP recommends the use of aggregates within Demand Planning.

??An APO aggregate consists of a subset of the characteristics contained within the master planning object structure. Creating and working with aggregates is optional. Data is always saved at the lowest detailed level. If aggregates do exist, the system saves the planning data both at the defined aggregate level and at the lowest detailed level. Data is saved consistently in duplicate. This means that the total of details is the same as the aggregate value.

??In the APO Administrator Workbench you create characteristics as navigation attributes. These should be used for selecting and navigation but not as planning levels. You then assign these attributes to the characteristics they belong to. This is how you can assign the attributes "sales employee", and "priority", for example, to the characteristic "customer " during definition of the InfoObject "Customer".

Characteristic Value Combinations
Characteristic Value Combinations

Customer dimension

C Customer Region Baker West
C Customer
Region
Baker
West

Product dimension

P

Product

Product group

P-102 Pumps

P-102

Pumps

dimension P Product Product group P-102 Pumps Which customer and product combinations should be planned?

Which customer and product combinations should be planned?

? SAP AG 2001

??Each characteristic value combination represents a planning object in Demand Planning.

??From a technical point of view, each unique combination of characteristic values in each dimension is represented by a key.

Create Characteristic Value Combinations
Create Characteristic Value Combinations

? Create single characteristic value combinations

? Delete single characteristic value combinations

? Generate characteristic value combinations

? Analyze characteristic value combinations

? SAP AG 2001

Customer dimension Fact table:
Customer dimension
Fact
table:

Product dimension

??Characteristic value combinations define the valid relationships between characteristic values and form the basis for aggregation/disaggregation of key figure values. There are two ways of creating characteristic value combinations:

??Automatically, by generating characteristic value combinations based on existing data from an InfoCube. With this option, the system generates all the new combinations that it finds in the horizon specified. You can plan automatic generation periodically so that new characteristic value combinations are added each time but old ones are never deleted.

??Individually, by completely defining characteristic values (this creates one data record)

??If you want to create multiple characteristic value combinations (for new products, for example), it is often a good idea to maintain the characteristic value combinations in Excel, then load them into an InfoCube, and start to generate the characteristic value combinations for this InfoCube.

??Realignment also provides possibilities for reorganizing actual data and characteristic value combinations. For more information, read SAPnet R/3 frontend note 360935, and access report /SAPAPO/TS_REALIGNMENT via transaction SE38.

??The result of the creation process is a network of planning objects.

Basic Parameters for Planning Area
Basic Parameters for Planning Area

Planning area

Basic Parameters for Planning Area Planning area General parameters • Base unit of measure • Base

General parameters

Base unit of measure

Base currency

Exchange rate type

? SAP AG 2001

Storage buckets profile

Day

Week

Calendar year/month

Quarter

Year

Posting period

??Planning data is stored in the base unit of measure and the base currency.

??All the products you want to plan in a planning area need to be converted into the base unit of measure at least once.

??A storage buckets profile defines the periods over which data (based on a given planning area) in Demand Planning, and Supply Network Planning will be saved. You need to have a storage buckets profile before you can create a planning area.

??To create a storage buckets profile, choose Periodicities for Planning Area from the Current Settings in Demand Planning or Supply Network Planning. Make the following specifications in a storage buckets profile:

??one or more periodicities where you would like to save data

??a typical valid time period Horizon (you set the actual horizon when creating the time series for the planning version)

??If data is saved with a special time stream (such as factory calendars), enter a time stream ID (entry optional). The time stream must be as long as or longer than the horizon. It may not be shorter.

??If at the start of a planning horizon data is to be saved in a fixed number of rolling days, then in a larger time bucket, specify the number of days (specification optional).

??You can for example store your actual data in the InfoCube on a monthly time basis and enter the planning data in the planning area within a more detailed time buckets profile, such as weekly.

Assigning Key Figures to a Planning Area
Assigning Key Figures to a Planning Area

Planning table

Assigning Key Figures to a Planning Area Planning table Planning book Planning area Characteristics Key figures

Planning book

Key Figures to a Planning Area Planning table Planning book Planning area Characteristics Key figures Master

Planning area

Characteristics

Key figures

Planning book Planning area Characteristics Key figures Master planning object structure SNP characteristics DP

Master planning object structure

SNP characteristics DP characteristics

Aggregates

Time Time series series objects objects liveliveCacheCache
Time Time series series
objects objects
liveliveCacheCache

? SAP AG 2001

??Key figure data can be read from different InfoCubes or time series objects. ??Key figures are only stored in time series objects in the liveCache.

Actual and Planning Data
Actual and Planning Data
Planning area Actual key figures Forecast Planning key figures Time series Time series Forecasts objects
Planning area
Actual key figures
Forecast
Planning key figures
Time series
Time series
Forecasts
objects objects
to SNP
liveliveCacheCache
? Incoming order value
? Quantities
Planned independent
requirements for
SNP and PP/DS
R/3
? Values
Excel
Order Order
objects
objects
liveliveCacheCache
Administrator Workbench
?
SAP AG 2001

??Key figure data can be read from different InfoCubes or time series objects.

??Key figure planning data is stored in time series objects in the liveCache.

??To store planning data in the database (in an InfoCube), create an extraction structure for the planning area. This extraction structure appears as a DataSource for the APO source system in the Administrator Workbench. You link this DataSource with the InfoCube via an InfoSource. For more information read notes 373756, and 374534.

Create Proportional Factors
Create Proportional Factors

? Version dependent

? Period specific (optional)

? Storage in key figure APODPDANT

? Maintenance in planning table

Product family

70 % Product A
70 %
Product A
30 % Product B
30 %
Product B
50 % ? ?
50 %
? ?

Plant A

50 %? Maintenance in planning table Product family 70 % Product A 30 % Product B 50

Maintenance in planning table Product family 70 % Product A 30 % Product B 50 %

Plant B

? SAP AG 2001

??Constant proportional factors are one way of executing disaggregation. Constant proportional factors are derived from historical data or occasionally past planning data. Disaggregation can be executed in different ways for different key figures.

??The proportional factors define the percentage rates at which aggregated data is disaggregated to the members.

??Enter the version, key figure and horizon to perform an automatic calculation of proportional factors. The system first calculates the entire quant ity (value) for the key figure in the specified horizon. The quantities (values) of the individual members are then defined and the percentage calculated.

??You must then specify for which version, and which horizon the proportional factors are to be saved.

??If you select "detailed proportions", you can choose for example which historical periods should be saved for which future periods, for example, the proportions of June 99 based on the proportions of June 98 etc.

??You can also maintain the proportional factors interactively via the planning table.

Disaggregation Methods
Disaggregation Methods

The aggregated data is distributed to the members per period according to the following criteria:

 
S
S

Pro rata

According to member data, with no equal member data

 
P
P

Based on a different key figure

The disaggregation proportions are predefined via another key figure (for example, the APODPDANT key figure)

 
I
I

Pro rata / in case blank after another key figure

According to member data with no member data according to another key figure

?

SAP AG 2001

??Data is disaggregated using the procedure detailed above

??Generate constant proportional factors when you want to disaggregate the planning data in the following ways.

??Always based on the constant proportional factors

??Based on constant proportional factors, if there is no existing planning data

Pro Rata Disaggregation
Pro Rata Disaggregation
Total Region Customer Sales Sales Europe 350 700
Total
Region
Customer
Sales
Sales
Europe
350
700

Details

USA

Customer1

100

100

Europe

Customer1

150

300

USA

Customer2

50

50

Europe

Customer2

200

400

? SAP AG 2001

Disaggregation
Disaggregation

??The above slide illustrates how disaggregation is performed if you set key figure Sales to calculation type Pro rata.

??The data is disaggregated according to the distribution ratio that the system derives dynamically from the existing planned data. The proportional factors are not used with this disaggregation type.

??In this example, the data is distributed to customer 1 and customer 2 in region Europe based on the ratio 3:4 (150:200).

Disaggregation: APODPDANT Key Figure
Disaggregation: APODPDANT Key Figure
Total Region Customer Sales New sales Prop. factor Europe 350 700 0.5 Aggregation Disaggregation Details
Total
Region
Customer
Sales
New sales
Prop. factor
Europe
350
700
0.5
Aggregation
Disaggregation
Details

USA

Customer1

100

100

0.25

Europe

Customer1

150

350

0.25

USA

Customer2

50

50

0.25

Europe

Customer2

200

350

0.25

? SAP AG 2001

??The above slide illustrates how disaggregation is performed if you set key figure Sales to calculation type P with key figure APODPDANT.

??The data is disaggregated according to the proportional factors. In this example, customer 1 and customer 2 in region Europe have the same proportional factors (0.25), so the data is distributed equally between them.

??The proportional factors are percentage- based and held in the key figure APODPDANT. You can make the system calculate proportions for the key figure APODPDANT based on Actual_data.

Defining a Planning Area: Version
Defining a Planning Area: Version

Planning table

Defining a Planning Area: Version Planning table Planning book Characteristics Key figures Planning area Key figures

Planning book

Characteristics
Characteristics
Key figures
Key figures

Planning area

Key figures
Key figures
Planning version
Planning version
Characteristics
Characteristics

? SAP AG 2001

??In order to be able to save data for a planning area version, time series must be created for that version. The system creates time series in the liveCache for each characteristic value combination, and each key figure.

??If you have to re-initialize a planning area after actualizing your master data or extending the planning horizon, you must not delete the old time series objects before creating new objects. The system can see where new characteristic value combinations already exist, and only creates time series objects for the new master data time series objects.

Initializing Version Planning Area
Initializing Version Planning Area

APO Master data (model independent)

PPM

Active model

Model 1

Products

Transportation

lanes

Locations

Simulation

model

Transportation lanes Locations Simulation model Planning Version 1 version dependent master and

Planning Version 1

version dependent master and transaction data

Active Version 000

version dependent master and transaction data

Planning Version n

version dependent master and transaction data

Version n version dependent master and transaction data Planning area Characteristics Key figures ? SAP AG

Planning area

Characteristics

Key figures

? SAP AG 2001

??You initialize the planning area by right clicking on the planning area, and choosing Create time series objects.

??Enter the planning version plus the start and end date. You can re- initialize the planning area in rolling periods. This deletes "obsolete" periods, and adds new periods for the future.

??If you have to re-initialize a planning area after actualizing your master data or extending the planning horizon, you do not have to delete the old time series objects before creating new objects. The system is able to recognize where new characteristic value combinations already exist, and only creates time series objects for the new master data time series objects.

??You delete time series objects, for example, if you are working with five versions, but only want to keep two of them.

Version Management
Version Management

? Copy versions

? Delete versions

Planning area 1 Planning area 2 Characteristic allocation Version 1 Version 2 Key figures allocation
Planning area 1
Planning area 2
Characteristic
allocation
Version 1
Version 2
Key figures
allocation

? SAP AG 2001

??Each planning version (or DP version) is a separate set of data. You can display only one version at a time in int eractive planning. Different versions of the plan can be saved for archiving or comparison purposes.

??You can also copy demand planning versions using Version Management. A version number must first be created. After the version number is created, you can copy the data using the copy function.

??Both the version data and the version number are deleted when you delete using Version Management.

??Demand planning versions are 10 characters long and are alphanumeric.

??Different version management tools are provided for the versions you use in SNP and PP/DS.

Releasing the Demand Plan
Releasing the Demand Plan
Releasing the Demand Plan Demand Planning Time series objects live live Cache Cache Key figure Production

Demand Planning

Time series

objects

liveliveCacheCache

Key figure

Time series objects live live Cache Cache Key figure Production Planning Order objects live live Cache
Time series objects live live Cache Cache Key figure Production Planning Order objects live live Cache

Production Planning

Order

objects

liveliveCacheCache

Category (FA)

? Creating planned independent requirements with a time buckets profile

? Workdays are taken from the location shipping calendar

? Location split

? Product split

? Daily buckets profile when DP storage buckets profile does not contain any days

? SAP AG 2001

??If the forecast is completed in demand planning, release the forecasted amount to the liveCache as a planned independent requirement.

??To do this follow the path Demand Planning->Environment->Release to SNP

??The "add data" flag means that the released amounts will be added to planned individual requirements that may already exist. It is a good idea to use this setting if you want to release from multiple planning areas.

??If the "location" characteristic is contained in the DP planning area, the sales quantities are disaggregated to the locations automatically. If you have maintained the distribution of products to various locations in the location split table, the system will use the corresponding factors.

??You can, for instance, control distribution of a product group to members via product split. Product split is used when you want to remove characteristic 9AMATNR using extended characteristic selection.

??If the storage buckets profile from the DP planning area does not contain days, you can still split the sales quantities over days using the daily buckets profile. How this split is made depends on the settings in the SNP requirements profile in SNP 2 product master view.

Location Split
Location Split
?Product ?Product demand demand 40 % 40 % 20 %
?Product ?Product demand demand
40 %
40 %
20 %
Split ?Product ?Product demand demand 40 % 40 % 20 % In contrast to location level

In contrast to location level disaggregation in the planning area, a percentage split can be defined in location splits.

Define either generic or specific quotas for each product.

DC 1

DC 2

DC 3

? SAP AG 2001

??If the "location" characteristic is contained in the DP planning area, the sales quantities are disaggregated to the locations automatically. When you release it, you specify your product and location characteristics (such as 9AMATNR and 9ALOCNO), and the system releases the exact location product quantities planned.

??If you are using location split, you are not permitted to enter the location characteristic name, as allocation will be made according to that in the location split table.

??Product split will always be checked.

InfoCubes & Demand Planning: Unit Summary
InfoCubes & Demand Planning: Unit Summary
InfoCubes & Demand Planning: Unit Summary ? SAP AG 2001 You are now able to: ?

? SAP AG 2001

You are now able to:

? Configure planning area settings

? Create planning networks

? Explain consistent planning

? Describe alternative methods of disaggregation

? Maintain proportional factors

? Release sales data

Exercises Unit: Configuration Topic: Creating a planning object structure At the conclusion of this exercise,
Exercises Unit: Configuration Topic: Creating a planning object structure At the conclusion of this exercise,
Exercises Unit: Configuration Topic: Creating a planning object structure At the conclusion of this exercise,

Exercises

Unit:

Configuration

Topic:

Creating a planning object structure

At the conclusion of this exercise, you will be able to:

?? Create a planning object structure

?? Generate characteristic value combinations

?? Create and initialize a planning area

?? Calculate proportional factors

The course scenario is as follows:

The actual data is transferred to the APO SALES InfoCube. Each group now creates its own planning object structure and planning area to generate planning data based on shared actual data from the InfoCube.

1-1

Create a planning object structure called POS##. This planning object structure should contain the following characteristics:

9ALOCNO

APO - Location

9AMATNR

APO - Product

CUST

Sold-to party

DIVISION