September 17, 2020 Release Notes

Update to Demand Plan Hierarchy Viewing and Navigation

A new way of viewing and navigating a hierarchy has been introduced to make it easier to review a number of nodes within a level together. A summary of new behavior is described below.

1. Persistent Company level

The first change is that the Company level will persist in all hierarchies. Users will no longer be able to select the company level within the hierarchy.

This was required in order to provide the ability to show all nodes in a level within the statistics grid as described below.

DemandCaster - Demand Plan and 8 more pages - Work - Microsoft​ Edge

2. Selecting a level displays all nodes within the level

This is a significant new feature that allows users to view all the nodes within a level at once. Please note that this is only applicable to the statistics grids. Units grids, revenue grids, and others are only displayed in context.

In the image below, I have chosen the customer level to view and see all the nodes with the customer level. As noted, though I have a units grid in the page and tab below, it is not visible. If I wish to view the detail of a node within a level. I can click on the Action Menu icon or simply select a node.

DemandCaster - Demand Plan and 9 more pages - Work - Microsoft​ Edge

By selecting the node within the level, I now see the levels child statistics and units grid since the hierarchy is now in context.

Please note that with the addition of the company level, a new forecast needs to be run to re-populate the forecast statistics.

3. Fixed Plan Row

The plan row is now fixed. We made this update since edits can not be made without the plan row. Since it is required we removed the capability for users to hide the plan row.

If the plan line is not in the correct location following the release, please delete the grid and create a new grid in its place.

Advanced Planning Demand Plan Percent Editing to Work Like Event Plan Editing

An update has been made to bring the same behavior of editing event plan values by percent to demand planning.  

  1. Click the percent, to open the percent dialogue.
  2. Enter the percent edit value and the start and end periods and click preview
  3. If the results are acceptable, click "Apply"
  4. Upon applying, the results will be in edit mode for further editing.
  5. If acceptable, click the "save" button to apply the adjustment

Updated Advanced Planning Upload Error Handling

We continue to add more information to help customers understand issues with any of their Advanced Planning uploads.

New Transfer Order Data Entity

Previously, transfer order data between locations were managed through sales order and purchase order tables. This presented some challenges in specific customer use cases. In response, we have introduced a new transfer order data entity that can manage transfer orders independent of purchase orders and sales orders (though this use case will still be supported).

The structure of the table is described in the data table section Transfer Orders (transferorders.txt).

New SKU Transition Logic

A new transition linking logic has been introduced that transitions an old SKU to a new SKU only when all the inventory at both source and destination locations are consumed at about the same time. This feature calculates requirements for the SKU across all locations and then based on those requirements and the available inventory, distributes the inventory from the source to the destinations so that all locations can transition at the same time.

This feature is currently limited in its availability. If interested, please contact support to enable the feature in your account. For reference, the feature name is "SoftTransitionLinkCalculateBasedOnSourceStockout."

In the example below, the source has independent demand and dependent demand from its destination locations. It has 400,000 units on hand. The objective is to supports its independent and dependent demand in a manner that ensure that it and its destination locations all run out of inventory at about the same time taking into account transfer times.

In this example, the source transitions to the new items during the week of January 3rd.

DemandCaster-Item Planning Details and 5 more pages - Work - Microsoft​ Edge

In one of the destination locations, the transition does not occur until 2 weeks later - January 17. It transitions later because there is a 2 week transit time from source to destination.


Add your comment

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.