Search Results fnd_wf_standard




Overview
Explore in AI Chat

Overview

FND_WF_STANDARD is a PL/SQL package body owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It provides the standard Oracle Workflow wrapper layer used to integrate concurrent program execution into workflow-driven business processes. Its principal business function is to submit, monitor, and complete Oracle Concurrent Manager requests from within a workflow activity, allowing a workflow process to invoke an EBS concurrent program, wait for it to finish, and then hand control back to the workflow engine. The package is classified as OTHER in the ETRM repository and carries a status of VALID.

In practice, FND_WF_STANDARD is the plumbing that allows a workflow function or notification to call the Concurrent Manager and reflect its outcome back into workflow item state. It abstracts the mechanics of FND_REQUEST.SUBMIT_REQUEST, concurrent request polling, and completion status handling, while also supporting the callback pattern used by the workflow engine when the concurrent program finishes. This makes it a foundational component for EBS features such as Standard Concurrent Program workflow activities.

Key Procedures and Functions

The ETRM metadata documents six procedures and functions in this package body:

  • SUBMITCONCPROGRAM — submits a concurrent program to the Concurrent Manager on behalf of the workflow, initiating the asynchronous execution of the target request.
  • EXECUTECONCPROGRAM — combines submission and execution handling, driving the concurrent program through the workflow call path.
  • WAITFORCONCPROGRAM — polls or blocks until the submitted concurrent request reaches a terminal phase, allowing the workflow to await completion before proceeding.
  • SUBMIT_CP — a lower-level submission helper that performs the actual concurrent request submission logic.
  • SEED_CB — the workflow callback routine invoked by the workflow engine when the associated concurrent request activity completes, used to seed callback behavior into the workflow.
  • CALLBACK — the standard callback entry point executed when the workflow engine returns control, updating the workflow item based on the concurrent request outcome.

Tables Accessed

The documented table reference for this package is FND_CONCURRENT_REQUESTS, accessed through the APPS synonym. This table is the authoritative record of every concurrent request submitted to the Concurrent Manager, storing request identifiers, phase and status codes, completion text, and timing information. FND_WF_STANDARD reads from and writes to it to determine whether a submitted request is pending, running, completed normally, completed with warnings, or errored, and to reconcile the workflow item with the concurrent request result.

The dependency metadata further shows references to FND_CONCURRENT, FND_CONC_PP, FND_MESSAGE, FND_PROFILE, FND_REQUEST, WF_CORE, WF_ENGINE, WF_ENGINE_UTIL, WF_ITEM_ACTIVITY_STATUS, and SYS.STANDARD. These represent the supporting concurrent manager, workflow engine, profile, and messaging APIs that the package calls during submission, monitoring, and callback processing.

Usage Notes

FND_WF_STANDARD is invoked indirectly rather than by end users. It is called by the Oracle Workflow engine when a workflow process definition includes a Standard Concurrent Program activity, and it is referenced by five other database objects per the ETRM metadata. Custom workflow functions in the APPS schema can call SUBMITCONCPROGRAM, EXECUTECONCPROGRAM, and WAITFORCONCPROGRAM directly to embed concurrent program execution in bespoke workflow processes.

The CALLBACK and SEED_CB routines are registered with the workflow engine so that completion of the concurrent request resumes the suspended workflow, updates WF_ITEM_ACTIVITY_STATUS, and progresses the item to the next activity. Because the package body is not referenced by any other database object but references many, it operates as a mid-tier integration utility. The package body is VALID in both 12.1.1 and 12.2.2, and its behavior is stable across those release levels.