Requirements parameters

• Storage site (field STOFCY)

Use this field to define the storage site (warehouse).

The site defined on the user record is displayed by default but can be amended.

A storage site has the check box Stock (Details tab) selected.

• BOM type (field MRPALTTYP)

This field is used in conjunction with the BOM code field. Use this field to define which type of BOM code (Manufacturing or Subcontract) will be defined in the BOM code field.

• BOM code (field MRPBOMALT)

Use this field to define the BOM code that is to be used in the Material Requirements Planning (MRP) and the Master Production Schedule (MPS) calculations.

The Manufacturing module must exist in the folder for this field to be available for entry.

• Weekly structure (field MRPTWD)

A weekly structure is a set of 7 values, each specifying the hourly capacity of a day in the week.
The weekly structure is used in the calendar management.

The Manufacturing module must exist in the folder for this field to be available for entry.

Calendars are used for calculating the capacity of a work center.
A calendar can be common to multiple work centers or specific to an individual work centre. It is made up of a succession of periods linked to weekly schedules.

• Replanning analysis (field MRPANYLTI)

Specify the duration of the replanning analysis period (in weeks). This period starts beyond the firm horizon, provided it has been defined for the product.

• Load calculation (field MRPCAPLTI)

Use this field to define the duration of the load calculation (in weeks), if permitted for the defined BOM code.

Scheduling will not be calculated if this value is null.

• Production lead time (field MRPMFGLTI)

Use this field to define the type of manufacturing lead time to be used by the calculations:

• Product lead times. Lead times defined on the product-site record for all suggested work orders.
• Routing/product lead times. Lead times calculated from the production routing, and from the calendars associated with work centers for the work orders in the charge calculation period and beyond product lead times.
• Always routing lead times. Lead times calculated from the operation routing for all suggested work orders.

Lead time calculation from routings significantly increases the processing time.

When a routing is not associated with the product, the default data is obtained from the product-site record.

• Maximum stock analysis (field MRPMAXANY)

Click this check box to activate overstock analysis. The suggestion considers the maximum stock at period end.

• Print calculation report (field MRPPRNFLG)

Click this check box to print a report of the MRP or MPS calculations at the end of the processing run.

• MPS and MRP products (field MRPITM)

Click this check box if all MRP and MPS managed products should be included in the planning calculations.

Previous suggestions and replanning messages will be erased and replaced for all processed products.

• Exclusive selection (field MRPITMCOD)

Click this check box if the WOS/POS suggestions calculation is only to be performed on the items selected according to the MRP and MPS parameters (products MRP, RPS, MRP+MPS).
The MWS inherited from a different requirement calculation (MPS calculation towards a MRP calculation and reciprocally) and triggered by a WOS on parent products excluded from the current items, are excluded from the current calculations. This option is recommended if there is an overlap between product groups, for example, MRP on MRP product and MPS on MRP+MPS product, or identical groups (MRP and MPS on MRP+MPS product). It also reduces the calculation volume (MRP on MRP product and MPS on MPS product).

If you leave this check box clear this ensures the ascending compatibility between previous versions of the requirement calculations. The WOS/POS suggestion calculation is carried out on all products at the site. Only the WOS/MWS results relating to the selected product group are then specified in the ORDERS table. All MWS are considered as requirements for the current calculation, regardless of their origin (either MRP or MPS).

• Days (field MRPDAYNBR)

The requirement calculation groups requirements by period and generates purchase or production suggestions for each requirement.

Material Requirements Planning (MRP) calculation periods are known as 'buckets'. Buckets can be defined in days, weeks and months. The grouping matches the division of the proposals from the calculation.

You are advised to use the same division as defined in the scheduling parameters.

It is possible to perform a requirement calculation with one or many period types (but always in the following order: days, weeks, months).

The division into periods can be performed over a horizon of 2000 days (just over 5 years), and for a maximum of 1000 periods.

Depending on the calculation start date, the number of periods will automatically be adjusted so that 'week' type periods start on the first day of the week and 'month' type periods cover an entire month with a possible week's overlap.

For example, a grouping of 30 days/ 4 weeks/ 12 months will be expressed as:

