Search Results okc_process_def_parms_b




Overview
Explore in AI Chat

Overview

The OKC_PROCESS_DEF_PARMS_B table is a core repository within the Oracle E-Business Suite Contracts Core (OKC) module, specifically for Oracle EBS 12.1.1 and 12.2.2. It serves as the master definition table for parameters associated with process definitions. In the context of the Contracts application, process definitions are used to model and execute complex business workflows and validations. This table's primary role is to define the signature of these processes by storing the metadata for each input or output parameter, including its name, data type, and constraints. It is a foundational object that enables the dynamic and configurable execution of contract-related business logic.

Key Information Stored

The table stores the metadata that defines a parameter for a process definition. While the full column list is not detailed in the provided excerpt, the description specifies the core attributes recorded. The primary key is the ID column, which uniquely identifies each parameter record. A critical foreign key is the PDF_ID column, which links the parameter to its parent process definition in the OKC_PROCESS_DEFS_B table. Based on the documented description, other essential columns would store the parameter's name, its datatype (e.g., VARCHAR2, NUMBER, DATE), a flag indicating whether it is optional or mandatory, and a potential default value. This structure allows the system to understand what data a process expects or returns at runtime.

Common Use Cases and Queries

A primary use case is the analysis and troubleshooting of contract business processes. Developers and functional consultants query this table to understand the expected inputs for a specific process or to audit parameter definitions. Common SQL patterns include listing all parameters for a given process definition or identifying processes that use a specific datatype. For example, to find all parameters for a process definition known by its ID, one would use a query such as: SELECT * FROM okc_process_def_parms_b WHERE pdf_id = <process_definition_id> ORDER BY id;. Reporting use cases often involve joining with OKC_PROCESS_DEFS_B to produce a comprehensive list of processes and their full parameter signatures for documentation or impact analysis during upgrades or customizations.

Related Objects

The OKC_PROCESS_DEF_PARMS_B table is centrally connected to several other key tables in the Contracts Core schema, as documented by its foreign key relationships.

  • Parent Reference: The table references OKC_PROCESS_DEFS_B via the PDF_ID foreign key, linking each parameter to its master process definition.
  • Child References (Tables that depend on OKC_PROCESS_DEF_PARMS_B):

These relationships illustrate that the parameter definitions stored in this table are consumed by various components of the Contracts process engine to execute business logic, evaluate outcomes, and support extensibility.