Postal Code Removal Concurrent Program Has Constraint On Postal Code Field
(Doc ID 2807001.1)
Last updated on SEPTEMBER 17, 2021
Applies to:
Oracle HRMS (Canada) - Version 12.1 HRMS RUP13 and laterInformation in this document applies to any platform.
Symptoms
Problem Statement:
Created Canada city with Wrong Postal Code 0G1 to 0G1, it was added to a
combination which already has addresses associated so it cannot be disabled
or deleted. The main issue is that when further attempting to use the
concurrent program "Postal Code Removal" the seeded constraints on the Postal
Code range fields prevent this CP from running against the erroneously
entered postal code. Thus making it impossible to remove an incorrectly typed
Postal Code. Either the validation should have fired on the CA Define Cities
Form to not allow entry in the first place or the validation should be
removed from CP parameters so that erroneously entered Postal Codes have a
method to be removed.
NAN, where A is Alphabet and N is Numeric
Steps to Reproduce:
The issue can be reproduced at will with the following steps:
1. Responsibility: CA Super HRMS Manager
2. Navigate to Processes and Reports > Submit Processes and Reports
3. Select "Postal Code Removal"
4. Enter relevant Province, City, and select existing Postal Code 0G1 0G1 from the LOV
5. Error appears stating postal code is invalid.
Cause
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
Symptoms |
Cause |
Solution |
References |