Search Results okc_class_operations




Overview
Explore in AI Chat

Overview

OKC_CLASS_OPERATIONS is a Contracts Core (OKC) configuration table in Oracle E-Business Suite 12.1.1 and 12.2.2. It holds seeded data that defines the allowable operations available to each contract or document class. In effect, it is the authorization and capability matrix that tells the Contracts framework which actions (operations) are permitted for a given class, and which process definition governs those actions.

The table is owned by the OKC schema and carries VALID status. It operates as a cross-reference between three foundational property definitions: contract classes (OKC_CLASSES_B), operations (OKC_OPERATIONS_B), and process definitions (OKC_PROCESS_DEFS_B). Because the rows are seeded rather than freely user-entered, the table is treated as reference/configuration data. Row instances of these allowed operations are then consumed by OKC_OPERATION_INSTANCES, which records the actual execution of an operation against a specific contract.

The ETRM metadata applies a heuristic Data Vault classification of satellite-leaning. As a modeling suggestion, this reflects the presence of descriptive attributes and audit columns attached to a natural business key, with the table referencing parent hub entities rather than acting as a pure junction link. The classification should be treated as advisory, not as a physical constraint of the delivered schema.

Key Information Stored

The table includes 16 documented columns. The most significant are summarized below.

  • ID — Surrogate primary key, enforced by constraint OKC_COP_PK. It uniquely identifies each class-operation row and is referenced by OKC_OPERATION_INSTANCES.COP_ID.
  • CLS_CODE — Business-key column identifying the contract/document class to which the allowed operation applies. Foreign key to OKC_CLASSES_B.
  • OPN_CODE — Business-key column identifying the operation permitted for the class. Foreign key to OKC_OPERATIONS_B.
  • PDF_ID — Foreign key to OKC_PROCESS_DEFS_B, linking the operation to its governing process definition.
  • QA_PDF_ID — Secondary process definition reference, typically associated with a QA or alternate workflow path.
  • SEARCH_FUNCTION_ID and DETAIL_FUNCTION_ID — Identify the search and detail functions (forms or OA Framework pages) invoked when the operation is executed for the class.
  • GRID_DATASOURCE_NAME — Names the data source backing the grid display associated with the class-operation.
  • OBJECT_VERSION_NUMBER — Optimistic locking column used by the framework to control concurrent updates.
  • SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, supporting multi-org or data-security partitioning.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS audit columns.
  • ZD_EDITION_NAME — Editioning column; it participates in both unique indexes and is central to Online Patching (ADOP) in 12.2.2.

Two unique indexes define candidate business keys: OKC_CLASS_OPERATIONS_U1 (ID, ZD_EDITION_NAME) and OKC_CLASS_OPERATIONS_U2 (OPN_CODE, CLS_CODE, ZD_EDITION_NAME). The second index establishes the combination of operation and class as the meaningful natural identifier.

Common Use Cases and Queries

Typical usage centers on inspecting, validating, or reporting the operations enabled for a class. The most common query joins the table to its three parents to present a readable definition:

  • Listing allowed operations per class: SELECT c.cls_code, c.opn_code, p.pdf_id FROM okc_class_operations c, okc_process_defs_b p WHERE c.pdf_id = p.pdf_id;
  • Checking which classes permit a specific operation by filtering on OPN_CODE, useful when troubleshooting why an action is unavailable.
  • Resolving the search/detail functions executed for a class-operation, using SEARCH_FUNCTION_ID and DETAIL_FUNCTION_ID.
  • Tracing executed actions by joining to OKC_OPERATION_INSTANCES on COP_ID = ID, which maps configuration to actual contract activity.
  • Validating seeded setup during implementation comparisons or regression testing, particularly distinguishing rows by ZD_EDITION_NAME in 12.2.2.

Related Objects

  • OKC_CLASSES_B — Parent class definition; joined via CLS_CODE.
  • OKC_OPERATIONS_B — Parent operation definition; joined via OPN_CODE.
  • OKC_PROCESS_DEFS_B — Governs the operation workflow; joined via PDF_ID (and referenced by QA_PDF_ID).
  • OKC_OPERATION_INSTANCES — Child table recording executed operations; joined via COP_ID → ID.
  • FND_SECURITY_GROUPS — Referenced via SECURITY_GROUP_ID for data security.

These relationships make OKC_CLASS_OPERATIONS the bridge between Contracts configuration and runtime operation records.