You use this program to define the various setup options applicable to the Requirements Planning module.
For this module to run efficiently, we recommend that you select the options you require before processing any transactions. However, most of the options can be changed later, if necessary.
Field | Description | ||||
---|---|---|---|---|---|
Default period size for reports and queries |
|
||||
Single day |
Select this for the default period size applicable to reports and queries to be a single day. |
||||
Multiple days |
Select this for the default period size applicable to reports and queries to be multiple days. |
||||
Number of days |
Indicate the number of days that you want to be viewed as a period. |
||||
Weeks |
Select this for the default period size applicable to reports and queries to default to weeks. |
||||
First day of week |
Indicate the first day of the week to use as the default for the period. |
||||
Months |
Select this for the period size of reports and queries to default to months. |
||||
Default pricing method for suggested p/o review | |||||
Current inventory cost price |
Select this to use the current inventory cost price as the default pricing method when reviewing suggested purchase orders within the Purchase Order Review program. |
||||
Last price paid |
Select this to use the last price paid as the default pricing method when reviewing suggested purchase orders within the Purchase Order Review program. |
||||
Purchase price |
Select this to use the purchase price as the default pricing method when reviewing suggested purchase orders within the Purchase Order Review program. |
||||
General options | |||||
Include confirmed jobs in job review |
Select this to be able to review confirmed jobs (which have not yet been started) within the Job Review program. |
||||
Requirements planning load levelling required |
Select this option to include the final phase of the requirements planning calculation. If this option is not selected, then the dynamic capacity profile is not built in the snapshot directory and load levelling is unavailable within Requirements Planning. |
||||
Browse stock codes with requirements | Select this to display the Stock Codes with Requirements
listview when browsing on Stock codes in
the following programs: If you do not select this option, then the Browse on Stock Codes listview is displayed instead. |
||||
Number of days after stock arrived that it can be used |
This indicates the number of days before stock can be used in the Requirements Calculation. The number of days entered here is added to the dock-to-stock days for each item. It is used when calculating the delivery date of a job linked to a sales order, purchase order or SCT (Supply Chain Transfer).
|
Field | Description | ||||
---|---|---|---|---|---|
Resource planning | |||||
Number of decimals in resource quantity per |
Indicate the maximum number of decimals (0 to 6) required to be held for the quantity per field in the resource structure file. |
||||
Default time period length (days) |
Indicate the default number of days in each time bucket for resource planning. The Resource Planning Query allows you to override this time period at run time. |
||||
Forecast planning | |||||
Frequency allowance (days) |
This is added to the longest cumulative manufacturing time to calculate the manufacturing time fence. |
||||
Visibility factor (days) |
This indicates the number of days into the future that you want to look for forecasting purposes. It is the number of days from the planning time fence that general planning will take place. The visibility factor (in days) added to the planning time fence gives the planning horizon and any date thereafter is not normally subject to any build schedules.
|
||||
Forecast amendment journals required |
Select this to create a journal of all additions, deletions or changes made to forecasts (see Forecast Amendment Journal). |
||||
Build schedule | |||||
Amendment journals required |
Enable this to create a journal of all additions, deletions, or changes made to build schedules (see Build Schedule Amendment Journal). |
Field | Description | ||||
---|---|---|---|---|---|
Include in requirements calculation | |||||
Stock on hand |
Select this to include stock on hand in the calculation of requirements. 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.
|
||||
Safety stock |
Select this for the safety stock quantity held against a warehouse to create a demand in the prior period. This in turn could result in the creation of a purchase order or a job. The demand created is reflected in the pegging file. Safety stock will be included in the calculation used to establish any oversupply/shortage: (qty on hand + supply - demand - safety stock) |
||||
Purchase orders |
Select this to include purchase orders in the calculation of requirements. |
||||
Confirmed jobs |
Select this to include confirmed jobs in the calculation of requirements. |
||||
Unconfirmed jobs |
Select this to include unconfirmed jobs in the calculation of requirements. |
||||
Jobs on hold |
Select this to include jobs on hold in the calculation of requirements. This applies to confirmed and unconfirmed jobs. When a job is placed on hold it is often because of a problem with the finished product, or the customer has cancelled the sales order for it. For this reason, you may want to include/exclude the job from the Requirements Calculation to ensure that any materials attached are not incorrectly ordered.
|
||||
Forecasts |
Select this to include forecasts in the calculation of requirements.
|
||||
Sales orders |
Select this to include sales orders in the calculation of requirements. If sales orders are not included, then the available quantity is subtracted from safety stock to establish the demand quantity. If included together with stock on hand, then the stock on hand is subtracted from safety stock to establish the demand quantity. If neither sales orders nor stock on hand are included, then safety stock is the demand quantity.
|
||||
Quotations |
Select this to include quotations in the calculation of requirements.
|
||||
Build schedule |
Select this to include the build schedule in the calculation of requirements.
|
||||
Forward orders |
Select this to include forward orders in the calculation of requirements. If not selected, they are excluded. Ensure that the Sales orders option has been included in the calculation of requirements. |
||||
Orders in suspense |
Select this to include orders in suspense in the calculation of requirements. If not selected, they will be excluded. Ensure that the Sales orders option has been included in the calculation of requirements. |
||||
Supply chain transfer orders |
Select this to include supply chain transfer orders in the calculation of requirements.
|
||||
Goods in transit |
Select this to include goods in transit records in the calculation of requirements.
|
||||
Non-MPS items | |||||
Apply gross requirement rules 'I' and 'S' |
Select this to apply rule I (forecasts only), and S (sales orders only) in the Requirements Calculation program when determining the gross requirement of non-MPS items.
|
||||
Apply gross requirement rules 'H' and 'C' |
Select this to apply rule H (highest of forecasts and sales orders) and C (cumulative highest of forecasts and sales orders) in the Requirements Calculation program when determining the gross requirement of non-MPS items.
|
||||
Period length for 'H' and 'C' (days) |
If you selected to apply gross requirement rules H and C, then your entry here is used to calculate the period to which sales orders and forecasts are allotted. For example: A period length of 7 days calculated from 1 September 2003 translates into the following period allocations: Period 1: 01/09/03 – 07/09/03 Period 2: 08/09/03 – 14/09/03 Period 3: 15/09/03 – 21/09/03 Period 4: 22/09/03 – 28/09/03 In the above example, a forecast with a date of 10/09/03 is used in period 2 and a sales order with a ship date of 18/09/03 is used in period 3. |
||||
Apply demand time fence rule |
Select this to use 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). |
||||
Apply safety stock time fence rule |
When a quantity on hand for a stock 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. If you select one of the time fence rule options, then MRP will apply the rule selected and safety stock demand is inserted at the calculation run date plus the time fence selected. When Inventory Optimization min/max levels are applied in the Requirements calculation, they are applied from the calculation date plus the time fence rule selected. |
||||
None | If you select this option, then MRP treats safety stock
as demand. This is applied at the beginning of the netting off
process, which means that safety stock is not available to
supply any other demand. For example, if you have an on hand quantity of 120 for an item and safety stock for the item is set to 50, you will only have 70 (120 - 50) to supply other demand. This is because MRP will have raised a demand for the safety stock quantity of 50. |
||||
Demand time fence | Select this if you want MRP to apply safety stock outside of the Demand Time Fence. | ||||
Manufacturing time fence | Select this if you want MRP to apply safety stock outside of the Manufacturing Time Fence. | ||||
Planning time fence | Select this if you want MRP to apply safety stock outside of the Planning Time Fence. |
Field | Description | ||||
---|---|---|---|---|---|
Req. calculation - override batching rules with rule 'A' | |||||
Override all items' batching rules |
Select this to override the buying rules held against each stock code, when running the Requirements Calculation. |
||||
Do NOT override any items' batching rules |
Select this to use the buying rule assigned to the stock item when running the Requirements Calculation. |
||||
Only override MPS items' batching rules |
Select this to override only the buying rules held against MPS items when running the Requirements Calculation. |
||||
Schedule jobs and purchase orders according to demand |
Select this to schedule the order/delivery/start dates of existing jobs, suggested jobs, and purchase orders according to when the demand is required. This means that the supply is scheduled according to the earliest demand date found, even if the supply may have been linked to a demand in the future.
|
||||
Schedule specific supply |
Select this to schedule a specific supply (existing or suggested job, sub job, purchase order or requisition) to the specific demand to which it is linked. This means that, for example, supply for a job linked to a sales order will be scheduled according to the sales order. If you do not select this option, then the Requirements Calculation program links the supply of an item to the first demand for the item, according to the demand dates. This option is only enabled if you selected the option: Schedule jobs and purchase orders according to demand.
|
||||
Include all stock codes in requirements file |
Select this to include 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 either demand or supply. This option is selected automatically if any of the setup options: Include safety stock, Consolidate warehouses, or Schedule jobs and purchase orders according to demand is selected.
|
||||
Reduce qty on hand by allocated qty (if s/o not required) |
Select this to reduce the quantity on hand by the quantity allocated to sales orders in the warehouse file, if you have not selected the Include in requirements planning - Sales orders option. |
||||
Make provision for lot expiry in requirements calculation |
Select this to decrease stock on hand for expired lots when generating material requirements in the Requirements Calculation program. When you enable this option, you need to enable the Stock on hand at the Include in requirements calculation field (Planning 1 tab), because the suggestions made by the system vary depending on your selections. When this option is disabled, stock on hand for expired lots is included as stock on hand in the Requirements Calculation program. |
||||
Do not lock live files while creating snapshot files |
Select this to leave your live data files unlocked while the snapshot files are being created. Snapshot files are created when you run the Requirements Calculation program. The process involves extracting supply and demand information from a number of live files within SYSPRO and netting them off in order to establish future material and capacity requirements. These files are normally locked to prevent information from being posted to these files while the snapshot is in progress. However, this can sometimes be difficult to accomplish in a wide area network environment.
|
||||
Allow additional requisition users |
By default, only requisitions created by the requisition users QOT and MRP are recognized as supplies by the Requirements Calculation program. Select this to indicate that additional requisition users can be included in the requirements calculation when calculating supply for requisitions according to requisition users. These additional users are configured on the Requisition Users tab. |
||||
Suppress MRP ordering for non current ECC rev/rel | Select this if the Requirements Calculation program
must not raise suggested supplies (i.e. jobs, requisitions or
SCTs) for non current revision/releases of Engineering Change
Control items. If you do not select this option, then the Requirements Calculation program creates suggested supply for non-current revision/release ECC items. |
||||
Allow MRP to reschedule goods in transit due dates |
Within the Requirements Calculation program, if you are scheduling supply according to demand and there are existing Goods in Transit then this option dictates whether Goods in Transit are rescheduled or not. If you do not select this option, then 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. |
||||
Include quotations where probability is greater than |
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. |
Field | Description |
---|---|
Assign higher priority | |
Start date |
Select this to assign a higher priority to the start date of a job than the job priority held against the job, when using forward finite scheduling. |
Job priority |
Select this to assign a higher priority to the job priority held against a job than the start date of a job, when using forward finite scheduling. |
Assign higher priority | |
Suggested jobs |
Select this to assign a higher priority to suggested jobs than quotations, when using forward finite scheduling. |
Quotations |
Select this to assign a higher priority to quotations than suggested jobs, when using forward finite scheduling. |
Finite scheduling | |
Maximum generated queue time (days) |
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. |
Field | Description | ||||
---|---|---|---|---|---|
Warehouse selection | |||||
All |
Select this to include all warehouses in the Requirements Calculation. |
||||
Range |
Select this to indicate a range of warehouses to include in the Requirements Calculation. |
||||
List |
Select this to indicate a list of warehouses to include in the Requirements Calculation. |
||||
Define List |
Enter a list of up to 10 warehouses that must be included in the Requirements Calculation. |
||||
By warehouse |
Select this to include warehouses according to the option: Include warehouse in requirements planning calculation defined against the warehouse itself (Warehouse Maintenance). The option: Include warehouse in requirements planning calculation (Warehouse Maintenance) is available only if you select the By warehouse option here. |
||||
Consolidate selected warehouses |
Select this to consolidate the information of all the warehouses selected (e.g. quantity on hand, safety stock, WIP, etc.) All information is consolidated using warehouse --.
|
You use the Define List function to enter a list of up to 10 warehouses that must be included in the Requirements Calculation.
Field | Description |
---|---|
Define warehouse list | |
Warehouse | Enter the warehouse you want to add to the list. |
Add | Select this to add the warehouse to the list of warehouses. |
Remove | Select this to remove the highlighted warehouse from the list of warehouses. |
Warehouse | This displays the warehouse(s) currently added to the list |
Close | Select this to return to the previous
screen. You will need to select the Save function to save the list of warehouses you entered. |
Field | Description | ||||
---|---|---|---|---|---|
Requisition user selection |
By default, only requisitions created by the requisition users QOT and MRP are recognized as supplies by the Requirements Calculation program. If you selected the option: Allow additional requisition users (Planning 2 tab), then you can selectively indicate which requisition users can be included in the requirements calculation (see Requirements Calculation).
|
||||
All |
Select this to include all requisition users in the MRP calculation. |
||||
Range |
Select this to include a range of requisition users in the MRP calculation. You indicate this range using the From and To fields. |
||||
By requisition user |
Select this to include requisitions from requisition users only if the option: Include user in MRP calculation is enabled against the user code (User Maintenance). |
||||
Requisition user option |
Requisitions for requisition users QOT and MRP are also included/excluded according to the selection you make here. |
||||
By originator |
Select this to include requisitions originated by the requisition user. |
||||
By current holder |
Select this to include requisitions currently held by the requisition user, irrespective of the user who created the requisition. This includes requisitions created by the current holder and which have not yet been routed. |
The options on this tab page enable you to control forecast depletion into the past as well as into the future. This means that you do not have to inactivate old forecasts to prevent them from being depleted and you can prevent forecasts from being depleted out into the future once the 'more current' forecasts have been depleted.
Forecasts are depleted when stock is reduced in the Sales Order module. This occurs when either an invoice or a dispatch note is printed.
When you change any options on this tab, the Forecast Depletion Take on program is run when you save your changes. You can also run this program from the SYSPRO Desktop ( -> ).
If you do not select any of the options on this tab, then the Forecast Depletion Take on program is not run. As stock items are invoiced, the active forecasts are reduced from the earliest forecast forwards and credit notes increase any depleted forecast up to the original value of the forecast, starting with the latest depleted forecast.
Field | Description |
---|---|
Forecast depletion | |
Deplete forecasts | Indicate whether or not you want to deplete forecasts according to the options on this tab page. |
Exclude forecast depletion for | Indicate the items for which you do not want to deplete
forecasts. The Gross requirements rule and MPS status for a stock code are define on the Production Details pane of the Stock Code Maintenance program. Note that 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 selecting to exclude them from depletion using the options below. |
Gross requirements rule 'A' | Select this to exclude all MPS items with a gross
requirements rule of A - Sum of forecasts &
sales orders from forecast depletion. This option only applies to stocked items. It does not apply to non-MPS items. |
Gross requirements rule 'I' | Select this to exclude 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. |
Non-MPS items | Select this to exclude non Master Production Schedule
items from forecast depletion. This option only applies to stocked items. |
Non-stocked items | Select this to exclude non-stocked items from forecast
depletion. Depletion for non-stocked items only occurs when the non-stocked item is invoiced after Forecast depletion is activated and if you do not select to exclude non-stocked items (i.e. you do not select this option). |
Forecast depletion period type | Indicate the time frame into the future to which you want to limit forecast depletion. |
None | Select this if you do not want to limit forecast depletion into the future. |
Days | Select this to limit forecast depletion to a set number
of days. You indicate the number of days at the Forecast period length - Number of days field. The last depletion date is calculated by adding the days indicated to the ship date passed. |
Demand time fence | Select this to limit forecast depletion to within the
Demand time fence defined against the stock item (Stock Code Maintenance - Sales Details). The last depletion date is calculated by adding the demand time fence to the ship date passed. Therefore, this pads a period length after the ship date of the order and if any active forecasts are found within the demand time fence period, then these are depleted. This option only applies to stocked items. |
Planning time fence | Select this to limit forecast depletion to within the
planning time fence. The last depletion date is calculated by adding the planning time fence to the ship date passed. The program accumulates the Lead time (Stock Code Maintenance) + Planning frequency (Requirements Planning Setup - Frequency allowance days) + Demand time fence (Stock Code Maintenance). The total time (including non-working days) is added to the first ship date found. Thereafter, any forecast located within the time span of the Planning time fence will be depleted. This option only applies to stocked items. |
Planning horizon | Select this to limit forecast depletion to within the
planning horizon. The last depletion date is calculated by adding the planning horizon to the ship date passed. The Planning horizon comprises the Planning time fence plus the Visibility factor (Requirements Planning Setup - General 2 tab). This option only applies to stocked items. |
Use forecast calendar | Select this to limit forecast depletion to within the
forecast calendar. Past due forecasts are ignored and the
calculated start date of the current period is used as the
start date of depletion. This option only applies to stocked items. This option is not available if the Inventory Forecasting module is not installed or licensed. |
Forecast period length | |
Number of days | Indicate the number of days to which you want to limit forecast depletion. This applies when you select the Forecast period type - Days option. |
Allow past due forecasts to be depleted | These options enable you to control forecast depletion
into the past. These options are not applied in the Requirements Planning Query program so do not suppress the pegging (i.e. past due forecasts still generate past due supplies). |
Yes | If you select this option, then depletion starts at the earliest active forecast with a quantity available and depletes forecasts from that date. |
No | Select this if you do not want to deplete past due
forecasts. The ship date on the order is used as the depletion
start date. Forecasts are depleted from the ship date forward. |
Number of days prior to ship date | Select this to deplete 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. |
Forecast period length prior to ship date | This applies if you selected the Number of days prior to ship date option. |
Number of days | Indicate the number of days prior to the ship date to
be 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. For example if you enter 15, then depletion starts 15 days earlier than the ship date for a sale or credit note and if any forecast is located within 15 days, it is depleted. |
Deplete forecasts by customer |
Select this to deplete forecasts relating to the customer passed, followed by forecasts where the customer is spaces. This means that the calculated forecast depletion start and end dates are applied to forecasts by customer. If you select this option, then forecasts with a customer equal to the customer against the sales order are depleted first. If no forecast records are found for the customer, or the forecasts for the customer have been fully depleted, then forecasts where the customer is spaces are depleted. Forecasts with a different customer are excluded from depletion. Note that the other forecast depletion options selected still apply. |
Allow forecasts outside of period to be depleted |
This works together with the option: Forecast depletion period type - Use forecast calendar. If you do not select this option, then depletion only takes place up to the end of the depletion date calculated. This means that the current forecast calendar period end date is the end point of depletion. If you select this option, then depletion continues to take place beyond the current forecast calendar period end date. For example: The forecast quantity for April is 10 and for May it is 15. In April, you invoice an order for a quantity of 13. If you did not select Allow forecasts outside of period to be depleted, then the forecast for April is depleted fully, but the forecast for May remains at 15. If you selected Allow forecasts outside of period to be depleted, then the forecast for April is depleted fully and the forecast for May is depleted by 3. This option only applies to stocked items. |