Results for “error_rule”

16 results




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

Overview

The APPS.WF_XML package is a core Oracle Workflow infrastructure component that manages the storage, generation, parsing, and retrieval of XML-based message payloads within the Oracle E-Business Suite notification framework. Its primary business function is to serialize workflow notifications, event messages and attachments into XML form and to reconstruct them at the point of consumption. Because Oracle Workflow supports an XML message format for notifications and business events, WF_XML acts as the transformation bridge between the relational workflow tables and the XML message content that is presented to users through the Notification System or transmitted to external systems.

The package is classified as OTHER in the ETRM API classification and holds VALID status in both release 12.1.1 and 12.2.2. It exposes 28 documented procedures and functions, and depends on WF_DIRECTORY and the workflow type definitions WF_EVENT_T and WF_PARAMETER_LIST_T. It is referenced by five dependent packages, including WF_MAIL, WF_DIAGNOSTICS, WF_BES_DYN_FUNCS, ALR_MLR_PACKAGE and WF_REPOPULATE_AQ, confirming its role as a low-level utility consumed by both the notification mailer and Business Event System subsystems.

Key Procedures and Functions

The documented procedures cover four broad areas: XML content construction, notification lifecycle management, queue interaction and message interpretation.

  • Content generation and retrieval: GENERATE, GETXMLMESSAGE, GETMESSAGE, GETSHORTMESSAGE, GETDOCCONTENT, GETBDOCCONTENT, GETATTACHMENT and GETLOBTABLESIZE build or extract XML payloads, document content, binary document content and attachment bodies, and report on large object sizing.
  • Tag and exception handling: GETTAGVALUE extracts a named element from an XML document; GETEXCEPTIONMESSAGE and ERROR_RULE provide error path handling; SUMMARYRULE supports condensed message output.
  • Notification and queue operations: ENQUEUENOTIFICATION, REMOVENOTIFICATION, DEQUEUEMESSAGE, GETQUEUEMESSAGE, SETFIRSTMESSAGE, SENDNOTIFICATION and RECEIVE manage the placement, extraction and delivery of messages through the Advanced Queueing infrastructure.
  • Response processing: GETRESPONSEDETAILS returns the response content captured against a notification.

Tables Accessed

WF_XML reads and writes the principal Workflow runtime tables through APPS synonyms. WF_NOTIFICATIONS and WF_NOTIFICATION_ATTRIBUTES hold notification headers and their attribute values; WF_MESSAGE_ATTRIBUTES stores message content; WF_EVENT_T and WF_PARAMETER_LIST_T represent event and parameter payloads; WF_AGENT_T and WF_DIRECTORY resolve agent addresses; WF_ITEMS, WF_ITEM_ACTIVITY_STATUSES and WF_PROCESS_ACTIVITIES provide the process context needed to render notification XML. WF_QUEUES, together with DBMS_AQ, supports queue persistence, while DBMS_LOB, DBMS_SESSION, DUAL and PLITBLM provide supporting LOB, session and utility services.

Usage Notes

WF_XML is not typically invoked directly by end users. It is called internally by the Workflow Notification Mailer, by Business Event System functions and by diagnostic and repopulation utilities such as WF_DIAGNOSTICS and WF_REPOPULATE_AQ. Developers writing custom notification handlers, event subscriptions or XML message processors may call its public procedures to generate or parse workflow message content. Because it manipulates queue and LOB structures, invocations should be treated as transactional and executed within the standard Workflow processing environment rather than ad hoc SQL sessions.