Search Results okc_contract_risks




Overview
Explore in AI Chat

Overview

OKC_CONTRACT_RISKS is a transaction table in the Contracts Core (OKC) schema of Oracle E-Business Suite, present in both 12.1.1 and 12.2.2. It stores the risk assessments captured against a contract, including the assessed probability and impact of each identified risk event, whether the risk has actually occurred, and any supporting narrative. A defining characteristic documented in the ETRM metadata is that risks recorded here are not version-specific: they attach to the contract as a whole rather than to a particular contract version or clause revision.

Under a heuristic Data Vault classification mined from the foreign key structure, this table resolves as a link. That is a modeling suggestion rather than a physical property: the table primarily records an association between a contract and a risk event, with its own descriptive attributes (probability, impact, comments, occurrence details) layered on top. It therefore behaves simultaneously as a relationship record and as a satellite of the contract-risk intersection.

Key Information Stored

The table is documented with 20 columns. The surrogate primary key is CONTRACT_RISK_ID, enforced by the constraint OKC_CONTRACT_RISKS_PK. The unique index OKC_CONTRACT_RISKS_U1 exposes the business-key candidate: BUSINESS_DOCUMENT_TYPE, BUSINESS_DOCUMENT_ID, BUSINESS_DOCUMENT_VERSION, and RISK_EVENT_ID, meaning a given risk event is recorded once per business document and version combination.

Common Use Cases and Queries

The most frequent requirement is reporting the risk profile of a contract or a portfolio of contracts. Because the business key is document-based rather than CONTRACT_ID-based, queries typically join through the document identifiers or through the contract header.

  • List all risks for a specific contract, filtered on BUSINESS_DOCUMENT_ID.
  • Aggregate exposure by RISK_EVENT_ID or by IMPACT_CODE to rank the most significant risks across a contract portfolio.
  • Identify risks that have materialized, using RISK_OCCURRED_FLAG = 'Y' and OCCURRENCE_DATE for trend or loss analysis.
  • Extract the descriptive attributes into a data warehouse or risk dashboard, using LAST_UPDATE_DATE for incremental loads.

A representative pattern filters on the business key and joins outward to the risk event definition to resolve codes to names:

  • SELECT r.CONTRACT_RISK_ID, r.RISK_EVENT_ID, r.PROBABILITY_CODE, r.IMPACT_CODE, r.RISK_OCCURRED_FLAG FROM okc.okc_contract_risks r WHERE r.business_document_id = :contract_id;

Because the table is not version-specific, no version-level history should be expected; the CURRENT version reference is the relevant scope for most reporting.

Related Objects

Two self-referencing foreign keys are documented, indicating hierarchical relationships within the table itself:

  • OKC_CONTRACT_RISKS.CONTRACT_ID — links a risk row to the parent contract record (self-referencing relationship).
  • OKC_CONTRACT_RISKS.RISK_EVENT_ID — links a risk row to its associated risk event (self-referencing relationship).

In practice, RISK_EVENT_ID resolves to the OKC risk event setup, and the business document columns align with the OKC contract header and version structures used throughout Contracts Core. Risk records are surfaced in the Contracts authoring and risk-management UI, and are read by standard contract reporting and by the Contract Terms and Risk APIs, which enforce the same business key when creating or updating risk lines. Any integration that inserts directly must satisfy OKC_CONTRACT_RISKS_U1 and supply OKC_CONTRACT_RISKS_PK values from the OKC sequence.