Results for “oke_k_fifo_logs_u1”

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

Overview

OKE.OKE_K_FIFO_LOGS is a transactional table in the Oracle E-Business Suite Contracts (OKE) module that maintains the list of most recently accessed contract documents for each user using a first-in, first-out (FIFO) eviction algorithm. The table exists to support the "recent document list" navigation feature within Oracle Contracts, allowing users to quickly return to contract documents they have worked on recently without re-running a full query. The number of contract documents retained per user per document list is governed by the profile option OKE: Recent Document List; when that threshold is exceeded, the oldest entries are aged out in FIFO order.

The table is owned by the OKE schema, resides in the APPS_TS_TX_DATA tablespace with PCTFREE 10, and is documented as VALID in both Oracle EBS 12.1.1 and 12.2.2. The ETRM dependency record confirms that OKE_K_FIFO_LOGS does not reference any database object directly, but it is referenced by the APPS synonym OKE_K_FIFO_LOGS and logically joins to OKE_K_HEADERS through the K_HEADER_ID column. From a Data Vault modeling perspective, the mined classification suggests this object is satellite-leaning — it records descriptive, user-context state (recent access, sequence position) around a business key that ultimately resolves to a contract document header, rather than representing an independent hub or an associative link between two distinct hubs.

Key Information Stored

Each row captures a single "recent document" pointer for a given user and document list. The most significant columns are:

• USER_LOG_ID (NUMBER) — The surrogate primary key, enforced by the unique index OKE_K_FIFO_LOGS_U1. This is the sole column of the table's primary key and is generated as the recent-document-list unique identifier.
• OBJECT_NAME (VARCHAR2(30)) — Identifies the document list to which the entry belongs. The metadata notes that each user owns three contract document logs, one per contract document type, so OBJECT_NAME distinguishes those lists.
• K_HEADER_ID (NUMBER) — The unique identifier of the contract document header being tracked. This is a foreign key to OKE_K_HEADERS and is the column through which the recent-document entry resolves to an actual contract.
• SEQUENCE (NUMBER) — The recent-document sequence position, used to order entries and drive the FIFO eviction behavior. It is the fourth column of the non-unique index OKE_K_FIFO_LOGS_N1.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard Who columns providing audit trail and, importantly, the user attribution. CREATED_BY participates in the business-key unique index OKE_K_FIFO_LOGS_U2.

Two unique indexes act as business-key candidates. OKE_K_FIFO_LOGS_U1 (USER_LOG_ID) is the declared primary key and is purely surrogate. OKE_K_FIFO_LOGS_U2 (OBJECT_NAME, CREATED_BY, K_HEADER_ID) is the meaningful business key: it guarantees that a given user (CREATED_BY) sees any single contract document (K_HEADER_ID) at most once within a given document list (OBJECT_NAME). OKE_K_FIFO_LOGS_N1 (OBJECT_NAME, SEQUENCE, CREATED_BY) is a non-unique index optimized for FIFO retrieval and ordering per list per user. The complete documented column set is nine columns.

Common Use Cases and Queries

Business and technical scenarios center on retrieving and maintaining recent-access lists for contract users, and on diagnosing FIFO behavior when the profile option threshold changes.

• Recent document list retrieval — Order a user's entries within a document list by SEQUENCE to render the "recent documents" navigation. The N1 index supports this directly:

SELECT k_header_id, sequence, creation_date
FROM   oke.oke_k_fifo_logs
WHERE  object_name = :p_object_name
AND    created_by  = :p_user_id
ORDER  BY sequence;

• Resolving a recent entry to its contract — Join to OKE_K_HEADERS on K_HEADER_ID to surface contract number, status, and parties for the recent list.
• Detecting duplicates or FIFO anomalies — Grouping by OBJECT_NAME, CREATED_BY to count retained documents per user validates that the count does not exceed the profile-option limit and that no duplicate business keys exist:

SELECT object_name, created_by, COUNT(*)
FROM   oke.oke_k_fifo_logs
GROUP  BY object_name, created_by
HAVING COUNT(*) > :profile_limit;

• Audit and purge reporting — Using CREATION_DATE / LAST_UPDATE_DATE to identify stale entries for housekeeping or to reconcile usage against the OKE: Recent Document List profile setting.
• Per-contract access history — Filtering on K_HEADER_ID to determine which users recently accessed a specific contract.

Related Objects

The dependency data confirms the following relationships, supplemented by standard OKE module context:

• OKE.OKE_K_HEADERS — The contract document header table. The documented foreign key OKE_K_FIFO_LOGS.K_HEADER_ID → OKE_K_HEADERS resolves each recent-document entry to its contract. This is the principal join.
• APPS.OKE_K_FIFO_LOGS — The APPS-layer synonym through which application code and reports access the table; the ETRM record lists it explicitly as a referencing object.
• OKE_K_FIFO_LOGS_U1 / U2 / N1 — The unique and non-unique indexes that enforce the surrogate and business keys and support FIFO ordering. OKE_K_FIFO_LOGS_U2 (OBJECT_NAME, CREATED_BY, K_HEADER_ID) is the index most relevant when investigating the user's search term and business-key duplicates.
• OKE: Recent Document List profile option — Not a database object, but the configuration controlling how many rows per user per list may persist; it is central to interpreting table contents.
• FND_USER — Standard EBS reference that reconciles CREATED_BY / LAST_UPDATED_BY to a user name for reporting recent-document lists by person.

Collectively, these objects establish OKE_K_FIFO_LOGS as a lightweight, user-scoped satellite of contract header activity, tightly coupled to OKE_K_HEADERS and driven by the Recent Document List profile option.