APO Overview

IBM Business Consulting Services
Advanced Planning and Optimizer
Supply Chain Management
© Copyright IBM Corporation 2003

General Topics
 Supply Chain Management Overview
 What is Supply Chain Management
 Where does it fit
 SCM Process
 Requirement of APO for SCM planning
 Advance Planning and Optimization

 Components of SAP APO
 DP, SNP, PP, DS
 Integration with ECC - Core Interface
 Overview of CIF
 Data creation in CIF
 Integration Model Variant
 Outbound queues and Inbound queues
 CIF Debugging
 Appendix
 Technical inputs – BAPI, BADI, EXIT, Function Modules, Reports, Tables
2 Presentation Title | Confidential | Document ID Advanced Planning and Optimizer © Copyright IBM Corporation 2010
What is Supply Chain Management (SCM)?
The supply chain includes all activities related to the planning

and executing of supply, production, and distribution
management.
Managing this supply chain effectively can increase business

flexibility and create bottom-line value.
Therefore, SCM can provide competitive advantage in today’s

networked economy.
TODAY’S SEQUENTIAL SUPPLY CHAIN

SAP’s Vision of SCM
SAP Transforms
ADAPTIVE SUPPLY CHAIN NETWORK

SAP SCM – Where does it fit

SAP Business Suite
SAP PLM
Maintenance & Quality
Distribution Management
SAP ERP
Purchase Order
Sales Order &

SAP SAP
Management
Financials
SRM Human Resources CRM
Corporate Services
Operations
Inventory & Production
SAP SCM
SAP NetWeaver
APO - SAP SCM Supply Chain Planning Solution
 SAP Advanced Planning and Optimization (SAP APO) supports comprehensive

planning capabilities:
- Supply network planning
- Demand planning
- Supply chain network design
- Collaborative planning processes (demand and supply)
- Production planning
- Transportation planning
- Global available to promise (Global ATP)
APO Overview

Overview of Advanced Planning and Optimizer
 SAP (Advanced Planning and Optimizer) or SAP (APO) is the planning component
within the mySAP SCM solution. APO is an acronym for Advanced Planner and
Optimizer. This is a large component of SAP's New Dimension products. APO is an
entire suite of supply chain planner applications that increase overall knowledge of the
supply chain and provide forecasting, planning and optimization. There are eight
application levels within SAP APO: network design, supply network planning, demand
planning, production planning and detailed scheduling, transportation planning and
vehicle scheduling, global availability and supply chain collaboration.
 The SAP APO is not a standalone application and requires a backend ERP system such
as SAP R/3 for the execution. SAP R/3 communicate with SAP APO using the APO
Core Interface (CIF) which supplies SAP APO with the master and the transaction data
in the real time. Interaction between the SAP R/3 at backend and the SAP APO is in real
time and any data related to the production, the sales or the supplies is immediately
transferred from one system to another without requiring any batch processing.
Advanced Planning and Optimizer contd…
Modules within SAP APO

 Supply Chain Cockpit - A graphical tool for evaluating and controlling the
supply chain
 Demand Planning - a toolkit of statistical and collaborative forecasting
techniques.
 Supply Network Planning - used to calculate quantities to be delivered to a
location in order to match customer demand and maintain the desired service
level.
 Global Available to Promise - uses a rule based strategy to ensure you can
deliver what you promise to your customers.
 Transportation Planning / Vehicle Scheduling - optimizes transportation
route and schedules vehicle resources.
 Service Parts Planning
 Production Plan / Detailed Scheduling - create procurement proposals for
in-house production or external procurement to cover product requirements
and optimizes the same.
The Complete SCM Solution

Measure
Supply Chain Performance Management
Plan
Dyn. Supply Chain Cooperation
Dyn. Supply Chain Cooperation

Vendor
Demand Planning Supply Network Customer
(DP) Planning
(SNP)
Private Private
Exchanges Exchanges
Source Make Deliver
Supplier
Relationship Availability Check
Production Planning/
Management
Detailed Scheduling
(ATP)
(SRM) Transportation Planning
Scheduling agreement (PP/DS) (TP/VS)
Partner release Partner
Monitor
Supply Chain Event Management
Supply Chain Planning: Why do companies need it?

Balance & optimize supply and demand
Customers
Storage
DEMAND
Locations
SUPPLY
Plants
Suppliers
SAP APO Components
DP SNP PP DS

Components of APO – continued …
 Managing the flow of products and services and the associated information, across the business
