Run Value Chain Planning After Upgrade Steps

Use the Run Value Chain Planning After Upgrade Steps scheduled process to upgrade all supply chain planning data when upgrading from one release of Oracle Fusion to a newer release in order to ensure compatibility and performance.

While this process is running, you shouldn't run any other planning process. Also, you won't be able to run or view plans during the period that this process is running.

When to Use

During specific upgrades you may need to run this process but it isn't required for all upgrades. Check the release notes documentation of the specific release. Use this process when you want to perform all of the Supply Chain Planning data upgrade steps that are needed to ensure version compatibility after upgrading from one release of Oracle Fusion to another release.

Privileges Required

  • Perform Order Orchestration And Planning Data Collection (MSP_PERFORM_ORDER_ORCHESTRATION_AND_PLANNING_DATA_COLLECTION_PRIV)

Specifications

Review the following before setting up this scheduled process:

Specification Description
Job Type Ad hoc job. Can be scheduled or included in a job set based on requirements.
Frequency As required.
Time of Day After work hours is preferred, but can be submitted any time based on your requirements. It’s recommended to not run the process while users are working on the plan.
Duration Typically takes a few minutes. However, based on data and other conditions, the time may vary.
Compatibility There should only be one instance of the job running at any one time.

Parameters

No parameters are required when you use the Run Value Chain Planning After Upgrade Steps scheduled process.

Troubleshooting Information

  • You can view the status of the two jobs in the Scheduled Processes work area.
  • When the program is submitted, you can Resubmit, Put on Hold, Cancel Process, Release Process as provided by the Scheduled Processes work area.
  • For a long-running process that appears to be stuck and not finishing, click on the Cancel Process button and then re-submit the process.
  • If the job fails:
    • Review the error messages in the log file.
    • If the reason for failure isn’t clear from the logs, as a next step, review finer details in the diagnostic logs with the help of product support.