MM: Confirmation Matching – Common Ref No Field Is Mandatory In Backend But Not Mandatory Frntend (Doc ID 2885616.1)

Last updated on JULY 29, 2022

Applies to:

Symptoms

On : 14.5.0.0.0 version, Production Support

ACTUAL BEHAVIOR
---------------
MM confirmation matching – Common ref no field is mandatory in backend but not mandatory in front end

EXPECTED BEHAVIOR
-----------------------
If common ref no field is not checked in MMDCNMNT, it should not be checked while performing the match.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. From MMDCNMNT, maintain the rule for FULLMATCH.
2. Make sure common ref field is unchecked in the rule maintenance
3. While doing the MM match, verify if system does a full match if common ref number field does not match

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, MM matching is not correct as per the rule maintained

Changes

Cause

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