system to maximize value to the end consumer.
Suppliers Manufacturer Distribution Retailer Consumer
Product/Services
Demand Planning
Demand and Cash flow
Information
Reuse/Maintenance/After Sales Service
Supply Chain Planning at a Glance
Factors that Influence Demand Planning and SNP
Overview of SAP APO Demand Planning
Demand Planning Concept
APO Application Architecture
Extracting Transaction Data
Data Storage in DP / SNP
 Data stored in buckets, no reference

to orders
 In liveCache time
 Suitable for tactical planning (DP)
series objects
 Data stored with reference to orders

 In liveCache orders  Suitable for operative planning (SNP)
 Data stored in infocube

 Suitable for old planning data (like
 In an InfoCube sales history – based on which
forecasting can be carried out)
What is LiveCache
The SAP liveCache technology is an object-based enhancement of the SAP MaxDB
database system. It was developed for managing complex objects in applications in
which large quantities of data must be constantly available and changeable. You can only
use SAP liveCache technology with SAP applications.
Properties of an SAP application with SAP liveCache technology:

 With optimal configuration, all application data and objects are located in the working
memory
 Multiple application servers are sharing the read/write cache
 Relational and object-oriented data modeling
 Data-intensive business logic is executed close to the application data (minimizing round
trips)
 All database functions are available
APO Core Interface (CIF)

Overview of CIF
What is Core Interface ?
 APO Core Interface

- connects an APO and a standard R/3 system
 determines source and target systems within complex system
environments through Integration Models
- supplies APO with the relevant master and transaction data
 transfer of planning relevant data only
 initial and incremental data transfer
 real-time interface
- returns planning results to the OLTP system
APO-CIF is delivered as a plug-in . This is a general product name given
by SAP for the R/3 interfaces to the new dimension applications. R/3
Plug-in is name of an R/3 enhancement which enables integration with
the mySAP.com components like BW, APO, SEM, etc. APO-CIF interface
solution is available for R/3 systems from Release 3.1I.
APO Core Interface (CIF)
 APO software includes a communication layer to enable integration between APO

and OLTP systems (eg. R/3 system).
 APO CIF is the communication layer to be applied to R/3 to enable integration of
R/3 system with APO system. There is a similar communication layer which comes
as a standard function in the APO system.
 APO CIF is a real-time interface between R/3 & APO system
 The main roles of CIF are :
- Determine source and target systems
- Initially supply APO with master and transactional data
- Incrementally keep on supplying APO with transactional data
- Return planning results to R/3 system
 In order to integrate two systems together, data mapping must take place. Data
mapping includes matching up table/structure names and field names between
systems.
 CIF integration models provide automatic data mapping between R/3 objects and
the corresponding objects in APO.
 Between non-R/3 ERP and APO, other interfaces like BAPI or ALE are used.
CIF Functions
ERP -> APO APO -> ERP

Master Data Transaction Data Planning Results
 Locations  Planned/Production  ATP Results
 Products Orders  Manufacturing Orders
 PPMs (BOM+Routing)  Sales Orders  Procurement Orders
 Characteristics  Purchase Orders  VMI Sales Orders
 Capacities  Stocks
 ATP Requests
APO
APO
ERP BW
ERP ERP
APO ERP
CIF Setup and Related Configuration Tasks
 R/3  APO
- Set up a logical system - Set up a logical system
- Assign LS to client - Assign LS to client
- Set up RFC destination - Set up business system
- Define target system (same name group
as the RFC destination) - Assign LS to BSG
Note : Details of the CIF configurations are not covered in this training
However, the required CIF settings

are mentioned in the attached
document for reference
Some useful transaction for CIF setting in R/3 and APO
Initial CIF Settings – R/3 Initial CIF Settings – APO

 Check ALE settings or activate ALE  Check ALE settings or activate ALE
settings settings
 Define the logical system BD54  Define the logical system BD54
 Assign logical system to a client SCC4  Assign logical system to a client SCC4
 Set the RFC destination SM59  Set the RFC destination SM59
 Assign target system and queue type  Set up business system group
CFC1  Create BSG /SAPAPO/C1
 Maintain the SAP APO release NDV2  Assign logical systems to BSG
 Activate BTEs for SAP APO integration /SAPAPO/C2
BF11  Maintain distribution definitions
 User parameters for CIF CFC2 /SAPAPO/CP1
 User parameters for CIF /SAPAPO/C4
