Wednesday, 13 May 2009
CIF Management for eWM
The eWM SCM platform is connect to the ECC system using CIF (qRFC) integration. The same integration technology used for APO.
The CIF is used both master data and transaction data.
Data is transferred using buffered qRFC technology:
Master data via standard CIF master data model, for eWM consideration/limitation must be made around vendor and customer replication as well batch managed products. Further consideration relates to managing batch determination in eWM. Critical to understand how characteristics and class are replicated and very critical to consider that it is not possible to use a SCM system for eWM batch management if set-up for configurable materials. This could be a problem if decision is made to use same SCM/APO development system for APO and eWM.
Changes are automatically updated for active models depending on Application Component (APO) flagged as well as change pointers set-up.
Transaction data, deliveries replicated to eWM system. From eWM delivery confirmation and goods movement. It is important that correct queue name is assigned to QIN scheduler.
One of the fundamental aspects regarding the CIF between ECC and eWM is related to monitoring and model management.
Queue must monitored for errors, job’s set-up to re-activate queue in error due to locking.
For active models, jobs must be set-up to de-activate a activate in order to include newly created master data objects. It is important in the CIF not to specify actual vendor or product codes but rather use other selection criteria such as plant / material types. For product material status is very useful to manage timing of replication in order avoid replicating a product that is still in the process of being updated in ECC.