cif management

1

CORE INTERFACE MANAGEMENT (CIF)

Objective The following document is an outline of all activities to properly manage the Interface between APO system and the R/3 SAP System. The activities include Data transfer programs, Manual analysis of errors, Clean up activities and scheduled clean up jobs. This document will outline the monitoring and clean up procedures used for the monitoring and maintenance of the APO Core interface. Each procedure will have a description, referenced Business Process procedure if required, frequency, responsibility and escalation path.

Overview of the APO Core Interface The Core Interface (CIF) is the communication layer between R/3 system and APO system. The CIF enables the exchange of data between the 2 systems. The main tasks of the SAP APO CIF include determination of the source and target systems, transfer of the initial relevant master data and transactional data, transfer of data changes, and return of published planning results from APO. Communication between R/3 and APO is based on the asynchronous transfer technology of the “queued remote function call” (qRFC). A remote function call (RFC) is when a function module in a different system is called. This technology is used in the integration between APO and R/3 both for the initial data supply and transfer of data changes ( from R/3 to APO) as well as for publication of planning results ( from APO to R/3)

2

Tools and Transactions

Integration Models

In the SAP R/3 System, you define in an integration model which master and transactional data objects are to be copied to SAP APO. Some of the objects that can be transferred are as follows

• Plants • Material masters • Customer masters • Vendor masters • Production process models (BOM and routing/recipe) • Planned Orders • Production orders • Purchasing Documents • Stock • Customer orders

The following is specified in the integration model.

• The APO target System

• The data objects you want to transfer

During the copy of data from R/3 to APO the integration model is first generated and then activated. Old Integration models are also deleted.

CFM1 - Generates the integration model. This transaction defines the master or transaction data that will transfer from R/3 to APO for the first time ( initial transfer)

( program RIMODGEN is used for background scheduling)

CFM2 - Activates the integration model. In this transaction you activate the integration model that was previously generated. This triggers the actual data transfer from R/3 to APO.

( program RIMODAC2 is used for background scheduling)

3

CFM7 - This program deletes old integration models. New integration models are generated every time the CIF is run in Batch ( all week days) All Old models are deleted after 7 days as part of the CIF job stream.

( program RIMODEL is used for background scheduling)

RAPOKZFX - This program detects and corrects inconsistencies between material master and integration models. In rare cases, inconsistencies occur between data in integration models and field APOZK in table MARC.

RCIFIMAX – This report finds inconsistencies between the integration models and their run time versions.

qRFC Monitoring

Communication between R/3 and APO is based on the asynchronous transfer technique queued Remote Function Call (qRFC). This technique is used in the integration of SAP APO with an R/3 System, both for the initial data supply and incremental supply (R/3 � APO) and for the publication of planning results (APO � R/3).

The data is first buffered by the system it is sent from, then transferred to the target system. The advantage is that the initializing application does not have to wait for the update to be completed in the target system. However, return parameters cannot be delivered which means that potential error messages cannot be directly returned to the application.

The system differentiates between two types of error when processing qRFC modules:

1. Communication errors These include:

o Network problems o A non-existent RFC destination, etc.

Due to periodic repetition of the data transfer, communication problems should disappear of their own accord as soon as the network connection is available again.

2. Application errors These include:

o Program errors o Non-posting of data to the target system o Locking of objects o Missing master data for transaction data

Application problems must be solved by a system administrator.

4

The qRFC is the central instance for monitoring application errors. It is available in both R/3 and APO. All transfer channels (queues) are displayed for all target systems.

APO qRFC Alert Report: /SAPAPO/RCIFQUEUECHECK - The report ensures the sending of queue block notification in case of outbound CIF errors The APO production Support team is notified of Outbound queue blocks via lotus notes email. If the issue must be resolved at the plant level a subsequent note is sent to the superuser APO qRFC Alert Report: /SAPAPO/RCIFINQUEUECHECK - The report ensures the sending of queue block notification in case of inbound CIF errors The APO production Support team is notified of inbound queue blocks via lotus notes email. If the issue must be resolved at the plant level a subsequent note is sent to the superuser R/3 - SMQ1- qRFC outbound queue Monitor - This transaction enables you to check outbound queues on the R/3 system. APO – SMQ1 - qRFC outbound queue Monitor - This transaction enables you to check outbound queues on the APO system R/3 – SMQ2 - qRFC inbound queue Monitor - This transaction enables you to check inbound queues on the R/3 system APO – SMQ2 - qRFC inbound queue Monitor - This transaction enables you to check inbound queues on the APO system SCM Queue Manager