Some Useful transaction related to CIF in R/3 and APO
CIF related transaction – R/3 CIF related transaction – APO

 CFM1 Create integration model  /SAPAPO/C3 View CIF application log
 CFM2 Activate/deactivate integration models  /SAPAPO/C4 Setting of user parameters CIF
 CFG1 View CIF application log  /SAPAPO/C5 Send planning results to R/3
 CFC2 User parameters for CIF  /SAPAPO/C1 Create business system group
 CFC3 Block sizes for initial transfer  /SAPAPO/C2 Assign logical systems to a
 CFM5 Filter object search in integration models business system group
 CFC1 Define logical systems as APO systems  /SAPAPO/CQ SCM Queue Manager
 NDV2 Setting of release level of APO systems  /SAPAPO/CCR Comparison/reconciliation tool
 SMQ1 qRFC monitor incl. functions start, stop,  SMQ1 qRFC monitor incl. functions start, stop,
execute execute
 SM59 Definition of RFC destinations  SM59 Definition of RFC destinations
 SALE Definition of logical systems  SALE Definition of logical systems
Overview of data creation in CIF

R3 to APO
Transfer of Master Data
•Initial transfer
•R/3 •APO
•R/3 master data •APO master data
•Plant •Location
•Customer
•Product
•Vendor
•Resource
•Material master
•Capacity •Production
process model
•Routing and
•bill of material
•Incremental data transfer
Integration Model
•Transaction Code : CIF-EA
•Integration Model distinguishes between

Master Data and Transactional Data elements
•You can have multiple integration models.

However, there are certain recommendations in
deciding how many integration models to create
for an implementation (details given later)
•In integration model, you select:
•The data sets (master data objects,
transactional data objects)
•APO target system for data transfer
•Creation, Change, Display, Deletion possible
Integration Model – Initial Data Transfer
1. • Generate integration model •Name
•Target system
•Determine name and APO

•Plant
•target system
•Material master
•Resource
•Select master data •...
2. •Activate integration model
•Integration model is active
•Start •Master data will be transferred
Integration Model – Generation

 Integration Model = Name + Application
 Target System = APO System (it should be a logical system having active
RFC connection)
 Specify data objects to transfer - Filtering criteria available {Examples: -
Plant, MRP Type (X0 or X1), MRP Controller}
 “Execute” – system compiles the selected data objects (report available to
check compiled objects)
 “Generate” (save the model)
Integration Model – Activation
• “Activate” integration model (which

has been “generated” in previous
step)
• This initiates data transfer from R3

to APO
• The integration models are created

with time-stamps
• The active integration model is

indicated by the icon
Selection Criteria – MRP Type X0
R/3 Material master D

Material master C
Integration model
Name PUMP
Material master B Target s. APOCLNT800
MRP type X0 Material master A
Applic. MATERIALS
MRP procedure X
Without MRP, Mat. A Material master
with BOM explosion X0 Customers
...
Relevant materials
Mat. B Mat. C Mat. D Material
X0 X0 VB Plant 1000
MRP type X0
Material
Planning in Product C ...
status
APO Product B
APO
Product A
Which Products to plan in APO ?

Planning type APO Possible APO not
recommended in APO recommended
Externally procured products X

with long replenishment times
Products manufactured X
in-house at bottleneck
resources
Products that are not X

critical for planning
(Non-critical) products X
planned with reorder
point planning
(Non-critical) products X
planned with KANBAN
Transfer of New APO-Relevant Master Data
New Data Transfer Regenerate Data
Integration Model-1 : Products A & B at 10:00 hrs Integr Model-1 : Products A & B at 10:00 hrs
New material (Product Q) to be

transferred to APO
Deactivate Model
Existing integration model Execute+ Save
"Activate"
Active/Inact.
Activate Model
Re-Transfer of Product A, B & Q happens

Integration Model-1 : Products A,B,Q at 11:00 hrs
Active
Integration Model-1 : Products A & B at 10:00 hrs
Inactive
Transfer of only Product Q happens
Transfer of New APO-Relevant Master Data
New Data Transfer Regenerate Data Transfer
The system re-generates the existing

