Skip Headers

Oracle Order Management Using Oracle Workflow in Oracle Order Management
Release 12.1
Part Number E16350-02
Go to Table of Contents
Contents
Go to previous page
Previous
Go to next page
Next

Seeded Function Activity Definitions

This chapter covers the following topics:

OM Order Header

Approve - Continue Line

The Approve - Continue Line activity is an OM Order Header activity that uses standard Oracle Workflow functionality to continue the workflow in progress. Approve - Continue Line activity is used to mark the position in the process where, upon completion the approval process, the halted process will continue.

The Approve - Continue Line activity calls the PL/SQL procedure named WF_ STANDARD.CONTINUEFLOW.

The Approve - Continue Flow activity contains two activity attributes:

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

Book

The Book activity calls the PL/SQL procedure named OE_BOOK_WF.BOOK_ORDER to book an order. The Book activity uses the lookup OM Subprocess Results, Handles Holds. This lookup contains the following result codes:

The Book activity will complete with one of these results.

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:

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.

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 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 Book - Eligible activity is contained in the Seeded Data File oexwford.wft, and is associated with the OM Order Header item type.

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:

The Close activity will complete with one of these results.

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:

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 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:

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 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:

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

Invoice Interface - Header Level

The Invoice Interface - Header Level activity is an OM Order Header activity that calls the PL/SQL procedure named OE_INVOICE_WF.INVOICE_INTERFACE to conduct header level invoice interfacing.

Invoice Interface - Header Level uses the lookup (has a result type of) Invoice

Results. This lookup contains the following result codes:

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

OM Order Line

Authorize to Ship - Check Status

The Authorize to Ship - Check Status activity is an OM Order Line activity that calls the PL/SQL procedure named OE_RLM_WF.CHECK_AUTHORIZE_TO_SHIP to determine whether an order line is authorized for shipping.

Authorize to Ship - Check Status uses the lookup (has a result type of) Yes/No. This lookup contains the following result codes:

The Authorize to Ship - Check Status activity is contained in the Seeded Data File oexwford.wft, and is associated with the OM Order Line item type.

Authorize to Ship - Wait for Authorization

The Authorize to Ship - 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. Authorize to Ship - Wait for Authorization marks the position in the process where, when the line is authorized, the halted process will continue.

The Authorize to Ship - Wait for Authorization activity calls the PL/SQL procedure named WF_STANDARD.BLOCK.

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

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.SUBMIT_CONC_ PROG_WF. 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:

The AutoCreate FAS activity uses the lookup (has a result type of) Concurrent Program Status. This lookup contains the following result codes:

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

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.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. This lookup contains the following result codes:

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

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.

The Branch on Source Type activity uses the lookup (has a result type of) Source Type. This lookup contains the following result codes:

The Branch on Source Type activity is contained in the Seeded Data File oexwford.wft, and is associated with the OM Order Line item type.

Calculate Cost Rollup

The Calculate Cost Rollup activity is an OM Order Line activity that calls the CTO PL/SQL procedure named CTO_WORKFLOW.CALCULATE_COST_ROLLUP_WF_ML to calculate the cost of a configuration.

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

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.SUBMIT_AND_ CONTINUE_WF. 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.

Calculate Lead Time contains the following attributes:

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

Calculate Lead Time - Setup Parameters

The Calculate Lead Time - Setup Parameters is an OM Order Line activity that calls the Configure to Order PL/SQL procedure named CTO_WORKFLOW.SET_ PARAMETER_LEAD_TIME_WF_ML to prepare to launch the lead time calculation concurrent program. This is accomplished by setting up the line number as the parameter of the concurrent program.

The Calculate Lead Time - Setup Parameters activity uses the lookup (has a result type of) Lead Time Result. This lookup contains the following result codes:

The Calculate Lead Time - Setup Parameters activity is contained in the Seeded Data File oexwford.wft, and is associated with the OM Order Line item type.

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.Purchase_ price_calc_wf to determine the purchase price of the configuration.

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

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.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. This lookup contains the following result codes: Process AutoCreate PO

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

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.

The Check Supply Type activity uses the lookup (has a result type of) Check Supply Type Results. This lookup contains the following result codes:

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

