Changelog
Functional change history of the system. Here you can see what has changed, how it worked before, and how it works now.
Latest Update
v2.2.0 - 2026-01-09: MOQ/Rounding fix, chart improvements, and documentation updates
MOQ/Rounding fix, chart improvements, and documentation updates
MOQ now uses Rounding Value from ZPRM
Order recommendations now correctly use the rounding_value field from SAP ZPRM for quantity rounding.
Only min_lot_size from ZCOVRM was used. If rounding_value was 24,000 in ZPRM but min_lot_size was 0, recommendations could be any number like 67,000.
System now uses BOTH min_lot_size (ZCOVRM) AND rounding_value (ZPRM). Effective MOQ = max of both. Quantities are rounded UP to multiples of rounding_value. Example: rounding_value = 24,000 → recommendations are 24k, 48k, 72k.
Recommendations now match SAP expected order quantities. No more odd numbers that don't fit pallet/container sizes.
Charts no longer distorted by ">>" column
Time bucket charts now exclude the ">>" and "<<" columns that contain sums outside the 12-week horizon.
The ">>" column (future beyond horizon) was included in charts, causing massive axis distortion and making the chart unreadable.
Charts only show the 12-week horizon. Beyond-horizon quantities are returned separately as metadata (beyond_horizon.past and beyond_horizon.future).
Charts are now readable and useful for analysis. Axis scales reflect actual weekly data.
Clarified Coverage Days vs Days to Stockout
Updated Glossary with clear explanations of why these metrics can differ.
Users were confused: "If I have 8 days coverage, I have 8 days to stockout, no?"
Glossary now explains: Coverage Days = current physical stock only. Days to Stockout = stock + Open POs (considers incoming orders). Added new "Open PO Qty" definition.
Users now understand that Days to Stockout is more optimistic because it includes stock in transit.
SAP Safety Time integration with working days to calendar days conversion
Safety Stock now uses SAP Safety Time
The system now prioritizes the SAP Safety Time field (ZCOVRM column CI) over the Policy parameter to determine safety stock days.
Safety Stock was only obtained from the Policy parameter (safety_stock_days). If SAP had a different value in Safety Time, it was ignored.
The system now reads SAP Safety Time (ZCOVRM) first. If it exists, it converts from working days to calendar days (×1.4) and uses it as Safety Stock. Only if SAP has no value, Policy is used as fallback.
Breach calculations (days until safety stock is broken) now match what SAP considers as the safety threshold.
Automatic conversion from working days to calendar days
SAP uses working days (5 days/week) for Safety Time, but our system calculates in calendar days (7 days/week).
No conversion existed. If someone manually entered 10 days of safety stock, the system interpreted it as 10 calendar days.
SAP Safety Time is automatically multiplied by 1.4 (7/5). Example: 10 SAP working days = 14 calendar days in the system.
Correct alignment with SAP logic. Users no longer need to do manual conversions.
Functional Changelog in Help Center
A new Changelog section was added to the Help Center for transparency on system changes.
No way for users to see what changed in the system. Updates were invisible and caused confusion when behavior changed.
Help Center now has a Changelog section showing all versions with: what changed, how it worked before, how it works now, and the impact. Users can track system evolution.
Full transparency. Users can understand system changes and verify that reported issues were addressed.
Open POs integration and improved ADC calculation
Open POs included in risk calculation
Open Purchase Orders are now considered as incoming stock, reducing false CRITICAL alerts.
The system only considered current physical stock (unrestricted_qty). If there were 100 units in stock and 500 units already ordered in transit, the system ignored them and could generate a CRITICAL alert.
The system adds Open POs to effective stock for simulation: Effective Stock = Current Stock + Open PO. If there are 100 in stock + 500 in transit, the simulation uses 600 as the starting point.
Significant reduction of false CRITICAL alerts. The system now better matches SAP's view which already knows there is stock in transit.
Open POs included in purchase recommendations
Purchase recommendations now subtract existing Open POs to avoid over-stock.
If you needed 500 units and already had 300 ordered, the system recommended 500. Result: over-stock of 300.
If you need 500 units and already have 300 ordered, the system recommends only 200. Rec = Need - (Projected Stock + Open PO).
More accurate recommendations that avoid duplicate orders and generate quantities aligned with SAP.
ADC with weighted average
Average Daily Consumption (ADC) calculation now gives more weight to the most recent months.
ADC = Simple average of the last 3 months. If consumption was 900, 1200, 1050, ADC was (900+1200+1050)/(3×30) = 35 units/day.
ADC = Weighted average: recent month 50%, previous month 30%, 2 months ago 20%. With the same data: (900×0.5 + 1200×0.3 + 1050×0.2)/30 = 34 units/day.
ADC reacts faster to demand changes. If consumption is decreasing, ADC reflects that trend sooner.
Have questions about any change? Contact the support team.