Forecast consumption on second level for phantoms
The innovation in AX 2012 to add forecast consumption by "any transaction" was very important. It closed the gap for the Assembly to Order business scenarios.
These scenarios require forecasting on a level below a configured end product. The forecast is maintained on major subas...
Supply Forecast Entity
The existing standard "Supply Forecast Entity" is a read only entity.
A data entity is required to import supply forecast to superseed current only available process to copy and paste supply forecast directly in D365 screen.
Such process is used in the context of managing procureme...
Thanks for your input! If it gets voted, we will consider it in our long term roadmap.
Sincerely,
Beatriz Nebot Gracia
Senior Product Manager, Microsoft
SubContract Planning
This is not a trivial ask of Microsoft. Create a new subcontract PLANNING workbench where a user can see ALL the implied subcontract PO's that would be created from planned production/batch orders. Zero change in setup, you still add a Service item to the BOM/formula of type Vendor and optiona...
Thanks for your input! If it gets voted, we will consider it in our long term roadmap.
Sincerely,
Beatriz Nebot Gracia
Senior Product Manager, Microsoft
Intercompany master planning fails if Coverage plan by dimension for ‘Batch number’ is enabled
In Storage dimension group, dimension Inventory status is marked as ‘Coverage plan by dimension’. When running intercompany plan, customer is getting an error: "A value for the required coverage planned storage dimension Batch number could not be found for product in company ***. No planned inte...
Let coverage group setting decide Marking behavior when firming planned orders
End users should not decide if marking should be created or not when firming a planned order. Typically it's the type of the item that should decide (stock items should NOT generate marking against receipt and make-to-order product should). Create a parameter on the coverage group level where it...
Replenishment based on Reorder point (ROP)
Through the Safety stock-calculation we already have the possibility to calculate the ROP-levels based on the average issue during lead time. However, as the Master scheduling regards the date when the Minimum quantity is reached as a Requirement date (Delivery date) - and not as an Order date...
Thank you for your feedback.
During 2021 release wave 2, we shipped "Priority based planning" for Planning Optimization, which allows you to fulfill the orders where the net flow is lower than the reorder point.
Details on priority based planning can be found in:
Priority-based planning - Supply Chain Management | Dynamics 365 | Microsoft Docs
Optimize your supply chain with priority-based planning - Microsoft Dynamics 365 Blog
Sincerely,
Beatriz Nebot Gracia
PM,
Microsoft.
coverage functionality "make-to-order"
There should be a coverage group functionality “make-to-order”. Master planning and Explosion should always show either a planned production order or a planned purchase order even if there is stock physical available.
Maybe this could be solved by positive days with negativ...
Thank you for your feedback.
Currently this is not in our roadmap; however, we are tracking it and if we get more feedback and votes, we may consider it in the future.
Sincerely,
Christian Rytt
PM,
Microsoft.
Include explosion of phantom items during creating of manual created planned orders
With the current logic of planning optimization there is a gap for the firming of manual created planned (batch)orders. Those will not get exploded after firming.
As the production order is created in status sheduled you would expect planning arranged the explosion of the pha...
Sequenced planned batch orders are not being generated if the routes setup is non-linear/parallel
Sequencing is not working for planned production orders with production routes that contain resource operations in parallel.
Thanks for your input! If it gets voted, we will consider adding it to our long term roadmap.
Sincerely,
Beatriz Nebot Gracia
Senior Product Manager, Microsoft
Explosion Form- When using the Transfer delay date button, both the confirmed ship date and the confirmed receipt date should be updated accordingly.
Explosion Form- When using the Transfer delay date button, both the confirmed ship date and the confirmed receipt date should be updated accordingly.
Could you please add more details to the idea?
Administrator
Thank you for your feedback.
Currently this is not in our roadmap; however, we are tracking it and if we get more feedback and votes, we may consider it in the future.
Sincerely,
Christian Rytt
PM,
Microsoft.