Apo core interface cif

APO Core APO Core Interface (CIF)Interface (CIF)

ContentsContents Introduction to Core Interface (CIF) Role of CIF Components of CIF – Integration Models Data Transfer (Master Data and Transactional Data) CIF Monitoring

Introduction to CIFIntroduction to CIF

What is Core Interface ?What is Core Interface ?

► APO Core InterfaceAPO Core Interface connects an APO and a standard R/3 systemconnects an APO and a standard R/3 system

► determines source and target systems within complex determines source and target systems within complex system environments through Integration Modelssystem environments through Integration Models

supplies APO with the relevant master and transaction datasupplies APO with the relevant master and transaction data► transfer of planning relevant data onlytransfer of planning relevant data only► initial and incremental data transfer initial and incremental data transfer ► real-time interfacereal-time interface

returns planning results to the OLTP systemreturns 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 Core Interface (CIF)

► APO software includes a communication layer to enable integration APO software includes a communication layer to enable integration between APO and OLTP systems (eg. R/3 system).between APO and OLTP systems (eg. R/3 system).

► APO CIF is the communication layer to be applied to R/3 to enable 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 integration of R/3 system with APO system. There is a similar communication layer which comes as a standard function in the APO communication layer which comes as a standard function in the APO system. system.

► APO CIF is a APO CIF is a real-time interfacereal-time interface between R/3 & APO system between R/3 & APO system► The main roles of CIF are :The main roles of CIF are :

- Determine source and target systems- Determine source and target systems- Initially supply APO with master and transactional data- Initially supply APO with master and transactional data- Incrementally keep on supplying APO with transactional data- Incrementally keep on supplying APO with transactional data- Return planning results to R/3 system- Return planning results to R/3 system

► In order to integrate two systems together, data mapping must take In order to integrate two systems together, data mapping must take place. Data mapping includes matching up table/structure names and place. Data mapping includes matching up table/structure names and field names between systems.field names between systems.

► CIF integration models provide CIF integration models provide automatic data mapping between R/3 automatic data mapping between R/3 objects and the corresponding objects in APO.objects and the corresponding objects in APO.

► Between non-R/3 ERP and APO, other interfaces like BAPI or ALE are Between non-R/3 ERP and APO, other interfaces like BAPI or ALE are used.used.

APOAPO

APOAPO

APOAPOBWBWERPERP

ERPERP ERPERP

ERPERP

ERP -> APOMaster Data

Locations Products PPMs (BOM+Routing) Characteristics Capacities

Transaction Data

Planned/Production Orders

Sales Orders Purchase Orders Stocks ATP Requests

APO -> ERPPlanning Results

ATP Results Manufacturing Orders Procurement Orders VMI Sales Orders

CIF FunctionsCIF Functions

CIF Setup and Related CIF Setup and Related Configuration TasksConfiguration Tasks

► R/3R/3

Set up a logical systemSet up a logical system

Assign LS to clientAssign LS to client

Set up RFC destinationSet up RFC destination

Define target system (same Define target system (same

name as the RFC destination)name as the RFC destination)

► APOAPO

Set up a logical Set up a logical

systemsystem

Assign LS to clientAssign LS to client

Set up business Set up business

system groupsystem group

Assign LS to BSGAssign LS to BSGNote : Details of the CIF configurations are not covered in this training

However, the required CIF settings are mentioned in the attached document for reference

Master Data Master Data TransferTransferR3 to APOR3 to APO

Transfer of Master DataTransfer 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

Integration ModelIntegration 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 Integration Model – Initial Data TransferData 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

Integration Model – Integration Model – GenerationGeneration

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 – Integration Model – ActivationActivation

• “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 Selection Criteria – MRP Type X0X0

MRP type X0

MRP procedure X

Without MRP, with BOM explosion

Mat. AX0

Mat. BX0

Mat. CX0

Mat. DVB

R/3R/3

Planning in

APO

Product CProduct B

Product A

Material master DMaterial master CMaterial 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

...

...

MaterialstatusAPO

Which Products to plan in APO ?

Planning type APOrecommended

Possiblein APO

APO notrecommended

Externally procured productswith long replenishment times

X

Products manufacturedin-house at bottleneckresources

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

Transfer of New APO-Transfer of New APO-Relevant Master DataRelevant 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 TransferNew Data Transfer Regenerate DataRegenerate Data

Integr Model-1 : Products A & B at 10:00 hrs

Deactivate Model

