Search Results icx_transactions_s

Overview

APPS.WF_FWKMON is a server-side PL/SQL package body belonging to the Oracle Workflow framework monitor component within Oracle E-Business Suite. Its role is to support the runtime presentation and management of workflow monitoring through self-service, web-based interfaces, particularly the Workflow Monitor and the notification response infrastructure exposed through the ICX (Oracle Applications Framework/self-service) stack. The package bridges Oracle Workflow runtime data with the ICX transaction and security layer, allowing end users, administrators, and anonymous guests to retrieve notification results, inspect item activity statuses, resolve role e-mail addresses, and generate access URLs for monitoring workflows without directly querying workflow tables.

Because WF_FWKMON references ICX_TRANSACTIONS and ICX_TRANSACTIONS_S, it participates in the ICX transaction bookkeeping used to register and track self-service sessions. The package is classified as an OTHER API, meaning it is not part of Oracle's published public API set but is nonetheless a critical internal dependency for delivered Workflow Monitor functionality. It is not referenced by any other database object, but it depends heavily on FND_PROFILE, FND_WEB_CONFIG, ICX_CALL, ICX_SEC, WF_CORE, WF_MONITOR, and numerous workflow runtime tables.

Key Procedures and Functions

The documented ETRM metadata lists twelve callable units for this package body. These fall into several functional groups:

• Notification handling: GETNOTIFICATIONRESULT, ISRESPONDNOTIFICATION, and GETNTFRESPONDERNAME support retrieval of the outcome of a workflow notification and identification of the responder, enabling the Monitor to display what action was taken and by whom.
• Item status: GETITEMSTATUS returns the current status of a workflow item, central to displaying process state in the Monitor.
• Directory and role access: GETROLEEMAILADDRESS resolves the e-mail address associated with a workflow role, typically used for notification delivery and administrative display.
• Security and access keys: GETENCRYPTEDACCESSKEY and GETENCRYPTEDADMINMODE generate encrypted tokens used to authorize monitor access and administrative mode, preventing URL tampering.
• Administrator check: ISMONITORADMINISTRATOR determines whether the current user holds Workflow Monitor administrative privileges.
• Anonymous and guest URLs: GETANONYMOUSSIMPLEURL, GETANONYMOUSADVANCEURL, and GETGUESTMONITORURL construct URLs that allow anonymous or guest users to view simple status, advance workflow items, or open the guest monitor, respectively.
• Guest entry point: GUESTMONITOR serves as the guest-facing procedure that invokes the monitor for unauthenticated access.

No parameter signatures are provided in the documentation; the above describes purpose only.

Tables Accessed

WF_FWKMON reads and writes workflow runtime and configuration data. ICX_TRANSACTIONS and ICX_TRANSACTIONS_S store the self-service transaction records that link a user session to a monitored workflow item. WF_ACTIVITIES and WF_PROCESS_ACTIVITIES provide the process definition and activity structure needed to render the workflow hierarchy. WF_ITEM_ACTIVITY_STATUSES supplies the per-item activity state used by GETITEMSTATUS. WF_NOTIFICATIONS and WF_NOTIFICATION_ATTRIBUTES hold notification instances and their attributes for result and responder resolution. WF_MESSAGE_ATTRIBUTES supports message-level detail, WF_COMMENTS stores user comments, and WF_ROLES supports role e-mail and permission checks. OWA_UTIL is used to emit HTML output.

Usage Notes

WF_FWKMON is invoked indirectly through the Oracle Workflow Monitor and its associated self-service Java/HTML pages rather than from the Oracle Forms interface. Administrators typically reach it via the Workflow Monitor administration screens, while end users and guest users access it through generated anonymous and guest URLs. Because it references ICX_SEC and ICX_CALL, any custom code invoking these routines must run within an authenticated ICX session or supply a valid encrypted access key. Customizations should prefer documented public Workflow APIs; direct calls to WF_FWKMON are unsupported and may be affected by patching across 12.1.1 and 12.2.2.