Requirements Planning Preferences

Setup Options > Preferences > Manufacturing > Requirements Planning

This is the default period size applicable to reports and queries. You can override this in any program that requires a period to be entered. Options include: Single day, Multiple days, Weeks and Months.

This is the number of days that you want to be viewed as a period.

This is the first day of the week that will be used as the default for the period (0-Sunday, 1-Monday, 2-Tuesday, 3-Wednesday, 4-Thursday, 5-Friday, 6-Saturday).

This enables you to review jobs that have not yet been started within the Job Review program.

This displays the Stock Codes with Requirements listview when browsing on items in the Supply Chain Review, Job Review, Blanket Purchase Order Review, Purchase Order Review, and Requisition Review programs. Otherwise, the Browse on Stock Codes listview is displayed instead.

This is the number of days before stock can be used in the Requirements Calculation. This is added to the dock-to-stock days for each item and is used when calculating the delivery date of a job linked to a sales order, purchase order or supply chain transfer.

This is the maximum number of decimals (0 to 6) allowed to be held for the quantity per field in the resource structure file.

This is the default number of days in each time bucket for resource planning. The Resource Planning Query program allows you to override this time period at run time.

This creates a journal of all additions, deletions or changes made to forecasts.

This creates a journal of all additions, deletions, or changes made to build schedules.

This must be included if you are catering for expired lots (this decreases stock on hand). If sales orders are not included, then the available quantity is subtracted from safety stock to establish the demand quantity. If included together with sales orders, then the stock on hand is subtracted from safety stock to establish the demand quantity. If neither stock on hand nor sales orders are included, then safety stock is the demand quantity.

This creates demand in the prior period, which could result in the creation of a purchase order or a job (the demand created is reflected in the pegging file). Safety stock is included in the calculation used to establish any oversupply/shortage: (qty on hand + supply - demand - safety stock).

You can exclude/include purchase orders or purchase order lines from the MRP calculation when adding or maintaining purchase orders using the Purchase Order Entry program. Requisition lines can be excluded from the calculation using the Requisition Entry Maintenance program.

Select this to include confirmed jobs in the calculation of requirements.

Select this to include unconfirmed jobs in the calculation of requirements.

A job is placed on hold often because of a problem with the finished item, or the customer has canceled the order. So, you might want to exclude the job from the calculation to ensure that any materials attached are not incorrectly ordered. The Requirements Calculation, Forward Finite Scheduling and MRP Low Level Code Validation programs will check whether to exclude/include a job on hold. Sub jobs attached to a job on hold are also excluded, even if the sub jobs themselves are not on hold.

Forecasts are ignored if the Build schedule option is enabled.

Orders for MPS items are ignored if build schedules are included.

If orders are not included, then the available qty is subtracted from safety stock to establish the demand qty.

If orders are included (as well as stock on hand) then stock on hand is subtracted from safety stock to establish the demand qty. If neither is included, then safety stock is the demand qty.

If the Reduce quantity on hand by allocated option is enabled, then the on hand qty is reduced by the qty allocated to orders.

A default offer must be selected against the quotation for it to be included in MRP. Otherwise MRP does not generate demand for the items on the quotation.

This includes the build schedule in the calculation of requirements. This ignores forecasts and orders for MPS items as MPS only supports a single level of dependent demand (i.e. demand in the form of job allocations). The only demand seen for an MPS item is the build schedule.

This includes forward orders in the calculation of requirements. The Sales orders option must be enabled.

This includes orders in suspense in the calculation of requirements. The Sales orders option must be enabled.

This includes supply chain transfer orders in the calculation of requirements.

The Sales orders and Goods in transit options must be enabled and the Consolidate selected warehouses option must not be enabled.

