Search Results raise_table




Overview

FND_WF_EVENT is an Oracle Application Object Library (FND) package that supports the Oracle Workflow notification and event framework embedded within Oracle E-Business Suite. The package body resides in the APPS schema and is classified under the generic "OTHER" API category, indicating that it is a supporting or utility package rather than a formally published public interface. Its principal responsibility is to resolve the runtime context of a workflow item — that is, to determine whether the current activity for a given item type and item key is an outstanding notification or a form-based activity, and to return the associated form function, attribute values, and error information to the caller.

In the 12.1.1 and 12.2.2 releases, FND_WF_EVENT operates alongside the core Workflow engine tables to enable forms and concurrent processes to interrogate the state of a workflow-driven transaction. The header of the source file (afwfeveb.pls) shows that the package has been largely stable since 2003, with the current logic centered on the GET_FORM_FUNCTION routine that inspects the most recent activity for a workflow item.

Key Procedures and Functions

The ETRM metadata documents four program units within the package body:

  • GET_FORM_FUNCTION — The central public function. It accepts a workflow item type and item key and returns the form function name applicable to the most recent activity. It opens a cursor over WF_ITEM_ACTIVITY_STATUSES filtered by activity status 'NOTIFIED', ordered by begin date and execution time descending, so that the latest notified activity is examined first. If a notification identifier is non-zero, the function retrieves the response attribute value from the notification attributes; otherwise it resolves the attribute value through the process activity, activity, and activity attribute tables. This dual-path logic allows the package to return the correct form entry point regardless of whether the item is sitting on a notification or on a form activity.
  • RAISE_TABLE — The procedure corresponding to the user's search term. Although the excerpt does not show its body, in the context of FND_WF_EVENT it is used to signal or raise errors related to table-level workflow operations, providing a structured mechanism for reporting invalid item type, item key, or missing attribute conditions to the calling application.
  • GET_ERROR_NAME — A helper function that translates an error code or condition into a meaningful error name for display or logging, supporting diagnostics within workflow event processing.
  • ERASE — A utility procedure that removes or clears transient workflow event data, typically used for cleanup of cached or temporary state associated with a completed activity.

Tables Accessed

The package reads from the core Workflow runtime dictionary and runtime tables via APPS synonyms. WF_ITEM_ACTIVITY_STATUSES provides the activity status and notification/process activity identifiers used to determine the current context. WF_NOTIFICATIONS, WF_NOTIFICATION_ATTRIBUTES, and WF_MESSAGE_ATTRIBUTES support resolution of notification response values. WF_PROCESS_ACTIVITIES, WF_ACTIVITIES, WF_ACTIVITY_ATTRIBUTES, and WF_ACTIVITY_ATTR_VALUES provide the activity definition and attribute value resolution path for form-based activities. WF_ITEMS supplies the item instance context, while WF_PARAMETER_LIST_T, WF_PARAMETER_T, and the PL/SQL table type PLITBLM are used for parameter handling. All access appears to be read-only, consistent with the interrogation role of the package.

Usage Notes

FND_WF_EVENT is referenced by five other packages, indicating it is invoked indirectly by higher-level Workflow APIs rather than being called directly by end users. It is most commonly reached when an Oracle Forms-based workflow component needs to determine which form function should be launched for the current item, or when a concurrent program needs to evaluate workflow activity state. Customizations should avoid direct dependency on this package unless the calling code faithfully reproduces the item type, item key, and status assumptions described above. In upgrade scenarios between 12.1.1 and 12.2.2, the package remains compatible with the standard Workflow schema, and any error surfaced through RAISE_TABLE should be interpreted in conjunction with the Workflow Administrator diagnostic reports.