Search Results okc_user_hook_calls




Overview
Explore in AI Chat

Overview

The OKC_USER_HOOK_CALLS table is a core technical object within the Oracle E-Business Suite Contracts Core (OKC) module, specifically for versions 12.1.1 and 12.2.2. It functions as a configuration registry for user-defined PL/SQL routines, commonly known as hooks, within the contract management process. The table's primary role is to define the linkage between a specific contract process and the custom business logic that should be invoked at defined points during that process's execution. This enables significant extensibility, allowing organizations to inject custom validation, data transformation, or workflow logic into standard Oracle Contracts operations without modifying the base application code.

Key Information Stored

The table's structure is defined by its primary and foreign key relationships. The two critical columns are PDF_ID and PDF_USING_ID, which together form the primary key (OKC_USER_HOOK_CALLS_PK). The PDF_ID column stores a foreign key reference to a specific process definition in the OKC_PROCESS_DEFS_B table. This identifies the contract process or event that triggers the custom hook. The PDF_USING_ID column stores a foreign key reference to a parameter definition in the OKC_PROCESS_DEF_PARMS_B table. This identifies the specific PL/SQL routine (the hook) to be called, along with its associated execution parameters. The table essentially stores a many-to-many relationship, mapping which custom routines are called for which processes.

Common Use Cases and Queries

The primary use case is auditing and managing custom extensions within the Contracts module. Administrators and developers query this table to understand what custom logic is attached to critical business processes, such as contract approval, amendment, or termination. A common diagnostic query involves joining to related definition tables to get a readable list of hooks. For example:

  • Identifying Hooks for a Process: A query joining OKC_USER_HOOK_CALLS (UHC) to OKC_PROCESS_DEFS_B (PDF) and OKC_PROCESS_DEF_PARMS_B (PDP) can resolve the internal IDs to meaningful names, showing which PL/SQL package.procedure is invoked for a given process definition name.
  • Impact Analysis: Before modifying or decommissioning a custom PL/SQL package, this table is queried to identify all contract processes that depend on it, using the PDF_USING_ID foreign key relationship.
  • Troubleshooting: When a contract process behaves unexpectedly, checking this table is a standard step to verify if custom hook logic is being invoked and could be the source of the issue.

Related Objects

The OKC_USER_HOOK_CALLS table is centrally connected to two other key definition tables in the Contracts Core schema, as documented by its foreign key constraints.

  • OKC_PROCESS_DEFS_B: This table is referenced via the column OKC_USER_HOOK_CALLS.PDF_ID. It contains the master definitions of executable processes within the Contracts module.
  • OKC_PROCESS_DEF_PARMS_B: This table is referenced via the column OKC_USER_HOOK_CALLS.PDF_USING_ID. It stores the definitions of parameters and, critically, the PL/SQL call specifications for user-defined hooks that can be associated with those processes.

These relationships form the backbone of the extensibility framework, where OKC_USER_HOOK_CALLS acts as the junction table linking a process (from OKC_PROCESS_DEFS_B) to its configured custom logic (defined in OKC_PROCESS_DEF_PARMS_B).