Start Backlog Planning
Use the Start Backlog Planning scheduled process to replan the fulfillment of demands in the order backlog. Each plan run reads in the latest supply and demand data from the collected data.
The Start Backlog Planning scheduled process can be used to schedule the Backlog
Management plan run at predefined time, or can be launched on demand. You can either
plan the entire backlog or plan only orders for a specific Organization, Category, Item,
or, Customer. The plan uses a default demand priority rule to prioritize demands, or
another rule can be specified to prioritize demands in the Demand Priority Rule
attribute. You can run the Start Backlog Planning scheduled process multiple times in
parallel for different subsets of the plan data. This approach can improve backlog
management rescheduling performance by rescheduling more order lines in a given period
of time.
Note: Subsequent runs of the Start Backlog Planning process will run in
parallel only if there are no shared components with other runs of the scheduled
process that are still in progress. Otherwise, the subsequent runs of the scheduled
process will error out.
When to Use
The Start Backlog Planning scheduled process should be scheduled to run typically once a day, preferably after Collections.
Backlog Management is designed to allocate the latest supply across the entire order backlog. Launch the Start Backlog Planning process up to once to a few times a day for all demands. When you launch Backlog Planning for a subset of demands (a specific Org or Item), do so only if all the demands for the subset don't share supply with any other demands.
Privileges Required
- Create Backlog Plan (MSC_CREATE_BACKLOG_PLAN_PRIV)
Specifications
Review the following before setting up this scheduled process:
| Specification | Description |
|---|---|
| Job Type | Ad hoc job Scheduled |
| Frequency | Once daily or after each Collection run, to replan the fulfillment of demands in backlog with latest data from the execution system. If there is a high volume, then schedule Collections as well as this job to run at off-peak intervals. |
| Time of Day | After work hours at 00:00:00 a.m. |
| Duration | Typically few minutes to a few hours. You need to ensure that the Start Backlog Planning scheduled process completes before launching Run Plan from Backlog Analysis screen. Duration can vary based on the parameters selected and the data volumes. |
Parameters
| Parameter | Optional or Required | Description | Parameter Values | Special Combinations Required | Notes |
|---|---|---|---|---|---|
| Demand Priority Rule | Optional | Specify the demand priority rule. If you don't specify a rule, the process uses the default demand priority rule that's defined on the Manage Backlog Planning Options page. | Drop-down list to select one demand priority rule | N/A | N/A |
| Source System | Required | Select the source system for which backlog plan is run. | Drop-down list to select a source system | You can select more than one organization from the same source system. | N/A |
| Organizations | Optional | Select this parameter to replan the backlog related to the selected ship-from organization in Backlog Management. | Edit icon to select one or more organizations | You can select more than one organization from the same source system. | N/A |
| Category | Optional | Select this parameter to replan backlog related to all items in a category. | Drop-down list to select a category | If you don't specify a category, then your entire backlog for all categories will be planned based on other parameters values. | N/A |
| Item | Optional | Select this parameter to replan backlog related to an item. | Drop-down list to select an item | If you don't specify an item, then your entire backlog for all items will be planned based on other parameters values. | N/A |
| Customer | Optional | Select this parameter to replan backlog related to customer. | Drop-down list to select a customer | If you don't specify a customer, then your entire backlog for all customers will be planned based on other parameters values. | N/A |
| Generate replay data sets | Optional | Select this parameter to specify whether to generate replay data sets. Enable this setting when you need to provide Oracle Support with detailed plan run information. You can download this as a compressed file from the process log of the Start Filtered Backlog Planning child process. | Check box | N/A | N/A |
Troubleshooting Information
- You can view the status of Start Backlog Planning in the Scheduled Processes work area.
- The validation errors and warning messages that prevented the Start Backlog Planning process are displayed in the error log.
- Interactive warning validations aren't available.
- When the program is submitted, you can resubmit or cancel process as provided by the Scheduled Processes work area.
- In case this job is running for a long time, it can be canceled (or force canceled). Provide the log file and scheduled process ID information to support.
- This job considers plan options provided in the Backlog Options UI, for instance Plan Horizon and Past Due Horizon. Reduce the horizon values in case this process is running too long.
- You can run this job for multiple organizations of the same source system in one run.
- Here are few things to check if the job performance is slower than expected or
not finishing:
- Verify that this is not a generic issue with all scheduled processes.
- Verify that the selected parameters haven't changed since the last run. For example, in the last run only one organization was selected whereas, in the current run you haven't selected any organization. In such case, the job will run for all organizations in the instance hence it will take longer time to complete.
- Note that all the orders that are to be planned must be collected.
- When demands are planned using the Start Backlog Planning scheduled process, the planning results are automatically saved to the demands.
- The Start Backlog Planning scheduled process is launched daily or intermittently to plan the entire backlog, or a large subset of the backlog. The scheduled process considers the latest collected supply and demand data.
- The Start Backlog Planning scheduled process can also be called via REST. For more details see the REST guide.
- If the job fails, try to pinpoint the specific parameter that caused the failure by reviewing the error logs. If the reason for failure is not clear from the logs, review details in the diagnostic logs with the help of product support.
- For debugging purposes, you can run the Extract Backlog Planning Run Data process with the scheduled process identifier as a parameter to extract data files. This process is supported only for backlog planning runs that are launched through the Start Backlog Planning scheduled process.
- Run the backlog plan in parallel only from Scheduled Processes work area only, and not from the Backlog Analysis page in the Backlog Management work area.