Results for “okc_condition_occurs”

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

Overview

OKC_CONDITION_OCCURS is a transactional table within the OKC (Contracts Core) schema of Oracle E-Business Suite, available in both 12.1.1 and 12.2.2. It stores each occurrence of a Condition defined in OKC_CONDITION_HEADERS_B. While the header table holds the reusable definition of a contract condition—such as payment terms, pricing clauses, or deliverable obligations—OKC_CONDITION_OCCURS captures the point-in-time instantiation of that condition against a specific contract, quote, or related business document. The object is registered in ETRM with a VALID status and is owned by the OKC schema.

From a Data Vault modeling perspective, the FK structure suggests this object is hub-leaning. The table is anchored by a distinct surrogate key (ID) and carries a foreign key to OKC_CONDITION_HEADERS_B (CNH_ID), together with a date/time attribute and standard audit columns. This pattern is characteristic of a core business entity rather than a pure link or satellite, though it also carries attributes and point-in-time data that would map naturally to satellite structures in a Data Vault design.

Key Information Stored

The table contains 10 documented columns. The most significant are:

• ID — Surrogate primary key (OKC_CONDITION_OCCURS_PK), uniquely identifying each occurrence. It is also the business-key candidate surfaced through the unique index OKC_CONDITION_OCCURS_U1.
• CNH_ID — Foreign key to OKC_CONDITION_HEADERS_B, linking the occurrence to its condition definition.
• DATETIME — The effective or reference date/time of the occurrence.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the Oracle ADF/BC4J framework to detect concurrent updates.
• CREATED_BY, CREATION_DATE — Standard WHO audit columns identifying the user and timestamp of row creation.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — WHO audit columns capturing the most recent modification context.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, enforcing multi-org/multi-tenant data security.

The overlap between the surrogate ID and the U1 unique index indicates that ID serves dual purposes as both technical and candidate business key in the physical model.

Common Use Cases and Queries

Typical scenarios include reconciling contract condition occurrences against their definitions, auditing condition timing, and reporting on conditions active for a given contract period. A common join retrieves condition text alongside each occurrence:

• SELECT o.id, h.condition_name, o.datetime FROM okc_condition_occurs o JOIN okc_condition_headers_b h ON h.id = o.cnh_id;
• Filtering by SECURITY_GROUP_ID to honor organization-level access restrictions in multi-org deployments.
• Auditing recent changes using LAST_UPDATE_DATE and LAST_UPDATED_BY.
• Reconciling resolved time values through OKC_RESOLVED_TIMEVALUES.COE_ID for SLA or milestone reporting.

Related Objects

OKC_CONDITION_OCCURS sits at the center of a small but important relationship cluster:

• OKC_CONDITION_HEADERS_B — Parent definition table, joined via CNH_ID.
• OKC_ACTION_ATT_VALS — Child table referencing COE_ID, holding action attribute values for the occurrence.
• OKC_RESOLVED_TIMEVALUES — Child table referencing COE_ID, storing resolved time values used in condition evaluation.
• FND_SECURITY_GROUPS — Referenced via SECURITY_GROUP_ID for row-level security.

These relationships make the table a pivotal junction between condition definitions and their downstream action and time-value resolutions within the Contracts Core module.