Previous	Next		Contents	Index	Navigation	Glossary	Library

   Include Sales Orders:

• To include sales orders in the load, select:

All sales orders: Include sales orders past due, up to the cutoff date.

Sales orders from start date forward: Include sales orders up to the cutoff date.

   Sales Order Demand Class:

• To limit the sales orders loaded to a particular demand class, select a demand class. Only sales order items from this demand class are loaded.

   Demand Time Fence:

• To limit the source forecast with a demand time fence, select:

Load forecast outside demand time fence only: Ignore forecast entries on and within the demand time fence. When you include sales orders and consume forecasts, this option loads sales orders within the demand time fence, and the greater of sales orders and forecasts outside the demand time fence.

Load orders within and forecast outside demand time fence: Load only sales orders on and within the demand time fence, and only forecast entries outside the demand time fence.

Ignore demand time fence: Ignore the demand time fence. When you include sales orders and consume forecasts, this option loads all forecast demand across the planning horizon.

Note: Use the include sales orders option to also load sales order demand across the planning horizon.

   Overwrite:

• To overwrite the existing entries of the destination schedule, select:

All entries: Erase all existing master schedule entries associated with the master schedule name and load new entries.

For example, if you load master schedules MS-A and MS-B into master schedule MS-C the first time and then load master schedule MS-B into master schedule MS-C the second time, the result is that MS-C contains master schedules from the second load of MS-B.

Same source only: Erase only the entries with a source that has been previously loaded into the master schedule. This allows you to update master schedule information with the latest picture of the sales orders, updated forecasts or master schedule information.

For example, if you load master schedules MS-A and MS-B into master schedule MS-C the first time and then load master schedule MS-B into master schedule MS-C the second time, the result is that MS-C contains master schedules from the first load of MS-A and the second load of MS-B.

Or, if you load sales orders into master schedule MS-C the first time and then load sales orders again using this option. Master schedule MS-C reflects all the current sales orders including those that were booked in the interim of the first and second loads.

• To add new entries to the destination schedule, select:

No: This loads new entries, but does not erase existing master schedule entries.

   Start Date

• Select the start date of your schedule.

If you specify a start date Oracle Master Scheduling/MRP and Supply Chain Planning first selects the planning BOM entries that start outside the start date, then explodes those entries. When you load a forecast into an MDS the master schedule load will load all the forecast entries after the start date minus backward update consumption days for the forecast set. The start date does not apply to exploded entries that fall before start date due lead time offsetting from planning BOM entries that start after the forecast load start date.

   Cutoff Date

• Select the cutoff date of your schedule.

   Explode

• Select Yes to explode the schedule entries, down to the MPS explosion level. See MPS Explosion Level.

   Quantity Type:

• To load forecast quantities, select:

Current: This loads the original forecast quantity minus any consumption quantities. When you choose this option, you cannot choose to consume the forecast, since the forecast quantities have already subtracted sales order demand.

Original: This loads the forecast without any consumption. When you choose this option, you should choose to consume the forecast if you intend to load the master schedule using forecasts and sales orders. Consuming the original forecast ensures that demand is not overstated.

Attention: To insure a consistent picture of demand, you should load sales orders and forecasts during the same load process, rather then loading them in two separate steps. If you load them separately, and you create sales orders in the interim, you could overstate or understate demand. For example, suppose you define a forecast entry for 100 on 01-FEB and load it into the master schedule. You create a sales order for 30 on 01-FEB. The forecast is consumed to 70, but the master schedule remains at 100. You then load sales orders as a separate step. The total demand for 01-FEB becomes 130, which overstates the actual and forecasted demand. If you launched a single process instead of two, you would see a forecast of 100 and no sales order demand, or a forecast of 70 and a sales order for 30. Either way, the correct demand of 100 results

   Consume

• Select Yes to consume the forecast. See Forecast Consumption.

   Modification Percent

• Enter a percent by which to multiple the schedule entries.

   Carry Forward Days

• Enter a number of workdays to move the schedule forward in time. To move the schedule backward, enter a negative number.

   Backward Consumption Days

• Enter a number of workdays the consumption process will move backward when looking for a forecast quantity to consume. See: Backward and Forward Consumption Days.

   Outlier Percent

• Enter the maximum percent of the original forecast that a sales order can consume. See: Outlier Update Percent.