Search Results okc_process_defs_v




Overview
Explore in AI Chat

Overview

OKC_PROCESS_DEFS_V is a PL/SQL view owned by the APPS schema within the OKC - Contracts Core product of Oracle E-Business Suite. It exposes process definition metadata used by the Contracts Core module to drive workflow-enabled processing, contract document generation, and integration routines. The view is registered as VALID in both EBS 12.1.1 and 12.2.2 and is classified as a reporting and integration artifact rather than a transactional entity, so it is typically consumed by concurrent programs, forms, and custom SQL reports rather than by end-user data entry screens.

The view presents a denormalized, language-filtered read of process definition records. Its principal role is to make seeded and customer-defined process definitions queryable through the standard APPS synonym layer, allowing reports and interfaces to join process configuration data against workflow and contract processing logic without touching the underlying base tables directly. The presence of the WF_PROCESS_NAME column — the object the user searched for — reflects the view's central purpose: correlating a contract process definition with its Oracle Workflow process name.

Underlying Base Objects

The view is defined over two base objects, both referenced through APPS synonyms:

  • OKC_PROCESS_DEFS_B — the base table holding the non-translatable attributes of each process definition, including the workflow metadata, procedure and package names, application context, seed flag, and the descriptive flexfield attribute columns.
  • OKC_PROCESS_DEFS_TL — the translation table holding language-specific descriptive fields such as NAME, DESCRIPTION, SHORT_DESCRIPTION, and COMMENTS, along with the SFWT_FLAG.

The join is performed on ID equals ID, restricted by PDFT.LANGUAGE = USERENV('LANG'), which returns the display language of the current session. This design is consistent with the standard EBS _B/_TL translatable entity pattern and supports multilingual deployments without requiring the caller to manage language filtering explicitly.

Key Columns

  • ROW_ID — the ROWID of the base record, useful for row-level addressing.
  • ID — the primary identifier of the process definition.
  • NAME, DESCRIPTION, SHORT_DESCRIPTION, COMMENTS — translated, user-facing text.
  • WF_NAME and WF_PROCESS_NAME — the Oracle Workflow item type and process name associated with the definition; WF_PROCESS_NAME is the column most frequently queried to trace a contract process to its workflow definition.
  • PROCEDURE_NAME and PACKAGE_NAME — the PL/SQL routine invoked when the process executes.
  • PDF_TYPE, USAGE, APPLICATION_ID, and SEEDED_FLAG — classification and ownership attributes distinguishing seeded Oracle definitions from customer-defined ones.
  • BEGIN_DATE and END_DATE — date-range validity for the definition.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the descriptive flexfield segment columns.
  • OBJECT_VERSION_NUMBER and the standard audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) — concurrency control and audit trail.
  • MESSAGE_NAME and SCRIPT_NAME — supporting metadata for messaging and scripting behavior.

Common Use Cases and Queries

Typical scenarios include locating the workflow process associated with a contract process definition, auditing which definitions are seeded versus custom, and joining process configuration to contract or workflow reporting.

To find definitions by workflow process name:

SELECT id, name, wf_name, wf_process_name,
       package_name, procedure_name, seeded_flag
FROM   apps.okc_process_defs_v
WHERE  wf_process_name = :p_process_name;

To list all custom (non-seeded) definitions active as of the current date:

SELECT id, name, usage, pdf_type, begin_date, end_date
FROM   apps.okc_process_defs_v
WHERE  seeded_flag = 'N'
AND    TRUNC(SYSDATE) BETWEEN begin_date AND NVL(end_date, SYSDATE);

To join definitions to concurrent program usage or contract templates, the view is commonly keyed on ID or APPLICATION_ID. Because the view filters on the session language, callers should ensure the reporting session language is set appropriately when comparing translated NAME or DESCRIPTION values across environments.