Professional Documents
Culture Documents
SAP AG 1999
l December 1998
n SAP APO Release 1.1 GA
w Supply Chain Cockpit, DP, Supply Network Planning, PP/DS, ATP
w over 250 installations, 12 productive customers
l October 1999:
n SAP APO Release 2.0 GA
w SAP Enjoy Release
w Enhancements: Push, Hierarchical Planning, ...
w SAP APO Collaborative Planning 2.0 Pilot Shipment
l May 2000
n SAP APO Release 3.0A
w strong enhancements
w strong industry support
SAP AG 1999
APO
CRT
PI xx / CIF
SAP AG 1999
l CIF release
n functional enhancement to establish integration
n similar to PI release
l CRT
n conflict resolution transport
n aligns changes made to objects by CIF and HP
l HP
n hot package
n regular way to ship R/3 corrections
l LCP
n legal change package
n HP + HR modifications
l sequence
SAP AG 1999
l CIF
n modifications + enhancements as stand-alonelayer
l PI
n Plug in landscape
w modifications
w enhancements
n planned to make PI available via Core Hot Packages
w prerequisite for IBU releases / Add Ons
w R/3 4.0B
w R/3 4.5B
SAP AG 1999
SC Cockpit
KPIs
APO
Supply Available
BW Demand
Network
Production Detailed
To
Planning Planning Scheduling
Planning Promise
Sales
data
OLTP
SAP AG 1999
n 4.5A GUI can be used for APO, BW and R/3 OLTP which means only one GUI version
n R/3 OLTP: APO and BW support specific R/3 releases and Hot Package versions. Please
investigate according to your system and package level.
Example: To run BW and APO in combination with one R/3 4.0B system, APO requires
currently at least HP 16, BW requires at least HP 12.
To run both. APO and BW, in combination with the R/3 4.0B, you have to install as a
consequence HP 16.
n APO currently does not support any analysis functionality like Bex Analyzer in BW does. All
kind of reporting needs to be done in BW.
n Master data extraction from OLTP to BW does not conflict with APOs CIF for R/3 (Core
Interface)
CIF for R/3 establishes the integration between R/3 systems and APO meaning the exchange
of master and transactional data as well as planning results.
Master data for APO Demand Planning are uploaded via DP immanent extractors, which are
similar to BW extractors. Both do not conflict with each other.
Deltas for BW and Demand Planning do not conflict with each other
n Patches: Recommended to apply the most up-to-date BW patch for APO Demand Planning and
BW
BW APO
OLTP
SAP AG 1999
BW APO
Historical Planned
Historical data
Data Mart
Interface
Planning results DB Datamart
Staging
Staging
n Master data extraction from OLTP to BW does not conflict with APOs CIF for R/3 (Core
Interface)
Master data for APO Demand Planning are uploaded via DP immanent extractors, which are
similar to BW extractors. Both do not conflict with each other.
Deltas for BW and Demand Planning do not conflict with each other as well
n Sales data from BW are uploaded to APO DP
Forecasts are calculated and measured based on this data
n Planning results like future demands are transfered back to BW for analysis
n Data Flow:
Export InfoSource generatedin BW
Export InfoSource transfered to APO via Meta Data Update
Sales data uploaded to APO DP via the Export InfoSource
APO
Demand Planning
D Historical
M
I Planned
SAP AG 1999
SAP AG 1999