Export of records via ReqItemCoverageSettingsEntity is not up to date for inherited data e.g. from Default order settings.
Data in item coverage form that that is inherited from other tables (for example Planned order type or Coverage group) is not accurate when exported via data entity (ReqItemCoverageSettingsEntity).
Reproduction steps
Company USMF
Export using standard data entity R...
Parameter to remove default filter in Net requirements
When the Net requirements form is launched the transactions are automatically filtered to not include transactions with reference "Safety stock". My client has the need to see the Safety stock transactions, therefore they have to remove the filter every time they launch the Net requirements fo...
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
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.
...
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
Formula/BOM lines "Planning group" to work with different proportion or UOM alternate items, than main priority item
When creating a Planning group for the items in the formula/bom lines, it can only be done for items that can replace the main priority item with the same quantity and unit of measure.
I have seen many cases where this substitution is required but the alternative items must be consumed i...
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
Production order scheduling - random selection of resource when multiple resources meet requirement and have same best available time
On production order scheduling, if there's multiple resources that meet the same requirements and have the same best available time slot, scheduling selects resource with alphabetically smallest resource-id. If the load is less than 100%, work will be split unevenly between resources; smallest r...
Firm planned orders in batch based on query
In master planning, it is possible to setup automatic firming time fence on coverage groups. What I experience as an requested feature is the possibility to perform firming of planned order in recurring batch job, based on a predefined query. I therefore suggest that I can create a feature, that...
Work needs to finish on calendar opening period
My customer is using production orders to reserve personnel capacity to serve their customers. Their staff works mostly from 08:00 to 16:00. When scheduling production orders, sometimes first available slot is late in the afternoon. As a result, production order could be scheduled to start on ...
No more "Marked for Deletion" in WrkCtrCapRes
CURRENT FUNCTIONALITY: A prod order in status Released, where picking work has been created , will get “marked for deletion” for all capacity reservations” after I run scheduling while open picking work exists. The user thinks this is capacity reservation “on the way ou...
coverage calculation by inventory status > net requirement with empty inventory status
If the setup requires coverage calculation by dimension inventory status, there appear data sets on net requirement with empty inventory status. This is very difficult to understand by the customer and also difficult to explain. There should be a solution to prevent empty inventory status in c...
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.
PO per site and supplier
When firming planned orders form different sites with same supplier one (1) PO is created with lines updated with delivery addresses to those sites. The PO-header has a delivery address from one of the sites. Here D365O has to create one (1) PO per site and supplier or give the user a choice t...
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.
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