Search Results oke_k_fifo_logs_pk

Overview

OKE_K_FIFO_LOGS is a table in the OKE (Project Contracts) product family of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. Per the ETRM metadata, its documented description is "User Contract Document Access FIFO Log." The table records first-in, first-out access history for contract documents associated with user contracts, providing an audit-oriented trail of which document objects were touched, by whom, and in what order. It is owned by the OKE schema and comprises nine documented columns.

From a Data Vault modeling perspective, the metadata's heuristic classification is satellite-leaning. This is consistent with the table's design: it carries a surrogate primary key (USER_LOG_ID), descriptive attributes such as OBJECT_NAME and SEQUENCE, and standard EBS audit columns, while its meaningful business relationship is expressed through a foreign key to OKE_K_HEADERS. Rather than acting as a hub of business entities or a link resolving many-to-many relationships, OKE_K_FIFO_LOGS behaves as a dependent, descriptive record attached to a contract header — the classic satellite pattern.

Key Information Stored

The table's documented columns and primary business content are as follows:

• USER_LOG_ID — the surrogate primary key, enforced by OKE_K_FIFO_LOGS_PK and also backed by unique index OKE_K_FIFO_LOGS_U1. It uniquely identifies each FIFO access log entry.
• OBJECT_NAME — identifies the contract document object being logged; part of the business-key candidate in OKE_K_FIFO_LOGS_U2.
• K_HEADER_ID — foreign key to OKE_K_HEADERS, tying each log row to a specific contract header; also part of OKE_K_FIFO_LOGS_U2.
• SEQUENCE — the ordering value that supports the FIFO semantics of the log (i.e., the relative order in which objects were accessed).
• CREATION_DATE and CREATED_BY — the timestamp and user who created the log entry; CREATED_BY participates in OKE_K_FIFO_LOGS_U2.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN — standard EBS audit trail columns tracking the most recent modification and the login context.

Notably, the unique index OKE_K_FIFO_LOGS_U2 (OBJECT_NAME, CREATED_BY, K_HEADER_ID) functions as the documented business-key candidate: it captures the natural combination of "who accessed which object for which contract." The surrogate key USER_LOG_ID remains the physical PK, while U2 enforces the semantic uniqueness of an access event.

Common Use Cases and Queries

Typical uses centre on auditing and document-access reporting for project contracts. A common pattern joins the log to OKE_K_HEADERS to resolve contract context:

• Access history by contract: SELECT l.USER_LOG_ID, l.OBJECT_NAME, l.SEQUENCE, l.CREATION_DATE, l.CREATED_BY FROM OKE.OKE_K_FIFO_LOGS l WHERE l.K_HEADER_ID = :header_id ORDER BY l.SEQUENCE;
• User activity audit: aggregate rows by CREATED_BY over a date range to identify which users accessed contract documents and how frequently.
• FIFO ordering checks: order by SEQUENCE (or CREATION_DATE) to reconstruct the exact order in which documents were accessed for a given header.
• Duplicate-access detection: query against the U2 business key (OBJECT_NAME, CREATED_BY, K_HEADER_ID) to validate unique access events or to find repeat touches.

These queries support compliance reporting, troubleshooting document-visibility issues, and reconstructing document consumption sequences in contract workflows.

Related Objects

• OKE_K_HEADERS — the sole documented foreign-key parent; joined via OKE_K_FIFO_LOGS.K_HEADER_ID = OKE_K_HEADERS.K_HEADER_ID.
• OKE_K_FIFO_LOGS_PK and OKE_K_FIFO_LOGS_U1 — primary-key constraint and unique index on USER_LOG_ID.
• OKE_K_FIFO_LOGS_U2 — unique business-key index on (OBJECT_NAME, CREATED_BY, K_HEADER_ID).
• OKE_K_LINES, OKE_K_ITEMS, and other OKE_K_* contract-structure tables — conceptually related through the contract header, offering fuller contract context.
• FND_USER — referenced logically through CREATED_BY / LAST_UPDATED_BY to resolve user names.