Release Notes 2025.3.0 (April 21, 2025)

What's new 

Platform

In-memory caching and performance improvements

1. Forecast results: The application fetches the forecast results and error metrics from InMemory caching, which helps with faster screen load times and improved performance, especially when dealing with large datasets.

2. ETL/Dataloads: Data load time is significantly reduced using in-memory caching. This applies to all entities, including master data, cross-hierarchy, and transactions.

3. Run jobs Parallelly: The application allows you to run multiple jobs parallel, such as multiple overrides, data loads, forecasts, etc., within memory caching.

4. Forecast creation: The performance of creating forecasts using bigger filter criteria is significantly improved with In-Memory caching.

Demand planning

Planning view enhancements:

1. Edit planning view: The application allows you to edit the planning view. An Edit option is enabled at each planning view record in the list screen, where you can edit the planning view parameters such as Filter criteria and hierarchy level. After editing, the application automatically refreshes the planning with the new filter criteria and hierarchy level.

2. Rename a plan in view: The application allows you to rename a planning view by clicking on the "Rename" option within the planning view list screen.

3. Description of planning item in search results: When creating a planning view, the application also shows the planning item ID and the description in the search results. A configured view option is introduced, where the planner can choose between IDs and descriptions in the search results.

4. Create a planning view without the need to save a filter: The application now allows planners to create a planning view without having to save a filter. Planners can select filter criteria and click the apply button. After applying the filter criteria, the hierarchy level button will be enabled. Planners can change the filter criteria multiple times and adjust the hierarchy levels without the need to save the filter criteria. They can skip the step of saving the filter and directly click on "Create a Planning View."

Forecast management:

1. Rename forecast: The application now allows you to rename the forecast directly from the list page and edit the forecast screen. You can also rename a forecast scenario.

2. Differentiates published forecast vs forecast scenario: The application also differentiates the forecast scenario from the published forecast with an indicator. This indicator is available within the forecast list/management screen.

3. Visualization: A summary graph is introduced in the multi-item view of the forecast and scenario comparison screen.

 NPI Planning

1. The Like Items dropdown will now display all selected items at the top of the list on both the Edit and Create NPI Plan screens. The remaining products that are not selected will appear below the selected ones and be listed alphabetically.

2. Rename NPI plan: The application allows you to rename an NPI Plan by clicking on the "Rename" option within the planning view list screen.

Segmentation:

1. Filter without saving: The application allows the planners to select filter criteria and click the Apply button to see the segmentation results immediately. Once the filter is applied (either saved filter or Apply filter), it applies to both the Segmentation Dashboard and the Demand Profile.

2. Save and run segmentation: When the planner edits the segmentation, the application automatically saves the changes and runs the segmentation with the updated parameters/settings. The user does not need to click the "Run" button again to see the latest results.

3. Saving filter criteria in user preferences: Whenever the planner applies a new filter criteria, it will be saved in the user preferences for each segmentation level. For example, if four different segmentations are created at the tenant level, the user can apply different filter criteria for each segmentation.

Replenishment planning

Family MOQ: The product sourcing network supports a Family Minimum Order Quantity (MOQ). When generating a proposed order, the system checks if the Family MOQ is enabled for the item. If it is, the system adjusts the Suggested Order Quantity (SOQ) of each item within the family to meet the Family MOQ requirements. As a result, the overall SOQ for all items in the family will comply with the Family MOQ, even if their net requirements are lower than the Family MOQ.