ER: Redundant Diffs Cannot Be Excluded From Being Used In MFCS For Creating New Products
(Doc ID 2964746.1)
Last updated on AUGUST 04, 2023
Applies to:
Oracle Retail Merchandising Foundation Cloud Service - Version NA and laterInformation in this document applies to any platform.
Goal
Requirement
It should be possible to block Diffs from being used, to allow them to be phased out and removed once all products that use them have been purged from the system. This is a requirement for 2 reasons:
• Colours are often only used for a short period of time.
• New Diffs are often created without checking if it already exists, causing duplicates (i.e. two diff ids with the same description)
If these Diffs continue to appear as options that can be selected, users run the risk of selecting a diff that should no longer be used.
Background
Once an item is created, the diff groups and diffs can no longer be changed. And diffs cannot be taken out of diff groups as long as items exist that use them. For UDAs it is possible to mark them as “not used” in the UDA induction upload. But for Diffs such functionality does not exist.
Requested solution
Allow Diffs to be excluded from creating new products with them. This can be achieved through allowing them to be removed from a Diff group with a "removal date" - allowing them to exist for existing products, while not displaying them in diff groups when creating SKUs for new Styles. Alternatively the Diff itself gets a flag similar to the UDA flag to make them "in use" or not.
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 |