Results for “okc_operation_instances_v”

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

Overview

OKC_OPERATION_INSTANCES_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the OKC — Contracts Core product family. It exposes operation instance records that represent runtime executions of contractual operations, such as contract generation, versioning, approval, or termination activities performed by the Contracts Core engine. The view is validated and marked VALID in the ETRM metadata for both release 12.1.1 and 12.2.2, meaning the underlying definition resolves cleanly against the shipped schema.

Functionally, the view acts as a thin projection over the OKC_OPERATION_INSTANCES base table. It renames ROWID to ROW_ID and selects a fixed set of columns including identifiers, status codes, multi-object reference attributes (JTOT_OBJECT1_CODE, OBJECT1_ID1, OBJECT1_ID2), and standard WHO/audit columns. Because it preserves the base table's columns without joins or aggregation, it behaves as a stable, read-friendly interface suitable for reports, concurrent programs, and integration extracts that must not depend directly on the base table name.

Underlying Base Objects

The documented definition references a single object: OKC_OPERATION_INSTANCES, exposed in the APPS schema through a synonym. No joins, unions, or lookup resolutions are present in the view text, so row counts and data types mirror the base table exactly. Consequently, the view inherits the base table's primary key, foreign key relationships, and any column-level constraints. Because the synonym is the documented reference, DBAs should treat OKC_OPERATION_INSTANCES as the authoritative physical object and OKC_OPERATION_INSTANCES_V solely as a projection layer.

Key Columns

• ROW_ID — the base table ROWID, useful for direct row addressing and for building correlated updates.
• ID — primary identifier of the operation instance.
• NAME — user- or system-assigned name of the instance.
• COP_ID — identifier of the contract operation (COP) definition that the instance executes.
• STATUS_CODE — lifecycle state of the instance, for example pending, running, completed, or failed.
• TARGET_CHR_ID — the contract header the operation acts upon.
• OBJECT_VERSION_NUMBER — optimistic locking token used by the framework during concurrent updates.
• JTOT_OBJECT1_CODE, OBJECT1_ID1, OBJECT1_ID2 — a generic multi-object reference triple; JTOT_OBJECT1_CODE identifies the entity type while OBJECT1_ID1 and OBJECT1_ID2 carry its key components. For line-level entities, OBJECT1_ID1 typically holds the header ID and OBJECT1_ID2 the line ID.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit attributes.
• REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE — concurrent program context indicating which request or program last touched the row.

Common Use Cases and Queries

The view is typically queried to diagnose operation failures, reconcile contract processing history, or extract instance activity for downstream systems. A common pattern filters by target contract header and ordered recency:

• Failed operations by contract: select ID, NAME, STATUS_CODE, LAST_UPDATE_DATE from OKC_OPERATION_INSTANCES_V where TARGET_CHR_ID = :p_chr_id and STATUS_CODE = 'FAILED' order by LAST_UPDATE_DATE desc.
• Instance lookup by object reference: filter on JTOT_OBJECT1_CODE, OBJECT1_ID1, and OBJECT1_ID2 to retrieve the operation instances tied to a specific header/line pair — the scenario most relevant to the "object1_id2" search term.
• Concurrent program traceability: group by PROGRAM_ID, PROGRAM_APPLICATION_ID and REQUEST_ID to reconcile instances produced by a specific batch run.
• Audit extraction: select the WHO columns to satisfy change-tracking or SOX reporting requirements.

Because the view exposes no derived logic, queries against it are index-friendly and behave identically to queries on OKC_OPERATION_INSTANCES. Join it to OKC_OPERATIONS_V or contract header views on COP_ID and TARGET_CHR_ID when fuller context is required.