Search Results fwk_tbx_lookup_codes_b

Overview

APPS.FWK_TBX_LOOKUP_CODES_VL is a seeded, VALID database view owned by the APPS schema within the FND — Application Object Library product of Oracle E-Business Suite. The _VL suffix identifies it as a "view with translation" object, meaning it presents translated (language-dependent) columns joined to the base lookup definition. It is part of the Oracle Application Framework (OAF) "Toolbox" (TBX) family of objects that support shared framework utilities used across EBS modules in both Release 12.1.1 and 12.2.2.

Unlike the customer-extensible FND Lookups (FND_LOOKUP_VALUES_VL), the FWK_TBX lookups are a dedicated, framework-internal lookup set. The view presents one row per lookup code per installed language, exposing the language-specific meaning and description alongside the code and its effective dating. Its primary role is to allow Oracle Application Framework pages, controllers, and dependent EBS forms to resolve a lookup code to a user-language display string without querying the two underlying tables directly. Reporting and integration layers also query it to enumerate valid TBX codes and to join code values to descriptive labels.

Underlying Base Objects

The view is defined over two documented base objects, referenced in the ETRM metadata as synonyms:

• FWK_TBX_LOOKUP_CODES_B — the base table holding language-independent rows: lookup type, lookup code, and the active date range.
• FWK_TBX_LOOKUP_CODES_TL — the translation table holding the language-specific MEANING and DESCRIPTION for each lookup code.

The view text joins the two on LOOKUP_TYPE and LOOKUP_CODE and filters the translation to the session language via T.LANGUAGE = USERENV('LANG'). Because USERENV('LANG') resolves to the current session's language code, the view returns exactly one translation row per code for the connected user's language, providing a de-normalized, single-row-per-code result set. The ROWID of the base row is exposed as ROW_ID, typically for OAF entity-row binding and updates.

Key Columns

• ROW_ID — the ROWID of the corresponding FWK_TBX_LOOKUP_CODES_B row; used by OAF for row identification.
• LOOKUP_TYPE — the lookup type that categorizes the code (the grouping key for a set of codes).
• LOOKUP_CODE — the language-independent code value stored in the base table.
• START_DATE_ACTIVE — the date from which the code becomes effective; NULL indicates no start restriction.
• END_DATE_ACTIVE — the date after which the code is no longer effective; NULL indicates no end restriction.
• MEANING — the translated display meaning for the code in the session language.
• DESCRIPTION — the translated, longer descriptive text for the code.

Common Use Cases and Queries

The view is commonly used to render TBX code values as user-readable labels, to validate that a code is currently active, and to drive LOVs or lookup-based list pages in OAF. A typical query enumerating active codes for a given lookup type is:

• SELECT lookup_code, meaning, description FROM apps.fwk_tbx_lookup_codes_vl WHERE lookup_type = :p_type AND TRUNC(SYSDATE) BETWEEN NVL(start_date_active, TRUNC(SYSDATE)) AND NVL(end_date_active, TRUNC(SYSDATE)) ORDER BY meaning;

To resolve a single code to its label, a query such as SELECT meaning FROM apps.fwk_tbx_lookup_codes_vl WHERE lookup_type = :p_type AND lookup_code = :p_code is used. Because translation is resolved at the view level, the application does not need to specify a language; the session's USERENV('LANG') governs the result. For a complete listing regardless of effective dating, the date predicates may be omitted. When joining to transactional data, the view is best treated as a label source keyed on LOOKUP_TYPE and LOOKUP_CODE, with date filtering applied only where active-value exclusion is required.