Search Results fun_wf_common




Overview
Explore in AI Chat

Overview

APPS.FUN_WF_COMMON is the shared Workflow utility package for the Oracle E-Business Suite Financials (FUN) products, most notably Payables and Receivables. Its role is to centralize the recurring logic required to integrate FUN transactions with the Oracle Workflow engine and the Approvals Management Engine (AME). Rather than duplicating approval and notification code across individual transaction packages, the FUN product family funnels those operations through FUN_WF_COMMON.

The metadata confirms the package is VALID in the APPS schema and classified as OTHER in the ETRM API registry. It depends only on SYS and STANDARD, meaning it is a low-level building block rather than a consumer of other APPS packages, which reinforces its position as a foundational utility layer. In contrast, it is referenced by eight higher-level packages, including FUN_GLINT_WF, FUN_INITIATOR_WF_PKG, FUN_MULTI_SYSTEM_WF_PKG, FUN_RECIPIENT_WF, FUN_TRX_PUB, and FUN_TRX_PVT, confirming that the transaction and workflow sub-components of Financials depend on it to raise events, manage approval statuses, and resolve approvers.

Key Procedures and Functions

The ETRM register documents eighteen procedures and functions. They fall into three functional clusters:

No parameter signatures are published in the ETRM excerpt; the names above are the authoritative interface as documented.

Tables Accessed

FUN_WF_COMMON reaches these objects through APPS synonyms:

Usage Notes

Because FUN_WF_COMMON is referenced by FUN_TRX_PUB, FUN_TRX_PVT, and the FUN_*_WF packages, it is normally invoked indirectly. A user or concurrent program initiates an AP/AR transaction or batch, the transaction layer calls the relevant FUN_*_WF package, and that package delegates to FUN_WF_COMMON to resolve AME approvers, raise workflow events, and refresh transaction status. END users therefore encounter it through approval routing and notification screens and through the Workflow status monitor rather than through a dedicated form or concurrent program.

Custom development should call the public procedures above rather than manipulating WF_ITEM_ACTIVITY_STATUSES or FUN_TRX_HEADERS directly, since the package encapsulates the correct event-key generation, message assembly, and status transitions. Because the package is validated against 12.1.1 and 12.2.2, custom code that invokes it should be re-tested after any Financials patch, as the procedure inventory has evolved across releases.