Close

The Close activity is an OM Order Line activity that calls the PL/SQL procedure named OE_CLOSE_WF.CLOSE_LINE to close an order line.

The Close activity uses the lookup (has a result type of) OM Subprocess Results, Handles Holds. This lookup contains the following result codes:

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

Close - Continue Header

The Close - Continue Header activity is an OM Order Line activity that uses standard Oracle Workflow functionality to continue the workflow in progress. The Close - Continue Header activity is used to mark the position in the process where, upon completion the of Close activity, the halted header level process will continue. The Close - Continue Header activity calls the PL/SQL procedure named WF_ STANDARD.CONTINUEFLOW.

The Close - Continue Header activity contains the following attributes:

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

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.

To use Close - Deferred, the Close activity must be placed immediately after it in the process flow.

The Close - Deferred activity calls the PL/SQL procedure named WF_ STANDARD.DEFER.

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

Configuration - Check Status

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.

The Configuration - Check Status activity uses the lookup (has a result type of) Config Data Results. This lookup contains the following result code:

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

Configuration - Create BOM and Routing

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.CREATE_BOM_AND_ROUTING_WF to create bill of material and routing for an order line.

Note: This function activity is not used in current processes and subprocesses and is listed for reference only. Do not use this activity when creating or extending workflow processes and subprocesses.

The Configuration - Create BOM and Routing activity uses the lookup (has a result type of) Config Incomplete. This lookup contains the following result codes:

The Configuration - Create BOM and Routing activity is contained in the Seeded Data File oexwford.wft, and is associated with the OM Order Line item type.

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.CREATE_CONFIG_ ITEM_WF to create configuration for an order line. This activity creates the new line on the order for the configuration item, creates the new item, and creates the BOM and Routing.

The Create Configuration activity uses the lookup (has a result type of) Config Incomplete. This lookup contains the following result codes:

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

Create Configuration - Eligible

The Create Configuration - 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.

The Create Configuration - Eligible activity calls the PL/SQL procedure named OE_ STANDARD_WF.STANDARD_BLOCK.

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

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.CREATE_FLOW_ SCHEDULE_WF to create a flow schedule for an order line.

The Create Flow Schedule activity uses the lookup (has a result type of) Config Incomplete. This lookup contains the following result codes:

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

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.CREATE_CONFIG_WF.

Note: This function activity is not used in current processes and subprocesses and is listed for reference only. Do not use this activity when creating or extending workflow processes and subprocesses.

The Create or Match Config Item activity is contained in the Seeded Data File oexwford.wft, and is associated with the OM Order Line item type.

Create Supply Order - Eligible

The 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, Autocreate Purchase Req, or Autocreate Dropship).

The Create Supply Order - Eligible activity calls the PL/SQL procedure named OE_ STANDARD_WF.STANDARD_BLOCK.

The Create Supply Order - Eligible activity uses the lookup (has a result type of) Reserved Status. This lookup contains the following result codes:

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

Create Work Order - Set Up Parameters

The Create Work Order - Set Up Parameters activity is an OM Order Line activity that calls the PL/SQL procedure named CTO_WORKFLOW.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.

The Create Work Order - Set Up Parameters activity uses the lookup (has a result type of) Config Incomplete. This lookup contains the following result codes:

The Create Work Order - Set Up Parameters activity is contained in the Seeded Data File oexwford.wft, and is associated with the OM Order Line item type.

End

The End activity marks the end of a process and does not perform any action. The End activity calls the PL/SQL procedure named WF_STANDARD.NOOP. The End activity is contained in the Seeded Data File oexwford.wft, and is associated with the OM Order Line item type.

End (Complete)

The End activity marks the end of a process and does not perform any action.

The End (Complete) activity calls the PL/SQL procedure named WF_ STANDARD.NOOP.

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

End (Incomplete)

The End (Incomplete) activity marks the end of a process and does not perform any action.

The End (Incomplete) activity calls the PL/SQL procedure named WF_ STANDARD.NOOP.

The End (Incomplete) activity is contained in the Seeded Data File oexwford.wft, and is associated with the OM Order Line item type.

End (Non Shippable)

