181182067-APO-Overview-ppt.ppt

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

Presentation Title | Confidential | Document ID Advanced Planning and Optimizer
2
 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
General Topics

3
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.

4
SAP’s Vision of SCM
ADAPTIVE SUPPLY CHAIN NETWORK
TODAY’S SEQUENTIAL SUPPLY CHAIN
SAP Transforms

5
SAP SCM – Where does it fit
SAP SCM
SAP PLM
SAP
SRM
SAP
CRM
SAP ERP
Financials
Human Resources
Corporate Services
Operations
Maintenance & Quality
Inventory & Production
Sales
Order
&
Distribution
Management
Purchase
Order
Management
SAP NetWeaver
SAP Business Suite

6
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

8
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.

9
Advanced Planning and Optimizer contd…

10
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.

11
The Complete SCM Solution
Private
Exchanges
Vendor
Partner Partner
Customer
Supplier
Relationship
Management
(SRM)
Scheduling agreement
release
Source Deliver
Availability Check
(ATP)
Transportation Planning
(TP/VS)
Make
Production Planning/
Detailed Scheduling
(PP/DS)
Demand Planning
(DP)
Plan
Supply Network
Planning
(SNP)
Supply Chain Performance Management
Measure
Supply Chain Event Management
Monitor
Dyn.
Supply
Chain
Cooperation
Dyn.
Supply
Chain
Cooperation
Private
Exchanges

12
Supply Chain Planning: Why do companies need it?
Customers
Storage
Locations
Plants
Suppliers
Balance & optimize supply and demand
DEMAND
SUPPLY

DP SNP PP DS
SAP APO Components

14
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.
Demand Planning
Suppliers Manufacturer Distribution Retailer Consumer
Reuse/Maintenance/After Sales Service
Product/Services
Information
Demand and Cash flow

15
Supply Chain Planning at a Glance

16
Factors that Influence Demand Planning and SNP

17
Overview of SAP APO Demand Planning

18
Demand Planning Concept

19
APO Application Architecture

20
Extracting Transaction Data

21
Data Storage in DP / SNP
 In liveCache time
series objects
 In liveCache orders
 In an InfoCube
 Data stored in buckets, no reference
to orders
 Suitable for tactical planning (DP)
 Data stored with reference to orders
 Suitable for operative planning (SNP)
 Data stored in infocube
 Suitable for old planning data (like
sales history – based on which
forecasting can be carried out)

22
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)

24
Overview of CIF

25
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.

26
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.

27
APO
APO
APO
BW
ERP
ERP ERP
ERP
ERP -> APO
Master Data
 Locations
 Products
 PPMs (BOM+Routing)
 Characteristics
 Capacities
Transaction Data
 Planned/Production
Orders
 Sales Orders
 Purchase Orders
 Stocks
 ATP Requests
APO -> ERP
Planning Results
 ATP Results
 Manufacturing Orders
 Procurement Orders
 VMI Sales Orders
CIF Functions

28
CIF Setup and Related Configuration Tasks
 R/3
- Set up a logical system
- Assign LS to client
- Set up RFC destination
- Define target system (same name
as the RFC destination)
 APO
- Set up a logical system
- Assign LS to client
- Set up business system
group
- 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

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

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

31
Overview of data creation in CIF
R3 to APO

32
Transfer of Master Data
•R/3 •APO
•Location
•Product
•Resource
•Production
process model
•R/3 master data •APO master data
•Plant
•Customer
•Vendor
•Material master
•Capacity
•Routing and
•bill of material
•Initial transfer
•Incremental data transfer

33
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

34
Integration Model – Initial Data Transfer
1. • Generate integration model •Name
•Target system
•Plant
•Material master
•Resource
•...
•Determine name and APO
•target system
•Select master data
2. •Activate integration model
•Integration model is active
•Master data will be transferred
•Start

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

36
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

