Lookup for Citizenship Status Field Changed from Extensible to User

The configuration level of the existing lookup type PER_CITIZENSHIP_STATUS is changed from Extensible to User. You can now modify or delete Oracle-delivered lookup codes, or create your own lookup codes.

NOTE: Once you modify an Oracle-delivered lookup code, you have taken ownership of that lookup code. No further changes will be delivered to that lookup code by Oracle.

Here's the reason why this change was introduced. The Lookup Configuration Level for the PER_CITIZENSHIP_STATUS lookup type was Extensible. Oracle delivered the following lookup codes with the +MY tag: Citizen, Foreign worker, and Permanent resident. But the Active and Expired global lookup codes don't have a tag of -MY. This caused confusion, because the Active and Expired lookup codes were also displayed along with the codes for Malaysia.

Because the lookup type was defined as Extensible, it wasn't possible to change the tags associated with the lookup codes. By making the lookup type as User, it's possible to add the -MY tag to the Active and Expired lookup codes. This eliminates the confusion, so that only the Citizen, Foreign worker, and Permanent resident lookup codes are displayed for the Malaysian citizenship.

Alternatively, if you don't want the Citizen, Foreign worker, and Permanent resident lookup codes to be displayed at all, you can deselect the Enabled check box for these codes.

By changing the lookup type from Extensible to User, you have full control over the lookup codes in the PER_CITIZENSHIP_STATUS lookup type. 

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

• If a lookup code that has been used is deleted, the application continues to operate as normal. But for users that have used the deleted lookup code, the Citizenship Status field will be displayed as a blank. If the user edits the Citizenship Status field, the deleted lookup code won't be displayed in the list of values, but the user will be able to select a valid lookup code.
• If a deleted lookup code is passed as part of an HCM Data Loader file, an error will be displayed indicating that the lookup code isn't valid, and the record won't be loaded until a valid lookup code is used.
• If a lookup code is deleted, Oracle will deliver the same lookup code in the next update. So, it's recommended to deselect the Enabled flag rather than deleting the lookup code.