SAP Random Help

CIF is the standard interface between APO and ECC used to transfer master data (uni-directional) and transaction data (bi-directional). But very often due to some master data issue transaction data does not flow through and gets stuck in CIF queue. SAP provides CIF Delta Reconciliation Report (commonly know as CCR) that compares transaction data for given product-location between APO & ECC to list the differences. This output result is typically reviewed by production support team and necessary processing action (one of Send to ECC, Send to APO, Delete in ECC and Delete in APO action button) executed to reconcile the transaction data differences. Any APO consultant doing CIF monitoring on regular basis knows the effort required and also over time turns monotonous. However the choice of action to be taken is limited (most of the cases only 1 of the 4 actions possible) based on the transaction data object type (like Purchase Requisition, Purchase / Stock Transfer Order, Planned Ord

Most common error messages that we face when analyzing CIF execution. For every error message we have a few recommended actions and possible root causes. 1. Order version __ __ not valid at date __ . Root causes:  PPM/PDS or production version is no longer valid at order date of execution.  No available PPM/PDS orPV at order’s date of execution.  PPM or PDS has not been ciffed correctly to APO. Solution: Check production version status is not locked. Update new validity dates for production version. Cif changes to APO in order to update the PPMs or PPDs. Re-explode the orders where necessary. 2. Product ____ doesn’t exist in an active integration model. Root causes:  Material intergation model is not active.  Product has cross-plant status as blocked.  Material has MRP type different than X_*. Solution:  Check and correct the cross-plant status of the product..  Check and correct the MRP type of the product (X_).  Activate the integration model and C