Fusion Global HR: The Rule "Validate If Contact Exists Based On The Name Date Of Birth And Relationship" is Case Sensitive (Doc ID 2868522.1)

Last updated on MAY 18, 2023

Applies to:

Symptoms

ACTUAL BEHAVIOR
---------------
The rule "Validate if Contact Exists Based on the Name Date of Birth and Relationship" is case sensitive.
If you enter a contact with same name but in different case (Lower/Upper/Camel), the rule is not working and allows a duplicate contact to get saved.
  
EXPECTED BEHAVIOR
-----------------------
The rule "Validate if Contact Exists Based on the Name Date of Birth and Relationship" should not be case sensitive.
If you enter a contact with same name but in different case (Lower/Upper/Camel), error should pop up and not allow a duplicate contact to get saved.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Login to HCM as an HR
2. Navigate to HR > Show More > Search For ‘Emergency And Alternate Contacts’
3. Search for an Employee
4. Click on the Advance Search link to enter the page ‘Emergency And Alternate Contacts’
5. Click on the Name, that will take you to the My Contacts page
6. Able to view the existing contacts
7. Click on Add and Create a New Contact
8. While adding a new contact, try entering the same information as of the existing contact (in this case, this is added in Camel Case) Error pops up as expected.
9. However, adding the same contact (Same Last Name, First Name and contact type) but in UPPER CASE, the rule is not triggering and is allowing a duplicate contact to be saved.

Cause

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