Search Results okc_rep_contracts_all




Overview
Explore in AI Chat

Overview

OKC_REP_CONTRACTS_ALL is the master repository table for the Oracle Contracts Core (OKC) module in Oracle E-Business Suite. As documented in the ETRM metadata, this is the main Contracts table, storing the latest version of all Repository-authored contracts. Within the OKC schema, it functions as the authoritative record from which contract parties, relationships, access controls, and related business documents are derived. The table is central to contract authoring, negotiation tracking, approval routing, and lifecycle management across the enterprise.

From a Data Vault modeling perspective, the FK-based heuristic classifies OKC_REP_CONTRACTS_ALL as hub-leaning. It is anchored by a single, stable surrogate primary key (CONTRACT_ID) and acts as the integration point for multiple downstream satellite and link structures. This suggests the table behaves as a business hub for contract identity, with descriptive attributes carried at the same grain and numerous dependent objects attaching through foreign keys. The presence of SOURCE_CODE, ORIG_SYSTEM_REFERENCE_CODE, and related columns further supports its role as a canonical contract registry.

Key Information Stored

The table exposes 70 documented columns in ETRM 12.2.2. The most operationally significant ones are:

Common Use Cases and Queries

Reporting and integration scenarios frequently query OKC_REP_CONTRACTS_ALL to list active contracts, track expirations, or reconcile contract data with purchasing and receivables. A typical pattern retrieves contracts nearing expiration:

  • SELECT CONTRACT_ID, CONTRACT_NUMBER, CONTRACT_NAME, CONTRACT_EXPIRATION_DATE FROM OKC.OKC_REP_CONTRACTS_ALL WHERE ORG_ID = :org_id AND CONTRACT_STATUS_CODE = 'ACTIVE' AND CONTRACT_EXPIRATION_DATE BETWEEN SYSDATE AND SYSDATE + 90;
  • Join to OKC_BUS_DOC_TYPES_B on CONTRACT_TYPE = DOCUMENT_TYPE_ID to categorize contracts by type.
  • Join to OKC_REP_CONTRACT_PARTIES on CONTRACT_ID to retrieve parties and their roles.
  • Link to workflow tables via WF_ITEM_TYPE and WF_ITEM_KEY to report on pending approvals.

Because CONTRACT_ID is a reliable unique key, this table is a preferred driving source for extracts into data warehouses and for custom concurrent programs.

Related Objects

  • OKC_BUS_DOC_TYPES_B — Referenced via CONTRACT_TYPE; supplies document type definitions.
  • OKC_REP_CONTACT_ROLES_B — Referenced via NOTIFY_CONTACT_ROLE_ID for notification roles.
  • OKC_REP_CONTRACT_PARTIES — Child table joined on CONTRACT_ID; stores contractual parties.
  • OKC_REP_CONTRACT_RELS — Child table joined on CONTRACT_ID; captures contract relationships.
  • OKC_REP_CONTRACT_ACCESS — Child table joined on CONTRACT_ID; manages access control lists.
  • OKC_REP_CONTRACTS_ALL_PK / _U1 — Primary and unique indexes anchored on CONTRACT_ID.