1. 1
Overview 8
Backup&Recovery 2
Software Maintenance 9
Optimizer 3
Sizing&Platform 10
Performance 4
Interface 11
Others 5
APO&BW 6
CIF 7
liveCache

2. Integration - BW & APO ERP ERP APO ERP ERP Communication APO -> BW
Customer Information
Sales History
POS Information, ...
Costs
Transport Costs
Production Costs, ...
Performance Figures
Shipping Rate,
Throughput, ...
APO -> BW
Forecasts
Communication
APO <-> APO
Demand
Capacity to Deploy
Production Plans
...
APO
APO
ERP BW
ERP
ERP
APO
ERP

3. Integration: ERP & APO ERP APO ERP BW ERP ERP APO ERP ERP  APO
Master Data
Plants, vendors, customers
Materials, products
Bills of material and routing (production process models)
Characteristics
Capacities
APO  ERP
Planning Results
ATP results
Manufacturing orders
Procurement orders
VMI sales orders
Transactional Data
Planned/production orders
Sales orders
Purchase orders
Stocks
ATP requests
ERP
APO
ERP BW
ERP
The ERP system provides master data and transactional data for planning to an APO system, and receives back the planning results.
The ERP system remains the dominant system for the master data. The APO system cannot change the master data in an SAP OLTP (ERP) system. However, the APO system can create and modify its own master data in the APO database (for example, it can maintain some table fields).
Simulation results for planning runs are not sent to the SAP OLTP system.
ERP
APO
ERP

4. Interface Scenario Non-SAP System CIF BAPIs SAP APO Internet SAP OLTPLO SD HR
qRFC
BAPI
CIF
(Core Interface)
BAPI
BAPIs
SAP APO
BAPI
Two different integration techniques are used to link an APO system and ERP systems.
Linkage of APO with one or more SAP OLTP systems:
The required interface is called the APO Core Interface (CIF). It defines and controls the data transfer between SAP OLTP systems and APO systems.
The CIF interface is an add-on to an SAP R/3 System that is installed using the relevant R/3 Plug-In.
CIF uses queued remote function calls (qRFC). This guarantees serialization and update in the target system.
Linkage of APO with non-SAP systems:
The required interfaces are implemented as Business Application Programming Interfaces (BAPIs). BAPIs are documented standard interfaces that enable object-oriented access to SAP systems (via C++, Java, Visual Basic, IDocs, COM/DCOM, ...).
Comm.-
IDoc
Internet
RFC

5. APO Core Interface APO Core Interface (CIF)
Connects an APO and a standard SAP OLTP 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
The APO CIF:
Is used to connect the APO to SAP OLTP systems
Provides a tight coupling between APO and one or more SAP OLTP systems
Is a real-time interface
Ensures the supply of relevant incremental data changes to APO
An integration model is defined in an SAP OLTP system. This model is used to select the data objects that are needed in APO’s streamlined data structures and that must be transferred from the SAP’s complex data tables via CIF.

6. APO Core Interface
Add-on Component to a R/3 systemData Exchange between APO and R/3
Supply APO with Planning and Optimization Relevant Data from R/3(Master and Transaction)
Return APO Planning Results to R/3
Initial and Incremental Data Transfer (Automatic Switch)
Determines source and target system within complex system environments.
Real-time interface.
Event-driven transmission of changes to APO
Also called
NDI(New Dimension Interface) Plug-in
R/3 Plug-in
After transferring initial data, only new or changed data is transferred.
Master data changes are forwarded to APO in packets via batch jobs.
Transaction data changes are forwarded to APO in real-time.

7. Plug-in Versions Modifying Version : PI Non-Modifying Version : PI-A
CRT Specific
Such as APO, CRM, SEM
Non-Modifying Version : PI-A
CRT Independent
Such as BW, BBP
Releases >= 4.0B, No more CRT after PI
* Maintenance planned until Sep. 2004
**Maintenance planned until Dec. 2003
***Maintenance planned until Jun. 2005
C.f. BW 3.0A is out of maintenance

8. Data Transmission Standard SAP OLTP APO liveCache APO DB Initial
Transfer
Incremental
Master Data
Transactional Data
APO DB
liveCache
Master data representing the current factory layout on the OLTP side is mapped into a consistent data pool that is transmitted into APO. This data is made of information such as products, business partners, and work centers. Running operations on the OLTP side need not be interrupted when this transfer is made.
Modes of operation are separated into initial data transfer and incremental transfer. The first data transfer including basic data sets is called initial, and the transfer of changes is called incremental. Later, any necessary incremental transfers that include only changes of data on the OLTP side are filtered and routed to APO automatically (either periodically or, if there is a need, immediately).
Guaranteeing the referential integrity of these data pools is a major benefit of connecting APO to an SAP OLTP system.
Transactional data is data that changes often, like
Sales orders
Process orders
Production orders
Logically, the procedure for transmitting transactional data is similar to that for master data. Two modes for this transmission exist: initial and incremental. After the initial transfer, only data changes need to be forwarded. Transactional data is required in real time, or as close to real time as possible. Therefore, incremental transfer is event driven: within each transaction containing a change of a planning-relevant element in the OLTP system, the change is sent simultaneously to APO.

