Results for “row_id”

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

Overview

The FWK_TBX_LOOKUP_TYPES_VL view is a seeded, read-only database object owned by the APPS schema within the FND — Application Object Library product module of Oracle E-Business Suite. It is a translatable (VL, or "view language") view that presents user-facing text for lookup type definitions associated with the FWK (Framework) Toolbox lookup infrastructure. In Oracle EBS, lookup types provide the configurable, code-driven value sets that populate many application list of values (LOVs), flexfields, and status fields. The translatable counterpart exposes the display name and description for the currently active session language rather than all installed languages.

Because the view is filtered by the session language, its primary role is in reporting and integration scenarios where a human-readable label is required. Application code, concurrent programs, and custom reports that read from FWK_TBX_LOOKUP_TYPES_VL automatically receive the appropriate translated text without needing to join to the translation table directly. This makes it a convenient abstraction layer for multilingual deployments, where the underlying base table stores one row per installed language.

Underlying Base Objects

Per the documented ETRM metadata for 12.2.2, the view is defined over FWK_TBX_LOOKUP_TYPES_TL (referenced as a synonym). The _TL suffix indicates a translation table, which holds one row per language for each lookup type. The view definition given in the metadata is straightforward:

• FWK_TBX_LOOKUP_TYPES_TL — the translation table supplying LOOKUP_TYPE, DISPLAY_NAME, and DESCRIPTION for each installed language.
• ROWID — the physical row identifier of the translation row, aliased as ROW_ID, providing a unique key for the view.

The view applies the predicate WHERE T.LANGUAGE = USERENV('LANG'), so only the row matching the current language environment is returned. This is the defining characteristic of a _VL view: it hides the multilingual complexity of the base table and presents a single-language projection. No joins to additional tables are present in the documented definition, meaning the view is a thin filter rather than a composite query.

Key Columns

• ROW_ID — the ROWID of the underlying translation row, aliased for readability. Useful as a unique identifier within a query result.
• LOOKUP_TYPE — the internal identifier for the lookup type. This is the stable, language-independent key used throughout Oracle EBS to reference the lookup category.
• DISPLAY_NAME — the translated, user-facing name of the lookup type in the current session language. This is the value most often presented in reports and LOVs.
• DESCRIPTION — the translated descriptive text for the lookup type, providing additional context for the lookup category.

Common Use Cases and Queries

The view is typically queried when a report or interface must display the friendly name of a toolbox lookup type in the user's own language. A representative query retrieves the display name and description for all lookup types visible to the current language:

• Populating LOVs and list of values — supplying translated labels for lookup type selection.
• Multilingual reporting — ensuring output matches the language of the session without explicit language joins.
• Integration and data extraction — providing a stable, translatable source for downstream systems that require displayable lookup metadata.

A common sample is:

SELECT lookup_type, display_name, description
FROM apps.fwk_tbx_lookup_types_vl
ORDER BY display_name;

Because the row count is already constrained to the session language, no additional language filter is necessary. Joining this view back to the base translation table should be avoided, as the view is intended to be consumed directly as the translated projection of the lookup type metadata.