Search Results okc_rep_recent_contracts

Overview

The OKC_REP_RECENT_CONTRACTS table is a reference table within the Oracle Contracts Core (OKC) module of Oracle E-Business Suite, present in both 12.1.1 and 12.2.2. It stores a record of contracts that a given user has recently viewed from the Contract Repository, enabling the application to present a personalized "recently viewed contracts" list. Rather than holding contractual content itself, the table acts as a lightweight tracking mechanism that maps an application user to the business documents they have accessed. Its role is purely operational and presentation-oriented; it supports navigation and user experience within the Contracts Repository rather than enforcing transactional contract logic.

Under the heuristic Data Vault classification mined from its foreign-key structure, this object is documented as standalone. As a modeling suggestion, this classification implies the table neither behaves as a hub nor as a dependent satellite of a parent contract entity; it records an independent association between a user and a viewed document. This makes it a convenience or audit-style log rather than a core dimension of the contracts data model.

Key Information Stored

The documented physical schema comprises nine columns in the OKC schema. The most significant are:

• USER_ID — the application user who viewed the contract; a component of both the primary key and the unique index.
• BUSINESS_DOCUMENT_ID — the identifier of the contract or business document that was viewed; also a key component.
• BUSINESS_DOCUMENT_TYPE — the type discriminator for the referenced document, allowing the same table to track multiple document categories; a key component.
• LAST_VISITED_DATE — the timestamp of the most recent access, used to order or age the recency list.
• CREATED_BY, CREATION_DATE — standard Oracle who/audit columns recording initial insertion of the row.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns capturing the last modification and login context.

The primary key OKC_REP_RECENT_CONTRACTS_PK1 is defined over the composite of USER_ID, BUSINESS_DOCUMENT_ID, and BUSINESS_DOCUMENT_TYPE. A unique index, OKC_REP_RECENT_CONTRACTS_U1, is defined over the same three columns. Because the primary key and the unique index share an identical column set, the business-key candidate is the same composite; no separate surrogate key column is documented. The composite key enforces that a user has at most one recency record per business document.

Common Use Cases and Queries

Typical usage centers on retrieving a user's most recently accessed contracts for display in the Repository UI or in custom reporting. A representative query to list the latest viewed contracts for a user is:

• SELECT BUSINESS_DOCUMENT_ID, BUSINESS_DOCUMENT_TYPE, LAST_VISITED_DATE FROM OKC.OKC_REP_RECENT_CONTRACTS WHERE USER_ID = :p_user_id ORDER BY LAST_VISITED_DATE DESC;

Administrators may profile activity by joining the table to user and contract reference data, for example to identify frequently viewed documents or dormant contracts. A cleanup or archival routine might delete aged rows:

• DELETE FROM OKC.OKC_REP_RECENT_CONTRACTS WHERE LAST_VISITED_DATE < SYSDATE - 365;

Because recency data is user-specific and low-volume per user, it is well suited to dashboard widgets and personalized navigation menus rather than to financial or analytical reporting. The LAST_VISITED_DATE column provides the natural sort key for recency ordering.

Related Objects

Consistent with its standalone classification, the table has no documented foreign keys to parent entities. Its relationships are logical rather than enforced:

• OKC_K_HEADERS (contract headers) — joined on BUSINESS_DOCUMENT_ID to resolve the viewed document where the type indicates a contract.
• OKC_K_LINES (contract lines) — related through the parent contract referenced by the recency record.
• FND_USER — joined on USER_ID to resolve the application user who viewed the document.
• OKC_REP_* Repository views and APIs — the Contract Repository UI and its supporting APIs read from this table to render the recently viewed list.
• OKC_BUSINESS_DOCUMENTS / document type lookups — interpret BUSINESS_DOCUMENT_TYPE and the referenced document identity.

In summary, OKC_REP_RECENT_CONTRACTS is a small, standalone tracking table that enhances the usability of the Oracle Contracts Repository by recording which contracts each user viewed most recently.