Search Results okc_class_operations_v




Overview
Explore in AI Chat

Overview

OKC_CLASS_OPERATIONS_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the OKC — Contracts Core product family, which underpins the Oracle Contracts and Enterprise Contracts modules. The view surfaces the configuration of class-level operations: the mapping between an operation code, a contract class code, and the specific PL/SQL functions and datasources that the Contracts user interface invokes when a user opens, searches, or displays a contract of a given class.

In the Contracts architecture, operations such as create, search, and detail display are not hard-coded per form. Instead, they are resolved at runtime through class operation records. OKC_CLASS_OPERATIONS_V provides a stable, read-only projection of those records, making it the appropriate object for extensions, custom reports, OAF page personalizations, and integration extracts that need to determine which function a given class-operation combination resolves to. Because the view is a thin wrapper over the base table, it inherits the standard EBS WHO columns, enabling auditing and concurrent-program-safe querying.

Underlying Base Objects

The view is defined over a single documented base object, OKC_CLASS_OPERATIONS, referenced through a synonym. The view text selects from that table using the alias COV and exposes the ROWID of the base row as ROW_ID alongside the primary key ID, allowing downstream code to join back to the base table without ambiguity. No joins are performed inside the view, so it is effectively a column-renamed and column-ordered projection rather than a denormalized construct. This design keeps the view inexpensive to query and ensures that any row visible in the view corresponds one-to-one with a row in OKC_CLASS_OPERATIONS.

Key Columns

The column of principal interest to integrators is DETAIL_FUNCTION_ID, which identifies the PL/SQL function used to render the detail (transaction) page for a given operation and class. This is the column most frequently targeted by the search term "detail_function_id", because it is the authoritative pointer from a Contracts class operation to the executable detail logic.

Common Use Cases and Queries

Typical usages include diagnosing why a contract class opens a particular detail page, building configuration reports that compare search and detail function assignments across classes, and extracting operation metadata for migration or integration. The following query returns all configured operations for a class, ordered by operation code and class:

  • SELECT opn_code, cls_code, search_function_id, detail_function_id FROM apps.okc_class_operations_v ORDER BY cls_code, opn_code;
  • SELECT id, detail_function_id, grid_datasource_name FROM apps.okc_class_operations_v WHERE cls_code = :p_class_code;
  • SELECT COV.detail_function_id FROM apps.okc_class_operations_v COV WHERE COV.opn_code = :p_opn_code AND COV.cls_code = :p_cls_code;

Because the view exposes OBJECT_VERSION_NUMBER and the full audit set, it is equally suitable for delta extracts that reconcile class operation configuration between environments. Queries should be schema-qualified with APPS and, where large result sets are anticipated, filtered on CLS_CODE or OPN_CODE to take advantage of the base table's indexing.