Activate Model

Re-Transfer of Product A, B & Q happens

Transfer of New APO-Transfer of New APO-Relevant Master DataRelevant 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 TransferNew Data Transfer Regenerate 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.

Periodic Data Transfers Periodic Data Transfers through Batch Jobsthrough 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

Incremental Data TransferIncremental Data TransferTransaction CFC5

Business Transaction Event, immed .

Material master

ALE change pointer, periodic

no incremental data transfer


Customers




Vendors



Changed R/3 master dataobjects are transferred intoAPO when the changes are

saved in real-time

APO

Changes to R/3 master dataobjects are recorded and the

transfer of the changes is(periodically, for example)

triggered

IncrementalIncremental Data Transfer Data Transfer

Incremental Data Transfer – Incremental Data Transfer – ALE Change PointersALE Change Pointers

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 SettingsALE Change Pointer Settings

Periodic Incremental Data Periodic Incremental Data Transfers through Batch JobsTransfers 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 AMat.planning

Plan. deliv .time 10 days

11 days

Master datachange

Change pointer

Matl . A Plan. deliv . time

...

Matl . B in-house pro. time

Customizing

Changed masterdata in APO

Execute

Incrementaldata transfer

Product A


Change pointer generally active?Relevant message type

active?

Target sys. APOCLNT800

Material master ...Object types

VariantDELTA_MAT

MRP type X0

Incremental data transfer

APO

Delete change pointers regularlyDelete change pointers regularly

Material master AMat.planning


11 days

Master datachange

Change pointer

Matl . A Plan. deliv . time

...

Matl . B in-house pro. time

Customizing

Changed masterdata in APO

Execute


Product A


Change pointer generally active?Relevant message type

active?

Target sys. APOCLNT800

Material master ...Object types

VariantDELTA_MAT

MRP type X0

Incremental data transfer

APO

Transactional Data Transactional Data TransferTransferR3 to APOR3 to APO

APO to R3 (Publication)APO to R3 (Publication)

Transactional Data Transfer Transactional Data Transfer – R3 to APO– R3 to APO

Initial datatransfer

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


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)

Publication of Planning Publication of Planning Results – APO to R3Results – APO to R3

► Planning Results are transferred from APO to R3, which is termed Planning Results are transferred from APO to R3, which is termed as Publicationas Publication

► Configuration in APO : Configuration in APO : Basic settings (publication of planning results)Basic settings (publication of planning results)

► specify for each plant and publication type (example, in-specify for each plant and publication type (example, in-house production or external procurement,etc), which R/3 house production or external procurement,etc), which R/3 System (logical system) to publish planning results.System (logical system) to publish planning results.

► For SNPFor SNP, you set the form for transferring SNP planning results to , you set the form for transferring SNP planning results to the R/3 System with the Customizing operation: the R/3 System with the Customizing operation: Set transfer to Set transfer to OLTP systemOLTP system. The default setting for SNP is that the changes are . The default setting for SNP is that the changes are collected and collected and transferred periodicallytransferred periodically..

► For PPDSFor PPDS : : In APO transaction /SAPAPO/C4 you set how (in what form) new 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. transaction data is to be transferred from APO PP/DS into R/3. It is usually a It is usually a real-time transferreal-time transfer (this is the default setting for (this is the default setting for PP/DS data). PP/DS data).

There is also the possibility of collecting the changes in APO There is also the possibility of collecting the changes in APO first, then transferring them to the R/3 as a collected group first, then transferring them to the R/3 as a collected group (transaction /SAPAPO/C5).(transaction /SAPAPO/C5).

Publication of Planning Publication of Planning ResultsResults

► Report Report : /SAPAPO/RDMCPPROCESS: /SAPAPO/RDMCPPROCESST-CodeT-Code : /SAPAPO/C5: /SAPAPO/C5Function ModuleFunction Module : /SAPAPO/DM_CP_PUB: /SAPAPO/DM_CP_PUB

► Orders that have been created, changed or deleted in APO Orders that have been created, changed or deleted in APO applications are published back to R/3 through the above applications are published back to R/3 through the above function module.function module.

► APO applications that can create, change, delete orders APO applications that can create, change, delete orders are:are:PP/DSPP/DS : Direct Publication: Direct PublicationSNPSNP : Periodic Publication: Periodic Publication

Publication of Planning Publication of Planning ResultsResults