• A grouping in days during the first 30 days;
• A grouping by week after the first 30 days and for the following 4 weeks;
• A grouping in months after the 30 days and 4 weeks for the following 12 months.

• Weeks (field MRPWEENBR)

• Months (field MRPMONNBR)

• Automatic adjustment (field MRPBUCCOR)

Click this check box to adjust the schedule automatically to conform to the following rules:

• A week starts with the first working day: Monday in Europe (defined by parameter FIRWRKDAY - First work day of week (chapter STO, group SCH)).
• A month starts on the first day of the month.

The following rules are applied:

• If a number of days and a number of weeks are defined, the number of days will be increased so the first week starts on a Monday (according to parameter FIRWRKDAY - First work day of week).
• If a number of weeks and a number of months are defined, the number of weeks will be increased so the last month is complete.
• If a number of days, a number of weeks and a number of months are defined, the first two rules are applied sequentially.

For example:

• If the 'days' period ends in the middle of the week the system will add as many days as required so the next period starts on the first working day of the week.
• If the 'weeks' period does not end at the end of the month the system will add as many weeks and days as required so the next period can start on the first day of the following month.

• Specific parameter (field MRPSPEPAR)

Use this parameter for a specific processing script. This parameter is not used by Sage X3.

• Deduct allocations (field MRPPHYSTO)

The MRP or MPS process is based on the start stock quantity, requests (demand) and resources (replenishments). It determines the reorder suggestions required for each product.

Start stock specifies the stock type on which the calculations are based.

Click this check box if physical stock must be included in the calculated start stock. Allocated stock will be deducted from the start stock.

• Quality control stock (field MRPCTLSTO)

Use this field to control how uninspected items (stock at status Q), that is those items that have not yet been through Quality Control, are to be used in calculation of available stock.

• No. Uninspected stock must not be included in the initial stock.
• Yes in starting stock. Uninspected stock must be included in the initial stock.
• Yes at date end control. Uninspected stock must be included in the available stock from the date it passes Quality Control.

• Rejected stock (field MRPREJSTO)

Click this check box if the planning calculations should include rejected stock (stock at status R) in the initial stock.

• Transfers (field MRPTRFSTO)

Click this check box if the planning calculations should include transfer stock (stock being transferred to a different site) in the initial stock.

Sage advise that you leave this check box clear. Selecting this check box can significantly affect the time it takes to run the MRP calculations.

Leave this check box clear if your intersite transfers are managed using a continuous workflow (process).

If a direct delivery at one site without an initial Purchase order on the other site does not create an intersite transfer receipt simultaneously on the second site, click this check box. That is, you should include transfer stock if the receipt at the second site (the intersite 'transferred to' site) is generated independently.

A purchase order (TRF) that exists on the requester site will cover all requirement stock. The planning calculations will recognize the purchase order as a resource and will subtract the transferred stock from the calculations.

• Phantoms (field MRPGHOSTO)

Click this check box if the planning calculations should include the eventual stock of phantom subgroups in the initial stock.

This parameter is only active if you select the check box MPS and MRP products (Processing block) first.

• Forecasts (field MRPSOSFLG)

Click the check box to specify if the associated requirement (demand) is to be included in the MRP or MPS calculations.

You can include demand from the forecasts you have entered, sales and intersite orders, and project tasks.

• Sales orders planned (field MRPSOPFLG)

• Sales orders firm (field MRPSOFFLG)

• Transfers suggested (field MRPTPSFLG)

• Transfers planned (field MRPTPPFLG)

• Transfers firm (field MRPTPFFLG)

• Pending issues (field MRPWAISTO)

Click this check box if the planning calculations should decrease quantities related to suspended transactions from the available stock.

• Forecast offset (field MRPHORDEM)

Click this check box if any sales forecast adjustments must be within the demand horizon. This only concerns products for which a request horizon has been defined at the site level.

The adjustment for the planning calculations is based on the following principle:

• Within the demand horizon, forecasts are ignored.
• Beyond the demand horizon, the maximum anticipated quantity is considered. This equates to the difference between actual orders (SOP and SOF) and the forecast quantities (SOS).

