Search Results okc_process_defs_b_u1

Overview

The OKC.OKC_PROCESS_DEFS_B table is the master definition repository within the Oracle Contracts (OKC) module of Oracle E-Business Suite. It stores the registration records for every PL/SQL procedure or Oracle Workflow process that the application may invoke as an OUTCOME, a CONTRACT PROCESS, a QUALITY ASSURANCE (QA) process, or a FUNCTION referenced inside a condition line. In effect, it is the central registry that tells the Contracts engine what executable logic to call, and under which usage category, when a business event fires.

Each row describes a distinct process definition, combining workflow metadata (workflow item type and process name) with PL/SQL metadata (package and procedure name) so that the runtime can dispatch to the correct technology based on the PDF_TYPE value of ALERT, SCRIPT, PPS, or WPS. The table is transactional data held in the APPS_TS_TX_DATA tablespace with a PCT Free of 10, and its indexes reside in APPS_TS_TX_IDX.

Using Data Vault modelling heuristics, this object leans toward a hub classification: it holds a stable, uniquely identified business entity (the process definition) referenced by numerous downstream tables through the PDF_ID foreign key. Modelers may treat OKC_PROCESS_DEFS_B as a hub with the associated descriptive columns (WF_NAME, USAGE, PDF_TYPE, and the ATTRIBUTE1–15 flex columns) carried as satellite attributes where historization is required.

Key Information Stored

The table comprises 38 documented columns. The most significant are summarized below.

• ID — System-generated unique identifier, populated from sequence OKC_PROCESS_DEFS_S1 and serving as the primary key (OKC_PROCESS_DEFS_B_PK). This is the surrogate key propagated to all dependent tables as PDF_ID.
• NAME — The user-facing name of the process definition.
• PDF_TYPE — The process definition type; valid values are ALERT, SCRIPT, PPS, and WPS. Together with USAGE this forms the non-unique index OKC_PROCESS_DEFS_B_N1.
• USAGE — The intended use of the definition; valid values include Approve, Auto Numbering, Approve Change Request, Function, Outcome, and Quality Assurance. It resolves against FND_LOOKUPS where LOOKUP_TYPE = 'OKC_PROCESS_USAGE_TYPES'.
• WF_NAME and WF_PROCESS_NAME — The workflow item type name and the workflow process name invoked when the definition is workflow-driven.
• PACKAGE_NAME and PROCEDURE_NAME — The PL/SQL package and procedure invoked when the definition is code-driven; the combination is validated against the data dictionary.
• OBJECT_VERSION_NUMBER — Concurrency control counter, set to 1 on insert and incremented on update, used by the APIs to detect stale records.
• BEGIN_DATE and END_DATE — Effective dating that controls when the definition is active.
• SEEDED_FLAG and APPLICATION_ID — Identify Oracle-seeded versus customer-defined records and the owning application.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS for row-level security.
• Standard Who columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN provide audit lineage.

The unique index OKC_PROCESS_DEFS_B_U1 covers (ID, ZD_EDITION_NAME), which combines the surrogate ID with the editioning column used in the 12.2 online patching architecture. This is the business-key candidate that enforces uniqueness across editions.

Common Use Cases and Queries

Typical usage centers on resolving which logic executes for a contracts event and on auditing the process registry. A frequent query lists all active outcomes for a given type:

• SELECT id, name, pdf_type, usage, wf_name, package_name, procedure_name FROM okc_process_defs_b WHERE usage = 'Outcome' AND SYSDATE BETWEEN begin_date AND NVL(end_date, SYSDATE+1);
• Joining to dependent tables to trace where a definition is used, e.g. linking ID to OKC_OUTCOMES_B.PDF_ID or OKC_CONDITION_LINES to see which condition lines invoke a given function.
• Reconciliation reports that list definitions by PDF_TYPE (ALERT vs SCRIPT vs WPS) to confirm that workflow and PL/SQL implementations are correctly categorized.
• Security and audit queries filtering on SECURITY_GROUP_ID or SEEDED_FLAG to separate Oracle-delivered definitions from custom ones.

Because the PK and the U1 index lead on ID, point lookups and joins on PDF_ID are highly selective and should always be driven through the ID column.

Related Objects

OKC_PROCESS_DEFS_B is referenced by eight documented child tables, and each shares the PDF_ID column as its foreign key to the parent ID.

• OKC_PROCESS_DEF_PARMS_B (PDF_ID → ID) — Parameter metadata consumed alongside the definition when invoking the process.
• OKC_OUTCOMES_B (PDF_ID → ID) — Outcomes registered against the process definition.
• OKC_K_PROCESSES (PDF_ID → ID) — Contract process invocations.
• OKC_QA_LIST_PROCESSES (PDF_ID → ID) — QA list processes attached to the definition.
• OKC_CONDITION_LINES — Consumes definitions used as FUNTION entries within condition lines.
• OKC_CLASS_OPERATIONS (PDF_ID → ID) — Class-level operations bound to the definition.
• OKC_K_SEQ_HEADER (PDF_ID → ID) — Auto-numbering sequence headers.
• OKC_USER_HOOK_CALLS (PDF_ID → ID) — User hook invocations.
• OKS_K_DEFAULTS (PDF_ID → ID) — Service contract defaults referencing the definition.
• FND_SECURITY_GROUPS — Parent of the SECURITY_GROUP_ID foreign key used for row-level access control.

Collectively these relationships establish OKC_PROCESS_DEFS_B as the hub through which all Contracts process execution flows.