SAP AG 2000 / 1

APO-BW Integration

SAP AG 2000 / 2

Overview

Business Scenarios

Agenda

Workplace and Roles

Technical View

11

44

Business Content55

33

22

Summary66

SAP AG 2000 / 3

Overview

Business Scenarios

Agenda

Workplace and Roles

Technical View

11

44

Business Content55

33

22

Summary66

SAP AG 2000 / 4

OLTPOLTP

R/3R/3 R/3R/3 Non R\3OLTP

Non R\3OLTP

BW DemandPlanning

Transpor-tation

Planning

PP/DSProduction Planning Detailed Scheduling

SupplyNetworkPlanning

AvailableTo

Promise

APO

SC Cockpit

KPIsKPIs

Salesdata

Salesdata

Integration via CIF for R/3Upload via BW extractors

BW, APO and OLTP

R/3R/3 R/3R/3 Non R\3OLTP

Non R\3OLTP

PI xx

SAP AG 2000 / 5

APO installation details

APO 2.0A is based on

• an R/3 4.6A Kernel

• BW 1.2B

APO 3.0A is based on

• an R/3 4.6C Kernel

• BW 2.0B

For HW/database combinations please check

https://SAPNet/.../PAM

SAP AG 2000 / 6

Overview

Business Scenarios

Agenda

Workplace and Roles

Technical View

11

44

Business Content55

33

22

Summary66

SAP AG 2000 / 7

Demand Planning (DP)Sales AnalysisSales Analysis

BW and Demand Planning

BW Admin. Workbench delivered with APO

StagingStagingStagingStaging

Historical Planned

DB Datamart

FileR/3

FileFileR/3R/3

Data MartInterface

Data MartInterface

HistoricalHistorical data

Planning results

Sales Analysis Consolidation Enrichment Multi sources

APOAPOBWBW

SAP AG 2000 / 8

BW / APO Integration Scenario (Example1)

R/3

Example: Sales Overview (0sd_c03)

Demand Planning Cube

Historical data

Planning results

Transaction data

BW APOSingle Cube forPlan v.s Sale

SAP AG 2000 / 9

BW / APO Integration Scenario (Example2)

R/3

Example: Sales Overview (0sd_c03)

Demand Planning Cube

Historical data

Planning results

Transaction data

BW APO

Copy of Demand Planning Cube

Multicube forPlan v.s. Sale

SAP AG 2000 / 10

R/3R/3

APOAPOAPOAPO

APO - Standalone

R/3R/3

R/3R/3

SAP AG 2000 / 11

APO (Standalone) Scenario

R/3

Infocube for

Demand Planing

Historical data

APO

Other Infocube for Reporting Purpose

SAP AG 2000 / 12

SAP recommends to set up separate systems for APO and BW.

Reason

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.

APO (Standalone)

SAP AG 2000 / 13

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 kpi‘s 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”

Aggregation cannot be built on demand planning infocubes

APO (Standalone)

SAP AG 2000 / 14

BW and Demand Planning Reporting

Reporting for Demand Planner and Sales RepsReporting for Demand Planner and Sales RepsReporting for Demand Planner and Sales RepsReporting for Demand Planner and Sales Reps

Regional ForecastReporting

Regional ForecastReporting

Planned actualdeviation

Planned actualdeviation

Top 10 deviationsPlanned/ Actual

Top 10 deviationsPlanned/ Actual

Forecastaccuracy

Forecastaccuracy

APOAPO

Demand PlanningDMI

DMI

DP delivers Planning data through data mart interface (DMI) BW Info Cube for information consumers

Historical

Planned

SAP AG 2000 / 15

Integration of Arbitrary Workbooks Into APO

APO Supply Chain Cockpit

BW Excel Frontend

SAP AG 2000 / 16

Link Between BW Workbooks and Context Menu

Define default BW RFC Destination in the creation of context menu

Maintain Context Menu

Define Default Context Menu for new users

SAP AG 2000 / 17

SCC Context Menu

Drag & Drop

SAP AG 2000 / 18

Supply Chain Cockpit User- Specific Setting

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 / 19

Overview

Business Scenarios

Agenda

Workplace and Roles

Technical View

11

44

Business Content55

33

22

Summary66

SAP AG 2000 / 20

Sales and Operations Planning

Marketing Manager

Supply Chain Planner

22

long termforecasting

APOAPO33

R/3R/3

11

BWBW

BexMulti Cube Query

Account Manager

FlexiblePlanning Book

simulate supply plan

review exceptions

Actuals

Plan

compare and report onactuals vs. plan

44

33

reach consensus

55

marketing planning

salesplanning

transfer final result /demandplan

66

SAP AG 2000 / 21

Network Analysis and Design

APOAPO

11

FINANCE / CONTROLLING SCM / LOGISTICS

StrategicFinancial Planner

SEMSEM

StrategicLogistics Planner

Supply Chain Manager

create long-termdemand plan

2233

44review and simulate

BEx

communicate final result

transfer financial planning

55

trigger network analysis and design

SAP AG 2000 / 22

Collaborative Demand Planning

DemandPlanner

APO DPAPO DPinsert forecast

2211

44 alert broadcasting (e.g. e-mail)

66 forecast adjustment

create statisticalforecast

CHANNEL PARTNER MANUFACTURER

AccountManager

Internet

55review

forecasts

Internet

33create

consensusforecast

SAP AG 2000 / 23

Overview

Business Scenarios

Agenda

Workplace and Roles

Technical View

11

44

Business Content55

33

22

Summary66

SAP AG 2000 / 24

Chris’ Workplace as Supply Chain Manager

Chris’ Workplace as Supply Chain Manager

SCM and mySAP.com Workplace

Supply Chain Manager

Task

Lead the SC Team

Global / Regional responsibility for SC

Goal

Measure and Manage based on

Market share / Service Level

Total Supply Chain Cost

Asset Utilization

No Alerts / No Stockouts / ...

Tools

BW Web Reports on performance

Supply Chain Cockpit

Agregated Alerts via Exception Manager

SAP AG 2000 / 27

Overview

Business Scenarios

Agenda

Workplace and Roles

Technical View

11

44

Business Content55

33

22

Summary66

SAP AG 2000 / 28

APO-BW Content

Answer different types of questions

Overview and details of actual (or historic) plan: ‚What will be produced? What‘s the corresponding resource load?‘

Optimization: Compare plan A with plan B (APO planning versions)

Compare with execution data

History: Keep information on master plan

Store (aggregated) information on production plan

Evaluate APO planning results with SAP BW

Flexibility of reports, drill down, view from any angle

HTML reports, MS Excel, Graphics, Mini Apps, GIS integration

Integration with R/3 data

Download necessary (data volume)

SAP AG 2000 / 29

APO Product Map

Business Content

SAP AG 2000 / 30

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

Display results of network design: geographical context

Upload: Snapshot scenario

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 / 33

SAP AG 2000 / 34

APO-BW Content - Master data

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 / 35

SAP AG 2000 / 36

SAP AG 2000 / 37

SAP AG 2000 / 38

Overview

Business Scenarios

Agenda

Workplace and Roles

Technical View

11

44

Business Content55

33

22

Summary66

SAP AG 2000 / 39

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.

Summary

SAP AG 2000 / 40

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.

Analysis on plan versus actual should be performed in the BW system.

Summary