An Oracle blog about Workflow logs

  • January 18, 2013

Oracle Workflow - E-Business Suite vs Standalone

Vijay Shanmugam

Oracle Workflow has following components that together provide business process management capabilities.

  • Workflow Builder - Windows desktop tool to create and customize workflow processes
  • Workflow Loader - Commandline tool to load workflow definition to database
  • Workflow Engine - PLSQL engine to execute workflow processes definitions
  • Workflow Notification Mailer - Background program to send e-mail notifications
  • Workflow Business Event System - PLSQL and Java based engine to process business events
  • Workflow Agent Listeners - Background program to process business events

Oracle Workflow has been available in two flavors until about 2007.

  1. Workflow Embedded in E-Business Suite
  2. Workflow Standalone

This post is aimed at clarifying how Oracle Workflow in E-Business Suite and Standalone were versioned and the current status of these two flavors.

Workflow Embedded in E-Business Suite

In E-Business Suite, Oracle Workflow is an integral part of foundation modules (FND) alongside Profiles, Concurrent Programs, OA Framework and so on and is shipped in ATG patchsets. For example, Workflow's Java classes are available under $JAVA_TOP like any other FND module, it's PLSQL packages are compiled into APPS schema, datamodel is available under APPLSYS schema and so on. This
flavor is also called Embedded Workflow, meaning it was embedded
in E-Business Suite.


Embedded Workflow's packaging, release, installation and configuration follows standard E-Business suite's processes. Embedded Workflow is  not identified with it's own version in E-Business Suite, instead it's codelevel is always identified using the current ATG Patchset level.

For example, if a Customer is on E-Business Suite Release 12.1.3, then their Workflow codelevel is R12.ATG_PF.B.Delta.3 (in addition to any Workflow specific one-offs that may have applied on the baseline) which is a standard way of identifying any FND module.

Current Status

Oracle Workflow embedded in E-Business Suite has the same lifetime as the ATG Patchset in that Oracle E-Business Suite. For example, if a Customer is on Oracle E-Business Suite 12.1.3, the workflow module being integral part of Oracle E-Business Suite installation, has no different lifetime or support policy than the R12.ATG_PF.B Patchset. When looking at Oracle Workflow module from E-Business Suite standpoint, it should not be viewed as a separate product rather at the ATG Patchset level.

For more information please refer to 

Workflow Standalone

All of Oracle Workflow's sub-components and the underlying data model were packaged, released, installed and configured completely independent of E-Business Suite until about late 2007.  A Workflow Standalone installation results in a special database schema like OWF_MGR specific to workflow alone unlike the standard APPS and APPLSYS schemas of E-Business Suite.

Oracle Workflow Standalone however was not shipped on it's own but using following release vehicles.

  • Oracle Database - Upto 10gR2
  • Oracle iAS - Upto 10.1.2
  • Oracle Warehouse Builder - Still packaged with OWB 11g

Oracle Workflow standalone product was available as part of above product offerings which helped non-E-Business Suite Customers to have Workflow (Business Process Management) capabilities such as implementing custom approval flows, document approval routing, sending notifications and so on.


Workflow Standalone had it's own versioning mechanism that was completely unrelated to E-Business Suite's. For example, following were some of the recent verisons.

  • Oracle Database 10gR2 - Oracle Workflow 2.6.4
  • Oracle iAS 10.1.2 - Oracle Workflow
  • Oracle iAS 9.0.4 - Oracle Workflow 2.6.3

Current Status

With the advent of better Business Process Execution standards and tools, Oracle Workflow was ceased to be shipped with Oracle Database and Oracle iAS. Oracle BPEL Process Manager (in Oracle SOA Suite 10g) and Oracle SOA Suite 11g are the recommended technologies to be considered by Customers who were using Oracle Workflow Standalone to implement their business processes.

To this effect, MOS Doc 391546.1 was published to announce obsolescence of Workflow Standalone with Oracle Database 10gR2 as the terminal release vehicle for the product. This note applies only to Workflow as a standalone product and does not affect Workflow embedded in E-Business Suite.

Workflow Standalone Obsolescence Notice

MOS Doc 391546.1 clarifies that Workflow as a standalone product will not be shipped in Oracle Database 11g and above. Since Oracle Database 10gR2 is the last release Workflow Standalone was shipped in, existing Oracle Database 10gR2 Customers who also use Workflow Standalone will continue to receive support as per Oracle Database 10gR2 support policies. This obsolescence notice should not be confused with support for Workflow embedded in E-Business Suite.


Oracle Workflow embedded in E-Business Suite is being actively maintained and enhancements implemented based on Customer
requirements. We have some exciting days ahead of us for Oracle Workflow embedded in E-Business Suite.

Join the discussion

Comments ( 7 )
  • Naeem Tuesday, January 22, 2013

    Thanks Vijay for this great, to-the-point, information about the workflow. Vijay, I am also looking for some accurate information on checking its health and tune it to its best. I am using embedded workflow in 12.1.3. Could you please refer me to your any other blog that contains this?

  • Vijay Shanmugam Tuesday, January 22, 2013


    We are planning to start a series of troubleshooting and maintenance related topics for Oracle Workflow embedded in EBS. For now, please look at Workflow Analyzer scripts at https://blogs.oracle.com/oracleworkflow/entry/e_business_suite_proactive_support



  • HarKenToh Tuesday, January 22, 2013

    Workflow Analyzer script for E-Business Suite Workflow Monitoring and Maintenance [ID 1369938.1]

    The Workflow Analyzer is a Self-Service Health-Check script which reviews the overall Workflow Footprint, analyzes the current configurations and settings for the Workflow environment providing feedback and recommendations on Best Practices.

    This is a non-invasive script which provides recommended actions to be performed on the instance it was run on. For production instances, always apply any changes to a recent clone to ensure an expected outcome.

  • Naveen Tuesday, January 22, 2013

    Excellent article !



  • Vikram Singh Tuesday, February 5, 2013

    Great Article Sir.

    It refreshed everything.


  • Salam Hussain Sunday, June 14, 2015

    Hello Vijay/All,

    BPM in general and workflows in particular are becoming increasingly critical to modern business automations across all industry sectors. With that in mind I am not sure or convinced that the embedded Oracle Workflow in EBS with its 10+ years old technology is sustainable. For example, the lack of a suitable Business Rules Engine in EBS W/F is causing us so much grief as we cannot apply granular decision logic to our workflows and end up with very complex and high maintenance W/F code.

    Oracle BPM is already supporting EBS natively and it should also be the other way round, ie- embedded BPM with EBS, albeit a lighter version.

  • guest Tuesday, July 14, 2015

    Currently we are using oracle workflow builder (version 9i). Have few queries regarding this.

    1) Necessary requirements to monitor the workflow using wf_monitor.get_url.

    2) How to configure wf_web_agent in wf_resources table.

Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.