• Work orders planned (field MRPWOPFLG)

Click the check box to specify if the associated resource (order type) is to be included in the MRP or MPS calculations as a replenishment.

You can include incoming stock from purchase orders, work orders, intersite (transfer) and subcontract orders.

• Work orders released (field MRPWOFFLG)

• POs planned (field MRPPOPFLG)

• POs firm (field MRPPOFFLG)

• Transfers planned (field MRPTRPFLG)

• Transfers firm (field MRPTRFFLG)

• Subcontracts planned (field MRPEOPFLG)

• Subcontracts firm (field MRPEOFFLG)

• Project task planned (field MRPMTPFLG)

• Project task firm (field MRPMTFFLG)

• Ignore safety stock (field MRPSAFSTO)

Click this check box if the planning calculations should ignore safety (security) stock, regardless of the parameter defined in the reorder strategy.

• Ignore coverage (field MRPCOV)

Click this check box if the planning calculations should ignore the coverage duration for all processed products.

• Resources in coverage (field MRPCOVRES)

Click this check box if, for the products managed with coverage, the planning calculations should take replenishments (resources) into account in the coverage horizon.

• Ignore link scrap % (field MRPSHRPRC)

Click this check box if the planning calculations should ignore the loss (scrap) percentage on a component line of a bill of materials (BOM).

 Including the scrap percentage can increase the required amount of the component.

• Ignore firm horizon (field MRPPLHDAT)

Click this check box if the planning calculations should ignore the firm horizon when creating replenishment suggestions.

• Rebuild safety stock (field MRPSAFCOV)

Use this field to define how the MRP or MPS calculations should handle safety stock.

• Always. The calculations must always suggest a replenishment once the projected stock is less than the safety stock.
• At first requirement. The calculations must wait for the first requirement to suggest a replenishment, taking into account the safety stock.
  This value is ignored for products managed with dynamic safety stock.

• Work order suggestions (field MRPWOSFCY)

Click the check box to specify if the associated resource (order type) can be generated to cover demand or replenish stock.

Work order suggestions (WOS), Purchase order suggestions (POS), Intersite transfer requests (TRS) and Subcontract order suggestions (EOS) can be generated.

• POs suggested (field MRPPOSFCY)

• Intersite suggestions (field MRPWOSFCYI)

• Subcontract suggestions (field MRPEOSFCY)

• Last calculation date (field MRPLASDAT)

This field displays the date the MRP calculations/MPS calculations were last run.

• Time in minutes (field MRPLASLTI)

This field displays the length of time (in minutes) it took to complete the last MRP calculation/MPS calculation run.

• Type (field RPLTYP)

This field displays the type of resource that can be replanned.

The first two characters = the order type; the third character (P (Planned) or F (Firm)) = the status of the order. For example, POP=Purchase Order Planned, WOF=Work Order Firm.

• Method (field RPLMOD)

Replanning determines the consistency of the planning (within a replanning lead time) for each resource with the requests and suggestions, and optimizes the resource with respect to the requirements.

For each type of resource that can be replanned, use this field to define the replanning mode:

• No processing. The processing will not analyze the resource consistency.
• Messages only. Continue the calculation with the previous dates and quantities. This value will display a message confirming if the resource is not required ('Useless'), if it must be moved and/or if the quantity needs adjusting.
• Simulation. Continue the calculation with the replanning dates and quantities. This value means that a replanning message will be submitted if necessary, but also that the processing will simulate its recommendations by date and quantity for the resources concerned.

If the selected replanning mode is Messages only or Simulation, at least one lead time must be entered.

The replanning rule is only applied to those products whose reorder policy provides for replanning.

• Backward lead time (field RPLBWDLTI)

Use this field to define the earliest time (in calendar days) within which resources can be replanned.

The replanning uses this lead time to propose the coverage of a requirement to meet demand.

• Forward lead time (field RPLFRWLTI)

Use this field to define the latest time (in calendar days) within which resources can be replanned.

The replanning uses this lead time to propose the coverage of a requirement to meet demand.

