Guidelines for Setting Up Orchestration Processes

Create a copy of a predefined orchestration process instead of creating a new one. Using a copy of a predefined orchestration process and copying other predefined objects will help reduce your development and maintenance effort.

Predefined Orchestration Processes

Predefined Orchestration Process	Includes These Tasks
ShipOrderGenericProcess	Schedule Reservation Shipment Invoice
ReturnOrderGenericProcess	Return Receipt Invoice
OrderFulfillmentGenericProcess	Schedule Conditional. Starts the branch. Request Supply. Starts the back-to-back branch. Pause. Create Back to Back Shipment Request. Wait for Back to Back Shipment Request. Create Purchase Request. Starts the drop ship branch. Wait for Procurement. Create Reservation. Starts the warehouse shipment branch. Create Shipment Request. Wait for Shipment Advice. Merge. Ends the branch. Invoice. Wait for Invoice. Use it for various fulfillment requirements, such as back-to-back shipments, drop ship, and so on.

Note

• Use a predefined orchestration process as your first course of action.

  Create a copy of a predefined orchestration process only if the predefined orchestration process doesn't meet your needs.

  Don't modify a predefined orchestration process. Instead, create a copy of it, then modify the copy.

• Create a new orchestration process only if modifying the copy of a predefined one doesn't meet your needs.

Do the Required Set Ups

Do these set ups in the same order that the table lists them

Description	Get Details
Set up the task types that arrange fulfillment tasks in groups. Each task type references services that communicate with a type of fulfillment system. For example, a billing system.	Use Your Own Task Type to Apply Holds
Set up the orchestration process.	Set Up Orchestration Processes
Set up business rules that determine how the orchestration process handles changes to sales orders.	How Order Management Processes Change Orders
Set up the schedule that uses process planning to display the completion date of each task and the orchestration process.	Guidelines for Setting Up Orchestration Process Steps
Set up jeopardy threshold and jeopardy priority to assess the level of risk that's associated with the delay of an orchestration process task as low, medium, or high.	Jeopardy Threshold
Set up the status and status conditions for the sales order, task, orchestration process, fulfillment line, or order line.	Orchestration Process Status
Deploy your orchestration process.	Deploy Orchestration Processes

Plan Your Orchestration Process

Orchestration planning is the process of orchestrating and planning fulfillment for your sales order. For example, planning dates, planning shipments, and so on.

Specify how Order Management plans each orchestration process.

• Set and help meet the completion date for each orchestration process step and task in an orchestration process.

• Specify how to use the transformation rules that an orchestration process references to transform each source order, including planning for each step after it receives a source order from an order capture system.

• Use the Enable Orchestration Process Planning and Calculate Jeopardy parameter. For details, see Manage Order Management Parameters.

Replan Your Orchestration Process

Replanning is the process of updating the orchestration plan for the sales order to accommodate a change that happens to the sales order or in the fulfillment environment. For example, when your customer requests to change the quantity of a sales order you already submitted to fulfillment.

Specify how Order Management replans each orchestration process.

• Replan completion dates when a change happens to the sales order at any point in the orchestration process.

• Replan immediately after each orchestration process step finishes.

• Replan according to an event, such as every time the orchestration process receives an update from your order capture system. To control replanning, use the Plan Orchestration Processes scheduled process to schedule an update at regular intervals according to the frequency that your deployment requires.

  For example, if your orchestration process requires planning data that's current, then set up the scheduled process to run the orchestration process and update the planning data one time each day. See an example that uses a scheduled process. For details, see Fix Errors in More Than One Sales Order.

Enable the Replan Instantly option when you set up your orchestration process. It replans the orchestration process immediately after the process finishes the orchestration process step, then displays the revised order data according to the results of the replanning.

• Use Replan Instantly only for high priority sales orders, or with sales orders that include a jeopardy threshold of less than one day.

• For performance reasons, don't use Replan Instantly with an orchestration process step that's long or complex.

• If you don't enable Replan Instantly, then Order Management updates planning data only during the scheduled replanning.

What if I Need to Apply New Processing to Orders I Already Imported?

You must cancel the orders you already imported, modify the orchestration process definition or create a new one, then reimport your sales orders.

Migrate

If you use your implementation project to migrate an orchestration process instance from a development environment to a production environment, then don't modify the process name in either environment. Modifying the name might prevent Order Management from updating references to other data in the orchestration process. For details about using an implementation project, see Guidelines for Setting Up Order-to-Cash.

Copy and Duplicate

If you need to copy or duplicate an orchestration process, then make sure you validate it and remove all validation errors before you create the copy or duplicate. If you don't remove validation errors on the original process, then you might encounter a problem when you attempt to release the copy or duplicate. The Orchestration Process Definition page might not display any errors for the copy or duplicate but the status remains as New and doesn't update to Released when you attempt to release it.

Use the DOO_ScheduleShipInvoice Orchestration Process

Use the predefined DOO_ScheduleShipInvoice orchestration process to process a large volume of sales orders.

DOO_ScheduleShipInvoice is similar to DOO_OrderFulfillmentGenericProcess, except DOO_ScheduleShipInvoice only has the Scheduling, Shipping, and Invoice tasks.

You can modify DOO_ScheduleShipInvoice to integrate with your own fulfillment system. For example, if you need to add your own pause task or a custom task to integrate with your own fulfillment system, then you must include the statuses that your fulfillment system needs for the pause task and for the custom task.

One way to do this is to examine the orchestration process classes and see what statuses they use.

1. Go to the Setup and Maintenance work area, then search for and open the Manage Status Values task.
2. Click Orchestration Process Classes, then find a class that works for you. Make a note of the statuses that the class uses.
3. Add the statuses that you noted in the class to your task.

For details, see:

• Use REST API with FBDI to Import Large Volumes of Sales Orders
• Use REST API to Import Large Volumes of Sales Orders
• Use Order Management Extensions to Import Large Volumes of Sales Orders