Professional Documents
Culture Documents
1 2 3 4 5 6 7
8 9 10 11
Pros:
Optimized data structures Main memory based planning models
Modules
APO
liveCache
APO Optimizers
R/3 R/3 PI
SAP BW
Legacy OLTP
Non-SAP OLTP
Non-SAP OLTP
Deployment (1 day)
SAP APO
Demand Planning Data Load into APO Data Mart Execute Promotion Planning
SAP BW
Update Info cubes
Collaboration Partner
Forecast / Promotion Data Collection/ Distribution
Web server ITS
Dedicated HW/SW system for liveCache Low impact on OLTP performance Specialized and optimized solutions
SAP APO
App. Server APO Application
BW Layer
Optimizer
SAP OLTP
SAP OLTP
Database
Database Server
Database
liveCache
Presentation Client
Database
APO Components
APO 3.0 APO 3.1
SAP BW 2.0B
SAP BW 2.1C
7.4.x
SAP Kernel 4.6D
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
App Server
All Master Data (all Fields, R/3 Key) All Transactional Data (all Fields, R/3 Key)
APO
APO Application Optimizer
Database Server
APO-CIF
Database
liveCache
Database
SAP OLTP All Planning-Relevant Master Data (all Fields, GUID) All Planning-Relevant Transactional Data (Texts, GUID) 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)
Mapping of Master and Transactional Data in Anchor Tables (R/3 Key GUID)
LG Chemical : APO Overview 10
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 !!!