Skip to main content

Application Utilities Lookups and Application Object Library Lookups

Maintain existing and define additional Lookups for your shared Lookup types. You can define up to 250 Lookups for each Lookup type. Each Lookup has a code and a meaning. For example, Lookup type YES_NO has a code Y with meaning Yes, and a code N with a meaning No.
Note: In Releases 11.0 and earlier, there were two Lookup features, Special Lookups and Common Lookups. These two features have been merged into one. The new consolidated Lookups feature has Lookups maintained in this form.
If you make changes to a Lookup, users must log out then log back on before your changes take effect.
Lookups Block
Type
Query the type of your Lookup. You can define a maximum of 250 Lookups for a single type.
User Name
The user name is used by loader programs.
Application
Query the application associated with your Lookup type.
Description
If you use windows specialized for a particular Lookup type, the window uses this description in the window title.
Access Level
The access level restricts changes that are possible to a lookup type. The possible levels are:
System
No changes to the lookup codes are allowed.
Extensible
New lookup codes can be added. However, you cannot modify seeded lookup codes.
User
You can change any lookup code.
Security Group
This field is for HRMS security only. See: Customizing, Reporting, and System Administration in Oracle HRMS.
Only the security group of the current form session can be maintained using this form. Standard is the standard default security group. Custom indicates this lookup type is for a custom security group.
All global and cross-security group maintenance is done using the Generic Loader with the Lookups configuration file.
Lookups Values Block
Suggestion: If you would like to query records by a code attribute, such as the Enabled check box, then do the following:
Step 8. Query the lookup type.
Step 9. Move the cursor to any field in the lower region on the window.
Step 10. From the View menu, select Query By Example, Enter.
Step 11. Enter your query criteria.
Step 12. From the View Menu, select Query By Example, Run.
Code
Enter the code value for your Lookup. You can define a maximum of 250 Lookups for a single Lookup type. When you enter a valid Lookup meaning into a displayed window field, Lookups stores this code into a corresponding hidden field. For example, the Lookup "Y" displays the meaning "Yes" but stores the code value "Y" in a hidden field.
You cannot change the values in this field after committing them. To remove an obsolete Lookup you can either disable the code, enter an end date, or change the meaning and description to match a replacement code.
Meaning
When you enter a valid Lookup meaning into a displayed window field, Lookups stores the corresponding code into a hidden field. Lookups automatically displays the meaning in your Lookups field whenever you query your window. For example, the Lookup "Y" displays the meaning "Yes" but stores the code value "Y" in a hidden field.
Description
You can display the description along with the meaning to give more information about your Lookup.
Tag
Optionally enter in a tag to describe your lookup. The tag can be used to categorize lookup values.
Effective Dates
Enter the dates between which this Lookup becomes active. If you do not enter a start date, your Lookup is valid immediately.
Once a Lookup expires, users cannot insert additional records using the Lookup, but can query records that already use the Lookup. If you do not enter an end date, your Lookup is valid indefinitely.
Enabled
Indicate whether applications can use your Lookup. If you enter No, users cannot insert additional records using your Lookup, but can query records that already use this Lookup.
[ ]
The double brackets ([ ]) identify a descriptive flexfield that you can use to add data fields to this window without programming.

Comments

  1. Thank you for sharing this informative piece! Eagerly anticipating more content that bridges theory and hands-on application in the context of online training for Fusion Cloud SCM online training.

    ReplyDelete

Post a Comment

Popular posts from this blog

Applying Prepayments to Invoices

You can apply the available amount of Item type distributions from a Temporary type prepayment to one or more invoices to offset the amount you pay on the invoice(s). If you entered the prepayment as a Permanent type and want to apply it, you can query the prepayment in the Invoices window and change the Prepayment Type to Temporary. If you use Automatic Offsets then your setting for the Prevent Prepayment Application Across Balancing Segments Payables option controls whether you can apply a prepayment to an invoice or expense report with a different balancing segment. Prerequisites The invoice type is Standard, Mixed, or Expense Report. Today's date is on or after the Settlement Date of the prepayment. The invoice date is on or after the date of the prepayment. The prepayment is type Temporary, fully paid, validated, not cancelled, has no active holds, and has not already been fully applied. The prepayment has the same supplier, invoice currency and payment currenc

Matching Prepayments to Purchase Orders

You can match a prepayment to a purchase order or receipt. The accounting entries for Item distributions on a matched prepayment typically debit a prepayment account that Payables provides. However, during prepayment entry you can override any account that Payables defaults or builds. Payables does not create an encumbrance entry for the prepaid amount when a prepayment is matched to a purchase order. The match is treated like a reservation of the quantity billed. Payables does not calculate the invoice price variance or exchange rate variance at this point. Furthermore, you cannot change the unit price during the prepayment match to purchase order. A final match to the purchase order is not allowed either. When the matched prepayment is applied to an invoice, Payables reverses the matched quantity on the prepayment to reflect the balance of the total quantity matched. The following example illustrates a prepayment application to a purchase order: You contract to attend a $5,000 trade