Backlog Planning Options

Before you run plans in the Backlog Management work area, use the Manage Backlog Planning Options task to configure key backlog planning attributes. Your configuration settings serve as default specifications for processes like supply sourcing and reallocation. Here's the list of options:

Planning Horizon in Days: This is a duration measured from the horizon start date. Demands with requested dates within this horizon only are planned. So if the horizon start date is today and you specify 100 as the planning horizon value, then the planning process will plan orders with requested dates that fall within the next hundred days only.

The default maximum limit for Planning horizon is set to 366 days. If there is a business need to set the Planning Horizon in Days more than 366 and upto 731 days, then contact the administrator to create a profile option and profile value.

Horizon Start Date: It's the date from which the planning horizon is calculated. The default start date is the present day. If you change it to a future date, then the horizon will be calculated from that day.

Assignment Set Name: The name of the assignment set that contains the sourcing rules and bills of distribution used to implement your supply chain network. If your enterprise uses Oracle Global Order Promising, the assignment set up for order promising should be used for backlog management. If you do change the assignment set, you must run the Import Supply Chain Data for Backlog Management scheduled process.

Demand Priority Rule: This is the rule that the backlog planning process uses to prioritize orders for fulfillment. The rule you specify is the default demand priority rule, which means that this rule is always used unless you specify another one before taking plan run actions.

Past-Due Supply and Demand Considered in Days: This is a duration measured backward from the horizon start date. When a demand's scheduled date or a supply's expected date falls prior to the horizon start date, this demand or supply is termed past-due. The duration you specify determines how many days prior to the horizon start date a past-due demand or supply is valid for to be considered by the backlog planning process. You can override the value specified here while defining a backlog planning rule.

Demand Fulfillment Lead Time in Days: The number of days from the order creation date within which your customer, by contract, expects the order's fulfillment. This value is used to calculate the fulfillment lead time date. So if you specify 5 as the value, and the order creation date is 1/20/2020, then the fulfillment lead time date would be 1/25/2020, assuming that your requested date is between 1/20 and 1/25. If your requested date is later than your fulfillment lead time date, say 3/25/2020, then the fulfillment lead time date is considered to be the same as your the requested date.

Supply Plans: The existing supply plans in Oracle Supply Planning that you want to source supply data from, to get the most accurate supply picture. You can select multiple supply plans. If you don't select a supply plan, the backlog planning process uses whatever supply data is available from the collection process. To know more, refer to the Planning Processes chapter.

Category Set: This is a group of item categories used by the backlog planning process while assigning backlog planning rules by category. The default value is GOP_Catalog. You can't edit this value on this page because it's derived from the profile MSC_SRC_ASSIGNMENT_CATALOG in Oracle Global Order Promising. Whenever the category set value changes, you must run the Import Supply Chain Data for Backlog Management scheduled process.

Allocation Attributes: This is a parent-child hierarchy of attribute levels used for supply allocation. You select an allocation attribute at each level, always starting from the first tier. You can configure up to three attribute levels. Your attribute options are defined in and sourced from the Planning Attributes UI.