Results for “oke_k_user_attributes_v”

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

Overview

OKE_K_USER_ATTRIBUTES_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the OKE – Project Contracts product family. Its purpose is to present the descriptive flexfield (DFF) data captured against Project Contracts user attribute records in a denormalized, human-readable form. The base transactional table OKE_K_USER_ATTRIBUTES stores the raw attribute values as generic columns named USER_ATTRIBUTE01 through USER_ATTRIBUTE30, while the flexfield context information is held in separate translation tables. The view resolves this by joining the context code to the descriptive flexfield context definitions, exposing the context name and description alongside every attribute column. The view is documented as VALID in both Oracle EBS 12.1.1 and 12.2.2, and is referenced by the ETRM object registry with the owner APPS and the object type VIEW.

Underlying Base Objects

The view is defined over two documented base objects:

• OKE_K_USER_ATTRIBUTES (referenced through a SYNONYM aliased as UA) – the primary source, holding one row per user attribute record with the K_USER_ATTRIBUTE_ID, header and line associations, the context value, and the thirty generic attribute columns.
• FND_DESCR_FLEX_CONTEXTS_TL (referenced through a SYNONYM aliased as DFC) – the descriptive flexfield context translation table, which supplies the context name and description.

The join is driven by three conditions: the flexfield name must equal 'OKE_K_USER_ATTRIBUTES', the APPLICATION_ID must equal 777 (the OKE application identifier), and the language must match the session language via USERENV('LANG'). The match between UA.USER_ATTRIBUTE_CONTEXT and DFC.DESCRIPTIVE_FLEX_CONTEXT_CODE links each attribute row to its translated context definition. This structure means the view returns one row per base user attribute record, enriched with readable context metadata.

Key Columns

• K_USER_ATTRIBUTE_ID – primary key of the underlying user attribute record.
• K_HEADER_ID / K_LINE_ID – foreign keys associating the attributes with the contract header and, where applicable, the contract line.
• USER_ATTRIBUTE_CONTEXT – the descriptive flexfield context code that determines which attributes are meaningful.
• USER_ATTR_CONTEXT_NAME / USER_ATTR_CONTEXT_DESC – the translated context name and description sourced from FND_DESCR_FLEX_CONTEXTS_TL, providing the human-readable context label.
• USER_ATTRIBUTE01 through USER_ATTRIBUTE30 – the thirty generic DFF segments, including the specific column cited by the search, USER_ATTRIBUTE25.
• Audit columns – CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, and RECORD_VERSION_NUMBER, plus ROWID, supporting concurrency and audit reporting.

Common Use Cases and Queries

The view is typically used for reporting on contract-specific flexfield data without needing to decode context codes manually. A common query retrieves a particular segment such as USER_ATTRIBUTE25 for a known context:

• Filter by context – SELECT K_HEADER_ID, K_LINE_ID, USER_ATTRIBUTE25 FROM APPS.OKE_K_USER_ATTRIBUTES_V WHERE USER_ATTRIBUTE_CONTEXT = :context;
• Locate values across records – SELECT K_USER_ATTRIBUTE_ID, USER_ATTR_CONTEXT_NAME, USER_ATTRIBUTE25 FROM APPS.OKE_K_USER_ATTRIBUTES_V WHERE USER_ATTRIBUTE25 IS NOT NULL;
• Join to contract headers – link K_HEADER_ID to the OKE contract header tables to report attribute values alongside header detail.

Because the underlying DFF columns are generic, analysts should first query FND_DESCR_FLEX_CONTEXTS_TL or the flexfield setup to determine which segment maps to which attribute number in the relevant context. Access should be granted through the APPS schema or an appropriate custom synonym, and grants on the base tables should be reviewed before exposing the view to downstream extracts.