Search Results okc_process_defns_b

Overview

The OKC.OKC_CLASS_OPERATIONS table is a seeded reference table within the Oracle Contracts (OKC) module of Oracle E-Business Suite, present in both 12.1.1 and 12.2.2. It defines which operations are legally and functionally permissible for each contract class. The table stores development-seeded data that drives the creation of operation instances; operation instances are only instantiated if a matching class-operation combination exists here. For example, the RENEWAL operation is permitted for the CORPORATE class, while RENCON (Renewal Consolidation) is permitted for the SERVICE class. Each row therefore represents an authorized pairing of a business operation with a contract class, optionally linked to the forms and process definitions used to service that operation.

From a Data Vault modeling perspective, the mined foreign-key structure suggests a satellite-leaning classification. The table carries descriptive attributes (forms, process identifiers, grid data sources) that elaborate on a business relationship between contract classes and operations, making it a natural candidate for a satellite attached to a class-operation link.

Key Information Stored

The table contains 16 documented columns. The most significant are:

• ID — Surrogate primary key (constraint OKC_COP_PK), used for unique identification of each row.
• OPN_CODE — Operation code associated with the class; foreign key to FND_LOOKUP_VALUES and OKC_OPERATIONS_B.
• CLS_CODE — Contract class for which the operation is defined; foreign key to OKC_CLASSES_B.
• SEARCH_FUNCTION_ID — Foreign key to FND_FORM_FUNCTIONS identifying the form used for search.
• DETAIL_FUNCTION_ID — Foreign key to FND_FORM_FUNCTIONS identifying the form used for detailed requests.
• PDF_ID — Process associated with the class and operation; foreign key to OKC_PROCESS_DEFS_B.
• QA_PDF_ID — Additional process definition identifier referencing OKC_PROCESS_DEFNS_B.
• GRID_DATASOURCE_NAME — Name of the grid displayed on the Contracts tab of the E-Business Center form.
• OBJECT_VERSION_NUMBER — Optimistic locking column, set to 1 on insert and incremented on update by APIs.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard Who columns for audit tracking.
• SECURITY_GROUP_ID — Used in hosted/multi-tenant environments; foreign key to FND_SECURITY_GROUPS.
• ZD_EDITION_NAME — Editioning column supporting Online Patching in 12.2.x.

Two unique indexes are documented as business-key candidates: OKC_CLASS_OPERATIONS_U1 on (ID, ZD_EDITION_NAME) and OKC_CLASS_OPERATIONS_U2 on (OPN_CODE, CLS_CODE, ZD_EDITION_NAME). U2 enforces that an operation may be defined only once per class, making the (OPN_CODE, CLS_CODE) pair the true business key.

Common Use Cases and Queries

Typical usage centers on determining which operations are available to a given contract class and resolving the associated forms and processes for the Contracts user interface.

• Listing all operations enabled for a specific class:

  SELECT opn_code, cls_code, search_function_id, detail_function_id
  FROM   okc.okc_class_operations
  WHERE  cls_code = 'CORPORATE';

• Joining to OKC_CLASSES_B and OKC_OPERATIONS_B to produce a human-readable class-operation matrix for functional configuration reviews.
• Resolving GRID_DATASOURCE_NAME and PDF_ID values to understand which grid and process definition drive the E-Business Center Contracts tab.
• Auditing seeded versus customer-extended rows by inspecting CREATED_BY to distinguish delivered operations from site-defined ones.
• Validating the business key via OKC_CLASS_OPERATIONS_U2 to detect duplicate operation-class pairings before applying patches or upgrades.

Related Objects

• OKC.OKC_CLASSES_B — Referenced via CLS_CODE; defines each contract class.
• OKC.OKC_OPERATIONS_B — Referenced via OPN_CODE; defines each operation.
• OKC.OKC_PROCESS_DEFS_B — Referenced via PDF_ID; supplies the process definition for the operation.
• OKC.OKC_OPERATION_INSTANCES — References this table through COP_ID; holds instantiated operations created from the seeded definitions.
• FND_SECURITY_GROUPS — Referenced via SECURITY_GROUP_ID in hosted deployments.
• FND_LOOKUP_VALUES — Source of the operation code lookup values.
• FND_FORM_FUNCTIONS — Referenced by SEARCH_FUNCTION_ID and DETAIL_FUNCTION_ID for form resolution.