37
Selection Criteria – MRP Type X0
MRP type X0
MRP procedure X
Without MRP,
with BOM explosion
Mat. A
X0
Mat. B
X0
Mat. C
X0
Mat. D
VB
R/3
Planning in
APO
Product C
Product B
Product A
Material master D
Material master C
Material master B
Material master A
Integration model
Name PUMP
Target s. APOCLNT800
Applic. MATERIALS
Material master
Customers
Relevant materials
Material
Plant 1000
MRP type X0
...
...
Material
status
APO

38
Which Products to plan in APO ?
Planning type APO
recommended
Possible
in APO
APO not
recommended
Externally procured products
with long replenishment times
X
Products manufactured
in-house at bottleneck
resources
X
Products that are not
critical for planning
X
(Non-critical) products
planned with reorder
point planning
X
(Non-critical) products
planned with KANBAN
X

39
Transfer of New APO-Relevant Master Data
New material (Product Q) to be
transferred to APO
Integration Model-1 : Products A & B at 10:00 hrs
Execute Save
+
Existing integration model
"Activate"
Active/
Inact
.
Integration Model-1 : Products A,B,Q at 11:00 hrs
Integration Model-1 : Products A & B at 10:00 hrs
Transfer of only Product Q happens
Active
Inactive
New Data Transfer Regenerate Data
Integr Model-1 : Products A & B at 10:00 hrs
Deactivate Model
Activate Model
Re-Transfer of Product A, B & Q happens

40
Transfer of New APO-Relevant Master Data
The system re-generates the existing
model (the new master data is also
selected here) and then activates it.
Two models with the same name are
then active, the only differences being
the dates and times. If the data
transfer starts in this situation, the
system simply transfers the difference
data.
After the data transfer, the system
deactivates the "old" integration model,
leaving the "new" complete integration
model as the active model.
New Data Transfer Regenerate Data Transfer
If you want the system to retransfer all
the master data of an existing
integration model, you must deactivate
the old models and activate only the
new one.
A comparison of all active models then
takes place. As in this case, the model
with the old time is not active, all data
is transferred again.

41
Incremental Data Transfer
Transaction CFC9
Business Transaction Event, immed.
Material master
ALE change pointer, periodic
no incremental data transfer
Customers
Vendors
Changed R/3 master data
objects are transferred into
APO when the changes are
saved in real-time
APO
Changes to R/3 master data
objects are recorded and the
transfer of the changes is
(periodically, for example)
triggered
Incremental Data Transfer

42
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.
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
ALE Change Pointer Settings

43
Field Mapping between R3 and APO
 Refer to the attached document for details
Master Data Mapping
Between R3 and APO
Transactional Data Mapping
Between R3 and APO

44
Transactional Data Transfer – R3 to APO
Initial data
transfer
R/3
APO
Order with category
BF (PchOrd)
AG (PurRqs)
BM (SalesOrder )
AI (PlOrd.)
FA (FC req.)
AM (PrdRes)
CC (Stock)
...
R/3 transaction data APO transaction data
Purchase orders
Purchase requisitions
Sales orders
Planned orders
Planned ind.reqmts
Reservations
Stocks
...
Real-
time
Incremental
data transfer
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
Initial data transfer
takes through CIF
New transactional data
or changes to existing
transactional data are
transferred
automatically (real-
time)
Methodology of transfer
is same (using
Integration Models)

45
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).

46
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

47
Creation of integration model
variant

48
Integration model variant creation
CFM1 – Creation of
Variant

49
Periodic Data Transfers through Batch Jobs
Name PUMPS
Target system APOCLNT800
Application MATERIALS
Generate integration model
Name PUMPS
Target system APOCLNT800
Application MATERIALS
Activate integration model
Active/ Inact .
...
Execute
Save
+
Variant
PUMP_MAT
RIMODGEN report
Variant
PUMP_MAT
Start
RIMODAC2 report
JOB_1
+
JOB_2
alternative:
JOB_1_AND_2
Step 1
Step 2

