Results for “brm_wf_command_code”

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

Overview

JTF_BRM_PARAMETERS is a CRM Foundation (JTF) configuration table that stores the parameters governing the main workflow process of the Business Rule Monitor (BRM). The Business Rule Monitor is the background scheduling and evaluation engine used by Oracle CRM modules—most notably Oracle TeleSales, Oracle Territory Manager, and Oracle One-to-One Fulfillment—to periodically run business rules against transactional data and trigger corrective or notification workflows. Rather than hard-coding scheduling intervals, workflow command targets, and unit-of-measure definitions, the application externalizes them into this table so administrators can tune rule execution behavior without code changes. The table resides in the JTF schema and is marked VALID across Oracle E-Business Suite 12.1.1 and 12.2.2.

From a heuristic Data Vault modeling perspective, JTF_BRM_PARAMETERS is classified as a standalone object, suggesting it behaves as a reference or configuration hub rather than a transactional link or a historical satellite. It carries no child tables of its own and only one outbound foreign key, which supports treating it as a slowly changing reference entity whose rows define distinct parameter sets for the Business Rule Monitor engine.

Key Information Stored

The table contains 33 documented columns. The most operationally significant are:

• PARAMETER_ID — the surrogate primary key, enforced by the JTF_BRM_PARAMETERS_PK constraint and also by the unique index JTF_BRM_PARAMETERS_U1, making it both the technical and the documented business-key candidate.
• BRM_UOM_TYPE / BRM_UOM_CODE — the unit-of-measure type and code that define how the run interval is interpreted (for example, minutes, hours, or days).
• BRM_INTERVAL — the numeric interval value used together with the UOM to schedule Business Rule Monitor executions.
• BRM_WF_COMMAND_TYPE / BRM_WF_COMMAND_CODE — the Workflow command type and code that the monitor invokes when a rule condition is satisfied.
• WORKFLOW_PROCESS_ID, WORKFLOW_PROCESS_NAME, WORKFLOW_ITEM_TYPE — identifiers and descriptive metadata for the target workflow process the monitor launches.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, providing multi-tenant style data segregation across operating units or security contexts.
• APPLICATION_ID — associates the parameter row with the owning Oracle Application.
• OBJECT_VERSION_NUMBER — used for optimistic locking during concurrent updates.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns tracking row provenance.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the standard Oracle DFF (Descriptive Flexfield) column set, allowing customers to extend parameters without schema changes.

Common Use Cases and Queries

Administrators and developers consult this table when diagnosing why a Business Rule Monitor job runs at the wrong frequency, fires the wrong workflow, or fails to execute for a given security group. Typical reporting includes retrieving the active scheduling parameters for a specific application or security context and joining to FND_SECURITY_GROUPS to resolve the owning group name.

A representative query pattern:

• SELECT p.parameter_id, p.brm_uom_type, p.brm_uom_code, p.brm_interval, p.brm_wf_command_code, p.workflow_process_name FROM jtf.jtf_brm_parameters p WHERE p.application_id = :app_id AND p.security_group_id = :sg_id;
• Join to FND_SECURITY_GROUPS on SECURITY_GROUP_ID = SECURITY_GROUP_ID to label results by security group.
• Filter on OBJECT_VERSION_NUMBER during integration loads to detect stale rows.
• Query ATTRIBUTE_CATEGORY and the ATTRIBUTE1–15 columns to expose customer-specific flexfield extensions.

Because the table is small and read during workflow initialization, it is not a high-volume reporting subject; its primary analytical value is in configuration auditing and troubleshooting.

Related Objects

• FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID; the only documented foreign key relationship.
• FND_APPLICATION — resolves APPLICATION_ID to the owning product short name.
• FND_USER — resolves CREATED_BY and LAST_UPDATED_BY audit columns.
• JTF_BRM_RULES / JTF_BRM_RULE_SETS — the rule definitions evaluated by the monitor whose execution context this table parameterizes.
• WF_ITEM_TYPES / WF_PROCESSES — resolve WORKFLOW_ITEM_TYPE and WORKFLOW_PROCESS_NAME to the Workflow definitions referenced.
• FND_FLEX_VALUES_VL — relevant when the ATTRIBUTE flexfield columns are enabled and populated.
• JTF_BRM_JOBS / JTF_BRM_LOG — runtime entities that consume the parameters and record execution outcomes.