Documentation
Apps › Manufacturing Suite › Demand Forecast Replenishment › Documentation
Demand Forecast Replenishment help
Demand Forecast Replenishment calculates safety stock, reorder points, order quantities and the order to place now for every stockkeeping unit in Microsoft Dynamics 365 Business Central, from your own history, and explains every number. This guide is for planners, buyers and inventory managers and applies to version 1.29.
On this page
- Quick start
- What the app does
- Roles, role center and permissions
- Setup and planning profiles
- How a quantity is calculated
- Forecasting
- Demand preparation
- Dated replenishment
- Planner workspace and review
- Vendor orders
- Transfers between locations
- Exceptions
- Benchmark and pilot KPIs
- Running the engine
- Glossary
- Support
Quick start
Your first hour with the app: from install to the first approved purchase order.
Before you start
- At least 10 weeks of posted sales (or consumption) for the items you want to plan.
- A Vendor No. on the items (or on their stockkeeping units), and a lead time on the Item Vendor, Vendor or Item.
- A Unit Cost on the items (the EOQ needs it).
- A requisition worksheet template and batch, for example REQ / DEFAULT.
First steps
Install and assign permissions. Install “GSO Demand Forecast Replenishment” from AppSource. Give planners the permission set GSO Replenishment (Forecast Replenishment – Planner) and the person doing the setup GSO Replen Admin (Forecast Replenishment – Admin). The install creates the setup, the planning profile STANDARD, the nine box cells, the forecast models and the decision reasons.
Choose the role. In My Settings, choose the role Replenishment Planner. The role center opens with the exceptions, worksheets and setup links.
Fill in setup. Open Replenishment Setup. In Planning Integration, set Req. Wksh. Template Name and Req. Wksh. Batch Name. In Calculation, set Default Location Filter to the warehouses you plan (blank = all locations).
Check the planning profile. Open Planning Profiles and then STANDARD. The defaults suit most distributors: Demand Weeks 10, Z Factor 1.88, Purchase Interval (Weeks) 0.7, Safety Stock Cap (Weeks) 3. Set Ordering Cost and Holding Rate % to your own figures. Leave Write Planning Parameters on.
Add order packs. Open Order Packs and add the boxes and cartons you buy in, for example Pack Level Inner with Qty. per Pack 6, and Outer with 24. Without packs the app orders in units.
Pick a test group. Start with 20 to 50 items you know well. On their Item Cards, check the Demand Forecast Replenishment group: Exclude From Replenishment off, Update Planning Fields on.
Run the engine. On the Item List, select the test items and choose Calculate Replenishment. For all items, choose Run Engine Now on the role center.
Read the results. Open Planning Results. Check Result Code (OK, or a reason in Skip Reason), Average Weekly Usage, Safety Stock Qty., Target Stock Level (MSQ), EOQ and Suggested Order Qty. Choose Planner Workspace on one line and read Why This Quantity: every step with your own numbers.
Look at exceptions. Open Exceptions from the role center. Start with Projected Stockout lines marked critical: their latest order date has passed.
Review and decide. Open Planner Review List, set filters (for example a Vendor Filter) and choose Load. Use Accept Selected for the lines you agree with. Open a line with Open Workspace and use Change Quantity or Reject, with a reason, for the others.
Create requisition lines. On the Planner Review List, choose Create Requisition Lines. To group orders per vendor with minimum order values first, use Vendor Order Planning: Load, then Create Requisition Lines.
Create the purchase order. Open Requisition Worksheets, check the lines (vendor, quantity, order date, due date) and choose Carry Out Action Message. Business Central creates the purchase order. Approve and release it as you usually do.
Next steps
- Schedule Nightly Run on the setup page, so results and exceptions are fresh every morning.
- Clean the history: Demand Adjustments > Suggest Stockout Corrections and Suggest Spike Exclusions.
- Add vendor order constraints (fill-up target, maximum value, container, consolidation days) from the Vendor Card: Vendor Order Constraints.
- Turn on forecasting on a profile (Forecasting Enabled) and look at Forecast Backtests.
- Run a benchmark (page Benchmark Runs) on your history, and start the pilot KPIs with Pilot KPI Snapshots > Schedule Monthly Calculation, so you can measure results against a baseline.
Common first-run messages
| Result | What to do |
|---|---|
| Insufficient Demand Data | The item has no demand in the window. Check the Demand Entry Type on the Item Card, or record lost demand. |
| Planning Profile Missing | No planning profile exists. Create one on Planning Profiles and mark it Default. |
| EOQ is 0 | The item has no Unit Cost, or Ordering Cost or Holding Rate % on the profile is 0. |
| No requisition lines created | Set Req. Wksh. Template Name and Req. Wksh. Batch Name in setup, and select lines with a quantity. |
1. What the app does
Business Central plans purchases from the safety stock, reorder point and reorder quantity on each item or stockkeeping unit, and from demand forecasts. Most companies type those numbers once and never revisit them. This app calculates them from your own history for every stockkeeping unit (item, variant and location), explains each number, and helps planners act on them.
It works inside Business Central and through standard Business Central documents:
- It writes planning parameters to the Stockkeeping Unit (or the item when you do not use locations), so the Planning Worksheet and Requisition Worksheet plan with them.
- It can write Demand Forecast entries that MPS/MRP nets against sales orders.
- It creates Requisition Worksheet lines and Transfer Orders. You create purchase orders with the standard Carry Out Action Message.
What it calculates for each stockkeeping unit:
| Result | Meaning |
|---|---|
| Average Weekly Usage | Demand per week from the last weeks of history (or from the forecast). |
| Safety Stock Qty. | Buffer against changes in demand and lead time. |
| Target Stock Level (MSQ) | Safety stock plus the demand expected during the lead time and the purchase interval. It becomes the reorder point. |
| EOQ | Economic order quantity, kept within a range of weeks of usage. |
| Pack Qty. | The order pack used for rounding (inner, layer, outer, pallet). |
| Suggested Order Qty. | What to order now, with an Order Reason. |
| First Shortage Date, Latest Order Date | When stock runs out on the dated projection, and the last day to order in time. |
The calculation follows a proven safety stock method used in distribution for many years, extended with forecasting, dated supply and a planner workflow.
2. Roles, role center and permissions
Role center
Choose the Replenishment Planner profile (My Settings > Role). The role center shows a headline, the Replenishment Activities cues, the Replenishment Dashboard and the Pilot KPIs cues.
| Area | Pages |
|---|---|
| Top actions | Exceptions, Replenishment Worksheet, Planner Review List, Vendor Order Planning, Transfer Suggestions, Items, Vendors |
| Planning | Planning Results, Planning Profiles, Forecast Overrides, Forecast Versions, Demand Adjustments, Promotions, Item Lifecycles, Forecast Accuracy, What-If Calculator, Requisition Worksheets |
| History | Planning Audit Log, Forecast Override Log, Engine Runs, Demand Quality Issues, Pilot KPI Dashboard, Pilot KPI Snapshots |
| Setup | Replenishment Setup, Order Packs, Nine Box Cells, Seasonality Profiles, Vendor Ordering Calendars |
| New | Purchase Order, Transfer Order, Forecast Override |
| Action | Run Engine Now |
Other pages are found with Tell Me (Alt+Q), for example Forecast Models, Forecast Backtests, Forecast Lines, Forecast Runs, Benchmark Runs, Demand Series, Lost Demand Entries, Item Classifications, Stock Projection, Decision Reasons and Planning Profile Assignments.
Permission sets
| Permission set | Caption | For | Can do |
|---|---|---|---|
| GSO Replenishment | Forecast Replenishment – Planner | Planners and buyers | Run the engine, work with results, proposals, decisions, overrides, demand adjustments, promotions, item lifecycles, forecast versions, lost demand and KPIs. Reads setup, profiles, calendars, constraints and order packs. |
| GSO Replen Admin | Forecast Replenishment – Admin | Supply chain manager, partner | Everything the planner has, plus setup, planning profiles and assignments, forecast models, nine box cells, seasonality profiles, vendor ordering calendars, vendor order constraints, decision reasons, order packs and the logs. |
| GSO Replen Audit | Forecast Replenishment – Audit | Auditors, controllers | Reads every table and opens the pages. Cannot run the engine or change anything. |
Planners also need the standard Business Central permissions for items, vendors, requisition worksheets, purchase orders and transfer orders.
3. Setup and planning profiles
Setup has two levels:
- Demand Forecast Replenishment Setup: company-wide switches (worksheet, demand forecast name, approval, exceptions, classification, run limits).
- Planning Profiles: the calculation parameters. One profile is the default; others apply to item categories, locations, items or single stockkeeping units.
3.1 Demand Forecast Replenishment Setup
Open Replenishment Setup from the role center. The fields that matter most:
| Group | Field | What it does | Default |
|---|---|---|---|
| Calculation | Demand History Window (weeks) | Weeks of sales used for the ABC ranking. | 26 |
| Calculation | Default Location Filter | Locations the engine plans. Blank = all locations. | blank |
| Run Limits | Max. SKUs per Run, Commit Interval (SKUs), Max. Run Duration (Minutes) | Limits for large companies. 0 = no limit. | 0, 1, 0 |
| Classification | ABC A Cumulative Threshold %, ABC B Cumulative Threshold % | Pareto cut-offs for ABC classes. | 70, 90 |
| Classification | Margin Low Threshold %, Margin High Threshold % | Margin bands for the 9-Box. | 15, 30 |
| Policy Advisor | Lumpy ADI Threshold, Erratic CV-Squared Threshold | Cut-offs for the demand pattern. | 1.32, 0.49 |
| Planning Integration | Supply Parameters at Planning Time | Lets planning use the app’s numbers for item and location pairs without a stockkeeping unit, without writing them. | off |
| Planning Integration | Req. Wksh. Template Name, Req. Wksh. Batch Name | Where requisition lines are created. Required before you create lines. | blank |
| Planning Integration | Demand Forecast Name | The demand forecast the app writes to. Other demand forecasts are never changed. | GSO-FCST |
| Planning Integration | Require Forecast Approval, Allow Self-Approval | Forecasts reach planning only through an approved forecast version. | off, off |
| Exceptions and Transfers | Overstock Above Weeks of Cover, Dead Stock After Weeks, Stale Result After Hours, Flag Reorder Point Change Above %, Accuracy Window (Weeks), Flag Forecast Bias Above % | Exception thresholds. 0 turns a check off. | 26, 26, 48, 50, 13, 30 |
| Exceptions and Transfers | Transfers Require a Route, Min. Transfer Quantity | Transfer suggestion rules. | on, 1 |
| Pilot KPIs | Obsolete After Days, KPI per SKU, KPI Baseline Months | KPI rules. | 180, off, 3 |
| BC Time Series Forecast | Confidence Level %, Own Azure ML Endpoint URI, Own Endpoint API Key, Service Timeout (Sec.) | Connection to the Business Central time series service. See 5.3. | 80, blank, blank, 60 |
| Telemetry & Diagnostics | Enable Telemetry | Sends anonymous run counts to GMSOFT. | on |
Some fields on the setup page come from earlier versions and no longer change the calculation: Default Service Level %, Safety Stock Cap/Floor (Weeks of Usage), Default Ordering Cost per Order, Default Annual Holding Rate %, EOQ Min/Max Coverage Weeks, Auto-Update Reordering Policy, Blend BC Time Series Forecast, BC Forecast Weight %, Reject Forecast Above Delta %, History Periods Sent, Forecast Horizon (Periods), Min. History Periods, Enable Holt-Winters and Enable Vendor Rating Adjustment. Set the calculation values on the planning profile instead.
Setup actions: Run Engine Now, Run BC Forecast Now (tests the service connection), Schedule Nightly Run, Use as Current Demand Forecast, and links to the other pages.
3.2 Planning profiles
Open Planning Profiles. On install the app creates the profile STANDARD with the default values and marks it Default. Create more profiles when groups of items need other rules, for example fast movers, slow movers or seasonal goods.
| Group on the Planning Profile card | Field | Default | Meaning |
|---|---|---|---|
| Demand History | Demand Weeks | 10 | Weeks of history counted back from the work date. |
| Min. Weeks for New Items | 4 | Shortest window for a new item. | |
| Variance Basis | Population | Population or Sample variance. | |
| Keep Negative Weeks | on | A week where returns exceed sales keeps its negative quantity. | |
| Include Backorders | off | Adds open sales lines with a past shipment date. | |
| Include Lost Demand, Lost Demand %, Lost Demand Fraction | off | Adds recorded lost demand (page Lost Demand Entries). | |
| Variability Source | Demand History | Demand History or Forecast Error. | |
| Service Level | Z Factor | 1.88 | About 97% protection. |
| 9-Box Sets Z | off | The 9-Box cell’s Z replaces the other Z values. | |
| Lead Time and Purchase Interval | Purchase Interval (Weeks) | 0.7 | Time between two orders to the same vendor. |
| Max. Week Factor | 4 | Longest protection period in the safety stock formula. | |
| Max. Allowable Lead Time (Weeks) | 3 | Receipts that took longer are ignored. | |
| Min. Lead Time Receipts | 5 | Receipts needed to measure the lead time. | |
| Lead Time History (Months) | 12 | Months of posted receipts used. | |
| Lead Time Variability % | 15 | Used when the lead time is not measured. | |
| Default Lead Time (Days) | 1 | Last fallback. | |
| Update Item Vendor Lead Time | off | Writes a measured lead time to the Item Vendor. | |
| Count Supply within Protection Period | on | Time-phased supply, see 4.6. | |
| Safety Stock | Safety Stock Cap (Weeks), Safety Stock Floor (Weeks) | 3, 0 | Limits in weeks of usage. |
| Order Quantity | Ordering Cost, Holding Rate % | 1, 10 | EOQ costs. |
| EOQ Min. Weeks, EOQ Max. Weeks | 1.5, 3 | EOQ range in weeks of usage. | |
| Order Cap Trigger (Weeks), Order Cap (Weeks) | 5, 3 | A suggestion above 5 weeks is cut to 3 weeks (never below the need). | |
| Order Weeks Limit | 10 | Larger suggestions become one week of usage. | |
| Pack Threshold % | 60 | Pack choice, see 4.5. | |
| Result Freshness (Hours) | 24 | Older results are not ordered from. | |
| Buyer Rules | No Order Below One Pack | off | Nothing is ordered when the shortage is less than one pack (not at or below the safety stock), see 4.7. |
| Target Stock Weeks | 0 (off) | Raises the order so the average stock on the shelf reaches this many weeks of usage, see 4.7. | |
| Forecasting | Forecasting Enabled, Forecast Drives Planning, Forecast Period Type, Forecast Horizon (Periods), Backtest Periods, Model Switch Threshold %, Write Demand Forecast | off, off, Week, 12, 8, 5, off | See section 5. |
| Business Central Planning | Write Planning Parameters | on | Writes the numbers to the stockkeeping unit. |
| Write Reordering Policy | off | Also writes the recommended policy. | |
| Use Maximum Qty. Policy | off | Maximum Qty. instead of Fixed Reorder Qty. | |
| Newsvendor | Newsvendor Selling Period (Weeks) | 4 | See 4.9. |
| Dated Replenishment | Projection Weeks | 13 | See section 7. |
| Demand Preparation | Auto-Correct Stockout Weeks, Remove Past Promotions | off, on | See section 6. |
| Housekeeping | Audit Retention (Days) | 90 | How long the Planning Audit Log keeps entries. The default profile’s value applies to the whole log. |
3.3 Which profile applies
The most specific source wins:
- Planning Profile Code on the Stockkeeping Unit.
- A Stockkeeping Unit assignment on Planning Profile Assignments.
- Planning Profile Code on the Item Card.
- An Item assignment.
- An Item Category assignment (the item’s category, then its parent categories).
- A Location assignment.
- The Default profile.
Open assignments from Planning Profiles > Assignments.
3.4 Item Card fields
The Item Card has a Demand Forecast Replenishment group:
| Field | Use |
|---|---|
| Exclude From Replenishment | The engine skips the item. |
| Planning Profile Code | Pins a profile. |
| Z Factor Override | Z for this item (the stockkeeping unit has the same field). |
| Safety Stock Mode | Newsvendor uses the single-period calculation; any other value uses the statistical calculation. |
| Demand Entry Type | Sale (default), Consumption or Both. Use Consumption or Both for components and kits. |
| ABC Class Override | Fixes the ABC class. |
| Seasonality Profile Code | Monthly seasonal coefficients from Seasonality Profiles. |
| Update Planning Fields | Allows the engine to write the planning fields (on by default). |
| Last Safety Stock Calculation | When the item was last calculated. |
The group also shows Seasonality Source, Industry Override Profile, Override HW with Manual Profile and Service Level Override % from earlier versions; they do not change the calculation.
Item Card actions: Calculate Replenishment, View Calculation Results, Forecast Overrides, Item Lifecycle, Replenishment Exceptions and Replenishment What-If. The FactBoxes show the latest result and why stock is below safety stock.
3.5 Packs, calendars and the 9-Box
- Order Packs: per item and variant, optionally per vendor (blank = any vendor). Choose a Pack Level (Inner, Layer, Outer, Pallet) and either a Unit of Measure Code (the quantity comes from the item unit of measure) or a Qty. per Pack. Threshold % Override replaces the profile’s pack threshold for that row.
- Vendor Ordering Calendars: per vendor and location (blank location = all locations), with the reference lead time, minimum order quantity and order multiple. The calendar also holds the ordering days, the minimum order value and the purchase interval that vendor order planning uses.
- Nine Box Cells: nine cells of ABC class x margin band. The install creates them; Add missing cells restores deleted ones.
- Item Classifications: the ABC class, margin band and 9-Box number per item. Classify Items rebuilds them; a full engine run does it too.
4. How a quantity is calculated
Each stockkeeping unit goes through the same steps. The page Why This Quantity (in the planner workspace) shows them for one stockkeeping unit with its own numbers.
4.1 The steps in plain words
- Profile and lifecycle. The app finds the planning profile. A discontinued item, or a replaced item after its phase-out date, gets no order and its planning fields are cleared.
- Demand history. Weekly demand from posted sales (or consumption) at the location and variant, drop shipments left out, for the profile’s Demand Weeks, counted back from the work date. Week 1 is the latest full week. Active demand adjustments, backorders, lost demand and the seasonal coefficient are applied. A new item uses a shorter window, or its like item’s history.
- Average Weekly Usage (AWU) and variance of those weeks. Weeks with zero demand count.
- Demand pattern: Smooth, Intermittent, Erratic or Lumpy, from how often and how evenly the item sells.
- Lead time. In this order: the vendor calendar lead time when it is marked manual; the posted receipts of the item and vendor over the last 12 months (at least 5 receipts); the lead time on the Item Vendor, Vendor or Item; the profile default. When the lead time is not measured, its variability is 15% of the lead time.
- Z factor. The 9-Box cell (only when 9-Box Sets Z is on), else the stockkeeping unit or item override, else the location override, else the profile.
- Forecast (when the profile enables it). The forecast can replace AWU, and its error can replace the variance. See section 5.
- Promotions inside the protection period add their uplift.
- Forecast override. An active planner override has the last word on weekly demand.
- Stock position (Available) = on hand – open sales orders – outbound transfers + inbound transfers and goods in transit + open purchase orders.
- Safety stock, target stock level, need, EOQ, pack and final quantity (below).
- Policy and write-back to the stockkeeping unit, demand forecast entries, stock projection, audit log.
4.2 Safety stock
- Protection period (Week Factor) = lead time in weeks + purchase interval, at most the profile’s Max. Week Factor.
- Combined Variance (R) = Week Factor x weekly variance + (daily demand)² x (lead time standard deviation in days)². It covers both demand changes and late deliveries.
- Safety stock = Z x √R, capped at Safety Stock Cap (Weeks) x AWU, rounded, then raised to the floor when a floor is set.
The cap comes from the vendor ordering calendar, else the location, else the profile (0 = 3 weeks).
4.3 Target stock level (MSQ) and need
- MSQ = safety stock + (lead time in weeks + purchase interval) x AWU, rounded down. Recorded lost demand adds to AWU here when the profile includes it.
- Need = MSQ – Available, rounded down, 0 when stock already covers MSQ. For A and B items the vendor’s 9-Box modifier can raise or lower the need by up to 30%.
4.4 EOQ
EOQ = √(2 x yearly usage x Ordering Cost / (Holding Rate % x Unit Cost)), then kept between EOQ Min. Weeks and EOQ Max. Weeks of usage. The EOQ always uses the history usage, before forecasts, promotions and overrides, so a short-term override does not change the order size. With no unit cost the EOQ is 0.
4.5 Packs
The app uses the largest pack whose quantity is below Pack Threshold % of AWU. Packs for the item’s vendor come first; without any, packs with a blank vendor apply. A layer or pallet only counts when an inner or outer pack exists. With no suitable pack the app orders in units.
4.6 Available stock and time-phased supply
Every screen uses one definition of Available, so the worksheet, the explanation, the SKU Planner Workspace, the What-If Calculator, the exceptions and the engine always show the same figure:
| Component | What counts |
|---|---|
| On Hand | Item ledger quantity on the shelf at the location and variant now |
| Goods In | Open purchase order lines (no drop shipments), expected by the cut-off date |
| Transfers In | Open inbound transfers, not yet shipped plus in transit, arriving by the cut-off date |
| Transfers Out | Open outbound transfers not yet shipped, in full (subtracted) |
| Open Sales | Open sales order lines (no drop shipments), in full (subtracted) |
| Available | On Hand + Goods In + Transfers In – Transfers Out – Open Sales |
With Count Supply within Protection Period on (the default), the cut-off date is the work date + lead time + purchase interval: a purchase arriving next month then cannot hide a need today. With it off, all open supply counts. Open sales orders and outbound transfers always count in full. For an item-level result (blank location) all locations count together and the company’s own transfers are left out.
Choose Available on the worksheet to see the breakdown. The SKU Planner Workspace and the What-If Calculator show it in an Available Stock group, and Why This Quantity has one step per component, with the same names everywhere.
4.7 Final quantity and order reason
- EOQ rounded down to the pack (at least one pack) and need rounded up to the pack.
- The suggestion is the larger of the two.
- Order Cap: when the suggestion is more than Order Cap Trigger (Weeks) of usage, it is cut to Order Cap (Weeks) of usage, never below the need.
- Weeks Limit: when the suggestion is more than Order Weeks Limit weeks of usage, it becomes one week of usage, in units.
- Covered: when Available is already at or above MSQ, nothing is ordered.
- Buyer rules on the planning profile (group Buyer Rules, both off by default), when an order is suggested:
- No Order Below One Pack: when the shortage (MSQ – Available) is less than one pack (the selected pack, else the order multiple, else 1 unit), nothing is ordered. It does not apply when the stock is already at or below the safety stock: then the order always goes out.
- Target Stock Weeks: the order is raised (never lowered) so the average stock on the shelf over one cycle reaches this many weeks of usage. The average on hand is about safety stock + half the order, so order = 2 x (target weeks x AWU – safety stock), rounded up to packs, and still within the order cap and the order weeks limit. Example: AWU 10, safety stock 12, target 4 weeks, pack 12: 2 x (40 – 12) = 56, rounded up to 60; the average on hand is then about 12 + 30 = 42, 4.2 weeks.
- The bin capacity check (below) runs last.
The Order Reason says which rule decided: EOQ, Need, Order Cap, Weeks Limit, Covered, Newsvendor, Skipped, Discontinued, Bin Capacity, Below One Pack or Target Stock Weeks. Why This Quantity shows a Buyer rule step when a buyer rule changed the quantity, and always says whether lost demand was used.
Bin capacity check
At a location that uses bins, the app checks whether the order fits the item’s bins when it arrives (today + the lead time; 7 days when the lead time is 0). Only bins with a Max. Qty. on the bin content count; the receipt bin, the shipment bin, bins whose bin type is Receive or Ship and the Goods-In Bin Code from the setup are left out. When no bin of the item has a maximum, nothing is checked.
- Capacity = the sum of Max. Qty. x quantity per unit of measure of those bins.
- In the bins on arrival = what they hold now + put-aways into them – picks from them + warehouse journal adjustments waiting + goods in the goods-in and receipt bins not yet on a put-away + inbound transfers and purchase orders due by then – outbound transfers due by then (less what is already on a pick) – the lowest weekly sale of the demand history x the lead time in weeks. Each movement is counted once and the total is never below 0.
- Room = Capacity – In the bins on arrival – Bin Cap. Spare Weeks x the lowest weekly sale, never below 0. The lowest weekly sale is used on purpose: slow sales leave the bins fuller.
When the suggestion is larger than the room, the app orders the most whole packs that fit (0 when not one pack fits), sets the order reason Bin Capacity and ends the explanation with a step such as “ORDER 132 – lowered from 192 to fit the bins (room 140 when it arrives)”. The engine, the worksheet, the What-If Calculator and vendor orders (top-up and fill-up included) all apply it. A quantity you enter yourself is never changed or blocked: in the worksheet, the review list and the decision dialog it turns orange from Bin Cap. Warning Pct. of the room and red above the room, with a message. A purchase order line whose quantity does not fit the room on its expected receipt date shows a notification (setup Bin Cap. Check on Purchase Lines).
4.8 Worked example
Item 1000, location MAIN, profile STANDARD (defaults), Unit Cost 4.00. Order packs: Inner = 6, Outer = 24. The vendor’s Item Vendor lead time is 7 days, with no receipt history.
| Step | Calculation | Result |
|---|---|---|
| Last 10 weeks of sales | 15, 25, 20, 18, 22, 20, 24, 16, 21, 19 | total 200 |
| Average Weekly Usage | 200 / 10 | 20 |
| Variance (population) | 4,092 / 10 – 20² | 9.2 |
| Lead time | Item Vendor, 7 days; variability 15% | 7 days, std. dev. 1.05 days |
| Week Factor | 7/7 + 0.7 (below the maximum of 4) | 1.7 |
| Lead time component | (20/7)² x 1.05² | 9.0 |
| Combined Variance (R) | 1.7 x 9.2 + 9.0 | 24.64 |
| Safety stock | 1.88 x √24.64 = 9.33; cap 3 x 20 = 60 | 9 |
| Target stock level (MSQ) | 9 + 1.7 x 20 = 43 | 43 |
| Available | on hand 18 – sales orders 6 + purchase order 10 due in 3 days | 22 |
| Need | 43 – 22 | 21 |
| EOQ | √(2 x 20 x 52 x 1 / (10% x 4.00)) = 72, kept within 1.5-3 weeks (30-60) | 60 |
| Pack | 60% of 20 = 12; Inner 6 is below 12, Outer 24 is not | 6 |
| EOQ rounded down to pack | 60 / 6 = 10 packs | 60 |
| Need rounded up to pack | 21 / 6 = 3.5, so 4 packs | 24 |
| Suggestion | larger of 60 and 24; below the cap trigger (100) and the weeks limit (200) | 60, Order Reason EOQ |
Written to the stockkeeping unit with the Fixed Reorder Qty. policy: Safety Stock Quantity 9, Reorder Point 43, Reorder Quantity 60, Order Multiple 6, Time Bucket 5 days (0.7 weeks). Maximum Inventory on the result is MSQ + EOQ = 103.
If the purchase order of 10 were due in 20 days, it would fall outside the 12-day protection period: Available would be 12 and the need 31 (36 in packs). The EOQ of 60 would still decide.
4.9 Newsvendor items
For perishable, seasonal or one-off goods, set Safety Stock Mode = Newsvendor on the Item Card or Stockkeeping Unit. The app then orders one quantity for the selling period instead of a reorder point:
- Underage cost (the margin lost per unit not sold) = Unit Price – Unit Cost.
- Overage cost (the cost of a unit left over) = the cost of holding it over the selling period.
- Critical Ratio = underage / (underage + overage). It is the share of demand you plan to cover.
- Order quantity = expected demand over Newsvendor Selling Period (Weeks) + Z(critical ratio) x its standard deviation, minus Available, rounded up to the pack. Order Reason = Newsvendor.
When the selling period or the costs are missing, the app uses the statistical calculation and says why in Skip Reason. Newsvendor items get the Order reordering policy, so MRP does not plan them again.
4.10 What is written to Business Central
With Write Planning Parameters on, the app writes to the Stockkeeping Unit (created from the item when missing) or to the item when there is no location:
| Reordering Policy | Fields written |
|---|---|
| Fixed Reorder Qty. | Safety Stock Quantity, Reorder Point = MSQ, Reorder Quantity = EOQ rounded to pack, Time Bucket = purchase interval |
| Maximum Qty. | Safety Stock Quantity, Reorder Point = MSQ, Maximum Inventory |
| Lot-for-Lot | Safety Stock Quantity, Include Inventory |
| Order | Safety Stock Quantity = 0 |
For planned policies the Order Multiple is the pack quantity and the Minimum Order Quantity comes from the vendor ordering calendar. With Write Reordering Policy on, the recommended policy is written too:
| Situation | Policy Recommendation |
|---|---|
| Newsvendor | Order |
| Intermittent or Lumpy demand | Lot-for-Lot |
| Forecast Drives Planning on the profile | Lot-for-Lot (with demand forecast entries) |
| Use Maximum Qty. Policy on the profile | Maximum Qty. |
| Otherwise | Fixed Reorder Qty. |
When a stockkeeping unit is skipped later, the planning fields the app wrote are cleared, so planning never uses stale numbers.
5. Forecasting
Forecasting is optional per planning profile. Without it the app plans from history alone.
5.1 Model catalogue
Open Forecast Models. The install adds every model, enabled.
| Model | Engine | For |
|---|---|---|
| Naive, Seasonal Naive, Moving Average | AL (in the app) | Baselines; Moving Average and Naive also for intermittent demand |
| Simple Exponential Smoothing, Holt Linear Trend, Damped Trend | AL | Smooth demand |
| Holt-Winters Additive, Holt-Winters Multiplicative | AL | Seasonal demand (at least two seasons of history) |
| Croston, Syntetos-Boylan Approximation, Teunter-Syntetos-Babai | AL | Intermittent and lumpy demand |
| ARIMA, ETS, STL, ETS+ARIMA, ETS+STL, TBATS, All Models (Business Central) | Business Central time series service | All patterns; needs Azure AI |
Columns: Enabled, For Smooth Demand, For Intermittent Demand, Seasonal, Service Method, Min. History Periods, Min. Plan Tier. Clear Enabled to stop using a model. Add missing methods restores deleted rows.
5.2 Back-testing and selection
For each stockkeeping unit the app:
- Picks the enabled models that suit its demand pattern (intermittent and lumpy items use the intermittent models).
- Back-tests each one over the profile’s Backtest Periods: it forecasts each past period from the data before it and compares with what really happened.
- Selects the model with the lowest MASE one period ahead (error compared with a naive forecast). The current model stays unless another one is better by more than Model Switch Threshold %. This keeps forecasts stable.
- Writes the forecast for Forecast Horizon (Periods) to Forecast Lines, the test results to Forecast Backtests, and records each forecast in Forecast Accuracy to compare with actual demand later.
The planning result shows Forecast Model Code, Forecast Weekly Rate, Forecast RMSE and Forecast MASE. Forecast Lines > Show all methods shows the runners-up.
5.3 Business Central time series (Azure AI)
The models marked “(Business Central)” use Business Central’s own time series service (Azure Machine Learning):
- In Business Central online the Microsoft-hosted service is used. It counts against the tenant’s Azure AI usage. When the limit is reached, the run continues with the AL models.
- On premises, enter Own Azure ML Endpoint URI and Own Endpoint API Key in setup. The key is stored in isolated storage and never shown again.
- Series are sent in batches of up to 200, before the calculation starts. A failed call never stops a run; the AL models are used.
- A service model replaces the best AL model only when its live accuracy over at least 6 completed periods is better.
- Run BC Forecast Now on the setup page tests the connection and shows the result. Forecast Runs lists every forecast pass.
5.4 Forecast driving planning
| Profile setting | Effect |
|---|---|
| Forecasting Enabled only | Forecasts are made and measured. Safety stock and MSQ still use history. |
| Forecast Drives Planning | The forecast weekly rate replaces AWU for MSQ and the order quantity. The policy becomes Lot-for-Lot. |
| Variability Source = Forecast Error | The forecast’s RMSE replaces the history variance in the safety stock. |
5.5 Demand forecast entries for MPS/MRP
With Write Demand Forecast on, the selected forecast is written as Demand Forecast entries (by location and variant) to the setup’s Demand Forecast Name. Each run replaces the app’s own entries from the first forecast period on; other demand forecasts are never touched. Business Central planning nets these entries against sales orders.
- No entries are written for Fixed Reorder Qty. or Maximum Qty. items unless the forecast drives planning, because forecasts and reorder points would count the same demand twice.
- Use as Current Demand Forecast on the setup page makes this forecast the current demand forecast in Inventory Setup and turns on forecasts on locations and variants. It asks first.
5.6 Forecast versions and approval
Turn on Require Forecast Approval in setup when forecasts must be approved before planning uses them. The engine then stops writing demand forecast entries itself.
- Forecast Versions > Create from Forecasts, with optional item and location filters. The new version (status Draft) copies the selected forecasts as lines: Statistical Qty. and Final Qty. per item, variant, location and period.
- Planners change Planner Adjusted Qty. with an Adjustment Comment on the lines.
- Submit. Another user then chooses Approve or Reject (with a reason). With Allow Self-Approval on, the submitter may approve too.
- Reopen returns a submitted or rejected version to Draft.
- Release writes the Final Qty. of every line as demand forecast entries.
The version card shows who submitted, approved and released, and when.
5.7 Hierarchy: top-down and bottom-up
On a Draft version choose Build Aggregates, then Aggregates. The Forecast Aggregates page sums the lines bottom-up per item category, item, and item and location (Bottom-Up Qty.).
To plan top-down, choose an aggregate row and Set Top-Down Target. The target is spread over the lines below it in proportion to their current quantities, rounded to whole units so the lines add up exactly. Lines with a planner adjustment keep it; the rest of the target goes to the other lines.
5.8 Forecast overrides
When you know something the history does not (a new customer, a lost contract), add a Forecast Override for an item and location with a Starting Date and Ending Date:
| Override Type | Effect on weekly demand |
|---|---|
| Replace Weekly Demand | Uses Value as the weekly demand. |
| Adjust % | Raises or lowers demand by Value percent. |
| Add Weekly Quantity | Adds Value per week. |
A Reason is required. Every insert, change and delete is logged; see Change Log or Forecast Override Log. The override has the last word over history, forecast and promotions, but it does not change the EOQ.
5.9 Forecast accuracy
Forecast Accuracy shows the forecast against actual demand per stockkeeping unit, method, period and horizon. The exception list flags Forecast Bias when the selected method is biased beyond Flag Forecast Bias Above % over the accuracy window.
6. Demand preparation
Clean history gives better numbers. All changes are demand adjustments: reversible, with who and when, and the original quantity kept.
6.1 Demand adjustments
Open Demand Adjustments:
| Adjustment Type | Effect |
|---|---|
| Exclude Week | The week leaves the calculation. |
| Replace Quantity | The week uses Adjusted Qty. |
| Stockout Correction | A week that sold less because stock ran out gets the average of the other weeks. |
| Promotion Removal | A past promotion week gets the average of the other weeks. |
Actions: Suggest Stockout Corrections, Suggest Spike Exclusions, Accept, Reject and Revert. Suggestions start inactive. Accept makes them count; Revert makes an active adjustment inactive again, and the next calculation uses the original week.
6.2 Stockout correction
A week is a stockout week when it ended with no stock on hand and sold less than the other weeks. With Auto-Correct Stockout Weeks on the profile, the engine corrects these weeks itself. Without it, run Suggest Stockout Corrections and accept the suggestions you agree with.
6.3 Spikes
Suggest Spike Exclusions finds weeks far above normal (more than three standard deviations) and suggests excluding them. You can also open Demand Quality Issues and use Exclude Spike from Demand or Mark as Resolved.
6.4 Promotions
Open Promotions and create a Promotion Card: Starting Date, Ending Date, Uplift % and Status (Planned, Active, Closed). Add lines for items; a blank Variant Code or Location Code on a line means all. A line can have its own Uplift %.
- A Planned or Active promotion inside the protection period adds its uplift to the demand used for MSQ and the order.
- With Remove Past Promotions on the profile (the default), weeks of past promotions are taken out of the history as Promotion Removal adjustments, so a promotion does not inflate normal demand.
6.5 Lifecycle
Open Item Lifecycles (or Item Lifecycle on the Item Card):
| Stage | Effect |
|---|---|
| New | Uses the Like Item No. history, times Like Item Factor %, for the weeks before the item’s own first sale. |
| Growth, Mature, Decline | Information for planners. |
| Discontinued | No order; the planning fields the app wrote are cleared. |
| Replaced | No order after Phase-Out Date (blank = at once). The item hands its history to the Replacement Item No. |
To replace an item, open the lifecycle of the old item: set Stage = Replaced, Replacement Item No. = the new item, Phase-In Date (from when the new item uses the old item’s history, blank = at once) and Phase-Out Date (after which the old item is no longer ordered, blank = at once).
6.6 Lost demand
Record sales you could not make on Lost Demand Entries (item, variant, location, date, quantity, reason). With Include Lost Demand on the profile, Lost Demand % of it counts as demand.
7. Dated replenishment
Quantities alone can hide timing problems. The app also projects stock week by week.
7.1 Stock projection
For each stockkeeping unit the app builds Projection Weeks (default 13) of projected stock. Weeks run Monday to Sunday; week 1 contains the work date. Overdue supply and demand count in week 1.
| Column | Source |
|---|---|
| Opening Qty. | Stock on hand, then the previous week’s ending quantity |
| Scheduled Receipts | Open purchase orders by expected receipt date |
| Transfer Receipts | Inbound transfers and goods in transit by receipt date |
| Open Sales Qty. | Open sales orders by shipment date |
| Forecast Qty. | The selected forecast, else the weekly usage |
| Demand Qty. | The larger of open sales and forecast (sales consume the forecast, as in Business Central planning), plus outbound transfers |
| Ending Qty. | Opening + receipts – demand |
| Below Safety Stock, Shortage | Ending below safety stock; ending below zero |
Open Stock Projection from the Planning Results page or the worksheet.
7.2 First shortage and latest order date
- First Shortage Date: the first week whose ending quantity is below zero.
- Safety Stock Breach Date: the first week below safety stock.
- Latest Order Date: the first shortage date minus the lead time, never before the work date. Order by this date to receive the goods before stock runs out.
7.3 Date-based exceptions
The Projected Stockout exception is based on these dates: it appears when the first shortage falls within the protection period. It is critical when the latest order date is today or earlier, because the order must go out now. The vendor order fill-up also uses these dates to decide which items to add first.
8. Planner workspace and review
8.1 Replenishment Worksheet
Load builds one line per calculated stockkeeping unit for the item and location filters. Each line is recalculated against today’s stock with the stored MSQ, EOQ and pack. Results older than Result Freshness (Hours) show a note instead of a quantity. Choose the Available number to see its breakdown (On Hand, Goods In, Transfers In, Transfers Out, Open Sales).
- Apply to Planning Fields writes the proposed parameters of the selected lines.
- Create Requisition Lines creates lines in the setup’s requisition worksheet.
8.2 SKU Planner Workspace (why this quantity)
Open it from Planning Results > Planner Workspace or Planner Review List > Open Workspace. One page per stockkeeping unit:
| Section | Shows |
|---|---|
| General | Item, variant, location, vendor, ABC class, result code |
| Recommendation | Suggested Order Qty., Order Reason, Decision, Decided Qty., Safety Stock Qty., MSQ, EOQ, AWU, lead time, First Shortage Date, Latest Order Date, Open Exceptions |
| Available Stock | On Hand, Goods In, Transfers In, Transfers Out, Open Sales and Available right now (choose Available for the breakdown) |
| Why This Quantity | Every calculation step in plain words with the numbers, then the open exceptions |
| History and Forecast Chart, Demand History and Forecast | Past weekly demand and future forecast |
| Stock Projection | The dated projection |
| Shelf View, Shelf Stock by Week | Week by week the stock on the shelf with the suggestion and with the buyer’s quantity (the decided quantity, else the suggestion) as the first order, both with the system’s follow-up orders every purchase interval, weeks of cover, and the average weeks on hand for both |
| Decision History | Last decision, by whom, when, reason and comment |
Actions: Accept, Change Quantity, Reject, Recalculate, What-If, Audit Log, Demand Adjustments, Decision History and Item.
8.3 Accept, change or reject
| Action | Result |
|---|---|
| Accept | Orders the suggested quantity. |
| Change Quantity | Orders the quantity you enter. A Reason Code is required. |
| Reject | Orders nothing. A Reason Code is required. |
The Decision dialog asks for Quantity, Reason Code and Comment. Some reasons require a comment. The install adds the reasons FORECAST, ONE-OFF, STOCK, SUPPLIER and OTHER (OTHER needs a comment); change them on Decision Reasons.
Every decision is logged on Proposal Decisions with the calculation it was made on. When you load the worksheet again, the decision on the same calculation is applied again. A rejected line is never ordered.
8.4 Planner Review List
The bulk version of the workspace. Set Item Filter, Location Filter, ABC Class Filter and Vendor Filter, then Load.
- Accept Selected accepts the selected lines at the suggested quantity. Lines with an outdated result are skipped.
- Reject Selected rejects them with one reason.
- Create Requisition Lines creates lines for accepted, changed and other selected lines.
- Open Workspace, Decision History, Decision Reasons.
8.5 What-If Calculator
What-If Calculator (page Replenishment What-If Calculator) shows the last engine result for one stockkeeping unit and recalculates safety stock, MSQ, EOQ and the order with other inputs: Average Weekly Usage, Std. Deviation, Lead Time (Days), Lead Time Std. Dev. (Days), Purchase Interval (Weeks), Z Factor, Safety Stock Cap (Weeks), Pack Qty., Unit Cost, Ordering Cost, Holding Rate % and Available. Nothing is saved. Calculate runs it, Use Current Stock fills today’s stock and Reset Inputs starts again. The Available Stock group shows today’s breakdown.
Shelf View answers “why does it order when I have 179?” in shelf terms. Type a Buyer Qty. (it starts as the suggestion). Shelf Stock by Week shows, for each projection week, the demand (planning usage, or open sales when larger), the open receipts, the week the first order arrives (ordered today, arriving after the lead time), the system’s follow-up orders arriving that week (Follow-Up Arrives (A) and (B)), the stock on hand with the suggestion and with the buyer qty. and the weeks of cover for each. A week below the safety stock is orange, a stock-out red.
The two cases differ only in the first order: (A) the suggestion, (B) your quantity. After that the view does what the app really does: at every purchase interval it reviews the item, and when the stock on hand plus the orders still on their way is at or below the target stock level (MSQ), it orders the larger of the EOQ and the shortfall to MSQ, rounded up to the pack, arriving after the lead time. Example: MSQ 100, EOQ 40, pack 25, on hand 60 and nothing on order at a review: the system orders max(40, 100 – 60) = 40, rounded up to 50, arriving one lead time later. A larger first order pushes the first follow-up later. Stock can still run out when the lead time is longer than the time to the next review.
Avg. Weeks on Hand gives the average stock on the shelf over the projection, in weeks of usage, for both cases, including the follow-up orders (a stock-out week counts as 0). It counts the shelf only, not stock plus open orders.
The Stock Projection part (and the First Shortage Date, Latest Order Date and exceptions) is different on purpose: it places no new orders, so it shows when the stock runs out if you do nothing.
9. Vendor orders
9.1 Vendor Order Planning
Open Vendor Order Planning, set Item Filter and Location Filter, and choose Load. The page groups the suggested orders into one order per vendor and location and shows:
- Order Value (LCY), Min. Order Value, Below Minimum, Shortfall (LCY).
- Next Ordering Date, Ordering Day Today, Expected Receipt Date from the vendor ordering calendar.
- Top-Up Lines and Top-Up Value (LCY): items added to reach the minimum, closest to their reorder point first, never above their maximum inventory.
- With order constraints: Fill-Up Target, Order Weight, Order Volume, Containers, Binding Constraint, Fill-Up Qty., Waiting Lines and Fill-Up Message.
Select orders, set Include Top-Up Lines if you want the additions, and choose Create Requisition Lines.
9.2 Supplier constraints and fill-up
Open Vendor Order Constraints from the Vendor Card (or from Vendor Order Planning). One record per vendor, optionally per location (blank = all locations):
| Field | Use |
|---|---|
| Fill-Up Target | None, Min. Order Value, Min. Order Qty., Weight, Volume, Full Container or Free Freight Value |
| Max. Order Value, Max. Weight, Max. Volume | Upper limits for one order |
| Container Capacity (Volume), Round to Full Containers | Container planning |
| Free Freight Value | Order value for free freight |
| Consolidation Days | Lines needed later than this wait for the next order |
| Notes | Free text |
How the fill-up works:
- Lines needed more than Consolidation Days after the earliest latest order date wait for the next order.
- When the order is below the fill-up target, whole packs (or order multiples) are added to the lines that run short first: first shortage date, then latest order date, then lowest days of cover.
- A line never goes above its maximum inventory or the profile’s Order Weeks Limit.
- When the order is above a maximum (value, weight, volume or one container), packs are removed from the latest-needed lines first, never below what a line needs.
Weights and volumes come from the item (gross weight, unit volume) or its purchase unit of measure.
9.3 From requisition lines to purchase orders
All paths (worksheet, review list, vendor order planning) create lines in the requisition worksheet named in setup:
- Order Date = the vendor’s next ordering day; Due Date = order date + lead time.
- The quantity is the decided quantity when a planner accepted or changed the line.
Open Requisition Worksheets, review the lines and choose Carry Out Action Message to create the purchase orders.
10. Transfers between locations
Open Transfer Suggestions and choose Load. A location gives stock only above its maximum inventory and always keeps its safety stock. A location below its MSQ is filled up to its maximum inventory. The largest shortage is served first from the largest surplus, per item and variant.
Select lines and choose Create Transfer Orders: one transfer order per pair of locations. With Transfers Require a Route on, pairs without a transfer route are skipped.
11. Exceptions
Exceptions (page Replenishment Exceptions) is the planner’s daily list. The engine rebuilds it at the end of each run; Refresh rebuilds it for the current filters.
| Exception Type | Meaning |
|---|---|
| Projected Stockout | The first shortage falls within the protection period (critical when the latest order date has passed) |
| Below Safety Stock | Available stock is below safety stock |
| Overstock | Stock covers more weeks than the overstock limit |
| Dead Stock | No sales or consumption for the dead stock weeks |
| Stale Result | The result is older than the limit |
| Parameter Jump | The target stock level changed by more than the limit since the previous run |
| Calculation Skipped | The engine skipped the stockkeeping unit; see the reason |
| Transfer Available | Another location has surplus stock |
| Planner Override Active | A forecast override is in force |
| Forecast Bias | The forecast runs high or low beyond the limit |
| Forecast Rejected | The profile forecasts but no model could be fitted |
Actions: Replenishment Worksheet, Transfer Suggestions, What-If, Recalculate Item, Planning Result, Forecast Overrides, Item Card.
12. Benchmark and pilot KPIs
12.1 Benchmark
The benchmark shows what the app’s policy would have done on your own history, next to your current Business Central parameters. It changes no planning data.
- Open Benchmark Runs and choose Run Benchmark.
- Set Item Filter, Location Filter, History Weeks and Warm-up Weeks.
- The app replays each stockkeeping unit’s real weekly demand twice, with the same rules: once with the app’s calculation and once with the current reorder point, reorder quantity, maximum inventory or safety stock.
| Result | Meaning |
|---|---|
| App Fill Rate %, Baseline Fill Rate % | Share of demand served from stock |
| App Stockout Weeks, Baseline Stockout Weeks | Weeks with unserved demand |
| App Avg. Inventory Value, Baseline Avg. Inventory Value | Average stock value |
| App Orders, Baseline Orders | Number of orders |
| Best Method MASE (Avg.), Naive MASE (Avg.) | Forecast error of the best model compared with a naive forecast |
Results shows the figures per stockkeeping unit. The benchmark is a simulation on past demand; it is not a promise of future results.
12.2 Pilot KPIs
Pilot KPIs measure live results month by month, so you can compare with the months before the app.
- Pilot KPI Snapshots > Calculate KPIs calculates a period. Schedule Monthly Calculation creates a monthly job queue entry; the first run also calculates KPI Baseline Months back as the baseline.
- Pilot KPI Dashboard compares the latest month with the baseline. Export KPIs creates an Excel workbook.
| KPI | Meaning |
|---|---|
| Fill Rate %, Order Line Fill Rate % | Quantity and lines shipped on or before the planned shipment date |
| Shortage Days, Shortage SKUs | Days ending with no stock while there was demand |
| Avg. Inventory Value (LCY) | Average daily stock value |
| Excess Stock Value (LCY), Obsolete Stock Value (LCY) | Stock above need; stock without movement for Obsolete After Days |
| Acceptance %, Avg. Adjustment % | Share of recommendations accepted; average change made by planners |
Rows are stored for the company and per location, and per stockkeeping unit with KPI per SKU.
12.3 Buyer vs System
Who was right, the system or the buyer? The app answers on your real sales, not on a one-week impression.
Daily Order Records. Every engine run writes, for each stockkeeping unit it calculated, what the system suggested that day (after packs, caps and bin capacity), with the target service level of its safety stock (from the Z factor: 1.65 = 95.05 %). The next run adds what the buyer really ordered that day, from the purchase order lines with that Order Date, and compares the two: Agreed (within one pack or the Agreement Tolerance % on setup), Buyer Ordered More, Buyer Ordered Less, Buyer Did Not Order or System Suggested Nothing. The ordered quantity is kept even when the order is deleted later. Records older than Order Record Retention Days (400) are deleted. The role center shows Buyer Agreement % (30 Days).
Replay. Buyer vs System Replays > Run Replay (also on the role center and setup) asks for a period and filters (item, location, vendor, purchaser, ABC class). For each stockkeeping unit with records in the period it replays the real daily demand twice from the real stock at the start: once with the buyer’s real purchase receipts, once with the system’s suggestions arriving after their lead time. Transfers and other entries apply to both. Demand that finds no stock is lost; nothing is backordered.
| Result | Meaning |
|---|---|
| Cycle Service % | Share of replenishment cycles (receipt to receipt) without a day out of stock |
| Days Out of Stock | Days whose demand was not served in full, or that started with no stock |
| Lost Units | Demand that found no stock |
| Avg. Stock Qty., Avg. Stock Value | Average end-of-day stock, and at unit cost |
| Deliveries | Receipt days of the path |
| Winner, Verdict | The path that met the target; with less stock when both did; the closer one when neither did |
Totals by Buyer, Totals by Vendor and Totals by ABC Class show the same figures per group; Daily Order Records opens the records behind a row. Schedule Weekly Replay on setup replays every Sunday the last Replay Weeks (10) weeks ending the Sunday before.
The system path assumes the real lead times recorded with each suggestion. Like the benchmark, the replay is a simulation on past demand, not a promise of future results.
13. Running the engine
| How | Scope |
|---|---|
| Run Engine Now (role center or setup) | All items, all planned locations |
| Calculate Replenishment on the Item Card | One item |
| Calculate Replenishment on the Item List | The selected items |
| Recalculate Item on Planning Results or Exceptions | One item |
| Schedule Nightly Run on setup | A recurring job queue entry, every night |
A full run (no filters) also rebuilds the 9-Box classification and marks results that the run did not touch. A stockkeeping unit that fails is saved with Result Code Error and the run continues. Large companies can set run limits in setup; a stopped run resumes where it stopped. Engine Runs shows every run with its status and counts.
Check after each run: Planning Results (filter on Result Code), Exceptions and Engine Runs. Every calculation is copied to the Planning Audit Log, kept for the default profile’s Audit Retention (Days).
14. Glossary
| Term | Meaning |
|---|---|
| ADI | Average demand interval: weeks per week with demand. Above 1.32 demand is intermittent. |
| AWU | Average Weekly Usage. |
| CV² | Squared coefficient of variation of the demand sizes. Above 0.49 demand is erratic. |
| EOQ | Economic order quantity: the order size that balances ordering and holding cost. |
| MASE | Mean absolute scaled error: forecast error divided by the error of a naive forecast. Below 1 beats naive. |
| MSQ | Target stock level: safety stock plus demand over the protection period. Written as the reorder point. |
| Protection period | Lead time plus purchase interval. |
| Purchase interval | Time between two orders to the same vendor. |
| SKU | Stockkeeping unit: item + variant + location. |
| Z factor | Number of standard deviations of protection. 1.88 is about 97%. |
Support
Contact GMSOFT at [email protected] or through the support page. Include your Business Central version, the app version shown in Extension Management, the item and location, and the steps that lead to the problem.