► Publication settings (distribution definitions) in APO IMG needs to be done for Publication settings (distribution definitions) in APO IMG needs to be done for all objects (like planned order, planned order with conversion indicator, etc) all objects (like planned order, planned order with conversion indicator, etc) that have been created in APO.that have been created in APO.

► In case the following objects have been created in R/3 and then changed in In case the following objects have been created in R/3 and then changed in APO, the changed parameters can be published back to R/3 without any APO, the changed parameters can be published back to R/3 without any need to maintain the distribution definitions :need to maintain the distribution definitions :

# Sales Order# Sales Order # Inhouse Production# Inhouse Production# External Procurement# External Procurement # Production Campaign# Production Campaign

► However for the following objects, distribution definitions has to be defined However for the following objects, distribution definitions has to be defined irrespective of them being created in R/3 or not :irrespective of them being created in R/3 or not :

# PIR# PIR # Delivery# Delivery# Confirmation (IS Auto)# Confirmation (IS Auto) # Confirmation Deletion (IS Auto)# Confirmation Deletion (IS Auto)# Reservations# Reservations # Reporting Points (IS Auto)# Reporting Points (IS Auto)

Integration Model – Other Integration Model – Other FunctionsFunctions

Deactivate integration model+Connection between R/3 and APO for the relevant master and transaction data will be cancelled

+Deactivated models can be deleted

+You can check the consistency of the selected data in the integration model

Delete integration model

Consistency check

+Check whether the data objects are already contained within an integration model

Filter object search

Deactivate integration model+Connection between R/3 and APO for the relevant master and transaction data will be cancelled

+Deactivated models can be deleted

+You can check the consistency of the selected data in the integration model

Delete integration model

Consistency check

++Check whether the data objects are already contained within an integration model

Filter object search

CIF MonitoringCIF Monitoring

Data Transfer TechniqueData Transfer Technique

► Data transferred in both Data transferred in both directions (from R/3 to APO as well as from APO to directions (from R/3 to APO as well as from APO to R/3) by means of one or more R/3) by means of one or more queued Remote Function Calls (qRFC)queued Remote Function Calls (qRFC). .

► The function calls are buffered in the sending system and executed The function calls are buffered in the sending system and executed asynchronously in the same sequence they were called. This serialization is asynchronously in the same sequence they were called. This serialization is controlled by the use of identical queue names and is required to assure controlled by the use of identical queue names and is required to assure consistency.consistency.

► Multiple qRFCs can be combined into a Multiple qRFCs can be combined into a logical unit of work (LUW)logical unit of work (LUW), , whereby one LUW on the sender side results in one LUW on the receiver whereby one LUW on the sender side results in one LUW on the receiver side.side.

Steps for Data Transfer – (1)Steps for Data Transfer – (1)► The system transfers only the planning of the active planning version '000'.The system transfers only the planning of the active planning version '000'.► Product and location are assigned to the same business system group.In the R/3 Product and location are assigned to the same business system group.In the R/3

system, an active integration model exists for the respective material and plant.system, an active integration model exists for the respective material and plant.► The application (for example the PP/DS or the SNP) in the APO system creates The application (for example the PP/DS or the SNP) in the APO system creates

an event.The event includes the Type of Change (Add, Change, Delete) and the an event.The event includes the Type of Change (Add, Change, Delete) and the Internal Order Number.The system sends the event to a module of integration Internal Order Number.The system sends the event to a module of integration module CIF (Core Interface) and stores it there temporarily.module CIF (Core Interface) and stores it there temporarily.

► The system transfers the changes to the R/3 system at a certain time.Generally, The system transfers the changes to the R/3 system at a certain time.Generally, the system transfers changes as mentioned below:the system transfers changes as mentioned below: PP/DS : immediately (that is if you save the schedule in the APO system)PP/DS : immediately (that is if you save the schedule in the APO system) SNP : The system collects changes of the SNP and transfers them in blocks.SNP : The system collects changes of the SNP and transfers them in blocks.

► You can define deviations from this in Customizing.To do this, call You can define deviations from this in Customizing.To do this, call Transaction /SAPAPO/C4.In column 'Recording' you can define whether Transaction /SAPAPO/C4.In column 'Recording' you can define whether the system collects changes or not.the system collects changes or not.

► If the system collects changes, it has to transfer all collected changes If the system collects changes, it has to transfer all collected changes via Transaction /SAPAPO/C5.via Transaction /SAPAPO/C5.

