Results for “jtf_brm_uom_type”

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

Overview

APPS.JTF_BRM_RULES_V is a supplementary view in the Oracle E-Business Suite Applications (APPS) schema that exposes Business Rule Management (BRM) rule definitions in a form suitable for coding, inquiry, and integration. The object is registered as View Type "supplementary," meaning its primary purpose is to simplify Forms coding rather than to serve as a public data access interface. The view is shipped with FND Design Data reference JTF.JTF_BRM_RULES_V and is reported as VALID in ETRM 12.2.2; the same definition is present in 12.1.1.

The view presents one row per business rule, joining the rule's base definition with process metadata, workflow lookup descriptions, and person (owner) details. Access is governed by an Oracle Internal Use Only warning: Oracle does not support direct querying or modification of application data through this object except from standard Oracle Applications programs. Consultants and developers should treat it as a diagnostic and read-only reporting surface, and must expect its column list to change materially in subsequent minor or major releases.

Underlying Base Objects

The documented definition of the view references the following objects:

• JTF_BRM_RULES_VL — the base view providing the translatable rule attributes and rule identity.
• JTF_BRM_PROCESSES (synonym) — supplies process-level context such as process identifiers and process activity dates.
• FND_GLOBAL (package) — used within the view logic for session/context resolution.
• FND_LOOKUPS (view) — resolves lookup codes to their meanings, for values such as object type, UOM type, and check/tolerance UOM codes.
• JTF_LOOKUPS_BRM_WF_V (view) — a BRM-specific lookup view used to resolve workflow display names.
• PER_ALL_PEOPLE_F (synonym) — the HR people date-tracked table, used to derive rule owner names.

Because owner names originate from PER_ALL_PEOPLE_F, effective-dated person records influence results; likewise, lookup-based descriptive columns depend on the language and lookup configuration of the environment.

Key Columns

The column list reflects the view's role as a denormalized rule catalog. Identity columns include RULE_ID, RULE_NAME, RULE_DESCRIPTION, ROW_ID (the underlying ROWID), and SEEDED_FLAG. Ownership is exposed through RULE_OWNER_ID and the joined RULE_OWNER_NAME. Object targeting is described by BRM_OBJECT_TYPE, BRM_OBJECT_CODE, and OBJECT.

Scheduling and monitoring attributes include PROCESS_ID, BRM_CHECK_INTERVAL, BRM_UOM_TYPE, BRM_CHECK_UOM_CODE, CHECK_INTERVAL_UOM, BRM_TOLERANCE_INTERVAL, BRM_TOLERANCE_UOM_CODE, and TOLERANCE_INTERVAL_UOM. These are paired with the effective-dating columns RULE_START_DATE_ACTIVE and RULE_END_DATE_ACTIVE, which define the interval in which a rule is active. The user's search term, rule_end_date_active, corresponds directly to the RULE_END_DATE_ACTIVE column; a NULL value indicates an open-ended rule with no scheduled termination.

Workflow integration columns are WORKFLOW_ITEM_TYPE, WORKFLOW_PROCESS_NAME, and WORKFLOW_DISPLAY_NAME. The view also exposes VIEW_NAME, VIEW_DEFINITION, and PROCESS_START_DATE_ACTIVE / PROCESS_END_DATE_ACTIVE, plus ATTRIBUTE1 through ATTRIBUTE11, which are descriptive flexfield segments available for customer-specific rule metadata.

Common Use Cases and Queries

The principal uses are investigating why a business rule fired, auditing which rules are currently in effect, and identifying orphaned or expired rule configurations. Filtering on RULE_END_DATE_ACTIVE is the standard way to determine active versus retired rules. A typical active-rule listing is:

SELECT rule_id, rule_name, br m_object_code, rule_start_date_active, rule_end_date_active FROM apps.jtf_brm_rules_v WHERE TRUNC (SYSDATE) BETWEEN NVL (rule_start_date_active, TRUNC (SYSDATE)) AND NVL (rule_end_date_active, TRUNC (SYSDATE));

To locate rules with no end date, or that have expired:

• SELECT rule_id, rule_name FROM apps.jtf_brm_rules_v WHERE rule_end_date_active IS NULL;
• SELECT rule_id, rule_name, rule_end_date_active FROM apps.jtf_brm_rules_v WHERE rule_end_date_active < TRUNC (SYSDATE);

Joining to owner and workflow information supports escalation and ownership audits, for example grouping by RULE_OWNER_NAME or resolving WORKFLOW_DISPLAY_NAME for a given WORKFLOW_ITEM_TYPE. Where the workflow lookup resolves poorly, the underlying JTF_BRM_RULES_VL should be used instead. Because the view is supplementary and unsupported for direct data access, any query used in production should be validated against supported BRM APIs, and the definition re-verified after each patch or upgrade.