Search Results init_monitor

Overview

APPS.JTF_BRM_PVT is the private implementation package body for the Business Rule Monitor (BRM) infrastructure within Oracle E-Business Suite Release 12.1.1 and 12.2.2. The BRM component provides scheduled, rule-driven monitoring of business conditions by leveraging the Oracle Workflow engine as its runtime orchestration layer. This package is classified as PVT, meaning it is intended strictly for internal consumption by the Workflow engine and by the public wrapper APIs that front it; it is not a supported integration point for customer extensions.

The package encapsulates the lifecycle logic required to instantiate a Business Rule Monitor, arm it with a timer interval derived from a unit-of-measure specification, evaluate configured rules on each interval tick, and terminate the monitor cleanly. Because the monitor runs as a Workflow item of type JTFBRM, the package bridges Workflow activity callbacks with the underlying BRM configuration tables. Administrators interact with the behavior indirectly through BRM setup and the Workflow Administrator responsibility rather than by calling this package directly.

Key Procedures and Functions

• SELECTOR — Workflow selector procedure that determines which process to execute based on the supplied function mode. In RUN mode it directs the engine to the MONITOR_RULES process; on error it records context via WF_CORE.CONTEXT and re-raises.
• INIT_MONITOR — Creates, initializes, and starts a Business Rule Monitor instance. Returns TRUE on success and FALSE on failure.
• START_MONITOR — Begins execution of the monitor instance after initialization has completed.
• CALCULATE_INTERVAL — Computes the effective timer interval from the caller-supplied unit-of-measure type, unit-of-measure code, and timer unit count.
• PROCESS_RULES — Evaluates the rules associated with the active monitor and dispatches resulting actions.
• CHECK_INTERVAL — Determines whether the elapsed time has reached the configured interval, gating the next rule processing cycle.
• GET_BRM_COMMAND — Retrieves the BRM command directive that governs the monitor's current behavior.
• STOP_MONITOR — Terminates the monitor instance and releases its runtime state.
• COMMIT_WF — Commits Workflow-related transactional work so that monitor state changes are persisted independently of the caller's transaction boundary.

Tables Accessed

• JTF_BRM_ACTIVITIES_S — The BRM activities base table (with its _S suffix denoting the language-independent segment), read and updated to maintain monitor activity records.
• JTF_BRM_PARAMETERS — Stores configurable parameters that drive monitor behavior, such as timer units and administrative settings.
• JTF_BRM_PROCESSES — Holds the process definitions that SELECTOR and PROCESS_RULES use to resolve the correct Workflow process to run.
• DUAL — Used for scalar evaluations and single-row utility queries.

Usage Notes

JTF_BRM_PVT is invoked almost exclusively by the Oracle Workflow engine through the JTFBRM item type. The SELECTOR procedure serves as the standard Workflow activity function, receiving the item type, item key, activity ID, and function mode, and returning the name of the process to run. The package is also reachable through the public BRM APIs that create and manage monitors on behalf of administrative setup screens. Profile option JTF_BRM_WF_ADMINISTRATOR is read during INIT_MONITOR to resolve the Workflow administrator identity for the monitor instance.

No other documented packages reference JTF_BRM_PVT, confirming its position as a leaf-level private implementation. Custom code should not call these procedures directly; developers requiring monitor behavior should use the supported public BRM APIs and rely on Workflow configuration instead. Because the package writes to BRM configuration tables and raises Workflow events, any diagnostic testing should be performed in a non-production environment with Workflow background engines monitored closely. The c_lookups search term is commonly associated with BRM rule configuration, but lookup resolution is handled through the public BRM layer rather than within this private package body.