2025-03-24 - Smarter stock reservations in Reflex 3000 version 25.0 and higher

Written by: Jan Willem de Vos & Rogier Bessem

At ReflexSystems, we continuously work on improving our software together with our customers. Thanks to practical experiences and valuable feedback, we have recently implemented a significant optimization in how stock reservations are managed in Reflex 3000.

Why this change?

Stock reservations are essential for reliable planning and a smooth production and delivery process. In practice, we noticed that in some situations it was difficult to accurately reconstruct how certain reservation statuses were created. Think of complex scenarios with recipe-based articles, automatically linked packaging, or order changes. Although the system functioned, we saw opportunities to make this process more robust, transparent, and flexible.

What has improved?

Starting from version 25.0.38 / 25.1.43, the stock reservation system has been completely revamped. Instead of aggregated daily statuses, we now use a more transparent and detailed model:

• New tables track reservations per article, batch, and transaction.
• This ensures better traceability, easier recovery in case of corrections, and more flexibility when integrating with external tools like Crystal Reports, Power BI, or other external applications.
• For you as a user, the presentation of data remains unchanged: in Reflex 3000, you will still see the familiar summaries.
• For external applications, however, the data from the new tables must be aggregated.

What does this mean for you?

The new approach is more robust, easier to maintain, and better suited for future expansions. The benefits include:

• Improved reliability: Reservations can always be traced back to the transaction level.
• Less frequent ‘Recalculate Sellable Stock’ actions.
• Easier integrations with reporting tools.
• Faster issue resolution for complex stock-related questions.

Impact on external applications

Do you use external reporting tools like Crystal Reports, Power BI, or other external applications? Then it is important to know that stock reservation data is now stored in new tables. These tables contain detailed transaction records instead of daily statuses.

To correctly display data in external reports, it is necessary to aggregate these records. While this may require a minor adjustment in your reports, it also offers more possibilities for analysis and control. You gain access to the underlying details of each reservation, which improves the quality of your reports.

Our consultants are ready to assist you in modifying existing integrations or reports if necessary.

A future-proof solution

With this improvement, we take a significant step in optimizing stock management within Reflex 3000. It is part of our mission to provide you with powerful, reliable, and user-friendly tools to support your business processes.

Do you have any questions or want to know what this change means for your situation? Feel free to contact your dedicated contact person or our support department.

---

Technical specifications (for those who want to know more)

The tables VrdRes and PVrdRes are deprecated and replaced by:

Data Model

Types and Sources

• ReservationType indicates the type of reservation:

  • StockReservationType_Purchase
  • StockReservationType_Sale
  • StockReservationType_ProductionIn
  • StockReservationType_ProductionOut

• ReservationSource indicates the origin:

  • StockReservationSource_PurchaseOrder
  • StockReservationSource_SaleOrder
  • StockReservationSource_ProductionOrderIn
  • StockReservationSource_ProductionOrderOut

• EntityId1 and EntityId2 identify the source of the reservation (e.g., order number and order line).

Note: ReservationType and ReservationSource do not always match. When reserving a recipe-based article for a sales order, depending on the recipe settings, reservations may be created for the raw materials of the sold product. In this case, ReservationType is ProductionIn, while the ReservationSource remains SaleOrder.