• Replan quantities (field RPLUPDQTY)

Use this field to define which type of replanning must be carried out for quantities (advance, delay).

• Replan dates (field RPLUPDDAT)

Use this field to define which type of replanning must be carried out for dates (advance, delay).

• Decrease below EOQ (field RESBLWLOT)

Use this check box to define the replanning behavior when a resource is sufficient to cover the requirements:

• Reordering in net quantity:

If the reduction is not authorized, replanning does not suggest modifying the resource quantity.

If the reduction is authorized, replanning suggests reducing the resource quantity up to the requirement.

• Minimum reordering quantity (economic lot):

If the reduction is not authorized, replanning does not suggest modifying the resource quantity.

If the reduction is authorized:

If the resource quantity is less than the batch/lot, replanning does not suggest modifying the resource quantity.

If the resource quantity is greater than the batch/lot, replanning suggests the quantity is either the requirement or the economic lot, whichever is the greater value.

• Retain orders in process (field WIPPRO)

Use this field to control the replanning of work in progress orders:

• No. Always replan work in progress orders.
• Always. Never replan work in progress orders.
• According to product. Replanning is determined by what is defined for the Protection in process (replan) check box (WIPPRO) on the product-site record:
• If this check box is clear, work in progress orders are replanned.
• For those products that have this check box selected, work in progress orders are never replanned.

A work order is defined as "in progress" if at least one production tracking record exists; a subcontract order is defined as "in progress" as soon as it is ordered; a purchase order is defined as "in progress" if it is partially received.

• Ignore reorder policy in replanning (field REOPOLDIS)

Click this check box if the reorder strategy for 'net quantity' type is to be ignored. Resources are replanned with reference to the requirements included in the calculations.

Leave this check box clear if resources are only replanned with reference to the first (chronological) requirement included in the calculations.

• Replan material requirements (field MRPMWRPLN)

Select this check box to replan material requirements created for a work order if the work order is replanned.

Leave this check box clear if the original material requirements created for a work order are to be retained.

If the original work order is replanned because, for example, the date or quantity has changed, the work order components retain the original date and/or quantity if you leave this check box clear. Changes to the replanned work order are ignored.

• BOM type (field MPSALTTYP)

This field is used in conjunction with the BOM code field. Use this field to define which type of BOM code (Manufacturing or Subcontract) will be defined in the BOM code field.

• BOM code (field MPSBOMALT)

Use this field to define the BOM code that is to be used in the Material Requirements Planning (MRP) and the Master Production Schedule (MPS) calculations.

The Manufacturing module must exist in the folder for this field to be available for entry.

• Weekly structure (field MPSTWD)

A weekly structure is a set of 7 values, each specifying the hourly capacity of a day in the week.
The weekly structure is used in the calendar management.

The Manufacturing module must exist in the folder for this field to be available for entry.

Calendars are used for calculating the capacity of a work center.
A calendar can be common to multiple work centers or specific to an individual work centre. It is made up of a succession of periods linked to weekly schedules.

• Replanning analysis (field MPSANYLTI)

Specify the duration of the replanning analysis period (in weeks). This period starts beyond the firm horizon, provided it has been defined for the product.

• Load calculation (field MPSCAPLTI)

Use this field to define the duration of the load calculation (in weeks), if permitted for the defined BOM code.

Scheduling will not be calculated if this value is null.

• Production lead time (field MPSMFGLTI)

Use this field to define the type of manufacturing lead time to be used by the calculations:

• Product lead times. Lead times defined on the product-site record for all suggested work orders.
• Routing/product lead times. Lead times calculated from the production routing, and from the calendars associated with work centers for the work orders in the charge calculation period and beyond product lead times.
• Always routing lead times. Lead times calculated from the operation routing for all suggested work orders.

Lead time calculation from routings significantly increases the processing time.

When a routing is not associated with the product, the default data is obtained from the product-site record.

• Maximum stock analysis (field MPSMAXANY)

Click this check box to activate overstock analysis. The suggestion considers the maximum stock at period end.

• Print calculation report (field MPSPRNFLG)

Click this check box to print a report of the MRP or MPS calculations at the end of the processing run.

