Results for “oke_attribute_groups_v”

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

Overview

OKE_ATTRIBUTE_GROUPS_V is an APPS-owned view in the Oracle E-Business Suite Project Contracts (OKE) module. It presents a consolidated, user-facing list of the attribute groups that can be assigned to project contract user attributes. Rather than exposing a single physical table, the view assembles a unified result set from two distinct sources: seeded lookup values defined in Oracle's reference data, and customer-defined descriptive flexfield contexts created for the contract user attribute flexfield.

The view is read-only by design and serves primarily as a reporting and integration interface. Reports, concurrent programs, and custom extensions query it to present a single "attribute group" domain without needing to understand the underlying lookup-versus-flexfield split. This is particularly relevant to the search term descriptive_flex_context_name, because user-defined rows in this view are sourced directly from the descriptive flexfield context name, while system rows are derived from lookup meanings.

Underlying Base Objects

The documented view text is a UNION of two queries over the following base objects:

• FND_LOOKUP_VALUES_VL — Supplies the seeded "SYSTEM" attribute groups. The view filters on LOOKUP_TYPE = 'ATTRIBUTE_GROUP' and VIEW_APPLICATION_ID = 777 (the OKE application identifier), returning the lookup code, meaning, description, active dates, and enabled flag.
• FND_DESCR_FLEX_CONTEXTS_VL — Supplies the "USER" attribute groups. The view filters on APPLICATION_ID = 777, DESCRIPTIVE_FLEXFIELD_NAME = 'OKE_K_USER_ATTRIBUTES', and GLOBAL_FLAG = 'N', so only non-global, customer-defined contexts appear. The DESCRIPTIVE_FLEX_CONTEXT_CODE and DESCRIPTIVE_FLEX_CONTEXT_NAME columns become the group code and name respectively.

Both underlying objects are themselves views (the _VL suffix denotes a view with a translated/ML component), so no direct base table access is exposed to the consumer. This layering keeps the column shapes consistent while masking the physical storage.

Key Columns

• ATTRIBUTE_GROUP_TYPE — A literal discriminator. Returns 'SYSTEM' for lookup-sourced rows and 'USER' for flexfield-context rows.
• ATTRIBUTE_GROUP_CODE — The internal identifier. For system rows this is LOOKUP_CODE; for user rows it is DESCRIPTIVE_FLEX_CONTEXT_CODE.
• ATTRIBUTE_GROUP_NAME — The display label. For system rows this is MEANING; for user rows it is DESCRIPTIVE_FLEX_CONTEXT_NAME.
• DESCRIPTION — Free-text description from the originating source.
• START_DATE_ACTIVE / END_DATE_ACTIVE — Effective dates for system rows; user rows return NULL via TO_DATE(NULL), as flexfield contexts do not carry active date ranges in this view.
• ENABLED_FLAG — Indicates whether the group is currently active.

Common Use Cases and Queries

The view is typically used to populate attribute group selection lists, validate incoming interface data, or drive contract attribute reporting. A frequent pattern is separating system from user-defined groups:

• List all available attribute groups: SELECT attribute_group_type, attribute_group_code, attribute_group_name FROM oke_attribute_groups_v WHERE enabled_flag = 'Y' ORDER BY 1, 3;
• Retrieve only customer-defined contexts: SELECT attribute_group_code, attribute_group_name FROM oke_attribute_groups_v WHERE attribute_group_type = 'USER';
• Resolve a descriptive flex context name back to its group: SELECT attribute_group_code FROM oke_attribute_groups_v WHERE attribute_group_name = :context_name AND attribute_group_type = 'USER';

Because the view joins two metadata sources, it is an efficient single point of reference for both seeded and extensible attribute groups within Project Contracts.