Allocate forecast - Period / Period key (Period allocation categories)
Current system functionality to allocate a period for the demand forecast lines is a manual process where users select at line level the Allocate forecast option to specify the period key.
This option will enable the forecast to be spread across the month as required and with...
Unposted (draft, in review, rejected) stock journals should not be included in net item requirement calculation
Currently item requirement calculations are affected by all stock movement journals, regardless of the status of the journal.
This means journals in draft, in review or even rejected (!) status is driving demand through MRP. This is wrong, only posted journals should be includ...
Default order settings should not be disregarded by refilling warehouse
We have a main production site with a separate warehouse where we store a surplus stock of both production and purchase items.
We only receive deliveries and manufacture production items at our main production site.
In order for MRP to consider stock held at t...
Item Coverage Setup should not contain any dimensions as mandatory
For Items that have a wide range of different dimensions, when attempting to declare the Item coverage, the dimensions are mandatory. This poses a significant issue as the combination of possible dimensions can result in thousands of variations, making it cumbersome and time-consuming to set u...
Planned orders are generating by looking with Batch disposition code but not with Batch expiration date
Planned orders are generating by looking with Batch disposition code but not with Batch expiration date. If we are not updating the batch disposition code and we have expiration date completed still system is looking for on hand and not creating any planned orders.
Transaction-dynamic period with Method used to reduce forecast requirement is not working with planning optimization
'Transaction-dynamic period' with Method used to reduce forecast requirement is not working with planning optimization. Currently it is working as 'None'. As this logic is not working system is creating excess quantity planned orders.
Support about Catch-weight co-products and catch-weight products in Planning optimization.
Support about Catch-weight co-products and catch-weight products in Planning optimization.
It is a necessary functionality, in classic master planning is active but in Planning optimization is considered as a gap, according with the support team of Microsoft.
...
Better control on what constitutes a production delay
For us, each production order will have some planning space entered as queue times in D365.
Production is allowed to start order at any date within interval StartDate - EndDate, as long EndDate is kept.
Our strategy is to create pick work as late as possible, very close...
Support for Freeze time Fence in Planning Optimization
Our client is a Pharmaceutical manufacturer that outsources all their packaging to CMOs. We use production orders with a service item and a raw material for this purpose. Currently we are using built-in master planning with an exception, but we are hoping to switch over to planning optimizatio...
Demand Forecast Copy Historical Demand for Engineering Versions
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...