Professional Documents
Culture Documents
SAP AG 2000 / 1
Agenda
1 2 3 4 5 6
Overview Technical View Business Scenarios Workplace and Roles Business Content Summary
SAP AG 2000 / 2
Agenda
1 2 3 4 5 6
Overview Technical View Business Scenarios Workplace and Roles Business Content Summary
SAP AG 2000 / 3
KPIs
APO
BW
Sales data
Demand Planning
PP/DS
Production Planning Detailed Scheduling
Transportation Planning
Available To Promise
PI xx
OLTP
R/3
R/3
R/3
R/3
SAP AG 2000 / 4
APO 2.0A is based on an R/3 4.6A Kernel BW 1.2B APO 3.0A is based on
https://SAPNet/.../PAM
SAP AG 2000 / 5
Agenda
1 2 3 4 5 6
Overview Technical View Business Scenarios Workplace and Roles Business Content Summary
SAP AG 2000 / 6
DB Datamart
Staging
R/3
R/3
File
SAP AG 2000 / 7
BW
Single Cube for Plan v.s Sale
Example: Sales Overview (0sd_c03) Planning results
APO
Demand Planning Cube
Historical data
Transaction data
R/3
SAP AG 2000 / 8
BW
APO
Planning results Demand Planning Cube
Transaction data
R/3
SAP AG 2000 / 9
APO - Standalone
R/3
APO
R/3
R/3
SAP AG 2000 / 10
APO
Infocube for Demand Planing Other Infocube for Reporting Purpose
Historical data
R/3
SAP AG 2000 / 11
APO (Standalone)
The APO system will be tuned for optimal APO functionality performance such as calculating forecasts in demand planning or deriving ATP values The BW system will be tuned for optimal query performance in order to return results in a timely fashion.
SAP AG 2000 / 12
APO (Standalone)
Reporting with BEX analyzer is possible
Need to install BW frontend component on client PCs use of BEX included in APO user starting from July 2000 (please see pricing / Supply Chain Planner)
Business content
Calling kpis from the supply chain cockpit is no problem even if they are located on the same system.
Limitation
IF you want to perform reporting directly on demand planning cubes. Please consider note: 0156695 You need to execute a program for each infocube to register APO request ID. /Sapapo/rmdp_cube_req_register
SAP AG 2000 / 13
APO
D M I
Historical Planned
Demand Planning
DP delivers Planning data through data mart interface (DMI) BW Info Cube for information consumers
SAP AG 2000 / 14
BW Excel Frontend
SAP AG 2000 / 15
SAP AG 2000 / 17
SAP standard menu > navigation > supply chain > settings > cockpit In the tab general, you can change your own context menu profile. This setting is user-specific.
SAP AG 2000 / 18
Agenda
1 2 3 4 5 6
Overview Technical View Business Scenarios Workplace and Roles Business Content Summary
SAP AG 2000 / 19
2
review exceptions
APO
reach consensus
6
Bex Multi Cube Query
R/3
Account Manager
sales planning
BW 4
Actuals compare and report on actuals vs. plan
SAP AG 2000 / 20
2 SEM
transfer financial planning
APO
3 trigger network
analysis and design review and simulate
5
communicate final result
BEx
Account Manager
Demand Planner
4 5
review forecasts
Internet
6
Internet
insert forecast
APO DP 1
SAP AG 2000 / 22
Agenda
1 2 3 4 5 6
Overview Technical View Business Scenarios Workplace and Roles Business Content Summary
SAP AG 2000 / 23
Goal
Market share / Service Level Total Supply Chain Cost Asset Utilization
Tools
BW Web Reports on performance Supply Chain Cockpit Agregated Alerts via Exception Manager
SAP AG 2000 / 24
Agenda
1 2 3 4 5 6
Overview Technical View Business Scenarios Workplace and Roles Business Content Summary
SAP AG 2000 / 27
APO-BW Content
Answer different types of questions
Overview and details of actual (or historic) plan: What will be produced? Whats the corresponding resource load? Optimization: Compare plan A with plan B (APO planning versions)
SAP AG 2000 / 28
Business Content
SAP AG 2000 / 29
APO-BW Content
Extract data for order based APO applications
Information on Live Cache order net View into the future Planning versions (different parameters, algorithms) One active planning version linked with execution system Planning version as characteristic for all transactional data
Decision on point of time for upload necessary: e.g. after optimization run Label upload: name of snapshot as characteristic No delta update
SAP AG 2000 / 30
SAP AG 2000 / 33
Content modeling involves the following main business objects Location - InfoObject 0APO_LOCNO
GIS enabled
Product - InfoObject 0APO_PROD Location Product - InfoObject 0APO_LPROD Resource - InfoObject 0APO_RESNAM Production Process Model - InfoObject 0APO_PPM
linked to R/3 infoobjects (as 0MATERIAL, 0PLANT, ...) through navigation attributes
SAP AG 2000 / 34
SAP AG 2000 / 35
SAP AG 2000 / 36
SAP AG 2000 / 37
Agenda
1 2 3 4 5 6
Overview Technical View Business Scenarios Workplace and Roles Business Content Summary
SAP AG 2000 / 38
Summary
Administrator workbench in an APO system includes all functions of BW, but there is some limitaion for DP infocubes. It is possible to perform reporting with BEX analyzer from infocubes in an APO system. SAP recommends to prepare separate servers for reporting& analysis and for plannning.
SAP AG 2000 / 39
Summary
BW/APO integration In case the R/3 system has an extractor older than PI 2000( which cannot send delta to several systems), actual data should be transferred to the BW system. Actual data is sent from BW to APO, and planning data is sent back from APO to BW using dart mart function.
SAP AG 2000 / 40