7

When using Demand Forecasting and Engineering Versions, history is lost when changing Engineering Versions. A function should be added to copy historical demand from the same item with an old version to the new version. Engineering Versions are treated as an inventory dimension when creating the Item allocation keys, so the forecast is only generated for that specific Version. When adding a new Version of the same item, the data for that item is lost and the new Version starts from scratch.


This functionality is necessary for Versions, but could also be useful to seed data on new items that will have similar usage/forecasting. Using the Data Management Entity to load Historical demand works as a work around, but requires exporting, formatting, and uploading data. This is inefficient and time consuming when dealing with Version changes.

Category: Planning
STATUS DETAILS
Needs Votes
Ideas Administrator

Thanks for your input! If it gets voted, we will consider adding it to our long term roadmap. 

Sincerely, 

Beatriz Nebot Gracia

Product Manager, Microsoft

Comments

A

Very common request, please add this!

Category: Planning

A

This is a key need in Demand Planning, the lost of history with a version update creates a lot of manual workarounds to handle for users. Great Idea Ansel!

Category: Planning