Results for “jtf_rs_table_attributes_vl”

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

Overview

JTF_RS_TABLE_ATTRIBUTES_VL is a multi-language (MLS) view owned by the APPS schema in Oracle E-Business Suite, belonging to the JTF — CRM Foundation product module. It presents a denormalized, language-resolved read model over the resource-management "table attributes" entity, exposing both the internal attribute definition and its user-facing translated name in a single result set. The view is a standard EBS "_VL" construct: it joins an "_B" (base) table holding language-independent columns with a "_TL" (translation) table holding the language-dependent descriptive column, filtered to the session's language.

In reporting and integration terms, this view is the recommended access point for queries that must display the user-visible attribute label. Because USER_ATTRIBUTE_NAME lives in the translated table and the view resolves it automatically via USERENV('LANG'), consumers do not have to write their own translation joins or language predicates. This makes it suitable for OBIEE/BI Publisher datasets, custom concurrent programs, and inbound/outbound interface programs that reference CRM resource table attribute metadata.

Underlying Base Objects

The view is defined over two synonyms that resolve to the underlying JTF CRM Foundation tables:

• JTF_RS_TABLE_ATTRIBUTES_B — the base table supplying language-independent data, aliased B in the view text.
• JTF_RS_TABLE_ATTRIBUTES_TL — the translation table supplying language-dependent data, aliased T.

The join predicate is B.ATTRIBUTE_ID = T.ATTRIBUTE_ID, with the additional restriction T.LANGUAGE = USERENV('LANG'). The ROW_ID column is sourced from B.ROWID, and all descriptive-for-user columns (USER_ATTRIBUTE_NAME) come from the translation table, while definitional and DFF columns come from the base table.

Key Columns

• ROW_ID — the base table ROWID, used as a stable row identifier in EBS forms and APIs.
• ATTRIBUTE_ID — primary key of the attribute definition; the join key between the _B and _TL tables.
• ATTRIBUTE_NAME — internal (developer-facing) name of the attribute, from the base table.
• USER_ATTRIBUTE_NAME — the translated, end-user-visible label. This is the column returned when a user searches for user_attribute_name, and it is the field that distinguishes the _VL view from the base table.
• ATTRIBUTE_ACCESS_LEVEL — controls the visibility/access classification of the attribute.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the underlying APIs.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the standard EBS descriptive flexfield (DFF) context and segment columns, available for client-specific extension data.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS WHO audit columns.

Common Use Cases and Queries

Typical scenarios include building LOV queries that display user-friendly attribute labels, generating metadata reports for CRM resource configuration, and validating attribute access levels before exposing fields in custom UIs.

Retrieve all attributes with their translated names:

• SELECT attribute_id, attribute_name, user_attribute_name, attribute_access_level FROM jtf_rs_table_attributes_vl ORDER BY user_attribute_name;

Filter to a specific user-facing label, which is the pattern implied by the user_attribute_name search term:

• SELECT attribute_id, attribute_name, user_attribute_name FROM jtf_rs_table_attributes_vl WHERE user_attribute_name = :p_name;

Join to related CRM resource data using the attribute identifier:

• SELECT v.user_attribute_name, v.attribute_category FROM jtf_rs_table_attributes_vl v WHERE v.attribute_id = :p_attribute_id;

Because the language predicate is embedded in the view, no additional LANGUAGE filter is required; results automatically reflect the language of the querying session, governed by USERENV('LANG').