My Oracle Support Banner

Enhancement Request: MC_REJECTIONS Should Contain More Information to Identify the Event Causing the Issue (Doc ID 2795517.1)

Last updated on FEBRUARY 16, 2023

Applies to:

Oracle Retail Merchandising Foundation Cloud Service - Version 19.1 and later
Information in this document applies to any platform.


RMS MC_REJECTIONS table should contain more information to easily identify the event causing the issue along with the key identifiers.

Steps to reproduce
1. Find some items in RMS that do not have any dependencies that would prevent item from reclassification.
2. Create a reclassification Request in RMS going into affect tomorrow.
3. Create a purchase order in RMS using the items, so that it will prevent item from reclassification.
4. Run RECLSDLY batch in Execute Mode.
5. Items on Purchase order are rejected during Reclassification.
6. Check MC rejections table.

MC_REJECTIONS table does not provide any identifiers such as reclass_number etc to identify the rejected record other than deriving information from rejection reasons.

This table should have the following attributes that can be used by the clients to identify the interface that is causing the issue

For eg ..(Using Reclass as an Example)
1. Source Column --> Interface area/Program Name that is causing the issues
2. Key Value --> For eg Reclass Number
3. create DateTime
4. Last Update DateTime


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

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