Results for “workflow_process_id”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

JTF_BRM_PARAMETERS_V is a reporting and forms-support view owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It belongs to the JTF product family, commonly identified as CRM Foundation, and exists to serve the Business Rule Monitor (BRM) form. The Business Rule Monitor is the CRM Foundation component that governs automated monitoring behaviour within the CRM application stack, allowing administrators to define parameters that determine how business events are evaluated, how frequently they are polled, and which workflow processes are invoked when a rule condition is satisfied.

The view does not introduce new persistent data. Instead, it projects rows from the JTF_BRM_PARAMETERS base table and enriches each row with decoded, human-readable meanings derived from Oracle Application Object Library lookups. Its purpose is therefore presentational: it supplies the BRM form, and any dependent reporting or integration layer, with a denormalised, display-ready result set. Because the view resolves lookup meanings through external joins rather than storing codes alone, it allows the form to render descriptive text for unit-of-measure and workflow command attributes without requiring the calling module to issue separate lookup queries. The user search term "workflow_process_id" corresponds directly to a column carried by this view from the underlying parameters table, reflecting its role in associating a monitor rule with a specific workflow definition.

Underlying Base Objects

The view text defines a three-way join. The driving object is JTF_BRM_PARAMETERS, referenced in the documentation metadata as a synonym and exposed in the SELECT through the alias JBP. This table holds one row per business rule monitor parameter, including its unit-of-measure configuration, interval, workflow command details, and workflow assignment columns. All primary keys, audit columns, and workflow identifiers originate here.

The second and third sources are inline query blocks over FND_LOOKUPS, an APPS view over the FND_LOOKUPS base lookup table. The first inline block, aliased FL1, filters for LOOKUP_TYPE = 'JTF_BRM_UOM_TYPE', while the second, aliased FL2, filters for LOOKUP_TYPE = 'JTF_BRM_WF_COMMAND_TYPE'. Both apply enabled-flag and effective-date filters so that only currently active lookups are considered. These blocks are joined to the base table with outer joins (+) on the code columns, meaning a parameter row survives even when no matching lookup exists; in that case the corresponding meaning column returns null. The documented metadata also lists FND_GLOBAL as a referenced package, consistent with standard APPS views that rely on session context for organisational and user resolution.

Key Columns

The view exposes PARAMETER_ID, the primary identifier for each monitor parameter, and ROW_ID, the physical row identifier of the underlying base-table row. Standard audit columns CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN are carried through for traceability.

Unit-of-measure configuration is represented by BRM_UOM_TYPE and BRM_UOM_CODE, with BRM_UOM_MEANING supplying the decoded lookup meaning from FL1. BRM_INTERVAL captures the polling or evaluation interval for the monitor.

Workflow command information is held in BRM_WF_COMMAND_TYPE and BRM_WF_COMMAND_CODE, decoded into BRM_WF_COMMAND_MEANING via FL2. The columns most relevant to the user's search are WORKFLOW_PROCESS_ID, WORKFLOW_ITEM_TYPE, and WORKFLOW_PROCESS_NAME. Together these establish the association between a monitor parameter and the Oracle Workflow process it drives: WORKFLOW_ITEM_TYPE identifies the workflow item type, WORKFLOW_PROCESS_ID identifies the specific process definition, and WORKFLOW_PROCESS_NAME provides the readable process name.

Common Use Cases and Queries

Typical uses include diagnosing which workflow process is bound to a given monitor parameter, auditing active workflow command configurations, and generating administrative reports of BRM setup across environments.

To retrieve parameters linked to a specific workflow process:

• SELECT parameter_id, workflow_item_type, workflow_process_id, workflow_process_name, brm_interval FROM jtf_brm_parameters_v WHERE workflow_process_id = :p_process_id;

To list all parameters with their decoded unit-of-measure and command meanings:

• SELECT parameter_id, brm_uom_code, brm_uom_meaning, brm_wf_command_code, brm_wf_command_meaning, workflow_process_name FROM jtf_brm_parameters_v ORDER BY parameter_id;

To identify parameters whose workflow command lookup has no active meaning, indicating an unmapped or disabled lookup:

• SELECT parameter_id, brm_wf_command_type, brm_wf_command_code FROM jtf_brm_parameters_v WHERE brm_wf_command_meaning IS NULL;

Because the view is not indexed independently, queries should filter on columns that map directly to the base table, such as PARAMETER_ID or WORKFLOW_PROCESS_ID, to allow the optimizer to push predicates into JTF_BRM_PARAMETERS. When the view is used for high-volume extraction, joining directly to JTF_BRM_PARAMETERS and resolving lookups separately may yield better performance.