Results for “oke_k_user_attributes_h”

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

Overview

OKE_K_USER_ATTRIBUTES_H is a history (audit) table in the OKE – Project Contracts module of Oracle E-Business Suite, available in both 12.1.1 and 12.2.2. It stores the descriptive flexfield-style user attribute values associated with project contract headers and lines, preserving each prior version of those attribute sets as contracts undergo amendment and revision. In the ETRM 12.2.2 physical schema, the table is owned by the OKE schema, is marked VALID, and contains 41 documented columns.

Because the table preserves multiple MAJOR_VERSION values per logical attribute set and carries no mutable descriptive attributes of its own beyond the version-scoped user attribute payload, a Data Vault classification heuristic (mined from the foreign-key structure) suggests treating it as a link object. It sits between the contract header and line history entities and connects them to a versioned set of user-defined attribute values. It should not be modeled as a hub, since its identity is drawn from the parent contract header/line and its own surrogate identifier rather than from an independent business concept.

Key Information Stored

The most important columns in this table are:

• K_USER_ATTRIBUTE_ID – Surrogate identifier for the user attribute record; part of the primary key OKE_K_USER_ATTR_H_PK.
• MAJOR_VERSION – Version discriminator that distinguishes history rows for the same logical attribute set; the second component of the primary key.
• K_HEADER_ID – Foreign key to the contract header history table OKE_K_HEADERS_H; identifies the contract header to which the attributes belong.
• K_LINE_ID – Foreign key to the contract line history table OKE_K_LINES_H; identifies the specific line when the attributes are line-level.
• USER_ATTRIBUTE_CONTEXT – Describes the context under which the user attribute values are interpreted, typically the flexfield context or attribute group name.
• USER_ATTRIBUTE01 through USER_ATTRIBUTE30 – Thirty positional columns holding the actual user-defined attribute values. These are generic placeholders whose meaning depends on USER_ATTRIBUTE_CONTEXT.
• RECORD_VERSION_NUMBER – Optimistic locking / record version indicator maintained by the OKE framework.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN – Standard EBS WHO columns capturing audit and user information.

The surrogate primary key OKE_K_USER_ATTR_H_PK is composed of K_USER_ATTRIBUTE_ID and MAJOR_VERSION. The documented unique index OKE_K_USER_ATTR_H_U1 also covers (K_USER_ATTRIBUTE_ID, MAJOR_VERSION), while the business-key candidate OKE_K_USER_ATTR_UK01 covers K_HEADER_ID, K_LINE_ID, USER_ATTRIBUTE_CONTEXT, and MAJOR_VERSION — meaning a given header/line/context combination can have exactly one row per major version.

Common Use Cases and Queries

Typical uses include auditing historical user attribute values on contracts, reconstructing the state of a contract at a specific version, and reporting on user-defined fields that OKE exposes through contract header and line DFFs.

• Retrieve the current-version attributes for a header: SELECT * FROM oke.oke_k_user_attributes_h WHERE k_header_id = :p_header_id AND major_version = (SELECT MAX(major_version) FROM oke.oke_k_user_attributes_h WHERE k_header_id = :p_header_id);
• Reconstruct a historical view by filtering on a specific MAJOR_VERSION and USER_ATTRIBUTE_CONTEXT.
• Join to OKE_K_HEADERS_H on (K_HEADER_ID, MAJOR_VERSION) to combine header details with user attribute payloads.
• Join to OKE_K_LINES_H on (K_LINE_ID, MAJOR_VERSION) for line-level reporting.
• Extract attributes for downstream analytics by unpivoting USER_ATTRIBUTE01..USER_ATTRIBUTE30.

Related Objects

• OKE_K_HEADERS_H – joined on K_HEADER_ID and MAJOR_VERSION; the parent contract header history.
• OKE_K_LINES_H – joined on K_LINE_ID and MAJOR_VERSION; the parent contract line history.
• OKE_K_USER_ATTRIBUTES – the non-history counterpart for current user attribute values.
• OKE_K_HEADERS and OKE_K_LINES – current-version parents of the corresponding history records.
• OKE contract public APIs that administer header, line, and DFF attribute maintenance, which write to both the current and history tables.

Because OKE_K_USER_ATTRIBUTES_H is a history table, it is typically read-only in reporting contexts and should not be updated directly; changes flow in through the standard OKE contract amendment and versioning APIs.