Platform

Tooltip descriptions for the Planning time series in the planning views.

The planning view now displays tooltips for planning time series, allowing planners to quickly understand each measure by simply hovering over its name. 

• The tooltip pulls the description from the Planning Time Series Configuration. 
• Tooltips appear instantly on hover across all planning views, including single-item, multi-item, and item/measure/dimension views.

Enhanced grid controls for the Planning View list screen. 

The Planning View List screen is enhanced with grid controls that are consistent with other table views in the application. 

• Users can apply filters on any column, 
• Perform global searches, 
• Adjust row density with Compact, Standard, or Comfortable modes. 
• Hide/Unhide specific columns via the Manage Columns panel.

The exceptions column in the planning views list screen.

The Planning View List screen now displays the Exceptions column, based on the exceptions configuration in the Admin App. 

• If a planning grid has no exceptions configured, the Exceptions column on the planning view list screen will be hidden to avoid confusion. 
• When exceptions exist but no items violate them, the column appears with a count of 0.

Optimize Planning view performance by excluding blank/null records from backend computation.

The performance of the planning views has been improved by excluding Null records from backend computations, while the UI dynamically handles blank placeholders. 

• The backend sends only non-zero data points, drastically reducing computation volume (~90%), execution times, memory usage, etc. 
• The users can continue to submit overrides in the Null buckets.

Toggle to switch between Multi-item and Single-item view.

The Planning View now includes a toggle that lets planners seamlessly switch between multi-item and single-item views in the detail screen. 

• The toggle icon is visible in both modes, with hover text indicating the action (“Switch to Single Item View” or “Switch to Multi-Item View”).
• Switching between views is dynamic and preserves user context, including the selected planning view and applied filters. 
• The transition is fast and smooth, enabling planners to analyze both consolidated and item-level data without reloading or losing context.

Demand Planning

Publish the Segmentation results to Product Master/Product Customer Master.

The application now allows planners to publish segmentation results to selected entities, such as Product, Product–Customer, or Product–Location, and store them in standard Segmentation attributes. 

• Standard segmentation attribute names can be configurable based on the Tenant’s requirement. For example:
  • Demand Analysis ABC/Demand Analysis XYZ
  • Inventory Analysis ABC/Inventory Analysis XYZ
• The segmentation results can only be published to an entity where they match the hierarchy level. For example, 
  • Family–Region segmentation can be published to Product–Customer Master. 
  • Product-Location segmentation can be published to Product-Location Master.

Create planning views/forecasts based on the segmentation filter.

The planner can now create a planning view based on the segmentation attributes.

Suppose the segmentation results are published to the master data dimension levels (product, customer, location, or source). In that case, planners can use those attributes and apply filters when creating a planning view or forecast.

Automatic refresh of planning views based on updated Segmentation results.

Planning views automatically refresh whenever new segmentation results are published, ensuring planners always see the correct planning items based on the segmentation output.

For example, if a planner creates a view filtered by categories AX and BY, all products currently assigned to those categories are displayed. When segmentation is republished, and a product moves from AX to BX, the view automatically refreshes to reflect the change, removing the product from the AX filter. This ensures planning views always align with the latest segmentation results without any manual intervention.

Replenishment 

Flag to ignore PSN.

A new column, “PSN Status,” has been introduced in the Product Sourcing Network to indicate whether each sourcing relationship is active or inactive. This enhancement ensures that only active PSNs are considered by the replenishment planning/solver engine, while inactive PSNs are automatically excluded from all solver computations.

Clickable links - Proposed orders quick filters.

Quick filters have been introduced on the Proposed Orders screen to easily filter proposed orders by order type, order status, and order schedule.

Aggregated level view in the proposed orders.

Introduced a new Aggregate View in the Proposed Orders screen to view order summary at a higher level. This view groups proposed orders by Product, Location, or Source (excluding Customer) Hierarchy Level. 

• The view supports drill-down, enabling users to click a group to filter and see detailed proposed orders for that selection. 
• Aggregated totals for all KPIs will be shown at the bottom of the view.

Data exceptions in the Proposed orders.

The replenishment engine now captures data gaps in a structured Data Exceptions table, helping planners understand why proposed orders were not generated or were created with warnings.

• Data errors include Product Location combinations where demand exists, but the solver couldn’t generate Proposed orders because of missing respective Product Sourcing Network (PSN) data or BOMs.
• Data warnings—includes the PSNs with missing data. Like no PSN priority, no preferred supplier, or no cost details. However, the replenishment engine has generated orders using fallback logic.

Planners can click on warnings to view affected PSNs and take corrective actions, ensuring accurate master data and enabling the successful generation of proposed orders in subsequent planning runs.

Infrastructure upgrade

Upgrade Duck DB Version Used in the Forecast Engine.

The forecasting and replenishment engines have been upgraded to use Duck DB 1.4.2, as the Mother Duck no longer supports older versions (< 1.3.0). This upgrade is needed because we were experiencing sync issues with older versions.