► Alternatively, you can schedule a job periodically.Use report Alternatively, you can schedule a job periodically.Use report /SAPAPO/RDMCPPROCESS to do this./SAPAPO/RDMCPPROCESS to do this.

Steps for Data Transfer – (2)Steps for Data Transfer – (2)

► If the changes are collected, an order may be repeatedly changed If the changes are collected, an order may be repeatedly changed between two transfers. The system collects the events of an order, between two transfers. The system collects the events of an order, for which the following applies: for which the following applies:

Creating + Changing -> CreationCreating + Changing -> Creation Creating + Deleting -> No TransferCreating + Deleting -> No Transfer Changing + Deleting -> DeletionChanging + Deleting -> Deletion

► A conversion into CIF structures follows.This is especially a A conversion into CIF structures follows.This is especially a conversion of APO-intern product numbers and location numbers conversion of APO-intern product numbers and location numbers (Guids) into the external R/3 material numbers and plants. If order (Guids) into the external R/3 material numbers and plants. If order numbers are included (like in changes of existing orders), the numbers are included (like in changes of existing orders), the system also converts the APO-internal order number into the R/3 system also converts the APO-internal order number into the R/3 order number.order number.

► Then the system determines the receiver.Then the system determines the receiver.

► The system then sends the order data via qRFC to the R/3 system The system then sends the order data via qRFC to the R/3 system (the q in qRFC stands for queue).(the q in qRFC stands for queue).

Steps for Data Transfer – (3)Steps for Data Transfer – (3)

► In the R/3 system, the system first converts the order data coming from In the R/3 system, the system first converts the order data coming from the APO into R/3 format. The system converts them into a date and a time.the APO into R/3 format. The system converts them into a date and a time.

► During creation of new orders in the R/3 system, the system performs a During creation of new orders in the R/3 system, the system performs a number assignment in the R/3.The system must transfer this new number number assignment in the R/3.The system must transfer this new number back into the APO system, together with other changes to the order, which back into the APO system, together with other changes to the order, which may have been made in the R/3 system.The APO system then makes the may have been made in the R/3 system.The APO system then makes the assignment (mapping) between the R/3 order and the APO order and stores assignment (mapping) between the R/3 order and the APO order and stores it.it.

Communication MethodCommunication Method

The queue for The queue for communication might be of communication might be of two types :two types :

►Outbound QueueOutbound Queue►Inbound QueueInbound Queue

Communication Method - Communication Method - Outbound QueueOutbound Queue

► Calling system sends the queues to the receiving system without Calling system sends the queues to the receiving system without taking care of the system load of the receiving system.taking care of the system load of the receiving system.

► No scheduling of the processes happen in the receiving system.No scheduling of the processes happen in the receiving system.

► Effect : Effect :

- Overloading of receiving system - Overloading of receiving system - CIF performance deteriorates with high data volume- CIF performance deteriorates with high data volume

Communication Method - Communication Method - Inbound QueueInbound Queue

► Calling system sends the queues to the “entrance” (inbound) of the Calling system sends the queues to the “entrance” (inbound) of the receiving system which allows the receiving system to control the receiving system which allows the receiving system to control the system queue load on its own.system queue load on its own.

► Scheduling of the processes happen in the receiving system.Scheduling of the processes happen in the receiving system.

► Effect : Effect : - Better CIF performance- Better CIF performance

► To change from Outbound to Inbound Queue :To change from Outbound to Inbound Queue : Refer Notes 388001, 388528, 388677Refer Notes 388001, 388528, 388677

CIF Monitoring – Applications CIF Monitoring – Applications at a Glanceat a Glance

► On R3 sideOn R3 side

qRFC Monitor (Transaction CFQ1)qRFC Monitor (Transaction CFQ1) Application Log (Transaction CFG1)Application Log (Transaction CFG1)

► On APO sideOn APO side

qRFC Monitor (Transaction SMQ1)qRFC Monitor (Transaction SMQ1) Application Log (Transaction /n/SAPAPO/C3)Application Log (Transaction /n/SAPAPO/C3)

► Monitoring both R3 and APO from within APOMonitoring both R3 and APO from within APO

SCM Queue Manager (Transaction /n/SAPAPO/CQ)SCM Queue Manager (Transaction /n/SAPAPO/CQ) qRFC Alert (Transaction /n/SAPAPO/CW)qRFC Alert (Transaction /n/SAPAPO/CW)

Important Pre-Requisite at R3 Important Pre-Requisite at R3 and APO end (1)and APO end (1)