9. Business System Groups
Each source R/3 system and APO itself must be assigned to a BSG
For easy master data maintenance in APO , the APO system is in the same BSG as the R/3 system where the majority of the master data is from. Otherwise, master data maintenance has to be done locally (separately) for each system.
Within standard SAP systems, an integration model is used to integrate the corresponding SAP client with an APO client. This involves creating a link from a logical system in the OLTP system to a logical system in APO, based on a RFC destination with the name of the target logical system.
In the example shown in the graphic, each OLTP system needs a logical system defined for its own client (and assigned to it) and a logical system for the APO client. So logical systems 1 and 4 must be defined within the first OLTP system. The APO system needs a logical system defined for its own client and a logical system for every OLTP system to be linked to it. So logical systems 1, 2, 3, and 4 must be defined within the APO system.
A Business System Group (BSG) integrates the APO logical system and one or more SAP OLTP logical systems into a higher level logical unit from the point of view of APO. An RFC destination must be defined in the APO system for every target OLTP logical system.
APO uses BSGs to differentiate master data from different source systems with identical material numbers. In the example shown in the graphic, material number P1 identifies (the same type of) a screw in logical systems 1 and 2 whereas the same material number identifies a hammer in logical system 3. To resolve this conflict and to be able to transfer all these SAP material numbers into APO, logical system 3 needs to be assigned to a different business system group than logical systems 1 and 2. The APO system internally uses BSG names to create unique material numbers.
There must always be at least one business system group defined within APO. Both APO and each linked SAP OLTP system must be assigned to exactly one BSG. For APO itself, it does not matter which BSG it is assigned to. Each BSG must contain at least one SAP source system, and different master data objects must have unique names within the group. More than one BSG is only necessary if there is no unique naming convention within all SAP systems linked to the APO.

10. Interface setup Define logical system
Create CIF logon user in the target APO system
Security profile: SAP_ALL, S_RS_ALL, S_BI-WHM_RFC
Type: Dialog or Service as of 46C
Note
Create CIF logon user in the source R/3 system
Security profile: SAP_ALL, S_BI-WX_RFC, S_ENTW
Create RFC connection
Set tRFC option to a limited number of retries, e.g., 2 or 3 retries with 10min interval

11. Interface setup Maintain APO release Transaction NDV2(R/3)
Use RFC-Destination name for target APO system
Use SAP_APO for the system type
The release of the target APO system: (30A for APO 3.0A, 31 for APO 3.1 etc.)

12. Interface setup Maintain target system Transaction CFC1(R/3)
Use RFC-Destination name for target APO system
Operation mode T for Transactional Events Active (standard)
Q-Type: Queue RFC (Blank)

13. Interface setup Define Business System Group(BSG)
Transaction /SAPAPO/C1(APO)
Assign logical system to BSG
Transaction /SAPAPO/C2(APO)
Two different logical systems with identical number ranges are operating when a distributed system landscape is constructed with APO, the identical names must be changed with a customer exit.
APO_CIAPOCF001 EXIT_/SAPAPO/SAPLCIF_LOC_001: Location
APO_CIAPOCF002 EXIT_/SAPAPO/SAPLCIF_ATP_001: Maintain ATP check control
APO_CIAPOCF003 EXIT_/SAPAPO/SAPLCIF_IRQ_001: Reduction of planned indep. req.
APO_CIAPOCF004 EXIT_/SAPAPO/SAPLCIF_ORD_001: Production and planned orders
APO_CIAPOCF005 EXIT_/SAPAPO/SAPLCIF_PROD_001: Products
APO_CIAPOCF006 EXIT_/SAPAPO/SAPLCIF_PU_001: Purchase order documents
APO_CIAPOCF007 EXIT_/SAPAPO/SAPLCIF_QUOT_001: Quotas and their schedules;
EXIT_/SAPAPO/SAPLCIF_QUOT_001: Customizing settings quotas
APO_CIAPOCF008 EXIT_/SAPAPO/SAPLCIF_RES_001: Resource
APO_CIAPOCF009 EXIT_/SAPAPO/SAPLCIF_RSV_001: Reservation requirement
APO_CIAPOCF010 EXIT_/SAPAPO/SAPLCIF_SLS_001: Sales order
APO_CIAPOCF011 EXIT_/SAPAPO/SAPLCIF_STOCK_001: Stock

14. Interface setup Activate Global Change Pointer
Transaction BD61(R/3)
Activate Business Transaction Event for APO
Transaction BF11(R/3)
Check the active field for the appl. ‘ND-APO’ and ‘NDI’

15. Interface setup Change Pointer for Message Type Transaction BD50(R/3)
CIFMAT: material master(active)
CIFVEN: vendors(active)
CIFCUS: customers(active)
CIFSRC: info records(optional)
CIFPPM: BOMs and Routings(optional)

16. Interface setup User parameter in R/3 User parameter in APO
Transaction CFC2
User parameter in APO
Transaction /SAPAPO/C4

17. Interface setup User parameter in APO Object parameter
Transaction /SAPAPO/C41
Object parameter
Transaction CFC3(R/3)
Note

18. Interface setup Control for Change data transfer of master data
Transaction CFC5(R/3)
The setting will be customized by application team members.
The actual transfer of the changed entry will be performed by the transaction CFP1 under the option ‘1’ was chosen.

19. Interface setup Monitor for tranfer of transaction data
Transaction CFP2(R/3)
The status for all the data type should be in green traffic icon.
This transaction is also used to stop temporarily the transaction data transfer.

20. Interface setup
Scheduling jobs for deleting log