Results for “okc_contract_processes”

5 results




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

Overview

The OKC_K_PROCESSES_V view is a Contracts Core (OKC) dictionary object owned by the APPS schema. It is documented in ETRM as a view defined over the contract processes table, providing a stable read interface to the underlying data that supports Oracle Contracts and its integrated modules. In Oracle EBS 12.1.1 and 12.2.2, the view is registered as VALID and exposes the contractual process records maintained against contract documents, including the IN_PROCESS_YN flag that indicates whether a given process is currently active or in flight. Because it presents a denormalized, read-only projection of the base table, the view is typically consumed by reports, concurrent programs, forms, and outbound integrations rather than being used for direct DML. Its descriptive "K" prefix places it within the OKC contracts kernel objects, and its use of the standard WHO columns makes it consistent with the audit and multi-org conventions applied throughout the E-Business Suite.

Underlying Base Objects

The view is defined over OKC_K_PROCESSES, which is referenced in the documented metadata as a SYNONYM resolving to the underlying base table. The ETRM description confirms this relationship, describing OKC_K_PROCESSES_V simply as "View for table OKC_CONTRACT_PROCESSES." The view text selects every significant column from the base object without joins, filters, or aggregations, so it is effectively a one-to-one projection of OKC_K_PROCESSES. Each row in the view corresponds to one row in the base table. This design keeps the read path fast and predictable while insulating dependent code from any future changes to the base table's physical structure. Standard Oracle EBS audit columns, the OBJECT_VERSION_NUMBER for optimistic locking, and the fifteen descriptive ATTRIBUTE columns from the DFF framework are all carried through unchanged.

Key Columns

  • ROW_ID — the base table ROWID, usable for direct row identification and update-through-view strategies.
  • ID — the primary key of the contract process record.
  • OBJECT_VERSION_NUMBER — supports optimistic locking during concurrent updates.
  • PDF_ID, CHR_ID, CRT_ID — foreign key references to the associated contractual document, header, and contract respectively, linking the process to its owning agreement.
  • USER_ID — the user associated with the process.
  • PROCESS_ID — identifies the process definition or instance being tracked.
  • IN_PROCESS_YN — the search term of interest; a Y/N flag indicating whether the process is currently running or pending. This is the primary filter used to isolate in-flight processes.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — descriptive flexfield segments retained for extensibility.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard WHO audit columns.

Common Use Cases and Queries

Typical usage centers on identifying processes that are still active for a given contract and on auditing process history. The following query locates all in-process records for a contract:

SELECT id, chr_id, crt_id, process_id, user_id, creation_date
FROM apps.okc_k_processes_v
WHERE in_process_yn = 'Y'
AND crt_id = :contract_id;

Integration and monitoring routines frequently invert the predicate to find completed processes, while reporting extracts join the view to OKC_K_HEADERS for contract context. Because the view is a straight projection, it is also safe to query inside concurrent programs without performance penalty, and the presence of ROWID permits controlled updates where Oracle EBS historically supported them.