Search Results okc_process_defs_b_pk

Overview

OKC_PROCESS_DEFS_B is a core configuration table in the Oracle Contracts (OKC) module of Oracle E-Business Suite, available in both 12.1.1 and 12.2.2. It stores definitions of executable PL/SQL processes, stored procedures, and Oracle Workflow processes that the Contracts application invokes during contract lifecycle processing. Specifically, entries in this table are referenced as OUTCOME actions, CONTRACT PROCESS steps, QA PROCESS checks, or FUNCTION calls embedded within a CONDITION LINE. In effect, OKC_PROCESS_DEFS_B acts as the central registry that maps a logical business action to its underlying technical implementation, whether that implementation is a PL/SQL package procedure or a Workflow process type.

From a data modeling perspective, the documented foreign-key structure classifies this object as hub-leaning in a heuristic Data Vault sense. The table holds a stable, uniquely identified set of process-definition business entities (the hub), while the numerous subordinate tables that point to it via PDF_ID behave as satellites and links capturing context, parameters, and usage. This classification is a modeling suggestion derived from the FK topology rather than a warehouse design mandate.

Key Information Stored

The table is populated through 38 documented columns. The most significant are:

• ID — Surrogate primary key, enforced by OKC_PROCESS_DEFS_B_PK. This is the value propagated as PDF_ID into all dependent tables.
• ZD_EDITION_NAME — Editioning column used in 12.2.2 for online patching and edition-based redefinition. Together with ID it forms the unique business-key candidate OKC_PROCESS_DEFS_B_U1.
• NAME — The user-facing name of the process definition.
• PDF_TYPE — Discriminator identifying whether the definition is an outcome, contract process, QA process, function, or similar category.
• USAGE — Indicates the functional context in which the definition may be applied.
• PACKAGE_NAME and PROCEDURE_NAME — Identify the PL/SQL implementation invoked when the definition executes.
• WF_NAME and WF_PROCESS_NAME — Identify the Oracle Workflow item type and process for workflow-based definitions.
• MESSAGE_NAME and SCRIPT_NAME — Support messaging and scripted execution contexts.
• BEGIN_DATE and END_DATE — Effective-dating columns governing when the definition is active.
• APPLICATION_ID — The owning application, typically Contracts.
• SEEDED_FLAG — Distinguishes Oracle-seeded definitions from customer-defined ones.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS supporting multi-org/security partitioning.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the OAF framework.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — Descriptive flexfield storage for extensibility.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO audit columns.

Common Use Cases and Queries

Typical uses include auditing which PL/SQL procedures are wired to contract outcomes, tracing a Workflow process used during contract approval, and validating that seeded definitions remain intact after patching. A representative query lists active definitions by type:

• Auditing outcomes: SELECT id, name, package_name, procedure_name FROM okc_process_defs_b WHERE pdf_type = 'OUTCOME' AND TRUNC(SYSDATE) BETWEEN begin_date AND NVL(end_date, SYSDATE+1);
• Resolving a PDF_ID to its implementation: join dependent tables such as OKC_K_PROCESSES or OKC_OUTCOMES_B on PDF_ID.
• Identifying customer extensions: filter on seeded_flag = 'N'.
• Locating Workflow-driven processes: filter where WF_NAME and WF_PROCESS_NAME are populated.
• Impact analysis before modifying a procedure: query all items referencing a given ID across the dependent tables.

Related Objects

OKC_PROCESS_DEFS_B sits at the center of a dense reference graph. The following tables reference it through the PDF_ID column, which maps to this table's primary key ID:

• OKC_K_PROCESSES.PDF_ID — Attaches process definitions to contract process flows.
• OKC_K_SEQ_HEADER.PDF_ID — Links definitions to sequence header constructs.
• OKC_OUTCOMES_B.PDF_ID — Associates outcomes with their executable definitions.
• OKC_CLASS_OPERATIONS.PDF_ID — Ties definitions to class-level operations.
• OKC_PROCESS_DEF_PARMS_B.PDF_ID — Stores parameters passed to each process definition.
• OKC_QA_LIST_PROCESSES.PDF_ID — Connects quality-assurance lists to their processes.
• OKC_USER_HOOK_CALLS.PDF_ID — Binds user hook calls to definitions.
• OKS_K_DEFAULTS.PDF_ID — References definitions within service/contract defaults.

The table itself carries an outward foreign key to FND_SECURITY_GROUPS through SECURITY_GROUP_ID. Together these relationships establish OKC_PROCESS_DEFS_B as the authoritative hub for executable contract processing logic.