Search Results select_yn

Overview

The OKC_OPERATION_LINES table resides in the OKC schema and belongs to the Oracle Contracts Core (OKC) product family within Oracle E-Business Suite 12.1.1 and 12.2.2. The table records the detailed line-level information associated with an operation instance, providing additional context about what has occurred or is expected to occur for a given operation. This design allows ETRM (Enterprise Contracts) to capture the granular, directional, and hierarchical relationships between contract headers and lines that participate in operational events such as mergers, renewals, terminations, or mass changes.

From a heuristic Data Vault modeling perspective, this table is classified as satellite-leaning, reflecting the fact that it predominantly stores descriptive attributes tied to parent entities rather than acting as the hub of a business relationship. It depends on several hubs and links through its foreign key structure, particularly OKC_OPERATION_INSTANCES, OKC_K_HEADERS_B, and OKC_K_LINES_B.

Key Information Stored

The table contains 22 documented columns in the 12.2.2 physical schema. The most significant include:

• ID — The surrogate primary key, uniquely identified by the OKC_OPERATION_LINES_PK constraint and the OKC_OPERATION_LINES_U1 unique index. This is the business-key candidate for the row.
• OIE_ID — Foreign key to OKC_OPERATION_INSTANCES, tying each line to its parent operation instance.
• SUBJECT_CHR_ID / OBJECT_CHR_ID — Foreign keys to OKC_K_HEADERS_B, identifying the subject and object contract headers involved in the operation.
• SUBJECT_CLE_ID / OBJECT_CLE_ID — Foreign keys to OKC_K_LINES_B, identifying the corresponding contract lines.
• PARENT_OLE_ID — Self-referencing foreign key enabling hierarchical nesting of operation lines.
• SELECT_YN / ACTIVE_YN / PROCESS_FLAG — Control flags indicating whether the line is selected, active, or ready for processing.
• MESSAGE_CODE — Diagnostic or status message associated with the line.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, supporting multi-org security enforcement.
• OBJECT_VERSION_NUMBER — Optimistic locking column for concurrent update control.
• Standard WHO/audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) and concurrent program context columns (REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE).

Common Use Cases and Queries

Typical reporting and diagnostic scenarios include tracing which contract lines are affected by a given operation instance, auditing mass-change requests through OKC_MASSCHANGE_REQ_DTLS, and reconstructing the subject/object relationships for merger, split, or renewal operations.

• List all operation lines for an operation instance:

  SELECT ole.id, ole.subject_chr_id, ole.object_chr_id,
         ole.subject_cle_id, ole.object_cle_id, ole.process_flag
  FROM   okc_operation_lines ole
  WHERE  ole.oie_id = :operation_instance_id;

• Retrieve hierarchical operation lines with parent-child relationships:

  SELECT ole.id, ole.parent_ole_id, ole.message_code
  FROM   okc_operation_lines ole
  WHERE  ole.parent_ole_id IS NOT NULL;

• Cross-reference mass change details to affected operation lines:

  SELECT mrd.ole_id, ole.oie_id, ole.subject_chr_id
  FROM   okc_masschange_req_dtls mrd,
         okc_operation_lines     ole
  WHERE  mrd.ole_id = ole.id;

Related Objects

The following objects are most tightly coupled to OKC_OPERATION_LINES through foreign key and dependency relationships:

• OKC_OPERATION_INSTANCES — Parent operation instance; joined via OIE_ID.
• OKC_K_HEADERS_B — Contract headers referenced as subject or object via SUBJECT_CHR_ID and OBJECT_CHR_ID.
• OKC_K_LINES_B — Contract lines referenced as subject or object via SUBJECT_CLE_ID and OBJECT_CLE_ID.
• OKC_OPERATION_LINES (self) — Parent-child hierarchy via PARENT_OLE_ID.
• OKC_MASSCHANGE_REQ_DTLS — Mass-change request details that reference operation lines via OLE_ID.
• FND_SECURITY_GROUPS — Security group lookup via SECURITY_GROUP_ID for multi-org access control.

Together these objects provide the relational backbone necessary to interpret the role of each operation line within the broader contract lifecycle managed by Oracle Contracts Core.