Store Creation Process Flow
(Doc ID 3040435.1)
Last updated on AUGUST 09, 2024
Applies to:
Oracle Retail Merchandising Foundation Cloud Service - Version 24.0 and laterInformation in this document applies to any platform.
Goal
On: MFCS/RMS 24.0.201.4 version
Business process requires that stores be staged so that they can be enriched/edited before the store_add process creates the store in MFCS.
The store_add process will populate other processes tables (pcs,stock_ledger,etc) and business does not accept their users needing to go to other screens/applications to fix or enrich the data that was not sent or with dummy values due to being across several departments, as an example:
• priceStore field is mandatory and not information a real estate department has access or knowledge about. Also, given that stores can be created weeks in advance its highly likely that this information would not be available.
The requirement is to be able to stage and have store records with a “status” field that will give control to our users on when a store is effectively created on MFCS.
Also, the base store screen uses a “all or nothing” approach that causes users to lose their work if they are missing a required field or if one of the values is not correct.
Lastly, store creation process documentation is not aligned with the base screen or API on which fields are optional or mandatory.
Solution
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
Goal |
Solution |
References |