Issue with MFCS to Planning Applications Integration for Trigger Files
(Doc ID 2668206.1)
Last updated on OCTOBER 03, 2023
Applies to:
Oracle Retail Integration Cloud Service - Version 16.0 and laterOracle Retail Merchandising Foundation Cloud Service - Version 16.0 and later
Oracle Retail Merchandise Financial Planning Cloud Service - Version 16.0 and later
Information in this document applies to any platform.
Symptoms
There is an issue with the trigger file(s) to be sent to planning applications (ex: MFPEECS) from Source Merchandising Foundation Cloud Service (MFCS). Currently GBUCS 1.0 has a trigger file which is not same for GBUCS 3.0 complete file request. So there is a need for supporting applications hosted on both GBUCS 1.0 and 3.0 enviroments.
For example:
GBUCS 1.0 uses rms_clnd.complete GBUCS 3.0 uses rms_clnd.csv.dat.complete
Source system (MFCS) through Bulk Data Integration (BDI) sends the trigger file. With this new requirement between GBUCS 1.0 and 3.0, Source system has to send two trigger files - one trigger file for planning application (RPAS Solutions) and another for supporting SFTP Server.
Changes
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 |
| Changes |
| Cause |
| Solution |
| References |