Results for “okc_operation_lines_u1”

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

Overview

OKC.OKC_OPERATION_LINES is a transactional table within the Oracle E-Business Suite Contracts (OKC) schema that records the detail lines associated with an Operation Instance. Where OKC_OPERATION_INSTANCES captures the header-level definition of a processing action (such as renewal, consolidation, or mass change), OKC_OPERATION_LINES provides line-level granularity describing what did happen, or what will happen, for that operation. Each row always references a subject Contract Header, indicating the contract against which the operation is executed. In Renewal Consolidation scenarios, a second contract header (the target) is also populated via OBJECT_CHR_ID, allowing the table to model both source and destination contracts on a single line.

From a modeling perspective, the Data Vault classification mined from the foreign-key structure is satellite-leaning. This suggests the table functions primarily as a descriptive satellite attached to the Operation Instance hub, rather than as an independent hub or a pure link table. Its identity is anchored by the Operation Instance (OIE_ID) and enriched with contract, line, and processing attributes.

Key Information Stored

The table contains 22 documented columns. The most operationally significant are:

• ID — The surrogate primary key of the table, enforced by the unique index OKC_OPERATION_LINES_U1. This is the single documented business-key candidate and the definitive row identifier.
• OIE_ID — Foreign key to OKC_OPERATION_INSTANCES, tying the line to its parent operation instance.
• SUBJECT_CHR_ID — Identifier of the subject Contract Header (OKC_K_HEADERS_B); the contract on which the operation acts.
• OBJECT_CHR_ID — Identifier of the object Contract Header; for Renewal Consolidation this is the target contract.
• SUBJECT_CLE_ID and OBJECT_CLE_ID — Line-level identifiers referencing OKC_K_LINES_B for subject and object contract lines respectively.
• PARENT_OLE_ID — Self-referencing foreign key to OKC_OPERATION_LINES.ID, supporting hierarchical line structures.
• SELECT_YN — Indicates whether the line was requested for processing (Y/N).
• PROCESS_FLAG — Processing status indicator with valid values A, E, and P.
• ACTIVE_YN — Active/inactive status of the line.
• MESSAGE_CODE — Diagnostic or error code associated with the line's processing outcome.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, supporting Multi-Org/security partitioning.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE, which together support concurrent program traceability and optimistic locking.

Common Use Cases and Queries

A frequent requirement is to report all operation lines for a given operation instance, joining to the contract headers to resolve contract numbers:

• Operation detail: SELECT ol.ID, ol.SELECT_YN, ol.PROCESS_FLAG, kh.CONTRACT_NUMBER FROM OKC_OPERATION_LINES ol, OKC_K_HEADERS_B kh WHERE ol.SUBJECT_CHR_ID = kh.ID AND ol.OIE_ID = :p_oie_id;
• Pending processing: filter on PROCESS_FLAG = 'P' or SELECT_YN = 'Y' to identify lines awaiting or selected for processing.
• Renewal Consolidation analysis: rows where both SUBJECT_CHR_ID and OBJECT_CHR_ID are populated represent source-to-target contract relationships.
• Line hierarchy: a self-join on ol.PARENT_OLE_ID = parent.ID reconstructs parent-child operation structures.
• Concurrent program auditing: query by REQUEST_ID or PROGRAM_ID to trace batches of operations, using the OKC_OPERATION_LINES_N7 index on LAST_UPDATE_DATE for incremental extraction.

Related Objects

• OKC_OPERATION_INSTANCES — Parent hub via OIE_ID.
• OKC_K_HEADERS_B — Referenced twice, through SUBJECT_CHR_ID and OBJECT_CHR_ID.
• OKC_K_LINES_B — Referenced twice, through SUBJECT_CLE_ID and OBJECT_CLE_ID.
• OKC_OPERATION_LINES — Self-referencing through PARENT_OLE_ID.
• OKC_MASSCHANGE_REQ_DTLS — Child table whose OLE_ID references this table's ID.
• FND_SECURITY_GROUPS — Referenced through SECURITY_GROUP_ID for security partitioning.

The supporting non-unique indexes OKC_OPERATION_LINES_N1 through N6 cover SUBJECT_CHR_ID, OBJECT_CHR_ID, SUBJECT_CLE_ID, OBJECT_CLE_ID, OIE_ID, and PARENT_OLE_ID, confirming these as the principal access paths for joins and lookups.