Search Results parent_attribute_code

Overview

OKE_OBJECT_ATTRIBUTES_VL is a multi-lingual (VL) view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the OKE – Project Contracts module. It exposes descriptive and configuration metadata for object attributes registered against database objects within the Project Contracts and related Oracle Projects schemas. Its principal purpose is to translate the language-independent attribute definitions stored in the base table into the session's active language, enabling forms, reports, and integration interfaces to display attribute names and descriptions appropriate to the logged-in user.

The view is classified as VALID and is documented in ETRM for both 12.1.1 and 12.2.2. It plays a supporting role rather than a transactional one: it is a metadata layer that describes how other objects (such as contract lines, deliverables, and other OKE entities) may be secured, queried, displayed as columns, or surfaced as form items. Applications and extensions frequently join to this view when building dynamic, attribute-driven user interfaces or when validating attribute codes entered by users.

Underlying Base Objects

The view is defined over two synonyms, each resolving to a base table in the APPS schema:

• OKE_OBJECT_ATTRIBUTES_B – the language-independent "base" table holding the attribute code, datatype, and a series of flag columns controlling security and UI behaviour.
• OKE_OBJECT_ATTRIBUTES_TL – the translation table holding the translated ATTRIBUTE_NAME and DESCRIPTION for each attribute, keyed by language.

The view joins the two tables on DATABASE_OBJECT_NAME and ATTRIBUTE_CODE, and restricts the translation row to T.LANGUAGE = USERENV('LANG'), so that only the translation matching the current session language is returned. This is the standard VL view pattern in EBS and guarantees exactly one row per attribute per session.

Key Columns

• ROW_ID – the ROWID of the base table row; used internally and rarely referenced in application SQL.
• DATABASE_OBJECT_NAME – identifies the database object (typically a table or view) to which the attribute belongs.
• ATTRIBUTE_CODE – the internal, language-independent identifier of the attribute.
• ATTRIBUTE_NAME / DESCRIPTION – translated, user-facing label and long description.
• DATATYPE – the data type of the attribute (e.g. character, number, date), driving validation and formatting.
• SECURABLE_FLAG, QUERYABLE_FLAG, VIEW_COLUMN_FLAG, FORM_ITEM_FLAG – control flags indicating whether the attribute can be secured, queried, rendered as a view column, or exposed as a form item.
• ATTRIBUTE_GROUP_CODE – groups related attributes for presentation.
• PARENT_ATTRIBUTE_CODE – the searched column; identifies the parent attribute when attributes are arranged in a hierarchy, enabling dependent or cascading attribute structures.
• Audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) – standard WHO columns from the base table.

Common Use Cases and Queries

Typical scenarios include generating dynamic contract attribute screens, validating user-entered attribute codes, and reporting on attribute configuration. The PARENT_ATTRIBUTE_CODE column is queried when resolving attribute hierarchies.

List attributes for a database object in the session language:

• SELECT attribute_code, attribute_name, datatype, parent_attribute_code FROM oke_object_attributes_vl WHERE database_object_name = :object_name ORDER BY attribute_name;

Find child attributes for a given parent:

• SELECT attribute_code, attribute_name FROM oke_object_attributes_vl WHERE database_object_name = :object_name AND parent_attribute_code = :parent_code;

Locate attributes eligible for form display:

• SELECT attribute_code, attribute_name FROM oke_object_attributes_vl WHERE form_item_flag = 'Y' AND database_object_name = :object_name;

Because the view already filters by USERENV('LANG'), callers should not add further language predicates; doing so can suppress rows unexpectedly.