Search Results okc_risk_events_b




Overview
Explore in AI Chat

Overview

OKC_RISK_EVENTS_B is a Contracts Core (OKC) base table that stores the user-defined risk events available to the Oracle E-Business Suite Contracts module. Risk events represent the catalog of adverse occurrences that users may associate with a contract, contract line, or contract risk record for the purpose of scoring and tracking contractual exposure. The table functions as a definition or lookup repository rather than a transactional ledger; individual risk assessments that reference these definitions are recorded elsewhere, primarily in OKC_CONTRACT_RISKS.

The table carries the standard EBS concurrency and auditing columns, indicating that rows are maintained through Oracle Forms or the Contracts application programming interfaces rather than direct SQL. Based on the foreign key topology mined from the documented schema, the object is standalone, with no inbound foreign keys from other tables listed in the relationship data. Applying a heuristic Data Vault classification, OKC_RISK_EVENTS_B is best modeled as a reference or hub-style entity: its surrogate identifier RISK_EVENT_ID is stable, unique, and referenced by dependent transaction tables, while the datable START_DATE and END_DATE attributes suggest that a satellite would be required to capture the temporal validity of each risk event definition.

Key Information Stored

The documented physical schema contains nine columns. The most significant are:

  • RISK_EVENT_ID — the surrogate primary key, enforced by OKC_RISK_EVENTS_B_PK and additionally protected by the unique index OKC_RISK_EVENTS_B_U1. This is the value propagated to dependent tables as a foreign key.
  • START_DATE — the date from which the risk event definition becomes effective and selectable within the Contracts application.
  • END_DATE — the date on which the risk event definition is retired or no longer available for new associations.
  • OBJECT_VERSION_NUMBER — the optimistic locking counter used by the EBS framework to detect concurrent updates.
  • CREATED_BY, CREATION_DATE — the standard who-audit pair recording the user and timestamp of row insertion.
  • LAST_UPDATED_BY, LAST_UPDATE_DATE — the standard who-audit pair recording the most recent modification to the row.
  • LAST_UPDATE_LOGIN — the login identifier of the session that performed the last update, used for audit and diagnostic tracing.

The START_DATE/END_DATE pair functions as a partial business key describing the validity window of a risk event, while RISK_EVENT_ID remains the sole unique business-key candidate documented in the metadata.

Common Use Cases and Queries

The principal use case is populating the risk event list of values presented to users when creating or editing contract risk records. Reporting queries typically join the base table to its translation or descriptive companion to obtain the event name and description, and then to OKC_CONTRACT_RISKS to measure how frequently each event is cited.

A representative validity query retrieves risk events active on a given date:

  • SELECT risk_event_id, start_date, end_date FROM okc.okc_risk_events_b WHERE TRUNC(SYSDATE) BETWEEN start_date AND NVL(end_date, TRUNC(SYSDATE));
  • SELECT r.risk_event_id, COUNT(*) FROM okc.okc_contract_risks r GROUP BY r.risk_event_id ORDER BY 2 DESC;
  • SELECT b.* FROM okc.okc_risk_events_b b WHERE b.last_update_date >= :p_since; for incremental extraction into a reporting or warehouse layer.

Because the object resides in the OKC schema, custom queries should be schema-qualified or executed under a responsibility whose MO: Security profile grants access to the Contracts tables.

Related Objects

  • OKC_CONTRACT_RISKS — the primary dependent table. Its RISK_EVENT_ID column carries a foreign key to OKC_RISK_EVENTS_B, meaning every contract risk record may reference one of these definitions.
  • OKC_RISK_EVENTS_TL — the translation table that supplies language-specific names and descriptions for each risk event, joined on RISK_EVENT_ID.
  • OKC_RISK_EVENTS_V — the commonly used view joining the base and translation tables for user-facing queries.
  • OKC_RISK_EVENTS_B_PK and OKC_RISK_EVENTS_B_U1 — the constraint and unique index that enforce uniqueness of RISK_EVENT_ID and protect referential integrity for dependent rows.
  • OKC_CONTRACT_RISK_LINES and related Contracts risk assessment entities — downstream consumers that inherit risk event context through OKC_CONTRACT_RISKS.

Together these objects form the risk definition and risk assessment layer of the Oracle Contracts Core model, with OKC_RISK_EVENTS_B serving as the controlled vocabulary that underpins all downstream risk analysis.