Search Results object1_id2




Overview
Explore in AI Chat

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

Overview

OKC_OPERATION_INSTANCES is a core transactional table within the OKC (Contracts Core) schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It stores operation instances, where an operation instance represents a single runtime occurrence of a Contract Operation defined in OKC_CLASS_OPERATIONS. While the class operation defines the reusable template, behavior, and rules of a contract operation, the operation instance captures the specific execution context for a given contract and acts as the collection point for the detailed information generated by that operation. This table is central to contract lifecycle processing, including mass change, renewal, termination, and clause-driven automation.

From a Data Vault modeling perspective, the table's FK structure is heuristic-classified as satellite-leaning. It references parent descriptors (OKC_CLASS_OPERATIONS), the contract header hub (OKC_K_HEADERS_B), and FND_SECURITY_GROUPS rather than serving as a pure junction between two hubs. This suggests treating OKC_OPERATION_INSTANCES as a satellite attached to the contract header hub, carrying operation-specific descriptive and status attributes.

Key Information Stored

Common Use Cases and Queries

Typical reporting scenarios include tracing all operation instances executed against a specific contract, auditing mass change activity, and reconciling operation line detail. A simple status report by contract might read:

SELECT oi.id, oi.name, oi.status_code, oi.creation_date FROM okc_operation_instances oi WHERE oi.target_chr_id = :chr_id ORDER BY oi.creation_date DESC;

A joined query resolving the operation class and the lines collected beneath each instance would use OKC_CLASS_OPERATIONS via COP_ID and OKC_OPERATION_LINES via OIE_ID. Queries filtering on BATCH_ID support mass change request monitoring, while filters on REQUEST_ID and PROGRAM_ID support concurrent program diagnostics. The SECURITY_GROUP_ID column should be used in any query executed on behalf of an organization-restricted user.

Related Objects

  • OKC_CLASS_OPERATIONS — Parent definition table; joined on OKC_OPERATION_INSTANCES.COP_ID = OKC_CLASS_OPERATIONS.ID.
  • OKC_K_HEADERS_B — Contract header hub; joined on OKC_OPERATION_INSTANCES.TARGET_CHR_ID = OKC_K_HEADERS_B.ID.
  • OKC_OPERATION_LINES — Detail lines belonging to an instance; joined on OKC_OPERATION_LINES.OIE_ID = OKC_OPERATION_INSTANCES.ID.
  • OKC_MASSCHANGE_REQ_DTLS — Mass change request detail rows referencing instances via OIE_ID.
  • FND_SECURITY_GROUPS — Security grouping referenced by SECURITY_GROUP_ID.