Results for “process_end_date_active”

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

Overview

The APPS.JTF_BRM_RULES_V view is a CRM Foundation (JTF) database object that exposes business rule definitions maintained by the Business Rule Workbench form. It consolidates rule header attributes, associated business rule processes, workflow configuration, lookup-decoded meanings, and rule-owner information into a single queryable result set. The view is not a stored table; it is a join-based projection whose primary purpose is to feed the Business Rule Workbench form (the workflow_display_name reference in the view text confirms that workflow metadata is surfaced directly to the UI), while also being available for custom reporting and integration.

In Oracle EBS 12.1.1 and 12.2.2, the object is owned by APPS, is VALID, and belongs to the JTF – CRM Foundation product family. Because it is a view over translated and non-translated base objects, it is read-oriented: DML against the view is generally not supported, and rule maintenance is performed through the underlying base tables via the form or public APIs.

Underlying Base Objects

Per documented metadata, JTF_BRM_RULES_V is defined over the following objects:

• JTF_BRM_RULES_VL (VIEW) — the translated base view holding the rule header (rule name, description, owner, object type/code, view name/definition, active dates, DFF attributes).
• JTF_BRM_PROCESSES (SYNONYM) — supplies the process-level scheduling and workflow configuration columns (check interval, UOM types, tolerance interval, workflow item type and process name, seeded flag).
• FND_LOOKUPS (VIEW) — joined three times to decode object type, check-interval UOM, and tolerance-interval UOM meanings, filtered to enabled lookups active as of TRUNC(SYSDATE).
• PER_ALL_PEOPLE_F (SYNONYM) — resolves RULE_OWNER_ID to the full name of the owning person.
• JTF_LOOKUPS_BRM_WF_V (VIEW) — supports workflow display-name resolution surfaced as WORKFLOW_DISPLAY_NAME.
• FND_GLOBAL (PACKAGE) — supplies session/context values (for example, the current application and responsibility) used in the view's query predicates.

The join chains JTF_BRM_RULES_VL to JTF_BRM_PROCESSES on PROCESS_ID, decodes lookup values from FND_LOOKUPS, resolves the owner from PER_ALL_PEOPLE_F via RULE_OWNER_ID, and attaches the workflow description from the workflow lookup view. This design centralizes rule, process, and workflow presentation in one structure.

Key Columns

• ROW_ID, RULE_ID, RULE_NAME, RULE_DESCRIPTION — rule identity and descriptive text.
• RULE_OWNER_ID / RULE_OWNER_NAME — owning person's identifier and resolved full name (from PER_ALL_PEOPLE_F).
• BRM_OBJECT_TYPE, BRM_OBJECT_CODE, OBJECT — the rule's target object type/code and its decoded lookup meaning.
• PROCESS_ID, BRM_CHECK_INTERVAL, BRM_UOM_TYPE, BRM_CHECK_UOM_CODE, CHECK_INTERVAL_UOM — process reference and scheduling cadence with decoded UOM.
• BRM_TOLERANCE_INTERVAL, BRM_TOLERANCE_UOM_CODE, TOLERANCE_INTERVAL_UOM — tolerance window and decoded UOM.
• WORKFLOW_ITEM_TYPE, WORKFLOW_PROCESS_NAME, WORKFLOW_DISPLAY_NAME — workflow binding, where WORKFLOW_DISPLAY_NAME is the WF_DESCRIPTION shown in the Workbench form.
• RULE_START_DATE_ACTIVE / RULE_END_DATE_ACTIVE, PROCESS_START_DATE_ACTIVE / PROCESS_END_DATE_ACTIVE — effective dating for the rule and its process.
• SEEDED_FLAG — indicates Oracle-seeded versus user-defined rules.
• VIEW_NAME, VIEW_DEFINITION — the underlying database view that implements rule evaluation.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — descriptive flexfield columns.

Common Use Cases and Queries

Typical uses include auditing active business rules, reporting which workflow each rule invokes, and identifying seeded versus custom rules prior to upgrades or patching.

• List active rules with workflow display names — filter on effective dates and order by rule name:

SELECT RULE_ID, RULE_NAME, OBJECT, WORKFLOW_ITEM_TYPE,
       WORKFLOW_PROCESS_NAME, WORKFLOW_DISPLAY_NAME
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));

• Report seeded versus custom rules — aggregate on SEEDED_FLAG to gauge customization.
• Identify owner and process scheduling — join RULE_OWNER_NAME with BRM_CHECK_INTERVAL, CHECK_INTERVAL_UOM, BRM_TOLERANCE_INTERVAL, and TOLERANCE_INTERVAL_UOM to review operational cadence.

Because the view already decodes lookup meanings and resolves owner and workflow descriptions, these queries avoid additional joins to FND_LOOKUPS or PER_ALL_PEOPLE_F and are suitable for concurrent programs, BI Publisher reports, and integration extracts in both 12.1.1 and 12.2.2.