Results for “pa_lookups”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PA_LOOKUPS is an APPS-owned, VALID database view in the Oracle E-Business Suite Projects (PA) product family. It presents system-defined lookup codes and their corresponding meanings for Oracle Projects, resolving the MEANING and DESCRIPTION columns into the language of the current session. In EBS 12.1.1 and 12.2.2 the object is registered in the ETRM as a read-only view owned by the APPS schema; it holds no data of its own and functions purely as a filtered projection over the Oracle Application Object Library (FND) lookup infrastructure.

Because it exposes Projects-relevant lookup values in a single, language-aware, application-scoped structure, PA_LOOKUPS is commonly used as a reference source in concurrent programs, Oracle Reports, OAF pages, and custom SQL integrations that need to translate stored lookup codes into user-facing text. It is not an interface table and should never be written to; all maintenance of lookup content is performed through the FND lookup maintenance forms against the underlying base object.

Underlying Base Objects

The documented referenced base object is FND_LOOKUP_VALUES, accessed through a synonym. PA_LOOKUPS is defined as a query over FND_LOOKUP_VALUES LV with three restricting predicates:

• LANGUAGE = USERENV('LANG') — returns only the rows matching the session language, which is why the view automatically presents meanings and descriptions in the user's own language rather than in the base installed language.
• VIEW_APPLICATION_ID = 275 — application ID 275 is Oracle Projects, so only lookup types registered to the Projects application are returned.
• SECURITY_GROUP_ID = FND_GLOBAL.LOOKUP_SECURITY_GROUP(LV.LOOKUP_TYPE, LV.VIEW_APPLICATION_ID) — applies the standard FND lookup security group filter, restricting visibility of lookup values according to the lookup type's security configuration.

Although the view's select list enumerates a TAG and attribute columns inherited from the FND structure, the documented column listing for PA_LOOKUPS includes PREDEFINED_FLAG in place of TAG. The combination of the language predicate and the security group function makes the view inherently session-sensitive, so identical queries can return different row sets for different users or language settings.

Key Columns

• LOOKUP_TYPE — the lookup type name (for example, a Projects-specific lookup such as a project status, expenditure category, or billing classification), identifying the group to which a code belongs.
• LOOKUP_CODE — the internal code stored on Projects transactions and entities; this is the value typically persisted in PA tables.
• MEANING — the translated, user-facing label for the code, rendered in the session language.
• DESCRIPTION — the optional longer translated description for the code.
• ENABLED_FLAG — indicates whether the lookup value is currently active and selectable.
• PREDEFINED_FLAG — identifies whether the value is seeded by Oracle (system-defined) or user-defined.
• START_DATE_ACTIVE / END_DATE_ACTIVE — the effective date range over which the lookup value is valid.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, LAST_UPDATE_DATE — standard WHO audit columns describing creation and last modification.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — descriptive flexfield segments available on lookup values for additional, installation-specific information.

Common Use Cases and Queries

Typical uses include populating value lists in custom reports, validating lookup codes passed into interfaces, and translating stored codes into display text in BI Publisher or Oracle Reports output. A frequent pattern is to join PA_LOOKUPS to a Projects transaction table on LOOKUP_CODE to obtain the meaning for reporting.

Retrieve all enabled values for a specific lookup type:

• SELECT lookup_code, meaning, description FROM apps.pa_lookups WHERE lookup_type = :p_lookup_type AND enabled_flag = 'Y' AND TRUNC(SYSDATE) BETWEEN NVL(start_date_active, SYSDATE) AND NVL(end_date_active, SYSDATE);

Resolve a single code to its translated meaning:

• SELECT meaning FROM apps.pa_lookups WHERE lookup_type = :p_lookup_type AND lookup_code = :p_lookup_code;

Distinct lookup types available to the session:

• SELECT DISTINCT lookup_type FROM apps.pa_lookups ORDER BY lookup_type;

Because the view enforces language and security grouping internally, queries should not repeat those predicates; doing so can inadvertently exclude valid rows. Always qualify the view with the APPS schema or a synonym, and treat the result set as read-only reference data.