The End (Non Shippable) activity marks the end of a process and does not perform any action.

The End (Non Shippable) activity calls the PL/SQL procedure named WF_ STANDARD.NOOP.

The End (Non Shippable) activity is contained in the Seeded Data File oexwford.wft, and is associated with the OM Order Line item type.

End (Not Eligible)

The End (Not Eligible) activity marks the end of a process and does not perform any action.

The End (Not Eligible) activity calls the PL/SQL procedure named WF_ STANDARD.NOOP.

The End (Not Eligible) activity is contained in the Seeded Data File oexwford.wft, and is associated with the OM Order Line item type.

End (Over Shipped Beyond Tolerance)

The End (Over Shipped Beyond Tolerance) activity marks the end of a process and does not perform any action.

The End (Over Shipped Beyond Tolerance) activity calls the PL/SQL procedure named WF_STANDARD.NOOP.

The End (Over Shipped Beyond Tolerance) activity is contained in the Seeded Data File oexwford.wft, and is associated with the OM Order Line item type.

End (Ship Confirm)

The End (Ship Confirm) activity marks the end of a process and does not perform any action.

The End (Ship Confirm) activity calls the PL/SQL procedure named WF_ STANDARD.NOOP.

The End (Ship Confirm) activity is contained in the Seeded Data File oexwford.wft, and is associated with the OM Order Line item type.

End (Unreserve)

The End (Unreserve) 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.NOOP.

The End (Unreserve) activity is contained in the Seeded Data File oexwford.wft, and is associated with the OM Order Line item type.

Export Compliance Screening

Oracle Order Management provides a subprocess for export compliance screening, The Export Compliance Screening-Line is a subprocess to the seeded Line Flow—Generic With Export Compliance workflow process, and executes International Trade Management functions. ITM handles all export related compliance checks, including Restricted Party Screening, Embargo Country Screening, License Determination, Document Generation and other partner supported screening such as EPCI.

It is recommended to add this subprocess after Scheduling.

The Export Compliance Screening activity calls the PL/SQL procedure named OE_ EXPORT_COMPLIANCE_WF.ECS_REQUEST.

The Export Compliance Screening activity uses the lookup (has a result type of) OM Export Compliance Results. This lookup contains the following result codes:

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

Export Compliance Screening - Eligible

The Export Compliance Screen - Eligible activity is an OM Order Line activity that determines export compliance.

The Export Compliance Screening - Eligible activity calls the PL/SQL procedure named OE_STANDARD_WF.STANDARD_BLOCK.

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

Firm Demand

The Firm Demand activity is an OM Order Line activity that calls the PL/SQL procedure named OE_OEOL_SCH.FIRM_DEMAND to firm the order line.

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

Firm Eligible

The Firm Eligible activity is an OM Order Line activity that calls the PL/SQL procedure named OE_STANDARD_WF.STANDARD_BLOCK to determine whether an order line is eligible to be firmed.

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

Fulfill

The Fulfill activity is an OM Order Line activity that calls the PL/SQL procedure named OE_FULFILL_WF._FULFILLMENT to perform fulfillment for an order line. The Fulfill activity contains the following attributes:

The Fulfillment activity coordinates the fulfillment of lines so that they progress together to invoicing. It applies to models and kits (shippable and non-shippable lines), fulfillment sets, and service lines attached to goods. The Fulfill activity also derives and stores additional data needed for Oracle Daily Business Intelligence (DBI) and service lines.

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

Fulfill - Continue Header Flow

The Fulfill - 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. The Fulfill - Continue Header Flow activity is used to mark the position in the process where, upon completion the Fulfill activity by all lines, the halted header level process will continue.

The Fulfill - Continue Header Flow activity calls the PL/SQL procedure named WF_ STANDARD.CONTINUEFLOW.

The Fulfill - Continue Header Flow activity contains the following attributes:

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 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:

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 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 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:

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 Inventory Interface activity must be placed immediately after it in the process flow.

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

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 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 Firmed

The Is Line Firmed activity is an OM Order Line activity that calls the PL/SQL procedure named OE_OEOL_SCH.IS_LINE_FIRMED to determine whether an order line is firmed.

