Update Planning Clusters

Use the Update Planning Clusters scheduled process to update the locations within the planning clusters.

When to Use

This process triggers automatically after a collection run if you have selected any organization, subinventory, or geography entity. It updates the locations associated with the clusters if you've made any changes to regions, zones, or locations mappings. It also ensures that the association between locations and planning clusters remains up to date, especially when the cluster is defined using regions or zones.

Privileges Required

• Run Plan with Snapshot (MSC_RUN_PLAN_WITH_SNAPSHOT_PRIV)

Specifications

Review these specifications before setting up this scheduled process:

Specification	Description
Job Type	Scheduled
Frequency	Triggers automatically after a collection run. Schedule the collection run on an as-needed basis.
Time of Day	After working hours.
Duration	Duration varies based on the total number of entities that you're collecting and the total number of clusters that you maintain.
Compatibility	There should be only one instance of the job running at any time, and there’s no current functional need to run multiple instances of this process simultaneously.

Parameters

There are no parameters associated with this scheduled process.

Troubleshooting Information

• You can view the status of the Update Planning Clusters scheduled process on the Scheduled Processes work area.
• The validation errors and warning messages that prevented the process from completing display in the error log.
• Interactive warning validations are not performed.
• After you submit the scheduled process, you can perform any of these tasks in the Scheduled Processes work area:
  • Resubmit it
  • Put it on hold
  • Cancel the process
  • Release the process
• After the process successfully completes, you can view the locations associated with the planning clusters by clicking the Assign Location Priority tab on the Manage Planning Clusters page.
• If the job fails:
  • Review the error messages in the log file.
  • If the reason for the failure isn’t clear from the logs, review the diagnostic logs and contact product support for more help.