Lookup Types
Lookup types provide the lists of values in application fields that are drop-down lists.
You can't create a new lookup with the name starting with ORA, to avoid any conflict with the lookups predefined in the application.
How You Modify Lookup Types
You can change many lookup types during or after implementation.
The configuration level of a lookup type determines whether the lookups in that lookup type can be edited. The lookup configuration levels are: User, Extensible, and System.
Here's a table that shows which lookup management tasks are allowed at each modification level.
Allowed Task |
User |
Extensible |
System |
---|---|---|---|
Deleting a lookup type |
Yes |
No |
No |
Inserting new codes |
Yes |
Yes |
No |
Changing the wording that displays on the page (Meaning field) |
Yes |
Yes |
Yes |
Updating start date, end date, and enabled fields |
Yes |
Yes, only if the code isn't predefined data |
No |
Deleting codes |
Yes |
Yes, only if the code isn't predefined data |
No |
Updating tags |
Yes |
No |
No |
Updating module |
Yes |
No |
No |
If a product depends on a lookup type, the configuration level must be set to system or extensible to prevent deletion. Once the configuration level is set for a lookup type, it can't be changed. The configuration level for lookup types created using the Define Lookups page is by default set at the User level.