model (the new master data is also If you want the system to retransfer all
selected here) and then activates it. the master data of an existing
integration model, you must deactivate
Two models with the same name are the old models and activate only the
then active, the only differences being new one.
the dates and times. If the data
transfer starts in this situation, the A comparison of all active models then
system simply transfers the difference takes place. As in this case, the model
data. with the old time is not active, all data
is transferred again.
After the data transfer, the system
deactivates the "old" integration model,
leaving the "new" complete integration
model as the active model.
Incremental Data Transfer
Transaction CFC9
APO
Material master
Changed R/3 master data
Business Transaction Event, immed . objects are transferred into
ALE change pointer, periodic APO when the changes are
saved in real-time
no incremental data transfer
Customers
Business Transaction Event, immed . Changes to R/3 master data
ALE change pointer, periodic objects are recorded and the
transfer of the changes is
no incremental data transfer (periodically, for example)
triggered
Vendors
Business Transaction Event, immed .
Incremental Data Transfer
ALE change pointer, periodic
no incremental data transfer
Incremental Data Transfer – ALE Change Pointers
n The process of incremental data transfer reverts to the ALE change pointer. This
change pointer selects the master data for the system to retransfer. When you call up
the transaction Incremental data transfer of master data (CFP1), specify the the logical
target systems and the master data objects (material masters, vendors, sources of
supply, customers), that have changes to be transferred.
ALE Change Pointer Settings
Change pointers are used by the ALE message distribution. Changes to Master Data are recorded
and given a change number (if they are in an active message type).
Transaction BDCP
CIF Message types must be activated for change recording. Transaction BD50
Activate Change Pointers. Transaction BD61
The fields relevant to a message type to be selected. Transaction BD52
Field Mapping between R3 and APO
 Refer to the attached document for details
Master Data Mapping Transactional Data Mapping

Between R3 and APO Between R3 and APO
Transactional Data Transfer – R3 to APO
APO Initial data transfer

R/3 takes through CIF
Initial data
R/3 transaction data APO transaction data
transfer Order with category New transactional data
Purchase orders
BF (PchOrd ) or changes to existing
Purchase requisitions
AG (PurRqs ) transactional data are
Sales orders BM (SalesOrder ) transferred
Planned orders AI (PlOrd .) automatically (real-
FA (FC req.)
Planned ind.reqmts time)
AM (PrdRes )
Reservations
Incremental CC (Stock)
Stocks ... Methodology of transfer
...
data transfer
is same (using
Real- Integration Models)
time
The APO transaction data objects are not generally identical to those of the R/3 System. The
system transfers various R/3 transaction data into APO as orders that differ by ATP category
Publication of Planning Results – APO to R3

 Planning Results are transferred from APO to R3, which is termed as
Publication
 Configuration in APO :
- Basic settings (publication of planning results)
 specify for each plant and publication type (example, in-house production or external
procurement,etc), which R/3 System (logical system) to publish planning results.
 For SNP, you set the form for transferring SNP planning results to the R/3
System with the Customizing operation: Set transfer to OLTP system. The
default setting for SNP is that the changes are collected and transferred
periodically.
 For PPDS :
- In APO transaction /SAPAPO/C4 you set how (in what form) new transaction data is to
be transferred from APO PP/DS into R/3. It is usually a real-time transfer (this is the
default setting for PP/DS data).
- There is also the possibility of collecting the changes in APO first, then transferring
them to the R/3 as a collected group (transaction /SAPAPO/C5).
Publication of Planning Results
 Report : /SAPAPO/RDMCPPROCESS
T-Code : /SAPAPO/C5
Function Module : /SAPAPO/DM_CP_PUB
 Orders that have been created, changed or deleted in

APO applications are published back to R/3 through the
above function module.
 APO applications that can create, change, delete orders

are:
PP/DS : Direct Publication
SNP : Periodic Publication
Creation of integration model

variant
Integration model variant creation
CFM1 – Creation of
Variant
Periodic Data Transfers through Batch Jobs
Generate integration model
Name PUMPS JOB_1

Target system APOCLNT800 Variant
Execute
PUMP_MAT Step 1
Application MATERIALS +
Save
...
RIMODGEN report alternative:
JOB_1_AND_2
Activate integration model

JOB_2
Name PUMPS
Variant
APOCLNT800 Active/ Inact .
Target system
PUMP_MAT + Step 2
Application MATERIALS
Start
RIMODAC2 report
Periodic Incremental Data Transfers through Batch Jobs
The settings for an incremental data transfer can be saved as variants and used for periodic
scheduling of incremental data transfer as a job. Report RCPTRAN4 is used for that
purpose.
Master data Change pointer generally active?
change Relevant message type
active?
Material master A
Mat.planning Change pointer
MRP type X0 Matl . B in-house pro. time
Plan. deliv .time 10 days

Customizing Matl . A Plan. deliv . time
...
11 days
Incremental data transfer

