Missing Integrations From MFCS To RDF
(Doc ID 2946204.1)
Last updated on MAY 03, 2023
Applies to:Oracle Retail Merchandising Foundation Cloud Service - Version NA and later
Information in this document applies to any platform.
In an end to end solution between MFCS and RDF, issues based forecasts and day level forecasts are required. MFCS has the ability to accept issues forecasts and day level forecasts from RDF Cloud Service. However, for RDF to perform this, it needs to be sent the following information which is missing:
1. Issues based forecasts. The sales history is sent from selling at the point of sale, but not the issues based forecast which is based on shipments outbound from the warehouse.
2. Out of stock indicators for the warehouse. This is sent for stores, but not the warehouse. This is required for RDF to generate an issues forecast for MFCS.
3. Day level interfaces - Out of stock, sales (and issues), and transaction histories sent to RDF, per the documentation are sent weekly with an end of week date. This is not sufficient for RDF to generate a day level forecast
4. Triggering of interfaces on a daily basis such as the product hierarchy. Due to the short lead time for items in grocery, items can be set up, and the next day sales come through which must be sent to RDF.
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