APO TECHNICAL OVERVIEW

APO Technical Workshopfor LG Chemical

Based on APO 3.10

LG Chemical : APO Overview 2

77 liveCache

22

33

44

55

66

Software Maintenance

Sizing&Platform

Interface

APO&BW

CIF

11 Overview

99

1010

1111

Optimizer

Performance

Others

88 Backup&Recovery


History of Resource Planning Systems: APS Advanced Planning and Scheduling (APS) system features:

Separate system Own data pool

Pros: Optimized data structures Main memory based planning models

Cons (through dependency on ERP): Two systems, two data pools Data must be downloaded and uploaded by batches Data integrity difficulties through disintegration Never the current status


SAP APO System APO is SAP’s APS solution

Based on SAP Basis System and mySAP BW Powerful memory-resident analytical engine Specialized and configurable data objects Open interface to both SAP and non-SAP systems

Modules Demand Planning (DP) Supply Network Planning (SNP) Production Planning and Detailed Scheduling (PP/DS) Global Available To Promise (GATP) Transportation Planning and Vehicle Scheduling (TP/VS) Collaborative Planning (CP) Network Design (ND)


Application and Basis Components of SAP APO

R/3R/3 PI

R/3R/3 PI

SAPBWSAPBW

LegacyOLTP

LegacyOLTP

Non-SAPOLTP

Non-SAPOLTP

Non-SAPOLTP

Non-SAPOLTP

Queued RFC (qRFC), Synchronous RFC (sRFC), BAPIModel Generator, mapping, connectivity

APOOptimizers

ProductionPlanning Detailed

Scheduling

ProductionPlanning Detailed

Scheduling

DemandPlanning

(uses BW)

DemandPlanning

(uses BW)

Vendor Managed Inventory

Vendor Managed Inventory

SupplyNetworkPlanning

AvailableTo

Promise

Supply Chain Cockpit

Supply Chain Cockpit

Database with BW techniques

available

CapableTo

Match

liveCacheliveCache

APO


APO Planning Horizon

Supply Network Planning (1-6 month)

Demand Planning (6-24 month)

Production Planning (4-8 weeks)

Detailed Production Scheduling (1 week)

Deployment (1 day)

Planning horizon


Example: Production Planning in APO (DP)

SAP APOSAP OLTP System

Sales Information System (SIS)

Perform Material Requirements Planning

(MRP)

Manufacturing / Purchasing

Demand Planning

Data Load into APO Data Mart

Execute Consensus Meeting

Release to OLTP or SNP

* Alternative steps, capacity constraint-based planning

Confirmation of Final Forecast

SAP BW

Collaboration Partner

Forecast / Promotion Data

Collection/ Distribution

Legacy / Flat File

Extract Data

Update Info cubes

SNP *Constrained Demand Plan

Forecast Accuracy Reporting

Execute Forecast Run

Execute Promotion Planning

Determine Realignment Procedures


APO System: Scalable Architecture

Database

Database

Presentation ClientPresentation ClientBrowserBrowser

Presentation ClientPresentation Client

Dedicated HW/SW system for liveCache Low impact on OLTP performance Specialized and optimized solutions

SAP APO

liveCacheliveCache

APOApplication

Ap

p.

Se

rve

rA

pp

. S

erv

er

Database

Da

tab

as

e S

erv

er

Da

tab

as

e S

erv

er

APOApplication

BW Layer

APO DB

Optimizer

SAPOLTP

ITS

SAPOLTP

Webserver


APO Components

APO 3.1

SAP APO 3.1

SAP BW 2.1C

SAP BASIS 4.6D

SAP Kernel 4.6D

APO 3.0

SAP APO 3.0

SAP BW 2.0B

SAP BASIS 4.6C

SAP Kernel 4.6D

7.2.x 7.4.x

APO 3.0 : >= PI 2001.2 patch level 4, >= SAPGui 6.10

APO 3.1 : >= PI 2002.1 patch level 4, >= SAPGui 6.20


Data Distribution

Ap

p S

erv

er

Ap

p S

erv

er

Database

Da

tab

as

e S

erv

er

Da

tab

as

e S

erv

er

liveCacheliveCache

OptimizerAPO

Application

APOApplication

SAPOLTP

Database

APO

APO-CIF

All Master Data(all Fields, R/3 Key)All Transactional Data(all Fields, R/3 Key)

All Planning-Relevant Master Data(Plan.-rel. R/3 & APO Fields without

Texts, GUID)All Planning-Relevant Transactional

Data(Plan.-rel. R/3 & APO Fields, GUID)

APO DB

All Planning-Relevant Master Data

(all Fields, GUID)All Planning-Relevant

Transactional Data(Texts, GUID)

Mapping of Master and Transactional Data in Anchor Tables(R/3 Key GUID)


Performance Benefits of liveCache Avoids/reduces disk I/O:

Data is kept in main memory, all operations run in memory so large data cache necessary

Disk based logging need not be used

Reduces dataflow between application and data management: Application logic runs where the data is, avoiding network load

Reduces runtime of operations on data: Application logic operates with COM routines on object data faster than SQL

commands on relational data


Client Concept with APO 3.10 APO 3.10 is Client-Specific with Condition Current Restrictions

BW InfoCubes generate coding (client-independent)– InfoCubes can only be used within one single client, which is determined through

the first call of a BW-dependent application– It is not possible to change the productive client at a later stage

All APO applications using BW InfoCubes are client-independent – Demand and Supply Planning (planning area)– Product allocation check (global ATP), if using BW InfoCubes– Collaborative Demand and Supply Planning– Network Design if data supply through BW InfoCube

InfoCube-dependent applications such as DP and/or SNP are restricted to one client!

Exception SAP BW 2.x / SAP APO 3.x : Working in several Clients (note.384057) SAP BW 3.0 within SAP SCM 4.0 : Working in several Clients (note.522569) Too many considerations !!!

Documents

APO TECHNICAL OVERVIEW