• MPS and MRP products (field MPSITM)

Click this check box if all MRP and MPS managed products should be included in the planning calculations.

Previous suggestions and replanning messages will be erased and replaced for all processed products.

• Exclusive selection (field MPSITMCOD)

Click this check box if the WOS/POS suggestions calculation is only to be performed on the items selected according to the MRP and MPS parameters (products MRP, RPS, MRP+MPS).
The MWS inherited from a different requirement calculation (MPS calculation towards a MRP calculation and reciprocally) and triggered by a WOS on parent products excluded from the current items, are excluded from the current calculations. This option is recommended if there is an overlap between product groups, for example, MRP on MRP product and MPS on MRP+MPS product, or identical groups (MRP and MPS on MRP+MPS product). It also reduces the calculation volume (MRP on MRP product and MPS on MPS product).

If you leave this check box clear this ensures the ascending compatibility between previous versions of the requirement calculations. The WOS/POS suggestion calculation is carried out on all products at the site. Only the WOS/MWS results relating to the selected product group are then specified in the ORDERS table. All MWS are considered as requirements for the current calculation, regardless of their origin (either MRP or MPS).

• Days (field MPSDAYNBR)

The requirement calculation groups requirements by period and generates purchase or production suggestions for each requirement.

Material Requirements Planning (MRP) calculation periods are known as 'buckets'. Buckets can be defined in days, weeks and months. The grouping matches the division of the proposals from the calculation.

You are advised to use the same division as defined in the scheduling parameters.

It is possible to perform a requirement calculation with one or many period types (but always in the following order: days, weeks, months).

The division into periods can be performed over a horizon of 2000 days (just over 5 years), and for a maximum of 1000 periods.

Depending on the calculation start date, the number of periods will automatically be adjusted so that 'week' type periods start on the first day of the week and 'month' type periods cover an entire month with a possible week's overlap.

For example, a grouping of 30 days/ 4 weeks/ 12 months will be expressed as:

• A grouping in days during the first 30 days;
• A grouping by week after the first 30 days and for the following 4 weeks;
• A grouping in months after the 30 days and 4 weeks for the following 12 months.

• Weeks (field MPSWEENBR)

• Months (field MPSMONNBR)

• Automatic adjustment (field MPSBUCCOR)

Click this check box to adjust the schedule automatically to conform to the following rules:

• A week starts with the first working day: Monday in Europe (defined by parameter FIRWRKDAY - First work day of week (chapter STO, group SCH)).
• A month starts on the first day of the month.

The following rules are applied:

• If a number of days and a number of weeks are defined, the number of days will be increased so the first week starts on a Monday (according to parameter FIRWRKDAY - First work day of week).
• If a number of weeks and a number of months are defined, the number of weeks will be increased so the last month is complete.
• If a number of days, a number of weeks and a number of months are defined, the first two rules are applied sequentially.

For example:

• If the 'days' period ends in the middle of the week the system will add as many days as required so the next period starts on the first working day of the week.
• If the 'weeks' period does not end at the end of the month the system will add as many weeks and days as required so the next period can start on the first day of the following month.

• Specific parameter (field MPSSPEPAR)

Use this parameter for a specific processing script. This parameter is not used by Sage X3.

• Deduct allocations (field MPSPHYSTO)

The MRP or MPS process is based on the start stock quantity, requests (demand) and resources (replenishments). It determines the reorder suggestions required for each product.

Start stock specifies the stock type on which the calculations are based.

Click this check box if physical stock must be included in the calculated start stock. Allocated stock will be deducted from the start stock.

• Quality control stock (field MPSCTLSTO)

Use this field to control how uninspected items (stock at status Q), that is those items that have not yet been through Quality Control, are to be used in calculation of available stock.

• No. Uninspected stock must not be included in the initial stock.
• Yes in starting stock. Uninspected stock must be included in the initial stock.
• Yes at date end control. Uninspected stock must be included in the available stock from the date it passes Quality Control.

• Rejected stock (field MPSREJSTO)

Click this check box if the planning calculations should include rejected stock (stock at status R) in the initial stock.