The Inventory option: Full goods in transit transfers facility must be enabled (this creates suggested SCT's for items which are transfer-supplied).

This includes goods in transit records in the calculation of requirements. If including supply chain transfer orders, ensure that the Inventory option: Full goods in transit transfers facility is selected.

This applies forecasts only and sales orders only to determine the gross requirement of non-MPS items. If you only select this option then the gross requirement for all other non-MPS items is determined by applying rule A (sum of forecasts and sales orders). If you don't select this option then gross requirement rule A is applied to all non-MPS items assigned rule I and S.

This applies the highest of forecasts and sales orders and cumulative highest of forecasts and sales orders to determine the gross requirement of non-MPS items. If you only select this option, then the gross requirement for all other non-MPS items is determined by applying rule A (sum of forecasts and sales orders). If you don't select this option, then gross requirement rule A is applied to all non-MPS items assigned rule H and C.

This determines the period to which sales orders and forecasts are allotted if you selected to apply gross requirement rules H and C.

This uses only sales orders within the demand time fence, regardless of the gross requirement rule assigned to the item (i.e. forecasts within the demand time fence are excluded from the calculation of requirements).

When a quantity on hand for an item drops below its minimum level, MRP tries to replenish the order immediately, which may result in the unnecessary expediting of orders. This option enables you to indicate a time fence during which MRP will not raise demand for safety stock. MRP applies the rule you select and inserts safety stock demand at the calculation run date plus the time fence selected. Options include: None, Demand time fence, Manufacturing time fence and Planning time fence.

This overrides the buying rules held against each stock code when running the Requirements Calculation.

This uses the buying rule assigned to the stock item when running the Requirements Calculation.

This override only the buying rules held against MPS items when running the Requirements Calculation.

If you elected to schedule jobs and purchase orders according to demand, then this schedules a specific supply (existing or suggested job, sub job, purchase order or requisition) to the specific demand to which it is linked (e.g. supply for a job linked to a sales order will be scheduled according to the sales order). Otherwise the Requirements Calculation program links the supply of an item to the first demand for the item, according to the demand dates.

This includes all stock codes and warehouses in the requirements file, regardless of whether there is demand/supply. This enables you to produce reports listing all stock code/warehouse combinations that do not have demand or supply. Selecting this option may considerably increase the size of both the requirements file and the reports generated from this file.

This option cannot be deselected if you have enabled the Consolidate selected warehouses option.

If you are not including sales orders in the Requirements Calculation program, then this reduces the quantity on hand by the quantity allocated to sales orders in the warehouse file.

This decreases stock on hand for expired lots when generating material requirements in the Requirements Calculation program. You will also need to enable the Stock on hand option at the Include in requirements calculation field, because the suggestions made by the system vary depending on your selections. If this field is disabled, then stock on hand for expired lots is included as stock on hand in the Requirements Calculation program.

This indicates that additional requisition users can be included in the Requirements Calculation when calculating supply for requisitions according to requisition users. By default, only requisitions created by the requisition users QOT and MRP are recognized as supplies by the Requirements Calculation program.

This prevents the Requirements Calculation program from raising suggested supplies (i.e. jobs, requisitions or SCTs) for non-current revision/releases of ECC-controlled items. In addition, archived BOM structures are ignored when performing the low level calculation, except for Phantom parts (these are always included in the low level code calculation, even when archived).

This allows goods in transit to be re-scheduled if you are scheduling supply according to demand and there is existing goods in transit. Otherwise, existing goods in transit can be moved out to fill a future requirement and the demand created by this action can be filled either by suggesting a new supply chain transfer and/or moving existing supply chain transfers in.

This uses the date on which the MRP calculation is run (instead of the job start date) when checking structure off dates. If the suggested job start date is prior to the calculation date, then instead of checking that against the structure on/off dates, the calculation date is checked. This means that only structures that are current at the time of the calculation are used.

Select this to take account of quotes that are likely to become firm orders, by including them in the calculation of material requirements. In this way you could start purchasing raw materials with long lead times in anticipation of the order.

This assigns a higher priority to the start date of a job than the job priority held against the job, when using forward finite scheduling.

This assigns a higher priority to the job priority held against a job than the start date of a job, when using forward finite scheduling.

This assigns a higher priority to suggested jobs than quotations, when using forward finite scheduling.

This assigns a higher priority to quotations than suggested jobs, when using forward finite scheduling.

This indicates the maximum queue time allowed when calculating forward finite capacity, setting a limit on the insertion of operations into the capacity profile for each work center.

This indicates the warehouses you want to include in the Requirements Calculation. Options include All, Range, List and By warehouse. The By warehouse option includes warehouses according to the Include warehouse in requirements planning calculation option defined against the warehouse itself.

This consolidates the information of all the selected warehouses using warehouse --. You must specify a Component warehouse to use against each warehouse (for by the consolidation routine in the Requirements Calculation program). If left blank, then MRP cannot raise suggested supply. Don't select this if you want the Requirements Calculation program to include SCT orders and/or blanket purchase orders, or if you are using bought out details (e.g. supplier, lead time and dock to stock) at warehouse level.

If this option is enabled, then you won't be able to deselect the Include all stock codes in requirements option.

By default, only requisitions created by the requisition users QOT and MRP are recognized as supplies by the Requirements Calculation program.

This includes all requisition users in the MRP calculation.

This includes a range of requisition users in the MRP calculation.

This includes requisitions from requisition users only if the Include user in MRP calculation option is enabled against the user code.

Requisitions for requisition users QOT and MRP are also included/excluded according to the selection you make here.

This includes requisitions originated by the requisition user.

This includes requisitions currently held by the requisition user, regardless of the user who created the requisition. This includes requisitions created by the current holder and which have not yet been routed.

This depletes forecasts according to your selections.

This indicates the time frame into the future according to which you want to limit forecast depletion based on the ship date passed. Options include: Days, Demand time fence, Planning time fence, Planning horizon and Use forecast calendar.

This indicates the number of days to which you want to limit forecast depletion if you chose Days at the Forecast depletion period type option.

These options enable you to control forecast depletion into the past.

This depletes past due forecasts from the earliest active forecast with a quantity available.

This depletes past due forecasts from the ship date on the order.

This depletes past due forecasts up to a number of days prior to the ship date on the order. The depletion start date is moved back by the number of days specified.

If you chose Number of days prior to ship date at the Allow past due forecasts to be depleted option, then this is the number of days prior to the ship date used to calculate the depletion start date. The depletion start date for the forecast is calculated by subtracting the number of days defined here from the ship date on the order (e.g. if you enter 15, then depletion starts 15 days earlier than the ship date for a sale or credit note and any forecast located within 15 days is depleted).

This depletes forecasts relating to the customer against the sales order followed by forecasts where the customer is spaces. Forecasts with a different customer are excluded from depletion.

This only applies to stocked items. It works together with the Use forecast calendar choice against the Forecast depletion period type option and enables forecast depletion to take place beyond the current forecast calendar period end date. Otherwise depletion only takes place up to the end of the depletion date calculated (i.e. the current forecast calendar period end date is the end point of depletion).

This indicates the items for which you do not want to deplete forecasts. MPS items are always included in forecast depletion. You can only exclude MPS items by setting them to a gross requirements rule of A or I and then select to exclude them from depletion using the options below.

This excludes all MPS items with a gross requirements rule of A - Sum of forecasts & sales orders from forecast depletion. This only applies to stocked items. It does not apply to non-MPS items.

This excludes all MPS items with a gross requirements rule of I - Forecasts only from forecast depletion. This option only applies to stocked items. It does not apply to non-MPS items.

This excludes non-Master Production Schedule items from forecast depletion. This only applies to stocked items.

This excludes non-stocked items from forecast depletion. Depletion for non-stocked items only occurs when the item is invoiced, after the Deplete forecasts option is enabled and you are not excluding non-stocked items.