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