• Transfers (field MPSTRFSTO)

Click this check box if the planning calculations should include transfer stock (stock being transferred to a different site) in the initial stock.

Sage advise that you leave this check box clear. Selecting this check box can significantly affect the time it takes to run the MRP calculations.

Leave this check box clear if your intersite transfers are managed using a continuous workflow (process).

If a direct delivery at one site without an initial Purchase order on the other site does not create an intersite transfer receipt simultaneously on the second site, click this check box. That is, you should include transfer stock if the receipt at the second site (the intersite 'transferred to' site) is generated independently.

A purchase order (TRF) that exists on the requester site will cover all requirement stock. The planning calculations will recognize the purchase order as a resource and will subtract the transferred stock from the calculations.

• Phantoms (field MPSGHOSTO)

Click this check box if the planning calculations should include the eventual stock of phantom subgroups in the initial stock.

This parameter is only active if you select the check box MPS and MRP products (Processing block) first.

• Forecasts (field MPSSOSFLG)

Click the check box to specify if the associated requirement (demand) is to be included in the MRP or MPS calculations.

You can include demand from the forecasts you have entered, sales and intersite orders, and project tasks.

• Sales orders planned (field MPSSOPFLG)

• Sales orders firm (field MPSSOFFLG)

• Transfers suggested (field MPSTPSFLG)

• Transfers planned (field MPSTPPFLG)

• Transfers firm (field MPSTPFFLG)

• Pending issues (field MPSWAISTO)

Click this check box if the planning calculations should decrease quantities related to suspended transactions from the available stock.

• Forecast offset (field MPSHORDEM)

Click this check box if any sales forecast adjustments must be within the demand horizon. This only concerns products for which a request horizon has been defined at the site level.

The adjustment for the planning calculations is based on the following principle:

• Within the demand horizon, forecasts are ignored.
• Beyond the demand horizon, the maximum anticipated quantity is considered. This equates to the difference between actual orders (SOP and SOF) and the forecast quantities (SOS).

• Work orders planned (field MPSWOPFLG)

Click the check box to specify if the associated resource (order type) is to be included in the MRP or MPS calculations as a replenishment.

You can include incoming stock from purchase orders, work orders, intersite (transfer) and subcontract orders.

• Work orders released (field MPSWOFFLG)

• POs planned (field MPSPOPFLG)

• POs firm (field MPSPOFFLG)

• Transfers planned (field MPSTRPFLG)

• Transfers firm (field MPSTRFFLG)

• Subcontracts planned (field MPSEOPFLG)

• Subcontracts firm (field MPSEOFFLG)

• Project task planned (field MPSMTPFLG)

• Project task firm (field MPSMTFFLG)

• Ignore safety stock (field MPSSAFSTO)

Click this check box if the planning calculations should ignore safety (security) stock, regardless of the parameter defined in the reorder strategy.

• Ignore coverage (field MPSCOV)

Click this check box if the planning calculations should ignore the coverage duration for all processed products.

• Resources in coverage (field MPSCOVRES)

Click this check box if, for the products managed with coverage, the planning calculations should take replenishments (resources) into account in the coverage horizon.

• Ignore link scrap % (field MPSSHRPRC)

Click this check box if the planning calculations should ignore the loss (scrap) percentage on a component line of a bill of materials (BOM).

 Including the scrap percentage can increase the required amount of the component.

• Ignore firm horizon (field MPSPLHDAT)

Click this check box if the planning calculations should ignore the firm horizon when creating replenishment suggestions.

• Rebuild safety stock (field MPSSAFCOV)

Use this field to define how the MRP or MPS calculations should handle safety stock.

• Always. The calculations must always suggest a replenishment once the projected stock is less than the safety stock.
• At first requirement. The calculations must wait for the first requirement to suggest a replenishment, taking into account the safety stock.
  This value is ignored for products managed with dynamic safety stock.

• Work order suggestions (field MPSWOSFCY)

Click the check box to specify if the associated resource (order type) can be generated to cover demand or replenish stock.