The Is Line Firmed activity uses the lookup (has a result type of) OM SubProcess Results. The lookup contains the following result codes:

The Is Line Firmed 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:

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:

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.

To use Purchase Release - Deferred, the Purchase Release activity must be placed immediately after it in the process flow.

The Purchase Release - Deferred activity calls the PL/SQL procedure named WF_ STANDARD.DEFER.

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

Purchase Release - Eligible

To enable a function for manual completion, you must place a special block activity before the actual function activity. For purchase release, the Purchase Release - Eligible activity is the special block activity that facilitates this.

The Purchase Release - Eligible activity calls the PL/SQL procedure named OE_ STANDARD_WF.STANDARD_BLOCK.

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

Reprice

The Reprice activity is an OM Order Line activity that calls the PL/SQL procedure named OE_REPRICE_WF.START_REPRICING to reprice an order line.

The Reprice activity contains the following attributes:

The Reprice activity uses the lookup (has a result type of) OM Subprocess Results. This lookup contains the following result codes:

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

Reprice - Eligible

To enable a function for manual completion, you must place a special block activity before the actual function activity. For repricing, the Reprice - Eligible activity is the special block activity that facilitates this.

The Reprice - Eligible activity calls the PL/SQL procedure named OE_STANDARD_ WF.STANDARD_BLOCK.

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

Schedule

The Schedule activity is an OM Order Line activity that calls the PL/SQL procedure named OE_OEOL_SCH.SCHEDULE_LINE to schedule an order line.

The Schedule activity uses the lookup (has a result type of) OM Subprocess Results, Handles Holds. This lookup contains the following result codes:

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

Schedule - Deferred

The Schedule - Deferred activity is an OM Order Line activity that uses standard Oracle Workflow functionality to defer the order line scheduling to the background engine.

To use Schedule - Deferred, the Schedule activity must be placed immediately after it in the process flow.

The Schedule - Deferred activity calls the PL/SQL procedure named WF_ STANDARD.DEFER.

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

Schedule - Eligible

To enable a function for manual completion, you must place a special block activity before the actual function activity. For scheduling, the Schedule - Eligible activity is the special block activity that facilitates this.

The Schedule - Eligible activity calls the PL/SQL procedure named OE_STANDARD_ WF.STANDARD_BLOCK.

The Schedule - Eligible activity is contained in the Seeded Data File oexwford.wft, 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.START_SHIPPING to initiate shipping for an order line. The Ship activity uses the lookup (has a result type of) Shipping Results. This lookup contains the following result codes:

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

Ship - Deferred

The Ship - Deferred activity is an OM Order Line activity that uses standard Oracle Workflow functionality to defer shipping to the background engine.

To use Ship - Deferred, the Ship activity must be placed immediately after it in the process flow.

The Ship - Deferred activity calls the PL/SQL procedure named WF_ STANDARD.DEFER.

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

Start

The Start activity marks the start of a process and does not perform any action. Although it is not necessary, you may include it in your process diagram to visually mark the start of a process as a separate node.

The Start activity calls the PL/SQL procedure named WF_STANDARD.NOOP. The Start activity is contained in the Seeded Data File oexwford.wft, and is associated with the OM Order Line item type.

Utility - Is Return Line Receivable?

The Utility - Is Return Line Receivable? activity is an OM Order Line activity that calls the PL/SQL procedure named OE_RMA_WF.IS_LINE_RECEIVABLE to determine whether an return order line must be received.

The Utility - Is Return Line Receivable? activity uses the lookup (has a result type of) Yes/No. This lookup contains the following result codes:

The Utility - Is Return Line Receivable? activity is contained in the Seeded Data File oexwford.wft, and is associated with the OM Order Line item type.

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.GET_LINE_CATEGORY to determine the category of an order line. An order line can either be an order or a return. The Utility to Get Line Category activity uses the lookup (has a result type of) Line Category. This lookup contains the following result codes:

The Utility to Get Line Category activity is contained in the Seeded Data File oexwford.wft, and is associated with the OM Order Line item type.

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.GET_SUPPLY_SOURCE_TYPE to determine the supply source type for an order line. A supply source can be either internal or external.

