Open: Cim200 Planning > Utilities > System Set Up > Maintain Planning Settings | General
Open: Cim200 Planning > Utilities > System Set Up > View Planning Settings | General
Note: The View Planning Settings option allows you to view the settings but not amend them.
Enter the following settings:
Time Fence 1
Time Fences are used by the Demand Schedule to determine how to combine similar demands from Sales Forecasts and Sales Orders.
Time Fence 1 takes effect only when Sales Forecasts are in use.
Enter a number of days, which is the period from current day forward during which any Sales Forecasts will be ignored.
The Demand Schedule will only look at Sales Orders in this period, as these are firm demands.
Time Fence 2
Enter a number of days in Time Fence 2. This is the period after Time Fence 1 during which both Sales Forecasts and Sales Orders are considered by Demand Schedule.
Within this period, Sales Forecasts are consumed by Sales Orders in the same forecast period, so that demands are not counted twice. Therefore, the total demand per item per forecast period is the Sales Forecast quantity or the Sales Order quantity, whichever is higher.
Outside of Time Fence 2, Demand Schedule only reads demands from Sales Forecasts; Sales Orders will be ignored.
Enter the period that the Demand Schedule looks forward from today’s date to read demands. This period can be expressed in Days, Weeks, Months or Years by selecting the appropriate period type from the drop-down list.
Where production or purchase lead times are longer, the Planning Horizon may need to be a longer period, so that demands are captured in time for purchase ordering and production planning to start.
Where production and purchase lead times are shorter, the Planning Horizon may be a shorter period, so that demands further into the future can be safely ignored and the list of recommendations is smaller and easier to work with.
Any demands dated later than the Planning Horizon period will not be included in the Demand Schedule but will be listed in the Demand Schedule Exclusions list.
Include Proforma Orders
Tick this box to include live Proformas from Sales Order Processing in the Demand Schedule.
Often a Proforma is converted to a Sales Order only after it is paid, and this could be a reason to exclude Proformas from Planning.
Tick this box to include live Quotations from Sales Order Processing in the Demand Schedule.
Depending on the likelihood of Quotations becoming orders, and order lead times, it may be beneficial to include Quotations in the Demand Schedule.
Include On Hold Customers
When a customer is put on Hold, new Sales Orders cannot be entered for them, but existing Sales Orders are not directly affected.
Depending on the reason for putting customers on Hold, and company policy towards orders for held customers, this setting can determine whether their existing orders should still be planned.
Tick this box to include live orders from Sales Order Processing in the Demand Schedule for customers who are on Hold in the Sales Ledger.
Exclude SOs Raised via Quotations
Tick this box to exclude Sales Orders from the Demand Schedule where they have been created from Quotations, in turn preventing MRP recommendations to make or buy to satisfy those demands.
Exclude ‘On Hold’ SOs
In addition to, or instead of a customer being placed on hold, Sales Orders themselves can be put on hold, perhaps due to credit control issues. Often this means that any purchasing or production relating to held orders should also be put on hold.
Tick this box to exclude Sales Orders with On Hold status from the Demand Schedule, in turn preventing MRP recommendations to make or buy to satisfy those demands.
Include Locked WOs
Tick this box to include open orders from Works Order Processing in the Demand Schedule, even if they are Locked.
Treat overdue orders as due today
Select this option to have MRP treat unfulfilled orders which are overdue as due today instead, so they have a more realistic due date.
Recommendations based on overdue demands could themselves be dated incorrectly.
Overdue replenishments may be recommended by MRP to cancel and re-raise with a later date.
To keep with orders’ true due dates, and have more visibility of overdue orders in Planning, do not select the option.
There are separate options for Purchase Orders, Works Orders and Sales Orders; each option can be selected independently. The option for Works Orders will affect the replenishment date of the built item and the demand dates for any outstanding components.
Firm Planning Period
A Firm Planning Period is the number of days, from today, during which changes will not be made to existing orders because it will be too late.
In the case of Works Orders, this is usually where production should already have begun; for Purchase Orders it would be where the supplier has already begun fulfilling the order.
Setting a Firm Planning Period informs MRP that any recommendations it would make, such as to cancel or reschedule, to orders/order lines with due dates within this period should be disregarded; and ensures that no recommendation will be made for them.
Separate Firm Planning Periods can be set for Works Orders and Purchase Orders.
- In Firm Planning Period – WO enter the firm planning period for Works Orders.
- In Firm Planning Period – PO enter the firm planning period for Purchase Orders.
Include Purchase Requisitions as Replenishment Source
If Purchase Requisitions are in use, open Requisitions can be treated as another replenishment source.
Tick Include Requisitions as Replenishments to include open Purchase Requisition lines in MRP when calculating replenishments.
Replenishment Horizon Use Lead Time
The Replenishment Horizon is the period that MRP looks forward from the due date of a demand to find any existing replenishments which can fulfil it, before recommending raising a new order.
If a replenishment is due to arrive late, but still quicker than if a new order were to be raised today, there may be no benefit in raising a new order.
Tick Replenishment Horizon Use Lead Time to have MRP use the specific lead time of each time to look ahead for replenishment orders to meet demands.
If this option is not ticked, MRP will look at each item’s Replenishment Horizon Days setting to determine the period to look forward for replenishments.
PO Order Date
Use this setting to determine, when creating Purchase Orders from MRP, which date to use as the Document Date.
- Select Recommended Order Date to use the MRP calculated order date.
- Select Date Actioned to use today’s date.
Sub-Assembly Tagging Mode
When creating recommendations for sub-assembly Works Orders, each recommendation is tagged with a Parent recommendation, to give greater insight into why the recommendation has been made.
Where a sub-assembly recommendation is triggered by a demand from a higher-level works order, which is itself ultimately triggered by a demand from a Sales Order, there is more than one possible parent order to display.
- Select Sales Order Demand to set the Parent Tag to the Sales Order demand which has triggered the recommendation.
- Select Parent Demand to set the Parent Tag to the demand which has directly triggered the recommendation.
WO Cancellation Code
When cancelling a Works Order, a Cancellation Code must be assigned to the cancelled order.
If the order is cancelled by actioning a Cancel recommendation from MRP, a Cancellation Code will be automatically assigned to the order.
In WO Cancellation Code, type or select the code for MRP to automatically assign.
Recalculate Bom Usage Levels
An Item BOM Usage Level is a number: the lowest level it exists at within all the Bills of Materials where it is a component. The Usage Level number is then used by MRP to determine the order in which it is processed, so that components which sit at lower levels are processed later than those at higher levels, and those that don’t exist in any BOMs.
BOM Usage Levels are recalculated automatically as new Bills Of Materials or Works Orders are entered, or when they are amended.
In addition, during the MRP Refresh items with a zero Usage Level are recalculated.
It is recommended to use this option in certain circumstances where the Usage Level will have been affected, but not through manual creation or amendments of BOMs – for example, where they have been imported.
It can also be used as a full recalculation of all item Usage Levels, to ensure they are correct.