Search Results jtf_brm_processes_u1

Overview

JTF.JTF_BRM_PROCESSES is a seed-data configuration table in the Oracle E-Business Suite JTF (or CRM Foundation) schema that defines which workflow process the Business Rule Monitor (BRM) should launch when an object instance satisfies a defined business rule. Each row binds a business rule to a specific workflow process, together with the scheduling, unit-of-measure, and tolerance attributes that govern how frequently the rule is evaluated and what threshold constitutes a violation. The table is stored in the APPS_TS_SEED tablespace, consistent with its role as a reference and setup repository.

Under a heuristic Data Vault classification, JTF_BRM_PROCESSES is satellite-leaning. It carries descriptive, versioned attributes (scheduling intervals, workflow identifiers, effective dates, and audit columns) attached to a parent business rule rather than acting as an independent hub of business keys or a pure associative link. This classification is a modeling suggestion derived from the foreign-key structure and should be validated against the intended integration pattern.

Key Information Stored

The physical table contains 38 documented columns. The most consequential are:

• PROCESS_ID — Surrogate primary key and unique identifier for the process. It anchors the unique index JTF_BRM_PROCESSES_U1 (documented in 12.2.2 as PROCESS_ID, ZD_EDITION_NAME).
• RULE_ID — Foreign key to the business rule in JTF_BRM_RULES_B; the business-key binding between a rule and its monitoring process.
• WORKFLOW_ITEM_TYPE and WORKFLOW_PROCESS_NAME — Identify the workflow item type and process to invoke; values are validated through lookups to JTF_LOOKUPS_BRM_WF_V.
• BRM_UOM_TYPE — Lookup type identifier governing the check interval's unit of measure.
• BRM_CHECK_UOM_CODE and BRM_CHECK_INTERVAL — The unit of measure and numeric interval controlling how often the rule is evaluated.
• BRM_TOLERANCE_UOM_CODE and BRM_TOLERANCE_INTERVAL — The tolerance window and its unit of measure.
• LAST_BRM_CHECK_DATE — Timestamp of the most recent rule evaluation.
• SEEDED_FLAG — Indicates whether the row is Oracle-seeded or customer-defined.
• START_DATE_ACTIVE and END_DATE_ACTIVE — Effective dating for the process definition.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS for multi-tenant data partitioning.
• APPLICATION_ID, OBJECT_VERSION_NUMBER, and ZD_EDITION_NAME — Application ownership, optimistic locking, and editioning support.
• Standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) provide audit lineage.

Common Use Cases and Queries

Typical scenarios include auditing which workflow processes are registered for a given rule, diagnosing why a rule failed to trigger a workflow, and reporting on monitoring coverage. A representative query joins the rule table to resolve rule names:

• SELECT p.PROCESS_ID, p.RULE_ID, r.RULE_NAME, p.WORKFLOW_ITEM_TYPE, p.WORKFLOW_PROCESS_NAME FROM JTF.JTF_BRM_PROCESSES p JOIN JTF.JTF_BRM_RULES_B r ON r.RULE_ID = p.RULE_ID WHERE p.SEEDED_FLAG = 'N';
• Identifying stale monitoring: SELECT * FROM JTF.JTF_BRM_PROCESSES WHERE LAST_BRM_CHECK_DATE < SYSDATE - 1;
• Filtering by workflow type: SELECT * FROM JTF.JTF_BRM_PROCESSES WHERE WORKFLOW_ITEM_TYPE = :item_type;
• Effective-dating checks using START_DATE_ACTIVE and END_DATE_ACTIVE to isolate currently active processes.

The nonunique indexes N1 (RULE_ID), N2 (BRM_UOM_TYPE), and N5 (WORKFLOW_ITEM_TYPE) support these access paths efficiently.

Related Objects

• JTF_BRM_RULES_B — Parent business rule; joined via RULE_ID.
• JTF_BRM_WF_ATTR_VALUES — Child attributes table referencing PROCESS_ID, supplying workflow attribute values per process.
• FND_SECURITY_GROUPS — Joined via SECURITY_GROUP_ID for security partitioning.
• JTF_LOOKUPS_BRM_WF_V — Lookup view validating WORKFLOW_ITEM_TYPE and WORKFLOW_PROCESS_NAME.
• FND_LOOKUPS — Validates BRM unit-of-measure code values.
• FND_USER and FND_LOGINS — Resolve WHO-column audit references.