The Utility to Get Supply Source Type activity uses the lookup (has a result type of) Supply Source Type. This lookup contains the following result codes:

The Utility to Get Supply Source Type activity is contained in the Seeded Data File oexwford.wft, and is associated with the OM Order Line item type.

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. The Wait For Approval activity uses standard Oracle Workflow functionality to pause the process until the order line is approved. Wait for Approval marks the position in the process where, when all the order line is approved, the halted process will continue.

The Wait for Approval activity calls the PL/SQL procedure named WF_ STANDARD.WAITFORFLOW.

The Wait for Approval activity contains the following attributes:

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

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. The Wait For Booking activity uses standard Oracle Workflow functionality to pause the process until the order is booked. Wait for Booking marks the position in the process where, when the order is booked, the halted line level process will continue. The Wait for Booking activity calls the PL/SQL procedure named WF_ STANDARD.WAITFORFLOW.

The Wait for Booking activity contains the following attributes:

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

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. It is not necessary to perform these calculations if the configuration data is already created by the autocreate config batch program. If this is the case, the subprocess would end.

Wait for Create Configuration calls the PL/SQL procedure named WF_ STANDARD.BLOCK.

The Wait for Create Configuration activity uses the lookup (has a result type of) Config Data Results. This lookup contains the following result codes:

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

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 configuration line level process completes when the configuration ships. 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, when the results are received, the halted process will continue.

Wait for CTO calls the PL/SQL procedure named WF_STANDARD.BLOCK.

The Wait for CTO activity uses the lookup (has a result type of) Config Item Results. This lookup contains the following result codes:

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

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. The Wait For Inspection activity uses standard Oracle Workflow functionality to pause the process. Wait for Inspection marks the position in the process where, when the item is inspected, the halted process will continue.

The Wait for Inspection activity calls the PL/SQL procedure named WF_ STANDARD.BLOCK.

The Wait for Inspection activity uses the lookup (has a result type of) RMA Wait Result. This lookup contains the following result codes:

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

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 Invoice Interface activity uses standard Oracle Workflow functionality to pause the process. Wait for Invoice Interface marks the position in the process where, after invoice interface is complete, the halted process will continue.

The Wait for Invoice Interface activity calls the PL/SQL procedure named WF_ STANDARD.WAITFORFLOW.

Wait for Invoice Interface contains the following attributes:

The Wait for Invoice Interface activity is contained in the Seeded Data File oexwford.wft, 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. The Wait For PO Receipt activity uses standard Oracle Workflow functionality to pause the process. Wait for PO Receipt marks the position in the process where, when the receipt is received, the halted process will continue. The Wait for PO Receipt activity calls the PL/SQL procedure named OE_ STANDARD_WF.STANDARD_BLOCK.

The Wait for PO Receipt activity uses the lookup (has a result type of) Config Process Results. This lookup contains the following result codes:

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

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. The Wait For Receiving activity uses standard Oracle Workflow functionality to pause the process. Wait for Receiving marks the position in the process where, when the item is received, the halted process will continue.

The Wait for Receiving activity calls the PL/SQL procedure named OE_RMA_ WF.WAIT_FOR_RECEIVING.

The Wait for Receiving activity uses the lookup (has a result type of) OM Subprocess Success Results. This lookup contains the following result codes:

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

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 Revenue or Delivery activity uses standard Oracle Workflow functionality to pause the process. Wait for Revenue or Delivery marks the position in the process where the halted process will continue.

The Wait for Required for Revenue or Delivery activity calls the PL/SQL procedure named WF_STANDARD.BLOCK.

The Wait for Required for Revenue or Delivery activity is contained in the Seeded Data File oexwford.wft, and is associated with the OM Order Line item type.

OM Standard

Approvals

A workflow process for Approvals allows you to leverage any business process where Approvals may be required. The Approver list is set up in Oracle Order Management and tied to a specific transaction type; workflow notifications provide details of the approval or rejection. The Approval activity is seeded in the negotiation phase as well as in the Oracle iStore Returns flow. A list of approvers can be defined through the Transaction Types or Approvals window, which can be accessed from the Transaction Types window or the Transaction Types menu.

Utility - Set Notification Approver