► Logging Mode to be switched on :Logging Mode to be switched on :► Transaction in R3 Transaction in R3 : CFC2: CFC2► Transaction in APOTransaction in APO : /SAPAPO/C41: /SAPAPO/C41

► NormalNormal the number of data records transferred is loggedthe number of data records transferred is logged

► Detailed Detailed the number and content of the data records transferred is loggedthe number and content of the data records transferred is logged

► Delete entriesDelete entries: : You can delete logs of the application log in R/3 and APO. You can delete logs of the application log in R/3 and APO. The system does not delete the logs automatically. The system does not delete the logs automatically. You can delete logs of the application log in R/3 and APO. You can delete logs of the application log in R/3 and APO. Recommendation : Deleting the logs periodically (schedule Recommendation : Deleting the logs periodically (schedule

background processing)background processing) Refer Next slide for further detailsRefer Next slide for further details

CIF MonitoringCIF Monitoring

Application

log

R/3:

Error

R/3 APO

RFCCore InterfaceCore InterfaceCore Interface

Master/

transaction data

Master/

transaction data

APO master/

transaction data

live

Cache

live

Cache

- Communication errors

- Application errors

RFC

Application

log

APO:

Error

CIF Monitoring – An ExampleCIF Monitoring – An Example

Example: Application Log in APOExample: Application Log in APO

RefreshAPO qRFC Monitor

MUSTER In-house production02.10.2002 120

User Subobject typeDate Number

APO Application Log

USERADMIN In-house production02.10.2002 1

User Subobject typeDate Number

R/3 Application Log

Problem class: very importantProblem class: mediumProblem class: additional information

Inbound R3CLNT800: For system APOCLNT800 no active integration

Function: /SAPAPO/CIF_IP_OUTBOUND: Order material P-102, plant 1000

MUSTER CIF_ORDER_INBOUND_30A800

Status text

No active integration model

Client User Function module

MUSTER CIF_ORDER_INBOUND_30A800 Transaction recorded

Example:Example:► A planned order for A planned order for

a finished product a finished product and purchase and purchase requisitions for the requisitions for the components of the components of the finished product finished product have been created have been created in APO. in APO.

► However, they However, they were not included were not included in any active in any active integration model integration model in the R/3 System in the R/3 System at the time when at the time when the order was the order was created in APO. created in APO.

► Therefore, the Therefore, the orders were not orders were not created in R/3 but created in R/3 but kept in the queuekept in the queue

Monitor Change TransferMonitor Change Transfer

► Report : RCPQUEUE (Use T-Code : SE38)Report : RCPQUEUE (Use T-Code : SE38)

► This report is used to monitor the transfer of Transaction Data. This This report is used to monitor the transfer of Transaction Data. This report can be used for :report can be used for :

¤ Checks the status of the active data channels - accordingly Checks the status of the active data channels - accordingly various data channels can be closed or opened.various data channels can be closed or opened.

¤ Display and analyze the objects to be transferred for each Display and analyze the objects to be transferred for each filter object filter object

The list of the data channels are given in next slide.The list of the data channels are given in next slide.

Data Channels Data-Object-Data Channels Data-Object-wisewise

► Initial supply Initial supply CF_ADC_LOAD CF_ADC_LOAD ► Stock Stock CFSTK* CFSTK* ► Purchase orders and purchase reqn Purchase orders and purchase reqn CFPO* CFPO* ► Planned orders/Production orders Planned orders/Production orders CFPLO* CFPLO* ► Sales orders Sales orders CFSLS* CFSLS* ► Manual reservations Manual reservations CFRSV* CFRSV* ► Confirmations Confirmations CFCNF* CFCNF* ► Planned independent Rqmnt Planned independent Rqmnt CFPIR* CFPIR* ► MaterialsMaterials CFMAT* CFMAT* ► Production campaigns Production campaigns CFPCM* CFPCM* ► Master data for classes Master data for classes CFCLA* CFCLA* ► Master data for characteristics Master data for characteristics CFCHR*CFCHR*

Steps to follow – Data Steps to follow – Data Transfer from R3 to APO 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

Steps to follow – Data Steps to follow – Data Transfer from APO to R3 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

Data Inconsistency between Data Inconsistency between R3 and APO – CIF Delta R3 and APO – CIF Delta

ReportReportR/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)

liveCacheDatabase

Compare

QuestionsQuestions

Thank You

Education

Apo core interface cif