Work order suggestions (WOS), Purchase order suggestions (POS), Intersite transfer requests (TRS) and Subcontract order suggestions (EOS) can be generated.

• POs suggested (field MPSPOSFCY)

• Intersite suggestions (field MPSWOSFCYI)

• Subcontract suggestions (field MPSEOSFCY)

• Last calculation date (field MPSLASDAT)

This field displays the date the MRP calculations/MPS calculations were last run.

• Time in minutes (field MPSLASLTI)

This field displays the length of time (in minutes) it took to complete the last MRP calculation/MPS calculation run.

• Type (field RPLTYPS)

This field displays the type of resource that can be replanned.

The first two characters = the order type; the third character (P (Planned) or F (Firm)) = the status of the order. For example, POP=Purchase Order Planned, WOF=Work Order Firm.

• Method (field RPLMODS)

Replanning determines the consistency of the planning (within a replanning lead time) for each resource with the requests and suggestions, and optimizes the resource with respect to the requirements.

For each type of resource that can be replanned, use this field to define the replanning mode:

• No processing. The processing will not analyze the resource consistency.
• Messages only. Continue the calculation with the previous dates and quantities. This value will display a message confirming if the resource is not required ('Useless'), if it must be moved and/or if the quantity needs adjusting.
• Simulation. Continue the calculation with the replanning dates and quantities. This value means that a replanning message will be submitted if necessary, but also that the processing will simulate its recommendations by date and quantity for the resources concerned.

If the selected replanning mode is Messages only or Simulation, at least one lead time must be entered.

The replanning rule is only applied to those products whose reorder policy provides for replanning.

• Backward lead time (field RPLBWDLTIS)

Use this field to define the earliest time (in calendar days) within which resources can be replanned.

The replanning uses this lead time to propose the coverage of a requirement to meet demand.

• Forward lead time (field RPLFRWLTIS)

Use this field to define the latest time (in calendar days) within which resources can be replanned.

The replanning uses this lead time to propose the coverage of a requirement to meet demand.

• Replan quantities (field RPLUPDQTYS)

Use this field to define which type of replanning must be carried out for quantities (advance, delay).

• Replan dates (field RPLUPDDATS)

Use this field to define which type of replanning must be carried out for dates (advance, delay).

• Decrease below EOQ (field RESBLWLOTS)

Use this check box to define the replanning behavior when a resource is sufficient to cover the requirements:

• Reordering in net quantity:

If the reduction is not authorized, replanning does not suggest modifying the resource quantity.

If the reduction is authorized, replanning suggests reducing the resource quantity up to the requirement.

• Minimum reordering quantity (economic lot):

If the reduction is not authorized, replanning does not suggest modifying the resource quantity.

If the reduction is authorized:

If the resource quantity is less than the batch/lot, replanning does not suggest modifying the resource quantity.

If the resource quantity is greater than the batch/lot, replanning suggests the quantity is either the requirement or the economic lot, whichever is the greater value.

• Retain orders in process (field WIPPROS)

Use this field to control the replanning of work in progress orders:

• No. Always replan work in progress orders.
• Always. Never replan work in progress orders.
• According to product. Replanning is determined by what is defined for the Protection in process (replan) check box (WIPPRO) on the product-site record:
• If this check box is clear, work in progress orders are replanned.
• For those products that have this check box selected, work in progress orders are never replanned.

A work order is defined as "in progress" if at least one production tracking record exists; a subcontract order is defined as "in progress" as soon as it is ordered; a purchase order is defined as "in progress" if it is partially received.

• Ignore reorder policy in replanning (field REOPOLDISS)

Click this check box if the reorder strategy for 'net quantity' type is to be ignored. Resources are replanned with reference to the requirements included in the calculations.

Leave this check box clear if resources are only replanned with reference to the first (chronological) requirement included in the calculations.

• Replan material requirements (field MPSMWRPLN)

Select this check box to replan material requirements created for a work order if the work order is replanned.

Leave this check box clear if the original material requirements created for a work order are to be retained.

If the original work order is replanned because, for example, the date or quantity has changed, the work order components retain the original date and/or quantity if you leave this check box clear. Changes to the replanned work order are ignored.