Search Results okc_operation_instances




Overview
Explore in AI Chat

Overview

The OKC_OPERATION_INSTANCES table is a core data object within the Oracle E-Business Suite Contracts Core (OKC) module. It serves as the transactional repository for instances of predefined contract operations. In the context of contract lifecycle management, an operation is a business process or action, such as a renewal, amendment, or termination, defined within a contract template or class. When such an operation is initiated for a specific contract, an instance is created and recorded in this table. Its primary role is to track the execution and status of these operational workflows, acting as a central collection point for detailed information that drives the contract's progression through its defined business processes in both EBS 12.1.1 and 12.2.2.

Key Information Stored

While the provided metadata does not list specific columns, the foreign key relationships and description define the critical data elements. Each record represents a single execution instance of a contract operation. The table's primary key is the ID column (OIE_ID). Crucially, it stores foreign key references that anchor the operation instance to its definition and its associated contract. The COP_ID column links to OKC_CLASS_OPERATIONS, identifying the template or class operation being instantiated. The TARGET_CHR_ID column links to OKC_K_HEADERS_B, the base contracts table, specifying the contract upon which the operation is being performed. Additional columns likely track the instance's status, start date, completion date, initiator, and other execution attributes necessary for managing the operation's lifecycle.

Common Use Cases and Queries

A primary use case is generating reports on pending or in-progress contract operations across the enterprise, such as identifying all renewal operations scheduled for the current quarter. Support personnel may query this table to diagnose the status of a specific operation that appears stalled. A common SQL pattern involves joining to the contract headers and operation definitions to create a meaningful report:

  • SELECT khr.contract_number, cop.operation_name, oie.status, oie.start_date FROM okc_operation_instances oie, okc_k_headers_b khr, okc_class_operations cop WHERE oie.target_chr_id = khr.id AND oie.cop_id = cop.id AND oie.status = 'IN_PROGRESS';

Another critical use case is during mass change requests, where this table is referenced by OKC_MASSCHANGE_REQ_DTLS to track which operation instances are affected by a bulk update.

Related Objects

The OKC_OPERATION_INSTANCES table is central to the Contracts Core operational model. Its key relationships, as documented, are:

  • OKC_CLASS_OPERATIONS: The source definition for the operation instance, via the COP_ID foreign key.
  • OKC_K_HEADERS_B: The target contract for the operation, via the TARGET_CHR_ID foreign key.
  • OKC_OPERATION_LINES: Contains detailed line-level information (e.g., specific clauses or articles being modified) that is associated with and collected under a single operation instance.
  • OKC_MASSCHANGE_REQ_DTLS: References this table to manage the impact of mass change requests on specific operation instances.