Results for “okc_rep_imp_risks_t_u1”

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

Overview

The table OKC.OKC_REP_IMP_RISKS_T is a Contracts Core (OKC) repository object that stores risk-line information associated with contract records processed through the Oracle EBS contract import (repository import) framework. It belongs to the OKC schema and is classified as VALID in both Oracle EBS 12.1.1 and 12.2.2. The table captures the risk events, probability ratings, impact assessments, and occurrence indicators recorded against each imported contract, supporting downstream contract risk analysis and reporting.

From a Data Vault modeling perspective, the heuristic classification derived from the foreign key structure identifies this table as standalone. No parent-child hierarchy beyond its two outbound references is documented, suggesting that the object is best modeled as an independent entity or a link-style association between imported contracts and risk events, rather than as a pure hub or satellite. This classification is a modeling suggestion only; the physical table is a standard relational structure with 22 documented columns.

Key Information Stored

The table maintains a surrogate primary key, IMP_RISK_ID, which is also the sole business-key candidate, enforced by the unique index OKC_REP_IMP_RISKS_T_U1. The most significant columns include:

• IMP_CONTRACT_ID — foreign key to OKC_REP_IMP_CONTRACTS_T, linking each risk line to its parent imported contract.
• RISK_EVENT_ID — foreign key to OKC_RISK_EVENTS_B, tying the row to the master risk event definition.
• RISK_INDEX — ordinal position of the risk within the contract.
• RISK_EVENT_TXT — free-text description of the risk event.
• PROBABILITY_TXT and PROBABILITY_CODE — the probability assessment in display and coded form.
• RISK_IMPACT_TXT and RISK_IMPACT_CODE — the impact assessment in display and coded form.
• RISK_COMMENTS — additional narrative remarks.
• RISK_OCCURED_YN and RISK_OCCURENCE_DATE — whether the risk materialized and when.
• BUSINESS_DOCUMENT_TYPE, BUSINESS_DOCUMENT_ID, BUSINESS_DOCUMENT_VERSION — business document context for the risk record.
• Concurrent-program audit columns: PROGRAM_ID, PROGRAM_LOGIN_ID, PROGRAM_APPLICATION_ID, REQUEST_ID, RUN_ID.

Common Use Cases and Queries

Typical usage centers on reviewing risks imported with contracts and validating import completeness. A representative query joining to the parent contract table is:

• SELECT r.IMP_RISK_ID, r.IMP_CONTRACT_ID, r.RISK_EVENT_TXT, r.PROBABILITY_CODE, r.RISK_IMPACT_CODE FROM OKC.OKC_REP_IMP_RISKS_T r WHERE r.IMP_CONTRACT_ID = :contract_id;
• Risk-event reconciliation: join to OKC_RISK_EVENTS_B on RISK_EVENT_ID to resolve master event attributes.
• Concurrent-program traceability: filter by REQUEST_ID or RUN_ID to audit import runs.
• Reporting on realized risks using RISK_OCCURED_YN and RISK_OCCURENCE_DATE.
• Duplicate detection across BUSINESS_DOCUMENT_ID and RISK_INDEX combinations.

Related Objects

The following objects are the most significant for navigation and joins:

• OKC_REP_IMP_CONTRACTS_T — parent contract import table; join on IMP_CONTRACT_ID.
• OKC_RISK_EVENTS_B — master risk event definitions; join on RISK_EVENT_ID.
• OKC_REP_IMP_RISKS_T_U1 — unique index supporting the primary key.
• OKC contract import concurrent programs and repository APIs that populate this table during contract import.
• OKC risk management views and business logic that consume the risk attributes stored here.