Results for “hxc_lookups”

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

Overview

HXC_LOOKUPS is a read-only dictionary view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the HXC (Time and Labor Engine) product family. It presents a filtered, runtime-resolved projection of Oracle Application Object Library (FND) lookup data that is relevant specifically to the Time and Labor Engine application (APPLICATION_ID = 809). Rather than exposing the entire FND_LOOKUP_VALUES repository, the view restricts the result set to lookup types and values registered against the HXC application, so that reports, concurrent programs, and integrations can retrieve valid Time and Labor codes without additional predicates against the underlying FND tables.

Because it is a view (not a table), it stores no data of its own. Its status is VALID in both 12.1.1 and 12.2.2, and its column layout is identical across those releases, which makes it safe to reference in custom code that must remain portable between them. The view is typically consumed to populate list-of-values prompts, resolve stored codes into user-facing meanings, and drive conditional logic in Time and Labor and OTL-based reporting.

Underlying Base Objects

The ETRM metadata documents the view as being defined over four referenced objects:

• FND_APPLICATION (SYNONYM) — supplies the application row, filtered to APPLICATION_ID = 809, ensuring only HXC lookup types are returned.
• FND_LOOKUP_TYPES (SYNONYM) — provides the lookup type definition that links to each value.
• FND_LOOKUP_VALUES (SYNONYM) — the primary source of lookup codes, meanings, descriptions, and effective dates.
• FND_GLOBAL (PACKAGE) — used to derive language and lookup security context at runtime.

Functionally, the view joins FND_APPLICATION to FND_LOOKUP_TYPES on APPLICATION_ID, and then to FND_LOOKUP_VALUES on LOOKUP_TYPE, applying security and language predicates along the way. The effective query text is:

SELECT T.LOOKUP_TYPE, V.LOOKUP_CODE, V.MEANING, V.DESCRIPTION, V.ENABLED_FLAG, V.START_DATE_ACTIVE, V.END_DATE_ACTIVE FROM FND_APPLICATION A, FND_LOOKUP_TYPES T, FND_LOOKUP_VALUES V WHERE V.LANGUAGE = USERENV('LANG') AND V.VIEW_APPLICATION_ID = 3 AND V.SECURITY_GROUP_ID = FND_GLOBAL.LOOKUP_SECURITY_GROUP(T.LOOKUP_TYPE, V.VIEW_APPLICATION_ID) AND A.APPLICATION_ID = 809 AND A.APPLICATION_ID = T.APPLICATION_ID AND T.LOOKUP_TYPE = V.LOOKUP_TYPE

Key Columns

• LOOKUP_TYPE — identifies the lookup category being queried (for example, the HXC-specific lookup types registered against application 809).
• LOOKUP_CODE — the internal, stored value returned by the application; typically used as a foreign key reference in transactional tables.
• MEANING — the translatable, user-facing label corresponding to the lookup code.
• DESCRIPTION — supplementary free-text detail for the lookup value, where maintained.
• ENABLED_FLAG — indicates whether the value is active ('Y') or disabled ('N') for selection.
• START_DATE_ACTIVE and END_DATE_ACTIVE — the effective date range during which the lookup value is valid.

Common Use Cases and Queries

The most frequent use is validating or resolving HXC codes in custom reports and interfaces. A typical query returns only currently enabled values:

SELECT lookup_type, lookup_code, meaning FROM apps.hxc_lookups WHERE enabled_flag = 'Y' AND TRUNC(SYSDATE) BETWEEN NVL(start_date_active, SYSDATE) AND NVL(end_date_active, SYSDATE) ORDER BY lookup_type, lookup_code;

Because language and security predicates are resolved internally, callers do not need to re-implement USERENV('LANG') logic. If the requirement is to see the complete lookup picture (including lookup types not tied to HXC), developers should query FND_LOOKUP_VALUES directly instead. Note that the view relies on FND_GLOBAL.LOOKUP_SECURITY_GROUP, so it should always be executed in an environment where FND_GLOBAL is initialized.