The Workflow Definitions Loader is called WFLOAD and can be found in: $FND_TOP/bin
By default it can be used the following ways.
To upload: WFLOAD apps/pwd 0 Y UPLOAD file.wft
To force: WFLOAD apps/pwd 0 Y FORCE file.wft
To download: WFLOAD apps/pwd 0 Y DOWNLOAD file.wft ITEMTYPE1 [ITEMTYPE2...ITEMTYPEn]
To upgrade: WFLOAD apps/pwd 0 Y UPGRADE file.wft
You can use a concurrent program to load process definitions. Run Workflow Definitions Loader concurrent program.
The products listed below leverage Oracle Workflow for business process definition and integration.
Oracle Warehouse Builder
Oracle Warehouse Builder includes a Workflow Deployment Wizard that lets you deploy extract, transform, and load mappings to Oracle Workflow as functions within an item type. You can then use Oracle Workflow Builder to define the sequence of these functions as a workflow process. In designing the process, you can specify job dependencies between the mappings to ensure that jobs run in the proper order. You can then run the process from Oracle Workflow or schedule the process to run using Oracle Enterprise Manager.
Oracle Application Server InterConnect
The Oracle Workflow Business Event System enables Oracle Application Server InterConnect and Oracle Workflow to work together to provide a complete business process driven integration solution. With Oracle Application Server InterConnect and Oracle Workflow, you can define business collaborations across two or more applications to implement the business processes for an organization.
The Oracle Application Server InterConnect iStudio design tool automatically generates Oracle Workflow business event and subscription definitions corresponding to common view events and procedures. You can launch the Oracle Workflow home page from iStudio to review these definitions. The iStudio tool also deploys process bundles as Oracle Workflow item type definitions. These item types include starter workflow processes with Oracle Workflow event activities that correspond to Publish, Subscribe, Invoke, and Implement activities defined in iStudio. You can then launch Oracle Workflow Builder from iStudio to complete the workflow process definition by specifying the sequence of the event activities and optionally adding other activities such as notifications or functions.
For example, iStudio might generate a workflow process with two event activities, one that receives a CreatePO event and another that sends an AcceptPO event. You can then use Oracle Workflow Builder to define the business process that controls the execution of these activities. For instance, add a notification activity to send an e-mail requesting approval after the CreatePO event is received and before the AcceptPO is event is sent.
At runtime, Oracle Application Server InterConnect and Oracle Workflow communicate with each other through the Oracle Workflow Business Event System, leveraging the Oracle Advanced Queuing messaging infrastructure, to execute business processes defined across multiple applications.
Showing posts with label Workflow. Show all posts
Showing posts with label Workflow. Show all posts
Monday, November 9, 2009
Sunday, November 8, 2009
Oracle Workflow and Workflow Components
Oracle Workflow
Workflow is a business management system that automates and streamlines business process. Within and between enterprises, oracle workflow supports complete business process integration. Enables modeling, automation. Enables routing information of any type according to user defined business rules.Workflow Process
Every Business process is represented as a workflow process. Each workflow process in turn consists of a sequences of activities. Activities Includes business events such as raising PO, includes functions such as updating requisitions details and notifications such as e-mail to manager for approval. Sequence of such activities are represented in a Workflow process to achieve a business requirement.
Sample Workflow Process
Oracle Workflow is available in Two Versions:
- Standalone version
- Embedded version
1. A standalone version of Oracle Workflow is available with the Oracle database and Oracle9i Application Server.
2. Oracle Workflow is embedded in the Oracle E-Business Suite to enforce a common set of business rules.
3. Oracle Workflow Embedded version is incorporated in applications including Enterprise Resource Planning (ERP), Customer Relationship Management (CRM), and Human Resources Management Systems (HRMS).
4. Oracle Workflow Embedded version is leveraged by both professional applications (which are typically Forms-based applications for power users)
5. Self-service applications (which are typically HTML-based applications i expenses for expense reports processing)
6. Our discussion is confined to embedded workflow. But the concepts we discuss hold good for Standalone workflow version also.
Processing of event based workflow
On occurrence of event (such as submission of invoice for approval) Application Modules Raises invoice approval event and passes it to BES. BES triggers event subscriptions using rule functions. These event subscription in turn launches workflow process.
Oracle Workflow Architecture
Oracle workflow grouped into four parts
- Workflow Development Client
- Oracle Server
- Application Server
- End-User Client
Workflow Development Client: The development client is a PC running Windows 95, Windows 98, Windows 2000, or Windows NT 4.0 or higher. This platform is used to create and modify Oracle Workflow process definitions.
Development tool/utilities used by workflow developers to define workflow process are
-Workflow Builder
-Workflow Definitions Loader
-Workflow XML Loader
Oracle Server: The Oracle Server platform is the Oracle RDBMS. This platform hosts the business application integrated with Oracle Workflow, the Workflow Engine, Business Event System, Notification System, and directory services.
Components that reside on Oracle Server are
-Workflow Engine
-Notification System
-Directory Services
-Business Event System (for Event Based Workflow)
Application Server: The application server is the environment outside of the RDBMS. This environment includes ancillary services such as the Oracle9i Application Server (Oracle9iAS) as the web server, and the Notification Mailer.
End-User Client: The end-user client is the workstation or PC that an end user uses to perform daily tasks. This client includes browser support for reviewing and responding to notifications in the Notification Worklist, the Oracle Workflow Monitor to view workflow process, as well as mail applications for reviewing and responding to notifications by e-mail.
Components that reside on Client and accessible using browser are
-Notification Worklist
-Workflow Monitor
A process definition is composed of activities and the relationship between them that accomplish workflow process. Workflow process is initiated when an application calls a set of Oracle Workflow Engine APIs. Workflow engine invokes “Start” activity or “Receive” Event of a Workflow Process.
1.Each workflow process is identified by unique Item Type at database level(such as Payables Invoice Approval Workflow Item type is APINV).
2.Each workflow process is saved in a single flat file. Payables Invoice Approval Workflow process definition is stored in apfiawie.wft flat file.
3.After opening the workflow process definition in workflow builder. Right click on Item Type (in below picture it is AP Invoice) and select properties.
4.This displays Item type internal name and display name.
5.Workflow Process consists of Process Activities (In this slide we can note two process ‘Invoice Approval - Main and Send Notifications)
Process Activity
Most important activity in workflow process is a process activity. Process activity represents a collection of other activities (Function, Event, Notification). Icons/Nodes represents activities and Arrow corresponds to transition from one activity to other. Process Diagram displays Process activity. In this diagram we can see Invoice Approval – Main process activity comprising “Receive Invoice”, “Check if matched to PO”, “Send Notifications” etc.,
Most important activity in workflow process is a process activity. Process activity represents a collection of other activities (Function, Event, Notification). Icons/Nodes represents activities and Arrow corresponds to transition from one activity to other. Process Diagram displays Process activity. In this diagram we can see Invoice Approval – Main process activity comprising “Receive Invoice”, “Check if matched to PO”, “Send Notifications” etc.,
A function activity calls a PL/SQL stored procedure or some external program to perform an automated function in process activity. Select Activity Icon from process diagram. Right click on it and select properties. Check the first tab page to identify the activity type. Here it is a “Function” activity.
An event activity can either Receive, Raise, or Send a business event. This can be noted from “Event Action” field. We can select Icon using “Browse” button. Event Activity retrieves the event name, event key, and event data as specified in the event details (tab page). The event details can be dynamically determined at runtime.
-A Receive event activity can be marked as a Start activity for a process, meaning it is always enabled to receive events. Alternatively, a Receive event activity can be placed within the process, so that it is only enabled to receive events
-A Raise event activity retrieves information about the event and raises the event to the Business Event System, which will then execute subscriptions to the event.
-A Send event activity retrieves the event name, event key, event message, outbound agent, and inbound agent, as specified in the node’s event details.
When the workflow engine reaches a notification activity, it issues a Send( ) API call to the Notification System to send the message to an assigned performer. In this notification activity, Message being sent can be found in the Message field. This field holds the message content name. (In below picture Message content is Identified by name “Request Approver”). When a performer responds to a notification activity, the Notification System processes the response and informs the workflow engine that the notification activity is complete so that it can continue processing the next eligible activity.
In Notification Activity, you specify the performer (I.e. receiver) of a notification in “Node” tab page in Performer section. You can either designate the performer to be a specific role or an type attribute that dynamically returns the name of a role.
Attributes Acts as a global variable that can be referenced or updated by any activity within a process. Applications packages can reference and set item type attributes using the Oracle Workflow Engine APIs during runtime of workflow process. Attributes provide information that will need in a notification message. Can Right Click on Attribute in navigation Tree and select Properties. This displays internal name and type.
Wfstatus.sql
Wfstatus.sql is provided along with workflow product or oracle application. We can find it in $fnd_top/sql folder. We need to run this script from sql*plus. Complete list of activities executed for workflow process instance are displayed. Spooling the result to text file makes it easy for customer to send details of workflow process instance to support.
wfstatus.Sql script execution:
- Change to the $FND_TOP/sql directory
- Connect to sqlplus as apps
- spool
- Run the following command
@wfstatus APINV 57936_1 (Input parameters are Item_type and Item_key)
- spool off
- Open to view details of workflow Item
This is the output report of wfstatus.sql
Wfstatus.sql is provided along with workflow product or oracle application. We can find it in $fnd_top/sql folder. We need to run this script from sql*plus. Complete list of activities executed for workflow process instance are displayed. Spooling the result to text file makes it easy for customer to send details of workflow process instance to support.
wfstatus.Sql script execution:
- Change to the $FND_TOP/sql directory
- Connect to sqlplus as apps
- spool
- Run the following command
@wfstatus APINV 57936_1 (Input parameters are Item_type and Item_key)
- spool off
- Open
This is the output report of wfstatus.sql
Workflow Item section consists of Process Instance details. One record exists for combination of Item Type and Item Key. If no record is selected means workflow process is not launched and other sections of report will not have any information. Please note correct Item Type and Item Key needs to provided. Otherwise we will not get any data in workflow Item section.
Activity Statuses Section provides Activities executed in Activity column. Generally value in this column has two parts separated by forward slash “/”. First Part indicates the process activity and Second part indicates activity within that process activity. In this example ‘Invoice Approval Main” is the Process activity and “Check if matched to PO” is the activity within that process.
Status Column Provides the status of activity.
Activity Statuses Section provides Activities executed in Activity column. Generally value in this column has two parts separated by forward slash “/”. First Part indicates the process activity and Second part indicates activity within that process activity. In this example ‘Invoice Approval Main” is the Process activity and “Check if matched to PO” is the activity within that process.
Status Column Provides the status of activity.
Result column provides Return value on completion of that activity.
Errored Activities section provide details of activities that got Errored while executing workflow process.
Attribute Values provide values of variables that are being used while executing workflow process.
Attribute Values provide values of variables that are being used while executing workflow process.
Thursday, November 5, 2009
Predefined Workflows Embedded in Oracle Apps-Financials
Oracle General Ledger
Journal Approval Process--Journals can now be approved before posting. Create an approval hierarchy and define authorization limits for each user. The Journal Approval process automatically routes journals to the appropriate user, based on the approval hierarchy.
Step-Down AutoAllocations Process--Initiates the GL Allocation process and directs batches to the GL Mass Allocation process or the GL Recurring Journals process. These processes validate batches and determine if approvals are required for a batch, submit the batch(s) to approvers if required, then notify individuals of the approval results. If errors occur, the contact or responsibility can choose to rollback the Step-Down AutoAllocation process which reverses any posted journals.
Global InterCompany System--The Global Intercompany System (formerly CENTRA) is an enhanced feature for Release 11i. It provides an environment within which multiple companies can exchange intercompany transactions. When a sender company initiates an intercompany transaction, the workflow process notifies the receiver company of the transaction. The workflow process notifies the sender company if the receiver company approves or rejects the transaction. In addition, a threshold amount can be set to limit the volume of notifications or to notify approvers of only large transactions.
Oracle Payables
AP Open Interface Import Process--Automates verification and validation of data in the Open Interface tables. For example, this process can be modified to validate all accounting code combinations in the Open Interface tables. Notification of any invalid code combinations can be sent to a specified user for correction. Optionally the process can be set up to override any invalid code combinations with a designated default value. You can use Oracle Workflow to include additional workflow rules that meet the specific requirements of a business. Once an invoice has passed this process it is ready to be imported into the Oracle Payables application tables.
Credit Card Transaction Employee Process--Notifies and confirms credit card transactions with a card holder. Oracle Payables initiates this process after you submit the Credit Card Transaction Validation and Exception Report. The process notifies an employee of transactions created by the employee's credit card, and confirms the transaction information with the employee.
Credit Card Transaction Manager Process--Notifies and confirms credit card transactions with a card holder's manager. Oracle Payables initiates this process when the Credit Card Transaction Employee workflow process executes. The Credit Card Transaction Manager workflow process notifies a manager of transactions created by the employee's credit card, and determines if the manager needs to approve the transactions.
Expense Reporting Process--Oracle Payables uses the Expense Reporting workflow process to process the manager approval and accounting review of expense reports entered in Self-Service Expenses. The Expense Reporting process begins when a user submits an expense report, and finishes when an expense report is rejected or approved. If approved, the Expense Reporting process makes the expense report available for the Payables Invoice Import process. The Expense Report process notifies employees at key event points during the manager approval and accounting review process.
Oracle Projects
Project Approval and Status Change Process--Routes a project and notifies appropriate users of any project status change. For example, you can submit the project for approval, or notify appropriate people upon project closure. You select which workflow to use for the appropriate status change, as well as determining the person(s) to route the project to.
Budget Approval Process--Routes a project budget for approval and baseline. You select which workflow to use for the budget type, as well as determining the person(s) to route the budget to.
Oracle Purchasing
Procurement Workflow--The Procurement Workflow is a lights-out, hands-off transaction processing system that is truly flexible and extensible to all members of your supply chain. It is one of the key enablers in the shift towards more strategic sourcing and procurement activities. It consists of the Document Approval, Automatic Document Creation, Change Orders, Account Generation, Send Notifications, Price/Sales Catalog Notification, and Receipt Confirmation (used only by Self-Service Purchasing) workflow processes.
Document Approval Process--Performs all approval related activities in Oracle Purchasing. These include, but are not limited to, document submission, approval, forwarding, approval notifications, and rejection. This includes the PO Approval workflow process for approving purchase orders and the PO Requisition Approval workflow process for approving requisitions.
Automatic Document Creation Process--Automatically creates standard purchase orders or releases against blanket agreements using approved purchase requisition lines, if the requisition lines have the required sourcing information. This process is also known as the PO Create Documents workflow.
Change Orders Process--Allows you to control which changes require a manual reapproval and which will be automatically reapproved. All reapproved documents, either manual or automatic, will result in the document revision being incremented. This process is part of the PO Approval workflow.
Send Notifications Process--Looks for documents that are incomplete, rejected, or in need of reapproval, and sends notifications regarding the document's status to the appropriate people. This is also known as the PO Send Notifications for Purchasing Documents workflow.
Price/Sales Catalog Notification Process--Sends a notification to the buyer when the price/sales catalog information sent through the Purchasing Documents Open Interface includes price increases that exceed a price tolerance that you set. This process is also known as the PO Catalog Price Tolerance Exceeded Notifications workflow.
Oracle Receivables
Credit Memo Request Approval Process - Routes a credit memo request for approval using an organization's internal management hierarchy or approval limits defined in Oracle Receivables. If the request is approved, a credit memo is created in Oracle Receivables. Otherwise, the process notifies the requestor with an explanation of why it was rejected.
More Info=>http://www.cs.otago.ac.nz/oradocs/ois.817/a85440/wf/embed.htm
Journal Approval Process--Journals can now be approved before posting. Create an approval hierarchy and define authorization limits for each user. The Journal Approval process automatically routes journals to the appropriate user, based on the approval hierarchy.
Step-Down AutoAllocations Process--Initiates the GL Allocation process and directs batches to the GL Mass Allocation process or the GL Recurring Journals process. These processes validate batches and determine if approvals are required for a batch, submit the batch(s) to approvers if required, then notify individuals of the approval results. If errors occur, the contact or responsibility can choose to rollback the Step-Down AutoAllocation process which reverses any posted journals.
Global InterCompany System--The Global Intercompany System (formerly CENTRA) is an enhanced feature for Release 11i. It provides an environment within which multiple companies can exchange intercompany transactions. When a sender company initiates an intercompany transaction, the workflow process notifies the receiver company of the transaction. The workflow process notifies the sender company if the receiver company approves or rejects the transaction. In addition, a threshold amount can be set to limit the volume of notifications or to notify approvers of only large transactions.
Oracle Payables
AP Open Interface Import Process--Automates verification and validation of data in the Open Interface tables. For example, this process can be modified to validate all accounting code combinations in the Open Interface tables. Notification of any invalid code combinations can be sent to a specified user for correction. Optionally the process can be set up to override any invalid code combinations with a designated default value. You can use Oracle Workflow to include additional workflow rules that meet the specific requirements of a business. Once an invoice has passed this process it is ready to be imported into the Oracle Payables application tables.
Credit Card Transaction Employee Process--Notifies and confirms credit card transactions with a card holder. Oracle Payables initiates this process after you submit the Credit Card Transaction Validation and Exception Report. The process notifies an employee of transactions created by the employee's credit card, and confirms the transaction information with the employee.
Credit Card Transaction Manager Process--Notifies and confirms credit card transactions with a card holder's manager. Oracle Payables initiates this process when the Credit Card Transaction Employee workflow process executes. The Credit Card Transaction Manager workflow process notifies a manager of transactions created by the employee's credit card, and determines if the manager needs to approve the transactions.
Expense Reporting Process--Oracle Payables uses the Expense Reporting workflow process to process the manager approval and accounting review of expense reports entered in Self-Service Expenses. The Expense Reporting process begins when a user submits an expense report, and finishes when an expense report is rejected or approved. If approved, the Expense Reporting process makes the expense report available for the Payables Invoice Import process. The Expense Report process notifies employees at key event points during the manager approval and accounting review process.
Oracle Projects
Project Approval and Status Change Process--Routes a project and notifies appropriate users of any project status change. For example, you can submit the project for approval, or notify appropriate people upon project closure. You select which workflow to use for the appropriate status change, as well as determining the person(s) to route the project to.
Budget Approval Process--Routes a project budget for approval and baseline. You select which workflow to use for the budget type, as well as determining the person(s) to route the budget to.
Oracle Purchasing
Procurement Workflow--The Procurement Workflow is a lights-out, hands-off transaction processing system that is truly flexible and extensible to all members of your supply chain. It is one of the key enablers in the shift towards more strategic sourcing and procurement activities. It consists of the Document Approval, Automatic Document Creation, Change Orders, Account Generation, Send Notifications, Price/Sales Catalog Notification, and Receipt Confirmation (used only by Self-Service Purchasing) workflow processes.
Document Approval Process--Performs all approval related activities in Oracle Purchasing. These include, but are not limited to, document submission, approval, forwarding, approval notifications, and rejection. This includes the PO Approval workflow process for approving purchase orders and the PO Requisition Approval workflow process for approving requisitions.
Automatic Document Creation Process--Automatically creates standard purchase orders or releases against blanket agreements using approved purchase requisition lines, if the requisition lines have the required sourcing information. This process is also known as the PO Create Documents workflow.
Change Orders Process--Allows you to control which changes require a manual reapproval and which will be automatically reapproved. All reapproved documents, either manual or automatic, will result in the document revision being incremented. This process is part of the PO Approval workflow.
Send Notifications Process--Looks for documents that are incomplete, rejected, or in need of reapproval, and sends notifications regarding the document's status to the appropriate people. This is also known as the PO Send Notifications for Purchasing Documents workflow.
Price/Sales Catalog Notification Process--Sends a notification to the buyer when the price/sales catalog information sent through the Purchasing Documents Open Interface includes price increases that exceed a price tolerance that you set. This process is also known as the PO Catalog Price Tolerance Exceeded Notifications workflow.
Oracle Receivables
Credit Memo Request Approval Process - Routes a credit memo request for approval using an organization's internal management hierarchy or approval limits defined in Oracle Receivables. If the request is approved, a credit memo is created in Oracle Receivables. Otherwise, the process notifies the requestor with an explanation of why it was rejected.
More Info=>http://www.cs.otago.ac.nz/oradocs/ois.817/a85440/wf/embed.htm
Subscribe to:
Posts (Atom)
