Dynamics 365 Supply Chain Management

The request is to enable the vendor collaboration portal for shipping company vendors, so that it can issue invoices linked to voyages.

With reference to LCS Issue823033 

When Reporting currency and Transaction currency differ, while the postings occur on different dates, it has been observed that the 'Landed cost Goods in transit' is not correctly cleared, voucher transactions being unexpected.

The difference arises due to the exchange rate on the arrival journal date being different from the one on the date of the Purchase Order Invoice.

Dual Currency and its consistency, is highly needed in business processes, being a very common need.  

Many business processes would highly benefit from and enhancement in this area.'

When a supplementary item is provided free of charge in an intercompany scenario with direct delivery in DEMF, purchase and sales prices are automatically populated. This occurs regardless of the pricing parameters configured on the intercompany accounts.

it would be helpful to fix the issue and not populate the unit price of the supplementary item that is suppose to be free of charges

this impacting the business This behavior disrupts the intended pricing model and can lead to financial discrepancies, affecting the accuracy of cost allocations and profit margins. This impacts the efficiency of the order processing workflow and results in erroneous intercompany invoicing, ultimately affecting intercompany agreements and internal financial reporting. Since there are different items that may contain 2 to 3 supplementary items, the impact it has on all financial & reporting aspects is unneglectable. item is supposed to be provided for free as part of an intercompany transaction between different parts of the business. However, the system is incorrectly charging for this free item on both the purchase order and the sales order, even though it should not have a price. This issue disrupts the normal process, making it appear as though the business is paying for and selling the item when, in fact, it should be free of charge.

The 'Edit selected rows' feature on the SalesTable form does not update all Intercompany Sales Lines as expected. We would like to have all the Bulk grid update feature update ALL the records and not just random lines instead.

To be able to switch off the need for Quality Control on Item / Supplier combination after x sampled pieces, there should be some kind of expiration quantity on the Quality Association which makes it possible to set up Quality Control for the first x received pieces. So expiration of the association not only on date, but also on qty tested.

Starting with version 10.0.46 / Platform Update 70, the staged icon on the "All loads" form will be fully removed from the standard functionality, as noted in LCS bug 1037976.

We kindly request Microsoft to reconsider this change. The staged icon is widely used by many organizations and plays a vital role in tracking shipments. Its removal will require businesses to implement customizations to restore this functionality, potentially impacting operations and their business requirements.

Currently, when a purchase order line is cancelled, any markups or charges that were previously associated with that line remain included in the purchase order totals. This leads to an incorrect total value, as the markup from a now-irrelevant (cancelled) line still contributes to the PO total calculation.

This behavior can cause confusion and inaccurate financial reporting, especially when users rely on the purchase order totals for cost validation or approval processes.

Expected Behavior:

When a purchase order line is cancelled, any markups or charges linked to that line should be automatically excluded from the purchase order totals, ensuring that the total value accurately reflects only the active lines.

Business Impact:

Prevents incorrect financial totals on purchase orders.

Reduces manual effort needed to review or remove markups after cancellations.

Improves accuracy and transparency for users handling large or complex POs with multiple lines and charges.

When creating a purchase order for a specific warehouse and then attempting to create an item arrival journal for a different warehouse, the system currently blocks this action due to insufficient transactions with the status ordered/registered on both the UI and the warehouse mobile app. It would be beneficial to have a feature that allows for changing the inbound warehouse, as shipping containers may need to be rerouted to different warehouses based on various business factors.

In the Asset Management module, it is possible to automatically create a pending asset record when a purchase order is placed for an asset item, but there is no matching functionality for production orders. Some businesses have an asset-centric process where they will produce assets and then install and maintain them at customer locations, so the ability to convert a production order to an asset would help streamline this process.

Title: 

Improve Overview Costing Accuracy After Changing Indirect Cost Rate for Production Orders

Description:

an issue in Dynamics 365 Finance and Operations where the overview costing becomes incorrect after changing the indirect cost rate for production orders. This issue has been acknowledged by the D365 Product group engineers and marked as "by design" (Issue 793402). The problem arises because the system recalculates costs based on the most recent price during inventory closing, and it is unable to distinguish the actual price used at the exact historical time point.

Problem:

When the indirect cost rate for production orders is changed, the overview costing does not reflect the accurate costs. This discrepancy can lead to incorrect financial reporting and decision-making, as the recalculated costs do not match the historical prices used at the time of production.

Remarks:

The current design recalculates costs based on the most recent price during inventory closing, which does not account for the actual price used at the historical time point. This limitation affects the accuracy of cost reporting and can cause confusion for users relying on precise cost data.

Proposed Solution:

propose an enhancement to the costing mechanism in Dynamics 365 Finance and Operations to ensure that the overview costing accurately reflects the historical prices used at the time of production. This could involve storing and referencing the actual prices used at specific historical points, rather than relying solely on the most recent price during inventory closing.

Benefits:

• Improved accuracy in cost reporting
• Enhanced financial decision-making based on precise cost data
• Reduced confusion and errors in financial statements