Search Results okc_process_defs_b

Overview

The OKC_PROCESS_DEFS_B table is a core repository within the Oracle E-Business Suite Contracts Core (OKC) module. It serves as the master definition table for executable processes used throughout the contract management lifecycle. These processes, which can be PL/SQL procedures or Oracle Workflows, are defined once and then referenced as configurable components in various contract business rules. Specifically, they are utilized as the executable logic for Outcomes, Contract Processes, Quality Assurance (QA) Processes, or Functions within Condition Lines. This centralization ensures process consistency and reusability across the complex contracting functionality in both EBS 12.1.1 and 12.2.2.

Key Information Stored

While the provided metadata does not list specific columns, the primary key is documented as the ID column, which uniquely identifies each process definition. Based on its described role and common patterns in OKC, the table likely stores attributes such as the process name, a description, the type of process (e.g., PL/SQL or Workflow), the actual program unit or workflow name to be invoked, and active status flags. The ID (PDF_ID) is the critical foreign key referenced by numerous other entities in the schema to link business rules to their executable logic.

Common Use Cases and Queries

This table is central to configuring and troubleshooting automated contract actions. A common administrative query involves listing all defined processes to understand available automation for contract authoring, approval, or renewal workflows. For example: SELECT id, name, process_type FROM okc_process_defs_b WHERE enabled_flag = 'Y';. Support and development personnel frequently query this table to diagnose issues by identifying which process definition is linked to a specific contract line outcome or QA checklist, using joins to related tables like OKC_OUTCOMES_B or OKC_QA_LIST_PROCESSES on the PDF_ID column.

Related Objects

The OKC_PROCESS_DEFS_B table is a foundational parent table with extensive relationships. As per the metadata, its primary key (ID) is referenced as the PDF_ID foreign key in several key tables:

• OKC_K_PROCESSES & OKC_K_SEQ_HEADER: Links processes to contract documents and their sequencing.
• OKC_OUTCOMES_B: Associates executable outcomes with their process definition.
• OKC_CLASS_OPERATIONS & OKS_K_DEFAULTS: Ties processes to contract class rules and service contract defaults.
• OKC_PROCESS_DEF_PARMS_B: Stores parameters required for the execution of a defined process.
• OKC_QA_LIST_PROCESSES & OKC_USER_HOOK_CALLS: Connects processes to quality assurance checklists and custom user hooks.

This network of foreign keys underscores the table's critical role as the central hub for executable contract logic.