With the SCM queue Manager you can monitor both outbound and inbound queues. Instead of evaluation the monitors in both systems (R/3 and APO) separately when errors occur, the user can use the central SCM Queue Manager and application logs in both systems centrally.

If a blocked queue is identified in the qRFC alert and the nature of the message is master data or transactional data in nature the super user will be notified.

The super user can use this transaction to review and re-activate queues. Additional data can also be seen as this transaction automatically links to the target systems application log.

5

Application Logs All messaging for transfers between APO and R/3 is logged in the application log. You can use the application log to trace when (time) and What (data objects and integration model) was transferred by whom ( user). In Addition, the application log provides a detailed error message if an application error occurred, the. Logging must be enabled in APO configuration R/3 Application Log – CFG1. Displays all messaging in R/3 APO Application Log - /SAPAPO/C3 - Displays all messaging in APO APO report /SAPAPO/RDELLOG - Program to delete old Application logs in APO R/3 report RDELALOG - Program to delete old Application logs in R/3 CIF Post Processing CIF error handling ensures that all CIF queue entries are processing during the data transfer. This applies to transactional data only; master and initial data transfer are exempt from CIF error handling. Faulty queues no longer lead to queues blocks. Instead, they are logged in post processing records in the relevant target system for the data transfer. You can then call these post-processing records at a later point in time in CIF Post processing. Once the error has been corrected you can again send the objects to the relevant target system /SAPAPO/CPP - CIF Post Processing APO report CIF/POSTPROC_ALERT - This report ensures sending of emails incase CIF error handling generates post processing records APO report /sapapo/CIFPOSTPROC_REORG - This report deletes old post -processing records

6

CIF Delta Reports

You can use the CIF delta reports to Identify and correct data inconsistencies between R/3 and SAP APO. The function covers unavailable and inconsistent objects. In SAP APO, the function covers the following objects: stock, sales order, planned order, production order, purchase orders, and purchase requisitions.

When you use the Compare/Reconcile function, a comparison is first of all carried out and the inconsistent objects identified in this process are listed. Then you can select individual, several, or all objects for the Reconcile. The selected data can be send from R/3 to SAP APO.

APO report /SAPAPO/CIF_DELTAREPORT3 - This report checks the external consistency between R/3 and APO and allows correction

APO report /SAPAPO/CIF_DELTAREPORT3_REOR - This report deletes old delta reports

Core Interface Monitoring Objects

Monitoring Object Description TRX Monitor Frequency

Indication or Error

Monitor Activity or Error handling Procedure

R/3 Reports RIMODGEN and RIMODAC2

Creation and Generation of the Integration Models SM37 daily status

Check if job is running as scheduled. ALL CIF jobs are part of APO_SAP_CIF_JOBS Monitoring Report

R/3 Report RIMODEL

This report deletes old integration models SM37 weekly Status

Check if job is running as scheduled. Part APO SAP CIF monitoring report

Inte

gra

tio

n M

od

el

Pro

gra

ms

R/3 Report RAPOKZFX.

This report detects and corrects inconsistencies between material master and integration models SM37 Daily Status

Check if job is running as scheduled. Part APO SAP CIF monitoring report

7

Output of Report RAPOKZFX.

List any inconsistencies found SP01 Daily Errors Listed

Check for material/Plant Combinations where correction of APOKZ was not carried out. ( due to lock problems) If errors are reported determine why material is locked and rerun job when lock is released

R/3 report RCIFIMAX

This report detects and corrects inconsistencies between integration models and runtime version SM37 D Status

Check if job is running as scheduled. Included in APO_SAP_CIF_JOBS monitoring report

Output of Report RCIFIMAX

List any inconsistencies found SP01 D

Inconsistencies listed

Check for items listed and reconcile inconsistencies by using the generation option of the report RCIFIMAX

APO report /SAPAPO/RCIFINQUEUECHECK the report ensures sending of emails in case of CIF inbound queue errors