50
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.
Material master A
Mat.planning
Plan. deliv .time 10 days
11 days
Master data
change
Change pointer
Matl . A Plan. deliv . time
...
Matl . B in-house pro. time
Customizing
Changed master
data in APO
Execute
Incremental
data transfer
Product A
Change pointer generally active?
Relevant message type
active?
Target sys. APOCLNT800
Material master ...
Object types
Variant
DELTA_MAT
MRP type X0
Incremental data transfer
APO
Delete change pointers regularly
Material master A
Mat.planning
11 days
Master data
change
Change pointer
Matl . A Plan. deliv . time
...
Matl . B in-house pro. time
Customizing
Changed master
data in APO
Execute
Incremental
data transfer
Product A
Change pointer generally active?
Relevant message type
active?
Target sys. APOCLNT800
Material master ...
Object types
Variant
DELTA_MAT
MRP type X0
Incremental data transfer
APO

51
Overview about Outbound queues and
Inbound Queues

52
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.

53
Communication Method
The queue for communication might be of two
types :
Outbound Queue
Inbound Queue

54
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

55
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

56
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

57
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

58
Steps to follow – Data Transfer from R3 to APO
Data not found
in APO
Check R/3
application log
(T-Code: CFG1)
Check R/3 qRFC
Monitor
(T-Code: SMQ1)
Check existence of
active integration
model
Check queue status Correct error Reactivate queue
in R/3 and
retransfer
Check APO application log
(T-Code: /SAPAPO/C3)
Correct error
No
Yes
Yes
No

59
Steps to follow – Data Transfer from APO to R3
Data not found
in R/3
Check APO application
log
(T-Code: /SAPAPO/C3)
Check APO qRFC
Monitor
(T-Code: SMQ1)
Check existence of
active integration
model
Check queue
status
Correct error Reactivate queue
in APO and
retransfer
Check R/3 application log
(T-Code: CFG1)
Correct error
No
Yes
Yes
No

CIF Debugging

61
Module Objectives
At the conclusion of this unit, you will be able to:
- Maintain Configurations for CIF Debugging
- Debug CIF Queue Inbound and Outbound

62
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

63
CIF Debugging
 Contents
- Inbound/Outbound Queue
 Configurations
 Case Study

64
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))

65
Example
 Outbound Queue
CIF Debugging
Outbound
 Inbound Queue
CIF Debugging
Inbound

Appendix

67
CIF Monitoring
Application
log
R/3:
Error
R/3 APO
RFC
Core Interface
Core Interface
Core Interface
Master/
transaction data
Master/
transaction data
APO master/
transaction data
live
Cache
live
Cache
- Communication errors
- Application errors
RFC
Application
log
APO:
Error

68
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)

69
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.

70
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*

71
qRFC Status and their Implications
•Refer to the attached document

72
Data Inconsistency between R3 and APO – CIF Delta Report
R/3 Report /SAPAPO/CIF_DELTAREPORT2
Sales orders
Objects to be checked
Production/process orders
Purchase requisition
APO
Partner system (R/3) R3CLNT800
Material P-102
Plant 100
Integration model Pump
...
...
Storage location stocks
Sales order stocks
...
...
(optional)
(optional)
(optional)
live
Cache
Database
Compare

73
Demand Planning and SNP process flow

74
Technical Components of APO for development
Refer to the following document
Includes
- BAPI
- BADI
- EXIT
- Report
- Table

75
Questions and Answers

76
Congratulations!
 Congratulations for completing this
training
 Thanks for your participation!

181182067-APO-Overview-ppt.ppt

Recommended

Recommended

More Related Content

Similar to 181182067-APO-Overview-ppt.ppt

Similar to 181182067-APO-Overview-ppt.ppt (20)

Recently uploaded

Recently uploaded (20)

181182067-APO-Overview-ppt.ppt