Results for “okc_risk_events_tl”

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

Overview

OKC_RISK_EVENTS_TL is the translation table for risk events within the Oracle Contracts Core (OKC) module. In Oracle E-Business Suite 12.1.1 and 12.2.2, Contracts Core provides the foundational infrastructure for authoring, negotiating, and managing contract documents, and risk events represent configurable business exceptions or contingencies that can be attached to contract terms. Because Oracle EBS supports multiple installed languages, any user-facing descriptive text associated with a risk event must be stored in a language-specific translation row. OKC_RISK_EVENTS_TL fulfills that role, holding the translatable attributes for each risk event while the base (non-translated) attributes reside in the corresponding base table, OKC_RISK_EVENTS_B.

The object is owned by the OKC schema and is classified as VALID in the ETRM repository. Its documented physical schema in ETRM 12.2.2 comprises 10 columns. From a heuristic Data Vault modeling perspective, this table is classified as standalone, meaning the mined foreign-key structure did not reveal a parent-child dependency requiring hub, link, or satellite treatment. This classification should be treated as a modeling suggestion rather than a prescriptive design rule, since translation tables are inherently satellites of their base entities in a strict Data Vault interpretation, but no explicit FK evidence was documented.

Key Information Stored

The table's most important columns are organized around a composite primary key and two unique business-key candidates.

• RISK_EVENT_ID — Surrogate identifier for the risk event. This column participates in the primary key and links each translation row back to its base record in OKC_RISK_EVENTS_B.
• LANGUAGE — The NLS language code identifying the language of the translated text. Together with RISK_EVENT_ID, it forms the composite primary key OKC_RISK_EVENTS_TL_PK.
• NAME — The translated display name of the risk event. This is a significant business attribute and is part of the second unique index, OKC_RISK_EVENTS_TL_U2, combined with LANGUAGE, making (NAME, LANGUAGE) a business-key candidate.
• DESCRIPTION — The translated long description of the risk event, used in contract authoring and review screens.
• SOURCE_LANG — Indicates the source language from which the translation was derived, supporting the standard Oracle translation (TL) pattern.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard Oracle EBS audit columns capturing who created and last modified each translation row, when, and through which login session.

The primary key OKC_RISK_EVENTS_TL_PK (RISK_EVENT_ID, LANGUAGE) distinguishes individual translation rows, while the unique index OKC_RISK_EVENTS_TL_U1 (RISK_EVENT_ID, LANGUAGE) enforces the same constraint at the index level. OKC_RISK_EVENTS_TL_U2 (NAME, LANGUAGE) enforces uniqueness of the translated name within each language, which is a meaningful business rule.

Common Use Cases and Queries

Typical usage involves joining translation rows to the base table to present risk event text in the user's session language, or filtering to a specific language for reporting.

• Retrieve the translated name and description for a given risk event: SELECT name, description FROM okc_risk_events_tl WHERE risk_event_id = :id AND language = USERENV('LANG');
• Join base and translation tables to produce a language-complete report: SELECT b.risk_event_id, t.name, t.description FROM okc_risk_events_b b, okc_risk_events_tl t WHERE b.risk_event_id = t.risk_event_id AND t.language = 'US';
• Identify which languages exist for a risk event: SELECT language FROM okc_risk_events_tl WHERE risk_event_id = :id;
• Detect missing translations by comparing base counts to translation counts per language.
• Audit recently modified translations using LAST_UPDATE_DATE for change-tracking reports.

Related Objects

The following objects are most significant in relation to OKC_RISK_EVENTS_TL. Join columns are inferred from the documented primary key and the standard Oracle TL pattern.

• OKC_RISK_EVENTS_B — The base table holding non-translated risk event attributes. Joined on RISK_EVENT_ID.
• OKC_RISK_EVENTS_V — The translated view that commonly unions or selects from the base and TL tables for user-facing queries.
• OKC_RISK_EVENTS_TL_PK — The primary key constraint enforcing uniqueness of (RISK_EVENT_ID, LANGUAGE).
• OKC_RISK_EVENTS_TL_U1 and OKC_RISK_EVENTS_TL_U2 — Unique indexes supporting key and business-name integrity.
• OKC_RISK_EVENT_DEFINITIONS — Related definitional content that may be associated with risk events.
• OKC_TERMS_TL — A parallel translation table demonstrating the consistent OKC translation pattern.

Because the heuristic classification is standalone, no FK dependencies were documented within the mined structure; relationships above are based on the standard translation-table convention and the shared RISK_EVENT_ID key.