Variant Incremental
DELTA_MAT Target sys. APOCLNT800 data transfer
Object types Execute
Material master ...
Changed master Product A
APO data in APO Plan. deliv .time 11 days
Delete change pointers regularly

Overview about Outbound queues and

Inbound Queues
Data Transfer Technique
 Data transferred in both directions (from R/3 to APO as well as from APO to
R/3) by means of one or more queued Remote Function Calls (qRFC).
 The function calls are buffered in the sending system and executed
asynchronously in the same sequence they were called. This serialization is
controlled by the use of identical queue names and is required to assure
consistency.
 Multiple qRFCs can be combined into a logical unit of work (LUW), whereby
one LUW on the sender side results in one LUW on the receiver side.
Communication Method
The queue for communication might be of two

types :
Outbound Queue
Inbound Queue
Communication Method - Outbound Queue
 Calling system sends the queues to the receiving system without

taking care of the system load of the receiving system.
 No scheduling of the processes happen in the receiving system.
 Effect :
- Overloading of receiving system

- CIF performance deteriorates with high data volume
Communication Method - Inbound Queue
 Calling system sends the queues to the “entrance” (inbound) of the

receiving system which allows the receiving system to control the
system queue load on its own.
 Scheduling of the processes happen in the receiving system.
 Effect :
- Better CIF performance
 To change from Outbound to Inbound Queue :

Refer Notes 388001, 388528, 388677
Important Pre-Requisite at R3 and APO end (1)
 Logging Mode to be switched on :

 Transaction in R3 : CFC2
 Transaction in APO : /SAPAPO/C41
 Normal
- the number of data records transferred is logged
 Detailed
- the number and content of the data records transferred is logged
 Delete entries:
- You can delete logs of the application log in R/3 and APO.
- The system does not delete the logs automatically.
- You can delete logs of the application log in R/3 and APO.
- Recommendation : Deleting the logs periodically (schedule background processing)
- Refer Next slide for further details
Detailed Error Log
 It is also required to delete the Error Logs periodically to

avoid overflow of database.
This can be done by :
- In R/3 Side : - In APO Side
T-Code : CFGD T-Code : /SAPAPO/C6

Report : RDELALOG Report :
/SAPAPO/RDELLOG
 Note : The above can be scheduled as a batch job, if

required
Steps to follow – Data Transfer from R3 to APO
Data not found

in APO
No
Check R/3 Check existence of
application log active integration
(T-Code: CFG1) model
Yes
Yes
Check R/3 qRFC Check queue status Correct error Reactivate queue
Monitor in R/3 and
(T-Code: SMQ1) retransfer
No
Check APO application log Correct error

(T-Code: /SAPAPO/C3)
Steps to follow – Data Transfer from APO to R3
Data not found

in R/3
No
Check APO application Check existence of
log active integration
(T-Code: /SAPAPO/C3) model
Yes
Yes
Check APO qRFC Check queue Correct error Reactivate queue
Monitor status in APO and
(T-Code: SMQ1) retransfer
No
Check R/3 application log Correct error

(T-Code: CFG1)
CIF Debugging

Module Objectives
At the conclusion of this unit, you will be able to:
- Maintain Configurations for CIF Debugging

- Debug CIF Queue Inbound and Outbound
Introduction
 Master and Transaction data in APO is either created in APO or transferred from SAP
R/3
 CIF integration models used to transfer data.
 There will be Inbound and Outbound Queues
 Debugging can be done for both Queues by using Configurations enabled in APO
CIF Debugging
 Contents
- Inbound/Outbound Queue
 Configurations
 Case Study
Configurations
 Go to transaction /SAPAPO/C4
 Make an Entry for User
 Enable RFC Debugging (Debugging On, Recording of t/qRFCs (NOSENDS))
(Debugging On, Recording of t/qRFCs (NOSENDS))
Example
 Outbound Queue
CIF Debugging
Outbound
 Inbound Queue
CIF Debugging
Inbound
Appendix

CIF Monitoring
Application
R/3 log
APO
R/3:
Error
RFC
- Communication errors
Master/
transaction
transaction data
data - Application errors
APO master/
Core
Core Interface
Interface RFC
transaction data
live
Application
Cache
Cache
log
APO:
Error
CIF Monitoring – Applications at a Glance
 On R3 side
- qRFC Monitor (Transaction CFQ1)

- Application Log (Transaction CFG1)
 On APO side
- qRFC Monitor (Transaction SMQ1)

- Application Log (Transaction /n/SAPAPO/C3)
 Monitoring both R3 and APO from within APO