The Utility - Set Notification Approver activity calls the PL/SQL procedure named OE_ORDER_WF_UTIL.SET_NOTIFICATION_APPROVER to determine the approver for the notification Approve Return Order. The Utility - Set Notification Approver activity contains the following attribute:

If this attribute is set to Profile Approver, then the approver is determined by the value of profile option OM: Notification Approver. If the profile is not set at any level, then this PL/SQL procedure assumes SYSADMIN as the default approver. On receiving such a notification, the role SYSADMIN can:

The Utility - Set Notification Approver activity is contained in the Seeded Data File oexwford.wft, and is associated with the OM Standard

Standard

Oracle Workflow provides some generic activities you can use to control your processes. The activities are associated with the Standard item type but can be used within any process you define. The Standard item type is automatically installed on your Oracle Workflow server. The following are the Standard activities used by Oracle Order Management. For more information about the Oracle Workflow Standard activities, refer to the Oracle Workflow User's Guide.

End

The End activity marks the end of a process and does not perform any action. You can use it to return a result for a completed process by specifying a Result Type for the activity. Although it is not necessary, you may include it in your process diagram to visually mark the end of your process as a separate node.

The End activity calls the PL/SQL procedure named WF_STANDARD.NOOP.

Start

The Start activity marks the start of a process and does not perform any action. Although it is not necessary, you may include it in your process diagram to visually mark the start of a process as a separate node.

The Start activity calls the PL/SQL procedure named WF_STANDARD.NOOP.

Wait

The Wait activity pauses the process for the time you specify. You can wait until:

The Wait activity has six activity attributes:

  1. Wait Mode: use this attribute to specify how to calculate the wait. You can choose one of the following wait modes:

  2. Absolute Date: if Wait Mode is set to Absolute Date, enter an absolute date.

  3. Relative Time: if Wait Mode is set to Relative Time, enter a relative time expressed in <days>.<fraction of days>. For example, enter 0.5 for a wait time of half a day (12 hours).

  4. Day of Month: If Wait Mode is set to Day of Month, choose a day of the month from the list. If the day you choose has already passed in the current month, then the activity waits until that day in the following month.

  5. Day of Week: If Wait Mode is set to Day of Week, choose a day of the week from the list. If the day you choose has already passed in the current week, then the activity waits until that day in the following week.

  6. 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.

The Wait activity calls the PL/SQL procedure named WF_STANDARD.WAIT.

Negotiation

The following are identified as status requirements for the negotiation phase that is applicable to both Quotes in Sales Orders as well as Sales Agreements.

Approved

This signifies the sales proposal has received internal approval, by all approvers. The version that has been approved should be exactly what is presented to the customer for acceptance, otherwise if changes are made, the document should go through approval again.

Approval Timeout

The proposal has not been approved or rejected and has reached the timeout point.

Assign

The offer is assigned to the first approver.

Customer Acceptance

This activity enables the customer to choose whether to accept or reject the proposal.

Note: Please note that this activity in the Negotiation process is different from Customer Acceptance where the customer does a pre-billing or post-billing acceptance of the goods received.

Customer Accepted

This signifies that the proposal has received the customer's approval and is accepted by the customer. Typically, the proposal should not be modified once the customer has accepted it. You must set this up with processing constraints. This includes the sign and counter sign process.

See Change Management in the Oracle Order Management Implementation Manual for more information on Processing Constraints.

Customer Rejected

This signifies that the proposal has been received and the customer has rejected the proposal.

Draft

When a quote is created and is being assembled and negotiated, it is being 'drafted'; the document has not been approved internally or accepted by the customer yet, and is therefore not in effect yet. Changes can be made to a draft document and there are no formal change approvals required.

Draft-Customer Rejected

If the customer rejects the sales proposal, it returns to the “Draft” activity. The status is updated to Draft-Customer Rejected.

Draft-Internal Rejected

A sales proposal in the internal approval process that is rejected returns to the “Draft” status. It will return to the same activity in the flow as when it was in the “Draft” status, but the status will be update to “Draft-Internal Rejected” The rejection reason (comments) should be viewable so that modifications can be made, and the document can be re-submitted for approval.

Get Next Approver

The next approver in the list of approvers is notified that the proposal approval has been sent to them and action is required.

