Search Results wf_monitor




Overview
Explore in AI Chat

Overview

APPS.WF_MONITOR is the Oracle Workflow monitoring package that supplies the server-side PL/SQL logic behind the Workflow Monitor component of Oracle E-Business Suite. It renders the status of running and completed workflow processes, exposes the graphical process diagram, and provides administrative access to item-level detail for a given workflow instance. In release 12.1.1 and 12.2.2 the package is installed in the APPS schema with a VALID status and is classified as a non-public ("OTHER") API. The package body depends on core Workflow Engine components such as WF_ENGINE, WF_CORE, WF_ENGINE_UTIL, and WF_DIRECTORY, and on the Oracle Application Framework utilities WF_WEB_CONFIG, ICX_CALL, WFA_HTML, and WFA_SEC, which together supply authentication and HTML rendering context. It is not referenced by any database object, but it references many, which confirms its role as a top-level presentation and diagnostic layer rather than a reusable application API.

Key Procedures and Functions

The documented interface contains twenty-seven procedures and functions, organized around two responsibilities: rendering HTML output and resolving workflow metadata.

  • Rendering entry points: SHOW, HTML, ENVELOPE, ENVELOPE_FRAME, and DRAW_PROCESS_CHILDREN generate the Monitor user interface, including the envelope view of a process and its nested subprocesses.
  • URL and navigation helpers: GETURL, GETDIAGRAMURL, GETENVELOPEURL, and GETADVANCEDENVELOPEURL build the links used to display diagrams and advanced process views.
  • Metadata resolution: GETPROCESS, GETROLE, GETRESOURCE, GETRESOURCES, NAME, and GETACCESSKEY retrieve process definitions, role and resource information, display names, and access keys required before a monitor page can be drawn.
  • Instance inspection: FIND_INSTANCE, INSTANCE_LIST, ENGAPI, and PROCESS_CHILDREN, together with GET_PROCESS_CHILDREN, locate workflow items, list processes for a user, and drill into child activities.

No parameter signatures are documented; the functions above are named for their purpose only.

Tables Accessed

WF_MONITOR reads the Workflow definition and runtime tables through APPS synonyms. Definition-side access includes WF_ACTIVITIES, WF_ACTIVITIES_TL, WF_ACTIVITY_ATTR_VALUES, WF_ACTIVITY_TRANSITIONS, WF_PROCESS_ACTIVITIES, WF_ITEM_TYPES_VL, and WF_ITEM_DEFINITION_UTIL_PUB, which provide activity names, transitions, and item type metadata. Runtime access includes WF_ITEMS, WF_ITEM_ACTIVITY_STATUSES, WF_ITEM_ACTIVITIES_HISTORY_V, WF_ITEM_ATTRIBUTE_VALUES, WF_NOTIFICATIONS, and WF_NOTIFICATION_ATTRIBUTES, which supply activity status, history, attribute values, and open notifications. WF_DIRECTORY, WF_ROLES, WF_RESOURCES, WF_LANGUAGES, WF_LOOKUPS, and WF_LOOKUP_TYPES resolve user, role, language, and lookup context. DBMS_LOB, DBMS_SESSION, HTF, HTP, and OWA_UTIL are used for CLOB handling, session state, and HTML generation.

Usage Notes

WF_MONITOR is invoked primarily through the Workflow Monitor web pages, which call SHOW and the associated URL helpers to display process status, diagrams, and notification history. Administrators reach it from the Workflow Administrator responsibility; end users may reach it where the monitor function is granted. It is also called by FND_RUN_FUNCTION and FND_FUNCTION registration paths when the monitor is launched from a menu or function. Custom code should treat WF_MONITOR as an internal presentation package: it is not a published API, its signatures may change between releases, and direct calls are discouraged in favor of documented Workflow Engine and Notification APIs. Dependency on FND_SESSION_MANAGEMENT, FND_PROFILE, and FND_WEB_CONFIG means it requires an active EBS session and properly configured web context to execute successfully.