Search Results okc_operation_lines_v




Overview
Explore in AI Chat

Overview

OKC_OPERATION_LINES_V is a reporting and integration view in the Oracle E-Business Suite Contracts Core (OKC) product, owned by the APPS schema. It exposes the contents of the OKC_OPERATION_LINES operation-line entity, which is used by the Contracts Core operation framework to represent the working set of records that a bulk operation (for example, a mass update, copy, or process action) will act upon. Each row corresponds to one line item within an operation instance, associating a subject contract or contract line with an object contract or contract line, and carrying processing state metadata.

The view is a thin projection over its single base synonym and is generally treated as the read interface for operation-line data. Because it surfaces the ACTIVE_YN column directly, it is a common target for queries and integrations that must distinguish currently active operation lines from historically retained or logically deleted ones, which is the typical intent behind searches on "active_yn."

Underlying Base Objects

The view is defined over a single documented base object: OKC_OPERATION_LINES, referenced through the synonym of the same name in the APPS schema. The view text selects from that synonym using the alias OPL and exposes ROWID as ROW_ID alongside the table's native primary key column, ID. No joins, unions, or aggregations are present in the definition, so the view adds no filtering, derivation, or transformation logic of its own. Row cardinality, data types, and nullability mirror the underlying operation-lines table exactly. Consequently, the view inherits the WHO columns and concurrent-program columns maintained by the base table's audit and request tracking, and any DML or data correction performed directly against OKC_OPERATION_LINES is immediately visible through this view.

Key Columns

  • ROW_ID – the ROWID of the underlying base row, useful for row-level addressing and updates.
  • ID – the operation-line primary key.
  • ACTIVE_YN – the active flag; indicates whether the operation line is currently active for processing. This is the column most often filtered on in the reported search context.
  • SELECT_YN – indicates whether the line has been selected by the user for inclusion in the operation.
  • PROCESS_FLAG – the processing state of the line as the operation executes.
  • OIE_ID – the operation instance identifier to which the line belongs.
  • SUBJECT_CHR_ID, SUBJECT_CLE_ID – the subject contract (header) and contract line identifiers acted upon by the operation.
  • OBJECT_CHR_ID, OBJECT_CLE_ID – the corresponding object contract and contract line identifiers produced by or associated with the operation.
  • PARENT_OLE_ID – self-referencing parent operation-line identifier, supporting hierarchical operation structures.
  • MESSAGE_CODE – stores the outcome or error message code returned for the line during processing.
  • OBJECT_VERSION_NUMBER – optimistic locking version used by the Contracts framework.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN – standard audit columns.
  • REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE – concurrent program tracking columns recording the request that last modified the row.

Common Use Cases and Queries

Typical uses include diagnosing why a contract operation did or did not process a given line, reconciling subject and object contract IDs for a mass action, and pulling active lines for downstream integration. A basic query returns only currently active operation lines for a given operation instance:

SELECT id, oie_id, subject_chr_id, subject_cle_id,
       object_chr_id, object_cle_id, process_flag, message_code
  FROM okc_operation_lines_v
 WHERE oie_id = :p_oie_id
   AND active_yn = 'Y'
 ORDER BY id;

A second pattern inspects failures and outcomes, filtering on the process flag and message code to isolate lines that did not complete successfully. A third pattern joins the view to contract header and line tables using SUBJECT_CHR_ID, SUBJECT_CLE_ID, OBJECT_CHR_ID, and OBJECT_CLE_ID to resolve descriptive details for reporting. Because the view performs no filtering, any query that requires only active rows must include the ACTIVE_YN predicate explicitly.