Initiate Approval

The proposal approval time has begun.

Internal Approved

The proposal has been approved. (See Approval List setup for a list of Internal Approvers).

Internal Rejected

The proposal has been rejected.

Negotiation Complete

This status indicates that the negotiation is complete.

Negotiation Complete - Eligible

This status indicates that the negotiation is eligible to be completed.

Negotiation Lost

This status signifies that the proposal has been lost. Neither the Internal management nor the Customer was able to reach an agreement. The proposal can only be transitioned to Lost if it is in the Draft stage. Once the proposal has been transitioned to Lost, it cannot be reinstated. However, it can be copied to restart the negotiation process.

Offer Expired

A Quote (negotiation) can have an expiration date. When the quote reaches this date, it expires and cannot become a firm order. To use it again, you must copy the quote. This status does not apply to sales agreements.

Pending Customer Acceptance

Once the sale proposal is approved internally, it waits at the customer acceptance block. The status is updated to “Pending Customer Acceptance” to signify that the proposal is waiting for customer acceptance.

Pending Internal Approval

When a proposal is sent for internal approval, the document is awaiting approval. If there were multiple approvers in an approval chain, the document would stay in “Pending Approval” status until all approvers have approved the document, or until someone rejects the document. Typically once the document has entered the approval process, no changes are allowed.

Submit Draft

The Draft phase of the quote has been completed and submitted for further processing.

Submit Draft - Eligible

The Draft phase of the quote has started and is eligible.

Quotes

Check Expiration Date

The offer Expiration Date is checked to see if it exists, does not exist, or if it has already expired.

Set Final Expiration Date

If an Expiration Date exists, Set Final Expiration Date will activate and set the final expiration date for the proposal.

Wait for Expiration

The proposal final expiration date has been set and the system is waiting for the expiration of the proposal.

Wait for Final Expiration

Final expiration has been determined and the system is waiting for that expiration to occur.

Sales Agreements

The following are the statuses for Sales Agreements (SA) that are needed in addition to the negotiation phase statuses.

Enter—Blanket

If the SA did not start from the negotiation phase but began with the fulfillment phase, then the SA will have an Entered status as the first status.

Check Negotiation Exists

Check Negotiation Exists executes a search to ensure that negotiation exists for the sales agreement.

Blanket Submit Draft - Eligible

The blanket draft is eligible for submission.

Blanket Submit Draft

The blanket draft is ready to be submitted.

Calculate Effective Dates

Blanket effective dates are calculated.

Fulfillment

Execute Blanket

The blanket execution is ready.

Wait for Start Date

The effective date of the blanket has not yet passed. The blanket is waiting to become active.

Blanket Active - Wait for Expiration

The sales agreement is active, but the expiration date has not yet passed.

Blanket Active - Wait for Final Expiration

The sales agreement is active, but the final expiration date has not yet passed.

Blanket Active - No End Date

The sales agreement is active with no end date specified.

Blanket - Expired

When an agreement reaches its end-date (Effective End Date Reached), it expires.

Note: The Effective End Date can be extended and the BSA returned to Active status. If you do not want any changes made to an expired BSA, configure a processing constraint accordingly.

Close - Blanket

The sales agreement has expired and is ready to be closed.

Close Blanket - Eligible

The sales agreement is eligible to be closed.

Terminate—Blanket

When a SA is in effect (active) either the customer or the supplier may terminate the SA. Typically there are termination clauses in the contract specifying who can terminate, when, and under what conditions penalties will apply. Draft or approved proposals cannot be terminated.

Awaiting Start Date

The Effectivity start date of the SA has not yet occurred. This status can also occur when Negotiation—Customer Acceptance is met but the start date has not yet occurred. This status is also applicable if the SA is entered from the Fulfillment phase, is at Submit-Draft, and the start date has not yet occurred.

Blanket—Active

After the proposal has been signed by both the parties, and the effective date has been reached, the SA reaches Blanket—Active status when the start date is reached. For a SA that begins in the Negotiation phase, Customer Acceptance must also be reached. Note that for Fulfillment there is no formal acceptance—a signature is not required.

Listing of Seeded COGS Functions