Results for “oke_k_user_attributes”

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

Overview

OKE_K_USER_ATTRIBUTES is a transactional table in the OKE (Project Contracts) product family of Oracle E-Business Suite, available in both 12.1.1 and 12.2.2. It stores the flexfield-style user attribute header and line records associated with Project Contracts, allowing implementers to capture customer-specific descriptive data against contract headers and contract lines without modifying the base schema. The table is owned by the OKE schema and is reported as VALID in the ETRM data dictionary.

From a Data Vault modeling perspective, the documented foreign key structure (K_HEADER_ID referencing OKE_K_HEADERS and K_LINE_ID referencing OKE_K_LINES) plus a surrogate unique identifier suggests a link classification. This table behaves as an association between the header and line entities and the user-defined attribute set defined by USER_ATTRIBUTE_CONTEXT, rather than as a pure descriptive satellite.

Key Information Stored

The table contains 40 documented columns. The most significant are the identifiers and the auditing and descriptive attributes:

• K_USER_ATTRIBUTE_ID — the surrogate primary key, enforced by OKE_K_USER_ATTRIBUTES_PK and unique index OKE_K_USER_ATTRIBUTES_U1. This is the single unique business-key candidate documented.
• K_HEADER_ID — foreign key to OKE_K_HEADERS, identifying the contract header the user attributes belong to.
• K_LINE_ID — foreign key to OKE_K_LINES, identifying the contract line the user attributes belong to.
• USER_ATTRIBUTE_CONTEXT — a context discriminator that identifies the flexfield context or attribute group in effect for a given row, allowing multiple attribute sets to coexist. It participates with K_HEADER_ID and K_LINE_ID in the unique index OKE_K_USER_ATTRIBUTES_UK01.
• USER_ATTRIBUTE01 through USER_ATTRIBUTE30 — thirty generic character columns holding the actual user-defined values. Callers populate only those needed for the active context; the remaining columns stay null.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard EBS WHO columns capturing creation and change audit history.
• RECORD_VERSION_NUMBER — an optimistic locking token used to detect concurrent updates to the same attribute record.

Because the attribute columns are generically typed, the semantic meaning of each USER_ATTRIBUTEn column is defined externally by the flexfield definition and the value of USER_ATTRIBUTE_CONTEXT.

Common Use Cases and Queries

Typical usage covers reporting on customer-specific contract data, integration extracts, and validation of DFF (Descriptive Flexfield) population.

• Retrieving all user attributes for a given contract header:

  SELECT * FROM OKE.OKE_K_USER_ATTRIBUTES
  WHERE K_HEADER_ID = :p_header_id;

• Joining header-level attributes to the parent contract:

  SELECT h.contract_number, ua.user_attribute_context, ua.user_attribute01
  FROM OKE.OKE_K_HEADERS h, OKE.OKE_K_USER_ATTRIBUTES ua
  WHERE h.k_header_id = ua.k_header_id
  AND ua.user_attribute_context = :p_context;

• Filtering line-level attributes to a specific contract line:

  SELECT * FROM OKE.OKE_K_USER_ATTRIBUTES
  WHERE K_LINE_ID = :p_line_id;

• Auditing recent changes using the WHO columns:

  SELECT k_user_attribute_id, last_updated_by, last_update_date
  FROM OKE.OKE_K_USER_ATTRIBUTES
  WHERE last_update_date >= SYSDATE - 7;

Reporting and migration scripts should always filter on USER_ATTRIBUTE_CONTEXT to avoid mixing attribute sets, and should treat the USER_ATTRIBUTEn columns as string-typed regardless of the intended business type.

Related Objects

• OKE_K_HEADERS — parent contract header table, joined via OKE_K_USER_ATTRIBUTES.K_HEADER_ID = OKE_K_HEADERS.K_HEADER_ID.
• OKE_K_LINES — parent contract line table, joined via OKE_K_USER_ATTRIBUTES.K_LINE_ID = OKE_K_LINES.K_LINE_ID.
• OKE_K_USER_ATTRIBUTES_PK / OKE_K_USER_ATTRIBUTES_U1 — primary key and unique index on K_USER_ATTRIBUTE_ID.
• OKE_K_USER_ATTRIBUTES_UK01 — unique index on K_HEADER_ID, K_LINE_ID, and USER_ATTRIBUTE_CONTEXT, enforcing one attribute set per context per header or line.
• OKE_K_HEADERS and OKE_K_LINES related views and APIs — the OKE Project Contracts APIs that read and write contract header and line data generally also surface the associated user attributes for DFF handling.