Search Results jtf_brm_processes_pk

Overview

JTF_BRM_PROCESSES is a CRM Foundation (JTF) table in Oracle E-Business Suite 12.1.1 and 12.2.2 that links a workflow process to a business rule. It is the association point between the business rule engine (BRM) definitions stored in JTF_BRM_RULES_B and the Oracle Workflow process that is launched when that rule is satisfied. Each row represents one rule-to-workflow binding, carrying the workflow item type and process name together with the monitoring parameters (unit of measure, check interval, and tolerance) that govern how the rule is evaluated.

Under the heuristic Data Vault classification derived from its foreign key structure, the table is satellite-leaning. PROCESS_ID is a generated surrogate primary key rather than a natural business key, and the row carries descriptive and temporal attributes (tolerance values, active dates, audit columns) that change over time. A Data Vault model would therefore typically treat this as a satellite attached to a rule hub, with the rule link resolved through RULE_ID.

Key Information Stored

• PROCESS_ID — surrogate primary key, populated by JTF_BRM_PROCESSES_PK. Also appears with ZD_EDITION_NAME in the unique index JTF_BRM_PROCESSES_U1.
• RULE_ID — foreign key to JTF_BRM_RULES_B; identifies the business rule to which the workflow process is bound.
• WORKFLOW_ITEM_TYPE — the Oracle Workflow item type that owns the process definition.
• WORKFLOW_PROCESS_NAME — the workflow process invoked when the rule evaluates true.
• BRM_UOM_TYPE, BRM_CHECK_UOM_CODE, BRM_CHECK_INTERVAL — the unit-of-measure basis, the UOM of the check, and the frequency at which the rule is evaluated.
• BRM_TOLERANCE_UOM_CODE, BRM_TOLERANCE_INTERVAL — tolerance thresholds applied during rule evaluation.
• LAST_BRM_CHECK_DATE — timestamp of the most recent rule evaluation for this process.
• START_DATE_ACTIVE, END_DATE_ACTIVE — effective-dating window controlling when the binding is active.
• SEEDED_FLAG — indicates whether the row is Oracle-seeded or customer-defined.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, enforcing multi-org/security grouping.
• APPLICATION_ID — the owning application, typically CRM Foundation.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the OAF/BC4J framework.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the standard DFF (descriptive flexfield) columns for customer extensions.
• ZD_EDITION_NAME — editioning column supporting Online Patching (EBR) in 12.2.x.

Common Use Cases and Queries

The primary operational use is diagnosing why a business rule did or did not fire a workflow. Joining JTF_BRM_PROCESSES to JTF_BRM_RULES_B and to the workflow runtime tables reveals the configured item type and process name for each rule.

• List all workflow bindings for a given rule:
  SELECT p.process_id, p.workflow_item_type, p.workflow_process_name, p.start_date_active, p.end_date_active FROM jtf_brm_processes p WHERE p.rule_id = :rule_id;
• Retrieve the rule, process, and tolerance context for reporting on rule configuration: join to JTF_BRM_RULES_B on RULE_ID and filter on SEEDED_FLAG and the active date window.
• Drill from a process binding into its workflow attribute values using JTF_BRM_WF_ATTR_VALUES.PROCESS_ID, which is the child of this table.
• Audit recently evaluated rules using LAST_BRM_CHECK_DATE, and compare BRM_CHECK_INTERVAL to actual elapsed time to detect stalled schedulers.
• Security-scoped extracts filtering on SECURITY_GROUP_ID when building custom BI Publisher or OBIEE reports over CRM rule configuration.

Related Objects

• JTF_BRM_RULES_B — parent business rule table; joined on JTF_BRM_PROCESSES.RULE_ID.
• JTF_BRM_WF_ATTR_VALUES — child table holding workflow attribute values; joined on PROCESS_ID.
• FND_SECURITY_GROUPS — referenced through SECURITY_GROUP_ID for security grouping.
• FND_APPLICATION — resolves APPLICATION_ID to the owning application name.
• WF_ITEM_TYPES and WF_PROCESS_ACTIVITIES — Oracle Workflow dictionary tables used to validate WORKFLOW_ITEM_TYPE and WORKFLOW_PROCESS_NAME.
• WF_ITEM_ACTIVITY_STATUSES / WF_ITEMS — runtime workflow tables used to trace invocations originating from these bindings.
• The CRM Business Rule APIs and the Business Rule Monitor concurrent program, which read this table when scheduling and evaluating rules.