Search Results okc_operation_lines

Overview

The OKC_OPERATION_LINES table is a core data object within the Oracle E-Business Suite Contracts Core (OKC) module, specifically in versions 12.1.1 and 12.2.2. It functions as a supporting table for the contract operations framework, which manages automated business processes and actions defined within a contract. The table's primary role is to provide granular, line-level detail for an Operation Instance. An Operation Instance represents the execution or planned execution of a specific business rule or action (e.g., generating a renewal, sending a notification, creating a mass change request). Therefore, OKC_OPERATION_LINES stores the detailed transactional or contextual information about what has occurred or is scheduled to occur for each step of that operation.

Key Information Stored

While the provided metadata does not list specific columns beyond foreign keys, the structure and relationships indicate the table's critical data elements. The primary identifier is the ID column, which serves as the primary key. The table's core function is to link operation details to the specific contract entities involved. This is achieved through foreign key columns that reference the subject and object of the operation. Key relational columns include OIE_ID, linking the line to its parent OKC_OPERATION_INSTANCES record; SUBJECT_CHR_ID and OBJECT_CHR_ID, referencing the subject and object contract headers (OKC_K_HEADERS_B); and SUBJECT_CLE_ID and OBJECT_CLE_ID, referencing the subject and object contract lines (OKC_K_LINES_B). The PARENT_OLE_ID column supports hierarchical relationships within operation lines themselves.

Common Use Cases and Queries

This table is essential for auditing, troubleshooting, and reporting on the automated lifecycle of contracts. A primary use case is tracing the complete history of an automated operation, such as a mass change, to understand which specific contract lines were processed. Technical consultants and support personnel often query this table to diagnose failed operations or to verify system-generated actions. A typical diagnostic query would join OKC_OPERATION_LINES to OKC_OPERATION_INSTANCES and the relevant contract headers or lines to retrieve a full audit trail.

• Sample Query Pattern: SELECT ol.* FROM okc_operation_lines ol, okc_operation_instances oi WHERE ol.oie_id = oi.id AND oi.operation_code = 'MASS_CHANGE' AND ol.subject_chr_id = :p_contract_id;
• Reporting Use Case: Generating a report of all operations performed on a specific contract line within a date range, detailing the operation type and the associated object contract line.

Related Objects

The OKC_OPERATION_LINES table is centrally connected to several key Contracts Core tables via documented foreign key relationships. These relationships define its integration within the schema.

• OKC_OPERATION_INSTANCES: The parent table for all operation executions. Joined via OKC_OPERATION_LINES.OIE_ID.
• OKC_K_HEADERS_B: References the contract header for both the subject and object of the operation via SUBJECT_CHR_ID and OBJECT_CHR_ID.
• OKC_K_LINES_B: References the contract line for both the subject and object of the operation via SUBJECT_CLE_ID and OBJECT_CLE_ID.
• OKC_OPERATION_LINES (Self-Referential): Supports a parent-child hierarchy within operation lines via PARENT_OLE_ID.
• OKC_MASSCHANGE_REQ_DTLS: Is referenced by this table, indicating operation lines can be the source for mass change request details (OKC_MASSCHANGE_REQ_DTLS.OLE_ID).