- SCM Queue Manager (Transaction /n/SAPAPO/CQ)

- qRFC Alert (Transaction /n/SAPAPO/CW)
Monitor Change Transfer- R/3
 Report : RCPQUEUE (Use T-Code : SE38)
 This report is used to monitor the transfer of Transaction Data. This report can be used
for :
¤ Checks the status of the active data channels - accordingly various data channels can be closed or opened.
¤ Display and analyze the objects to be transferred for each filter object
The list of the data channels are given in next slide.
Data Channels Data-Object-wise
 Initial supply CF_ADC_LOAD

 Stock CFSTK*
 Purchase orders and purchase reqn CFPO*
 Planned orders/Production orders CFPLO*
 Sales orders CFSLS*
 Manual reservations CFRSV*
 Confirmations CFCNF*
 Planned independent Rqmnt CFPIR*
 Materials CFMAT*
 Production campaigns CFPCM*
 Master data for classes CFCLA*
 Master data for characteristics CFCHR*
qRFC Status and their Implications
•Refer to the attached document
Data Inconsistency between R3 and APO – CIF Delta Report
APO
R/3 Report /SAPAPO/CIF_DELTAREPORT2
Partner system (R/3) R3CLNT800
Material P-102 (optional)
Plant 100 (optional)
Integration model Pump (optional)

Objects to be checked
Sales orders
Production/process orders
Purchase requisition
... ...
Storage location stocks

Sales order stocks
... ...
Compare live
Database Cache
Demand Planning and SNP process flow
Technical Components of APO for development
Refer to the following document

Includes
- BAPI
- BADI
- EXIT
- Report
- Table
Questions and Answers
Congratulations!
 Congratulations for completing this

training
 Thanks for your participation!

APO Overview

Cargado por

Información del documento

Título original

Derechos de autor

Formatos disponibles

Compartir este documento

Compartir o incrustar documentos

Opciones para compartir

¿Le pareció útil este documento?

¿Este contenido es inapropiado?

Copyright:

Formatos disponibles

APO Overview

Cargado por

Copyright:

Formatos disponibles

IBM Business Consulting Services

Advanced Planning and Optimizer

Supply Chain Management

© Copyright IBM Corporation 2003

 Advance Planning and Optimization

What is Supply Chain Management (SCM)?

The supply chain includes all activities related to the planning

Managing this supply chain effectively can increase business

Therefore, SCM can provide competitive advantage in today’s

TODAY’S SEQUENTIAL SUPPLY CHAIN

ADAPTIVE SUPPLY CHAIN NETWORK

SAP SCM – Where does it fit

Maintenance & Quality

Sales Order &

APO - SAP SCM Supply Chain Planning Solution

 SAP Advanced Planning and Optimization (SAP APO) supports comprehensive

© Copyright IBM Corporation 2003

Overview of Advanced Planning and Optimizer

Advanced Planning and Optimizer contd…

Modules within SAP APO

The Complete SCM Solution

Dyn. Supply Chain Cooperation

Supply Chain Planning: Why do companies need it?

SAP APO Components

© Copyright IBM Corporation 2003

Components of APO – continued …

Suppliers Manufacturer Distribution Retailer Consumer

Reuse/Maintenance/After Sales Service

Supply Chain Planning at a Glance

Factors that Influence Demand Planning and SNP

Overview of SAP APO Demand Planning

Demand Planning Concept

APO Application Architecture

Extracting Transaction Data

Data Storage in DP / SNP

 Data stored in buckets, no reference

 Data stored with reference to orders

 Data stored in infocube

Properties of an SAP application with SAP liveCache technology:

APO Core Interface (CIF)

© Copyright IBM Corporation 2003

What is Core Interface ?

 APO Core Interface

APO Core Interface (CIF)

 APO software includes a communication layer to enable integration between APO

ERP -> APO APO -> ERP

CIF Setup and Related Configuration Tasks

However, the required CIF settings

Some useful transaction for CIF setting in R/3 and APO

Initial CIF Settings – R/3 Initial CIF Settings – APO

Some Useful transaction related to CIF in R/3 and APO

CIF related transaction – R/3 CIF related transaction – APO

Overview of data creation in CIF

Transfer of Master Data

•Incremental data transfer

•Transaction Code : CIF-EA

•Integration Model distinguishes between

•You can have multiple integration models.

•Creation, Change, Display, Deletion possible

Integration Model – Initial Data Transfer

1. • Generate integration model •Name

•Determine name and APO

2. •Activate integration model