Oracleâ Order Management

Using Oracle Workflow in Oracle Order Management

Release 11i

August 2002 Part No. A96689-01

Using Oracle Workflow in Oracle Order Management, Release 11i Part No. A96689-01 Copyright © 2002, Oracle Corporation. All rights reserved. Primary Author: Jennifer Covert Mosinski

Contributing Authors: James Siri, Samuel Wong, Zeeshan Butt, Ginger Conroy, Linda Henry, Valerie Dubois, Leena Sampemane, and Usha Arora Contributors: Chris Swalve, Sumeet Rijhsinghani, Joshua Gould, Tony Maxey, Elizabeth Looney, Ari Aaltonen, Renga Kannan, Jyothi Narayan, Manish Chavan, Sandra Finley, Brian Hall, Laurent Frillandini, Menno Vlietrtra, Vijay Ramalingam, and Jeffrey Ruddell The Programs (which include both the software and documentation) contain proprietary information of Oracle Corporation; they are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright, patent and other intellectual and industrial property laws. Reverse engineering, disassembly or decompilation of the Programs, except to the extent required to obtain interoperability with other independently created software or as specified by law, is prohibited. The information contained in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. Oracle Corporation does not warrant that this document is error-free. Except as may be expressly permitted in your license agreement for these Programs, no part of these Programs may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of Oracle Corporation. If the Programs are delivered to the U.S. Government or anyone licensing or using the programs on behalf of the U.S. Government, the following notice is applicable: Restricted Rights Notice: Programs delivered subject to the DOD FAR Supplement are “commercial computer software” and use, duplication and disclosure of the Programs including documentation, shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement. Otherwise, Programs delivered subject to the Federal Acquisition Regulations are “restricted computer software” and use, duplication and disclosure of the Programs shall be subject to the restrictions in FAR 52.227-19, Commercial Computer Software - Restricted Rights (June, 1987). Oracle Corporation, 500 Oracle Parkway, Redwood City, CA 94065. The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently dangerous applications. It shall be licensee's responsibility to take all appropriate fail-safe, back up, redundancy and other measures to ensure the safe use of such applications if the Programs are used for such purposes, and Oracle disclaims liability for any damages caused by such use of the Programs. Oracle is a registered trademark, and OracleMetaLink, PL/SQL, are trademarks or registered trademarks of Oracle Corporation. Other names may be trademarks of their respective owners.

Contents
Send Us Your Comments ................................................................................................................... ix Preface.............................................................................................................................................................. i
Audience for This Manual ..................................................................................................................... i How To Use This Manual....................................................................................................................... i Documentation Accessibility .......................................................................................................... ii Other Information Sources ................................................................................................................... iii Online Documentation..................................................................................................................... iii Related User’s Guides...................................................................................................................... iii Guides Related to All Products ..................................................................................................... iv User Guides Related to This Product ........................................................................................... iv Installation and System Administration ...................................................................................... vi Other Implementation Documentation....................................................................................... vii Training and Support...................................................................................................................... ix Do Not Use Database Tools to Modify Oracle Applications Data............................................... ix About Oracle............................................................................................................................................ x Your Feedback ......................................................................................................................................... x

1

Introduction
Using Oracle Workflow in Oracle Order Management .............................................................. Setting Up Oracle Workflow in Oracle Order Management...................................................... Viewing Processes in Oracle Workflow Builder .......................................................................... Viewing Workflows in Oracle Order Management ..................................................................... Seeded Data Files................................................................................................................................ 1-2 1-2 1-3 1-4 1-6

iii

Seeded Data File oexwford.wft................................................................................................... Seeded Data File ctochord.wft .................................................................................................... Item Types ............................................................................................................................................ OM Change Order ...................................................................................................................... OM Order Header....................................................................................................................... OM Order Line............................................................................................................................ OM Standard ............................................................................................................................... CTO Change Order.....................................................................................................................

1-7 1-9 1-9 1-10 1-10 1-12 1-14 1-16

2 Processing Orders Using Oracle Workflow
Selecting Workflows .......................................................................................................................... Header Level Processes................................................................................................................ Line Level Processes..................................................................................................................... Assigning Workflows to Transaction Types .................................................................................. Line Workflow Assignments ...................................................................................................... Workflow Background Engine Processing .................................................................................... Scheduling Workflows .................................................................................................................... Repricing Order Lines...................................................................................................................... 2-2 2-3 2-3 2-7 2-8 2-9 2-10 2-11

3 Extending Oracle Order Management Seeded Workflows
Overview .............................................................................................................................................. Customizations.................................................................................................................................... Exceptions ...................................................................................................................................... Extending Workflow .......................................................................................................................... Dependencies ................................................................................................................................ Guidelines ...................................................................................................................................... Examples of Extending Workflow ............................................................................................. 3-2 3-2 3-3 3-3 3-4 3-5 3-6

4

Seeded Workflow Definitions
CTO Change Order Process .............................................................................................................. Notification for Change Order.................................................................................................... OM Change Order Processes ............................................................................................................ Change Order Process.................................................................................................................. OM Order Header Processes............................................................................................................. 4-2 4-2 4-4 4-4 4-5

iv

Order Flow - Generic ................................................................................................................... Order Flow - Generic with Header Level Invoice Interface ................................................... Order Flow - Return with Approval.......................................................................................... OM Order Line.................................................................................................................................. Line Flow - ATO Item ................................................................................................................ Line Flow - ATO Model............................................................................................................. Line Flow - Configuration ......................................................................................................... Line Flow - Configuration with Authorize to Ship (RLM)................................................... Line Flow - Generic .................................................................................................................... Line Flow - Generic with Authorize to Ship (RLM) .............................................................. Line Flow - Generic with Header Level Invoice Interface.................................................... Line Flow - Generic, With Export Compliance ...................................................................... Line Flow - Generic, Bill Only .................................................................................................. Line Flow - Generic, Bill Only with Inventory Interface ...................................................... Line Flow - Generic, Ship Only ................................................................................................ Line Flow - Generic, with Repricing at Fulfillment............................................................... Line Flow - Return for Credit Only.......................................................................................... Line Flow - Return for Credit Only with Approval .............................................................. Line Flow - Return for Credit with Receipt ............................................................................ Line Flow - Return for Credit with Receipt and Approval .................................................. Line Flow - Standard Service ....................................................................................................

4-6 4-7 4-9 4-11 4-12 4-14 4-16 4-19 4-21 4-24 4-26 4-28 4-31 4-33 4-35 4-37 4-40 4-41 4-44 4-46 4-48

5

Seeded Subprocess Definitions
OM Order Header Subprocesses ..................................................................................................... Approve Return - Order .............................................................................................................. Book - Order, Deferred ................................................................................................................ Book - Order, Manual .................................................................................................................. Close - Order ................................................................................................................................. Header Level Invoice Interface - Order................................................................................... OM Order Line Subprocesses ........................................................................................................ Authorized to Ship - Line .......................................................................................................... Buy ATO Item Flow ................................................................................................................... Calculate Lead Time - Line ....................................................................................................... Close - Line .................................................................................................................................. Create ATO Supply .................................................................................................................... 5-2 5-2 5-4 5-6 5-8 5-10 5-12 5-12 5-14 5-16 5-18 5-21

v

....................................Line............................................................................................................................................................................... B-2 Errors Viewing Workflow Status From Within Oracle Order Management . Purchase Release ......Line. Deferred ........ OM Standard ......................................................... Deferred ..............................Line....................................................Line..................................... B-2 Repricing Errors ........................................................ Create Supply .............Line .................................................. Standard...................Line................................................................................. Manual........................... Purchase Release .................ATO .................................................................................................... Ship .............. OM Order Line .......................................................... Schedule ...Line.......................................................................................................................................................................................................... 5-23 5-26 5-28 5-32 5-34 5-36 5-39 5-41 5-43 5-46 5-49 5-51 5-54 5-56 5-59 5-61 5-63 5-65 5-67 5-69 6 Seeded Function Activity Definitions OM Order Header .................................................. A-2 B Troubleshooting Expected Errors ..............Line.................................................................Line............................................................ Manual . Return Receiving ...Line.................................................................................................................................................... Reprice ............................................... Schedule ................................................................................................... Export Compliance Screening ................................................................................................................................................................................................ Deferred .............Line..Line......... Inventory Interface Non-Ship ....................................................................Create Configuration ........................... Manual ................................ Invoice Interface ................ Deferred .............................. Inventory Interface Non-Ship ...................................................................................... Deferred............Line ............................................................................Line................... Manual............................................................................................................Line........................................................Line ............................................................................................... Header Level Invoice Interface .........................................................................................................Line............................................ Enter ................................ Deferred ....................... Create Manufacturing Configuration Data ............. Manual ........................ B-3 vi .................................................... Create Supply Order ....................................... 6-2 6-9 6-45 6-46 A Windows and Navigator Paths Windows and Navigator Paths .......................Line .........Line................................................................................................................. Purchase Release ...... Create Work Order .....Line...................... Invoice Interface ...........

................................Unexpected Errors..... B-3 Glossary Index vii ...........................................................................................

viii .

Your input is an important part of the information used for revision.Send Us Your Comments Using Oracle Workflow in Oracle Order Management.com Please indicate whether you would like a reply. where? Are the examples correct? Do you need more examples? What features did you like most? If you find any errors or have any other suggestions for improvement. and page number (if available). please indicate the document title and part number. Release 11i Part No. please contact your local Oracle Support Services. section. If you have problems with the software. A96689-01 Oracle Corporation welcomes your comments and suggestions on the quality and usefulness of this document. and the chapter. ix . You can send comments to us at the following e-mail address: mfgdoccomments_us@oracle. ■ ■ ■ ■ ■ Did you find any errors? Is the information clearly presented? Do you need more information? If so.

x .

See Other Information Sources for more information about Oracle Applications products. ■ Chapter 1 of this manual provides an introduction about how Oracle Workflow is implemented and used in Oracle Order Management. i . How To Use This Manual This guide contains the information you need to understand and use Oracle Order Management and Oracle Workflow. ■ ■ ■ The Oracle Applications graphical user interface. read the Oracle Applications User’s Guide. To learn more about the Oracle Applications graphical user interface.Preface Audience for This Manual Welcome to Oracle Applications Release 11i of Using Oracle Workflow in Oracle Order Management. Oracle suggests you attend one or more of the Oracle Order Management or Oracle Workflow training classes available through Oracle University. This guide assumes you have a working knowledge of the following: ■ The principles and customary practices of your business area Oracle Order Management Oracle Workflow If you have never used Oracle Order Management or Oracle Workflow.

with good usability. however. Chapter 3 explains how to extend the seeded processes. Accessibility of Code Examples in Documentation JAWS. and supporting documentation accessible. ■ ■ ■ ■ ■ Documentation Accessibility Our goal is to make Oracle products. ii .■ Chapter 2 discusses how orders in Oracle Order Management are processed using Oracle Workflow. services. and Oracle Corporation is actively engaged with other market-leading technology vendors to address technical obstacles so that our documentation can be accessible to all of our customers.com/accessibility/. To that end. and activities to meet your business needs. Appendix A of this manual addresses troubleshooting for expected and unexpected errors. our documentation includes features that make information available to users of assistive technology. subprocesses. Oracle Corporation neither evaluates nor makes any representations regarding the accessibility of these Web sites. Chapter 6 defines and details the workflow function activities used in Oracle Order Management. may not always correctly read the code examples in this document. This documentation is available in HTML format. visit the Oracle Accessibility Program Web site at http://www. The conventions for writing code require that closing braces should appear on an otherwise empty line. For additional information. Accessibility of Links to External Web Sites in Documentation This documentation may contain links to Web sites of other companies or organizations that Oracle Corporation does not own or control. a Windows screen reader. Chapter 4 defines and details the workflow processes used in Oracle Order Management. Standards will continue to evolve over time. JAWS may not always read a line of text that consists solely of a bracket or brace.oracle. and contains markup to facilitate access by the disabled community. to the disabled community. Chapter 5 defines and details the workflow subprocess used in Oracle Order Management.

The new features section also includes information about any features that were not yet available when this guide was printed.Other Information Sources You can choose from many sources of information. and support services. including online documentation. Oracle Applications Release 11i Features Matrix . to increase your knowledge and understanding of Oracle Order Management and Oracle Workflow If this guide refers you to other Oracle Applications documentation. use only the Oracle Applications Release 11i versions of those guides. training.The new features section in the HTML help describes new features in Oracle Applications Release 11i. iii .This document lists new features available by patch and identifies any associated new documentation. The new features matrix document is available on OracleMetaLink. by reading from the Oracle Applications Document Library CD included in your media pack. You can read the guides online by choosing Library from the expandable menu on your HTML help window. or by using a Web browser with a URL that your system administrator provides. you can purchase them from the Oracle Store at http://oraclestore. Online help patches are available on OracleMetaLink.com. if your administrator has installed software from a mini-packs an upgrade. you may want to refer to other user’s guides when you set up and use Oracle Order Management or Oracle Workflow. ■ ■ Related User’s Guides Oracle Order Management and Oracle Workflow share business and setup information with other Oracle Applications products. If you require printed guides.oracle.Refer to the readme file for patches that you have installed to learn about new documentation or documentation patches that you can download. Readme File . Therefore. ■ Online Help . Online Documentation All Oracle Applications documentation is available online (HTML or PDF). For example. This information is updated for each new release of Oracle Order Management and Oracle Workflow. this document describes the new features.

query. as well as running and reviewing reports and concurrent processes.Guides Related to All Products Oracle Applications User’s Guide This guide explains how to enter data. and resources. you can create forecasts. Using a variety of tools and techniques. This guide also includes information on setting user profiles. and plan your end-items and their component requirements. Oracle Inventory User’s Guide This guide describes how to define items and item information. load these forecasts into master production schedules. price lists. and how to price special orders in Oracle Advanced Pricing. and set up Oracle Inventory. User Guides Related to This Product Oracle Advanced Pricing User’s Guide This guide describes how to set up modifiers. operations. releasing and rescheduling planning suggestions for discrete jobs and repetitive schedules. iv . You can also execute the plan. plan items. perform receiving and inventory transactions. You can access this user’s guide online by selecting Getting Started with Oracle Applications from any Oracle Applications help file. maintain cost control. Oracle Master Scheduling/MRP and Oracle Advanced Supply Chain Planning User’s Guide This guide describes how to anticipate and manage both supply and demand for your items. and navigate using the graphical user interface (GUI) available with this release of Oracle Order Management and Oracle Workflow (and any other Oracle Applications products). This guide also details how to use the drag and drop functionality to view and reschedule jobs. pricing agreements. pricing rules. formulas. run reports. perform cycle counting and physical inventories. Oracle Manufacturing Scheduling User’s Guide This guide describes how to use Oracle Manufacturing Scheduling to view and reschedule single discrete jobs or the entire shop floor.

it enables you to electronically collaborate with your customers to more accurately manage demand. Oracle Shipping Execution User’s Guide This guide describes how to set up Oracle Shipping Execution to process and plan your trips. and create reports. invoices. By explaining how to validate. You can use flexible address formats in the suppliers. copy existing sales orders. schedule orders. archive. create price lists. ship confirmation. Oracle Release Management User's Guide This manual describes how to manage high volume electronic demand by continually incorporating your customers demand into your order and planning processes. assemble-to-order. flow. Specifically this guide describes how discrete. It also describes how to plan. manage and reconcile incoming planning. query shipments. and mixed manufacturing environments are supported. repetitive.You also use v . and payments windows. project. determine freight cost and charges to meet your business needs. create and manage trading partner layers for trading partner specific customizations. release orders. Oracle Receivables User’s Guide Use this manual to learn how to implement flexible address formats for different countries. and discounts for orders. Oracle Work in Process User’s Guide This guide describes how Oracle Work in Process provides a complete production management system. run processes. stops and deliveries. Oracle Workflow Guide This guide explains how to define new workflow business processes as well as customize existing Oracle Applications-embedded workflow processes.Oracle Order Management User’s Guide This guide describes how to enter sales orders and returns. Oracle Supplier Scheduling User’s Guide This guide describes how you can use Oracle Supplier Scheduling to calculate and maintain planning and shipping schedules and communicate them to your suppliers. banks. shipping and production sequence schedules with updates to sales orders and forecasts.

7. and other information that you need to run the AD utilities. the Oracle8 technology stack.7 or Oracle Applications Release 11. AutoPatch.0.0 products to Oracle Applications Release 11i. and Self-Service Web Applications. Installing Oracle Applications This guide provides instructions for managing the installation of Oracle Applications products. vi . This guide contains instructions for using Oracle Rapid Install and lists the tasks you need to perform to finish your installation. which minimizes the time to install Oracle Applications. AD Relink. You should use this guide in conjunction with individual product user’s guides and implementation guides. Upgrading Oracle Applications Refer to this guide if you are upgrading your Oracle Applications Release 10. This guide describes the upgrade process and lists database and product-specific upgrade tasks. much of the installation process is handled using Oracle Rapid Install. You cannot upgrade to Oracle Applications Release 11i directly from releases prior to Oracle Applications Release 10. languages and character sets. It contains how-to steps. In Oracle Applications Release 11i. You must be either at Oracle Applications Release 10. Installation and System Administration Oracle Applications Concepts This guide provides an introduction to the concepts.this guide to complete the setup steps necessary for any Oracle Applications product that includes workflow-enabled processes. AD Administration. and terminology for Oracle Applications Release 11i. License Manager. Maintaining Oracle Applications Use this guide to help you run the various AD utilities. and the Oracle8i Server technology stack by automating many of the required steps. AD Controller. This guide also introduces the concepts behind Applications-wide features such as Business Intelligence (BIS). This guide also provides information on maintaining the Oracle applications file system and database. architecture. features. and others. or character mode) or Oracle Applications Release 11. to upgrade to Oracle Applications Release 11i. screenshots. technology stack. SmartClient. such as AutoUpgrade.7 (NCA. It provides a useful first book to read before an installation of Oracle Applications.

customize menus and online help. use this manual before implementing Oracle Order Management. enhancements. and manage concurrent processing. It provides a history of the changes to individual Oracle Applications products between Oracle Applications Release 11. Oracle Alert User’s Guide This guide explains how to define periodic and event alerts to monitor the status of your Oracle Applications data. It describes the UI for the Oracle Applications products and how to apply this UI to the design of an application built by using Oracle Forms. and changes made to database objects. It includes new features. Other Implementation Documentation Oracle Applications Product Update Notes Use this guide as a reference for upgrading an installation of Oracle Applications.Oracle Applications System Administrator’s Guide This guide provides planning and reference information for the Oracle Applications System Administrator. profile options. It contains information on how to define security. It describes the Oracle Application Object Library components needed to implement the Oracle Applications user interface described in the Oracle Applications User Interface Standards for Forms-Based Products. Oracle Applications Developer’s Guide This guide contains the coding standards followed by the Oracle Applications development staff. It also provides information to help you build your custom Oracle Forms Developer 6i forms so that they integrate with Oracle Applications.0 and Oracle Applications Release 11i. Oracle Applications User Interface Standards for Forms-Based Products This guide contains the user interface (UI) standards followed by the Oracle Applications development staff. This manual details additional steps and setup considerations for implementing Oracle Order Management with this feature. vii . Multiple Reporting Currencies in Oracle Applications If you use the Multiple Reporting Currencies feature to record transactions in more than one currency. and seed data for this interval.

This information helps you convert data from your existing applications. as well as for users responsible for the ongoing maintenance of Oracle Applications product data. This manual also provides information on creating custom reports on flexfields data.Multiple Organizations in Oracle Applications This guide describes how to set up and use Oracle Order Management with Oracle Applications' Multiple Organization support feature. Oracle Configure to Order Implementation Manual This manual explains how to set up Oracle Applications to use the configure to order functionality. Oracle eTechnical Reference Manuals Each eTechnical Reference Manual (eTRM) contains database diagrams and a detailed description of database tables. This documentation includes APIs and open interfaces found in Oracle Manufacturing. This manual is available in HTML format on the documentation CD-ROM for Oracle Applications Release 11i. so you can define and support different organization structures when running a single installation of Oracle Order Management. integrate Oracle Applications data with non-Oracle applications. Oracle Applications Flexfields Guide This guide provides flexfields planning. Oracle Applications Message Reference Manual This manual describes all Oracle Applications messages. Oracle Manufacturing APIs and Open Interfaces Manual This manual contains up-to-date information about integrating with other Oracle Manufacturing applications and with your other systems. forms. Oracle Order Management Suite APIs and Open Interfaces Manual This manual contains up-to-date information about integrating with other Oracle Manufacturing applications and with your other systems. reports. and write custom reports for Oracle Applications products. viii . setup and reference information for the Oracle Order Management implementation team. This documentation includes APIs and open interfaces found in Oracle Order Management Suite. and programs for a specific Oracle Applications product. Oracle eTRM is available on OracleMetaLink.

You can attend courses offered by Oracle University at any one of our many Education Centers. Oracle Data Browser. database triggers. Account Manager. managing an Oracle8i server. Oracle training professionals can tailor standard courses or develop custom courses to meet your needs. store. But if you use Oracle tools such as SQL*Plus to modify Oracle Applications data. you risk destroying the integrity of your data and you lose the ability to audit changes to your data.Training and Support Training Oracle offers a complete set of training courses to help you and your staff master Oracle Order Management and Oracle Workflow and reach full productivity quickly. you may change a row in one table without making corresponding changes in related tables. so you take only those courses appropriate to your job or area of responsibility. If your ix . and your hardware and software environment. or you can use Oracle Learning Network (OLN). and Oracle’s large staff of consultants and support specialists with expertise in your business area. retrieve. But when you modify Oracle Applications data using anything other than Oracle Applications. and data as examples in a customized training session delivered at your own facility. For example. change. This team includes your Technical Representative. In addition. our team of experienced professionals provides the help and information you need to keep Oracle Order Management and Oracle Workflow working for you. You have a choice of educational environments. or any other tool to modify Oracle Applications data unless otherwise instructed. These courses are organized into functional learning paths. Do Not Use Database Tools to Modify Oracle Applications Data Oracle STRONGLY RECOMMENDS that you never use SQL*Plus. and maintain information in an Oracle database. any change you make using Oracle Applications can update many tables at once. Oracle University's online education utility. Because Oracle Applications tables are interrelated. you can arrange for our trainers to teach at your facility. you may want to use your organization structure. terminology. Oracle provides powerful tools you can use to create. Support From on-site support to central support.

an integrated suite of more than 160 software modules for financial management. Your Feedback Thank you for using Oracle Order Management. When you use Oracle Applications to modify your data. as well as Oracle Applications. Oracle Applications automatically checks that your changes are valid. Oracle is the world’s leading supplier of software for information management. and office automation. supply chain management. decision support. You also lose the ability to track who has changed your information because SQL*Plus and other database tools do not keep a record of changes. and support services. different operating systems. you may store invalid information. unified computing and information resource.com Please indicate whether you would like a reply. personal computers. x . minicomputers. project systems. you risk retrieving erroneous information and you risk unpredictable results throughout Oracle Applications. allowing organizations to integrate different computers. education. and applications products. Oracle Applications also keeps track of who changes information. in over 145 countries around the world. Oracle products are available for mainframes. About Oracle Oracle Corporation develops and markets an integrated line of software products for database management. Oracle offers its database. and even different database management systems. and this manual. or this manual. manufacturing. Oracle Workflow. human resources and customer relationship management. along with related consulting. This manual contains a Reader’s Comment Form you can use to explain what you like or dislike about Oracle Order Management. tools. and the world’s second largest software company. You can send your comments via e-mail to the following address: mfgdoccomments_us@oracle. applications development. network computers and personal digital assistants. If you enter information into database tables using database tools. Oracle Workflow.tables get out of synchronization with each other. Oracle values your comments and feedback. different networks. into a single.

1 Introduction This chapter introduces how Oracle Workflow is used in Oracle Order Management. The following topics are addressed: ■ Using Oracle Workflow in Oracle Order Management on page 1-2 Setting Up Oracle Workflow in Oracle Order Management on page 1-2 Viewing Processes in Oracle Workflow Builder on page 1-3 Viewing Workflows in Oracle Order Management on page 1-4 Seeded Data Files on page 1-6 Item Types on page 1-9 ■ ■ ■ ■ ■ Introduction 1-1 .

You may decide to use Oracle Workflow Builder to define new workflow processes. First review all seeded Oracle Order Management workflow data to determine if the seeded flows meet your business requirements. returns. This guide details the requirements for setting up and using Oracle Workflow in Oracle Order Management.Using Oracle Workflow in Oracle Order Management Using Oracle Workflow in Oracle Order Management Oracle Order Management uses Oracle Workflow to control the sequence of events that occurs in the processing of orders. For information regarding implementation and setup of Oracle Workflow. refer to the Oracle Order Management Suite Implementation Manual. the guide explains that an access level of 100 in Oracle Workflow Builder is necessary. and initiates error processes. and explains the setup necessary for all modules. and return lines. detects errors. This guide also provides detailed information regarding the workflow processes that come seeded with Oracle Order Management. You can model your business processes by copying and editing seeded processes or by using seeded and custom activities as components. Oracle Workflow manages activities. maintains completed activity history. order lines. refer to the Oracle Workflow Guide. For information regarding the setup and implementation or Oracle Order Management. you can begin with the basic activities of order processing. For example. Oracle Order Management also uses Oracle Workflow to enable you to track the history of orders. Oracle Order Management enables you to model your business processes in terms of generic order processes. Do not change this access level. 1-2 Using Oracle Workflow in Oracle Order Management . This guide provides details about how to extend Oracle Workflow in Oracle Order Management to best meet your business needs. Setting Up Oracle Workflow in Oracle Order Management There are certain setup requirements to complete before using Oracle Workflow with Oracle Order Management. When defining a new workflow. The Oracle Workflow Guide provides a list of setup steps for Oracle Workflow. sends notifications. Warning: Oracle Corporation does not provide support if the access level of 100 is changed. executes functions.

then select the item type branch within that data source. Within Oracle Workflow Builder. refer to Chapter 3. messages. 2. complete the following steps: 1. notifications. The following image depicts the Oracle Workflow Builder: Introduction 1-3 . 3. Expand the data source. Expand the processes branch within your item type and select a process activity to display the diagram of the process in a Process window. subprocesses. "Extending Oracle Order Management Seeded Workflows".Viewing Processes in Oracle Workflow Builder For more information about extending the seeded Oracle Order Management workflow processes. select Open from the File menu. To view processes in Oracle Workflow Builder. refer to the Oracle Workflow Guide. For more information about setting up Oracle Workflow. and connect to the database. and properties. Viewing Processes in Oracle Workflow Builder From within the Oracle Workflow Builder you can view the different workflow processes discussed in this manual and their associated functions.

and properties. These processes must be in an active running state and also associated with a sales order or sales order line in order to view them. 2. Open the desired order in Oracle Order Management. To view processes for specific orders within Oracle Order Management. 1-4 Using Oracle Workflow in Oracle Order Management . Navigate to the Tools menu and select Workflow Status. subprocesses. notifications.Viewing Workflows in Oracle Order Management Viewing Workflows in Oracle Order Management From within Oracle Order Management you can view the active workflow processes discussed in this manual and their associated functions. messages. complete the following steps: 1.

Viewing Workflows in Oracle Order Management 3. A new window opens and displays the workflow status as an activities list. From the Activities List window you can select the order header workflow process or the order line workflow processes associated with the order. Introduction 1-5 . Selecting an order line workflow process opens a new activities list for that process. The following image depicts the Activities List window in Oracle Order Management: 4.

Seeded Data Files 5.wft The following seeded data file comes seeded with Oracle Discrete Manufacturing. The following image depicts the View Diagram window in Oracle Order Management: Seeded Data Files Each of the Oracle Order Management seeded workflows and their associated activities are contained in the following seeded data file: ■ oexwford. Select View Diagram under the activities list to view the actual workflow diagram. and is used in conjunction with Oracle Order Management: 1-6 Using Oracle Workflow in Oracle Order Management .

Bill Only with Inventory Interface Line Flow .Generic with Header Level Invoice Interface Line Flow .Generic.Configuration Line Flow .wft Seeded Data File oexwford.Configuration with Authorize to Ship (RLM) Line Flow .Return for Credit Only with Approval Line Flow .Return for Credit Only Line Flow .wft Item Types The seeded data file oexwford.ATO Item Line Flow . With Export Compliance Line Flow . with Repricing at Fulfillment Line Flow . Bill Only Line Flow .Seeded Data Files ■ ctochord.wft contains the following item types: ■ OM Change Order OM Order Header OM Order Line OM Standard ■ ■ ■ Processes The seeded data file oexwford.wft contains the following processes: ■ Change Order Process Line Flow .Generic.Generic.Generic.Generic.Generic with Authorize to Ship (RLM) Line Flow .Return for Credit with Receipt ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ Introduction 1-7 . Ship Only Line Flow .ATO Model Line Flow .Generic Line Flow .

Manual Buy ATO Item Flow Calculate Lead Time .Line.Order.wft: ■ Authorized to Ship .Line.Line Create Supply Order . Deferred Header Level Invoice Interface .Generic with Header Level Invoice Interface Order Flow .Line.Order Inventory Interface Non-Ship .Order Create Configuration .Seeded Data Files ■ Line Flow .Line Header Level Invoice Interface .Line Close .Return with Approval ■ ■ ■ ■ ■ Subprocesses The following are the workflow subprocesses contained in oexwford.Line.Line Close .Generic Order Flow . Manual Create Supply . Manual Create Manufacturing Configuration Data .Order.Return for Credit with Receipt and Approval Line Flow .Line Export Compliance Screening . Deferred ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ 1-8 Using Oracle Workflow in Oracle Order Management .Line Approve Return .Line Inventory Interface Non-Ship .Order Book . Manual Create Work Order .Line.Standard Service Line Flow . Deferred Book .Standard Service Order Flow .Line Enter .

wft contains the following process: ■ Notification for Change Order Item Types The following section discusses the different item types used in Oracle Order Management seeded workflows.Line Schedule .wft Item Types The seeded data file ctochord.Line.wft contains the following item types: ■ CTO Change Order Standard ■ To learn more about the Standard item type.Line Schedule . Deferred Purchase Release . Manual ■ ■ ■ ■ ■ ■ ■ ■ Seeded Data File ctochord.Line. Deferred Ship .Line. refer to the Oracle Workflow Guide. Oracle Order Management contains the following item types: ■ OM Change Order OM Order Header OM Order Line OM Standard ■ ■ ■ Introduction 1-9 . Processes The seeded data file ctochord.Line.Item Types ■ Invoice Interface . Manual Reprice .Line.Line Return Receiving . Deferred Purchase Release .Line Invoice Interface .

Change order notification flows are created using this item type. A header can contain one or many lines. Currently there is one process associated with OM Change Order: ■ Change Order Process OM Change Order sets up a framework for sending FYI notifications to the resolving responsibilities. The attributes are used and maintained by function activities and notification activities throughout the process. The following table lists the OM Change Order item type attributes: Length/Format/Lookup Type/Frame Target 150 Display Name Resolving Role Description The recipient of the notification or the resolver for the failed constraints Placeholder for the text entered in the Notification form Placeholder for Order Number Order Management Workflow Administrator Type Text User Text Order Number Order Management Workflow Administrator Text Number Role 2000 None None OM Order Header Oracle Order Management includes the concept of an order header. The OM Order Header item type identifies all Oracle 1-10 Using Oracle Workflow in Oracle Order Management . The following item type comes seeded with Oracle Configure to Order and is used in conjunction with Oracle Order Management: ■ CTO Change Order OM Change Order This item type is used to manage change orders. These attributes reference information in the Oracle Order Management application tables.Item Types ■ Standard The different items types are contained in different seeded data workflow files. The OM Change Order item type has several attributes associated with it. refer to the Oracle Workflow Guide. To learn more about the Standard item type.

Item Types Order Management order header process available.Order Header Level Invoice Interface . The attributes are used and maintained by function activities and notification activities throughout the process.Order.Order Book . Manual Close .Generic Order Flow .Generic with Header Level Invoice Interface Order Flow .Order ■ ■ ■ ■ The OM Order Header item type has several attributes associated with it. Deferred Book .Order. These attributes reference information in the Oracle Order Management application tables. The following table lists the OM Order Header item type attributes: Length/Format/Lookup Type/Frame Target None None None None None 30 Full Window None Display Name User ID Application ID Responsibility ID Order Management Workflow Administrator Org ID Order Category Header Short Descriptor Notification Approver Description User identifier used to set the context Type Number Application identifier for setting the Number workflow context Responsibility identifier Order Management Workflow Administrator Organization ID Order Category Header Short Descriptor Notification Approver Number Role Number Text Document Role Introduction 1-11 .Return with Approval ■ ■ The following five subprocesses are associated with OM Order Header: ■ Approve Return . Currently there are three processes associated with OM Order Header: ■ Order Flow .

Generic. With Export Compliance Line Flow . Ship Only Line Flow .Generic. This item type identifies all Oracle Order Management order line processes available.Standard Service ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ The subprocesses associated with OM Order Line include the following: ■ Authorized to Ship .Return for Credit Only Line Flow .Line Close . Bill Only with Inventory Interface Line Flow .Line.Item Types OM Order Line The following section discusses processes associated with the OM Order Line item type.Configuration with Authorize to Ship (RLM) Line Flow .Return for Credit with Receipt and Approval Line Flow .Line Create Configuration .Generic with Authorize to Ship (RLM) Line Flow .Generic with Header Level Invoice Interface Line Flow .Standard Service Line Flow . The processes associated with OM Order Line include the following: ■ Line Flow .ATO Model Line Flow . Manual ■ ■ ■ ■ 1-12 Using Oracle Workflow in Oracle Order Management .Line Buy ATO Item Flow Calculate Lead Time .ATO Item Line Flow .Generic Line Flow . with Repricing at Fulfillment Line Flow .Configuration Line Flow .Generic.Return for Credit Only with Approval Line Flow . Bill Only Line Flow .Return for Credit with Receipt Line Flow .Generic.Generic.

Deferred Purchase Release . Manual Create Supply .Line.Line.Line.Line Create Supply Order . These attributes reference information in the Oracle Order Management application tables. Manual Create Work Order .Line.Line.Line Enter .Line. Deferred Purchase Release .Line Invoice Interface . The following table lists the OM Order Line item type attributes: Length/Format/Lookup Type/Frame Target None None None Display Name User Id Application ID Responsibility ID Description User Identifier for the workflow initiator Application Identifier for the workflow initiator Responsibility Identifier Type Number Number Number Introduction 1-13 .Line Schedule .Line.Line Header Level Invoice Interface .Line. Deferred Ship .Line. Deferred Invoice Interface .Line Export Compliance Screening . The attributes are used and maintained by function activities and notification activities throughout the process. Manual Reprice .Line Return Receiving .Line Schedule .Item Types ■ Create Manufacturing Configuration Data . Deferred Inventory Interface Non-Ship . Manual ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ The OM Order Line item type has several attributes associated with it.Line Inventory Interface Non-Ship .

message or activity attributes. These lists can be referenced by activities and by item type. The application does not use this item type to create any flows. The following table lists the seeded lookup types associated with OM Standard and their lookup codes: Lookup Type Lookup Code Check Reservation Status Check Supply Type Results Concurrent Program Retry Concurrent Program Status Not Reserved. Work Order Abort. A lookup type is a static list of values. Retry Cancelled. Terminated. Reserved Buy. Drop Ship. Error.Item Types Display Name Order Management Workflow Administrator Org ID Lead Time Rollup Organization Lead Time Rollup Config Item Lead Time Date Lead Time Category Structure Line Category Lead Time Attribute Req ID Lead Time Request ID AFAS Line ID Line Short Descriptor Notification Approver Description Order Management Workflow Administrator Organization ID Manufacturing Organization of Config Item Configuration Item for which to calculate the Lead Time Lead Time Date Lead Time Category Structure Line Category Lead Time Attribute Req ID Lead Time Request ID AFAS Line ID Line Short Descriptor Notification Approver Type Role Number Number Number Text Number Test Attribute Number Number Document Role Length/Format/Lookup Type/Frame Target None None None None None None 30 None None None Full Window None OM Standard OM Standard is a repository for common functions and lookups. Warning 1-14 Using Oracle Workflow in Oracle Order Management . Incomplete. Normal. Flow Schedule. There are several lookup types associated with OM Standard.

Fulfillment Date. Partial Incomplete Fails. Incomplete Attended.Item Types Lookup Type Lookup Code Config Data Results Config Incomplete Config Item Results Config Line Result Config Process Results Enrollment Status Enrollment Status for Advance Enrollment Status for Arrear Invoice Results Invoicing Rule Lead Time Result Line Category Manufacturing Release Status Nonstock Flag Notification Approver Source Notification Required OM Check for Eligibility OM Export Compliance Results OM Subprocess Results OM Subprocess Results. Required Eligible. REquest Date. Not Eligible. Not Eligible. Waitlisted Complete. Hold Applied. Not Eligible. Partial Incomplete Complete. Partial Complete. No Routing Order. Requested. Override Complete. Incomplete. Passes Actual Shipment Date. System Date Introduction 1-15 . Not Eligible Complete. Incomplete. Incomplete. Waitlisted Attended. Requested. Partial Advanced. Return Eligible. Arrear Complete. Profile Approver Not Required. Handles Holds OM Subprocess Success Results OM Subprocess with Partial Processing OM Subprocess with Partial Processing. Schedule Ship Date. Stock Created By. Incomplete. On Hold. Not Eligible. Placed. Handles Holds Passes/Fails Repricing Date Config Data Created Complete. Order Created By. On Hold. Partial Complete. Reserved Complete. Waitlisted Placed. Config Data Not Created. Delink Config Data Created. Incomplete. Not Eligible Complete. Placed. Not Eligible Complete. Work Order Completed Nonstock. On Hold Complete. On Hold Complete. Incomplete. Incomplete. Promise Date.

Item Types Lookup Type Lookup Code Repricing Event Reserved Status RMA Wait Result Shipping Results Source Result Source Type Supply Source Type Unit of Measure Upgrade Purchase Release Status Line. Reserved Complete. Stock External. Event Confirmed. Shippable ATO Item. Internal Enrollment. Reprice Line Process AutoCreate PO. Build. These attributes reference information in the application tables. Price. Correct Receiving Non Shippable. Interfaced For more information about lookup types. Ship Confirm. The attributes are used and maintained by function activities as well as notification activities throughout the process. refer to the Oracle Workflow Guide. Currently there is one workflow processes associated with CTO Change Order: ■ Notification for Change Order The CTO Change Order item type also has several attributes associated with it. Unreserve Non Shippable. Over Shipped Beyond Tolerance. Dropship. The following table lists the CTO Change Order item type attributes: Length/Format/Lookup Type/Frame Target None None None 150 40 Display Name Sales Order Number Customer Name Line Number Item Name Request Date Description Sales Order Number Customer Name Line Number of the Model Item Name Request Date Type Number Text Text Text Text 1-16 Using Oracle Workflow in Oracle Order Management . CTO Change Order The CTO Change Order item type identifies all CTO Change Order workflow processes available. Eligible.

Item Types Display Name Scheduled Ship Date Scheduled Arrival Date Cancelled Flag Special Text Change Order Administrator Configuration Changed Flag Quantity Change Notification User Delink Action Flag Action Text Description Scheduled Ship Date Scheduled Arrival Date Order Line is Cancelled Special Text Change order Administrator Configuration is Changed Qty change Notification User Delink Action Flag Action Text Type Text Text Text Text Role Text Text Text Text Text Length/Format/Lookup Type/Frame Target 40 40 None 400 30 5 None 50 5 20 Introduction 1-17 .

Item Types 1-18 Using Oracle Workflow in Oracle Order Management .

The following topics are addressed: ■ Selecting Workflows on page 2-7 Assigning Workflows to Transaction Types on page 2-7 Workflow Background Engine Processing on page 2-7 Scheduling Workflows on page 2-10 Repricing Order Lines on page 2-11 ■ ■ ■ ■ Processing Orders Using Oracle Workflow 2-1 .2 Processing Orders Using Oracle Workflow This chapter discusses how orders in Oracle Order Management are processed using Oracle Workflow.

Some workflow steps between an order and line are interdependent based on how continue-flow and wait-for-flow activities are paired. Specify an assignment for the configured item type if you plan to use the line type for ATO configurations. This section provides an overview of the header and line level processes that come seeded with Oracle Order Management. The inventory item that a line processes may have specific flow requirements. You cannot select any order workflow to be used with a line workflow. The Workflow Assignments window displays the following item types to which a workflow can be assigned for a given order or order line type: ■ ATO Models. the workflow for a configuration item is different than for a standard item. the same line transaction type must follow a different line flow when used with a different order transaction type. the specified workflow assignment applies to all item types for which there is no specific assignment. Classes. Assigning workflow processes to header and line level transaction types enables you to initiate a process on an order and on an order line. Options. line level processes must be assigned. The standard item can be picked from stock and shipped. After you define a line transaction type. 2-2 Using Oracle Workflow in Oracle Order Management . Header level workflow processes must be assigned to transaction types in Oracle Order Management. Options Standard Items Service Items ■ ■ ■ ■ ■ ■ If the item type code is left blank.Selecting Workflows Selecting Workflows Oracle Order Management comes seeded with several workflow processes. Items Configured Item Kits Included Items PTO Models. Classes. a configuration must have a bill of materials and a work order created before it can be picked and shipped. If you do not use order and line flows designed to work together your orders or order lines could complete too early or never complete. Therefore. Therefore. Order Flow .Generic with Header Level Invoice Interface waits for an activity in the line flow to complete. For example. Both types of order lines can be used for the same line type. For example. It also provides recommendations for which workflows processes can best meet your business needs.

Order Flow . kits.Return with Approval: Use this header flow when all lines on the order are returns and header level approval is required. all of the line level processes seeded in Oracle Order Management are used for outbound processing.Generic Use this process for all items except for service items. Generic Processes The following line level workflow processes execute typical activities for entering and scheduling order lines: Line Flow . Processing Orders Using Oracle Workflow 2-3 .Return with Approval. and pick-to-order (PTO) models. Order Flow . ■ Line Level Processes With the exception of returns. Note: This process must be used in conjunction with Line Flow - ■ Generic with Header Level Invoice Interface. Always use this process unless you require the functionality specific to Order Flow . Order Flow . Header Level Processes The following list provides an overview of the header processes seeded in Oracle Order Management: ■ Order Flow . This process includes activities that book and close the order header. including assemble-to-order (ATO) items.Selecting Workflows Note: A workflow assignment is required for a given line type to support creation of lines using that line type. with outbound lines and with return lines. ATO models.Generic with Header Level Invoice Interface or Order Flow .Generic can be used with any line flow for any item type.Generic with Header Level Invoice Interface: Use this header flow if your business requires that all lines on the order invoice together at the header level. The following sections provide overviews of the line level processes seeded in Oracle Order Management.Generic: This is the most commonly used header flow.

For example. Bill Only Use this process when scheduling and shipping are not necessary for an ordered item.Generic. or a standard items.Generic is selected. Ship Only Use this process if you must ship a product but an invoice is not necessary. and close processes. and could be used for screening after scheduling but before manufacturing. Line Flow . Outbound lines for all item types (other than Service) can be handled by Line Flow . For example. the necessity of selecting a specific process for a particular item type is eliminated (this could be useful for customer service representatives). By selecting Line Flow . Note: This process must be used in conjunction with Order Flow - Generic with Header Level Invoice Interface. With Export Compliance Select this process when products exported to a denied party must be checked. you are a high volume ATO user. so the process line moves to invoice interface. Invoice is controlled by the AutoInvoice concurrent program.Selecting Workflows This flow will not work for configured items generated from assemble-to-order models. This flow decrements inventory. If. assemble-to-order models.Generic. Set up grouping rules in Oracle Receivables if only one invoice for the order is necessary. Bill Only with Inventory Interface Use this flow when products are not shipped but inventory decrement is required.Generic is effective because it manages several item types. invoice interface.Generic. specific Assemble to Order (ATO) Processes can improve performance. Line Flow .Generic. then proceeds with invoice interface. When Line Flow . Line Flow .Generic with Header Level Invoice Interface Use this process when all order lines must invoice simultaneously. the line progresses through the create supply.Generic. Line Flow . From a setup perspective.Generic. users must not remember to select different processes for assemble-to-order items. This process fulfills the order line. fulfill. For example. this process 2-4 Using Oracle Workflow in Oracle Order Management . ship. so shipping is not necessary. The inventory transaction must be accounted for. this process might be used if an invoice was incorrect and an adjustment must be made visible in Oracle Order Management Line Flow . some distributors have customers who pick up products in person. This process is commonly used in the defense industry. Line Flow . however. The product is picked up. If the party (such as the ship to) is authorized.

The flow runs calculation of manufacturing data.ATO Item Use this process instead Line Flow . and close. shipping. scheduling. Assemble to Order (ATO) Processes Assign the seeded line workflow for the Configured Item line type if your business processes ATO configurations. Line Flow . Line Flow . It then continues with shipping. fulfillment. fulfillment. you can delete Item Attributes that relate only to ATO models or ATO items to improve performance. fulfillment. deferred fulfillment.Generic for ordering only ATO models.Generic for ordering only ATO items. creating configuration. The following are item attributes associated only with ATO models and ATO items: ■ Lead Time Rollup Organization Lead Time Rollup Config Item Lead Time Date Lead Time Category Structure Lead Time Attribute Req ID Lead Time Request ID AFAS Line ID ■ ■ ■ ■ ■ ■ ATO processes seeded in Oracle Order Management include the following: Line Flow .Configuration This process is for configured items. or for shipping a non-billable toolset to repair a previously invoiced item. If your business does not process ATO models or ATO items. The process runs the typical entering and scheduling processes.ATO Model Use this process instead of Line Flow . invoice interface. invoice interface. The process then continues with shipping. Processing Orders Using Oracle Workflow 2-5 . and close. Assign this process to the order line type used for configurations as part of your implementation process. Configured Item refers to the actual item created by Oracle Configure to Order for an ATO model order line as part of the Autocreate configuration process. and creation of supply for configuration. but does process standard items and PTO items. The configured item is created from a model as a part of the Autocreate configuration process for ATO items.Selecting Workflows could be used when shipping free samples for a new product. and close. The process runs entering. This process also creates supply for an ATO Item.

Demand interfaced from Oracle Release Management as Not Authorized To Ship can be changed to Authorized to Ship using this workflow process. 2-6 Using Oracle Workflow in Oracle Order Management . Line Flow . for example. if you give credit for a product shipped on a CD. This process is useful when the returned items are expensive. The process runs an activity that issues credit without waiting for a receipt of goods or an approval. The modem is received then inspected to ensure that no mistreatment or neglect of the item occurred. but you do not want the CD to be returned. credit is issued.Generic with Authorize to Ship (RLM) use this flow if you use Oracle Release Management and want to forecast in Oracle Order Management. the process continues through invoicing and credit is issued. The process requires both receipt of goods and an approval.Return for Credit with Receipt and Approval This process is the most restrictive for incoming lines. invoice interfacing occurs. Inbound Processes The following line level workflow processes are used for returns or inbound lines: Line Flow .Return for Credit Only This process is used only for incoming lines.Return for Credit Only with Approval This processes is used only for incoming lines that requires approval. for example.Selecting Workflows Oracle Release Management Processes The following line level workflow process is commonly used with Oracle Release Management: Line Flow . Service Item Processes The following process is used for service items: Line Flow . This flow could be used. Line Flow . This process is commonly used when items such as modems are returned.Standard Service Use this process for service items such as support. This process could be used. Once the returned items are received by Oracle Purchasing. Once the line is fulfilled. credit should not be issued until the items are received. Once inspected and approved.Return for Credit with Receipt This process is used only for incoming order lines that require receipt of goods before credit can be issued. when a return must be approved by a manager or a customer service representative before credit is issued. Line Flow .

The following image depicts the Transaction Types window in Oracle Order Management: Processing Orders Using Oracle Workflow 2-7 . Oracle Order Management enables you to define both header and line level transaction types.Assigning Workflows to Transaction Types Assigning Workflows to Transaction Types Oracle Order Management transaction types determine the workflow processes executed at header and line levels. Oracle Order Management does not provide seeded transaction types. You must create your own transaction types using the transaction types window in Oracle Order Management.

drop-ship orders. activities. "Extending Oracle Order Management Seeded Workflows". The following image depicts the Line Workflow Assignments window: 2-8 Using Oracle Workflow in Oracle Order Management . Oracle Corporation does not provide support for your custom activities and processes. For information about creating your own workflow processes.Assigning Workflows to Transaction Types The Transaction Type determines the header level process used at the header level on an order. or notifications. Use this window to assign line flows to the line types used with an order type. You can also create your own workflows if you need additional processes. line type. Line Workflow Assignments The Line Workflow Assignments window is available for Oracle Order Management order transaction types. The combination of transaction type. Warning! Oracle Corporation provides support only for its seeded activities and processes. You can perform all standard processing including orders. For more information about extending existing workflow processes. orders for configured items. and orders for assemble-to-order items using seeded workflows. refer to Chapter 3. returns. refer to the Oracle Workflow Guide. and item type determines the line workflow.

Oracle Order Management enables you to define one assignment for a given combination. select Oracle Order Management item types (OM Order Header and OM Order Line) as the parameter. and item type combination. Processing Orders Using Oracle Workflow 2-9 . If the item type is left blank. line type. Workflow Background Engine Processing The Workflow Background Engine processes deferred activities. then that assignment applies to all item types which do not have specific assignments. Schedule the Workflow Background Process concurrent program to resubmit periodically. When scheduling with the concurrent program. If you use a line type for ATO models Oracle Order Management requires you to specify assignments for configured item types. The system then selects only activities specific to Oracle Order Management. It also processes wait activities and timed-out activities when the wait/time-out period is reached.Workflow Background Engine Processing A line flow can be assigned to an order type.

This can run less often (for example. Obtain other scheduling attributes. Define the Process Deferred parameter as Yes. Note: If scheduling encounters an unexpected error (such as system or network error). ■ ■ ■ 2-10 Using Oracle Workflow in Oracle Order Management . Schedule this request to run most frequently (for example. 2. Scheduling Workflows A line which not scheduled from the Sales Orders window can be scheduled using a workflow activity. for an order line.60 minutes). once per day). and process time-out and stuck less frequently. and all other parameters as No. add. This can run less frequently (for example. Define Process Time-out as Yes. complete the following steps: 1. 3. To set schedules for the Workflow Background Engine. The workflow activities are completed automatically based on your workflow process definition. process deferred activities frequently. Schedule Workflow Activity The standard schedule workflow activity performs the following functions: ■ Obtain a ship-from location for an order line. once every 30 . Each order process activity can be represented as a workflow activity.Scheduling Workflows Note: Always run at least three separate schedules of the Workflow Background Engine for order lines. The most common use of the background engine is to process deferred activities. every 10 -15 minutes). Obtain the schedule date for an order line. update and delete will also fail. Reserve order lines (when within the reservation time fence period). To improve performance. Define Process Stuck set to Yes and all other parameters as No. Set all other parameters to No. including delivery lead time and shipping methods.

"Seeded Subprocess Definitions". refer to the Oracle Order Management User’s Guide.Repricing Order Lines For more information about the scheduling activities available in Oracle Order Management. Oracle Order Management and Oracle Workflow also enable you to determine the following: ■ When repricing should occur Which pricing event phases are executed when repricing Whether to ignore the Calculate Price flag value for an order line Note: You must use the Reprice activity to access repricing ■ ■ functionality. refer to Chapter 5. Processing Orders Using Oracle Workflow 2-11 . Pricing Date Set the Reprice activity Repricing Date attribute when you insert the activity into a workflow. Repricing Order Lines Oracle Order Management enables you to reprice an order line at any point in the order life cycle using Oracle Workflow. refer to Chapter 6. For more information about the pricing functionality in Oracle Order Management. You can set the pricing date to one of the following dates for your order line: ■ Actual shipment date Schedule ship date Fulfillment date Promise date Request date System date ■ ■ ■ ■ ■ You can select the original pricing date on the order line if you set the Repricing Date attribute to Null. For more information about the subprocesses that use scheduling activities. "Seeded Function Activity Definitions".

For more information about pricing events. verify that you also define this event as a lookup type. 2-12 Using Oracle Workflow in Oracle Order Management . The Repricing Event attribute is an Oracle Order Management lookup type to list all pricing events for which repricing can be executed. Reprice Line is a seeded pricing event. ■ Repricing and freight charge recalculation occurs regardless of the value of the calculate price flag. you cannot select the new pricing event when setting the Repricing Event attribute. Calculate Price Flag You can control whether the repricing line workflow activity honors the value of the calculate price flag by setting the Reprice attribute Honor Price Flag to one of the following: ■ Yes: honors the value of the calculate price flag on the order. If you add a new pricing event for use with Reprice. If this is not defined as a lookup type. Repricing at the Line Ship/Schedule Date Place the Reprice activity after all shipping activities in a workflow to reprice an order line at shipment for workflows that processes only items and lines not in fulfillment sets. No: ignores the value of the calculate price flag. You can only associate line-level pricing phases with this event.Repricing Order Lines Pricing Phases Set the Repricing Event attribute to Pricing Event to control line-level pricing phases to be executed at repricing. refer to the Oracle Advanced Pricing User’s Guide. Current lookup codes for Repricing Event include the following: ■ Line Price Reprice Line ■ ■ You can recalculate base price while keeping the discounts given during the order entry time by setting the Repricing Event attribute to Price. Note: If you set the Repricing Event attribute to Null. the repricing event is Reprice Line.

non-shippable items. place the Reprice activity in your flow after the fulfillment activity. refer to the Oracle Advanced Pricing User’s Guide. Note: Placing the Reprice Line workflow activity after the fulfillment activity enables your workflow to process shippable items. For more information on defining Pricing Events. 2. Pricing Events. Use either the shipment date (either actual shipment date or scheduled ship date) for the Repricing Date attribute. Navigate to the Event Phases window and add each desired phase. Set the following workflow attributes: ■ Repricing Date: fulfillment date Repricing Event: Reprice Line or another defined event ■ Processing Orders Using Oracle Workflow 2-13 .Repricing Order Lines Note: If the Reprice activity fails it does not impact your shipping activities. and non-shippable lines in a fulfillment set. Repricing at the Line Fulfillment Date To reprice an order line at its fulfillment date. then update your pricing events. 3. Repricing at shipment validates the price list associated with the agreement specified on the order. Repricing at shipment does not validate agreements and their effective dates. Complete the following steps to reprice at the line fulfillment date: 1. Place the Reprice activity after the fulfillment activity in your workflow.

Repricing Order Lines 2-14 Using Oracle Workflow in Oracle Order Management .

3 Extending Oracle Order Management Seeded Workflows This chapter discusses how to extend the workflows seeded in Oracle Order Management. The following topics are addressed: ■ Overview on page 3-2 Customizations on page 3-2 Extending Workflow on page 3-3 ■ ■ Extending Oracle Order Management Seeded Workflows 3-1 .

and the types of extensions described in this manual. Use the seeded flows as examples to create new order or line flows using the seeded functional subprocesses and include your own custom activities in the Oracle Workflow Builder. change its internal name. you can however copy and rename Book . Oracle Corporation does not support customizations to seeded workflows. and performing special logic based on the amount. you can create new flows by using any of the following methods: ■ Copy a seeded order or line flow. Changing the basic logic of a seeded subprocess. However.Order.Overview Overview This chapter provides guidelines to follow for extending the Oracle Order Management seeded workflow processes to meet your business needs. display name. changing the wait period of the Wait activity from month end to daily). Manual. If the Oracle Order Management seeded workflows do not meet your business processing needs. Manual and then insert a notification function activity. and description in the Oracle Workflow Builder. Using a third party invoicing module instead of Oracle Accounts Receivable for invoice interface.Order. Customizations A customization changes the logic of the core application. Oracle Corporation supports the extension of workflows. such as Book . Oracle Corporation does not provide support for your custom activities and processes. Use the seeded flows as examples to create new order or line flows using the seeded functional subprocesses in the Oracle Workflow Builder. Change the definition as desired. Adding or deleting activities from a seeded subprocess alters seeded data. Examples of customizations include: ■ Adding a new custom header activity that checks whether the order exceeds a certain currency amount. processes. this creates a new activity to populate the custom tables. ■ ■ 3-2 Using Oracle Workflow in Oracle Order Management . Extensions include using existing seeded subprocesses to build new workflow processes and modifying parameters of a subprocess without changing process logic (for example. Warning! ■ ■ Oracle Corporation provides support only for its seeded activities.

For more information about extending workflows or to learn how to create your own workflows. Extending Workflow When extending existing workflows to meet your business needs. Modifying the integration of Oracle Order Management with another application such as Oracle Service. Exceptions The following exceptions are supported by Oracle Corporation: ■ You may change the item attribute OM WF Administrator to another responsibility (it defaults as SYSADMIN). RETRY_ONLY does not support aborting the flow or skipping the activity in an error state.Extending Workflow ■ Modifying drop-ship logic. You may tailor message bodies on seeded messages to meet your business needs. processes or flows that you define. Do not specify any other error process. always copy the seeded process and rename both the internal and display names before modifying the workflow. Extending Oracle Order Management Seeded Workflows 3-3 . This process ensures that you do not modify seeded data.wft files (which contain all the seeded flows and related information) from overriding your modifications. Warning! ■ Customization refers to the modification of the logic of a process or subprocess. Note: The RETRY_ONLY error process supports retrying only of ■ ■ ■ the activity in an error state. You can assign the seeded workflows to transaction types. and is not supported by Oracle Corporation. You can set the default error process of RETRY_ONLY on any new functions. Do not leave the error process field empty. It also prevents patches containing the. refer to the Oracle Workflow Guide.

but also determines whether an item is sourced internally or externally. processes.Line subprocess not only creates supply.Line are mandatory steps in header and line processes. you should not directly change the Book . and item attributes. your changes are not supported. use the seeded Book . this includes all function activities. shipping is dependent on booking and therefore cannot occur after booking. assign it to an order or line type. Lines should not interface to Oracle Invoicing until after shipping occurs (if a shipping activity exists in the process). refer to Assigning Workflows to Transaction Types.Order. The subprocess is designed to handle exceptions. All order header processes are created as parent flows.Order. Always modify a copy of a subprocess instead of function activities. The following list describes dependencies in Oracle Order Management: ■ Order lines wait for booking before continuing their flow. Order lines should not invoice until after booking occurs. subprocesses.Continue Line (Complete) function activity is part of the Book . Do not modify predefined data. Any changes to the seeded workflow data are overwritten when a patch containing the . For example. the Create Supply . respectively. For more information about assigning workflows to transaction types. Copy and rename what you want to change before making modifications. For example. For example. Once you have modified an order or line flow. Wait for Flow and Continue Flow workflow utilities support the order (parent) line (line or detail) coordination. For example. Manual subprocess by adding or deleting activities from it. Manual subprocess rather than the seeded Book function activity. and it may perform other functions as well. The Wait for Booking ■ ■ ■ ■ 3-4 Using Oracle Workflow in Oracle Order Management . Dependencies Oracle Order Management requires that some workflow events occur before others.Order. This creates certain dependencies that should not be violated. Manual subprocess.Order and Close .Extending Workflow Warning! If you modify any of Oracle Corporation’s seeded workflow data.wft file is applied. Processes for lines on orders are created as child (detail) flows. Close . The Book .

For example. Manual or Book Order.Order.Line subprocess. For instance. Manual subprocess to complete before the lines continue. this is considered extending. You could add a standard WF notification to a flow. and is not a customization. Note: Oracle Order Management supports only standard WF ■ ■ ■ notifications: either an FYI notification or a notification requiring a response. Do not design a line level process that conducts invoice interface before it shipping. The following are several examples of extending workflow: ■ You can construct a flow using only seeded sub-processes from Order Management. You could change it to wait for a different period of time.Order. If the necessary dependency requirements are met. ■ ■ Extending Oracle Order Management Seeded Workflows 3-5 . There are several ways to extend workflow processes without violating the Oracle Order Management dependencies.Extending Workflow function activity is part of the Enter . and the line level process should include Enter . by default the Header Close Order sub-process will wait until the end of the month before closing the order.Line subprocess. All line level processes should include the Close . The order header process should contain either Book . the Line or Header might proceed after a defined period of time. Notifications that call stored PL/SQL procedures are not supported. or send a Yes/No approval notification before invoicing.Line. You can change the WAIT period of a seeded WAIT function activity. Guidelines When extending workflow processes to meet your business needs. stay within the following guidelines: ■ All order header processes should include the Close . You could add a Time Out transition such that if there is no response to a notification. The line flow waits for the header level Book . Deferred. you might want to send a simple FYI notification before invoicing a line.Order subprocess.

4.Order subprocess. Some workflow function activities must be configured. or violate the rules for modifying a subprocess. If a line must conduct invoice interface. This is done by setting the function activity attributes. Attach your new process to a Transaction Type. Remember to modify the internal and display names of this new process. 2. Note: Always remember to copy the seeded process or subprocess and rename both the internal and displays name before making any modifications. Modify the Wait function activity in the copied and renamed Close . change core logic. 1. select a subprocess which performs that particular function.Order subprocess. Always specify RETRY_ONLY as the default error process for any workflow activity you define. If you want the orders to close twice a day.5. ■ ■ Examples of Extending Workflow This section discusses possible extensions to the seeded Oracle Order Management workflows. select the Node Attributes tab and set the Wait Mode to Relative Time. For example. 3. Copy and rename the internal and displays names for the Close . with a notification activity you must set up a performer (recipient). and set the Relative Time attribute to a value of . Process Parameters Complete the following steps to modify the Close . If you use Utility . Drag and drop this subprocess into your new header level process.Set Notification Approver to enable you to send notification to the user/responsibility specified in the Notification Approver profile option.Extending Workflow ■ Include the functional subprocess that represents the business process you are need. The extensions listed do not violate Oracle Order Management dependencies.Order subprocess to close orders more frequently than month-end. open the property sheet of the Wait activity. 3-6 Using Oracle Workflow in Oracle Order Management . you must also specify the user/responsibility in the profile option.

6. One way to extend a workflow process using an approval is to add an approval to the header before booking. Manual or Book . 2. Insert the approval notification function activity into the subprocess so that the approval occurs before booking. To create a process with this approval.Order. Create the approval message and notification. Set the performer of the notification. 3. 4. Insert the approval notification function activity into the subprocess so that the approval occurs before booking. complete the following steps: 1. Copy and rename the internal and displays names for the line level subprocess (such as Line Flow . For more information about creating messages and notifications. refer to the Oracle Workflow Guide. Deferred). Save your new subprocess and drag and drop it into a header level flow process (one that has been copied and renamed for your extensions). Extending Oracle Order Management Seeded Workflows 3-7 . For more details on creating and extending workflows refer to the Oracle Workflow Guide. 3. Assign your new line process to a Transaction Type in Oracle Order Management. Create the approval message and notification.Extending Workflow Approvals You can extend processes and subprocesses by adding approvals. Another way to extend a workflow process using an approval is to require approval for all standard line processes before a Ship activity can occur. Refer to the Oracle Workflow Guide for more information about approvals. 5. To create a process with this approval. 4. refer to the Oracle Workflow Guide. complete the following steps: 1. Set up a Transaction Type in Oracle Order Management that uses your new header process flow.Generic). 2. For more information about creating messages and notifications. Copy and rename the internal and displays names for the header level booking subprocess (Book . 5.Order. Select the performer of the notification. For more details on creating and extending workflows refer to the Oracle Workflow Guide.

Order. In the case of quotes. 4. To create a process with deferred booking. Deferred subprocess in place Book . refer to the Oracle Workflow Guide. There is no response within 30 days. 3.Order. 2. Create an approval message and notification. for example. The order closes if either of the following conditions occur: ■ The approval is rejected. 3-8 Using Oracle Workflow in Oracle Order Management .Extending Workflow Deferred Booking Another extension available at the order header level is to create a process with deferred booking. Time-out Transition for Notifications The time-out transition option is another way to extend workflow to meet business requirements. Save your new process and assign it to a Transaction Type in Oracle Order Management.Order. Deferred. Remove the Book . Set the performer of the notification. 3. Manual or Book .Generic). Manual subprocess. Assign your new line process to a Transaction Type in Oracle Order Management. For more information about creating messages and notifications. 5. Copy and rename the internal and displays names for the line level subprocess (such as Line Flow .Generic). complete the following steps: 1. a yes/no approval function activity is inserted before Book . On the Node tab of your notification define a time-out. orders processed using this Transaction Type close after 30 days if the notification is not approved.Order. If you use the Relative Time time-out of 30 days. ■ To set up such a process with a time-out transition. Copy and rename the internal and displays names for the order level process you want to extend (such as Order Flow . complete the following steps: 1. Insert the approval notification function activity into the subprocess so that the approval occurs before booking. 2. Insert the Book . If approved the order continues to the booking subprocess. 6.Order. Manual. 4.

4 Seeded Workflow Definitions This chapter discusses Oracle Order Management seeded processes and their definitions. The following topics are addressed: ■ CTO Change Order Process on page 4-2 OM Change Order Processes on page 4-4 OM Order Header Processes on page 4-5 OM Order Line on page 4-11 ■ ■ ■ Seeded Workflow Definitions 4-1 .

notification is sent to the planner of the top model/item in the shipping organization. the Change Order Process sends a notification of the change to the order. 4-2 Using Oracle Workflow in Oracle Order Management . When you submit a change to a sales order. A notification of the changes is sent to the buyer. If the planner code value is null or not a valid workflow user then the notification is sent to the system administrator. These changes can cause data inconsistency between Oracle Order Management and Oracle Work in Process if action is not taken by the planner to update associated Oracle Work in Process jobs or flow schedules. a notification is sent to the buyer on the requisition. For configured and ATO items. or multi organization configurations and ATO items a notification of the changes is always sent. For single-level. regardless if a reservation exists for the top level configuration or ATO Item.CTO Change Order Process CTO Change Order Process Notification for Change Order The Change Order process is an Oracle Configure to Order workflow process that initiates when you change any of the following attributes on an order: ■ Scheduled ship date Request date/scheduled arrival date Order line quantity Configuration ■ ■ ■ This process is also initiated if you cancel an order. Only one message is sent for all changes accepted in an order line. For multi level. if a reservation to a requisition or purchase order exists for the ATO item. The Change Order Process is contained in the seeded data file CTO Change Order and is associated with the CTO Change Order item type. For purchase to order ATO items. If there are configuration changes. single-organization configurations and ATO items a notification is sent only if a reservation or flow schedule exists for the configuration. a notification is sent even if no reservation exists.

the process continues on to the End subprocess in node 3.CTO Change Order Process Summary of the Change Order Process To view the properties of the Change Order Process process. you see that the process consists of 3 unique activities. which indicates that it can be assigned to a transaction type. Seeded Workflow Definitions 4-3 . This item type is associated with the RETRY_ONLY error process. This error process is initiated only when an unexpected error with Oracle Workflow is encountered in the process. After the notification is sent. When you display the Process window for the Change Order Process. Change Order Process Activities The following table provides descriptions of each function activity in Change Order Process. The purpose of this error handling process is to alert an administrator when an error occurs in a process and prompt the administrator to retry the process in error. The Details property page of the process activity indicates that Change Order Process has an error item type of WFERROR. This process is runnable. refer to Chapter 6. "Seeded Function Activity Definitions". select the process in the navigator tree and then select Properties from the Edit menu. For more information about individual function activities. Each node of this process is numbered for referencing. which comprise the 3 nodes that appear in the workflow diagram. The following diagram depicts the Change Order Process process. The workflow then proceeds to the Change Order Notification subprocess in node 2. The Change Order Process workflow begins at node 1 with the Start activity.

This process can also be initiated from an error message by selecting the Notify option. The purpose of this error handling process is to alert an administrator when an error occurs in a process and prompt the administrator to retry the process in error. Summary of the Change Order Process To view the properties of the Change Order Process process. The following diagram depicts the Change Order Process process.wft and is associated with the OM Change Order item type. which comprise the 3 nodes that appear in the workflow diagram. This process is runnable. Change Order Process is contained in the Seeded Data File oexwford. 4-4 Using Oracle Workflow in Oracle Order Management .OM Change Order Processes Activity Start (node 1) End (node 2) Function WF_STANDARD. then Notify from the Sales Order form. which indicates that it can be assigned to a transaction type.NOOP Result Type None None Required Yes Yes OM Change Order Processes Change Order Process When you change an order. The Details property page of the process activity indicates that Change Order Process has an error item type of WFERROR. This process sends notification that the order has been changed.NOOP WF_STANDARD. Each node of this process is numbered for referencing. you can select Actions. you see that the process consists of 3 unique activities. which initiates the Change Order Process. select the process in the navigator tree and then select Properties from the Edit menu. This item type is associated with the RETRY_ONLY error process. When you display the Process window for the Change Order Process. This error process is initiated only when an unexpected error with Oracle Workflow is encountered in the process.

Generic with Header Level Invoice Interface Order Flow . After the notification is sent.Return with Approval ■ ■ For more information regarding the OM Order Header item type.Generic Order Flow . Activity Start (node 1) End (node 2) Function WF_STANDARD. refer to Chapter 6. For more information about individual function activities. the process continues on to the End subprocess in node 3.NOOP WF_STANDARD. refer to Chapter 1. "Introduction". "Seeded Function Activity Definitions". The workflow then proceeds to the Change Order Notification subprocess in node 2.NOOP Result Type None None Required Yes Yes OM Order Header Processes The following section discusses the three workflows associated with the OM Order Header item type: ■ Order Flow .OM Order Header Processes The Change Order Process workflow begins at node 1 with the Start activity. Change Order Process Activities The following table provides descriptions of each activity in Change Order Process. Seeded Workflow Definitions 4-5 .

When you display the Process window for the Order Flow .Generic workflow process is the most often used workflow in Oracle Order Management. Order Flow .Generic is contained in the Seeded Data File oexwford. This process is runnable. The following diagram depicts the Order Flow .Generic. This error process is initiated only when an unexpected error with Oracle Workflow is encountered in the process. Transaction types determine which processes are attached to an order.wft and is associated with the OM Order Header item type. select the process in the navigator tree and then select Properties from the Edit menu.Order ■ Order Flow . 4-6 Using Oracle Workflow in Oracle Order Management . you see that the process consists of 2 unique activities and 2 subprocesses.Generic process.Generic Process To view the properties of the Order Flow . Manual Close . refer to the Oracle Order Management Implementation Suite.Order.Generic is associated with the following OM Order Header subprocesses: ■ Book . The Details property page of the process activity indicates that the Order Flow Generic process has an error item type of WFERROR. which comprise the 4 nodes that appear in the workflow diagram. Order Flow .Generic process contains subprocesses to verify that an order is booked and closed properly.Generic The Order Flow . The Order Flow .Generic is initiated if it is assigned to the transaction type for the order. For more information on defining transaction types.OM Order Header Processes Order Flow . This item type is associated with the RETRY_ONLY error process. Each node of this process is numbered for referencing. Summary of the Order Flow . which indicates that it can be assigned to a transaction type.Generic process. The purpose of this error handling process is to alert an administrator when an error occurs in a process and prompt the administrator to retry the process in error.

Order Flow .Order.NOOP Result Type None None Required Yes Yes Order Flow . the process continues on to the Close .Generic Activities The following table provides descriptions of each activity in the Order Flow Generic process. refer to Chapter 6.Generic with Header Level Invoice Interface workflow process can only end once the order is successfully closed. "Seeded Function Activity Definitions". After the order is closed. The workflow then proceeds to the Book . Manual subprocess in node 2.NOOP WF_STANDARD. the process closes the order.Generic with Header Level Invoice Interface first ensures that the order is booked before generating the invoice.Order subprocess in node 3. the process interfaces with Oracle Receivables to generate an invoice for the order.Generic with Header Level Invoice Interface The Order Flow . Upon completion of the invoice interface. When you submit a sales order that requires an invoice. For more information about individual activities. The Order Flow .Generic workflow begins at node 1 with the Enter activity. Activity Enter (node 1) End (node 2) Function WF_STANDARD. the process ends. Once the order is booked. the Order Flow . Seeded Workflow Definitions 4-7 .Generic with Header Level Invoice Interface is a workflow process that is initiated when you enter a sales order in Oracle Order Management.OM Order Header Processes The Order Flow . After booking is complete.

Order.Generic with Header Level Invoice Interface process. Each node of this subprocess is numbered for referencing.Generic with Header Level Invoice Interface process. you see that the process consists of 2 unique activities and 3 subprocesses. select the process in the navigator tree and then select Properties from the Edit menu. This item type is associated with the RETRY_ONLY error process. The following diagram depicts the Order Flow .wft and is associated with the OM Order Header item type. This process is runnable. When you display the Process window for the Order Flow . The Order Flow . The Details property page of the process activity indicates that the Order Flow Generic with Header Level Invoice Interface process has an error item type of WFERROR.Generic with Header Level Invoice Interface.OM Order Header Processes Order Flow . After an invoice is 4-8 Using Oracle Workflow in Oracle Order Management . The workflow then proceeds to the Book .Order subprocess in node 3. the process continues on to the Header Level Invoice Interface . The purpose of this error handling process is to alert an administrator when an error occurs in a process and prompt the administrator to retry the process in error. Summary of the Order Flow .Generic with Header Level Invoice Interface Process To view the properties of the Order Flow .Generic workflow begins at node 1 with the Enter activity. Manual subprocess in node 2.Generic with Header Level Invoice Interface is contained in the Seeded Data File oexwford. This subprocess initiates the interface with Oracle Receivables to generate an invoice for the order. which indicates that it can be assigned to a transaction type. which comprise the 5 nodes that appear in the workflow diagram. Once the order is booked. This error process is initiated only when an unexpected error with Oracle Workflow is encountered in the process.

OM Order Header Processes generated.Return with Approval process ends after the return order is closed. Seeded Workflow Definitions 4-9 . The approving manager can also decline authorization for the return.Return with Approval is contained in the Seeded Data File oexwford. Activity Enter (node 1) End (node 2) Function WF_STANDARD.Generic with Header Level Invoice Interface Activities The following table provides descriptions of each activity in the Order Flow Generic with Header Level Invoice Interface process.Return with Approval The Order Flow . ■ The Order Flow . The process ends in node 5 after the order is successfully closed. Returns must be booked and closed using the same processes as a sales order.Order process in node 4.Order. Once the approving manager authorizes the return.wft and is associated with the OM Order Header item type.Return with Approval workflow process is initiated when you submit a return on a sales order in Oracle Order Management. "Seeded Function Activity Definitions".Order ■ ■ Order Flow .NOOP Result Type None None Required Yes Yes Order Flow . Order Flow . the process ends. the process moves to the Close . the process first books the return and then sends a notification the verify that the return is authorized.Order Close . For more information about individual activities. Manual Approve Return . The Order Flow .Return with Approval workflow process is associated with the following OM Order Header subprocesses: ■ Book . The order is not eligible for return. The can end with a result of rejected if: ■ The approving manager does not authorize the return. When you submit a return in Oracle Order Management.NOOP WF_STANDARD. refer to Chapter 6.

The following diagram depicts the Order Flow . Order Flow .Return with Approval process. This subprocess sends notification to verify that the return is authorized. select the process in the navigator tree and then select Properties from the Edit menu.OM Order Header Processes Summary of the Order Flow . This process is runnable. After the authorization status is determined. This error process is initiated only when an unexpected error with Oracle Workflow is encountered in the process. 4-10 Using Oracle Workflow in Oracle Order Management . The Order Flow .Generic workflow begins at node 1 with the Enter activity.Order. The purpose of this error handling process is to alert an administrator when an error occurs in a process and prompt the administrator to retry the process in error. Each node of this subprocess is numbered for referencing. which indicates that it can be assigned to a transaction type. the process continues on to the Approve Return . The Details property page of the process activity indicates that the Order Flow Return with approval process has an error item type of WFERROR.Return with Approval process. the workflow process resumes and moves to the Close . Manual subprocess in node 2.Return with Approval Process To view the properties of the Order Flow . When you display the Process window for the Order Flow . you see that the process consists of 2 unique activities and 3 subprocesses.Order subprocess in node 3. This item type is associated with the RETRY_ONLY error process.Return with Approval. The workflow then proceeds to the Book . the process ends. Once the order is booked. which comprise the 5 nodes that appear in the workflow diagram.Order process in node 4. After the order is successfully closed.Return with Approval Activities The following table provides descriptions of each activity in the Order Flow Return with Approval process.

refer to Chapter 6.Return for Credit Only Line Flow .Return for Credit with Receipt Line Flow .Return for Credit with Receipt and Approval Line Flow .Generic.Generic with Header Level Invoice Interface Line Flow . Bill Only Line Flow .Generic.Generic with Authorize to Ship (RLM) Line Flow . With Export Compliance Line Flow .NOOP Result Type None None Required Yes Yes OM Order Line The following section discusses the workflow processes associated with the OM Order Line item type: ■ Line Flow .Generic.Generic Line Flow .Return for Credit Only with Approval Line Flow .ATO Item Line Flow .Standard Service ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ Seeded Workflow Definitions 4-11 .NOOP WF_STANDARD. Bill Only with Inventory Interface Line Flow .Configuration with Authorize to Ship (RLM) Line Flow .Generic.ATO Model Line Flow .Configuration Line Flow .OM Order Line For more information about individual activities.Generic. with Repricing at Fulfillment Line Flow . Ship Only Line Flow .Standard Service Line Flow . "Seeded Function Activity Definitions". Activity Enter (node 1) End (node 2) Function WF_STANDARD.

Summary of the Line Flow . The Details property page of the process activity indicates that the Line Flow . To initiate the Line Flow . create the supply for the assemble to order item.ATO Item Process To view the properties of the Line Flow .ATO Item process has an error item type of WFERROR.ATO Item process.Line ■ ■ ■ ■ ■ The Line Flow . select the process in the navigator tree and then select Properties from the Edit menu. and closing the line. The purpose of this error handling process is to 4-12 Using Oracle Workflow in Oracle Order Management .Line Create Supply Order .Line Close . ATO items are associated with Oracle Configure to Order.ATO Item process is contained in the Seeded Data File oexwford. The Line Flow .ATO Item workflow process supports ATO item lines only. This process is runnable.ATO Item process can only end after the line is closed. Line Flow . The Line Flow .Line Schedule .ATO Item The Line Flow . the process runs through several subprocess that schedule the line.ATO Item workflow process: ■ Enter . The following subprocess are contained in the Line Flow . This item type is associated with the RETRY_ONLY error process. prepare for shipping. Manual Ship . To learn more about implementing Oracle Configure to Order.wft and is associated with the OM Order Line item type. When you enter an order line in Oracle Order Management. which indicates that it can be assigned to a transaction type. Manual Invoice Interface . "Introduction".OM Order Line For more information regarding the OM Order Line item type. refer to the Oracle Configure to Order Implementation Manual. and can be assigned to ATO Item lines instead of the Line Flow-Generic. interface with Oracle Receivables for invoicing. refer to Chapter 1. you must enter an order in Oracle Order Management.ATO Item process.Line.ATO Item workflow process is initiated when an item on a sales order line is entered as an Assemble-to-Order (ATO) item.Line.

The following diagram depicts the Line Flow . When scheduling for the line is complete the Create Supply Order . After the order is booked the workflow process proceeds to the Schedule . When you display the Process window for the Line Flow . Each node of this subprocess is numbered for referencing. Manual subprocess is Seeded Workflow Definitions 4-13 . This subprocess ensures that the order is booked before proceeding with the rest of the line flow.Line subprocess in node 2. The Line Flow .Line.Line. The Ship . which comprise the 9 nodes that appear in the workflow diagram. you see that the process consists of 3 unique activities and 6 subprocesses. Manual subprocess is initiated.ATO Item process. This error process is initiated only when an unexpected error with Oracle Workflow is encountered in the process.ATO Item workflow begins at node 1 with the Enter .OM Order Line alert an administrator when an error occurs in a process and prompt the administrator to retry the process in error.ATO Item.Line subprocess.

the line is closed and the subprocess ends.ATO Model The Line Flow . The following subprocess are contained in the Line Flow .ATO Item process.Generic.Line ■ ■ ■ ■ 4-14 Using Oracle Workflow in Oracle Order Management . refer to the Oracle Configure to Order Implementation Manual. The Line Flow . To initiate the Line Flow .ATO Model process.Line. In node 7 the workflow interfaces with Oracle Receivables to create an invoice for the line.ATO Model process can only end after the line is closed.Deferred (node 5) WF_STANDARD.DEFER Fulfill (node 6) End (node 9) OE_FULFILL_WF. Manual Invoice Interface . For more information about individual activities. The Fulfill . For more information about implementing Oracle Configure to Order. Line Flow .ATO Item Activities The following table provides descriptions of each activity in the Line Flow . After the invoice interface is complete. you must enter an order in Oracle Order Management.START_ FULFILLMENT WF_STANDARD. refer to Chapter 6. "Seeded Function Activity Definitions".ATO Model workflow process is initiated when an item on a sales order line is entered as an Assemble-to-Order (ATO) model.Deferred activity in node 5 moves line fulfillment to the background engine. and can be assigned to ATO Model lines instead of the Line Flow .Line.OM Order Line initiated after supply is created for the line. ATO is associated with Oracle Configure to Order. The Line Flow .ATO Model workflow process: ■ Enter .NOOP Line Flow .Line Schedule . Activity Function Result Type None None None Required Yes Yes Yes Fulfill .ATO Model workflow process supports ATO model lines only. Deferred Close .Line Create Configuration .

This item type is associated with the RETRY_ONLY error process. The following diagram depicts the Line Flow . you see that the process consists of 3 unique activities and 5 subprocesses. which indicates that it can be assigned to a transaction type.ATO Model process.ATO Model Process To view the properties of the Line Flow . select the process in the navigator tree and then select Properties from the Edit menu. The purpose of this error handling process is to alert an administrator when an error occurs in a process and prompt the administrator to retry the process in error.ATO Item process. Each node of this subprocess is numbered for referencing. This process is runnable. This error process is initiated only when an unexpected error with Oracle Workflow is encountered in the process.OM Order Line The Line Flow . Seeded Workflow Definitions 4-15 .ATO Model process has an error item type of WFERROR.wft and is associated with the OM Order Line item type.ATO Model process is contained in the Seeded Data File oexwford. The Details property page of the process activity indicates that the Line Flow . which comprise the 8 nodes that appear in the workflow diagram.ATO Model. Summary of the Line Flow . When you display the Process window for the Line Flow .

Line. refer to Chapter 6. The Fulfill .START_ FULFILLMENT WF_STANDARD.ATO Model process. End).Eligible activity by progressing the order line or by running the Autocreate Config batch program.NOOP Line Flow . To initiate the Line Flow . Activity Function Result Type None None None Required Yes Yes Yes Fulfill . refer to the Oracle Configure to Order Implementation Manual. the workflow interfaces with Oracle Receivables to create an invoice for the line.ATO Model workflow begins at node 1 with the Enter .Line subprocess in node 2.Line subprocess.OM Order Line The Line Flow . After the invoice interface is complete.Deferred activity in node 4 moves line fulfillment to the background engine. Invoice Interface .Configuration The Line Flow .Line. Manual subprocess is initiated.Deferred (node 5) WF_STANDARD.Line) and the subprocess ends (node 8.Configuration workflow process: ■ Enter . To learn more about implementing Oracle Configure to Order. This workflow works only with ATO configuration items and must be assigned specifically to configuration lines during the implementation process. the line is closed (node 7. In node 6. you must move an ATO model line through Create Configuration . and starts the Line Flow .Line 4-16 Using Oracle Workflow in Oracle Order Management .DEFER Fulfill (node 6) End (node 9) OE_FULFILL_WF. After the order is booked the workflow process proceeds to the Schedule . Line Flow . The following subprocess are contained in the Line Flow . When scheduling for the line is complete the Create Configuration .Configuration process. This subprocess ensures that the order is booked before proceeding with the rest of the line flow. Close .ATO Model Activities The following table provides descriptions of each activity in the Line Flow . Deferred. For more information about individual activities. "Seeded Function Activity Definitions".Configuration process. links it to the order.Configuration workflow process is associated with Oracle Configure to Order. This creates the configuration item.

which indicates that it can be assigned to a transaction type.OM Order Line ■ Create Manufacturing Configuration Data . Seeded Workflow Definitions 4-17 .Line ■ ■ ■ The Line Flow .Configuration process. Each node of this subprocess is numbered for referencing.Configuration process can only end after the line is closed. The purpose of this error handling process is to alert an administrator when an error occurs in a process and prompt the administrator to retry the process in error. The following diagram depicts the Line Flow . which comprise the 8 nodes that appear in the workflow diagram. This process is runnable.Configuration. Manual Create Supply Order .Configuration process is contained in the Seeded Data File oexwford. Summary of the Line Flow .wft and is associated with the OM Order Line item type. When you display the Process window for the Line Flow . The Details property page of the process activity indicates that the Line Flow Configuration process has an error item type of WFERROR. Manual Ship .Line. Manual Close . select the process in the navigator tree and then select Properties from the Edit menu.Configuration Process To view the properties of the Line Flow . The Line Flow .Line. you see that the process consists of 4 unique activities and 4 subprocesses.Configuration process. This error process is initiated only when an unexpected error with Oracle Workflow is encountered in the process.Line. This item type is associated with the RETRY_ONLY error process.

Line Flow . refer to Chapter 6. the Ship .Deferred (node 5) WF_STANDARD. "Seeded Function Activity Definitions".NOOP Result Type None None None Required Yes Yes Yes Fulfill . the process ends (node 8). Manual subprocess in node 3.Deferred activity moves fulfillment to the background engine.Line. The process initiates the Close . Manual subprocess is initiated. Manual subprocess. In node 2.Line.Line subprocess in node 7.OM Order Line The Line Flow .Line. For more information about individual activities.Configuration Activities The following table provides descriptions of each activity in the Line Flow Configuration process. After the line is successfully closed.Configuration workflow begins at node 1 with the Start activity. then the Create Supply Order . the Fulfill . Once these subprocess are completed. Activity Start (node 1) Function WF_STANDARD.DEFER Fulfill (node 6) OE_FULFILL_WF.START_ FULFILLMENT 4-18 Using Oracle Workflow in Oracle Order Management . In node 5. the process runs the Create Manufacturing Configuration Data .

The Line Flow .Line.Configuration with Authorize to Ship (RLM) workflow process is associated with Oracle Release Management users. Manual Create Supply Order .Configuration with Authorize to Ship (RLM) process is contained in the Seeded Data File oexwford.Line. this process initiates. Manual Close .Line.Configuration with Authorize to Ship (RLM) workflow process: ■ Create Manufacturing Configuration Data . If the items on the line require authorization before shipping.Configuration with Authorize to Ship (RLM) Note: This process is not currently used in Oracle Order Management is listed for reference purposes only. Seeded Workflow Definitions 4-19 . The following subprocess are contained in the Line Flow . This workflow is specific to Oracle Release Management users and must be assigned during the implementation process.Configuration with Authorize to Ship (RLM) ensures that a line is eligible for shipping. The Line Flow .Line ■ ■ ■ ■ The Line Flow .NOOP Result Type None Required Yes Line Flow . Manual Authorized to Ship . Do not use this process when assigning processes to transaction types.Line Ship . you must enter an order in Oracle Order Management.Configuration with Authorize to Ship (RLM) process. refer to the Oracle Release Management Implementation Manual.OM Order Line Activity End (node 8) Function WF_STANDARD. Oracle Corporation does not provide support for this workflow process.wft and is associated with the OM Order Line item type. To learn more about implementing Oracle Release Management. To initiate the Line Flow . Line Flow .Configuration with Authorize to Ship (RLM) process can only end after the line is closed.

When you display the Process window for the Line Flow . This process is runnable.OM Order Line Summary of the Line Flow . which comprise the 10 nodes that appear in the workflow diagram. The purpose of this error handling process is to alert an administrator when an error occurs in a process and prompt the administrator to retry the process in error.Configuration with Authorize to Ship (RLM). This item type is associated with the RETRY_ONLY error process. This error process is initiated only when an unexpected error with Oracle Workflow is encountered in the process. The following diagram depicts the Line Flow . Each node of this subprocess is numbered for referencing. 4-20 Using Oracle Workflow in Oracle Order Management .Configuration with Authorize to Ship (RLM) Process To view the properties of the Line Flow . The Details property page of the process activity indicates that the Line Flow Configuration with Authorize to Ship (RLM) process has an error item type of WFERROR. which indicates that it can be assigned to a transaction type. you see that the process consists of 5 unique activities and 5 subprocesses.Configuration with Authorize to Ship (RLM) process. select the process in the navigator tree and then select Properties from the Edit menu.Configuration with Authorize to Ship (RLM) process.

created.Configuration with Authorize to Ship (RLM) Activities The following table provides descriptions of each activity in the Line Flow Configuration with Authorize to Ship (RLM) process. When you save an order line in Oracle Order Management.START_ FULFILLMENT WF_STANDARD. invoiced. shipped.Check Status activity. Manual subprocess in node 3 and the Create Supply Order . Activity Start (node 1) Configuration . Manual subprocess in node 6. "Seeded Function Activity Definitions". the process verifies that the order is booked before proceeding. the Authorized to Ship . Once these subprocess are completed. shipping and Seeded Workflow Definitions 4-21 . Once booking is verified. and closed. After the line is successfully closed.NOOP Result Type None Config Data Results None None None Required Yes Yes Yes Yes Yes Line Flow . invoicing. In node 2.Check Status (node 2) Fulfill . the process continues with scheduling.Deferred (node 7) Fulfill (node 8) End (node 10) Function WF_STANDARD.NOOP CTO_WORKFLOW.Line.Line subprocess is initiated in node 5.Generic The Line Flow . the Line Flow . it initiates when no other flow is determined necessary for a line.Configuration with Authorize to Ship (RLM) workflow begins at node 1 with the Start activity. the Fulfill . Manual subprocess in node 4. the process ends (node 10). refer to Chapter 6. The process initiates the Close . fulfilled. For more information about individual activities.Line.OM Order Line The Line Flow . Once status is verified the process moves through the Create Manufacturing Configuration Data Line.DEFER OE_FULFILL_WF. scheduled.Line subprocess in node 9. fulfillment. then Ship . Line Flow . If you use several different line flows in your business.Generic workflow can act as a default. supply creation.Generic process is a workflow process that is initiated when you save a sales order line in Oracle Order Management.Flow Generic process contains several subprocesses to ensure that an order line is properly entered. In node 7.CHECK_ RESERVATION_STATUS_WF WF_STANDARD. the process runs the Configuration .Deferred activity moves fulfillment to the background engine. The Line .

wft and is associated with the OM Order Line item type. This error process is initiated only when an unexpected error with Oracle Workflow is encountered in the process. The purpose of this error handling process is to alert an administrator when an error occurs in a process and prompt the administrator to retry the process in error. This process is runnable. The Details property page of the process activity indicates that the Line Flow Generic process has an error item type of WFERROR. Several of these actions are performed in the following workflow subprocesses contained in Line Flow .Generic process is contained in the Seeded Data File oexwford.Line.Generic. 4-22 Using Oracle Workflow in Oracle Order Management .Line Create Supply Order . which indicates that it can be assigned to a transaction type.Generic process.Generic can only end once the line is successfully closed.Line. The Line Flow . This item type is associated with the RETRY_ONLY error process.Line ■ ■ ■ ■ ■ Line Flow .Generic process. select the process in the navigator tree and then select Properties from the Edit menu. The following diagram depicts the Line Flow . Manual Invoice Interface . Manual Ship .Line Schedule .Line Close . you see that the process consists of 3 unique activities and 6 subprocesses. When you display the Process window for the Line Flow . Each node of this subprocess is numbered for referencing. which comprise the 9 nodes that appear in the workflow diagram. Summary of the Line Flow .Generic: ■ Enter .Generic Process To view the properties of the Line Flow .OM Order Line closing.

refer to Chapter 6. In node 2. In node 5. the Fulfill .Line. Node 7 is the Invoice Interface . the process attempts to schedule the line for the order using the Schedule .Generic workflow begins at node 1 with the Enter .Line subprocess that generates invoicing information for the line. This subprocess verifies that the order is booked before proceeding with the remainder of the workflow.START_ FULFILLMENT Result Type None None Required Yes Yes Seeded Workflow Definitions 4-23 . For more information about individual activities.Line subprocess at node 8. After supply is created for the line.Line subprocess.Deferred activity moves fulfillment to the background engine.Line subprocess.Generic Activities The following table provides descriptions of each activity in the Line Flow . The process initiates the Close . Manual subprocess in node 4 initiates. Activity Fulfill .Deferred (node 5) Fulfill (node 6) Function WF_STANDARD. Line Flow .Line subprocess is initiated in node 3.OM Order Line The Line Flow . After the line is successfully closed. "Seeded Function Activity Definitions". the Ship . the process ends (node 9). The Create Supply .DEFER OE_FULFILL_WF.Generic process.

Manual Authorized to Ship .NOOP Result Type None Required Yes Line Flow . The Line Flow . The following subprocess are contained in the Line Flow .Generic with Authorize to Ship (RLM) process can only end after the line is successfully closed.wft and is associated with the OM Order Line item type.Line. The Line .Flow Generic with Authorize to Ship (RLM) process is specific to Oracle Release Management users. refer to the Oracle Release Management Implementation Manual.Line Create Supply Order .Generic.Configuration with Authorize to Ship (RLM) workflow process: ■ Enter . and enables you to authorize order lines for shipping.Line.OM Order Line Activity End (node 8) Function WF_STANDARD.Generic with Authorize to Ship (RLM) process is contained in the Seeded Data File oexwford.Generic with Authorize to Ship (RLM) process. 4-24 Using Oracle Workflow in Oracle Order Management . Line Flow . Manual Invoice Interface .Generic with Authorize to Ship (RLM) contains all of the subprocess and activities contained in Line Flow .Generic with Authorize to Ship (RLM) The Line Flow . To initiate the Line Flow . To learn more about implementing Oracle Release Management. enter an order line in Oracle Order Management.Line Schedule .Line Ship .Line Close .Generic with Authorize to Ship (RLM) process is a workflow process that is initiated when you save a sales order line in Oracle Order Management. it must be assigned during the implementation process. as well as the Authorize to Ship (RLM) subprocess. Because this workflow is specific to Oracle Release Management users.Line ■ ■ ■ ■ ■ ■ The Line Flow .

Generic with Authorize to Ship (RLM) process.Generic with Authorize to Ship (RLM) Process To view the properties of the Line Flow . This subprocess verifies that the order is booked before proceeding with the remainder of the workflow. Seeded Workflow Definitions 4-25 .Generic with Authorize to Ship (RLM) process. you see that the process consists of 3 unique activities and 7 subprocesses.OM Order Line Summary of the Line Flow . When you display the Process window for the Line Flow . This error process is initiated only when an unexpected error with Oracle Workflow is encountered in the process. Each node of this subprocess is numbered for referencing.Generic with Authorize to Ship (RLM).Generic with Authorize to Ship (RLM) workflow begins at node 1 with the Enter . This process is runnable. select the process in the navigator tree and then select Properties from the Edit menu. This item type is associated with the RETRY_ONLY error process. which indicates that it can be assigned to a transaction type. The Line Flow . which comprise the 10 nodes that appear in the workflow diagram. The following diagram depicts the Line Flow .Line subprocess. The purpose of this error handling process is to alert an administrator when an error occurs in a process and prompt the administrator to retry the process in error. The Details property page of the process activity indicates that the Line Flow Generic with Authorize to Ship (RLM) process has an error item type of WFERROR.

START_ FULFILLMENT WF_STANDARD. Line Flow .Line subprocess that generates invoicing information for the line. fulfilled.Generic with Authorize to Ship (RLM) Activities The following table provides descriptions of each activity in the Line Flow . Manual subprocess at node 5 initiates. After approval is determined.Deferred (node 6) Fulfill (node 7) End (node 10) Function WF_STANDARD.Line subprocess. The Create Supply .Line subprocess is initiated in node 3.Line. Node 8 is the Invoice Interface . Activity Fulfill . the Fulfill . In node 6. The Oracle Release Management user Authorized to Ship . created. shipped.Generic with Header Level Invoice Interface process verifies that the order is booked before 4-26 Using Oracle Workflow in Oracle Order Management . the process attempts to schedule the line for the order using the Schedule .Line.Deferred activity moves fulfillment to the background engine. For more information about individual activities. The Line Flow .Generic.Generic with Header Level Invoice Interface contains all of the subprocess and activities contained in Line Flow . the Ship . The Line .NOOP Result Type None None None Required Yes Yes Yes Line Flow . scheduled. Deferred subprocess. the Line Flow . After the line is successfully closed. "Seeded Function Activity Definitions".Line subprocess with the Header Level Invoice Interface .Generic with Header Level Invoice Interface workflow contains several subprocesses to ensure that an order line is properly entered.Generic with Header Level Invoice Interface process is a workflow process that is initiated when you save a sales order line in Oracle Order Management.Flow Generic with Header Level Invoice Interface process interfaces with Oracle Receivables to generate invoicing information for an order line. but replaces the Invoice Interface .OM Order Line In node 2. Line Flow . the process ends (node 10).Generic with Header Level Invoice Interface The Line Flow .Generic with Authorize to Ship (RLM) process.Line subprocess at node 9. When you save an order line in Oracle Order Management. The process initiates the Close . and closed. The process works with the seeded header flow to support header level invoicing.Line subprocess at node 4 verifies that the line is approved for shipping. invoiced.DEFER OE_FULFILL_WF. refer to Chapter 6.

invoicing.Generic with Header Level Invoice Interface process. This item type is associated with the RETRY_ONLY error process. Deferred Close .Generic with Header Level Invoice Interface: ■ Enter . the process continues with scheduling. The Details property page of the process activity indicates that the Line Flow Generic with Header Level Invoice Interface process has an error item type of WFERROR. fulfillment. Manual Header Level Invoice Interface .Generic with Header Level Invoice Interface process. Once booking is verified. select the process in the navigator tree and then select Properties from the Edit menu.Line. When you display the Process window for the Line Flow .Line Create Supply Order .Line Schedule . Seeded Workflow Definitions 4-27 .wft and is associated with the OM Order Line item type.Line.OM Order Line proceeding. you see that the process consists of 1 unique activity and 6 subprocesses. This error process is initiated only when an unexpected error with Oracle Workflow is encountered in the process.Generic with Header Level Invoice Interface can only end once the line is successfully closed. Several of these activities are performed in the following workflow subprocesses contained in Line Flow . Each node of this subprocess is numbered for referencing. The following diagram depicts the Line Flow .Line. This process is runnable. shipping and closing. supply creation. Summary of the Line Flow . which indicates that it can be assigned to a transaction type.Line ■ ■ ■ ■ ■ Line Flow .Generic with Header Level Invoice Interface Process To view the properties of the Line Flow . The purpose of this error handling process is to alert an administrator when an error occurs in a process and prompt the administrator to retry the process in error. Manual Ship . The Line Flow . which comprise the 7 nodes that appear in the workflow diagram.Generic with Header Level Invoice Interface.Generic with Header Level Invoice Interface process is contained in the Seeded Data File oexwford.

Line. In node 5.Line subprocess. Line Flow .Generic with Header Level Invoice Interface process. followed by the End activity at node 7. The Line Flow .NOOP Result Type None Required Yes Line Flow .Generic. Node 6 is the Close . For more information about Oracle Order Management workflow activities. the process attempts to schedule the line for the order using the Schedule .OM Order Line The Line Flow . the Ship . Manual subprocess in node 4 initiates.Line subprocess. With Export Compliance process 4-28 Using Oracle Workflow in Oracle Order Management .Generic. In node 2.Generic with Header Level Invoice Interface Activities The following table provides a description of the activity in the Line Flow . With Export Compliance process is a workflow process that is initiated when you save a sales order line in Oracle Order Management that requires exportation. the Header Level Invoice Interface . Deferred activity moves header level invoice interfacing to the background engine. This subprocess verifies that the order is booked before proceeding with the remainder of the workflow. refer to Chapter 6. This enables the workflow to proceed.Generic.Line subprocess is initiated in node 3. The Create Supply .Line. Activity End (node 7) Function WF_STANDARD. With Export Compliance The Line Flow .Line subprocess.Generic workflow begins at node 1 with the Enter . "Seeded Function Activity Definitions". After supply is created for the line.

and closed.Generic.Generic. Line Flow . as well as the Export Compliance Screening .Generic. select the process in the navigator tree and then select Properties from the Edit menu.Line Create Supply Order . With Export Compliance process verifies that the order is booked before proceeding. invoicing. supply creation. the Line Flow .Line.Line ■ ■ ■ ■ ■ ■ Line Flow . shipping and closing.Generic. The Line Flow . Manual Ship .Generic. Manual Invoice Interface .Line Export Compliance Screening . The Line . Seeded Workflow Definitions 4-29 . This process is runnable.Generic.Line. With Export Compliance: ■ Enter . Once booking is verified. With Export Compliance process. scheduled. With Export Compliance process is contained in the Seeded Data File oexwford.Generic. shipped. With Export Compliance process contains several subprocesses to ensure that the order line is properly entered. which indicates that it can be assigned to a transaction type.wft and is associated with the OM Order Line item type. fulfillment. When you save an order line in Oracle Order Management. the process continues with scheduling. invoiced. Summary of the Line Flow . fulfilled.Generic. With Export Compliance contains all of the subprocess and activities contained in Line Flow .Line Close . With Export Compliance can only end once the line is successfully closed. the Line Flow . With Export Compliance workflow process initiates. When an order line is submitted that must comply with the United States Bureau of Export Administration’s Denied Party listing.Line subprocess.OM Order Line contains a subprocess that performs Denied Party screening according to United States Bureau of Export Administration’s Denied Party listing.Flow Generic.Line Schedule . With Export Compliance Process To view the properties of the Line Flow . created. Several of these activities are performed in the following workflow subprocesses contained in Line Flow .Generic.

the process attempts to schedule the line for the order using the Schedule . The Create Supply . With Export Compliance process has an error item type of WFERROR. With Export Compliance process. which comprise the 10 nodes that appear in the workflow diagram.Line subprocess. the Ship . This error process is initiated only when an unexpected error with Oracle Workflow is encountered in the process. the Export Compliance Screening . In node 2.OM Order Line The Details property page of the process activity indicates that the Line Flow Generic. To comply with the United States Bureau of Export Administration’s Denied Party listing.Line subprocess. The Line Flow .Line subprocess at node 3 initiates.Line. With Export Compliance. the 4-30 Using Oracle Workflow in Oracle Order Management . Each node of this subprocess is numbered for referencing. Manual subprocess at node 5 initiates. If the line passes this screening process. This subprocess verifies that the order is booked before proceeding with the remainder of the workflow. you see that the process consists of 3 unique activities and 7 subprocesses.Generic. This item type is associated with the RETRY_ONLY error process. When you display the Process window for the Line Flow . After supply is created for the line. At node 6.Line subprocess is initiated in node 4.Generic With Export Compliance workflow begins at node 1 with the Enter . The following diagram depicts the Line Flow .Generic. then the process approves the line for exporting and continues. The purpose of this error handling process is to alert an administrator when an error occurs in a process and prompt the administrator to retry the process in error.

refer to Chapter 6. The only process is contained in the Seeded Data File oexwford. After the line is successfully closed. and closed.Line Invoice Interface .Line. Bill Only The Line Flow . the process continues with invoicing.Generic.Deferred activity moves fulfillment to the background engine. Bill Only process is used in a situation when only a bill for the order must be generated.Generic. Line Flow .wft and is associated with the OM Order Line item type.Line subprocess that generates invoicing information for the line. Bill Only: ■ Enter .Generic. Once booking is verified. the Line Flow .NOOP Result Type None None None Required Yes Yes Yes Line Flow .START_ FULFILLMENT WF_STANDARD. fulfilled.Generic.Generic With Export Compliance process. Bill Only ends once the line is successfully closed.Line ■ ■ Line Flow . The Line Flow . Bill Only process is a workflow process is used for order lines that do not require shipping. Node 8 is the Invoice Interface . Activity Fulfill . For more information about individual activities. Bill Only process verifies that the order is booked before proceeding.Generic.DEFER OE_FULFILL_WF. The process contains several subprocesses to ensure that the order line is properly entered. Several of these actions are performed in the following workflow subprocesses contained in Line Flow .Generic With Export Compliance Activities The following table provides descriptions of each activity in the Line Flow . "Seeded Function Activity Definitions". the process ends at node 10. and closing. fulfillment. Deferred Close . Seeded Workflow Definitions 4-31 .Generic. The process initiates the Close .OM Order Line Fulfill . invoiced. When you save an order line in Oracle Order Management.Deferred (node 6) Fulfill (node 7) End (node 10) Function WF_STANDARD.Line subprocess at node 9.

which indicates that it can be assigned to a transaction type. Bill Only. The process initiates the Close . At node 3. Bill Only Process To view the properties of the Line Flow . 4-32 Using Oracle Workflow in Oracle Order Management . The Details property page of the process activity indicates that the Line Flow Generic.Line subprocess.Generic.Generic. When you display the Process window for the Line Flow . After the line is successfully closed. This process is runnable. This subprocess moves the invoice interface to the background engine.Generic. Each node of this process is numbered for referencing. Bill Only workflow begins at node 1 with the Enter . the process ends at node 5. Bill Only process. the Invoice Interface Line.Generic. select the process in the navigator tree and then select Properties from the Edit menu. Bill Only process. The process attempts to fulfill the order at node 2. Bill Only process has an error item type of WFERROR. The purpose of this error handling process is to alert an administrator when an error occurs in a process and prompt the administrator to retry the process in error. The Line Flow . Line Flow . which comprise the 5 nodes that appear in the workflow diagram. This item type is associated with the RETRY_ONLY error process. This subprocess verifies that the order is booked before proceeding with the remainder of the workflow. This error process is initiated only when an unexpected error with Oracle Workflow is encountered in the process.Generic.Generic.OM Order Line Summary of the Line Flow . Deferred subprocess is initiated. Bill Only Activities The following table provides descriptions of each activity in the Line Flow Generic.Line subprocess at node 4. Bill Only process. you see that the process consists of 2 unique activities and 3 subprocesses. The following diagram depicts the Line Flow .

Generic.NOOP Result Type None None Required Yes Yes Line Flow . Bill Only with Inventory Interface process verifies that the order is booked before proceeding.Generic. Bill Only with Inventory Interface Process To view the properties of the Line Flow .Generic.Generic.Generic. fulfilled. Deferred Close . Once booking is verified.Line Invoice Interface .wft and is associated with the OM Order Line item type.START_ FULFILLMENT WF_STANDARD. invoiced. Bill Only with Inventory Interface ends after the line is successfully closed.OM Order Line For more information about individual activities. When you save an order line in Oracle Order Management. Bill Only with Inventory Interface process is contained in the Seeded Data File oexwford.Generic. Bill Only with Inventory Interface The Line Flow . The Line Flow . Bill Only with Inventory Interface process is used in a situation when only a bill for the order must be generated.Line.Generic. fulfillment. Bill Only with Inventory Interface process. the Line Flow . the process continues with invoicing. refer to Chapter 6. Activity Fulfill (node 2) End (node 5) Function OE_FULFILL_WF. Bill Only with Inventory Interface: ■ Enter .Line ■ ■ Line Flow . and closed. which indicates that it can be assigned to a transaction type. Several of these actions are performed in the following workflow subprocesses contained in Line Flow .Generic. Bill Only with Inventory Interface process is a workflow process that is initiated when you save a sales order line in Oracle Order Management.Generic. The Line Flow . Seeded Workflow Definitions 4-33 . "Seeded Function Activity Definitions". select the process in the navigator tree and then select Properties from the Edit menu. and closing. This process is runnable. Summary of the Line Flow . The process contains several subprocesses to ensure that the order line is properly entered.

Bill Only with Inventory Interface Activities The following table provides descriptions of each activity in the Line Flow Generic. At node 2 the Inventory Interface Non-Ship . At node 4. Bill Only with Inventory Interface process.Generic.Line. the Invoice Interface . The process initiates the Close .Generic. The Line Flow . Bill Only with Inventory Interface workflow begins at node 1 with the Enter . This error process is initiated only when an unexpected error with Oracle Workflow is encountered in the process. Line Flow . Bill Only with Inventory Interface. This item type is associated with the RETRY_ONLY error process. Deferred subprocess is initiated.Line subprocess at node 5.Generic. Bill Only with Inventory Interface process. Deferred subprocess is initiated. This subprocess verifies that the order is booked before proceeding with the remainder of the workflow. The following diagram depicts the Line Flow . After completion of that subprocess. Each node of this process is numbered for referencing.Line.OM Order Line The Details property page of the process activity indicates that the Line Flow Generic. the Line Flow .Generic. the process ends at node 6. 4-34 Using Oracle Workflow in Oracle Order Management . which comprise the 6 nodes that appear in the workflow diagram. Bill Only with Inventory Interface process attempts to fulfill the order at node 3.Line subprocess.Generic. The purpose of this error handling process is to alert an administrator when an error occurs in a process and prompt the administrator to retry the process in error. When you display the Process window for the Line Flow . This subprocess moves the invoice interface to the background engine. After the line is successfully closed. you see that the process consists of 2 unique activities and 4 subprocesses. Bill Only with Inventory Interface process has an error item type of WFERROR.

Line Create Supply Order .Generic. Seeded Workflow Definitions 4-35 . Ship Only process is a workflow process that is initiated when you save a sales order line in Oracle Order Management that does not require invoicing. the Line Flow .Generic process except that it does not include the Invoice Interface . An order line can require this when the rest of the order lines have already been shipped with an invoice for the order. Activity Fulfill (node 2) End (node 5) Function OE_FULFILL_WF.Line Schedule . Ship Only: ■ Enter . fulfillment. the process continues with scheduling. Ship Only process contains several subprocesses to ensure that an order line is properly entered. "Seeded Function Activity Definitions". Ship Only is associated with order lines that only require shipping.Line ■ ■ ■ ■ Line Flow .Generic.Line.OM Order Line For more information about individual activities. and closing.Flow Generic.Generic. Ship Only The Line Flow .Generic. Line Flow . refer to Chapter 6. Ship Only process is identical to the Line Flow .Line. and closed. fulfilled.Line activity. The Line . Once booking is verified. Manual Close . shipping. Ship Only ends after the line is successfully closed. When you save an order line in Oracle Order Management.NOOP Result Type None None Required Yes Yes Line Flow .Generic. Ship Only process verifies that the order is booked before proceeding. created. scheduled. supply creation. Note: The Line Flow . shipped. Several of these actions are performed in the following workflow subprocesses contained in Line Flow .Generic.START_ FULFILLMENT WF_STANDARD. Manual Ship .Generic.

the Fulfill . Ship Only process. After the line is successfully closed.Generic. When you display the Process window for the Line Flow . This error process is initiated only when an unexpected error with Oracle Workflow is encountered in the process. The process initiates the Close . The purpose of this error handling process is to alert an administrator when an error occurs in a process and prompt the administrator to retry the process in error. which indicates that it can be assigned to a transaction type.Generic.Generic. which comprise the 8 nodes that appear in the workflow diagram. The following diagram depicts the Line Flow .Line subprocess.Line subprocess. the process attempts to schedule the line for the order using the Schedule . the process ends at node 8.wft and is associated with the OM Order Line item type. the Ship .Generic. Ship Only process has an error item type of WFERROR. Ship Only workflow begins at node 1 with the Enter . Ship Only Process To view the properties of the Line Flow . Manual subprocess in node 4 initiates. After supply is created for the line.Generic. This process is runnable. Summary of the Line Flow . The Details property page of the process activity indicates that the Line Flow Generic.Line subprocess at node 7.Deferred activity moves fulfillment to the background engine. In node 2.Line. Ship Only process. The Create Supply . This item type is associated with the RETRY_ONLY error process. Ship Only process is contained in the Seeded Data File oexwford.OM Order Line The Line Flow . Ship Only.Line subprocess is initiated in node 3. The Line Flow .Generic. This subprocess verifies that the order is booked before proceeding with the remainder of the workflow. you see that the process consists of 3 unique activities and 5 subprocesses. In node 5. Each node of this subprocess is numbered for referencing. select the process in the navigator tree and then select Properties from the Edit menu. 4-36 Using Oracle Workflow in Oracle Order Management .

shipped. When you save an order line in Oracle Order Management.Line.Line subprocess. with Repricing at Fulfillment: ■ Enter . scheduled.NOOP Result Type None None None Required Yes Yes Yes Line Flow . as well as the Reprice . Several of these activities are performed in the following workflow subprocesses contained in Line Flow . Ship Only Activities The following table provides descriptions of each activity in the Line Flow Generic.Generic workflow process.Generic. invoicing.Generic.Line ■ ■ ■ ■ ■ Seeded Workflow Definitions 4-37 . Activity Fulfill . The Line . the Line Flow .Generic.Generic. supply creation. with Repricing at Fulfillment process verifies that the order is booked before proceeding. "Seeded Function Activity Definitions". Manual Ship .Generic. Ship Only process.Line Create Supply Order . Manual Reprice . invoiced. fulfillment.Line Invoice Interface . with Repricing at Fulfillment contains all of the subprocess and activities contained in the Line Flow . with Repricing at Fulfillment The Line Flow . Once booking is verified. the process continues with scheduling. shipping.Generic.START_ FULFILLMENT WF_STANDARD.Flow Generic with Repricing at Fulfillment process contains several subprocesses to ensure that an order line is properly entered. and closed.Line.Deferred (node 5) Fulfill (node 6) End (node 8) Function WF_STANDARD. repricing. and closing. with Repricing at Fulfillment process is a workflow process initiated when you save a sales order line in Oracle Order Management that requires repricing after the order line is fulfilled.Line Schedule . For more information about individual activities. Line Flow . repriced.DEFER OE_FULFILL_WF. fulfilled. created.OM Order Line Line Flow . refer to Chapter 6.

wft and is associated with the OM Order Line item type. with Repricing at Fulfillment process.Line Line Flow . This item type is associated with the RETRY_ONLY error process.Generic.Generic. Summary of the Line Flow . with Repricing at Fulfillment process has an error item type of WFERROR. This error process is initiated only when an unexpected error with Oracle Workflow is encountered in the process. which indicates that it can be assigned to a transaction type. which comprise the 10 nodes that appear in the workflow diagram. select the process in the navigator tree and then select Properties from the Edit menu. The Line Flow .Generic. with Repricing at Fulfillment process is contained in the Seeded Data File oexwford. The purpose of this error handling process is to alert an administrator when an error occurs in a process and prompt the administrator to retry the process in error. Each node of this subprocess is numbered for referencing.OM Order Line ■ Close . with Repricing at Fulfillment ends after the line is successfully closed. The Details property page of the process activity indicates that the Line Flow Generic. When you display the Process window for the Line Flow . with Repricing at Fulfillment. with Repricing at Fulfillment process. 4-38 Using Oracle Workflow in Oracle Order Management . you see that the process consists of 3 unique activities and 7 subprocesses. The following diagram depicts the Line Flow .Generic.Generic.Generic. with Repricing at Fulfillment Process To view the properties of the Line Flow . This process is runnable.

Generic. "Seeded Function Activity Definitions". the Ship . Manual subprocess in node 4 initiates.Line subprocess at node 9.Deferred (node 5) Function WF_STANDARD.Deferred activity moves fulfillment to the background engine. For more information about individual activities. refer to Chapter 6. After the line is repriced. the process attempts to schedule the line for the order using the Schedule . Once the line is successfully closed.Line subprocess is initiated in node 3. In node 5.Line subprocess. the Reprice . with Repricing at Fulfillment process. the Fulfill . Activity Fulfill . This subprocess verifies that the order is booked before proceeding with the remainder of the workflow. the process proceed to the Invoice Interface . the process ends at node 10. with Repricing at Fulfillment workflow begins at node 1 with the Enter .Line is initiated. After supply is created for the line. The Create Supply . with Repricing at Fulfillment Activities The following table provides descriptions of each activity in the Line Flow Generic. In node 2.Line subprocess at node 8. The process initiates the Close .Line.OM Order Line The Line Flow .Generic. At node 7.Line subprocess. Line Flow .DEFER Result Type None Required Yes Seeded Workflow Definitions 4-39 .

Return for Credit Only The Line Flow . When your customer returns partial quantity of an order. This item type is associated with the RETRY_ONLY error process.Return for Credit Only. This is an order line process. The purpose of this error handling process is to alert an administrator when an error occurs in a process and prompt the administrator to retry the process in error. The Details property page of the process activity indicates that the Line Flow Return for Credit Only process has an error item type of WFERROR.Line Invoice Interface . This process is runnable. When you display the Process window for the Line Flow . you see that the process consists of 1 unique activity and 3 subprocesses.Return for Credit Only: ■ Enter .wft and is associated with the OM Order Line item type. The Line Flow .Line.Return for Credit Only process.Return for Credit Only process is a workflow process is used for return orders submitted in Oracle Order Management that do not require receipt or approval.Return for Credit Only process is contained in the Seeded Data File oexwford.Return for Credit Only ends after the line is successfully closed.NOOP Result Type None None Required Yes Yes Line Flow .OM Order Line Activity Fulfill (node 6) End (node 10) Function OE_FULFILL_WF. This error process is initiated only when an unexpected error with Oracle Workflow is encountered in the process. Once booking is verified. Deferred Close . the process continues with invoicing and closing. Summary of the Line Flow . which 4-40 Using Oracle Workflow in Oracle Order Management . These activities are performed in the following workflow subprocesses contained in Line Flow . the Line Flow Return for Credit Only process verifies that the return is booked before proceeding.Line ■ ■ Line Flow . When you save a return order line in Oracle Order Management. which indicates that it can be assigned to a transaction type. select the process in the navigator tree and then select Properties from the Edit menu.Return for Credit Only Process To view the properties of the Line Flow . Oracle Order Management splits the return line so that customers can be issued credit for what was returned.START_ FULFILLMENT WF_STANDARD.

For more information about individual activities. Line Flow . After the line is successfully closed.Return for Credit Only Activities The following table provides a description for the End activity in the Line Flow Return for Credit Only process. At node 2 the process uses the Invoice Interface . The following diagram depicts the Line Flow . Activity End (node 10) Function WF_STANDARD. When your customer returns partial quantity of an order. the process ends at node 4.OM Order Line comprise the 4 nodes that appear in the workflow diagram.Return for Credit Only process. This is an order line process. Seeded Workflow Definitions 4-41 .Line. The process initiates the Close .Line subprocess at node 3. Deferred subprocess to generate the credit invoice.Return for Credit Only workflow begins at node 1 with the Enter Line subprocess. refer to Chapter 6.NOOP Result Type None Required Yes Line Flow . The Line Flow . "Seeded Function Activity Definitions". Each node of this subprocess is numbered for referencing. Oracle Order Management splits the return line so that customers can be issued credit for what was returned.Return for Credit Only with Approval The Line Flow . This subprocess verifies that the order is booked before proceeding with the remainder of the workflow.Return for Credit Only with Approval process is a workflow process is used for return orders submitted in Oracle Order Management that requires approval.

invoiced. The process then verifies that the return is approved before proceeding with the return.Return for Credit Only with Approval process is identical to the Line Flow . Once booking and approval are verified.Return for Credit Only with Approval process.Line ■ ■ Line Flow .wft and is associated with the OM Order Line item type. These activities are performed in the following workflow subprocesses contained in Line Flow .Return for Credit Only with Approval ends after the line is successfully closed.Return for Credit Only with Approval process contains several subprocesses to ensure that the return is properly entered. the process continues with invoicing and closing. The purpose of this error handling process is to alert an administrator when an error occurs in a process and prompt the administrator to retry the process in error. This item type is associated with the RETRY_ONLY error process. approved. This error 4-42 Using Oracle Workflow in Oracle Order Management . This process is runnable.Return for Credit Only with Approval: ■ Enter . When you save a return order line in Oracle Order Management. the Line Flow Return for Credit Only with Approval process verifies that the return is booked before proceeding. The Line Flow .Line. as well as the Wait for Approval block activity.Return for Credit Only with Approval Process To view the properties of the Line Flow . The Details property page of the process activity indicates that the Line Flow Return for Credit Only with Approval process has an error item type of WFERROR. Summary of the Line Flow .Return for Credit Only process except that it includes the Wait for Approval activity. Deferred Close . Line Flow .OM Order Line Note: The Line Flow .Return for Credit Only with Approval contains all of the subprocess and activities contained in the Return for Credit Only workflow process.Line Invoice Interface . which indicates that it can be assigned to a transaction type.Return for Credit Only with Approval process is contained in the Seeded Data File oexwford. select the process in the navigator tree and then select Properties from the Edit menu. and closed. The Line Flow .

Each node of this process is numbered for referencing. This subprocess verifies that the order is booked before proceeding with the remainder of the workflow. For more information about individual activities. the process ends at node 5.Line. Line Flow .Return for Credit Only with Approval process. Once approval is obtained.Return for Credit Only with Approval.WAITFORFLOW End (node 5) WF_STANDARD. Activity Function Result Type None None Required Yes Yes Wait for Approval (node 2) WF_STANDARD. you see that the process consists of 2 unique activity and 3 subprocesses.OM Order Line process is initiated only when an unexpected error with Oracle Workflow is encountered in the process. which comprise the 5 nodes that appear in the workflow diagram. The process initiates the Close .Line subprocess. refer to Chapter 6.Line subprocess at node 4. The Line Flow . Deferred subprocess at node 3 to generate the credit invoice. At node 2 the process encounters a block activity that requires the return order line to obtain approval before proceeding with the workflow. "Seeded Function Activity Definitions". The following diagram depicts the Line Flow . After the line is successfully closed.NOOP Seeded Workflow Definitions 4-43 .Return for Credit Only with Approval Activities The following table provides a description for the activities in the Line Flow Return for Credit Only with Approval process. the workflow proceeds to the Invoice Interface . When you display the Process window for the Line Flow .Return for Credit Only with Approval workflow begins at node 1 with the Enter .

This error process is 4-44 Using Oracle Workflow in Oracle Order Management . When your customer returns partial quantity of an order.Return for Credit with Receipt process is a workflow process used for returns that require inspection before credit is given. and closed. This is an order line process.wft and is associated with the OM Order Line item type. Summary of the Line Flow .Line.Line Invoice Interface . The Line Flow . Oracle Order Management splits the return line so that customers can be issued credit for what was returned. The purpose of this error handling process is to alert an administrator when an error occurs in a process and prompt the administrator to retry the process in error.Return for Credit with Receipt process.Return for Credit with Receipt process is contained in the Seeded Data File oexwford. invoiced. Deferred Close . This process is runnable. These activities are performed in the following workflow subprocesses contained in Line Flow . fulfilled. Once booking is verified. approved.Return for Credit with Receipt Process To view the properties of the Line Flow . This item type is associated with the RETRY_ONLY error process.Return for Credit with Approval contains all of the subprocess and activities contained in the Return for Credit workflow process. The Details property page of the process activity indicates that the Line Flow Return for Credit with Receipt process has an error item type of WFERROR. select the process in the navigator tree and then select Properties from the Edit menu. the Line Flow Return for Credit with Receipt process verifies that the return is booked before proceeding. invoicing and closing. The Line Flow . When you save a return order line in Oracle Order Management.Return for Credit with Receipt The Line Flow . inspected.Line ■ ■ ■ Line Flow . the process continues with receiving.Line Return Receiving . Line Flow .Line subprocess and two fulfillment activities.Return for Credit with Receipt process contains several subprocesses to ensure that the return is properly entered. which indicates that it can be assigned to a transaction type.Return for Credit with Receipt: ■ Enter . as well as the Return Receiving .OM Order Line Line Flow .Return for Credit with Receipt ends after the line is successfully closed.

Return for Credit with Receipt workflow begins at node 1 with the Enter .Return for Credit with Receipt process. refer to Chapter 6. you see that the process consists of 3 unique activity and 4 subprocesses. When you display the Process window for the Line Flow .START_ FULFILLMENT Result Type None None Required Yes Yes Seeded Workflow Definitions 4-45 .DEFER OE_FULFILL_WF.Line subprocess waits for inspection of the returned items before proceeding to the order fulfillment activities in nodes 3 and 4. Each node of this process is numbered for referencing. After the line is successfully closed. the process ends at node 7. Deferred subprocess at node 5 to generate the credit invoice.Line. The workflow proceeds to the Invoice Interface . For more information about individual activities. "Seeded Function Activity Definitions". Activity Fulfill .Return for Credit with Receipt.Return for Credit with Receipt Activities The following table provides a description for the activities in the Line Flow Return for Credit with Receipt process. The following diagram depicts the Line Flow . Line Flow . This subprocess verifies that the order is booked before proceeding with the remainder of the workflow. The Close .Line subprocess initiates at node 6. which comprise the 7 nodes that appear in the workflow diagram.Deferred (node 3) Fulfill (node 4) Function WF_STANDARD. The Line Flow .OM Order Line initiated only when an unexpected error with Oracle Workflow is encountered in the process.Line subprocess. At node 2 the Return Receiving .

This is an order line process. 4-46 Using Oracle Workflow in Oracle Order Management .Return for Credit with Receipt and Approval process is contained in the Seeded Data File oexwford. Note: The Line Flow . invoiced. When you save a return order line in Oracle Order Management. approved.NOOP Result Type None Required Yes Line Flow . the Line Flow Return for Credit with Receipt and Approval process verifies that the return is booked before proceeding.Return for Credit with Receipt process contains several subprocesses to ensure that the return is properly entered.OM Order Line Activity End (node 7) Function WF_STANDARD. inspected.Return for Credit with Receipt process except that it includes the Wait for Approval activity.Return for Credit with Receipt and Approval The Line Flow . and closed.Return for Credit with Receipt and Approval process is identical to the Line Flow . The Line Flow . The Line Flow . the process continues with receiving.Line. When your customer returns partial quantity of an order.Return for Credit with Receipt and Approval: ■ Enter .Line ■ ■ ■ Line Flow .Return for Credit with Receipt and Approval ends after the line is successfully closed. invoicing and closing. fulfilled.wft and is associated with the OM Order Line item type. Once booking is verified.Return for Credit with Receipt and Approval process is a workflow process used for returns that require inspection and approval before credit is given. Oracle Order Management splits the return line so that customers can be issued credit for what was returned.Line Return Receiving . These activities are performed in the following workflow subprocesses contained in Line Flow .Line Invoice Interface . Deferred Close .

At node 3. you see that the process consists of 4 unique activities and 4 subprocesses. The purpose of this error handling process is to alert an administrator when an error occurs in a process and prompt the administrator to retry the process in error.Line subprocess waits for inspection of the returned items before proceeding to the order fulfillment activities in nodes 4 and 5.Line subprocess. From this activity the process must be manually progressed before the workflow can proceed to node 3. After the line is successfully closed.Line subprocess initiates at node 6. This subprocess verifies that the order is booked before proceeding with the remainder of the workflow. The following diagram depicts the Line Flow .Return for Credit with Receipt and Approval. Each node of this process is numbered for referencing. select the process in the navigator tree and then select Properties from the Edit menu. which comprise the 8 nodes that appear in the workflow diagram. This error process is initiated only when an unexpected error with Oracle Workflow is encountered in the process. This item type is associated with the RETRY_ONLY error process. the Return Receiving . The Close . The Line Flow .Return for Credit with Receipt and Approval Process To view the properties of the Line Flow . which indicates that it can be assigned to a transaction type.Return for Credit with Receipt and Approval workflow begins at node 1 with the Enter .Return for Credit with Receipt and Approval process. When you display the Process window for the Line Flow .Return for Credit with Receipt and Approval process. The workflow proceeds to the Invoice Interface . This process is runnable. At node 2 the process encounters a block activity that requires the return order line to obtain approval before proceeding with the workflow.Line. the process to the End activity at node 8.OM Order Line Summary of the Line Flow . Deferred subprocess at node 6 to generate the credit invoice. Seeded Workflow Definitions 4-47 . The Details property page of the process activity indicates that the Line Flow Return for Credit with Receipt and Approval process has an error item type of WFERROR.

Standard Service ends after the line is successfully closed.Line Invoice Interface . such as a warranty.Standard Service: ■ Enter .wft and is associated with the OM Order Line item type.Standard Service workflow process is initiated when a sales order with service lines is submitted in Oracle Order Management.Line Close . invoiced. refer to Chapter 6.DEFER OE_FULFILL_WF.Standard Service process is contained in the Seeded Data File oexwford.Return for Credit with Receipt and Approval Activities The following table provides a description for the activities in the Line Flow Return for Credit with Receipt and Approval process. For more information about individual activities. 4-48 Using Oracle Workflow in Oracle Order Management . and closed. the process continues with invoicing and closing. The Line Flow . the Line Flow Standard Service process verifies that the return is booked before proceeding.WAITFORFLOW WF_STANDARD.START_ FULFILLMENT WF_STANDARD. This type of line flow is used for service items that are purchased with other merchandise. These activities are performed in the following workflow subprocesses contained in Line Flow .Standard Service The Line Flow . Once booking is verified.NOOP Result Type None None None None Required Yes Yes Yes Yes End (node 8) Line Flow .Line ■ ■ Line Flow .Deferred (node 4) Fulfill (node 5) Function WF_STANDARD. fulfilled. Activity Wait for Approval (node 2) Fulfill . When you save a return order line in Oracle Order Management. The process contains several subprocesses to verify that the return is properly entered. "Seeded Function Activity Definitions".OM Order Line Line Flow .

The Details property page of the process activity indicates that the Line Flow Standard Service process has an error item type of WFERROR. which indicates that it can be assigned to a transaction type. After the Fulfill activity at node 3 complete. the process proceeds to the End activity at node 6. Line Flow .Standard Service Process To view the properties of the Line Flow .Line subprocess at node 4 to process an invoice. Seeded Workflow Definitions 4-49 . When you display the Process window for the Line Flow .Standard Service Activities The following table provides a description for the activities in the Line Flow Standard Service process.Standard Service process. which comprise the 6 nodes that appear in the workflow diagram.Line subprocess at node 5. you see that the process consists of 3 unique activities and 3 subprocesses. This process is runnable. the line enters the Invoice Interface . The purpose of this error handling process is to alert an administrator when an error occurs in a process and prompt the administrator to retry the process in error.Standard Service workflow begins at node 1 with the Enter . This error process is initiated only when an unexpected error with Oracle Workflow is encountered in the process. At node 2 the process uses the Fulfill . The process initiates the Close . The Line Flow . After the line is successfully closed. Each node of this process is numbered for referencing. select the process in the navigator tree and then select Properties from the Edit menu.Line subprocess.Deferred to move the process to the background engine.OM Order Line Summary of the Line Flow .Standard Service. This item type is associated with the RETRY_ONLY error process. The following diagram depicts the Line Flow . This subprocess verifies that the order is booked before proceeding with the remainder of the workflow.Standard Service process.

OM Order Line For more information about individual activities.Deferred (node 2) Fulfill (node 3) End (node 6) Function WF_STANDARD.DEFER OE_FULFILL_WF.START_ FULFILLMENT WF_STANDARD. "Seeded Function Activity Definitions".NOOP Result Type None None None Required Yes Yes Yes 4-50 Using Oracle Workflow in Oracle Order Management . refer to Chapter 6. Activity Fulfill .

5 Seeded Subprocess Definitions This chapter discusses the Oracle Order Management seeded subprocesses. The following topics are addressed: ■ OM Order Header Subprocesses on page 5-2 OM Order Line Subprocesses on page 5-12 ■ Seeded Subprocess Definitions 5-1 .

Order is contained in the Seeded Data File oexwford.Order subprocess initiates as part of the Order Flow . When sales order return is submitted. the process ends with an incomplete result and returns to the order flow.Order The Approve Return .Return with Approval Approve Return . Summary of the Approve Return . This process is not runnable. Approve Return . The Details property page of the process activity indicates that Approve Return Order has an error item type of WFERROR. this subprocess sends a notification to verify authorization for that order return. which means that it cannot be assigned to a transaction type. it is a subprocess of a runnable flow. The following diagram depicts the Approve Return . select the process in the navigator tree and then select Properties from the Edit menu. you see that the process consists of 7 unique activities. the subprocess ends and returns to the order flow.Order subprocess runs a sequence of activities that approve the return of a sales order. Approve Return . If the return is authorized.Order subprocess. When you display the Process window for the Approve Return .OM Order Header Subprocesses OM Order Header Subprocesses Approve Return . This error process is initiated only when an unexpected error with Oracle Workflow is encountered in the process.Order Subprocess To view the properties of the Approve Return .wft and is associated with the OM Order Header item type. This subprocess can end with the following results: ■ Complete Incomplete ■ If the return is not authorized. which comprise the 7 activity nodes that appear in the workflow diagram.Order. 5-2 Using Oracle Workflow in Oracle Order Management . The purpose of this error handling process is to alert an administrator when an error occurs in a process and prompt the administrator to retry the process in error.Order subprocess.Order is a non-runnable flow and is initiated as a subprocess of the following order flow: ■ Order Flow .Return with Approval process. Each node of this subprocess is numbered for referencing. This item type is associated with the RETRY_ONLY error process.

The process then ends with a complete result and returns to the order flow. The following table displays the different function activities in the Approve Return Order subprocess.OM Order Header Subprocesses The Approve Return .Order subprocess.Continue Line activity in node 4. Once this is determined. For more information about individual function activities. Seeded Subprocess Definitions 5-3 .Order Activities The tables in this section provide descriptions of each activity in the Approve Return . The process the waits until the return is canceled before proceeding to the End (Incomplete) activity in node 7. If the return is authorized the notification returns a pass result and process is approved at the Approve . The Utility . Approve Return . "Seeded Function Activity Definitions". the process sends the Approve Return Order notification in node 3. refer to Chapter 6.Order process begins when the following order flow is initiated: ■ Order Flow . If the return is not authorized the notification returns a failing result and the process proceeds to the Approval Failed block activity.Return with Approval The workflow begins at node 1 with the Start activity.Set Notification Approver activity in node 2 determines to whom notification is sent.

Order. Deferred moves the booking process to the background engine. The order will book when the Workflow Background Process concurrent program processes the activity.wft and is associated with the OM Order Header item type. which means that it cannot be assigned to a transaction type.Order.Order. Deferred process ends only after an order is booked.Continue Line WF_STANDARD. Book . Deferred enables you to move booking to the background engine. The Details property page of the process activity indicates that Book .Order. This process is not runnable. Deferred is contained in the Seeded Data File oexwford. Summary of the Book . The Book . Deferred Book . This can be used when you must enter many orders and cannot wait for each individual order to book before moving on. it is a subprocess of a runnable flow. When you use the Book .Order.Order. Deferred subprocess.Set Notification Approver (node 2) Approve .BLOCK End (Incomplete) (node 7)) WF_STANDARD. the subprocess ends and returns to the line flow.NOOP None None None Approval Failed (node 6) WF_STANDARD. After the order is booked.NOOP OE_ORDER_WF_UTIL.NOOP Book .SET_ NOTIFICATION_APPROVER Result Type None None Required Yes Yes Yes Yes Yes Yes Start (node 1) Utility . Book . Deferred subprocess. Deferred has an error item type of WFERROR.OM Order Header Subprocesses Activity Function WF_STANDARD. The purpose of this error handling process is to alert an administrator when an error occurs in a process and prompt the administrator to retry the process in error. you do not need to specifically request for an order to book. select the process in the navigator tree and then select Properties from the Edit menu. Deferred Subprocess To view the properties of the Book . 5-4 Using Oracle Workflow in Oracle Order Management .Order.Order.CONTINUEFLOW None (node 4) End (Complete) (node 5) WF_STANDARD.Order. This error process is initiated only when an unexpected error with Oracle Workflow is encountered in the process. This item type is associated with the RETRY_ONLY error process.

Order. Deferred subprocess. After the eligibility is determined.Eligible activity in node 4. "Seeded Function Activity Definitions". you see that the process consists of 4 unique activities.OM Order Header Subprocesses When you display the Process window for the Book . the process moves back to the Book activity in node 2. Deferred workflow begins at node 1 with the Book . Deferred process. The Book . This process can only end after the order is booked.Order. An On Hold or Incomplete result leads to Book . On Hold.DEFER Result Type None Required Yes Seeded Subprocess Definitions 5-5 . Deferred Activities The following table provides descriptions of each activity in the Book .Order. Activity Book .Order.Deferred activity. At the Book activity in node 2 is a seeded lookup activity that can complete with a result of Incomplete.Deferred (node 1) Function WF_STANDARD. Not Eligible. or Complete. Book . Deferred subprocess. A Complete or Not Eligible result leads to the Book . refer to Chapter 6.Order. which comprise the 4 activity nodes that appear in the workflow diagram. The following diagram depicts the Book .Continue Line (Complete) activity in node 3. For more information about individual activities. Each node of this subprocess is numbered for referencing.

CONTINUEFLOW OE_STANDARD_ WF.Order Manual subprocess.OM Order Header Subprocesses Activity Book (node 2) Function OE_BOOK_WF. Manual Subprocess To view the properties of the Book .STANDARD_BLOCK Yes Yes Book .Order.wft and is associated with the OM Order Header item type. Manual Book . handles holds None None Required Yes Book . the subprocess ends and returns to the line flow.Order. Manual is a non-runnable flow that is initiated as a subprocess of the following line flows: ■ Order Flow . The purpose of this error handling process is to alert an administrator when an error occurs in a process and prompt the administrator to retry the process in error. After the order is booked. select the process in the navigator tree and then select Properties from the Edit menu. Manual is contained in the Seeded Data File oexwford. which means that it cannot be assigned to a transaction type. This process is not runnable.Order.Order.Eligible (node 5) WF_ STANDARD. Summary of the Book . which comprise the 4 activity nodes that appear in the workflow diagram.Continue Line (Complete) (node 3) Book . The Details property page of the process activity indicates that Book . Manual process ends only after the order is booked. The following diagram depicts the 5-6 Using Oracle Workflow in Oracle Order Management . you see that the process consists of 4 unique activities. Manual is a subprocess that enables you to book an order manually by using the Book . Book . Manual process.Return with Approval ■ ■ The Book .Generic Order Flow .Order. When you display the Process window for the Book . Manual has an error item type of WFERROR. it is a subprocess of a runnable flow.Order.Eligible activity.Generic with Header Level Invoice Interface Order Flow . This error process is initiated only when an unexpected error with Oracle Workflow is encountered in the process.BOOK_ORDER Result Type OM Subprocess results. Book .Order. This item type is associated with the RETRY_ONLY error process.Order.

Order.Generic Order Flow .Order. the process proceeds to the Book activity at node 3. When eligibility is determined. Manual Activities The following table provides descriptions of each activity in the Book . At the Book . After booking is complete. refer to Chapter 6.Generic with Header Level Invoice Interface Order Flow . Manual subprocess.Order. The Book . Manual subprocess begins when the following line flows are initiated: ■ Order Flow . the processes ends and returns to its parent line flow. Book .Order.OM Order Header Subprocesses Book . Each node of this subprocess is numbered for referencing.STANDARD_BLOCK Result Type None None Required Yes Yes Seeded Subprocess Definitions 5-7 . "Seeded Function Activity Definitions". Manual subprocess.Return with Approval ■ ■ The workflow begins at node 1 with the Start activity. the process waits for you to manually verify that the order is eligible for booking.DEFER OE_STANDARD_ WF. Activity Start (node 1) Book .Eligible activity in node 2.Eligible (node 2) Function WF_STANDARD. For more information about individual activities.

The purpose of this error handling process is to alert an administrator when an error occurs in a process and prompt the administrator to retry the process in error. it is a subprocess of a runnable flow.Order subprocess.Order subprocess closes an order in Oracle Order Management. Yes Handles Holds None Yes Close .Order has an error item type of WFERROR.Generic with Header Level Invoice Interface Order Flow . After the order closes or is determined not eligible. This item type is associated with the RETRY_ONLY error process.Order process can end with a result of not eligible or complete. which means that it cannot be assigned to a transaction type. The Details property page of the process activity indicates that Close . Summary of the Close .Order Subprocess To view the properties of the Close .Generic Order Flow .Continue Line (Complete) (node 4) Function OE_BOOK_WF. you see that the process consists of 6 unique activities.Order The Close . CONTINUEFLOW Result Type Required OM Subprocess Results.wft and is associated with the OM Order Header item type.OM Order Header Subprocesses Activity Book (node 3) Book .Return with Approval ■ ■ The Close . Close .Order is contained in the Seeded Data File oexwford. The following diagram depicts the Close . This process is not runnable. select the process in the navigator tree and then select Properties from the Edit menu.Order process. This error process is initiated only when an unexpected error with Oracle Workflow is encountered in the process. Close Order is a non-runnable flow that is initiated as a subprocess of the following order flows: ■ Order Flow .Order subprocess. 5-8 Using Oracle Workflow in Oracle Order Management . Each node of this subprocess is numbered for referencing. the subprocess ends and returns to the order flow. which comprise the 6 activity nodes that appear in the workflow diagram.BOOK_ ORDER WF_STANDARD. When you display the Process window for the Close .

the process moves to the End (Incomplete) activity at node 5.Return with Approval ■ ■ The workflow begins at node 1 with the Wait activity. the process moves to another Wait activity at node 6. At the Close .Order process begins when the following order flows are initiated: ■ Order Flow .Wait for Line activity in node 2.OM Order Header Subprocesses The Close .Generic with Header Level Invoice Interface Order Flow . Once the order is successfully closed. the subprocess moves to the End (Complete) activity at node 4.Generic Order Flow . Seeded Subprocess Definitions 5-9 . If the Close activity returns not eligible result. the process determines whether the all of the order lines in the order are closed before proceeding with the Close activity at node 3. If the Close activity returns an On Hold or Incomplete result.

WAIT Result Type None None None None None None Required Yes Yes Yes Yes Yes Yes Header Level Invoice Interface . refer to Chapter 6.OM Order Header Subprocesses Close .Generic with Header Level Invoice Interface Header Level Invoice Interface . For more information about individual activities. the subprocess ends and returns to the line flow.Order is a non-runnable flow that is initiated as a subprocess of the following order flow: ■ Order Flow . it is a subprocess of a runnable flow.Order Subprocess To view the properties of the Header Level Invoice Interface .Order is contained in the Seeded Data File oexwford. The Header Level Invoice Interface . After this information is received. which means that it cannot be assigned to a transaction type.Order subprocess conducts a series of activities that interface with Oracle Receivable to determine invoicing information for an order. 5-10 Using Oracle Workflow in Oracle Order Management .Order The Header Level Invoice Interface . "Seeded Function Activity Definitions". Header Level Invoice Interface .WAITFORFLOW WF_STANDARD. Summary of the Header Level Invoice Interface .NOOP WF_STANDARD.Order subprocess. select the process in the navigator tree and then select Properties from the Edit menu. This process is not runnable.Order can be used only with Order Flow .NOOP WF_STANDARD.NOOP WF_STANDARD.Generic with Header Level Invoice Interface.Wait for Line (node 2) Close (node 3) End (Complete) (node 4) End (Not Eligible) (node 5) Wait (node 6) Function WF_STANDARD. Activity Wait (node 1) Close . Header Level Invoice Interface .WAIT WF_ STANDARD.wft and is associated with the OM Order Header item type.Order process ends only after header level invoice information for an order is determined.Order Activities The following table provides descriptions of each activity in the Authorize to Ship Line subprocess.

which comprise the 5 activity nodes that appear in the workflow diagram. This item type is associated with the RETRY_ONLY error process. The following diagram depicts the Header Level Invoice Interface .Order has an error item type of WFERROR. At the Fulfill . Seeded Subprocess Definitions 5-11 . When you display the Process window for the Header Level Invoice Interface Order process.OM Order Header Subprocesses The Details property page of the process activity indicates that Header Level Invoice Interface . The purpose of this error handling process is to alert an administrator when an error occurs in a process and prompt the administrator to retry the process in error.Order process begins as a subprocess of the following process: ■ Order Flow .Header Level activity at node 3.Continue Line and returns to its parent order flow.Generic with Header Level Invoice Interface The workflow begins at node 1 with the Start activity. This error process is initiated only when an unexpected error with Oracle Workflow is encountered in the process.Wait for Line activity in node 2.Order subprocess. Each node of this subprocess is numbered for referencing. The Header Level Invoice Interface . you see that the process consists of 5 unique activities. the process waits for all of the order lines to fulfill before proceeding with the order flow. The process then moves to the Invoice Interface . After Oracle Order Management interfaces with Oracle Receivables for the order the process moves to Invoice Interface .

BLOCK Result Type None Yes/No None None None Required Yes Yes Yes No No OM Order Line Subprocesses Authorized to Ship . "Seeded Function Activity Definitions".Generic with Authorize to Ship (RLM) This subprocess verifies that an item is approved for shipping.CHECK_ AUTHORIZE_TO_SHIP WF_STANDARD. After the line is authorized. For more information about individual activities. refer to Chapter 6.Wait for Line (Node 2) Invoice Interface Header Level (Node 3) Invoice Interface Continue Line (Node 4) Header Invoice Interface . the subprocess ends and returns to the line flow.Line The Authorized to Ship is a subprocess specific to Oracle Release Management users.Line verifies that a line is eligible for shipping.NOOP WF_STANDARD.Order Activities The following table provides descriptions of each activity in the Header Level Invoice Interface subprocess.NOOP OE_RLM_WF.wft and is associated with the OM Order Line item type. Authorized to Ship .OM Order Line Subprocesses Header Level Invoice Interface .Line is a non-runnable flow that is initiated as a subprocess of the following process: ■ Line Flow . 5-12 Using Oracle Workflow in Oracle Order Management . This subprocess will hold a line until it is authorized to ship. Authorize to Ship . The Authorize to Ship .Eligible (Node 4) Function WF_STANDARD. Authorize to Ship . a hold is placed on the item.BLOCK WF_STANDARD.Line process ends only when authorization to ship is granted. Activity Start (Node 1) Fulfill .Line is contained in the Seeded Data File oexwford. If the item is not authorized for shipping.

This item type is associated with the RETRY_ONLY error process.Line process. The Details property page of the process activity indicates that Authorize to Ship Line has an error item type of WFERROR.Line subprocess.OM Order Line Subprocesses Summary of the Authorized to Ship .Line Subprocess To view the properties of the Authorize to Ship . you see that the process consists of 4 unique activities. The Authorize to Ship . Each node of this subprocess is numbered for referencing. Seeded Subprocess Definitions 5-13 . which comprise the 4 activity nodes that appear in the workflow diagram. select the process in the navigator tree and then select Properties from the Edit menu. When you display the Process window for the Authorize to Ship . This error process is initiated only when an unexpected error with Oracle Workflow is encountered in the process. The purpose of this error handling process is to alert an administrator when an error occurs in a process and prompt the administrator to retry the process in error.Generic with Authorize to Ship (RLM) ■ The workflow begins at node 1 with the Start activity. The following diagram depicts the Authorized to Ship . which means that it cannot be assigned to a transaction type. it is a subprocess of a runnable flow.Line process begins when either of the following line flows are initiated: ■ Line Flow .Configuration with Authorize to Ship (RLM) Line Flow .Line subprocess. This process is not runnable.

this workflow subprocess ends and returns to its parent flow.CHECK_ AUTHORIZE_TO_SHIP WF_STANDARD. Order lines follow this subprocess when the ATO item on the line has the Buy planning attribute on the organization item master.Wait for Authorization (Node 4) Function WF_STANDARD. or when the buy type sourcing rules are assigned to it in the shipping warehouse. the Buy ATO Item Flow transfers a record to the requisition interface tables for this order line. 5-14 Using Oracle Workflow in Oracle Order Management .OM Order Line Subprocesses At the Authorize to Ship . then the process waits until authorization is granted before proceeding. then the subprocess completes and returns to the line flow.Line Activities The following table provides descriptions of each activity in the Authorize to Ship Line subprocess.BLOCK Result Type None Yes/No None None Required Yes Yes Yes No Buy ATO Item Flow Buy ATO Item Flow is a subprocess of the Create ATO Supply workflow. This process is runnable. If the order line is authorized to ship (a Yes result). For more information about individual activities. If the order line is not authorized to ship. Summary of the Buy ATO Item Flow Subprocess To view the properties of the Buy ATO Item Flow subprocess. which means that it can be assigned to a transaction type. For these lines.wft and is associated with the OM Order Line item type. select the process in the navigator tree and then select Properties from the Edit menu.NOOP WF_STANDARD. Buy ATO Item Flow is contained in the Seeded Data File oexwford. "Seeded Function Activity Definitions". Once the data is placed in the requisition interface tables.Check Status activity in node 2. refer to Chapter 6. the process attempts to verify whether the order line is authorized to ship. Authorized to Ship .NOOP OE_RLM_WF. Activity Start (Node 1) Authorize to Ship Check Status (Node 2) End (Node 3) Authorize to Ship .

"Seeded Function Activity Definitions". refer to Chapter 6. you see that the process consists of 4 unique activities. Seeded Subprocess Definitions 5-15 .OM Order Line Subprocesses The Details property page of the process activity indicates that Buy ATO Item Flow has an error item type of WFERROR. The purpose of this error handling process is to alert an administrator when an error occurs in a process and prompt the administrator to retry the process in error. The following diagram depicts the Buy ATO Item Flow subprocess. This item type is associated with the RETRY_ ONLY error process. When you display the Process window for the Buy ATO Item Flow process. For more information about individual activities. The Buy ATO Item Flow begins at node 1 with the Start activity. the AutoCreate PO Req activity transfers its record to the requisition interface tables for the order line. This error process is initiated only when an unexpected error with Oracle Workflow is encountered in the process. Upon successful completion of this activity. the process moves to the End (Complete) activity at node 3. Each node of this subprocess is numbered for referencing. which comprise the 4 activity nodes that appear in the workflow diagram. Buy ATO Item Flow Activities The following table provides descriptions of each activity in the Buy ATO Item Flow subprocess. At node 2.

Calculate Lead Time is initiated to determine the actual lead time of the configuration item in the organization in which it will be manufactured. the Calculate Lead Time subprocess ends when calculation is complete. The process updates the lead time attributes on the item master for the configuration item that organization.Line The Calculate Lead Time subprocess is specific to Oracle Configure to Order users. This item type is associated with the RETRY_ONLY error process.NOOP End (Incomplete) (Node 4) WF_STANDARD. it is a subprocess of a runnable flow. If the configuration item has routing associated with it. This process is not runnable. Summary of the Calculate Lead Time .NOOP Result Type None Required Yes Yes CTO_WORKFLOW_API_PK.NOOP Yes Yes Calculate Lead Time .Line is contained in the Seeded Data File oexwford. The Details property page of the process activity indicates that Calculate Lead Time . This process is a non-runnable flow initiated as a subprocess of the following line flow: ■ Create Manufacturing Configuration Data . which means that it cannot be assigned to a transaction type.Line.Line. If the configuration item does not have routing.Line Subprocess To view the properties of the Calculate Lead Time .Line has an error item type of WFERROR.OM Order Line Subprocesses Activity Start (Node 1) AutoCreate PO Req (Node 2) Function WF_STANDARD. Manual completes. select the process in the navigator tree.AUTO_ Config CREATE_PUR_REQ Process Results None None End (Complete) (Node 3) WF_STANDARD.wft and is associated with the OM Order Line item type. this process ends without performing the calculation Calculate Lead Time .Line subprocess. then select Properties from the Edit menu. Manual The Calculate Lead Time subprocess is initiated after Create Configuration . The purpose of this error handling process is to alert an administrator when an error occurs in a process and prompt the administrator to 5-16 Using Oracle Workflow in Oracle Order Management .

Setup Parameters activity no routing is found. If at the Calculate Lead Time .Line subprocess. and returns to its parent line flow. This error process is initiated only when an unexpected error with Oracle Workflow is encountered in the process.Setup Parameters activity in node 2. The following image depicts the workflow diagram for the Calculate Lead Time .Line Process Activities The following table provides descriptions of each activity in the Calculate Lead Time . where lead time is calculated.Line. Seeded Subprocess Definitions 5-17 . you see that the process consists of 4 unique activities which comprise the nodes in the workflow diagram. The process then moves to the End activity at node 4. At the Calculate Lead Time .Line subprocess. Calculate Lead Time . Manual The workflow begins at node 1 with the Start activity. When you display the Process window for the Calculate Lead Time .Line begins as a subprocess of the following line flow: ■ Create Manufacturing Configuration Data . Each node of this subprocess is numbered for referencing. the process sets the line number as the parameter of the concurrent program for lead time calculation and then moves to the Calculate Lead Time activity in node 3.Line subprocess. Calculate Lead Time .OM Order Line Subprocesses retry the process in error. The numbers themselves are not part of the process diagram. lead time is not calculated and the process proceeds directly to the End activity at node 4.

SUBMIT_ AND_CONTINUE_WF WF_STANDARD.Generic with Authorize to Ship (RLM) Line Flow . Ship Only Line Flow . Bill Only with Inventory Interface Line Flow .Generic.Generic.Generic. refer to Chapter 6. Bill Only Line Flow .Return for Credit with Receipt ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ 5-18 Using Oracle Workflow in Oracle Order Management . Close .OM Order Line Subprocesses For more information about individual activities.Return for Credit Only with Approval Line Flow .ATO Item Line Flow .Generic.Line The Close .Generic with Header Level Invoice Interface Line Flow .SET_ PARAMETER_LEAD_TIME_ WF_ML CTO_WORKFLOW. With Export Compliance Line Flow .NOOP CTO_WORKFLOW. Activity Function WF_STANDARD.NOOP Result Type None Lead Time Result None None Required Yes Yes Start (node 1) Calculate Lead Time .ATO Model Line Flow .Generic.Configuration with Authorize to Ship (RLM) Line Flow .Generic Line Flow . "Seeded Function Activity Definitions". with Repricing at Fulfillment Line Flow .Line is a non-runnable subprocess initiated at the end of the following line flows: ■ Line Flow .Line process closes a line in a line flow and is mandatory for all line level processes.Return for Credit Only Line Flow .Configuration Line Flow .Setup Parameters (node 2) Calculate Lead Time (node 3) End (node 4) No Yes Close .

Standard Service ■ ■ Each time an order line is saved.Standard Service Line Flow . you see that the process consists of 4 unique activities which comprise the activity nodes that appear in the workflow diagram.Return for Credit with Receipt and Approval Line Flow . Order lines can close independent of each other. which means that it cannot be assigned to a transaction type.Line subprocess is contained in the Seeded Data File oexwford.Line has an error item type of WFERROR.Line Subprocess To view the properties of the Close . The purpose of this error handling process is to alert an administrator when an error occurs in a process and prompt the administrator to retry the process in error. for which you can define processing constraints. select the process in the navigator tree. The Details property page of the process activity indicates that Close . Once an order line is closed. When you display the Process window for the Close . The numbers themselves are not part of the process diagram. Each node of this subprocess is numbered for referencing.OM Order Line Subprocesses ■ Line Flow . it is a subprocess of a runnable flow. Summary of the Close .Line process.wft and is associated with the OM Order Line item type. This process is not runnable. then select Properties from the Edit menu. it concludes with the Close Line subprocess. This error process is initiated only when an unexpected error with Oracle Workflow is encountered in the process. Seeded Subprocess Definitions 5-19 . a workflow process is initiated. activities and subprocesses. The Close . The following image depicts the workflow diagram for the Close .Line subprocess. An order line is eligible to close when it completes all of the line-level activities within the workflow process. This item type is associated with the RETRY_ONLY error process. no changes can be made to any fields except the descriptive flexfield.Line subprocess. After the workflow runs through its functions.

the line closes and proceeds to the Close .Line subprocess. The workflow ends only when the order line is determined complete or not eligible. after attempting to close. If the line is determined complete or not eligible.Line Process Activities The following table provides descriptions of each activity in the Close . which signifies to the header level parent flow that the line is closed. the process conducts the Wait activity at node 4. the process attempts to close the line. which waits until the line is complete or the hold is released. a result of Incomplete or On Hold is returned. The subprocess then ends and returns to its parent flow. This activity has four possible results: ■ Complete Not Eligible Incomplete On Hold ■ ■ ■ If. The workflow begins at node 1 with the Start activity. In the Close activity at node 2.OM Order Line Subprocesses The Close . The Wait activity has a default waiting time of 1 day.Continue Header activity at node 3.Line workflow begins at the end of runnable line flow. 5-20 Using Oracle Workflow in Oracle Order Management . Close .

select the process in the navigator tree and then select Properties from the Edit menu.WAIT Result Type None OM subprocess Results. which means that it cannot be assigned to a transaction type. Summary of the Create ATO Supply Process To view the properties of the Create ATO Supply process.NOOP OE_CLOSE_WF. "Seeded Function Activity Definitions". Create ATO Supply contains the following subprocesses: ■ Purchase Release . Seeded Subprocess Definitions 5-21 . This process is a subprocess of the following workflow: ■ Create Supply Order . refer to Chapter 6. This process is not runnable. Create ATO Supply is contained in the Seeded Data File oexwford.Line Buy ATO Item Flow ■ ■ Create ATO Supply can end with an incomplete or complete result. Activity Start (node 1) Close (node 2) End (node 3) Wait (node 4) Function WF_STANDARD. The supply type is determined using the source type of the order line. Manual The Create ATO Supply subprocess determines the need for supply creation by branching according to supply type.OM Order Line Subprocesses For more information about individual activities.wft and is associated with the OM Order Line item type. Deferred . and the sourcing rules of the item. This subprocess evaluates the supply type to determine which branch to follow.CLOSE_LINE WF_STANDARD. it is a subprocess of a runnable flow.ATO Create Work Order . the planning Make or Buy type.NOOP WF_STANDARD. handles Holds None None Required Yes Yes Yes Yes Create ATO Supply Create ATO Supply is a workflow subprocess that automates the creation of assemble-to-order supply for an order line.Line.Line.

you see that the process consists of 5 unique activities and 3 subprocesses. The workflow begins at node 1 with the Start activity. When you display the Process window for the Create ATO Supply. Each node of this process is numbered for referencing. The following diagram depicts the Create ATO Supply process. 5-22 Using Oracle Workflow in Oracle Order Management . This error process is initiated only when an unexpected error with Oracle Workflow is encountered in the process. which comprise the 8 nodes that appear in the workflow diagram.OM Order Line Subprocesses The Details property page of the process activity indicates that the Create ATO Supply process has an error item type of WFERROR. The purpose of this error handling process is to alert an administrator when an error occurs in a process and prompt the administrator to retry the process in error. This item type is associated with the RETRY_ONLY error process.

the process resumes and proceeds to the End (Complete) activity at node 4. Once this completes.Line returns an incomplete result.Line. or. the process proceeds to the End (Incomplete) activity at node 8. If the supply type is Work Order. the process determines the supply type for the order line. This process is initiated as a subprocess of the following workflows: ■ Line Flow .Line.Line process at node 3. Manual is a workflow process that creates configuration for a line flow.Line.Line subprocess ■ Create Configuration . This activity has five possible results: ■ Drop Ship Buy Work Order Flow Schedule Incomplete ■ ■ ■ ■ If the supply type is Drop Ship. Create Configuration .OM Order Line Subprocesses In the Check Supply Type activity at node 2. the process moves directly to the End (Incomplete) activity at node 8.wft and is associated with the OM Order Line item type.ATO subprocess at node 5. Once this completes. Once this completes. the process initiates the Create Flow Schedule activity at node 7. If the supply type is Flow Schedule. Deferred .ATO Model line flow Create Supply . Manual Create Configuration . The process then moves to the End (Complete) activity at node 4. the process proceeds the End (Complete) activity at node 4. Manual is contained in the Seeded Data File oexwford.Line. or. If the supply type is Buy. If the Check Supply Type activity has an error or is unable to determine a supply type. the process initiates the Purchase Release . If the Create Work Order . the process initiates the Create Work Order . the process initiates the Buy ATO Item Flow subprocess at node 6. Seeded Subprocess Definitions 5-23 . the process resumes and proceeds to the End (Complete) activity at node 4. if Buy ATO Item Flow returns an incomplete result. if Create Flow Schedule returns an incomplete result. the process proceeds to the End (Incomplete) activity at node 8. the process proceeds to the End (Incomplete) activity at node 8.

Manual Process To view the properties of the Create Configuration .Line. This error process is initiated only when an unexpected error with Oracle Workflow is encountered in the process. This item type is associated with the RETRY_ONLY error process. it is a subprocess of a runnable flow. Manual process. Manual process. Manual subprocess. The purpose of this error handling process is to alert an administrator when an error occurs in a process and prompt the administrator to retry the process in error.Line. Each node of this subprocess is numbered for referencing.OM Order Line Subprocesses This process can only end after configuration for the line is complete. 5-24 Using Oracle Workflow in Oracle Order Management . then select Properties from the Edit menu.Line. The Details property page of the process activity indicates that the Create Configuration .Line. which means that it cannot be assigned to a transaction type. The following image depicts the workflow diagram for the Create Configuration . The numbers themselves are not part of the process diagram.Line. you see that the process consists of 5 unique activities which comprise the 5 activity nodes that appear in the workflow diagram. Manual process has an error item type of WFERROR. select the process in the navigator tree. When you display the Process window for the Create Configuration . Summary of the Create Configuration . This process is not runnable.

Manual subprocess.BLOCK Result Type None None Config Incomplete Config Item Results Required Yes Yes Yes Yes Seeded Subprocess Definitions 5-25 .STANDARD_BLOCK CTO_WORKFLOW. Once this authorization is granted. If the result returned from the Create Configuration activity is complete.NOOP OE_STANDARD_ WF. The Create Configuration . If the result of the Wait For CTO activity is Complete. Create Configuration .Line subprocess completes. For more information about individual activities. If you use Line Flow . the process proceeds to the Create Configuration activity at node 3. the process returns to the Create Configuration .ATO Model this subprocess begins after the Schedule . you must manually progress the order. "Seeded Function Activity Definitions". then the process continues to End at node 5. Manual subprocess begins at node 1 with the Start activity.Eligible activity at node 2. This activity has three possible results: ■ Complete Incomplete On Hold ■ ■ If the result of this activity is Incomplete or On Hold.Line subprocess is initiated. Manual Process Activities The following table provides descriptions of each activity in the Create Configuration . Activity Start (node 1) Create Configuration Eligible (node 2) Create Configuration (node 3) Wait for CTO (node 4) Function WF_STANDARD. the process proceeds to the Wait for CTO activity at node 4.OM Order Line Subprocesses If you use Line Flow .Line.Line.Line. At the Create Configuration . this subprocess begins when the Create Supply .Eligible activity in node 2.CREATE_ CONFIG_ITEM_WF WF_STANDARD.Generic to process ATO Models. This activity has two possible results: ■ Complete De-Link ■ If the result of this activity is De-Link. refer to Chapter 6.Eligible activity at node 2. the process returns to the Create Configuration .

Manual Create Manufacturing Configuration Data .Line. Manual is a non-runnable flow that is initiated as a subprocess of the following line flows: ■ Line Flow . Summary of Create Manufacturing Configuration Data . The purpose of this error handling process is to alert an administrator when an error occurs in a process and prompt the administrator to retry the process in error. Manual contains the following subprocess: ■ Calculate Lead Time . Manual is contained in the Seeded Data File oexwford.Line.Line. Manual process shows that the process consists of 5 unique activities and 1 5-26 Using Oracle Workflow in Oracle Order Management . This error process is initiated only when an unexpected error with Oracle Workflow is encountered in the process. The Process window for the Create Manufacturing Configuration Data . Manual process has an error item type of WFERROR. Manual Process To view the properties of the Create Manufacturing Configuration Data . select the process in the navigator tree.Configuration or Line Flow . then select Properties from the Edit menu.wft and is associated with the OM Order Line item type.Line. Manual process is initiated as a subprocess of the line flow.Configuration Line Flow .Line.Line.Line Every time an order line is saved in Oracle Order Management. This item type is associated with the RETRY_ONLY error process.NOOP Result Type None Required Yes Create Manufacturing Configuration Data . Manual process.Line. Create Manufacturing Configuration Data . it is a subprocess of a line flow. which indicates that it cannot be assigned to a transaction type.Line. the line is evaluated to determine which workflow is assigned to the line.OM Order Line Subprocesses Activity End (node 5) Function WF_STANDARD. The Details property page of the process activity indicates that the Create Manufacturing Configuration Data .Configuration with Authorize to Ship (RLM). The Create Manufacturing Configuration Data . If the appropriate line flow for the line is Line Flow . This process is not runnable. the Create Manufacturing Configuration Data .Line. Manual is a workflow subprocess that creates the manufacturing configuration data for an order line.Line.Configuration with Authorize to Ship (RLM) ■ Create Manufacturing Configuration Data .

Each node of this subprocess is numbered for referencing. The workflow begins at node 1 with the Start activity.Line subprocess. or.OM Order Line Subprocesses subprocess which comprise the 6 activity nodes that appear in the workflow diagram. the subprocess can proceed to the End activity at node 5. Configuration data might already be created if the user created the configuration item using the Autocreate Config batch program. Calculate Cost Rollup.Line. Manual process is initiated as a subprocess of the selected line flow. the process proceeds to node 4: the Calculate Lead Time . Once this activity completes.Line.Line. Manual subprocess. Manual begins after Line Flow . rather than progressing the workflow process.Configuration or Line Flow . it comes to node 3. The Create Manufacturing Configuration Data . If the process proceeds down the default path. This activity can proceed down the default path. The numbers themselves are not part of the process diagram. In the Wait for Create Configuration activity at node 2 the process waits for the configuration data to complete. The Create Manufacturing Configuration Data . the process moves to Calculate Purchase Price activity at node 5.Configuration with Authorize to Ship (RLM) is selected as the appropriate line flow for the order line. Seeded Subprocess Definitions 5-27 . After successfully completing the calculate purchase price subprocess. if the configuration data is already created. The following image depicts the workflow diagram for the Create Manufacturing Configuration Data .

Line subprocess creates supply for an order line. with Repricing at Fulfillment Line Flow .Line.Generic with Header Level Invoice Interface Line Flow .PURCHASE_ PRICE_CALC_WF WF_STANDARD. "Seeded Function Activity Definitions".Standard Service ■ ■ ■ ■ ■ ■ Create Supply . It is a non-runnable flow initiated as a subprocess of the following line flows: ■ Line Flow .Generic Line Flow . Manual Process Activities The following table provides descriptions of each activity in the Create Manufacturing Configuration Data .Generic with Authorize to Ship (RLM) Line Flow .Generic.Line.NOOP WF_STANDARD.OM Order Line Subprocesses After Calculate Purchase Price finishes. With Export Compliance Line Flow . the process proceeds to the End activity at node 6. Create Manufacturing Configuration Data . Activity Start (node 1) Wait for Create Configuration (node 2) Calculate Cost Rollup (node 3) Calculate Purchase Price (node 3) End (node 5) Function WF_STANDARD.Generic.BLOCK CTO_ WORKFLOW.Line.Line contains the following subprocesses: ■ Create Supply Order . Ship Only Line Flow .Generic.CALCULATE_ COST_ROLLUP_WF_ML CTO_ WORKFLOW.NOOP Result Type None Config Data Results None Required Yes Yes Yes None Yes None Yes Create Supply . Manual subprocess. refer to Chapter 6. For more information about individual activities.Line The Create Supply . Manual 5-28 Using Oracle Workflow in Oracle Order Management .

Summary of the Create Supply .Line process will initiate as a subprocess of the line flow. One activity is reused to comprise the 8 activity nodes that appear in the workflow diagram.Line subprocess. Manual Purchase Release . The Details property page of the process activity indicates that the Create Supply Line process has an error item type of WFERROR. Seeded Subprocess Definitions 5-29 .Line process shows that the process consists of 5 unique activities. The numbers themselves are not part of the process diagram. This error process is initiated only when an unexpected error with Oracle Workflow is encountered in the process. select the process in the navigator tree. The Process window for the Create Supply . ATO Item. the Create Supply .Line. The first activity in this process is the Branch on Source Type activity. or standard item. then select Properties from the Edit menu.Line subprocess. it is a subprocess or a line flow. The Create Supply . The following image depicts the workflow diagram for the Create Supply . ATO Model. This activity evaluates the line source type and item attributes to determine the line type: drop ship.Line. Each node of this subprocess is numbered for referencing. which indicates that it cannot be assigned to a transaction type. the line is evaluated to determine which workflow is assigned to the line.wft and is associated with the OM Order Line item type. The purpose of this error handling process is to alert an administrator when an error occurs in a process and prompt the administrator to retry the process in error. ATO Model.Line Process To view the properties of the Create Supply . If the appropriate line flow for the line is one of the previously mentioned flows. This item type is associated with the RETRY_ONLY error process. Deferred ■ Each time an order line is saved in Oracle Order Management.Line process is contained in the Seeded Data File oexwford. supply for the items must be created. This process is not runnable.OM Order Line Subprocesses ■ Create Configuration . or ATO Item. If it is a dropship.

Generic with Authorize to Ship (RLM) Line Flow . With Export Compliance Line Flow .OM Order Line Subprocesses The Create Supply . Line Flow .Generic.Generic with Header Level Invoice Interface Line Flow .Line workflow begins when on of the following lines flows is selected as the appropriate flow for the order line: ■ Line Flow . Ship Only Line Flow .Generic.Generic. with Repricing at Fulfillment ■ ■ ■ ■ ■ 5-30 Using Oracle Workflow in Oracle Order Management .Generic.

ATO options. which leads to the Create Configuration Line.BRANCH_ ON_SOURCE_TYPE Result Type Source Type Required Yes Seeded Subprocess Definitions 5-31 .Standard Service The workflow begins at node 1 with the Branch on Source Type activity. If the source type is not ATO Item.Line Process Activities The following table provides descriptions of each activity in the Create Supply Order . Non-shippable lines are fulfilled after their dependencies are fulfilled. Once this subprocess is completed. or Dropship the process proceeds to the End activity at node 2. the subprocess moves to the End activity in node 5. Stock. This activity has five possible results: ■ Default ATO Item Stock Build Dropship ■ ■ ■ ■ When ATO Item is selected. and service lines follow the stock flow. Activity Branch on Source Type (node 1) Function OE_OEOL_SCH. Oracle Order Management’s Purchase Release subprocess is used for these order lines. the process proceeds to the End activity at node 4. All internal standard items and non-shippable lines such as classes. Create Supply . the process leads to the Create Supply Order . The item is eligible for shipping on its schedule date. Manual subprocess in node 6. "Seeded Function Activity Definitions". refer to Chapter 6.OM Order Line Subprocesses ■ Line Flow . Once this process completes. An ATO model has the Build result type. This flow indicates that Oracle Order Management must not create supply for the item (planning will provide supply for the item). Manual subprocess. Build. For more information about individual activities. All standard (non-ATO) items which have a source type code of External continue through the dropship workflow activity process. Manual subprocess in node 3.Line. and the order line flow continues.Line.

Line. select the process in the navigator tree. Manual Create Supply Order . the line is evaluated to determine which workflow is assigned to the line.Line. 4. Manual Process To view the properties of the Create Supply Order .Line.OM Order Line Subprocesses Activity End (nodes 2. If there is. the subprocess ends. Manual is a workflow subprocess that creates supply for ATO items and configurations.NOOP Result Type None Required Yes Create Supply Order . The Create Supply Order . it is a subprocess or a line flow. If the appropriate line flow for the line is one of the previously mentioned flows. then select Properties from the Edit menu.Line. Manual process is initiated as a subprocess of the line flow.ATO Item Line Flow . Manual subprocess contains the following subprocess: ■ Create ATO Supply Each time an order line is saved in Oracle Order Management.Configuration with Authorize to Ship (RLM) ■ ■ The Create Supply Order . This process is not runnable.Line. Summary of the Create Supply Order .Line. Create Supply Order . Manual process. which indicates that it cannot be assigned to a transaction type. 8) Function WF_STANDARD. the subprocess encounters the Create Supply Order . 5-32 Using Oracle Workflow in Oracle Order Management . Manual is initiated as a subprocess of the following runnable flows: ■ Line Flow . or creates and reserves supply manually. Manual process is contained in the Seeded Data File oexwford.Line. the Create Supply Order . 5.Line. It first verifies that there is a reservation already on the sales order line.Line Create Supply Order . Manual is initiated as a subprocess of the following workflow subprocess: ■ Create Supply .Line.Configuration Line Flow .Eligible block activity and waits until the user progresses the order line to the Create ATO Supply subprocess.wft and is associated with the OM Order Line item type. If there is no reservation.

Manual process shows that the process consists of 4 unique activities and 1 subprocess. The numbers themselves are not part of the process diagram. the Check Reservation activity determines whether there is quantity reserved to this line. After Create ATO Supply completes.Line. If there is no reservation to the line. the line flow proceeds to the End activity at node 5.Eligible activity at node 3 waits until the user progresses the order line to the Create ATO Supply subprocess at node 4. This item type is associated with the RETRY_ONLY error process. The Create Supply Order . Manual subprocess. Each node of this subprocess is numbered for referencing. Manual process begins when its parent line flow or the Create Supply . The Process window for the Create Supply Order . The purpose of this error handling process is to alert an administrator when an error occurs in a process and prompt the administrator to retry the process in error. At node 2.Line.Line subprocess initiates it as part of its flow.Line. The workflow begins at node 1 with the Start activity. The following image depicts the workflow diagram for the Create Supply Order . If there is.OM Order Line Subprocesses The Details property page of the process activity indicates that the Create Supply Order . The Create Supply Order . This error process is initiated only when an unexpected error with Oracle Workflow is encountered in the process. Manual process has an error item type of WFERROR. Seeded Subprocess Definitions 5-33 . the process proceeds to the Create Supply Order . comprising the 5 activity nodes that appear in the workflow diagram.Line.Eligible activity at node 3. the process proceeds directly to the End activity at node 5. and returns to its parent line flow.

Line is associated with assemble to order items.Line The Create Work Order . If the appropriate line flow for the line is one of the previously mentioned flows.Line. "Seeded Function Activity Definitions". The process can end with a complete or incomplete result. This process is not runnable. Create Work Order .NOOP CTO_WORKFLOW.Line. select the process in the navigator tree.STANDARD_BLOCK WF_STANDARD. The order line is on hold.OM Order Line Subprocesses Create Supply Order . Manual subprocess. Manual Process Activities The following table provides descriptions of each activity in the Create Supply Order . The Create Work Order . ■ Each time an order line is saved in Oracle Order Management. 5-34 Using Oracle Workflow in Oracle Order Management . the line is evaluated to determine which workflow is assigned to the line. indicating that when the process completes. the Create Work Order .Line process has a result type of Config Process Results.NOOP Result Type None Reserved Status Reserved Status None Required Yes Yes No Yes Create Work Order .Line process is contained in the Seeded Data File oexwford.Line Process To view the properties of the Create Work Order . it has a result of either complete (work order created) or incomplete (work order not completed). refer to Chapter 6. Activity Start (node 1) Check Reservation (node 2) Create Supply Order Eligible (node 3) End (node 5) Function WF_STANDARD. For more information about individual activities. Summary of the Create Work Order . It ends with an incomplete result if the following occurs: ■ There is an error during parameter setup.RSV_ BEFORE_BOOKING_WF OE_STANDARD_ WF.wft and is associated with the OM Order Line item type. The Create Work Order .Line subprocess is a workflow process that is initiated as a subprocess of the Create ATO Supply subprocess. then select Properties from the Edit menu.Line subprocess.Line process is initiated as a subprocess of the line flow.

The Details property page of the process activity indicates that the Create Work Order . the process moves directly to the End (Incomplete) activity Seeded Subprocess Definitions 5-35 . it is a subprocess or a line flow. When the Create Work Order . comprising the 6 activity nodes that appear in the workflow diagram. the Create Work Order . Each node of this subprocess is numbered for referencing.Line process shows that the process consists of 6 unique activities.Line process has an error item type of WFERROR. The Process window for the Create Work Order . This item type is associated with the RETRY_ONLY error process. The following image depicts the workflow diagram for the Create Work Order .Line subprocess. This error process is initiated only when an unexpected error with Oracle Workflow is encountered in the process. The purpose of this error handling process is to alert an administrator when an error occurs in a process and prompt the administrator to retry the process in error.OM Order Line Subprocesses which indicates that it cannot be assigned to a transaction type. At node 2.Set Up Parameters activity prepares to launch AutoCreate FAS by setting up the line number as the parameter for the program. The numbers themselves are not part of the process diagram.Set Up Parameters activity completes with a result of incomplete or on hold. The Create Work Order .Line workflow begins at node 1 with the Start activity.

If the result is not Normal. refer to Chapter 6. the process proceeds to the End (Complete) activity at node 4. For more information about individual activities.ATO Item 5-36 Using Oracle Workflow in Oracle Order Management . Activity Start (node 1) Create Work Order . which leads to the End (Complete) at node 4.Eligible. and then waits until the concurrent program completes before continuing. If the process ends as incomplete. the parent process moves back to Create Supply Order .OM Order Line Subprocesses at node 6.Line subprocess. Enter . If the result is Normal.Line The Enter . This activity initiates a concurrent program to create a work in process job for the order line.Line Process Activities The following table provides descriptions of each activity in the Create Work Order . When the activity completes with a result of complete.Set Up Parameters (node 2) Function WF_STANDARD. it proceeds to the AutoCreate FAS activity at node 3.Line is associated with the following line flows: ■ Line Flow .NOOP CTO_WORKFLOW.NOOP WF_STANDARD.NOOP None None Yes Yes Enter . From this notification. When it completes. the AutoCreate FAS activity can be retried (leading back to node 2). the activity verifies the result. A notification is then sent to the Order Management Workflow administrator with the following message: Failed AutoCreate FAS. or aborted.SET_ PARAMETER_WORK_ ORDER_WF Result Type None Config Incomplete Required Yes Yes AutoCreate FAS (node 3) CTO_WORKFLOW. the process moves to the Retry AutoCreate FAS notification activity.SUBMIT_ Concurrent Program Yes CONC_PROG_WF Status End (Complete) (node 4) End (Incomplete) (node 6) WF_STANDARD.Line subprocess verifies that lines on an order are booked before proceeding with the line flow. Create Work Order . "Seeded Function Activity Definitions".

Generic Line Flow .Return for Credit with Receipt Line Flow .Standard Service Line Flow .Generic. Bill Only Line Flow .Line Process To view the properties of the Enter . with Repricing at Fulfillment Line Flow .Generic with Authorize to Ship (RLM) Line Flow . then select Properties from the Edit menu.wft and is associated with the OM Order Line item type. which indicates that it cannot be assigned to a transaction type.Generic with Header Level Invoice Interface Line Flow .Return for Credit Only with Approval Line Flow . This process is not runnable. The purpose of this error handling process is to alert an administrator when an error occurs in a process and prompt the administrator to Seeded Subprocess Definitions 5-37 .Standard Service ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ Each time an order line is saved in Oracle Order Management. Summary of the Enter .Line Process.OM Order Line Subprocesses ■ Line Flow . With Export Compliance Line Flow .ATO Model Line Flow . the line is evaluated to determine which workflow is assigned to the line.Generic.Return for Credit with Receipt and Approval Line Flow . it is a subprocess or a line flow.Return for Credit Only Line Flow . Ship Only Line Flow .Line process has an error item type of WFERROR.Generic.Line process is contained in the Seeded Data File oexwford.Line process is initiated as a subprocess of the line flow. The Details property page of the process activity indicates that the Enter .Generic. If the appropriate line flow for the line is one of the previously mentioned flows. select the process in the navigator tree. the Enter .Generic. The Enter . Bill Only with Inventory Interface Line Flow . This item type is associated with the RETRY_ONLY error process.

OM Order Line Subprocesses retry the process in error. For more information about individual activities. comprising the 2 activity nodes that appear in the workflow diagram. After the order is booked the process proceeds to the End activity in node 2. refer to Chapter 6. The Process window for the Enter .WAITFORFLOW WF_STANDARD. This error process is initiated only when an unexpected error with Oracle Workflow is encountered in the process.Line process shows that the process consists of 2 unique activities. The following image depicts the workflow diagram for the Enter .NOOP Result Type None None Required Yes Yes 5-38 Using Oracle Workflow in Oracle Order Management . "Seeded Function Activity Definitions".Line subprocess. The numbers themselves are not part of the process diagram. The workflow begins at node 1 with the Wait for Booking activity.Line subprocess. This activity is a standard block activity that requires an order flow to be booked before proceeding. Each node of this subprocess is numbered for referencing. Activity Wait for Booking (node 1) End (node 2) Function WF_STANDARD. Enter .Line Process Activities The following table provides descriptions of each activity in the Enter .

Line subprocess performs Denied Party screening according to United States Bureau of Export Administration’s Denied Party listing. this subprocess initiates. The Export Compliance Screening . the process initiates a hold until the requirements are met. the line is evaluated to determine which workflow is assigned to the line. then the process approves the line for exporting and continues. it is a subprocess or a line flow. This error process is initiated only when an unexpected error with Oracle Workflow is encountered in the process. This item type is associated with the RETRY_ONLY error process.Line process is initiated as a subprocess of the line flow.Line process is contained in the Seeded Data File oexwford. The Process window for the Export Compliance Screening . The Export Compliance Screening . comprising the 7 activity nodes that Seeded Subprocess Definitions 5-39 .Line process. If it does not meet export requirements. The purpose of this error handling process is to alert an administrator when an error occurs in a process and prompt the administrator to retry the process in error.Line The Export Compliance Screening . The Details property page of the process activity indicates that the Export Compliance Screening . Summary of the Export Compliance Screening .Line Process To view the properties of the Export Compliance Screening .Line process shows that the process consists of 5 unique activities. If the appropriate line flow for the line is one of the previously mentioned flows.Line process has an error item type of WFERROR. then choose Properties from the Edit menu.Line process is a subprocess.wft and is associated with the OM Order Line item type. The process can end with the following results: ■ Complete On hold Override ■ ■ Each time an order line is saved in Oracle Order Management.Generic.OM Order Line Subprocesses Export Compliance Screening . This process is not runnable. which indicates that it cannot be assigned to a transaction type. select the process in the navigator tree. If the line passes this screening process. the Export Compliance Screening . This process is a subprocess of the following line flow: ■ Line Flow . With Export Compliance When an order line is submitted that must comply with the United States Bureau of Export Administration’s Denied Party listing.

Line subprocess. The Export Compliance Screening . the Export Compliance Screening activity attempts to verify whether the line meets export requirements. The following image depicts the workflow diagram for the Export Compliance Screening . This activity has four possible results: ■ Incomplete Override Complete Hold Applied ■ ■ ■ 5-40 Using Oracle Workflow in Oracle Order Management . With Export Compliance line flow. Each node of this subprocess is numbered for referencing.Generic. At node 2. The numbers themselves are not part of the process diagram.OM Order Line Subprocesses appear in the workflow diagram.Line process is initiated as a subprocess of the Line Flow . The workflow begins at node 1 with the Start activity.

Line. the process proceeds to the End activity at node 6. An Incomplete result leads to the Export Compliance Screening . the Header Seeded Subprocess Definitions 5-41 . Deferred is initiated as a subprocess of the following line level process: ■ Line Flow .STANDARD_ None BLOCK Header Level Invoice Interface . 7) Export Compliance Screening .NOOP OE_EXPORT_COMPLIANCE_ WF. Header Level Invoice Interface . An On Hold result leads to the Export Compliance Hold Applied notification activity at node 5. refer to Chapter 6. Override or On Hold.Eligible (node 4) Function WF_STANDARD.ECS_REQUEST WF_STANDARD. 6.Line.Generic with Header Level Invoice Interface.Line subprocess. "Seeded Function Activity Definitions".Eligible activity at node 4. Activity Start (node 1) Export Compliance Screening (node 2) End (nodes 3. Export Compliance Screening .Line.Generic with Header Level Invoice Interface Each time an order line is saved in Oracle Order Management. Deferred Header Level Invoice Interface .NOOP Result Type None OM Export Compliance Results None Required Yes Yes Yes No OE_STANDARD_WF. If the appropriate line flow for the line is Line Flow . The Header Level Invoice Interface . Deferred subprocess works with the seeded header flow to support header level invoicing. the line is evaluated to determine which workflow is assigned to the line. Deferred is a workflow process that interfaces with Oracle Receivables to generate an invoice for order lines. This activity blocks the process from proceeding until it can produce a result of Complete. respectively. Upon completion of this activity.Line.Line Process Activities The following table provides descriptions of each activity in the Export Compliance Screening . This activity sends notification indicating that an export compliance hold is applied to the line.OM Order Line Subprocesses A Complete or Override result moves the process to the End activities at nodes 3 and 7. For more information about individual activities.

Deferred process is a subprocess. The Header Level Invoice Interface . Summary of the Header Level Invoice Interface .Line. Deferred process is contained in the Seeded Data File oexwford. The Header Level Invoice Interface . Deferred process shows that the process consists of 6 unique activities. The Header Level Invoice Interface is initiated as a subprocess of the Line Flow Generic with Header Level Invoice Interface line flow. The purpose of this error handling process is to alert an administrator when an error occurs in a process and prompt the administrator to retry the process in error. This error process is initiated only when an unexpected error with Oracle Workflow is encountered in the process.OM Order Line Subprocesses Level Invoice Interface .Line. Deferred process is initiated as a subprocess of the line flow. which indicates that it cannot be assigned to a transaction type. The following image depicts the workflow diagram for the Header Level Invoice Interface . then select Properties from the Edit menu. Deferred Process To view the properties of the Header Level Invoice Interface . The Details property page of the process activity indicates that the Header Level Invoice Interface .Line process has an error item type of WFERROR. comprising the 6 activity nodes that appear in the workflow diagram. This process is not runnable. select the process in the navigator tree. The numbers themselves are not part of the process diagram.Line. Deferred subprocess.Line. Each node of this subprocess is numbered for referencing. The workflow begins at node 1 with the Start activity. it is a subprocess or a line flow. 5-42 Using Oracle Workflow in Oracle Order Management .wft and is associated with the OM Order Line item type. Deferred process.Line.Line.Line. The Process window for the Header Level Invoice Interface . This item type is associated with the RETRY_ONLY error process.

Bill Only with Inventory Interface Each time an order line is saved in Oracle Order Management. For more information about individual activities.Line process is initiated as a subprocess of the line flow. After completion of node 5.Continue Header Flow continues the process to the Wait for Invoice Interface block activity in node 5.DEFER OE_FULFILL_WF.Continue Header Flow (node 4) Wait for Invoice Interface (node 5) End (node 6) Function WF_STANDARD. the Inventory Interface Non-Ship . It is initiated as a subprocess of the following line flow: ■ Line Flow .NOOP Result Type None None None None None None Required Yes Yes Yes Yes Yes Yes Inventory Interface Non-Ship . the Fulfill . the line is evaluated to determine which workflow is assigned to the line. Once the background engine restarts the process. refer to Chapter 6.wft and is associated with the OM Order Line item type.Line process is contained in the Seeded Data File oexwford. Header Level Invoice Interface .CONTINUEFLOW WF_STANDARD.NOOP WF_STANDARD. the Fulfill .START_ FULFILLMENT WF_ STANDARD. The Inventory Interface Non-Ship .Deferred (node 2) Fulfill (node 3) Fulfill . At node 4. Deferred Process Activities The following table provides descriptions of each activity in the Header Level Invoice Interface subprocess. the process proceeds to the Fulfill activity at node 3.Line is a workflow process that interfaces with Oracle Inventory to relieve reservations and demand for non-shippable order lines. Seeded Subprocess Definitions 5-43 .OM Order Line Subprocesses At node 2. If the appropriate line flow for the line is one of the previously mentioned flows.Deferred activity defers the line flow to the background engine.Line Inventory Interface Non-Ship . the process continues to the End activity at node 5. "Seeded Function Activity Definitions".WAITFORFLOW WF_STANDARD. \ Activity Start (node 1) Fulfill .Line.Generic.

Line process has an error item type of WFERROR. Each node of this subprocess is numbered for referencing. This error process is initiated only when an unexpected error with Oracle Workflow is encountered in the process. 5-44 Using Oracle Workflow in Oracle Order Management .Line process shows that the process consists of 4 unique activities. which indicates that it cannot be assigned to a transaction type.Line process. This process is not runnable. The numbers themselves are not part of the process diagram. select the process in the navigator tree. The Inventory Interface Non-Ship . comprising the 5 activity nodes that appear in the workflow diagram. it is a subprocess or a line flow. This item type is associated with the RETRY_ONLY error process. then select Properties from the Edit menu. The Details property page of the process activity indicates that the Inventory Interface Non-Ship .Line process is a subprocess. The Process window for the Inventory Interface Non-Ship .OM Order Line Subprocesses Summary of the Inventory Interface Non-Ship . The following image depicts the workflow diagram for the Inventory Interface Non-Ship .Line subprocess.Line Process To view the properties of the Inventory Interface Non-Ship . The purpose of this error handling process is to alert an administrator when an error occurs in a process and prompt the administrator to retry the process in error.

The workflow begins at node 1 with the Start activity.OM Order Line Subprocesses The Inventory Interface Non-Ship .Generic. Bill Only with Inventory Interface line flow. This activity holds the process until the line is Seeded Subprocess Definitions 5-45 . An On Hold or Incomplete result leads the process to the Inventory Interface Eligible block activity at node 4. At node 2.Line process is initiated as a subprocess of the Line Flow . the Inventory Interface activity can complete with three possible results: ■ On Hold Incomplete Complete Not Eligible ■ ■ ■ A Complete or Not Eligible result moves the process directly to an End activity.

Each time an order line is saved in Oracle Order Management. 5) WF_STANDARD. Deferred process is identical to the Inventory Interface Non-Ship . "Seeded Function Activity Definitions".Eligible (node 4) WF. Activity Start (node 1) Function WF_STANDARD. Bill Only with Inventory Interface Note: The Inventory Interface Non-Ship . the Inventory Interface Non-Ship .Line.Line. Deferred is a workflow process that is initiated as a subprocess of the following line flow: ■ Line Flow . The process then returns to the Inventory Interface activity at node 2. the line is evaluated to determine which workflow is assigned to the line.STANDARD_BLOCK End (nodes 3. Yes Handles Holds None None No Yes Inventory Interface Non-Ship . Inventory Interface Non-Ship .wft and is associated with the OM Order Line item type.NOOP OM Subprocess Results.INVENTORY_INTERFACE Inventory Interface OE_STANDARD_ .Generic. For more information about individual activities. Inventory Interface Non-Ship .Line.Line.Line subprocess.Line. Deferred is a workflow process that interfaces with Oracle Inventory to relieve reservations and demand for non-shippable order lines. The C process is contained in the Seeded Data File oexwford. refer to Chapter 6.Line process except that it contains an extra activity for deferment.OM Order Line Subprocesses manually progressed. Deferred process is initiated as a subprocess of the line flow.NOOP Result Type None Required Yes Inventory Interface OE_INV_IFACE_ (node 2) WF.Line Process Activities The following table provides descriptions of each activity in the Inventory Interface Non-Ship . If the appropriate line flow for the line is one of the previously mentioned flows. Deferred Inventory Interface Non-Ship . 5-46 Using Oracle Workflow in Oracle Order Management .

select the process in the navigator tree. The numbers themselves are not part of the process diagram. which indicates that it cannot be assigned to a transaction type. This error process is initiated only when an unexpected error with Oracle Workflow is encountered in the process. Deferred Process To view the properties of the Inventory Interface Non-Ship . The Process window for the Inventory Interface Non-Ship . it is a subprocess or a line flow. Deferred process. then select Properties from the Edit menu.Line. Each node of this subprocess is numbered for referencing.Line. The Inventory Interface Non-Ship . This item type is associated with the RETRY_ONLY error process. Deferred subprocess. This process is not runnable. Deferred process is a subprocess. comprising the 6 activity nodes that appear in the workflow diagram. The purpose of this error handling process is to alert an administrator when an error occurs in a process and prompt the administrator to retry the process in error. The Details property page of the process activity indicates that the Inventory Interface Non-Ship .Line process has an error item type of WFERROR.Line. The following image depicts the workflow diagram for the Inventory Interface Non-Ship .Line.OM Order Line Subprocesses Summary of the Inventory Interface Non-Ship . Seeded Subprocess Definitions 5-47 .Line. Deferred process shows that the process consists of 5 unique activities.

Line. the Inventory Interface . This activity holds the process until the line is manually progressed. The workflow begins at node 1 with the Start activity.Eligible (node 5) WF.DEFER . Yes Handles Holds None No 5-48 Using Oracle Workflow in Oracle Order Management . Inventory Interface Non-Ship . From this activity the process is identical to the Inventory Interface Non-Ship .Generic. "Seeded Function Activity Definitions".OM Order Line Subprocesses The Inventory Interface Non-Ship . refer to Chapter 6. An On Hold or Incomplete result leads the process to the Inventory Interface Eligible block activity at node 5.Line subprocess. For more information about individual activities. After this activity completes.Line.NOOP Result Type None None Required Yes Yes Inventory Interface WF_STANDARD. At node 3.Deferred activity defers inventory interface. the process continues to the Inventory Interface activity at node 3. respectively. Deferred subprocess. Deferred process is initiated as a subprocess of the Line Flow .Line. the Inventory Interface activity initiates a PL/SQL that has three possible results: ■ On Hold Incomplete Complete Not Eligible ■ ■ ■ A Complete or Not Eligible result moves the process directly to the End activity at node 4 or node 6. At node 2.INVENTORY_INTERFACE Inventory Interface OE_STANDARD_ . Bill Only with Inventory Interface line flow. Activity Start (node 1) Function WF_STANDARD.STANDARD_BLOCK OM Subprocess Results. The process then returns to the Inventory Interface activity at node 3.Deferred (node 2) Inventory Interface OE_INV_IFACE_ (node 3) WF. Deferred Process Activities The following table provides descriptions of each activity in the Inventory Interface Non-Ship .

ATO Item Line Flow . This process is not runnable.NOOP Result Type None Required Yes Invoice Interface . then select Properties from the Edit menu.Line process is initiated as a subprocess of the line flow.Generic with Authorize to Ship (RLM) Line Flow . Invoice Interface .wft and is associated with the OM Order Line item type. If the appropriate line flow for the line is one of the previously mentioned flows.Generic Line Flow . select the process in the navigator tree.Line is initiated as a subprocess of the following line flows: ■ Line Flow .Line Process To view the properties of the Invoice Interface . 6) Function WF_STANDARD. with Repricing at Fulfillment Line Flow .Line process. The following image depicts the workflow diagram for the Seeded Subprocess Definitions 5-49 . The Details property page of the process activity indicates that the Invoice Interface .Line process has an error item type of WFERROR. With Export Compliance Line Flow . This item type is associated with the RETRY_ONLY error process.Line process shows that the process consists of 6 unique activities. The Invoice Interface .Line Invoice Interface .Standard Service ■ ■ ■ ■ ■ Each time an order line is saved in Oracle Order Management. This error process is initiated only when an unexpected error with Oracle Workflow is encountered in the process.OM Order Line Subprocesses Activity End (nodes 4. comprising the 6 activity nodes that appear in the workflow diagram.Line is a workflow subprocess used to interface with Oracle Receivables to obtain an invoice for an order line. the Invoice Interface .Line process is contained in the Seeded Data File oexwford. it is a subprocess or a line flow. the line is evaluated to determine which workflow is assigned to the line. The Invoice Interface Line process is a subprocess.Generic.Generic. which indicates that it cannot be assigned to a transaction type. The purpose of this error handling process is to alert an administrator when an error occurs in a process and prompt the administrator to retry the process in error. Summary of the Invoice Interface . The Process window for the Invoice Interface .

the process moves to the End (Complete) activity at node 6 and returns to its parent flow.Line subprocess. where is waits until the process is manually progressed. the process moves to the Invoice Interface . When this activity ends with a Complete result. If the Invoice Interface activity returns a result of On Hold or Incomplete. The numbers themselves are not part of the process diagram. the process proceeds to the End (Complete) activity at node 6 and returns to its parent flow. The Invoice Interface .OM Order Line Subprocesses Invoice Interface .Line process begins at node 1 with the Start activity. the process moves to the Wait for Required for Revenue or Delivery where it waits the necessary revenue or delivery information. Once this information is received. In the Invoice Interface activity at node 2 the process interfaces with Oracle Receivables to generate invoicing information for the order line. 5-50 Using Oracle Workflow in Oracle Order Management . the process moves to the End (Not Eligible) activity at node 3 and returns to its parent flow. If the Invoice Interface activity returns a Not Eligible result.Eligible activity node 4. Each node of this subprocess is numbered for referencing. If the Invoice Interface activity returns a result of Partial.

Deferred Invoice Interface .NOOP Result Type None OM Subprocess Results. Bill Only with Inventory Interface Line Flow . Handles Holds None None Required Yes Yes OE_INVOICE_ WF.ATO Model Line Flow . For more information about individual activities.Return for Credit Only with Approval Line Flow .NOOP WF_STANDARD.Generic. the line is evaluated to determine which workflow is assigned to the line.Line Process Activities The following table provides descriptions of each activity in the Invoice Interface Line subprocess. Invoice Interface .INVOICE_INTERFACE WF_STANDARD.Generic.Return for Credit with Receipt and Approval ■ ■ ■ ■ ■ ■ Each time an order line is saved in Oracle Order Management.NOOP 6) Invoice Interface . Activity Start (node 1) Invoice Interface (node 2) End (Not Eligible) (node 6) Wait for Required for Revenue or Delivery (node 5) Invoice Interface Eligible (node 4) Function WF_STANDARD.Return for Credit with Receipt Line Flow . "Seeded Function Activity Definitions". Deferred is a workflow subprocess used to interface with Oracle Receivables to obtain an invoice for an order line. If the appropriate line flow for Seeded Subprocess Definitions 5-51 .Line. Bill Only Line Flow .Return for Credit Only Line Flow .OM Order Line Subprocesses Invoice Interface .BLOCK Yes Yes OE_STANDARD_ WF.Line.Line is initiated as a subprocess of the following line flows: ■ Line Flow . refer to Chapter 6.STANDARD_BLOCK None None No Yes End (Complete) (node WF_STANDARD.

select the process in the navigator tree. Deferred process is a subprocess.Line.Line. Deferred process is initiated as a subprocess of that line flow.Line. The Process window for the Invoice Interface .Line. Deferred process shows that the process consists of 7 unique activities. The following image depicts the workflow diagram for the Invoice Interface . Deferred process is identical to the Invoice Interface . the Invoice Interface .Line. This process is not runnable. Deferred subprocess. 5-52 Using Oracle Workflow in Oracle Order Management . Deferred process.Line.Line process except that it contains an extra activity for deferment. Deferred Process To view the properties of the Invoice Interface . This item type is associated with the RETRY_ONLY error process.OM Order Line Subprocesses the line is one of the previously mentioned flows. Deferred process has an error item type of WFERROR.Line. The Details property page of the process activity indicates that the Invoice Interface .Line.wft and is associated with the OM Order Line item type. it is a subprocess or a line flow.Line. The Invoice Interface . The Invoice Interface . Deferred process is contained in the Seeded Data File oexwford. then select Properties from the Edit menu. comprising the 7 activity nodes that appear in the workflow diagram. Each node of this subprocess is numbered for referencing. The purpose of this error handling process is to alert an administrator when an error occurs in a process and prompt the administrator to retry the process in error. Summary of the Invoice Interface . This error process is initiated only when an unexpected error with Oracle Workflow is encountered in the process. which indicates that it cannot be assigned to a transaction type. Note: The Invoice Interface . The numbers themselves are not part of the process diagram.

the process moves to the Wait for Required for Revenue or Delivery where it waits until the revenue or delivery information is received. If the Invoice Interface activity returns a result of On Hold or Incomplete. In the Invoice Interface . Seeded Subprocess Definitions 5-53 . In the Invoice Interface activity at node 3 the process interfaces with Oracle Receivables to generate invoicing information for the order line.Eligible activity node 7.Deferred activity at node 2 defers the process to the background engine.Line process begins at node 1 with the Start activity. Once this information is received. When this activity ends with a Complete result. the process moves to the Invoice Interface . where is waits until the process is manually progressed. Once the background engine is run.OM Order Line Subprocesses The Invoice Interface . If the Invoice Interface activity returns a Not Eligible result. the process moves to the End (Not Eligible) activity at node 4 and returns to its parent flow. If the Invoice Interface activity returns a result of Partial. the process proceeds to the End (Complete) activity at node 6 and returns to its parent flow. the process resumes. the process moves to the End (Complete) activity at node 6 and returns to its parent flow.

Line subprocess. Deferred The Purchase Release .Line.Line. the Purchase Release .STANDARD_BLOCK None None Yes Yes Purchase Release .Line. Deferred process is contained in the Seeded Data File oexwford. 5-54 Using Oracle Workflow in Oracle Order Management . Activity Start (node 1) Invoice Interface Deferred (node 2) Invoice Interface (node 3) End (Not Eligible) (node 4) Wait for Required for Revenue or Delivery (node 5) Function WF_STANDARD. Deferred subprocess.NOOP WF_STANDARD.Line.wft and is associated with the OM Order Line item type. Handles Holds None None Required Yes Yes Yes OE_INVOICE_ WF.Line Each time an order line is saved in Oracle Order Management. Deferred Process Activities The following table provides descriptions of each activity in the Invoice Interface Line.NOOP WF_STANDARD.OM Order Line Subprocesses Invoice Interface . It is initiated as a subprocess of the following subprocess: ■ Create Supply . The Purchase Release . the line is evaluated to determine which workflow is assigned to the line. "Seeded Function Activity Definitions". If the assigned line flow for the line contains Create Supply . For more information about individual activities.Line.BLOCK Yes Yes End (Complete) (node WF_STANDARD. refer to Chapter 6.NOOP 6) Invoice Interface Eligible (node 7) OE_STANDARD_ WF. Deferred subprocess interfaces to Oracle Purchasing for externally sourced lines. Deferred process is initiated as a subprocess of that subprocess.INVOICE_INTERFACE WF_STANDARD.DEFER Result Type None None OM Subprocess Results.

Deferred process has an error item type of WFERROR. The Purchase Release .Line. which indicates that it cannot be assigned to a transaction type.Line. This process is not runnable. The following image depicts the workflow diagram for the Purchase Release . it is a subprocess or a line flow. This item type is associated with the RETRY_ONLY error process. Deferred process. Deferred process shows that the process consists of 5 unique activities. select the process in the navigator tree.Line.Line. Deferred Process To view the properties of the Purchase Release .Line. The numbers themselves are not part of the process diagram. comprising the 6 activity nodes that appear in the workflow diagram. then select Properties from the Edit menu.Line. The Details property page of the process activity indicates that the Purchase Release . Seeded Subprocess Definitions 5-55 . This error process is initiated only when an unexpected error with Oracle Workflow is encountered in the process. The Purchase Release . Deferred subprocess begins at node 1 with the Start activity. The Process window for the Purchase Release .Line. Deferred process is a subprocess. Deferred subprocess. Each node of this subprocess is numbered for referencing. The purpose of this error handling process is to alert an administrator when an error occurs in a process and prompt the administrator to retry the process in error.OM Order Line Subprocesses Summary of the Purchase Release .

For more information about individual activities. Deferred process but is used specifically for ATO order lines. This activity enables you to manually progress the order. the process moves into the Purchase Release .ATO subprocess interfaces to Oracle Purchasing for externally sourced lines. Deferred subprocess. In the Purchase Release activity at node 3.Line. Purchase Release .Line. Deferred Process Activities The following table provides descriptions of each activity in the Purchase Release Line.ATO The Purchase Release . Activity Start (node 1) Purchase Release Deferred (node 2) Purchase Release (node 3) Purchase Release Eligible (node 5) End (nodes 4. It is initiated as a subprocess of the following subprocess: ■ Create ATO Supply Note: The Purchase Release .NOOP Result Type None None Required Yes Yes OM Subprocess Results.OM Order Line Subprocesses The Purchase Release . 6) Function WF_STANDARD. "Seeded Function Activity Definitions". If the Purchase Release activity returns a Complete or Not Eligible result.RELEASE_TO_ PURCHASING OE_STANDARD_ WF.Line. the process proceeds to an End activity and returns to its parent process.Eligible activity at node 5.Line.NOOP WF_STANDARD.Deferred activity at node 2 moves processing to the background engine. 5-56 Using Oracle Workflow in Oracle Order Management .STANDARD_BLOCK WF_STANDARD. If the Purchase Release activity returns an On Hold or Incomplete result. Deferred . refer to Chapter 6. the process releases a record to the Oracle Purchasing requisition import tables.DEFER OE_OEOL_SCH. Yes Handles Holds None None No Yes Purchase Release .Line. Deferred . Deferred ATO subprocess is identical to the Purchase Release .

ATO subprocess. Each node of this subprocess is numbered for referencing.ATO process is a subprocess.ATO process has an error item type of WFERROR. Deferred ATO Process To view the properties of the Purchase Release .OM Order Line Subprocesses Each time an order line is saved in Oracle Order Management.Line. This process is not runnable. Deferred . Deferred . the line is evaluated to determine which workflow is assigned to the line. Summary of the Purchase Release . Deferred ATO process is initiated as a subprocess of that subprocess. The Purchase Release .ATO process shows that the process consists of 5 unique activities.Line. it is a subprocess or a line flow. Deferred . If the assigned line flow for the line contains Create ATO Supply subprocess. then select Properties from the Edit menu. This error process is initiated only when an unexpected error with Oracle Workflow is encountered in the process.ATO process. comprising the 6 activity nodes that appear in the workflow diagram.Line.Line.Line. This item type is associated with the RETRY_ONLY error process.Line. The numbers themselves are not part of the process diagram. Deferred . which indicates that it cannot be assigned to a transaction type. The Details property page of the process activity indicates that the Purchase Release . Deferred . The Purchase Release . The following image depicts the workflow diagram for the Purchase Release . select the process in the navigator tree. the Purchase Release .Line.Line. The purpose of this error handling process is to alert an administrator when an error occurs in a process and prompt the administrator to retry the process in error.wft and is associated with the OM Order Line item type. The Process window for the Purchase Release . Seeded Subprocess Definitions 5-57 . Deferred ATO process is contained in the Seeded Data File oexwford.

OM Order Line Subprocesses

The Purchase Release - Line, Deferred - ATO subprocess begins at node 1 with the Start activity. The Purchase Release - Deferred activity at node 2 moves processing to the background engine. In the Purchase Release activity at node 3, the process releases a record to the Oracle Purchasing requisition import tables. If the Purchase Release activity returns an On Hold or Incomplete result, the process moves into the Purchase Release - Eligible activity at node 5. This activity enables you to manually progress the order. If the Purchase Release activity returns a Complete or Not Eligible result, the process proceeds to an End activity and returns to its parent process.

Purchase Release - Line, Deferred - ATO Process Activities
The following table provides descriptions of each activity in the Purchase Release Line, Deferred - ATO subprocess. For more information about individual activities, refer to Chapter 6, "Seeded Function Activity Definitions".

5-58

Using Oracle Workflow in Oracle Order Management

OM Order Line Subprocesses

Activity Start (node 1) Purchase Release Deferred (node 2) Purchase Release (node 3) Purchase Release Eligible (node 5) End (nodes 4, 6)

Function WF_STANDARD.NOOP WF_STANDARD.DEFER OE_OEOL_SCH.RELEASE_TO_ PURCHASING OE_STANDARD_ WF.STANDARD_BLOCK WF_STANDARD.NOOP

Result Type None None

Required Yes Yes

OM Subprocess Results, Yes Handles Holds None None No Yes

Purchase Release - Line, Manual
The Purchase Release - Line, Manual subprocess interfaces to Oracle Purchasing for externally sourced lines. Purchase Release - Line, Manual enables you to manually progress the process instead of waiting for the background engine to pick it up.
Note: The Purchase Release - Line, Manual subprocess is identical

to the Purchase Release - Line, Deferred process except that it does not contain a deferment activity. The Purchase Release - Line, Manual process is contained in the Seeded Data File oexwford.wft and is associated with the OM Order Line item type.

Summary of the Purchase Release - Line, Manual Process
To view the properties of the Purchase Release - Line, Manual process, select the process in the navigator tree, then select Properties from the Edit menu. The Purchase Release - Line, Manual process is a subprocess. This process is not runnable, which indicates that it cannot be assigned to a transaction type; it is a subprocess or a line flow. The Details property page of the process activity indicates that the Purchase Release - Line, Manual process has an error item type of WFERROR. This item type is associated with the RETRY_ONLY error process. The purpose of this error handling process is to alert an administrator when an error occurs in a process and prompt the administrator to retry the process in error. This error process is initiated only when an unexpected error with Oracle Workflow is encountered in the process.

Seeded Subprocess Definitions 5-59

OM Order Line Subprocesses

The Process window for the Purchase Release - Line, Manual process shows that the process consists of 4 unique activities, comprising the 5 activity nodes that appear in the workflow diagram. The following image depicts the workflow diagram for the Purchase Release - Line, Manual subprocess. Each node of this subprocess is numbered for referencing. The numbers themselves are not part of the process diagram.

The Purchase Release - Line, Manual subprocess begins at node 1 with the Start activity. In the Purchase Release - Eligible activity at node 2, the activity must be manually progressed to the Purchase Release activity at node 3. If the Purchase Release activity returns an On Hold or Incomplete result, the process returns to the Purchase Release - Eligible activity at node 2. If the Purchase Release activity returns a Complete or Not Eligible result, the process proceeds to an End activity and returns to its parent process.

Purchase Release - Line, Deferred Process Activities
The following table provides descriptions of each activity in the Purchase Release Line, Deferred subprocess. For more information about individual activities, refer to Chapter 6, "Seeded Function Activity Definitions".

5-60

Using Oracle Workflow in Oracle Order Management

OM Order Line Subprocesses

Activity Start (node 1) Purchase Release Eligible (node 2) Purchase Release (node 3) End (nodes 4, 5)

Function WF_STANDARD.NOOP OE_STANDARD_ WF.STANDARD_BLOCK OE_OEOL_SCH.RELEASE_TO_ PURCHASING WF_STANDARD.NOOP

Result Type None None

Required Yes No

OM Subprocess Results, Yes Handles Holds None Yes

Reprice - Line
The Reprice - Line subprocess enables you to reprice an order line. This is useful for invoicing purposes. Reprice - Line is initiated as a subprocess of the following line flow:

Line Flow - Generic, with Repricing at Fulfillment

Each time an order line is saved in Oracle Order Management, the line is evaluated to determine which workflow is assigned to the line. If the assigned line flow is Line Flow - Generic, with Repricing at Fulfillment, the Reprice - Line process is initiated as a subprocess of the line flow. Reprice - Line is contained in the Seeded Data File oexwford.wft and process is associated with the OM Order Line item type.

Summary of the Reprice - Line Process
To view the properties of the Reprice - Line process, select the process in the navigator tree, then select Properties from the Edit menu. The Reprice - Line process is a subprocess. This process is not runnable, which indicates that it cannot be assigned to a transaction type; it is a subprocess or a line flow. The Details property page of the process activity indicates that the Reprice - Line process has an error item type of WFERROR. This item type is associated with the RETRY_ONLY error process. The purpose of this error handling process is to alert an administrator when an error occurs in a process and prompt the administrator to retry the process in error. This error process is initiated only when an unexpected error with Oracle Workflow is encountered in the process. The Process window for the Reprice - Line process shows that the process consists of 4 unique activities, comprising the 5 activity nodes that appear in the workflow diagram. The following image depicts the workflow diagram for the Reprice - Line

Seeded Subprocess Definitions 5-61

OM Order Line Subprocesses

subprocess. Each node of this subprocess is numbered for referencing. The numbers themselves are not part of the process diagram.

The Reprice - Line subprocess begins at node 1 with the Start activity. In the Reprice activity at node 2, the reprices the line. If the Reprice activity returns an Incomplete result then the process moves to the Reprice - Eligible activity at node 4. The process must be manually progressed to return to the Reprice activity. If the Purchase Release activity returns an Not Eligible or Complete result, the process proceeds to an End activity and returns to its parent process.

Reprice - Line Process Activities
The following table provides descriptions of each activity in the Reprice - Line subprocess. For more information about individual activities, refer to Chapter 6, "Seeded Function Activity Definitions".
Activity Start (node 1) Function WF_STANDARD.NOOP Result Type None Required Yes

5-62

Using Oracle Workflow in Oracle Order Management

Return Receiving . 5) Function OE_REPRICE_WF.STANDARD_BLOCK WF_STANDARD.Line is initiated as a subprocess of the following line flows: ■ Line Flow . If the assigned line flow is Line Flow . The Details property page of the process activity indicates that the Return Receiving .Line process. The purpose of this error handling process is to alert an administrator when an error occurs in a process and prompt the administrator to retry the process in error. This error process is initiated only when an unexpected error with Oracle Workflow is encountered in the process. the line is evaluated to determine which workflow is assigned to the line.Line process is a subprocess.wft and process is associated with the OM Order Line item type.Line is contained in the Seeded Data File oexwford.Line Process To view the properties of the Return Receiving .START_ REPRICING OE_STANDARD_ WF. Summary of the Return Receiving . then select Properties from the Edit menu.Return for Credit with Receipt and Approval ■ Each time an order line is saved in Oracle Order Management.Line The Return Receiving . The Return Receiving . The Process window for the Return Receiving .Return for Credit with Receipt Line Flow . The Return Receiving Line subprocess executes a series of activities that determine the status of a returned item. which indicates that it cannot be assigned to a transaction type. select the process in the navigator tree. it is a subprocess or a line flow. Return Receiving . the Return Receiving . This process is not runnable.OM Order Line Subprocesses Activity Reprice (node 2) Reprice .Line subprocess is used in returns. This item type is associated with the RETRY_ONLY error process.Return for Credit with Receipt and Approval. comprising the 5 activity nodes that appear in the Seeded Subprocess Definitions 5-63 .NOOP Result Type Required OM Subprocess Results No None None Yes Yes Return Receiving .Line process shows that the process consists of 4 unique activities.Line process is initiated as a subprocess of the line flow.Eligible (node 3) End (nodes 4.Line process has an error item type of WFERROR.Return for Credit with Receipt or Line Flow .

5-64 Using Oracle Workflow in Oracle Order Management . Return Receiving .Line Process Activities The following table provides descriptions of each activity in the Return Receiving Line subprocess. If the line is a return.OM Order Line Subprocesses workflow diagram. The Return Receiving . The numbers themselves are not part of the process diagram. If the return item is not eligible for receiving. If the return item is eligible for receiving.Line subprocess. the process ends. The following image depicts the workflow diagram for the Return Receiving . After the inspection is complete the process moves to the End (Complete) activity at node 5 and returns to its parent process. Each node of this subprocess is numbered for referencing. it is not eligible for return receiving and the process closes. In the Wait for Receiving activity at node 3 the process waits until the return item is received before progressing.Line subprocess begins at node 1 with the Start activity. the process then moves to the Wait for Inspection activity at node 4. In the Utility to Get Line Category activity at node 2 determines whether the line is an order or a return.

This process is a subprocess of the following line flows: ■ Line Flow .Generic.Generic.WAIT_FOR_ RECEIVING Result Type None Line Category Required Yes No OM Subprocess Success Yes Results None None None Yes Yes Yes Wait for Inspection WF_STANDARD.Line The Schedule . "Seeded Function Activity Definitions". the line is evaluated to determine which workflow is assigned to the line.Generic with Header Level Invoice Interface Line Flow .NOOP WF_STANDARD. Ship Only Line Flow .ATO Item Line Flow .Line subprocess schedules an order line for all order lines that must be shipped.Generic Line Flow . 7) WF_STANDARD.Generic with Authorize to Ship (RLM) Line Flow .Generic. With Export Compliance Line Flow .NOOP OE_STANDARD_WF. The Schedule .wft and is associated with the OM Order Line item type.ATO Model Line Flow .BLOCK (node 4) End (Complete) (node 5) End (Not Eligible) (nodes 6. If the appropriate line flow for the line is one of the previously mentioned flows. with Repricing at Fulfillment ■ ■ ■ ■ ■ ■ ■ Each time an order line is saved in Oracle Order Management. Activity Start (node 1) Utility to Get Line Category (node 2) Wait for Receiving (node 3) Function WF_STANDARD.Line process is contained in the Seeded Data File oexwford.OM Order Line Subprocesses For more information about individual activities. refer to Chapter 6.NOOP Schedule . Seeded Subprocess Definitions 5-65 .GET_ LINE_CATEGORY OE_RMA_WF.Line process is initiated as a subprocess of the line flow. the Schedule .

This process is not runnable.Line process shows that the process consists of 4 unique activities. which indicates that it cannot be assigned to a transaction type. then select Properties from the Edit menu. comprising the 5 activity nodes that appear in the workflow diagram. The Schedule . The Schedule . The Details property page of the process activity indicates that the Schedule .OM Order Line Subprocesses Summary of the Schedule . it is a subprocess or a line flow.Line Process To view the properties of the Schedule . The following image depicts the workflow diagram for the Schedule Line subprocess. 5-66 Using Oracle Workflow in Oracle Order Management . The numbers themselves are not part of the process diagram. This item type is associated with the RETRY_ONLY error process. Each node of this subprocess is numbered for referencing. This error process is initiated only when an unexpected error with Oracle Workflow is encountered in the process.Line subprocess begins at node 1 with the Start activity. The Process window for the Schedule .Line process is a subprocess. The purpose of this error handling process is to alert an administrator when an error occurs in a process and prompt the administrator to retry the process in error. select the process in the navigator tree.Line process.Line process has an error item type of WFERROR.

Line Process Activities The following table provides descriptions of each activity in the Schedule . If the Schedule activity returns a result of Incomplete or On Hold.NOOP Result Type None Required Yes OM Subprocess Results. Activity Start (node 1) Schedule (node 2) Schedule .Line. Deferred process is contained in the Seeded Data File oexwford. Seeded Subprocess Definitions 5-67 . the process proceeds to an End activity and returns to its parent process. Schedule .Line.STANDARD_BLOCK WF_STANDARD. Note: The Schedule . The Schedule .Eligible (node 3) End (nodes 4. Deferred The Schedule . Deferred subprocess is identical to the Schedule . 5) Function WF_STANDARD.Line. From there the process must be manually progressed to return to the Schedule activity. the process moves to the Schedule . No Handles Holds None None Yes Yes Schedule .NOOP OE_OEOL_SCH.Line process except that it contains two new activities: an activity to determine whether the line is scheduled.wft and is associated with the OM Order Line item type.Line subprocess schedules an order line for all order lines that must be shipped. For more information about individual activities. and a defer activity.Line subprocess. If the Schedule activity returns a Not Eligible or Complete result.OM Order Line Subprocesses The Schedule activity at node 2 attempts to schedule the order line. refer to Chapter 6.Eligible activity at node 4. "Seeded Function Activity Definitions".SCHEDULE_ LINE OE_STANDARD_ WF.

which indicates that it cannot be assigned to a transaction type.Line. Deferred subprocess. This item type is associated with the RETRY_ONLY error process.Line. The Details property page of the process activity indicates that the Invoice Interface . Deferred process is a subprocess.Line. This process is not runnable. Deferred process shows that the process consists of 6 unique activities. The Process window for the Schedule . it is a subprocess or a line flow.Line. Deferred process.Line.OM Order Line Subprocesses Summary of the Schedule . Deferred process has an error item type of WFERROR. The numbers themselves are not part of the process diagram. This error process is initiated only when an unexpected error with Oracle Workflow is encountered in the process. 5-68 Using Oracle Workflow in Oracle Order Management . Deferred To view the properties of the Schedule . The following image depicts the workflow diagram for the Schedule .Line. The purpose of this error handling process is to alert an administrator when an error occurs in a process and prompt the administrator to retry the process in error. Each node of this subprocess is numbered for referencing. select the process in the navigator tree. then select Properties from the Edit menu. The Schedule . comprising the 9 activity nodes that appear in the workflow diagram.

9) WF_STANDARD.DEFER OE_OEOL_SCH.Line.ATO Item Seeded Subprocess Definitions 5-69 . From there the process must be manually progressed to return to the Schedule activity.Line. If scheduling has not yet been completed. Deferred Process Activities The following table provides descriptions of each activity in the Schedule . "Seeded Function Activity Definitions".SCHEDULE_ LINE OE_STANDARD_ WF. the process ends and returns to its parent flow. Manual enables you to manually initiate shipping for an order line.Line.Line. Ship . No Handles Holds None None Yes Yes End (nodes 3.Line. For more information about individual activities.Eligible (node 8) Function WF_STANDARD. the process moves to the Schedule .IS_LINE_ SCHEDULED WF_STANDARD. If scheduling is complete or the line is not eligible for scheduling. Deferred subprocess begins at node 1 with the Start activity.NOOP OE_OEOL_SCH.NOOP Ship . the process proceeds to an End activity and returns to its parent process.Line. refer to Chapter 6. If the Schedule activity returns a result of Incomplete or On Hold.OM Order Line Subprocesses The Schedule . If the Schedule activity returns a Not Eligible or Complete result.Deferred activity at node 5.STANDARD_BLOCK Result Type None Required Yes OM Subprocess Results No None Yes OM Subprocess Results.Deferred (node 5) Schedule (node 6) Schedule . This activity moves scheduling to the background engine. 7.Eligible activity at node 8. 4. Manual Ship . the process moves to the Schedule . Manual is initiated as a subprocess of the following line flows: ■ Line Flow . The Is Line Scheduled activity at node 2 determines whether the line has already been scheduled. Schedule . Activity Start (node 1) Is Line Scheduled (node 2) Schedule . Deferred subprocess. The Schedule activity at node 6 attempts to schedule the order line.

With Export Compliance Line Flow . The following image depicts the workflow diagram for the Ship . The Process window for the Ship . The numbers themselves are not part of the process diagram.Configuration with Authorize to Ship (RLM) Line Flow . If the appropriate line flow for the line is one of the previously mentioned flows. which indicates that it cannot be assigned to a transaction type. This process is not runnable. The Details property page of the process activity indicates that the Ship . Manual process.Line.Generic with Authorize to Ship (RLM) Line Flow .Line. Manual process has an error item type of WFERROR.Generic Line Flow . Manual subprocess. Manual process is contained in the Seeded Data File oexwford. Manual process is initiated as a subprocess of that line flow. 5-70 Using Oracle Workflow in Oracle Order Management .Line.Configuration Line Flow .Generic. This error process is initiated only when an unexpected error with Oracle Workflow is encountered in the process. The Ship . select the process in the navigator tree. Summary of the Ship . The purpose of this error handling process is to alert an administrator when an error occurs in a process and prompt the administrator to retry the process in error. Each node of this subprocess is numbered for referencing. Manual Process To view the properties of the Ship .Generic with Header Level Invoice Interface Line Flow .Generic.Line. Manual process shows that the process consists of 6 unique activities.Line. This item type is associated with the RETRY_ONLY error process. then select Properties from the Edit menu.wft and is associated with the OM Order Line item type.OM Order Line Subprocesses ■ Line Flow . the line is evaluated to determine which workflow is assigned to the line. Ship Only ■ ■ ■ ■ ■ ■ Each time an order line is saved in Oracle Order Management. comprising the 6 activity nodes that appear in the workflow diagram. it is a subprocess or a line flow. The Ship . the Ship .Line.Line.Line. Manual process is a subprocess.

which returns one of the following four results: ■ Over Shipped Beyond Tolerance Ship Confirm Non Shippable Unreserved ■ ■ ■ If the Ship activity returns the Over Shipped Beyond Tolerance result. the process moves to an End activity and returns to its parent line flow. Non Shippable. or Unreserved result.Line. a notification is sent and the process moves to an End activity and returns to its parent line flow.OM Order Line Subprocesses The Ship . If the Ship activity returns a Ship Confirm. Manual subprocess begins at node 1 with the Ship activity. Seeded Subprocess Definitions 5-71 .

NOOP Shippable)(node 5) End (Unreserve) (nodes 6) WF_STANDARD. For more information about individual activities.DEFER Result Type Shipping Results None Required Yes Yes End (Over Shipped WF_STANDARD.Line. Manual Process Activities The following table provides descriptions of each activity in the Ship . refer to Chapter 6. "Seeded Function Activity Definitions".Line. Yes Handles Holds None None Yes Yes 5-72 Using Oracle Workflow in Oracle Order Management .NOOP Beyond Tolerance) (node 4) End (Non WF_STANDARD.OM Order Line Subprocesses Ship . Activity Ship (node 1) End (Ship Confirm) (node 2) Function OE_SHIPPING_WF. Manual subprocess.START_ SHIPPING WF_STANDARD.NOOP OM Subprocess Results.

The following topics are addressed: ■ OM Order Header on page 6-2 OM Order Line on page 6-9 OM Standard on page 6-45 Standard on page 6-46 ■ ■ ■ Seeded Function Activity Definitions 6-1 .6 Seeded Function Activity Definitions This chapter discusses the different functions and activities used by Oracle Order Management in Oracle Workflow.

Approve . upon completion the approval process.wft. The Approve .Continue Line activity is an OM Order Header activity that uses standard Oracle Workflow functionality to continue the workflow in progress. Book The Book activity calls the PL/SQL procedure named OE_BOOK_WF.Continue Line activity: The Approve .BOOK_ORDER to book an order. the halted process will continue.Continue Line The Approve .Continue Line activity is contained in the Seeded Data File oexwford.Continue Line activity calls the PL/SQL procedure named WF_ STANDARD.Continue Line activity is used to mark the position in the process where. Handles Holds.OM Order Header OM Order Header Approve . The Approve . The following image depicts the Book activity: 6-2 Using Oracle Workflow in Oracle Order Management .Continue Flow activity contains two activity attributes: ■ Waiting Flow Waiting Activity ■ The following image depicts the Approve . This lookup contains the following result codes: ■ Complete Incomplete On Hold Not Eligible ■ ■ ■ The Book activity will complete with one of these results. and is associated with the OM Order Header item type. The Book activity uses the lookup OM Subprocess Results.CONTINUEFLOW.

OM Order Header

The Book activity is contained in the Seeded Data File oexwford.wft, and is associated with the OM Order Header item type.

Book - Continue Line (Complete)
The Book - Continue Line (Complete) activity is an OM Order Header activity that uses standard Oracle Workflow functionality to continue the workflow in progress. Book - Continue Line (Complete) marks the position in the process where, upon completion of booking, the halted line level process will continue. The Book - Continue Line (Complete) activity calls the PL/SQL procedure named WF_STANDARD.CONTINUEFLOW. The Book - Continue Flow (Complete) activity contains two activity attributes:

Waiting Flow Waiting Activity

The following image depicts the Book - Continue Line (Complete) activity:

The Book - Continue Line (Complete) activity is contained in the Seeded Data File oexwford.wft, and is associated with the OM Order Header item type.

Book - Deferred
The Book - Deferred function activity is an OM Order Header activity that uses standard Oracle Workflow functionality to defer the booking activity to the background engine. To use Book - Deferred, the Book activity must be placed immediately after it in the process flow.

Seeded Function Activity Definitions

6-3

OM Order Header

The Book - Deferred activity calls the PL/SQL procedure named WF_ STANDARD.DEFER. Defer activities defer the subsequent process thread to the background queue without requiring you to change the cost of each activity in that thread to a value above the Workflow Engine threshold. This activity always interrupts the process thread by causing a disconnect to occur in the current database session, even if the thread is already deferred. The following image depicts the Book - Deferred activity:

The Book - Deferred activity is contained in the Seeded Data File oexwford.wft, and is associated with the OM Order Header item type.

Book - Eligible
To enable a function for manual completion, you must place a special block activity before the actual function activity. For booking, the Book - Eligible activity is the special block activity that facilitates manual booking. A process will stop upon reaching the Book - Eligible activity. The Progress Order LOV on the Sales Order form will show you that this order is eligible for booking. You can book such an order either by selecting OK on the LOV, or by selecting Book on the Sales Order form. The Book - Eligible activity calls the PL/SQL procedure named OE_STANDARD_ WF.STANDARD_BLOCK. The following image depicts the Book - Eligible activity:

The Book - Eligible activity is contained in the Seeded Data File oexwford.wft, and is associated with the OM Order Header item type.

6-4

Using Oracle Workflow in Oracle Order Management

OM Order Header

Close
The Close activity calls the PL/SQL procedure named OE_CLOSE_WF.CLOSE_ ORDER to close an order. The Close activity uses the lookup OM Subprocess Results, Handles Holds. This lookup contains the following result codes:

Complete Incomplete On Hold Not Eligible

The Close activity will complete with one of these results. The following image depicts the Close activity:

The Close activity is contained in the Seeded Data File oexwford.wft, and is associated with the OM Order Header item type.

Close - Wait for Line
An order cannot close until all of its lines have been closed. The Close - Wait for Line activity is an OM Order Header activity that uses standard Oracle Workflow functionality to pause the process until all line processes are complete. Close - Wait for Line marks the position in the process where, when all the lines are closed, the halted header level process will continue. The Close - Wait for Line activity calls the PL/SQL procedure named WF_ STANDARD.WAITFORFLOW. The Close - Wait for Line activity contains two activity attributes:

Continuation Activity Continuation Flow

The following image depicts the Close - Wait for Line activity:

Seeded Function Activity Definitions

6-5

OM Order Header

The Close - Wait for Line activity is contained in the Seeded Data File oexwford.wft, and is associated with the OM Order Header item type.

Enter
The Enter activity is an OM Order Header activity that is used to mark the start of an OM Order Header process. Enter is a Noop activity. A Noop activity acts as a place holder activity that performs no action. You can use this activity anywhere you want to place a node without performing an action. The Enter activity calls the PL/SQL procedure named WF_STANDARD.NOOP. The following image depicts the Enter activity:

The Enter activity is contained in the Seeded Data File oexwford.wft, and is associated with the OM Order Header item type.

Fulfill - Wait for Line
This activity is user in header level invoicing processes to halt invoicing until after all lines in an order are fulfilled. The Fulfill - Wait for Line activity is an OM Order Header activity that uses Oracle Workflow functionality to pause the process until all the order lines are fulfilled. Once fulfilled, the header level invoicing process can proceed with invoicing. The Fulfill - Wait for Line activity calls the PL/SQL procedure named WF_ STANDARD.WAITFORFLOW. The Fulfill - Wait for Line activity contains the following activity attributes:

Waiting Flow Waiting Activity

6-6

Using Oracle Workflow in Oracle Order Management

OM Order Header

The following image depicts the Fulfill - Wait for Line activity:

The Fulfill - Wait for Line activity is contained in the Seeded Data File oexwford.wft, and is associated with the OM Order Header item type.

Header Invoice Interface - Eligible
To enable a function for manual completion, you must place a special block activity before the actual function activity. For header level invoice interface, the Header Invoice Interface - Eligible activity is the special block activity that facilitates this. The Header Invoice Interface - Eligible activity calls the PL/SQL procedure named OE_STANDARD_WF.STANDARD_BLOCK. The following image depicts the Header Invoice Interface - Eligible activity:

The Header Invoice Interface - Eligible activity is contained in the Seeded Data File oexwford.wft, and is associated with the OM Order Header item type.

Invoice Interface - Continue Line
The Invoice Interface - Continue Line activity is an OM Order Header activity that uses standard Oracle Workflow functionality to continue the workflow in progress. Invoice Interface - Continue Line marks the position in the process where, once invoice interface is complete, the line level process will continue. The Invoice Interface - Continue Line activity calls the PL/SQL procedure named WF_STANDARD.CONTINUEFLOW. The Invoice Interface - Continue Flow activity contains two activity attributes:

Waiting Flow

Seeded Function Activity Definitions

6-7

This lookup contains the following result codes: ■ Complete Incomplete Not Eligible On Hold Partial ■ ■ ■ ■ The following image depicts the Invoice Interface .Header Level The Invoice Interface . Invoice Interface . Invoice Interface .Header Level activity is contained in the Seeded Data File oexwford.Header Level activity: The Invoice Interface .INVOICE_INTERFACE to conduct header level invoice interfacing. 6-8 Using Oracle Workflow in Oracle Order Management . and is associated with the OM Order Header item type. and is associated with the OM Order Header item type.OM Order Header ■ Waiting Activity The following image depicts the Invoice Interface .wft.wft.Header Level activity is an OM Order Header activity that calls the PL/SQL procedure named OE_INVOICE_WF.Header Level uses the lookup (has a result type of) Invoice Results.Continue Line activity is contained in the Seeded Data File oexwford.Continue Line activity: The Invoice Interface .

Wait for Authorization The Authorize to Ship . when the line is authorized.Check Status activity is contained in the Seeded Data File oexwford.Check Status activity: The Authorize to Ship . Authorize to Ship .Wait for Authorization marks the position in the process where. the halted process will continue. Authorize to Ship .BLOCK.Wait for Authorization activity: Seeded Function Activity Definitions 6-9 .Check Status activity is an OM Order Line activity that calls the PL/SQL procedure named OE_RLM_WF. and is associated with the OM Order Line item type.Wait for Authorization activity is an OM Order Line activity that uses the Oracle Workflow block functionality to pause a process until authorization for shipping is determined.Wait for Authorization activity calls the PL/SQL procedure named WF_STANDARD.Check Status uses the lookup (has a result type of) Yes/No. The Authorize to Ship .CHECK_AUTHORIZE_TO_SHIP to determine whether an order line is authorized for shipping.wft. This lookup contains the following result codes: ■ Yes No ■ The following image depicts the Authorize to Ship . The following image depicts the Authorize to Ship .OM Order Line OM Order Line Authorize to Ship .Check Status The Authorize to Ship . Authorize to Ship .

This PL/SQL procedure submits a concurrent program to create a work order and reserve it to the order line AutoCreate FAS contains the following attributes: ■ Arguments 11-100 Application Short Name Program Short Name Number Of Arguments Item Attribute Name Order Number Dummy Field Offset Days Load Type Status Type AFAS Org ID Class Code Failed Req ID Order Line ID Batch ID ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ 6-10 Using Oracle Workflow in Oracle Order Management .Wait for Authorization activity is contained in the Seeded Data File oexwford. AutoCreate FAS The AutoCreate FAS activity is an OM Order Line activity that calls the Oracle Configure to Order PL/SQL procedure named CTO_WORKFLOW. and is associated with the OM Order Line item type.wft.SUBMIT_CONC_ PROG_WF.OM Order Line The Authorize to Ship .

and is associated with the OM Order Line item type. Seeded Function Activity Definitions 6-11 .AUTO_ CREATE_PUR_REQ to place a record in the PO req interface tables for the order line. Requisition import creates a requisition and reserves it to the sales order line The AutoCreate PO Req activity uses the lookup (has a result type of) Config Process Results.wft. This lookup contains the following result codes: ■ Complete Incomplete ■ The following image depicts the AutoCreate PO Req activity: The AutoCreate PO Req activity is contained in the Seeded Data File oexwford. and is associated with the OM Order Line item type. This lookup contains the following result codes: ■ Cancelled Error Normal Terminated Warning ■ ■ ■ ■ The following image depicts the AutoCreate FAS activity: The AutoCreate FAS activity is contained in the Seeded Data File oexwford.wft.OM Order Line The AutoCreate FAS activity uses the lookup (has a result type of) Concurrent Program Status. AutoCreate PO Req The AutoCreate PO Req activity is an OM Order Line activity that calls the Oracle Configure to Order PL/SQL procedure named CTO_WORKFLOW_API_PK.

The Branch on Source Type activity uses the lookup (has a result type of) Source Type.OM Order Line Branch on Source Type The Branch on Source Type activity is an OM Order Line activity that calls the PL/SQL procedure named OE_OEOL_SCH.BRANCH_ON_SOURCE_TYPE to determine source type for a line. 6-12 Using Oracle Workflow in Oracle Order Management . Calculate Cost Rollup The Calculate Cost Rollup activity is an OM Order Line activity that calls the CTO PL/SQL procedure named CTO_WORKFLOW. The following image depicts the Calculate Cost Rollup activity: The Calculate Cost Rollup activity is contained in the Seeded Data File oexwford.wft. and is associated with the OM Order Line item type.wft. This lookup contains the following result codes: ■ ATO Item Build Dropship Stock ■ ■ ■ The following image depicts the Branch on Source Type activity: The Branch on Source Type activity is contained in the Seeded Data File oexwford.CALCULATE_COST_ROLLUP_WF_ML to calculate the cost of a configuration. and is associated with the OM Order Line item type.

SUBMIT_AND_ CONTINUE_WF. Calculate Lead Time contains the following attributes: ■ Arguments 13-100 Application Short Name Program Short Name Number of Arguments Item Attribute name LT Org BOM/ENG Specific/Range LT Item Routing Revision LT Date From Item To Item LT Category Set Name Category Structure Category From Category To ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ The following image depicts the Calculate Lead Time activity: Seeded Function Activity Definitions 6-13 . This procedure calculates the actual lead time of a configuration and updates the lead time attributes on the item master in the organization where the configuration will be manufactured.OM Order Line Calculate Lead Time The Calculate Lead Time activity is an OM Order Line activity that calls the Oracle Configure to Order PL/SQL procedure named CTO_WORKFLOW.

and is associated with the OM Order Line item type.Setup Parameters activity is contained in the Seeded Data File oexwford. The following image depicts the Calculate Purchase Price activity: 6-14 Using Oracle Workflow in Oracle Order Management . This lookup contains the following result codes: ■ Complete No Routing ■ The following image depicts the Calculate Lead Time . Calculate Lead Time . This is accomplished by setting up the line number as the parameter of the concurrent program.wft.SET_ PARAMETER_LEAD_TIME_WF_ML to prepare to launch the lead time calculation concurrent program. The Calculate Lead Time .Setup Parameters activity uses the lookup (has a result type of) Lead Time Result. Calculate Purchase Price The Calculate Purchase Price activity is an OM Order Line activity that calls the Oracle Configure to Order PL/SQL procedure named CTO_WORKFLOW. and is associated with the OM Order Line item type.Setup Parameters activity: The Calculate Lead Time .Setup Parameters is an OM Order Line activity that calls the Configure to Order PL/SQL procedure named CTO_WORKFLOW.OM Order Line The Calculate Lead Time activity is contained in the Seeded Data File oexwford.wft.Purchase_ price_calc_wf to determine the purchase price of the configuration.Setup Parameters The Calculate Lead Time .

The Check Supply Type activity uses the lookup (has a result type of) Check Supply Type Results. and the primary routing is flow routing) Incomplete ■ ■ ■ Seeded Function Activity Definitions 6-15 . and is associated with the OM Order Line item type. This lookup contains the following result codes: ■ Process AutoCreate PO Reserved ■ The following image depicts the Check Reservation activity: The Check Reservation activity is contained in the Seeded Data File oexwford.RSV_BEFORE_ BOOKING_WF to check if a reservation exists before creating supply for the order line. The Check Reservation activity uses the lookup (has a result type of) Reserved Status. the item has a planning type of Make or Make at Sourcing Rules. This lookup contains the following result codes: ■ Buy (in the shipping organization.wft. the item has a planning type of buy.wft. and is associated with the OM Order Line item type.OM Order Line The Calculate Purchase Price activity is contained in the Seeded Data File oexwford. Check Reservation The Check Reservation activity is an OM Order Line activity that calls the Oracle Configure to Order PL/SQL procedure named CTO_WORKFLOW. Check Supply Type The Check Supply Type activity is an OM Order Line activity that calls the Oracle Configure to Order PL/SQL procedure named CTO_WORKFLOW.CHECK_SUPPLY_ TYPE_WF to determine supply type for an order line. or buy type sourcing rules) Drop Ship (order line has source type of External) Flow Schedule (in the shipping organization.

The Close . upon completion the of Close activity. 6-16 Using Oracle Workflow in Oracle Order Management . and is associated with the OM Order Line item type. Handles Holds. and the primary routing is discrete routing) The following image depicts the Check Supply Type activity: The Check Supply Type activity is contained in the Seeded Data File oexwford. Close The Close activity is an OM Order Line activity that calls the PL/SQL procedure named OE_CLOSE_WF.Continue Header activity is an OM Order Line activity that uses standard Oracle Workflow functionality to continue the workflow in progress. The Close activity uses the lookup (has a result type of) OM Subprocess Results.CLOSE_LINE to close an order line. the halted header level process will continue.Continue Header activity is used to mark the position in the process where. Close .wft.OM Order Line ■ Work Order (in the shipping organization.wft. and is associated with the OM Order Line item type.Continue Header The Close . the item has a planning type of Make or Make at Sourcing Rules. This lookup contains the following result codes: ■ Complete Incomplete Not Eligible On Hold ■ ■ ■ The following image depicts the Close activity: The Close activity is contained in the Seeded Data File oexwford.

Continue Header activity calls the PL/SQL procedure named WF_ STANDARD.wft. The Close .OM Order Line The Close .Deferred activity calls the PL/SQL procedure named WF_ STANDARD. and is associated with the OM Order Line item type. Close . and is associated with the OM Order Line item type.Continue Header activity contains the following attributes: ■ Waiting Activity Waiting Flow ■ The following image depicts the Close .CONTINUEFLOW.Deferred activity is contained in the Seeded Data File oexwford. The Close .Deferred The Close .Deferred activity is an OM Order Line activity that uses the standard Oracle Workflow defer functionality to defer the closing functionality to the background engine.Continue Header activity: The Close .wft.Continue Header activity is contained in the Seeded Data File oexwford. Seeded Function Activity Definitions 6-17 .Deferred.DEFER.Deferred activity: The Close . To use Close . the Close activity must be placed immediately after it in the process flow. The following image depicts the Close .

Configuration .CREATE_BOM_AND_ROUTING_WF to create bill of material and routing for an order line.Create BOM and Routing The Configuration . Note: This function activity is not used in current processes and subprocesses and is listed for reference only.Create BOM and Routing activity: 6-18 Using Oracle Workflow in Oracle Order Management . Do not use this activity when creating or extending workflow processes and subprocesses.Check Status activity is contained in the Seeded Data File oexwford. The Configuration .Check Status activity is an OM Order Line activity that calls the Oracle Configure to Order PL/SQL procedure named CTO_WORKFLOW.CHECK_ RESERVATION_STATUS_WF to determine the status of configuration for an order line.Check Status activity: The Configuration .Check Status The Configuration .Check Status activity uses the lookup (has a result type of) Config Data Results. and is associated with the OM Order Line item type. The Configuration . This lookup contains the following result code: ■ Config Data Created The following image depicts the Configuration .Create BOM and Routing activity is an OM Order Line activity that calls the Oracle Configure to Order PL/SQL procedure named CTO_ WORKFLOW.wft.Create BOM and Routing activity uses the lookup (has a result type of) Config Incomplete.OM Order Line Configuration . This lookup contains the following result codes: ■ Complete Incomplete On Hold ■ ■ The following image depicts the Configuration .

OM Order Line The Configuration .wft. Seeded Function Activity Definitions 6-19 . Create Configuration . The Create Configuration activity uses the lookup (has a result type of) Config Incomplete. Create Configuration The Create Configuration activity is an OM Order Line activity that calls the Oracle Configure to Order PL/SQL procedure named CTO_WORKFLOW. and is associated with the OM Order Line item type.Eligible activity is an OM Order Line block activity that holds the order line until the user progresses the order manually or runs the autocreate configuration batch program.STANDARD_BLOCK.Eligible The Create Configuration . and creates the BOM and Routing.wft. and is associated with the OM Order Line item type.Create BOM and Routing activity is contained in the Seeded Data File oexwford. This activity creates the new line on the order for the configuration item.Eligible activity calls the PL/SQL procedure named OE_ STANDARD_WF. creates the new item.CREATE_CONFIG_ ITEM_WF to create configuration for an order line. The Create Configuration . This lookup contains the following result codes: ■ Complete Incomplete On Hold ■ ■ The following image depicts the Create Configuration activity: The Create Configuration activity is contained in the Seeded Data File oexwford.

Create Flow Schedule The Create Flow Schedule activity is an OM Order Line activity that calls the Oracle Configure to Order PL/SQL procedure named CTO_WORKFLOW.OM Order Line The following image depicts the Create Configuration .wft.Eligible activity is contained in the Seeded Data File oexwford. and is associated with the OM Order Line item type.CREATE_FLOW_ SCHEDULE_WF to create a flow schedule for an order line. and is associated with the OM Order Line item type.Eligible activity: The Create Configuration . 6-20 Using Oracle Workflow in Oracle Order Management .CREATE_CONFIG_WF. Create or Match Config Item The Create or Match Config Item activity is an OM Order Line activity that calls the PL/SQL procedure named OE_SOURCING. The Create Flow Schedule activity uses the lookup (has a result type of) Config Incomplete. This lookup contains the following result codes: ■ Complete Incomplete On Hold ■ ■ The following image depicts the Create Flow Schedule activity: The Create Flow Schedule activity is contained in the Seeded Data File oexwford.wft.

The Create Supply Order . Do not use this activity when creating or extending workflow processes and subprocesses.Eligible activity calls the PL/SQL procedure named OE_ STANDARD_WF. Create Supply Order .Eligible activity is an OM Order Line block activity that stops an order line workflow until the user progresses the order manually or runs the autocreate supply batch programs (Autocreate FAS.wft. or Autocreate Dropship).STANDARD_BLOCK. The following image depicts the Create or Match Config Item activity: The Create or Match Config Item activity is contained in the Seeded Data File oexwford. and is associated with the OM Order Line item type.wft.Eligible The Create Supply Order .Eligible activity is contained in the Seeded Data File oexwford. This lookup contains the following result codes: ■ Process AutoCreate PO Reserved ■ The following image depicts the Create Supply Order . The Create Supply Order .OM Order Line Note: This function activity is not used in current processes and subprocesses and is listed for reference only.Eligible activity: The Create Supply Order .Eligible activity uses the lookup (has a result type of) Reserved Status. Autocreate Purchase Req. and is associated with the OM Order Line item type. Seeded Function Activity Definitions 6-21 .

End (Complete) The End activity marks the end of a process and does not perform any action.SET_PARAMETER_WORK_ ORDER_WF to prepare to launch the autocreate supply batch programs by setting up the line number as the parameter to be used.Set Up Parameters activity is contained in the Seeded Data File oexwford.Set Up Parameters The Create Work Order . The Create Work Order .Set Up Parameters activity: The Create Work Order . and is associated with the OM Order Line item type.OM Order Line Create Work Order . This lookup contains the following result codes: ■ Complete Incomplete On Hold ■ ■ The following image depicts the Create Work Order . The End activity calls the PL/SQL procedure named WF_STANDARD. The following image depicts the End activity: The End activity is contained in the Seeded Data File oexwford.wft.wft. and is associated with the OM Order Line item type. 6-22 Using Oracle Workflow in Oracle Order Management .NOOP.Set Up Parameters activity uses the lookup (has a result type of) Config Incomplete. End The End activity marks the end of a process and does not perform any action.Set Up Parameters activity is an OM Order Line activity that calls the PL/SQL procedure named CTO_WORKFLOW.

and is associated with the OM Order Line item type.NOOP. and is associated with the OM Order Line item type. The End (Incomplete) activity calls the PL/SQL procedure named WF_ STANDARD.wft.OM Order Line The End (Complete) activity calls the PL/SQL procedure named WF_ STANDARD. The following image depicts the End (Non Shippable) activity: Seeded Function Activity Definitions 6-23 .wft. End (Non Shippable) The End (Non Shippable) activity marks the end of a process and does not perform any action. The following image depicts the End (Incomplete) activity: The End (Incomplete) activity is contained in the Seeded Data File oexwford. The End (Non Shippable) activity calls the PL/SQL procedure named WF_ STANDARD.NOOP.NOOP. End (Incomplete) The End (Incomplete) activity marks the end of a process and does not perform any action. The following image depicts the End (Complete) activity: The End (Complete) activity is contained in the Seeded Data File oexwford.

wft. The End (Over Shipped Beyond Tolerance) activity calls the PL/SQL procedure named WF_STANDARD.NOOP. The following image depicts the End (Not Eligible) activity: The End (Not Eligible) activity is contained in the Seeded Data File oexwford.OM Order Line The End (Non Shippable) activity is contained in the Seeded Data File oexwford. and is associated with the OM Order Line item type. The following image depicts the End (Over Shipped Beyond Tolerance) activity: 6-24 Using Oracle Workflow in Oracle Order Management . The End (Not Eligible) activity calls the PL/SQL procedure named WF_ STANDARD. End (Not Eligible) The End (Not Eligible) activity marks the end of a process and does not perform any action.wft. and is associated with the OM Order Line item type.NOOP. End (Over Shipped Beyond Tolerance) The End (Over Shipped Beyond Tolerance) activity marks the end of a process and does not perform any action.

and is associated with the OM Order Line item type.wft. and is associated with the OM Order Line item type.NOOP. Seeded Function Activity Definitions 6-25 .NOOP.wft. the Export Compliance Screening activity determines the line’s compliance. The following image depicts the End (Ship Confirm) activity: The End (Ship Confirm) activity is contained in the Seeded Data File oexwford. Export Compliance Screening When an order line is submitted that must comply with the United States Bureau of Export Administration’s Denied Party listing.wft. End (Ship Confirm) The End (Ship Confirm) activity marks the end of a process and does not perform any action. The End (Unreserve) activity calls the PL/SQL procedure named WF_ STANDARD. The End (Ship Confirm) activity calls the PL/SQL procedure named WF_ STANDARD. The following image depicts the End (Unreserve) activity: The End (Unreserve) activity is contained in the Seeded Data File oexwford. End (Unreserve) The End (Unreserve) activity marks the end of a process and does not perform any action. and is associated with the OM Order Line item type.OM Order Line The End (Over Shipped Beyond Tolerance) activity is contained in the Seeded Data File oexwford.

wft.Eligible activity: The Export Compliance Screening .Eligible The Export Compliance Screen .ECS_REQUEST.STANDARD_BLOCK. 6-26 Using Oracle Workflow in Oracle Order Management . The Export Compliance Screening .OM Order Line The Export Compliance Screening activity calls the PL/SQL procedure named OE_ EXPORT_COMPLIANCE_WF.Eligible activity is an OM Order Line activity that determines whether an order line must comply with United States Bureau of Export Administration’s Denied Party listing. and is associated with the OM Order Line item type. and is associated with the OM Order Line item type. The following image depicts the Export Compliance Screening . This lookup contains the following result codes: ■ Complete Hold Applied Incomplete Override ■ ■ ■ The following image depicts the Export Compliance Screening activity: The Export Compliance Screening activity is contained in the Seeded Data File oexwford. Export Compliance Screening .Eligible activity calls the PL/SQL procedure named OE_STANDARD_WF. The Export Compliance Screening activity uses the lookup (has a result type of) OM Export Compliance Results.wft.Eligible activity is contained in the Seeded Data File oexwford.

and is associated with the OM Order Line item type. The Fulfill .Continue Header Flow activity contains the following attributes: ■ Waiting Activity Waiting Flow ■ The following image depicts the Fulfill .Continue Header Flow The Fulfill . upon completion the Fulfill activity by all lines.wft.Continue Header Flow activity is used to mark the position in the process where.Continue Header Flow activity: Seeded Function Activity Definitions 6-27 .Continue Header Flow activity calls the PL/SQL procedure named WF_ STANDARD. The Fulfill . The Fulfill activity contains the following attributes: ■ Fulfillment Activity Name Completion Result Inbound Fulfillment Activity Name Inbound Completion Result ■ ■ ■ The following image depicts the Fulfill activity: The Fulfill activity is contained in the Seeded Data File oexwford.CONTINUEFLOW._FULFILLMENT to perform fulfillment for an order line. the halted header level process will continue. The Fulfill .OM Order Line Fulfill The Fulfill activity is an OM Order Line activity that calls the PL/SQL procedure named OE_FULFILL_WF.Continue Header Flow activity is an OM Order Line activity that uses standard Oracle Workflow functionality to continue the workflow in progress after an order line is fulfilled. Fulfill .

OM Order Line

The Fulfill - Continue Header Flow activity is contained in the Seeded Data File oexwford.wft, and is associated with the OM Order Line item type.

Fulfill - Deferred
The Fulfill - Deferred activity is an OM Order Line activity that uses standard Oracle Workflow functionality to defer fulfillment to the background engine. To use Fulfill - Deferred, the Fulfill activity must be placed immediately after it in the process flow. The Fulfill - Deferred activity calls the PL/SQL procedure named WF_ STANDARD.DEFER. The following image depicts the Fulfill - Deferred activity:

The Fulfill - Deferred activity is contained in the Seeded Data File oexwford.wft, and is associated with the OM Order Line item type.

Inventory Interface
The Inventory Interface activity is an OM Order Line activity that calls the PL/SQL procedure named OE_INV_IFACE_WF.INVENTORY_INTERFACE to interface with Oracle Inventory to relieve reservations and demand for non-shippable order lines. The Inventory Interface activity uses the lookup (has a result type of) OM Subprocess Results, Handles Holds. This lookup contains the following result codes:

Complete Incomplete Not Eligible

6-28

Using Oracle Workflow in Oracle Order Management

OM Order Line

On Hold

The following image depicts the Inventory Interface activity:

The Inventory Interface activity is contained in the Seeded Data File oexwford.wft, and is associated with the OM Order Line item type.

Inventory Interface - Deferred
The Inventory Interface - Deferred activity is an OM Order Line activity that uses standard Oracle Workflow functionality to defer inventory interface to the background engine. To use Inventory Interface - Deferred, the Inventory Interface activity must be placed immediately after it in the process flow. The Inventory Interface - Deferred activity calls the PL/SQL procedure named WF_ STANDARD.DEFER. The following image depicts the Inventory Interface - Deferred activity:

The Inventory Interface - Deferred activity is contained in the Seeded Data File oexwford.wft, and is associated with the OM Order Line item type.

Inventory Interface - Eligible
To enable a function for manual completion, you must place a special block activity before the actual function activity. For inventory interface, the Inventory Interface Eligible activity is the special block activity that facilitates this. The Inventory Interface - Eligible activity calls the PL/SQL procedure named OE_ STANDARD_WF.STANDARD_BLOCK. The following image depicts the Inventory Interface - Eligible activity:

Seeded Function Activity Definitions 6-29

OM Order Line

The Inventory Interface - Eligible activity is contained in the Seeded Data File oexwford.wft, and is associated with the OM Order Line item type.

Invoice Interface
The Invoice Interface activity is an OM Order Line activity that calls the PL/SQL procedure named OE_INVOICE_WF.INVOICE_INTERFACE to interface with Oracle Receivables for an invoice. The Invoice Interface activity uses the lookup (has a result type of) Invoice Results. This lookup contains the following result codes:

Complete Incomplete Not Eligible On Hold Partial

The following image depicts the Invoice Interface activity:

The Invoice Interface activity is contained in the Seeded Data File oexwford.wft, and is associated with the OM Order Line item type.

Invoice Interface - Deferred
The Invoice Interface - Deferred activity is an OM Order Line activity that uses standard Oracle Workflow functionality to defer the invoice interface with Oracle Receivables to the background engine. To use Invoice Interface - Deferred, the Invoice Interface activity must be placed immediately after it in the process flow.

6-30

Using Oracle Workflow in Oracle Order Management

OM Order Line

The Invoice Interface - Deferred activity calls the PL/SQL procedure named WF_ STANDARD.DEFER. The following image depicts the Invoice Interface - Deferred activity:

The Invoice Interface - Deferred activity is contained in the Seeded Data File oexwford.wft, and is associated with the OM Order Line item type.

Invoice Interface - Eligible
To enable a function for manual completion, you must place a special block activity before the actual function activity. For invoice interface, the Invoice Interface Eligible activity is the special block activity that facilitates this. The Invoice Interface - Eligible activity calls the PL/SQL procedure named OE_ STANDARD_WF.STANDARD_BLOCK. The following image depicts the Invoice Interface - Eligible activity:

The Invoice Interface - Eligible activity is contained in the Seeded Data File oexwford.wft, and is associated with the OM Order Line item type.

Is Line Scheduled
The Is Line Scheduled activity is an OM Order Line activity that calls the PL/SQL procedure named OE_OEOL_SCH.IS_LINE_SCHEDULED to determine whether an order line is scheduled. The Is Line Scheduled activity uses the lookup (has a result type of) OM Subprocess Results. This lookup contains the following result codes:

Complete Incomplete

Seeded Function Activity Definitions 6-31

OM Order Line

Not Eligible

The following image depicts the Is Line Scheduled activity:

The Is Line Scheduled activity is contained in the Seeded Data File oexwford.wft, and is associated with the OM Order Line item type.

Purchase Release
The Purchase Release activity is an OM Order Line activity that calls the PL/SQL procedure named OE_OEOL_SCH.RELEASE_TO_PURCHASING to release order line data to Oracle Purchasing. The Purchase Release activity uses the lookup (has a result type of) OM Subprocess Results, Handles Holds. This lookup contains the following result codes:

Complete Incomplete Not Eligible On Hold

The following image depicts the Purchase Release activity:

The Purchase Release activity is contained in the Seeded Data File oexwford.wft, and is associated with the OM Order Line item type.

Purchase Release - Deferred
The Purchase Release - Deferred activity is an OM Order Line activity that uses standard Oracle Workflow functionality to defer the release of order line data to Oracle Purchasing to the background engine.

6-32

Using Oracle Workflow in Oracle Order Management

Eligible To enable a function for manual completion.Deferred activity is contained in the Seeded Data File oexwford. and is associated with the OM Order Line item type.Eligible activity is contained in the Seeded Data File oexwford. The Purchase Release . The Reprice activity contains the following attributes: ■ Repricing Date Seeded Function Activity Definitions 6-33 .Deferred. For purchase release.STANDARD_BLOCK.wft.DEFER.Eligible activity calls the PL/SQL procedure named OE_ STANDARD_WF. Purchase Release .Eligible activity: The Purchase Release .Deferred activity: The Purchase Release . Reprice The Reprice activity is an OM Order Line activity that calls the PL/SQL procedure named OE_REPRICE_WF. and is associated with the OM Order Line item type. the Purchase Release Eligible activity is the special block activity that facilitates this. The following image depicts the Purchase Release . you must place a special block activity before the actual function activity. The following image depicts the Purchase Release .wft.START_REPRICING to reprice an order line.Deferred activity calls the PL/SQL procedure named WF_ STANDARD. the Purchase Release activity must be placed immediately after it in the process flow.OM Order Line To use Purchase Release . The Purchase Release .

STANDARD_BLOCK. and is associated with the OM Order Line item type.wft.Eligible activity is the special block activity that facilitates this.Eligible activity: The Reprice . Reprice .OM Order Line ■ Repricing Event Honor Calculate Price Flag? ■ The Reprice activity uses the lookup (has a result type of) OM Subprocess Results. 6-34 Using Oracle Workflow in Oracle Order Management . This lookup contains the following result codes: ■ Complete Incomplete Not Eligible ■ ■ The following image depicts the Reprice activity: The Reprice activity is contained in the Seeded Data File oexwford. For repricing.Eligible To enable a function for manual completion.Eligible activity is contained in the Seeded Data File oexwford.wft. you must place a special block activity before the actual function activity. The Reprice . the Reprice .Eligible activity calls the PL/SQL procedure named OE_STANDARD_ WF. and is associated with the OM Order Line item type. The following image depicts the Reprice .

wft. This lookup contains the following result codes: ■ Complete Incomplete Not Eligible On Hold ■ ■ ■ The following image depicts the Schedule activity: The Schedule activity is contained in the Seeded Data File oexwford.DEFER.SCHEDULE_LINE to schedule an order line.Deferred. the Schedule activity must be placed immediately after it in the process flow.Deferred The Schedule . To use Schedule .Deferred activity: Seeded Function Activity Definitions 6-35 . The Schedule activity uses the lookup (has a result type of) OM Subprocess Results.Deferred activity is an OM Order Line activity that uses standard Oracle Workflow functionality to defer the order line scheduling to the background engine.OM Order Line Schedule The Schedule activity is an OM Order Line activity that calls the PL/SQL procedure named OE_OEOL_SCH. and is associated with the OM Order Line item type. Schedule .Deferred activity calls the PL/SQL procedure named WF_ STANDARD. The Schedule . Handles Holds. The following image depicts the Schedule .

and is associated with the OM Order Line item type. Ship The Ship activity is an OM Order Line activity that calls the PL/SQL procedure named OE_SHIPPING_WF. The following image depicts the Schedule .Eligible activity is contained in the Seeded Data File oexwford.Eligible activity is the special block activity that facilitates this. the Schedule . For scheduling.wft. and is associated with the OM Order Line item type.START_SHIPPING to initiate shipping for an order line.Eligible activity calls the PL/SQL procedure named OE_STANDARD_ WF.Deferred activity is contained in the Seeded Data File oexwford. Schedule .Eligible activity: The Schedule . you must place a special block activity before the actual function activity.wft. The Ship activity uses the lookup (has a result type of) Shipping Results.STANDARD_BLOCK. The Schedule .Eligible To enable a function for manual completion. This lookup contains the following result codes: ■ Non Shippable Over Shipped Beyond Tolerance Ship Confirm Unreserve ■ ■ ■ The following image depicts the Ship activity: 6-36 Using Oracle Workflow in Oracle Order Management .OM Order Line The Schedule .

Deferred. Although it is not necessary.Deferred activity: The Ship activity is contained in the Seeded Data File oexwford.wft.DEFER.Deferred activity calls the PL/SQL procedure named WF_ STANDARD.wft.NOOP.wft. and is associated with the OM Order Line item type. The Ship .Deferred activity is an OM Order Line activity that uses standard Oracle Workflow functionality to defer shipping to the background engine. The following image depicts the Start activity: The Start activity is contained in the Seeded Data File oexwford. The following image depicts the Ship . and is associated with the OM Order Line item type.Deferred The Ship . To use Ship . and is associated with the OM Order Line item type. The Start activity calls the PL/SQL procedure named WF_STANDARD.OM Order Line The Ship activity is contained in the Seeded Data File oexwford. Start The Start activity marks the start of a process and does not perform any action. Ship . the Ship activity must be placed immediately after it in the process flow. you may include it in your process diagram to visually mark the start of a process as a separate node. Seeded Function Activity Definitions 6-37 .

Is Return Line Receivable? activity uses the lookup (has a result type of) Yes/No. This lookup contains the following result codes: ■ Order Return ■ The following image depicts the Utility to Get Line Category activity: The Utility to Get Line Category activity is contained in the Seeded Data File oexwford.wft.Is Return Line Receivable? activity is an OM Order Line activity that calls the PL/SQL procedure named OE_RMA_WF.Is Return Line Receivable? The Utility .wft. Utility to Get Line Category The Utility to Get Line Category activity is an OM Order Line activity that calls the PL/SQL procedure named OE_STANDARD_WF. 6-38 Using Oracle Workflow in Oracle Order Management . This lookup contains the following result codes: ■ Yes No ■ The following image depicts the Utility .GET_LINE_CATEGORY to determine the category of an order line. The Utility to Get Line Category activity uses the lookup (has a result type of) Line Category. and is associated with the OM Order Line item type.Is Return Line Receivable? activity is contained in the Seeded Data File oexwford.Is Return Line Receivable? activity: The Utility . The Utility . and is associated with the OM Order Line item type.OM Order Line Utility .IS_LINE_RECEIVABLE to determine whether an return order line must be received. An order line can either be an order or a return.

Wait for Approval marks the position in the process where. and is associated with the OM Order Line item type. This lookup contains the following result codes: ■ Internal External ■ The following image depicts the Utility to Get Supply Source Type activity: The Utility to Get Supply Source Type activity is contained in the Seeded Data File oexwford.GET_SUPPLY_SOURCE_TYPE to determine the supply source type for an order line. The Wait for Approval activity contains the following attributes: ■ Continuation Activity Continuation Flow ■ The following image depicts the Wait for Approval activity: Seeded Function Activity Definitions 6-39 . when all the order line is approved. the halted process will continue.WAITFORFLOW. The Wait for Approval activity calls the PL/SQL procedure named WF_ STANDARD. The Wait For Approval activity uses standard Oracle Workflow functionality to pause the process until the order line is approved. The Utility to Get Supply Source Type activity uses the lookup (has a result type of) Supply Source Type. A supply source can be either internal or external.OM Order Line Utility to Get Supply Source Type The Utility to Get Supply Source Type is an OM Order Line activity that calls the PL/SQL procedure named OE_STANDARD_WF. Wait for Approval The Wait for Approval activity is an OM Order Line activity that ensures an unapproved order does not proceed in its workflow process.wft.

The Wait For Booking activity uses standard Oracle Workflow functionality to pause the process until the order is booked. when the order is booked.wft. the subprocess would end. The Wait for Booking activity contains the following attributes: ■ Continuation Activity Continuation Flow ■ The following image depicts the Wait for Booking activity: The Wait for Booking activity is contained in the Seeded Data File oexwford. Wait for Create Configuration The Wait for Create Configuration activity is an OM Order Line activity which verifies that the configuration manufacturing data subprocess performs its calculations only when necessary.wft. If this is the case. Wait for Booking The Wait for Booking activity is an OM Order Line activity that ensures an order line does not proceed in its workflow process until the order is booked. Wait for Booking marks the position in the process where. It is not necessary to perform these calculations if the configuration data is already created by the autocreate config batch program.WAITFORFLOW.OM Order Line The Wait for Approval activity is contained in the Seeded Data File oexwford. and is associated with the OM Order Line item type. 6-40 Using Oracle Workflow in Oracle Order Management . The Wait for Booking activity calls the PL/SQL procedure named WF_ STANDARD. and is associated with the OM Order Line item type. the halted line level process will continue.

This lookup contains the following result codes: ■ Complete De-link ■ The following image depicts the Wait for CTO activity: Seeded Function Activity Definitions 6-41 . This lookup contains the following result codes: ■ Config Data Created The following image depicts the Wait for Create Configuration activity: The Wait for Create Configuration activity is contained in the Seeded Data File oexwford. The Wait for Create Configuration activity uses the lookup (has a result type of) Config Data Results. and is associated with the OM Order Line item type.BLOCK. when the results are received. Wait for CTO The Wait for CTO activity is an OM Order Line activity which verifies that an ATO Model order line does not proceed in its workflow process until the configuration line level process associated with the model line is complete. The Wait for CTO activity uses the lookup (has a result type of) Config Item Results.OM Order Line Wait for Create Configuration calls the PL/SQL procedure named WF_ STANDARD.wft. The configuration line level process completes when the configuration ships.BLOCK. the halted process will continue. Wait for CTO calls the PL/SQL procedure named WF_STANDARD. The Wait For CTO activity uses standard Oracle Workflow functionality to pause the process until these results are received. Wait for CTO marks the position in the process where.

This lookup contains the following result codes: ■ Complete Correct Receiving ■ The following image depicts the Wait for Inspection activity: The Wait for Inspection activity is contained in the Seeded Data File oexwford. Wait for Inspection The Wait for Inspection activity is an OM Order Line activity that ensures an order line does not proceed in its workflow process until the returned item is inspected.BLOCK. The Wait For Inspection activity uses standard Oracle Workflow functionality to pause the process. when the item is inspected. Wait for Inspection marks the position in the process where. Wait for Invoice Interface The Wait for Invoice Interface activity is an OM Order Line activity that ensures an order line does not proceed in its workflow process until the invoice interface with Oracle Receivables is performed. The Wait for Inspection activity calls the PL/SQL procedure named WF_ STANDARD. after invoice interface is complete. The Wait for Inspection activity uses the lookup (has a result type of) RMA Wait Result.wft. the halted process will continue. Wait for Invoice Interface marks the position in the process where. the halted process will continue. Wait for Invoice Interface contains the following attributes: ■ Continuation Activity 6-42 Using Oracle Workflow in Oracle Order Management . and is associated with the OM Order Line item type. The Wait For Invoice Interface activity uses standard Oracle Workflow functionality to pause the process.OM Order Line The Wait for CTO activity is contained in the Seeded Data File oexwford.wft. The Wait for Invoice Interface activity calls the PL/SQL procedure named WF_ STANDARD. and is associated with the OM Order Line item type.WAITFORFLOW.

The Wait for PO Receipt activity calls the PL/SQL procedure named OE_ STANDARD_WF. and is associated with the OM Order Line item type. Wait for PO Receipt The Wait for PO Receipt activity is an OM Order Line activity that ensures an order line does not proceed in its workflow process until Oracle Purchasing returns a receipt for the order line. Wait for PO Receipt marks the position in the process where. Seeded Function Activity Definitions 6-43 . The Wait For PO Receipt activity uses standard Oracle Workflow functionality to pause the process. Wait for Receiving The Wait for Receiving activity is an OM Order Line activity that ensures an order line does not proceed in its workflow process until the returned item is received.wft. when the receipt is received.STANDARD_BLOCK.wft. and is associated with the OM Order Line item type. The Wait for PO Receipt activity uses the lookup (has a result type of) Config Process Results. This lookup contains the following result codes: ■ Complete Incomplete ■ The following image depicts the Wait for PO Receipt activity: The Wait for PO Receipt activity is contained in the Seeded Data File oexwford.OM Order Line ■ Continuation Flow The following image depicts the Wait for Invoice Interface activity: The Wait for Invoice Interface activity is contained in the Seeded Data File oexwford. the halted process will continue.

Wait for Receiving marks the position in the process where. Wait for Revenue or Delivery marks the position in the process where the halted process will continue. when the item is received. This lookup contains the following result codes: ■ Complete Incomplete Not Eligible ■ ■ The following image depicts the Wait for Receiving activity: The Wait for Receiving activity is contained in the Seeded Data File oexwford. Wait for Required for Revenue or Delivery The Wait for Required for Revenue or Delivery activity is an OM Order Line activity that ensures an order line does not proceed in its workflow process until the order line is invoiced. The Wait for Receiving activity uses the lookup (has a result type of) OM Subprocess Success Results.BLOCK. The Wait for Required for Revenue or Delivery activity calls the PL/SQL procedure named WF_STANDARD. The Wait For Revenue or Delivery activity uses standard Oracle Workflow functionality to pause the process. The Wait for Receiving activity calls the PL/SQL procedure named OE_RMA_ WF. and is associated with the OM Order Line item type.wft.WAIT_FOR_RECEIVING. the halted process will continue.OM Order Line The Wait For Receiving activity uses standard Oracle Workflow functionality to pause the process. The following image depicts the Wait for Required for Revenue or Delivery activity: 6-44 Using Oracle Workflow in Oracle Order Management .

Utility .Set Notification Approver The Utility .OM Standard The Wait for Required for Revenue or Delivery activity is contained in the Seeded Data File oexwford. By using this activity.wft.BLOCK.SET_NOTIFICATION_APPROVER to determine the approver for the notification located immediately after this activity in a workflow process. OM Standard Approval Failed The Approval Failed activity can be used to transition failure results from approvals.Set Notification Approver activity calls the PL/SQL procedure named OE_ORDER_WF_UTIL. the flow remains active so that the order and order line can be manually cancelled.wft. and is associated with the OM Standard item type. and is associated with the OM Order Line item type. The Utility . It calls the WF Standard block function. The following image depicts the Approval Failed activity: The Approval Failed activity is contained in the Seeded Data File oexwford.Set Notification Approver activity contains the following attribute: ■ Source (used to select the notification approver) The following image depicts the Utility . The Approval Failed activity calls the PL/SQL procedure named WF_ STANDARD.Set Notification Approver activity: Seeded Function Activity Definitions 6-45 .

you may include it in your process diagram to visually mark the start of a process as a separate node. Start The Start activity marks the start of a process and does not perform any action. End The End activity marks the end of a process and does not perform any action. you may include it in your process diagram to visually mark the end of your process as a separate node. The following are the Standard activities used by Oracle Order Management.Set Notification Approver activity is contained in the Seeded Data File oexwford. refer to the Oracle Workflow Guide. and is associated with the OM Standard item type.Standard The Utility .NOOP. The Standard item type is automatically installed on your Oracle Workflow server. The following image depicts the End activity: The End activity calls the PL/SQL procedure named WF_STANDARD. Although it is not necessary. Standard Oracle Workflow provides some generic activities you can use to control your processes.wft. For more information about the Oracle Workflow Standard activities. Although it is not necessary. The following image depicts the Start activity: 6-46 Using Oracle Workflow in Oracle Order Management . You can use it to return a result for a completed process by specifying a Result Type for the activity. The activities are associated with the Standard item type but can be used within any process you define.

Seeded Function Activity Definitions 6-47 . as indicated in the Day of Month activity attribute. ■ ■ ■ 2. You can wait until: ■ A specific date A given day of the month A given day of the week A period of time after this activity is encountered ■ ■ ■ The Wait activity has six activity attributes: 1. If the day you choose has already passed in the current month. enter 0. then the activity waits until that day in the following month.NOOP. Absolute Date: if Wait Mode is set to Absolute Date. choose a day of the month from the list.Standard The Start activity calls the PL/SQL procedure named WF_STANDARD. You can choose one of the following wait modes: ■ Absolute Date: to pause the activity until the date specified in the Absolute Date activity attribute is reached. enter a relative time expressed in <days>.5 for a wait time of half a day (12 hours). Wait The Wait activity pauses the process for the time you specify. Day of Month: If Wait Mode is set to Day of Month. Day of Month: to pause the activity until a specified day of the month. 4. Relative Time: to pause the activity until the number of days specified in the Relative Time activity attribute passes. For example. Day of Week: to pause the activity until a specified day of the week. as indicated in the Day of Week activity attribute. 3.<fraction of days>. Relative Time: if Wait Mode is set to Relative Time. enter an absolute date. Wait Mode: use this attribute to specify how to calculate the wait.

Standard 5. 6-48 Using Oracle Workflow in Oracle Order Management .WAIT. Time of Day: The Wait activity always pauses until midnight of the time specified. unless you use this Time of Day activity attribute to specify a time other than midnight that the Wait activity should pause until. If the day you choose has already passed in the current week. Day of Week: If Wait Mode is set to Day of Week. then the activity waits until that day in the following week. choose a day of the week from the list. The following image depicts the Wait activity: The Wait activity calls the PL/SQL procedure named WF_STANDARD. 6.

A Windows and Navigator Paths This appendix discusses windows and navigator paths associated with using Oracle Workflow in Oracle Order Management. The following topics is addressed: ■ Windows and Navigator Paths Windows and Navigator Paths A-1 .

Requests Reports > Run Requests [OK] > AutoCreate Final Assembly Orders Orders. Returns > Sales Orders > Line Items Tab > Configurator Reports. Returns > Orders Organizer > Order Information > [Actions] > Cancel Orders. Returns > Sales Orders > [Book Order] Customers > Standard > (Addresses) > [Open] > (Business Purposes) Orders. Requests Reports > Run Requests [OK] > AutoCreate Configuration Items Reports. Returns > Orders Organizer > [Find] > Sales Orders > Lines tab > [Configurator] Orders. Requests > Export Compliance Screening Setup > Parameters Navigation Path Setup > Items > Item Types Setup > Items > Item Types A-2 Using Oracle Workflow in Oracle Order Management . Returns > Orders Organizer >Lines Tab > [Actions] > Cancel Orders.Windows and Navigator Paths Windows and Navigator Paths The following table lists the navigation path for windows accessible through Oracle Order Management: Window Name Application Utilities: ITEM_TYPE Lookups Application Utilities: ITEM_TYPE Lookups (INV) Application Utilities: Order Management ATO Configured Item AutoCreate Configuration Items AutoCreate Final Assembly Orders Book Order Business Purposes Cancel Orders Cancel Lines Configurator Setup > QuickCodes > Order Management Orders. Returns > Export Compliance > Export Compliance Workbench Reports. Returns > Sales Orders >Lines Tab> [Configurator] Export Compliance Workbench Export Compliance Screening Concurrent Program Enable Parameters Orders.

Windows and Navigator Paths Window Name Find Holds Navigation Path Orders. Returns > Order Organizer > [Find Orders] > Order Information Tab > [Find] or Orders. Returns > Order Organizer > [Find] > Sales Orders > Tools Menu > Workflow Status Pricing > Lookups Setup > QuickCodes > Receivables Order Information User: Order Status: Run a Simple or Advanced Search: Click a Sales Order Number Windows and Navigator Paths A-3 . Requests > Run Requests > [OK] > Inventory Interface .No Ship Item Assignment Item Attribute Controls Item Attributes Line Information Notification Notifications (Approval) Notifications List Oracle Pricing Lookups Oracle Receivables Lookup Order Details Shipping > Interfaces > Inventory Interface SRS Report. Returns > Order Organizer > [Actions] > Line Information Tab Orders.No Ship Setup > Items > Categories > Category Sets > [Assign] Setup > Items > Attribute Controls Items > Item Information > [Attributes] Orders. Returns > Order Organizer > [Actions] > Notification Workflow Notifications > Worklist Orders. Returns > Order Organizer > Tools Menu > Workflow Monitor Orders. Returns > Orders Organizer > Lines Tab > Tools Menu> Create Hold Sources> [Apply Holds] or Orders. Returns > Orders Organizer Setup > Orders > Holds Orders. Returns > Order Organizer > Hold Information Tab > [Find} Find Items Find Order and Line Approvals Find Orders Holds Holds (Line) Items > Item Search > [Find] > Item Search Orders. Returns > Sales Orders > Lines Tab > Tools Menu > Create Hold Sources > [Apply Holds] Inventory Interface Inventory Interface .

. Returns > Sales Orders > Lines Tab > Shipping Tab > Scheduled Ship Date or Orders. Returns > Sales Orders OR Orders. Returns > Purge Messages Reports. Returns > Sales Orders > Tools Menu > Schedule > Scheduling Actions > [Schedule.Windows and Navigator Paths Window Name Order Line Sort Criteria Order Management Lookup Purge Messages Release Expired Holds Release Holds Navigation Path Orders. Returns > Sales Orders > Lines Tab > Folders Menu > Sort Data Setup > QuickCodes > Order Management Orders. Returns > Run Requests > [OK] > Requisition Import Release Sources (Holds) Requisition Import Rollup Groups Sales Orders Setup > Financials > Flexfields > Key > Groups > [Find] Orders.. Returns > Order Organizer > [Find Orders] > Hold Information Tab > Release Sources > Release Tab Release Orders.] or Orders. Returns > Service Interface Setup > Shipping Tolerances Shipping > Transactions ITM Adapter > Administration > Skip Screening Setup > Transaction Types > Define A-4 Using Oracle Workflow in Oracle Order Management . Returns > Orders Organizer > [New Order] Schedule Orders Orders. Returns > Holds > Release > [Hold Sources] Orders. Returns > Requisition Import or Reports. Returns > Schedule Order Scheduling Actions Security Rules Service Interface Shipping Tolerances Shipping Transactions Skip Screening Transaction Types Orders. Requests > Run Requests > [OK] > Release Expired Holds Orders. Returns > Sales Orders > Tools Menu > Scheduling Setup > Rules > Security Orders.

Returns > Order Organizer > [Find Orders] > Order Information Tab Orders. Returns > Order Organizer or Sales Orders > Query orders > [Actions] > Viewing Cycle Status and Approval History Bills > Bills Setup > Financials > Validation > Value > [Find] > [View Hierarchies] Orders. Returns > Order Organizer > [Find Orders] > Order Information Tab WF Notifications Tools > Workflow Status Windows and Navigator Paths A-5 . Returns > Orders Organizer > [Find Orders] >Holds Tab> [Find] > [View Holds] Orders.Windows and Navigator Paths Window Name Transaction Types Usage Rules View Cycle Status and Approval History View Bills of Material View Hierarchies View Holds View Orders View Order Info Workflow Notification Workflow Status Navigation Path Setup > Financials > Transaction Types Setup > Credit > {Find} Assign Usage Rules Orders.

Windows and Navigator Paths A-6 Using Oracle Workflow in Oracle Order Management .

B Troubleshooting This chapter discusses troubleshooting when using Oracle Workflow in Oracle Order Management. The following topics are addressed: ■ Expected Errors on page B-2 Unexpected Errors on page B-3 ■ Troubleshooting B-1 .

When an activity is process by the Background Engine (the activity is deferred). the workflow activity.Expected Errors Expected Errors There are two error types that can occur in order and line flows: unexpected errors and expected errors. booking requires that a customer is specified on the order. If you attempt to book an order that does not specify a customer. After eight hours it transitions back to the invoicing activity. such as an invalid repricing event or pricing engine failure to locate a price list. The activity posts a message indicating the line is on hold and then completes to the Wait activity with an ON_HOLD result. Other examples of expected errors include the following: ■ A line is on hold and cannot be invoice interfaced. or end with an INCOMPLETE result. The flow must then transition to a block (which can be completed from the Sales Order window) or to a wait activity. The activity posts a message indicating that the order is on hold and then completes to the booking eligibility block with an ON_HOLD result. For example. the booking activity finds a hold on an order. Repricing Errors You can still reprice an order line if Reprice . activities are set to end with a ON_HOLD result if it cannot complete because of a hold.Line encounters an expected error. The Wait activity is set to wait for a response for eight hours. and/or order or line basis. Complete the following steps to reprice a line that failed the Reprice activity: 1. Navigate to the Sales Order Process Messages window to view the error condition. the order will not book. B-2 Using Oracle Workflow in Oracle Order Management . Booking cannot complete because no price list is specified on the order. error messages are stored in the Oracle Order Management processing message table. Expected errors are errors that business processes anticipate. the Processing Messages window appears to display messages that indicate errors. The Book activity will end with a result of Incomplete. View these messages via the Processing Message window using the concurrent program request number. As another example. ■ To anticipate these errors. the invoicing activity finds a hold on a line. When an activity is completed via the Sales Order window. For example.

6. Troubleshooting B-3 . select Actions. Save your work. Repeat Steps 1 through 6 until the error is resolved. Correct the error condition. refer to the Oracle Workflow Guide. Errors Viewing Workflow Status From Within Oracle Order Management If you encounter an error when trying to view workflow processes from within Oracle Order Management. Unexpected Errors Unexpected errors are those that an Oracle Order Management function activity does not anticipate. 5. and is set as SYSADMIN. Select Reprice Eligible from the menu to reprice the line again. All seeded Oracle Order Management function activities and process have a specified error process. The activity that encountered an unexpected error is marked with an Error status (in WF_ITEM_ACTIVITY_STATUSES) and a notification listing the error details is sent to the role specified in the OM Workflow Administrator item attribute. Retry Only. The Role item attribute WF_ADMINISTRATOR is defined for the header and line work item. Causes of unexpected errors can include the following: ■ Data integrity errors The table does not exist Rollback segments cannot be extended The package does not exist ■ ■ ■ To avoid unexpected errors. Select the Lines tab and locate the line with the repricing error. Navigate to the Sales Order window and query the order where the repricing error occurred. 4. your Oracle Workflow setup or your browser setup on your computer could be incorrect. 3. For more information about workflow viewing problems from within Oracle Applications. The default error process. and then select Progress Order. Select the line. 7. is a seeded Oracle Workflow error process. The error process sends notifications about the error to this role. 8. specify an error process when defining function activities and processes.Unexpected Errors 2.

B-4 Using Oracle Workflow in Oracle Order Management . This initiates a retry of the activity in error. The administrator can also opt to retry the activity from the Workflow Monitor. For more information on setting the OM Workflow Administrator item attribute.Unexpected Errors Once the problems have been corrected. refer to Assigning Workflows to Transaction Types. the administrator can select the Retry option on the notification and complete it.

Activities must be one of three types: function. or process. In the latter case. name. version) An Activity is the definition of a unit of work performed in the course of a business process. All activities are associated with an Item Type. Multiple versions of an activity definition are maintained in this table. which enable definitions to be updated without disturbing processes that are in progress. notification. meaning anyone can modify it or it can be assigned a protection level that is equal to the access level of the user defining the data. Function Activities are defined by a PL/SQL function executed directly by the workflow Glossary-i . You assign a value to an activity attribute by displaying the activity node’s Attribute Values properties page in the Process window. activity A unit of work performed during a business process. You define an activity attribute by displaying the activity’s Attributes properties page in the Activities window of Oracle Workflow Builder. Rows in this table represent the re-usable portion of the activity definition. activity (item type. it can either be set to customizable (1000). only users operating at an access level equal to or lower than the data’s protection level can modify the data. When workflow data is defined. activity attribute A parameter for an Oracle Workflow function activity that controls how the function activity operates.Glossary A access level A numeric value ranging from 0 to 100 that represents who the data is protected from for modification. and are identified by name. Additional properties are associated with activities per usage in a process.

. approval A positive response to a notification. Assemble-to-order is also an item attribute that you can apply to standard. Historical data that is independent from the live standing and transaction data. The network of activities and transitions that define the process are maintained by in the Process Activities and Activity Transitions tables. You can purchase or manufacture an assembly item. The defining PL/SQL functions accept standard arguments and return a completion result. assemble-to-order (ATO) An environment where you open a final assembly order to assemble items that customers order. and option class items. Function activities are used to perform fully automated steps in the process. All notification activities may have a time-out limit within which the activity must be performed.engine. archive Data Repository for non-live orders. ATO item See assemble-to-order item. Functions have a cost which indicates the amount of work the function represents. These activities have a “notification function” which is run to signal the external entity of its need to perform a task. model. which can then be referenced by other processes. Notification Activities are completed by some external entity (e.g. assemble-to-order (ATO) item An item you make in response to a customer order. ATO See assemble-to-order. See assemble-to-order. assembly An item that has a bill of materials. human). bill of materials. Process Definitions are also modeled as activities. Human notifications are associated with a Message defined in the Notification system. assemble-to-order (ATO) model A configuration you create for customer order that includes optional items.

Available To Promise (ATP) The quantity of on-hand stock. authorized quantity The authorized quantity is how many of an item that can be sent back to the warehouse from the customer. authorization The act of marking a notification as approved or not approved. ATP See available to promise. you define the types of supply and demand that should be included in your ATP calculation. This is the booked quantity. attribute See activity attribute. outstanding receipts and planned production which are not committed through a reservation or placing demand. or message attribute. bill of materials A list of component items associated with a parent item and information about how each item relates to the parent item. This would release or confirm a hold on an Order. option class. Oracle Manufacturing supports standard. credit memos. B background engine A supplemental Oracle Workflow engine that processes deferred or timed out activities. and planning bills. item type attribute. model. The most common type of bill is a standard bill of . AutoInvoice A program that imports invoices. In Oracle Inventory.ATO model See assemble-to-order model. The item information on a bill depends on the item type and bill type. and on account credits from other systems to Oracle Receivables.

Each time you submit a task. and other Oracle Manufacturing functions. config item An item which represents a unique configuration of model (ATO) and it’s classes and options. booking An action on an order signifying that the order has all the necessary information to be processed through its order flow. A concurrent process runs simultaneously with other concurrent processes to help you complete multiple tasks at once with no interruptions to your terminal. configuration item An item that corresponds to a base model and a specific list of options. Bills of Materials create configuration items for assemble-to-order models. This valid configuration of selected items is represented by a config item. concurrent process A task in the process of completing. . A standard bill of material lists the components associated with a product or subassembly. It specifies the required quantity for each component plus other information to control work in process. A config item goes through the manufacturing process cycle. material planning. C closed order An order and its order lines that have completed all activities in its process flow and for which the close activity is complete. A customer will enter his choice of classes and options for a given ATO model.material. It can be shipped as individual pieces as a set (kit) or as an assembly (configuration item). and is a shippable item. configuration A product a customer orders by choosing a base model and a list of options. configuration bill of materials The bill of materials for a configuration item. you create a new concurrent process.

configurator A window that enables you to choose options available for a particular model to define a particular configuration for the model. D delivery A set of order lines to be shipped to a customer’s ship-to location on a given date in a given vehicle. cost A relative value that you can assign to a function or notification activity to inform the Workflow Engine how much processing is required to complete the activity. A single delivery may include items from different sales orders and may include back orders as well as regular orders. The Workflow Engine can be set to operate with a threshold cost. credit order type This is any header level transaction type that allows for return lines. credit check A process that enables you to control the risk incurred when generating orders for your customers. delivery date The date on which the product is to arrive at the Ship-To Location. If an order exceeds either limit. complex activities. or calculated by applying in-transit lead time to a customer-specified Shipment Date. Multiple deliveries can be grouped into a single departure. Oracle Order Management places the order on hold for review. Credit Checking is a feature of Oracle Receivables that enables Order Management to automatically checks a customer order total against predefined order and total order limits. A background engine can be set up to poll for and process deferred activities. Assign a higher cost to longer running. configure-to-order An environment where you enter customer orders by choosing a base model and then selecting options from a list of choices. The type is used to specify defaulting values for this credit order and an associated workflow. Any activity with a cost above the Workflow Engine threshold cost gets set to Deferred and is not processed. This date is either specified by the customer on a delivery-based demand transaction. .

drop ship item An item to be sourced externally from the vendor directly to a customer. E export licenses A government license to supply certain products to certain countries that would otherwise be restricted. an RMA line. delivery line A shippable and booked line from the planning pool which has been allocated to a delivery.delivery detail Contains items to be shipped out of a warehouse. directory services A mapping of Oracle Workflow users and roles to a site’s directory repository. external functions Programs that are executed outside of Oracle8. They can be referred to as deliverables. After the delivery is closed. or delivering them. It accounts for any non-working days in between. drop shipment A method of fulfilling sales orders by selling products without handling. a WIP line or a PO line. export paper A document required by governmental agencies that provides information on goods shipped out of or into a country. This may be a sales order line. The selling company buys a product from a supplier and has the supplier ship the product directly to customers. the line is no longer available in the planning pool. the delivery line will also be considered closed. . delivery lead time Time (in days) is takes for items to reach the customer once it is shipped. stocking. After allocation.

F fulfillment Fulfilled sales order lines have successfully completed all Oracle Workflow processing activities up to eligibility for invoicing. The stored procedure accepts standard arguments and returns a completion result. ATO model. You can place a hold on any order or order line. H hold A feature that prevents an order or order line from progressing through the order cycle. customer sites. hold criteria Criteria used to place a hold on an order or order line. orders. see function. fulfillment set Items in a fulfillment set will be available for scheduling and shipping only when all the items are available and ready to be scheduled/shipped. function activity An automated Oracle Workflow unit of work that is defined by a PL/SQL stored procedure. Create a hold source when you want to put all current . or retrieve application information. and a PTO Ship model Complete will be in a fulfillment set. perform automated tasks within an application. hold source An instruction for Oracle Order Management to place a hold on all orders or lines that meet criteria you specify. A hold criteria can include customers. and items. or partially allowed but in proportions. fulfillment activity The synchronization point or gate in the workflow process at which lines wait for other lines to be fulfilled. function A PL/SQL stored procedure referenced by an Oracle Workflow function activity that can enforce business rules. Fulfillment sets can be complete only.

finished products. subassemblies. Oracle Order Management gives you the power to release holds for specific orders or order lines. standard lines that you can include on invoices. or Mixed (both inbound and outbound lines). Order (all outbound). including payment terms. and other information that is sent to a customer for payment. Oracle Order Management holds all new and existing orders for the customer or item in your hold source until you remove the hold source. and option classes you can use to group options in model and option class bills. This document may list any tax and freight charges. I inbound/outbound Lines In the Oracle Order Management. invoice item information. or sell. Anything you make. . lines on a header are either outbound (sales order lines in which material on the header is leaving the warehouse to go to a customer) or inbound (return lines in which material on the header is arriving at the warehouse to be credited back to the customer). hold type Indicates the kind of hold you place on an order or order line.and future orders for a particular customer or for a particular item on automatic hold. Oracle Manufacturing also uses items to represent planning items that you can forecast. or supplies. including components. invoice A document you create in Oracle Receivables that lists amounts owed for the purchases of goods or services. In Order Management. headers can be Return (all inbound). item attribute See Item Type Attribute. purchase. item A specific process. while still maintaining the hold source. or transaction that is managed by a workflow process. A summarized list of charges. document.

Item type is also used as a high level grouping for processes. L lead time line The production line Oracle Bills of Material uses to calculate the processing lead time for a particular repetitive assembly. An item type attribute is defined as a variable whose value can be looked up and set by the application that maintains the item.item type A grouping of all items of a particular category that share the same set of item attributes. An item type attribute and its value is available to all activities in a process. . Each value in a lookup type has an internal and a display name. lead time rollup An Oracle Bills of Material program that computes cumulative lead times for items. For example. The lookup code is stored in the attribute. PO Requisition is an item type used to group all requisitions created by Oracle Internet Commerce’s Web Requisitions page. Lookup Attributes are validated by a lookup type. line lead time The time required to complete the first assembly on a production line. lookup code The internal name of a value defined in an Oracle Workflow lookup type. since lead times may vary on different production lines. lookup type An Oracle Workflow predefined list of values. item type attribute A feature associated with a particular item type. see lookup type. but the code’s translated meaning is displayed whenever the attribute value is viewed by an end user. also known as an item attribute.

N node An instance of an activity in a process diagram as shown in the Process window. model An item whose bill of material lists options and option classes available when you place an order for the model item. and processes e-mail responses. notification web page A web page that you can view from any web browser to query and respond to workflow notifications. a priority. notification An instance of a message delivered to a user. a message attribute gets replaced with a runtime value when the message is sent. . A message must be defined before it can be associated with a notification activity. Defined as a Send source. message attribute A variable that you define for a particular message to either provide information or prompt for a response when the message is sent in a notification.M message The information that is sent by a notification activity. a body. A notification activity sends a message to a user containing the information necessary to complete the work. Defined as a Respond source. a message attribute prompts a user for a response when the message is sent. and possibly one or more message attributes. You can use a predefine item type attribute as a message attribute. notification mailer A concurrent program that sends e-mail notifications to users via a mail application. A message contains a subject. notification activity A unit of work that requires human intervention.

order number sequence. If the category code is Order. order scheduling See scheduling. credit check point. and transaction type. then the order can have both kinds of lines. . Return or Mixed. When an order is created with a particular Transaction Type. Line Transaction Types can be for any of the categories: Order or Return. you may want to limit your report to the current month. If the category code is Return. then the order can have only regular lines. Pick-to-order is also an item attribute that you can apply to standard. then the order can have only return lines.O order category An Order Transaction Type can exist for any of the following order categories: Order. Alternative to manufacturing the parent item on a work order and then shipping it. or display information by supplier number instead of supplier name. In Oracle Order Management. If the category code is Mixed. order type Classification of an order. this controls an order’s workflow activity. model. For example. pick-to-order A configure-to-order environment where the options and included items in a model appear on pick slips and order pickers gather the options when they ship the order. the Order Category code determines which lines are permitted for that order. and option class items. Notification activities that are included in a process must be assigned to a performer. pick-to-order (PTO) item A predefined configuration order pickers gather as separately finished included items just before they ship the order. or determine the form of a report. P parameter A variable used to restrict information in a report. performer A user or role assigned to perform a human activity (notification).

A process activity represents an activity that is referenced by a process. Process item types enable high level grouping of Oracle Workflow Processes. process item type Oracle Workflow processes can exist for different process item types. At order entry. These instances are marked with machine-generated ID’s to uniquely identify multiple instances of the same activity in the same process. process activity A process modeled as an activity so that it can be referenced by other processes. See process. and user. process definition An Oracle Workflow process as defined in the Oracle Workflow Builder. In general. The order picker gets a detailed list of the chosen options and included items to gather as separately finished items just before the order is shipped. responsibility. profile option A set of changeable options that affect the way your applications run. profile options can be set at one or more of the following levels: site. A header flow will have a workflow process item type OEOH and a line flow will have a workflow process item type OEOL. process A set of Oracle Workflow activities that need to be performed to accomplish a business goal. Each row specifies the usage of an activity as the child of a process. picking The process of withdrawing items from inventory to be shipped to a customer. PO See purchase order.pick-to-order (PTO) model An item with an associated bill of material with optional and included items. the configurator is used to choose the optional items to include for the order. application. .

Sometimes this is temporary. while you evaluate the condition of the item.protection level see access level. receiving Ad dock at the receiving facility to receive goods from suppliers or customers. PTO item See pick-to-order item. the items are transferred to stock and a credit can be issued. If unacceptable. purchase order A type of purchase order you issue when you request delivery of goods or services for specific dates and locations. The blanket purchase agreement determines the characteristics and the . at other times you return the items to the customer. receiving and inspection A condition of a returned inventory item signifying it has been received but is being inspected for damage. release An actual order of goods and services you issue against a blanket purchase agreement. Purchase Order (PO) / Sales Order (SO) The term Purchase Order represents the order as defined in Oracle Purchasing. or keep them but do not allow a credit. the items can be returned to the customer or scrapped. Each purchase order line can have multiple shipments and you can distribute each shipment across multiple accounts. If in acceptable condition. R received quantity The quantity of an inventory item returned by a customer for which you are not issuing a credit. You can order multiple items for each planned or standard purchase order. PTO model See pick-to-order model. The term Sales Order represents the order data as defined in Oracle Order Management.

Once reserved. Also known as hard reservation. result type The name of the lookup type that contains an activity’s possible result values. You can also insert the workflow Reprice activity within your order line workflow to force a order or line reprice at a particular point in time. reservation A guaranteed allotment of product to a specific sales order. result code The internal name of a result value. according to your business practices. repricing Repricing is the ability to automatically. the product cannot be allocated to another sales order or transferred in inventory. In Order Management. It involves receipt of goods previously sold to a customer. You identify a release by the combination of blanket purchase agreement number and release number.prices of the items. release of hold The action of removing the hold on an order. credit to a customer. return In Oracle Purchasing. as defined by the result type. it is the opposite of a sales order. release reason Justification for removing a hold on an order or order line. cause the recalculation of the base price of an order line or for the entire order. Certain attribute changes to an order line can trigger automatic reprice. an AutoCreate option that lets a buyer return a requisition line and all other unpurchased requisition lines on the same requisition to the requisition preparer. . A hold is placed on specific terms that assures that a certain quantity of an item is available on a certain date when transacted against a particular charge entity. The release specifies the actual quantities and dates ordered for the items. result value The value returned by a completed activity. or through a workflow activity. and possibly replacement with an identical or similar product. Oracle Order Management checks ATR (Available to Reserve) to verify an attempted reservation.

A synonym for serviceable item is a serviceable product. S scheduling Order scheduling includes assigning demand or reservations. Service may be for new products or for existing. previously ordered products. ship confirm A process in Shipping Execution which allows you to identify shipped quantities. service item An inventory item used to define a service program or warranty. and specify whether or not to back order unfulfilled quantities of released line items. Supply is replenished in response to demand or anticipated demand. shippable item An item with the shippable inventory item attribute set to Yes. assign freight charges. indicating that this item will appear on pick slips and pack slips. Service items can be recorded against serviceable products. service order An order containing service order lines. supply A quantity of materials available for use. and lots or sub inventories to an order line. . assign inventory control information for released lines. warehouses. supply type A bill of material component field that controls issue transactions from inventory to work in process. shipment dates.role One or more users grouped by a common responsibility or position.

workflow engine The Oracle Workflow component that implements a workflow process definition. There can be only one header flow associated with an order transaction type but a line transaction type can be coupled with different order types and item types and there can be different flow couplings for the permitted transaction type. transition The relationship that defines the completion of one activity and the activation of another activity within a process. maintains a history of completed activities. timeout The amount of time during which a notification activity must be performed before the Workflow Engine transitions to an error process or an alternate activity if one is defined. the arrow drawn between two activities represents a transition. The Workflow Engine manages the state of all activities for an item. The Workflow Engine is implemented in server PL/SQL and activated when a call to an engine API is made. the ship-to location. Workflow Process This determines the header flow for an order transaction type or line flows possible for a line transaction type. In a process diagram. . and internal or external orders. and detects error conditions and starts error processes. W WIP See work in process. automatically executes functions and sends notifications.T transaction type A feature that allows you to specify default values for orders and order lines including the customer. item type combinations. workflow definitions loader A concurrent program that lets you upload and download workflow definitions between a flat file and a database.

work in process An item in various phases of production in a manufacturing plant. This includes raw material awaiting processing up to final assemblies ready to be received into inventory.

Index
A
access level setup, 1-2 activities Approval Failed, 6-45 Approve - Continue Line, 6-2 Authorize to Ship - Check Status, 6-9 Authorize to Ship - Wait for Authorization, 6-9 AutoCreate FAS, 6-10 AutoCreate PO Req, 6-11 Book, 6-2 Book - Continue Line (Complete), 6-3 Book - Deferred, 6-3 Book - Eligible, 6-4 Branch on Source Type, 6-12 Calculate Cost Rollup, 6-12 Calculate Lead Time, 6-13 Calculate Lead Time - Setup Parameters, 6-14 Calculate Purchase Price, 6-14 Check Reservation, 6-15 Check Supply Type, 6-15 Close, 6-5 Close - Continue Header, 6-16 Close - Deferred, 6-17 Close - Wait for Line, 6-5 Close (line), 6-16 Configuration - Check Status, 6-18 Configuration - Create BOM and Routing, 6-18 Create Configuration, 6-19 Create Configuration - Eligible, 6-19 Create Flow Schedule, 6-20 Create or Match Config Item, 6-20 Create Supply Order - Eligible, 6-21 Create Work Order - Set Up Parameters, 6-22 End, 6-22, 6-46 End (Complete), 6-22 End (Incomplete), 6-23 End (Non Shippable), 6-23 End (Not Eligible), 6-24 End (Over Shipped Beyond Tolerance), 6-24 End (Ship Confirm), 6-25 End (Unreserve), 6-25 Enter, 6-6 Export Compliance Screening, 6-25 Export Compliance Screening - Eligible, 6-26 Fulfill, 6-27 Fulfill - Continue Header Flow, 6-27 Fulfill - Deferred, 6-28 Fulfill - Wait for Line, 6-6 Header Invoice Interface - Eligible, 6-7 Inventory Interface, 6-28 Inventory Interface - Deferred, 6-29 Inventory Interface - Eligible, 6-29 Invoice Interface, 6-30 Invoice Interface - Continue Line, 6-7 Invoice Interface - Deferred, 6-30 Invoice Interface - Eligible, 6-31 Invoice Interface - Header Level, 6-8 Is Line Scheduled, 6-31 Purchase Release, 6-32 Purchase Release - Deferred, 6-32 Purchase Release - Eligible, 6-33 Reprice, 6-33 Reprice - Eligible, 6-34 Schedule, 6-35 Schedule - Deferred, 6-35 Schedule - Eligible, 6-36 seeded, 6-1

Index-1

Ship, 6-36 Ship - Deferred, 6-37 Standard, 6-46 Start, 6-37, 6-46 Utility - Is Return Line Receivable?, 6-38 Utility - Set Notification Approver, 6-45 Utility to Get Line Category, 6-38 Utility to Get Supply Source Type, 6-39 Wait, 6-47 Wait for Approval, 6-39 Wait for Booking, 6-40 Wait for Create Configuration, 6-40 Wait for CTO, 6-41 Wait for Inspection, 6-42 Wait for Invoice Interface, 6-42 Wait for PO Receipt, 6-43 Wait for Receiving, 6-43, 6-44 Wait for Required for Revenue or Delivery, 6-44 Activities List window image, 1-5 Approval Failed image, 6-45 item type, 6-45 overview, 6-45 PL/SQL procedure, 6-45 seeded data file, 6-45 Approve - Continue Line overview, 6-2 assemble to order overview, 2-5 processes, 2-5 ATO processes, 2-5 attributes OM Change Order, 1-10 OM Order Header, 1-11 Authorize to Ship - Check Status image, 6-9 item type, 6-9 overview, 6-9 PL/SQL procedure, 6-9 seeded data file, 6-9 Authorize to Ship - Wait for Authorization image, 6-10 item type, 6-10 overview, 6-9 PL/SQL procedure, 6-9

seeded data file, 6-10 Authorized to Ship - Line item type, 5-12 overview, 5-12 parent processes, 5-12 process activities, 5-14 process diagram, 5-13 process summary, 5-13 seeded data file, 5-12 AutoCreate FAS attributes, 6-10 image, 6-11 item type, 6-11 lookup, 6-11 overview, 6-10 PL/SQL procedure, 6-10 seeded data file, 6-11 AutoCreate PO Req image, 6-11 item type, 6-11 overview, 6-11 PL/SQL procedure, 6-11 seeded data file, 6-11

B
background engine, 2-9 background engine processing, 2-9 background engine schedules, 2-10 Book overview, 6-2 PL/SQL procedure, 6-2 Book - Continue Line (Complete) image, 6-3 overview, 6-3 PL/SQL procedure, 6-3 Book - Deferred image, 6-4 overview, 6-3 PL/SQL procedure, 6-4 Book - Eligible image, 6-4 overview, 6-4 PL/SQL procedure, 6-4 Book - Order, Deferred

Index-2

overview, 5-4 Book - Order, Manual overview, 5-6 process diagram, 5-7 booking activities, 6-2 Branch on Source Type image, 6-12 item type, 6-12 overview, 6-12 PL/SQL procedure, 6-12 seeded data file, 6-12 Buy ATO Item Flow overview, 5-14 parent processes, 5-14 process diagram, 5-15

C
Calculate Cost Rollup image, 6-12 item type, 6-12 overview, 6-12 PL/SQL procedure, 6-12 seeded data file, 6-12 Calculate Lead Time attributes, 6-13 image, 6-13 item type, 6-14 overview, 6-13, 6-14 PL/SQL procedure, 6-13 seeded data file, 6-14 Calculate Lead Time - Line item type, 5-16 overview, 5-16 parent processes, 5-16 process activities, 5-17 process summary, 5-16 seeded data file, 5-16 Calculate Lead Time - Setup Parameters image, 6-14 item type, 6-14 lookup, 6-14 PL/SQL procedure, 6-14 seeded data file, 6-14 Calculate Price flag, 2-12

Calculate Purchase Price image, 6-14 item type, 6-15 overview, 6-14 PL/SQL procedure, 6-14 seeded data file, 6-15 Change Order Process activities, 4-5 diagram, 4-5 item type, 4-4 overview, 4-4 process diagram, 4-5 seeded data file, 4-4 summary, 4-4 Check Reservation image, 6-15 item type, 6-15 lookup, 6-15 overview, 6-15 PL/SQL procedure, 6-15 seeded data file, 6-15 Check Supply Type image, 6-16 item type, 6-16 lookup, 6-15 overview, 6-15 PL/SQL procedure, 6-15 result codes, 6-15 seeded data file, 6-16 Close image, 6-5, 6-16 item type, 6-16 lookup, 6-16 overview, 6-5 PL/SQL procedure, 6-5, 6-16 result codes, 6-16 seeded data file, 6-16 Close - Continue Header attributes, 6-17 image, 6-17 item type, 6-17 overview, 6-16 PL/SQL procedure, 6-17 seeded data file, 6-17 Close - Deferred

Index-3

6-21 lookup. 6-19 PL/SQL procedure.Create BOM and Routing image. 6-18 PL/SQL procedure. 6-20 Create Configuration . 6-18 item type. 5-31 process diagram. 5-24 process summary. 5-28 process activities. 5-20 process diagram. 6-17 overview. 6-5 Close (line) overview. 6-21 item type.Line. 5-18 parent processes. 6-20 PL/SQL procedure.Line. 5-26 process activities. 6-20 Create Manufacturing Configuration Data . 6-21 item type. 6-21 PL/SQL procedure. 6-20 seeded data file. 6-19 lookup. 5-26 Create or Match Config Item image. 6-20 result codes. 6-17 PL/SQL procedure. 6-19 seeded data file. 6-18 overview.Wait for Line image. 6-6 overview. 5-23 parent processes. 6-19 seeded data file. 5-26 parent processes. 6-19 Create Configuration . 6-21 overview. 6-18 seeded data file. 6-21 Create Supply . 6-17 item type. 6-20 overview. 6-20 item type. Manual overview. 6-18 result codes. 6-20 seeded data file.Order process diagram. 6-18 Configuration . 6-19 lookup.Line activities. 6-18 result codes.Eligible image. 6-16 concurrent programs. 6-19 result codes.Line overview. 6-21 overview. 6-5 PL/SQL procedure. 6-19 item type. 5-19 process summary. 5-28 process diagram. 5-9 Close . Manual overview. 5-26 process summary.Eligible image. 6-20 item type. 6-20 PL/SQL procedure. 6-20 overview. 5-29 process summary. 6-19 overview. 6-18 seeded data file. 5-25 process diagram. 5-18 process activities. 5-28 parent processes. 6-20 lookup. 6-21 Index-4 . 6-18 overview. 6-19 PL/SQL procedure. 6-19 Create Configuration image. 2-9 Configuration . 6-18 PL/SQL procedure. 5-29 Create Supply Order . 5-23 process activities. 5-19 Close .Check Status image. 6-17 seeded data file. 6-18 lookup.image. 5-24 Create Flow Schedule image. 6-17 Close . 5-31 overview. 6-19 item type.

6-46 item type. 4-3 process summary. 6-23 End (Incomplete) image. 4-2 ctochord. 6-24 overview. 6-23 PL/SQL procedure. 6-22 overview. 5-34 process diagram. 4-3 item type. 2-8 CTO Change Order processes CTO Change Order Process. 4-2 process diagram. 6-46 seeded data file. 6-22 creating workflow processes. 3-3 workflow. 6-24 seeded data file. 4-3 seeded data file. 6-24 overview. 6-22 PL/SQL procedure.Line Process Activities. 6-22 item type. 6-22. Manual overview. 3-3 transaction types. 5-34 process diagram. 6-23 End (Non Shippable) image. 6-22 result codes. 2-9 deferred activity processing.Line overview. 5-32 Create Work Order . 6-23 seeded data file. 6-24 item type. 6-24 PL/SQL procedure. 6-25 End (Ship Confirm) image. 6-25 overview. 6-25 PL/SQL procedure. 6-21 seeded data file. 6-24 PL/SQL procedure. 4-2 overview. 6-22 PL/SQL procedure. 1-9 processes.result codes. 6-22 seeded data file. 6-24 seeded data file. 6-23 overview. 6-23 seeded data file. 5-33 process summary. 6-21 Create Supply Order . 6-25 item type.Line. 6-24 item type. 5-34 Create Work Order . 6-22 End (Complete) image. B-3 deferred activities. 6-22 overview. 6-23 item type. 6-23 seeded data file. 6-25 overview. 1-9 customization exceptions. 6-24 End (Over Shipped Beyond Tolerance) image. 3-3 support. 6-23 PL/SQL procedure. 6-24 item type. 2-8 E End image.wft item types. 6-25 5-36 D default error process. 6-22 lookup. 4-2 CTO Change Order Process activities. 6-23 item type. 6-24 End (Not Eligible) image. 5-32 process activities. 6-22. 5-35 process summary. 2-9 determining header level processes Index-5 . 6-23 overview.Set Up Parameters image. 6-46 PL/SQL procedure. Create Work Order .

5-37 error handling. 6-27 Fulfill . 3-2 overview. 6-6 fulfillment date repricing. 6-25 item type. 6-6 Enter .Line overview.Wait for Line image. 6-25 seeded data file. 5-36 parent processes. 3-4 overview. 6-27 overview. 3-8 guidelines. 6-28 PL/SQL procedure. 3-2 methods of. 6-26 Export Compliance Screening . 6-26 overview. 6-26 lookup. 6-26 PL/SQL procedure. 6-28 Fulfill . 6-28 item type. 6-26 overview. 5-37. 6-6 overview. 6-26 seeded data file.Eligible image. 6-27 item type. 6-25 Enter image. 6-27 image. 6-27 PL/SQL procedure. 6-27 PL/SQL procedure. 5-38 process summary. B-1 expected. 5-39 overview. 5-36 process activities. 6-26 Export Compliance Screening . 3-3 extending workflows customization. 3-2 customization exceptions. 6-28 overview.Continue Header Flow attributes. 6-26 seeded data file. 3-2 F Fulfill attributes. 5-38 process diagram. 3-8 process parameters. 3-1 extending workflow dependencies.Deferred image. 2-13 Index-6 . 3-6 approvals. B-2 repricing. 3-3 examples. 6-6 PL/SQL procedure. 3-3 extending seeded processes. 6-26 item type.seeded data file. 5-39 parent processes. 6-28 seeded data file. 6-28 overview. B-2 error processes. 5-39 process activities. 6-27 seeded data file. 3-3. 6-26 item type. 6-6 PL/SQL procedure. 6-27 seeded data file.Line item type. 6-28 item type. 6-27 image. 6-25 overview. 3-6 time out transitions. 6-25 End (Unreserve) image. 6-25 PL/SQL procedure. 5-40 process summary. 3-5 modifying seeded data. B-1 expected errors. 5-41 process diagram. B-2 Export Compliance Screening image. 3-4 examples. 6-26 result codes. 6-25 PL/SQL procedure. 3-7 deferred booking. 5-39 extending processes. B-3 errors. 6-7 overview. 6-28 Fulfill .

Deferred. 6-38 Utility to Get Supply Source Type.Eligible.Check Status. 6-12 Calculate Cost Rollup. 6-3 Book . 6-23 End (Non Shippable).Eligible. 6-37 Start. 6-28 Fulfill . 6-43 Wait for Receiving. 6-33 Reprice.Deferred.Eligible. 6-46 End (Complete). 6-19 Create Configuration . 6-16 Close . 6-15 Check Supply Type. 6-22 End. 6-16 Configuration . 6-42 Wait for Invoice Interface. 6-44 Wait for Required for Revenue or Delivery. 6-27 Fulfill . 6-17 Close . 6-9 AutoCreate FAS. 6-3 Book . 6-22 End (Incomplete).Eligible. 6-2 Book . 6-31 Invoice Interface . 6-30 Invoice Interface . 6-21 Create Work Order . 6-2 Authorize to Ship . 6-35 Schedule . 6-20 Create of Match Config Item. 6-1 G generic line level processes. 6-36 Ship. 6-45 Utility to Get Line Category. 6-24 End (Over Shipped Beyond Tolerance).Set Up Parameters. 6-32 Purchase Release .Deferred. 6-10 AutoCreate PO Req. 6-43. 6-40 Wait for Create Configuration. 6-27 Fulfill .Deferred. 2-3 generic processes Line Flow . 6-13 Calculate Lead Time .Deferred. 6-36 Ship . 6-38 Utility .Check Status. 6-18 Configuration . 6-15 Close.Continue Header Flow. 6-33 Reprice . 6-35 Schedule . 6-41 Wait for Inspection. 6-6 Export Compliance Screening. 6-4 Branch on Source Type. 6-30 Invoice Interface . 6-6 Header Invoice Interface . 6-11 Book. 6-1 seeded. 6-25 Enter. 6-25 End (Unreserve). 4-21 Index-7 .Set Notification Approver. 6-19 Create Flow Schedule.Wait for Authorization. 6-8 Is Line Scheduled.Eligible. 6-40 Wait for CTO.Is Return Line Receivable?. 6-28 Inventory Interface .Create BOM and Routing. 6-23 End (Not Eligible). 6-42 Wait for PO Receipt.Wait for Line. 6-7 Inventory Interface. 6-5 Close (line).Continue Line. 6-5 Close . 6-37.Continue Header. 6-39 Wait. 6-34 Schedule. 6-12 Calculate Lead Time. 6-45 Approve . 6-22. 6-24 End (Ship Confirm). 6-29 Invoice Interface. 6-31 Purchase Release. 6-18 Create Configuration.Continue Line (Complete). 6-44 functions definitions. 6-39 Wait for Booking.Generic.Setup Parameters. 6-20 Create Supply Order . 6-25 Export Compliance Screening . 6-32 Purchase Release . 6-7 Invoice Interface .Eligible.Continue Line.Deferred.Deferred.Wait for Line.Header Level. 6-14 Calculate Purchase Price.Deferred. 6-47 Wait for Approval.Eligible. 6-14 Check Reservation. 6-9 Authorize to Ship . 6-26 Fulfill. 6-29 Inventory Interface .Eligible.Eligible.function activities Approval Failed.Eligible. 6-46 Utility .

6-30 item type.Eligible image. 4-6 Order Flow . 4-24 Line Flow . 2-6 Line Flow .Line. 4-7 selection recommendation. 2-6.Generic. Ship Only. 2-3 selection recommendation. Deferred item type. 6-29 seeded data file. with Repricing at Fulfillment. 6-28 overview. 5-43 process diagram.Line Flow . 5-46 process activities. Deferred item type. 2-3 2-3 I inbound processes. Bill Only. 5-46 parent processes. 2-6.Generic. 2-3 Order Flow . 6-29 item type.Generic. 4-44 Line Flow . 5-42 process summary. 4-40 Line Flow . 2-3 header level workflows Order Flow . 5-43 parent processes. 6-30 Inventory Interface Non-Ship .Generic. 2-3 seeded. 4-37 Order Flow . 2-6. 4-7 overview.Return with Approval Index-8 . 4-33 Line Flow . 5-46 process diagram. Deferred overview. 5-43 process activities. 5-42 Header level Invoice Interface .Deferred item type. 4-41 Line Flow . 4-35 Line Flow .Return for Credit Only. 2-3. 6-28. 6-7 Header Level Invoice Interface . 4-31 Line Flow . 6-29 PL/SQL procedure.Generic with Authorize to Ship (RLM). 4-6 overview. 2-6. 4-26 Line Flow .Line. 6-29 lookup. 2-3. 6-29 Inventory Interface . 2-3 Order Flow . overview. 5-48 process summary. With Export Compliance. 6-29 result codes. 2-3 usage.Generic with Header Level Invoice Interface. 4-28 Line Flow . 5-46 overview.Generic.Generic with Header Level Invoice Interface overview.Line item type.Eligible image. 5-44 Inventory Interface Non-Ship . 5-41 process activities. 4-46 Inventory Interface image. 6-29 overview. 5-43 overview. 6-28 PL/SQL procedure. Bill Only with Inventory Interface.Return for Credit Only with Approval. 6-28 seeded data file. 6-7 PL/SQL procedure. 5-47 H Header Invoice Interface . 4-9 selection recommendation.Line. 5-41 parent processes. 6-29 seeded data file. 6-30 overview.Generic. 2-3 overview. 5-45 process summary.Generic with Header Level Invoice Interface. 6-7 overview.Return for Credit with Receipt. 5-42 header level processes overview. 6-29 Inventory Interface .Generic. 2-3 usage.Return for Credit with Receipt and Approval.

6-8 PL/SQL procedure. 6-31 PL/SQL procedure. 6-31 overview. 6-30 item type.Configuration with Authorize to Ship (RLM) activities. 4-12 summary. 5-50 Invoice Interface . 1-10 processes. 4-15 item type. 4-19 overview. 4-17 Line Flow . 6-31 overview. 6-31 seeded data file. 6-31 item type. 6-8 Invoice Interface . 4-14 diagram. 6-8 overview.ATO Model activities. 4-18 diagram. 4-13 item type. 6-31 Invoice Interface . 6-30 lookup. 4-14 seeded data file. 2-5. 6-7 PL/SQL procedure.ATO Item activities. 6-30 overview. 4-19 summary.Line item type. 6-7 Invoice Interface . 6-32 item types in Oracle Order Management. 4-14 summary. 5-52 overview. 6-31 seeded data file. 4-14 overview. 4-23 Index-9 .Header Level image. 6-31 result codes. 6-30 result codes. 4-12 Line Flow . 4-16 seeded data file.Invoice Interface image. 6-30 PL/SQL procedure. 4-16 diagram. 6-32 item type. 6-31 item type.Generic activities. 2-5. 6-31 overview.Continue Line image.Eligible image. 4-21 diagram. 5-49 overview. 4-16 overview. 1-12 processes. 6-46 1-9 L Line Flow . 6-8 overview.Configuration activities. 4-20 item type. 4-15 Line Flow . 1-10 activities. 4-12 overview. 4-12 seeded data file.Deferred image. 4-18 item type. 6-31 PL/SQL procedure. 4-23 diagram. 4-20 Line Flow . OM Change Order. 6-31 seeded data file. 1-10 processes. 5-51 process activities. 4-5 OM Order Line. 6-32 lookup. 4-19 seeded data file. 2-5. 6-31 Invoice Interface . 5-49 parent processes. 5-51 Is Line Scheduled image. 6-30 PL/SQL procedure. 6-30 seeded data file.Line. 4-11 Standard. 5-49 process diagram. 4-4 OM Order Header. Deferred item type. 4-16 summary. 6-30 Invoice Interface .

4-25 item type.Return for Credit with Receipt and Approval activities. 2-6. 2-3 Line Flow . 2-4 summary. 4-39 item type. Bill Only activities. 4-41 summary.Return for Credit with Receipt activities. 4-28 diagram. 4-32 diagram.Return for Credit Only activities. 4-36 Line Flow . 4-28 summary. 4-26 overview. 4-37 summary. 4-46 overview. 2-6. 4-38 Line Flow . 4-47 item type. 4-37 seeded data file. 4-49 Index-10 . With Export Compliance activities. 4-44 overview. 4-37 overview. 4-40 summary. 4-40 Line Flow .Return for Credit Only with Approval activities. 4-26 selection recommendation. 4-26 seeded data file.Standard Service activities. 2-4. 4-36 item type. 4-43 item type. 4-33 overview. 4-41 item type. 4-21 selection recommendation. 4-35 overview. 4-43 diagram. 4-41 diagram. 4-28 item type. 4-41 overview. 4-41 seeded data file. 4-30 item type. 4-25 Line Flow . 2-3. 4-21 seeded data file. 4-42 Line Flow . 4-32 item type. 2-4. 4-33 Line Flow . 4-35 summary. 4-40 seeded data file. Ship Only activities. 2-3 summary. 4-31 overview. 4-45 diagram. 4-31 summary. 4-33 summary. 2-6. 4-33 seeded data file. 2-4. 4-24 overview. 4-47 Line Flow .Generic. 4-21 overview. 4-22 usage. 4-26 diagram.Generic.Generic with Authorize to Ship (RLM) activities. 4-46 summary. 4-31 seeded data file. 2-4 Line Flow . 4-28 overview. with Repricing at Fulfillment. 2-6.Generic. 4-34 diagram.Generic with Header Level Invoice Interface activities. 4-31 diagram. 4-35 seeded data file. Bill Only with Inventory Interface activities. 2-6. 4-34 item type. 4-24 summary.Generic. 4-32 Line Flow . 4-45 item type. 4-29 Line Flow . 4-44 Line Flow . 4-40 overview. 4-44 summary. 4-39 activities. 4-28 seeded data file. 4-46 seeded data file.Generic. 4-24 seeded data file. 4-27 usage. 2-4. 4-37 diagram. 4-44 seeded data file. 4-48 diagram. 2-4.item type.

4-40 Line Flow .Generic. 4-4 Change Order Process. 4-12 Line Flow . 4-28 Line Flow . 2-3 service items.wft item types. 1-7 processes. 2-4 Line Flow . 2-6. With Export Compliance overview.Generic. 2-3 seeded.diagram. 2-6.Return for Credit with Receipt and Approval overview. 2-4. 2-5. 4-21 selection recommendation. 2-8 associated with Oracle Release Management.Configuration overview. 4-26 selection recommendation.Return for Credit Only overview. 4-48 overview. 4-14 Line Flow . 2-4 usage. Ship Only overview. 4-16 Line Flow . 4-46 Line Flow . Bill Only with Inventory Interface overview. 2-6. 2-6 generic. 1-10 attributes. 4-35 Line Flow . 2-4. 4-44 Line Flow .Return for Credit Only with Approval overview.Generic. 2-6 line level processes assigning. 4-49 item type.ATO Item overview. 4-24 Line Flow . 2-6. 4-48 summary. A-1 O oexwford.Configuration with Authorize to Ship (RLM) overview. 1-10 attributes. 2-5. 2-6 overview. 1-8 Authorized to Ship . 3-4 N navigator paths. 4-37 Line Flow . with Repricing at Fulfillment overview. 2-6. 5-12 Calculate Lead Time . 2-6 Line Flow .ATO Model overview.Standard Service overview.Return for Credit with Receipt overview.Generic with Header Level Invoice Interface overview. 1-11 Index-11 . 2-3 inbound. 2-4. 4-41 overview. 2-3. 2-4.Generic. 2-3 usage. 4-48 seeded data file. 1-10 definition.Generic with Authorize to Ship (RLM) overview. 1-7 subprocesses.Generic. 4-48 Line Flow -Return for Credit Only with Approval overview. 4-19 Line Flow . 2-3 Line Flow . 1-10. 2-11 M modifying seeded data. 5-16 OM Change Order. 4-4 OM Order Header. 2-5. Bill Only overview. 2-3 line repricing.Generic overview. 1-10 processes.Line. 2-6. 4-49 line level inbound processes. 4-31 Line Flow . 4-33 Line Flow . 2-9 assigning transaction types. 2-6 line level workflows Line Flow . 2-4.Line.

4-26 Line Flow . 1-11 Book . Deferred.Generic.Return with Approval overview. 2-3 selection recommendation.Return for Credit Only with Approval overview. 2-4 Line Flow .Configuration overview. 2-4 usage. 2-6 overview. 6-9 AutoCreate FAS. 2-4 Line Flow .Generic with Header Level Invoice Interface overview. 2-6 Line Flow . 2-3 selection recommendation.Generic.Generic.Generic overview.Generic overview.Wait for Authorization.Generic. 4-37 Line Flow . 2-3 Order Flow . 4-7 Order Flow . 4-40 Line Flow . 4-33 Line Flow . 2-3 selection recommendation. 4-12 Line Flow .Return for Credit with Receipt and Approval overview.Check Status. Bill Only with Inventory Interface. 4-19 Line Flow . 2-4 Line Flow . Manual. 4-11 Line Flow . 2-5 Line Flow . 2-4 Line Flow . Ship Only overview.Order. 2-6 Line Flow .Generic.Generic. 2-4 selection recommendation. 2-6 Line Flow . 2-3 processes. 2-5 Line Flow . 4-21 Line Flow . Bill Only with Inventory Interface overview.Generic.ATO Model. 6-9 Authorize to Ship . 2-3 Line Flow .ATO Model overview.Generic. 2-4 Line Flow .Generic with Authorize to Ship (RLM). 2-3 usage. Ship Only.Configuration. 1-12 processes. 4-16 Line Flow . With Export Compliance overview.Return with Approval. 2-5 Line Flow . 2-3 selection recommendation.Generic with Authorize to Ship (RLM) overview. 4-44 Index-12 . 5-6 OM Order Line activities Authorize to Ship . 2-3 usage. 5-4 Book .Standard Service overview.Return for Credit Only overview. with Repricing at Fulfillment.Return for Credit with Receipt overview. Bill Only overview.Generic. 4-6 Order Flow . 6-10 Line Flow .Order.Configuration with Authorize to Ship (RLM). 2-3 Order Flow . 4-14 Line Flow .Generic with Header Level Invoice Interface.Generic. 4-41 Line Flow . Bill Only.Generic with Header Level Invoice Interface. 4-24 Line Flow . 1-11.ATO Item overview. 4-35 Line Flow . With Export Compliance. 4-5 Order Flow .ATO Item. 4-9 subprocesses. 2-6 Line Flow .Return for Credit Only with Approval.Order Flow . 4-28 Line Flow .Generic. 2-6 Line Flow .Generic with Header Level Invoice Interface overview.Return for Credit Only.Return for Credit with Receipt. 2-3 usage. 4-31 Line Flow .

4-6 overview. 5-59 Reprice . Deferred. 5-16 Close . Deferred. 5-26 Create Supply . 1-12 Authorized to Ship . 2-3 summary. 1-2 processing orders using. 5-41 Inventory Interface Non-Ship . 4-9 diagram. 2-7 Change Order Process. 1-2 viewing processes in. 4-7 overview. 4-10 diagram. 1-10 setup.Line. Deferred. 4-10 order line repricing.Generic activities. 2-11 P pricing date. 4-6 selection recommendation. Deferred. 4-7 seeded data file. 2-1 setup.Line. 4-7 diagram. 4-7 item type.Return with Approval activities.Line.Return for Credit with Receipt and Approval.Line.Line. 5-18 Create Configuration . Deferred.Line. 1-10 Standard.LIne. 4-6 usage. 1-3 Order Flow . 4-4 creating. 2-3 summary.Line Flow . 5-46 Invoice Interface . 5-61 Return Receiving . 1-3 viewing processes in. 5-23 Create Manufacturing Configuration Data Line.Line. 1-2 using Oracle Workflow in. 2-11 pricing lines. 4-8 item type.Line. 5-14 Calculate Lead Time . 5-12 Buy ATO Item Flow. 2-11 pricing phases. 5-49 Invoice Interface -Line.LIne.Line. 1-2 item types.Line. 5-32 Create Work Order . Manual. 2-12 process dependencies. 5-51 Purchase Release . Manual. 4-9 selection recommendation. 2-3 Order Flow . 1-4 Oracle Release Management line level processes. Manual. 1-2 introduction. 1-2 Oracle Workflow Builder image. 2-3.Line. 5-43 Inventory Interface Non-Ship .Line. 4-2 Index-13 . Manual. 1-5 assigning.Generic with Header Level Invoice Interface activities. 4-48 subprocesses. 3-6 processes Activities List window.Line. 1-2 using Oracle Order Management in.Line.Standard Service. 5-36 Export Compliance Screening . 5-28 Create Supply Order . 5-63 Schedule . 2-3 Order Flow . 1-9. 5-34 Enter . 2-6 Oracle Workflow introduction. Manual. 2-8 CTO Change Order Process. 2-3. 5-65 Schedule .Line. 2-3. 5-69 Oracle Order Management implementation. 5-39 Header Level Invoice Interface . 2-3 summary. 3-4 process parameters.Line. 4-6 seeded data file. 4-7 selection recommendation. 4-8 usage. 4-46 Line Flow . 4-9 seeded data file.Line. 4-9 overview. 5-54 Purchase Release .Line. 4-10 item type. 5-67 Ship .

Return for Credit Only with Approval overview.ATO Item overview. 4-19 Line Flow . 1-3 processing orders using Oracle Workflow.Deferred image. 2-12 fulfillment date.Generic with Header Level Invoice Interface overview. 2-13 image. 6-32 overview. 4-12 Line Flow . 6-33 PL/SQL procedure. 5-59 R Reprice attributes. Ship Only overview.definitions. 6-33 Calculate Price flag.Return for Credit Only overview. 2-2 View Diagram window.Return for Credit with Receipt overview. 4-21 Line Flow .Eligible image. 4-46 Line Flow .Generic.Generic. 4-31 Line Flow .Return for Credit with Receipt and Approval overview. with Repricing at Fulfillment overview. Deferred overview. 6-33 overview. 6-33 overview. 4-1 selecting. 6-32 PL/SQL procedure. 4-33 Line Flow . 5-54 Purchase Release . 2-3 inbound. 6-33 Purchase Release .Line. 6-34 item type. 4-24 Line Flow . 4-41 Line Flow . 1-4 viewing in Oracle Workflow Builder.Generic. 6-32 lookup.Generic with Authorize to Ship overview. Manual overview.Generic. 6-32 seeded data file. 2-1 Purchase Release image. 6-32 item type. 4-37 Line Flow . 6-33 Purchase Release . 4-16 Line Flow . 4-44 Line Flow .Line.Generic. 4-26 Line Flow . 6-34 Index-14 . 6-33 item type. 4-9 seeded.Generic with Header Level Invoice Interface overview.Return with Approval overview. 2-6 Line Flow . 6-33 seeded data file.Configuration overview. 6-32 Purchase Release . 1-6 viewing in Oracle Order Management.Configuration with Authorize to Ship (RLM) overview. 4-7 Order Flow . Bill Only overview.Generic overview. 4-14 Line Flow . 6-32 PL/SQL procedure. 4-28 Line Flow . 4-40 Line Flow .Generic overview.ATO Model overview. 4-1 generic. Bill Only with Inventory Interface overview. 6-33 item type. 4-48 Order Flow . 6-33 seeded data file. 4-6 Order Flow .Standard Service overview. 6-32 result codes. 4-35 Line Flow . With Export Compliance overview.

6-36 PL/SQL procedure.Line. 6-33 pricing date. 5-65 overview. 6-35 PL/SQL procedure. 5-68 process summary. 6-35 overview. 5-63 running background engine schedules. 6-35 seeded data file. 5-65 Schedule . 5-66 process summary. 2-11 pricing phases. 6-36 item type.lookup. 1-9 in Oracle Order Management. 2-12 seeded data file. 6-36 Schedule .Line overview. 6-34 item type. 2-12 schedule date. 5-67 seeded data file. 2-10 S sales orders assigning workflows to. 5-61 repricing. 2-3 line level.Line overview. 5-69 process diagram. 2-12 fulfillment date. 6-35 lookup.Eligible image. 5-67 overview. 6-35 item type. 2-10 scheduling processes. 2-7 Schedule image. 2-3 seeded workflows header level. 6-36 overview. 2-12 ship date. 2-12 Reprice .Line item type. 1-7 types of. 5-67 process diagram. 2-12 troubleshooting.wft. 6-36 overview. 2-12 repricing event attributes. 5-65 parent processes. Deferred item type. 6-34 ship date. 6-34 seeded data file. 2-3 line level. 2-12 repricing event attributes. oexwford.wft. 5-67 scheduling lines. 6-34 Reprice . 6-35 result codes. 6-34 overview. B-2 repricing order lines. 6-1 seeded data files ctochord.Eligible image. 6-34 overview. 2-12 Retry Only error process. 6-35 item type. 3-1 header level. 6-34 schedule date. 2-11 repricing pricing phases. 2-12 result codes. 2-10 seeded activity definitions. 5-66 seeded data file. 1-6 seeded processes extending. 5-67 process activities. B-3 Return Receiving . 6-33 PL/SQL procedure. 6-36 seeded data file. B-2 pricing phases. 5-65 process activities. 6-35 PL/SQL procedure. 2-3 selecting processes 1-6 Index-15 . 5-68 processes. 6-35 seeded data file. 6-35 Schedule . 6-34 PL/SQL procedure.Deferred image. 6-36 Schedule . 2-10 scheduling workflows. 2-13 handling errors in.

Line. 5-49 Invoice Interface . 1-2 Oracle Workflow. 2-2 recommendations. Manual item type. Deferred. 1-2 Ship image. 1-5 Authorized to Ship . 2-2 selecting subprocess recommendations. 6-36 result codes. 5-69 View Diagram window. 6-46 item type.Line. 2-6 service processes Line Flow . 6-37 item type. 5-1 Ship . 5-39 Header Level Invoice Interface . 2-2 selecting subprocesses guidelines. 1-6 viewing in Oracle Order Management. 5-54 Purchase Release . 1-12 Purchase Release .Line. 6-36 seeded data file. 5-18 Create Configuration . 2-8 custom processes. 6-37. 5-65 Schedule . 5-69 process activities.Line.Deferred image. 4-48 setup access level. 6-37 Ship . 5-1 Enter . 5-70 overview. 2-8 seeded functions.Line. 2-2 recommendations. 5-4 Book . Deferred. 5-32 Create Work Order .Standard Service. 6-36 PL/SQL procedure. 6-37.guidelines.Line. 5-43 Inventory Interface Non-Ship .Order. Deferred.Line. 1-2 Oracle Order Management. 5-23 Create Manufacturing Configuration Data . 1-2 Oracle Workflow in Oracle Order Management. 5-28 Create Supply Order . 5-16 Close . 5-61 Return Receiving .Line. 5-41 Inventory Interface Non-Ship .Order. Manual.Line. 1-3 support custom activities. Deferred. 2-6 Line Flow . 2-8 seeded subprocesses. 5-59 Reprice . 5-63 Schedule . 5-36 Export Compliance Screening . 2-8 seeded processes.Standard Service. 5-34 definitions. 2-8 seeded activities.Line. 5-51 OM Order Header. 5-72 process summary. 5-67 seeded.Line. 6-37 Ship . 5-14 Calculate Lead Time .Line. Manual.Line.Line. 2-8 Index-16 . 6-37 overview. Manual. 6-37 PL/SQL procedure.Line.Line.Line.Line. 6-46 Start image.Line. 5-6 Buy ATO Item Flow. 5-70 processes.Line. Manual.Line. Deferred. 5-69 standard activities. Manual. 6-36 overview. 6-37. 1-11 OM Order Line. 1-4 viewing in Oracle Workflow Builder. Deferred. 6-37 subprocesses Activities List window. 6-37 lookup.Line. 5-12 Book . 6-36 item type. 6-37 seeded data file. Manual. 6-37 overview. 5-26 Create Supply .Line. 5-46 Invoice Interface . 6-47 seeded data file. 6-46 PL/SQL procedure. 2-2 service item processes. 2-2 selecting workflows guidelines.

6-45 image.Is Return Line Receivable? image. 6-41 lookup. 6-38 item type. 6-39 item type. 6-38 PL/SQL procedure. 6-40 PL/SQL procedure. 6-38 seeded data file. B-3 Utility . 6-40 item type. 6-41 seeded data file. 6-46 Utility to Get Line Category image. 2-7 workflow assignments. B-3 W Wait attributes. 2-7 window image. 6-39 seeded data file. 6-39 lookup. 6-40 Wait for Create Configuration image. 1-6 viewing workflow status errors. 2-8 line level process assignments. 6-40 overview. 6-41 overview. 6-39 image. 2-8 Line Workflow Assignments window image. 6-45 PL/SQL procedure. 6-39 seeded data file. 6-39 overview. B-2 repricing. B-2 viewing workflow status. 6-38 overview. 6-45 item type. 6-40 image. 2-7 troubleshooting. 6-39 result codes. 6-40 Wait for Booking attributes. 6-38 result codes. 6-39 V View Diagram window image. 6-38 item type. 6-38 Utility . 6-38 overview. 6-47 image. 6-48 Wait for Approval attributes. 6-45 seeded data file. 6-38 seeded data file. 6-38 result codes. 6-38 Index-17 . 2-8 Line Workflow Assignments window. 6-38 lookup. 6-39 PL/SQL procedure. B-3 Utility to Get Supply Source Type image. 6-41 item type. 6-38 lookup. 6-41 result codes. 6-41 U unexpected errors. 6-40 item type. 6-40 PL/SQL procedure.Set Notification Approver attributes. 6-48 overview.T transaction types determining header level processes. 6-40 overview. 2-8 seeded. B-3 viewing workflow status. 6-46 overview. B-3 unexpected errors. 2-8 line flow assignments. 6-38 PL/SQL procedure. 6-40 seeded data file. 6-47 PL/SQL procedure. B-1 expected errors. 6-39 PL/SQL procedure. 6-41 Wait for CTO image.

2-10 seeded definitions. 6-43 result codes. 6-41 overview. 2-10 setup. 6-43 seeded data file. 6-42 overview. 6-43 PL/SQL procedure. 6-44 item type. 3-2 scheduling activity. 6-43 item type. 6-42 lookup. 6-42 PL/SQL procedure. 6-43 item type. 2-1 workflow background engine. 6-44 result codes. 5-1 workflows assigning. 6-43 overview. 2-8 workflow subprocess seeded definitions. 6-44 lookup. 2-10 workflow dependencies. 6-41 seeded data file. A-1 workflow processing orders using. 6-41 result codes. 6-42 seeded data file. 6-43 Wait for PO Receipt image. 6-44 seeded data file. 6-42 item type. 4-1 selecting. 6-43 overview. 6-43 PL/SQL procedure. 6-43 Wait for Receiving image. 6-42 seeded data file. 6-44 PL/SQL procedure. 2-2 Index-18 . 6-44 seeded data file. 6-44 overview. 3-3 extending. 6-45 overview. 6-41 PL/SQL procedure.item type. 6-42 image. 2-9 schedules. 6-44 Wait for Required for Revenue or Delivery image. 6-42 Wait for Invoice Interface attributes. 2-10 overview. 6-44 item type. 6-42 result codes. 2-2 selection guidelines. 6-42 PL/SQL procedure. 6-42 lookup. 6-43 lookup. 3-5 workflow processes creating. 3-4 workflow guidelines. 2-7 customizing. 6-45 windows. 6-42 Wait for Inspection image.

Master your semester with Scribd & The New York Times

Special offer for students: Only $4.99/month.

Master your semester with Scribd & The New York Times

Cancel anytime.