Overview of Orchestration

The orchestration process publishes the order forecasts to the suppliers through Oracle Supplier Portal, Business to Business (B2B) messaging using Oracle Collaboration Messaging Framework, or web services.

Note: The Item Forecast orchestration processes are grouped by collaboration plan and whether the plan is managed or B2B Only.

The orchestration process will be active until it expires based on the planning cycle end date or B2B Only expiration period. The following predefined orchestration processes are supported:

• Vcs_SupplyPlanning_Managed: This process is used for supply planning managed forecast collaboration. The process does the following:

  1. The forecast is published to Supplier Portal and sent to Collaboration Messaging Framework if applicable.

  2. When a commit is received, commit exceptions are run and commit decomposition initiated.

  3. When the planning cycle expires, all the records are marked with the Expired status and the Is_CURRENT_FLAG is set to N.

  This figure provides an overview of the Vcs_SupplyPlanning_Managed process.

  

• Vcs_SupplyPlanning_Unmanaged: This process is used for Supply Chain Collaboration supply planning B2B Only forecast collaboration. The process does the following:

  1. The forecast is sent to Collaboration Messaging Framework. If the supplier site isn't enabled for Collaboration Messaging Framework, an error event will be generated.

  2. When a commit is received, commit decomposition initiated.

  3. When the planning cycle expires, all the records are marked with the Expired status and the Is_CURRENT_FLAG is set to N. These records are deleted during the next decomposition cycle.

  This figure provides an overview of the Vcs_SupplyPlanning_Unmanaged process.