My Oracle Support Banner

Fulfilment Order Is Not Integrated Successfully Into MFCS. (Doc ID 2993518.1)

Last updated on DECEMBER 19, 2023

Applies to:

Oracle Retail Merchandising Foundation Cloud Service - Version 19.3 to 19.3 [Release 19.3]
Information in this document applies to any platform.

Symptoms

Fulfilment Order Shipment arrives before the Fulfilment Order in MFCS causing Failure in RIB.

Steps :

1)OMS system sends a Fulfilment Order, which gets integrated to MFCS and, since it is to be delivered directly by the Supplier, MFCS creates automatically a Purchase Order for this Fulfilment Order.

2) Later, OMS system sends a Dispatch (shipment) for the Fulfilment Order sent before.

3) Since the MFCS “ASN In” message requires the PO ID to be provided (it’s a mandatory attribute for Customer Orders which are dispatched directly by the Supplier), Client have the middleware (OIC) doing a lookup to the database, in order to retrieve the MFCS PO ID for the respective Fulfilment Order Id. However, sometimes there are some problems in OMS or in the middleware or in RIB/MFCS and the Fulfilment Order is not processed/integrated successfully
into MFCS.
  i. In these cases, when the “ASN In” message is integrated, it will not take the PO Id with it, and it will fail and end up in RIB Hospital.
  ii. If you retry to process the “ASN In” message from RIHA, it will not try to retrieve the PO ID and update it in the (failed) “ASN In”, before trying to integrate it again to MFCS – therefore, it will always fail.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.