Dynamics 365 Supply Chain Management

Ability for a user to select time out session duration (currently 60 minutes) preferably longer - e.g. 120min

When a standard cost has been activated, now 365 create a revaluation for WIP only for "Material consumption" and not for "Reported as finished" quantity. In this way we cannot calculate the correct WIP by production posting (Material consumption + Route consumption + Indirect - Reported as finished). Also we don't have the balancing between production posting and general ledger.

It should be better if we can have the "Reported as finished" production posting regarding revaluation after new standard cost activation.

In service update 10.0.17, a feature was added named 'Enable creation of a vendor invoice journal when discarding a freight bill', which is enabled by default.

Previously, discarding a freight estimate did two things. First it would create a vendor invoice journal, which isn't needed. Second it would update the associated PO lines to reflect the discarded estimates by creating negative charges to reverse the estimate, which is needed.

The update changes both of these features though. It prevents the vendor invoice journal creation, which is good, but it also prevented the PO line charge update, which is bad because then inventory value is overstated. When it is sold, COGS is also overstated, reducing profit.

Microsoft has agreed to look at fixing this in a future deliverable to only prevent creating the vendor invoice journal but continue to update the PO line charge. The feature is not of any use since it will cause problems with a company's income statement. The Idea is to separate those two functions, so vendor invoice journals won't be created but PO line charges will still be updated.

Please parameterize an option to have these fields editable on the FnO (Application-Side) instead of pushing changes via SQL Scripts

Fields: SplitSitePickingList & SplitSitePackingSlip

Table: SalesParameters

SAP: Accounts receivable > Setup> Accounts Receivable Parameters > Summary Update > Split based on

When activating a new standard cost for items in d365, the system posts adjustments that split the inventory transactions into separate line with varying quantities for the corresponding items and results in created date and time alteration.

As a consequence, the system modifies the original "created date and time" of the inventory transactions. This alteration can disrupt item traceability for customers who rely on the original creation timestamp for traceability and compliance purposes.

Go to Asset management > Assets > All assets.

Select any single asset and under Maintain, select "Install asset at Location". We are looking for a way to install multiple assets at single locations by allow selecting multiple assets before selecting "Install asset at location" button.

This will make asset installation/transfer easy and user friendly for bulk assets.

In D365 F&O DDMRP Functionality – Planned Orders not getting generated for Full Coverage Time Fence. Instead, a single planned order is getting generated for the current time period only.

Actual Result

Only 1 Planned purchase order is generated instead of 12 different Planned purchase orders for the respective Coverage time fence of 12 months (365 days).

Expected Result

The generation of 12 separate Planned purchase orders corresponding to the setup Coverage time fence of (365 days) 12 months.

1. Business Scenario

Process Overview:

The current intercompany process involves transactions between two legal entities: MHNZ (New Zealand) and MHDE (Germany). The process follows a direct delivery model where MHNZ creates a Sales Order, and MHDE creates a corresponding Purchase Order.

Issue Statement:

Once the Sales Order invoice is posted in MHNZ, users manually extract the invoices and send them to MHDE for manual Purchase Order invoicing.

This manual process is time-consuming, especially when handling high transaction volumes.

The risk of missing invoice postings increases during month-end financial close, leading to operational inefficiencies and potential financial reconciliation issues.

Expected Outcome:

The system should automatically post the Purchase Order invoice in MHDE as soon as the Sales Order invoice is posted in MHNZ.

This automation would streamline intercompany processing, reduce manual effort, and improve financial accuracy.

2. Current System Limitation

After thorough investigation, we identified that D365 FnO does not currently support automatic status updates for intercompany Purchase Orders to "Invoiced" when the corresponding Sales Order is invoiced.

Findings:

No direct system functionality exists to automate the intercompany invoicing process between two legal entities.

Batch jobs and FIN team consultation confirmed that available automation options are limited and do not fully support periodic intercompany tasks.

Manual intervention remains necessary, causing delays and errors in financial reporting.

3. Proposed Enhancement

Feature Request:

Enable an automated intercompany invoice posting mechanism in D365 FnO, where:

Once a Sales Order invoice is posted in one entity, the system automatically triggers the corresponding Purchase Order invoice posting in the other entity.

The system should allow configuration for legal entities to enable/disable this automation based on business needs.

A monitoring dashboard or log should track automatic postings for transparency and troubleshooting.

4. Priority & Business Impact

Given the high transaction volume and criticality of intercompany financial accuracy, this enhancement is highly beneficial for businesses operating in multiple legal entities.

We kindly request the PG team to consider this enhancement request for future updates to D365 FnO. If feasible, we would appreciate any guidance on potential roadmap inclusion or alternative solutions within the product framework.

Thank you for your time and consideration. Please let us know if additional information or use case details are required.

Best Regards,

In the context of demand forecasting in D365 SCM, we manually import a large volume of forecast lines each month that require allocation. Currently, the system does not automatically distribute the monthly forecast quantities into daily values based on the period allocation key we have configured. Instead, this allocation must be performed manually, which is time-consuming and impractical for handling large datasets.

I would like to ask for a new feature that would enable D365 SCM to automatically allocate monthly forecast quantities into daily values upon import, leveraging the predefined period allocation key. This automation would streamline the forecasting process, reduce manual effort, and improve overall efficiency.

to streamline the inbound process for vendors that don't provide an ASN, we will create an inbound load, based on the vendor packing slip information. We then print a load document in a uniform way, with all required barcodes so that the warehouse worker can use it for Load item receiving. The quantity entered on the load line is updated with the quantity from the vendor packing slip. In a lot of cases, this qty is more than ordered. However, the system does not allow this.

Even if over-delivery percentage is filled in on the load line (e.g.1000%) it is still not possible to enter a load line quantity that is greater than the PO line quantity for which the load is created. The system shows a warning message: "The quantity is greater than the quantity left to load for load line for Purchase order, order number PO..." but in fact this is treated as a blocking error (not able to save the load line). This is inconsistent with how the same load would behave when a packing structure is added for that inbound load. When adding a packing structure, I can create a packing structure line for a qty that is more than the load line quantity (and thus more than the PO line qty). When scanning the label from the packing structure (LP receiving) the packing structure quantity is registered and the work created qty on the load line is updated with the qty from the LP in the packing structure. When the load is 'receiving completed' the load line qty is updated with the packing structure qty. If it is possible to allow this via Packing structure, it should also be allowed to update the qty directly on the load line. If that requires an auto-update of deliver remainder (behind the scenes) to make this technically work, then that's probably how it should be done.