the report ensures sending of e-mails in case of outbound CIF errors SM37 D Status

Check if job is running as scheduled. Job is scheduled every 15 minutes, ADD to CIF Monitoring report

APO report /SAPAPO/RCIFQUEUECHECK the report ensures sending of emails in case of CIF outbound queue errors

the report ensures sending of emails in case of CIF inbound queue errors SM37 D Status

Check if job is running as scheduled. Job is scheduled every 15 minutes. ADD to CIF Monitoring report

qR

FC

Mo

nit

ori

ng

R/3 Monitor qRFC outbound queues

This transaction enables you to check outbound queues on the R/3 system SMQ1

if errors are mailed by /SAPAPO/CIFQUEUECHECK

Queue Status of entries with queue names CF*

For queue status, see Note 378903

8

APO Monitor Outbound Queues

This transaction enables you to check outbound queues on the APO system SMQ1

if errors are mailed by /SAPAPO/CIFQUEUECHECK



R/3 Monitor qRFC inbound queues

This transaction enables you to check inbound queues on the R/3 system SMQ2

if errors are mailed by /SAPAPO/CIFINQUEUECHECK



APO Monitor qRFC inbound Queues

This transaction enables you to check inbound queues on the APO system SMQ2




SC

M Q

ue

ue

Ma

nag

er

APO:SCM Queue Manager.

This transaction enables you to check all qRFC queues on the local APO and all connected R/3 systems

/SAPAPO/CQ


Queue Indicator

Check if red or yellow queue indicators are displayed. Can be used instead of SMQ1 and SMQ2. If error is something that the business user must address. Example: master data. The queue data should be sent to the correct super user for correction. If the queue is inbound it can be saved. Save LUW so that the block is cleared. The super user can review in SMQ3.

Ap

pli

ca

tio

n

Lo

g

R/3 Application Log CFG1 D Log Class

Check if there are very important logs ( flagged red) or important logs ( flagged yellow)

9

APO Application Log

/SAPAPO/C3 D Log Class

Check if there are very important logs ( flagged red) or important logs ( flagged yellow)

APO report /SAPAPO/RDELLOG

This report deletes old application logs in APO SM37 W Status

Check if job is running as scheduled. Added to CIF monitoring report

R/3 report RDELALOG

This report deletes old application logs in R/3 SM37 W Status

Check if job is running as scheduled. Added to CIF monitoring report

APO reporte /SAPAPO/CIF_POSTPROC_ALERT

This report ensures sending of emails incase CIF error handling generates post processing records SM37 D Status

Check if job is running as scheduled. Pa

Post Processing of CIF error handling

CIF error handling ensures that ALL CIF queues are processed during the data transfer. Applies to trx data only. Faulty queues are logged here for clean up later

/SAPAPO/CPP

Errors are mailed by CIF/POSTPROC_ALERT

Post Processing records displayed

Determine error cause ( verify application log) and correct error, Re-transfer objects if required

APO report /SAPAPO/CIF_POSTPROC_REORG

This report deletes old post -processing records SM37 W Status

Check if job is running as scheduled. C

IF E

RR

OR

HA

ND

LIN

G

( P

os

t p

roc

es

sin

g)

Output of APO report /SAPAPO/CIF_POSTPROC_REORG

Output of /SAPAPO/CIF_POSTPROC_REORG SM37 W

Yellow or red lamp

Check for records that could not be deleted.

APO reporte /SAPAPO/CIF_DELTAREPORT3

This report checks the external consistency between R/3 and APO and allows correction SM37 D Status

Check if job is running as scheduled

CIF

Delt

a R

ep

ort

s

Output of APO report /SAPAPO/CIF/DELTAREPORT3 SP01 D

Missing Objects reported

Check for missing objects reports to be missing in APO. If objects are missing Regional Superusers are to be notified

10

Reconciliation of inconsistencies

/SAPAPO/CCR D

If errors are reported by /SAPAPO/CIFDELTAREPORT3 trx in Background

Check for inconsistent objects and execute transfer of objects on respective tab strip

APO reporte /SAPAPO/CIF_DELTAREPORT3_REORG

This report deletes old delta results SM37 W Status

Check if job is running as scheduled. Add to CIF monitoring report