Prevent recalculation posting after End a Production order.
Unwanted journal entries are being created during the end of a production order in Dynamics 365 Finance. The expected behavior is that the entry made during production report as finished should be the final entry, with no additional entry during the end of the production order. Having multiple...
MIP report not showing data when generated with Past data
After posting picking list from Production order (where status was ‘Started’ and Remaining status was ‘Material consumption’), User update production order status to ‘Created’ from started (since order was cancelled by customer and no more Production order to run). Since no more this productio...
Thank you for the detailed scenario.
When a production order is manually deleted, the system intentionally removes it from operational and analytical data sets. As a result, downstream calculations such as MIP (Material in Process) are recalculated based on the current system state, not reconstructed from historical snapshots.
Even if the MIP is generated for a past date, the calculation relies on the existence of the production order record. Once the order is deleted, the system no longer has a reliable source to include it in MIP, as this would require reconstructing deleted transactional data, which is not supported.
This behavior is by design to ensure:
- Data consistency across planning, costing, and inventory
- Clear separation between reversals/cancellations and hard deletions
- Avoiding misleading historical results based on records that no longer exist
If historical visibility is required, the recommended approach is to cancel or close the production order rather than deleting it, so the record remains available for historical reporting and analysis.
For these reasons, the request cannot be supported.
Sincerely,
Johan Hoffmann
PM, Microsoft
The job card and route card posting through MES to inherit the cost category rate from the actual worker assigned to the job instead of resource cost rate
When reporting progress in Production floor execution, the job card is created successfully, but the system defaults to using the resource cost rate instead of the actual worker-specific cost rate, leading to discrepancies in cost accounting.
Business scenario: multiple workers using the...
Thank you for the feedback. This capability is already supported by the Production order default parameter called: Cost category. If you set it to No, then the system will use the rates defined in the pay agreement in the time and attendance module to calculate the cost.
Sincerely,
Johan Hoffmann
PM, Microsoft
Add Co-Product and Formula Options to Production Floor Execution
When utilizing production floor execution, limited visibility exists as to what the BOM / Formula along with what needs to be produced when co-products exist. Currently users must hover over the order number to view the details, which is insufficient for operators out on the shop floor. Adding...
Thank you for your feedback. This is a great suggestion!
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,
Johan Hoffmann
PM, Microsoft
Request a function to restrict generate production work order if cycle counting work exists
We would like to request any function from standard environment that can restrict system generate production work order if cycle counting work exists.
Financial Entries should not be posted for Estimated cost in Production Order
Production post picking list/RAF to GL should not be posted for Estimated Cost even if item model group parameter Post physical/financial inventory to GL.
If we not put check mark in "Post report as finished in ledger" and...
Thank you for your feedback. We are not considering the suggestion at this time due to the following reason:
It is the intent of the production control parameter: Post picking list in ledger to control if ledger transactions should be generated when the production picking list is posted. If there is a good business justification why this parameter is not serving is's requirement, please feel free to comment on that.
Sincerely,
Johan Hoffmann
PM, Microsoft
Addition of item "on hand" quantity to current operations report
Incorporating the "on hand" quantity into the current operations report in D365FO enhances visibility and control over inventory, leading to improved operational performance, cost savings, and increased customer satisfaction. This data-driven approach helps organizations stay agile and respons...
Production Floor Execution - Don't notified good quantity in each operation
In the "Production Floor Execution", when reporting the progress of operations, the display always appears to indicate the number of good parts that have been manufactured.
Ability to maintain more than one active ingredients in a production formula
In batch order, system should be able to populate and consume multiple active ingredients. Finished good should have provision to add multiple base attribute so that system acknowledge multiple active ingredients, not as a proportion or linked with single base attribute.
Thank you for your feedback. This is a great suggestion!
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,
Johan Hoffmann
PM, Microsoft
Restrict locations to pick item in production control
with one of the customer we are facing the issue with picking the BOM Item during estimation and explosion. currently the standard system picks item randomly from any location while we need to restrict the system not to pick from specific location.
Ex- we have a production order which r...
Thank you for your feedback. This is a great suggestion!
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,
Johan Hoffmann
PM, Microsoft
Administrator
Thank you for your feedback. We need some more details to understand your suggestion better. Can you please help us by answering the following questions?
Please provide a detailed scenario where you see the unwanted transactions generated during Ending the production order.
Sincerely,
Johan Hoffmann
PM, Microsoft