Deviations in Orchestrating Supply

Supply Chain Orchestration tracks transactions during the supply lifecycle of each buy, transfer, and make flow. Use it to view the supply request and supply status, including exceptions.

A deviation is a supply line that deviates from the promised delivery date or from the promised item quantity.

Change or delay might cause a deviation. Here are some example changes.

• Someone cancels the purchase order, work order, or transfer order.

• Quality assurance rejects an item because of a quality problem.

• A supplier can't meet the requested quantity or scheduled date.

• Someone reassigns a reserved supply.

You can manage change that happens in the supply.

• Create and manage alternate supply sources that meet demand.

• Split a supply tracking line into more than one tracking line. Create a parallel flow in the orchestration process for each split line.

Assume you receive a tracking line for a buy request that includes 100 items.

• Orchestration sends a buy request for a quantity of 100 to your procurement system.

• Procurement creates a requisition and a purchase order that includes three schedules. One schedule with a quantity of 50, another 30, and another 20.

• Procurement sends the purchase order to orchestration.

• Orchestration tracks each schedule independently, so it splits the tracking line that contains a quantity of 100 into three tracking lines. One with a quantity of 50, another 30, and another 20. It uses a separate orchestration process instance to track each schedule.

• You use the Supply Overview work area to manage the supply tracking lines.

• You can also manage exceptions for each tracking line.