Dynamics 365 Supply Chain Management

Currently, you can only add financial dimensions to the lines on the inventory movement journal. However, the inventory movement workflow editor only allows you to specify conditions based on the financial dimensions specified on the header.

Report : "Calculation details for cost and price" - Multilevel details are missing

Product and version: Finance and Operations

PROBLEM

Report : "Calculation details for cost and price" - Multilevel details are missing

To be able to generate multilevel cost

.

The system currently does not allow the creation of a Discount Trade agreement based on Line Discount Group unless the desired Line Discount Group is already assigned to at least one customer.

The Price Engine, also, does not consider the Line Discount Group specified on the Sales Order, and instead defaults to the one assigned to the customer master record, limiting flexibility for exceptional cases (e.g. large sales, agreement for the specific order, etc), generating inconsistency with the D365 logic.

The system should:

• allow the creation of Discount Trade Agreement even if the Line Discount Group is not assigned to a customer
• restore consistency with the standard logic and consider the Line Discount Group at Sales Order level

when using the PACK INVENTORY INTO CONTAINER , we would like to have the Ability to hide the "Remaining Quantity to Pack" on the RF Device in order to change this to a blind pack. this would help us to ensure that quality is being done.

For distribution and manufacturing companies that have inventory located in multiple physical warehouses, the ship to address of the customer order may dictate the ship from site/warehouse if the same product is stocked across multiple locations. For example if the same item is stocked in a warehouse in Mississippi and in Oregon, if a sales order is entered with a delivery address in Washington the stock in Oregon should be used to fulfill the requirement. A single customer could have multiple ship to addresses across the country so defaulting the site and warehouse at the customer level is not ideal. In current D365 the only way to accomplish this is to have a different customer for each delivery address.

Ideally the site and warehouse would default based upon the delivery address and not the customer.

Currently, SSRS reports on out platform fails to handle a large number of records. When the number comes to millions, the reports will take extremely long time to proceed the reports. And, in many cases, the report will fail.

One example can be mentioned is Inventory settlement adjustment report. More details can be found at: LCS > Issue 979603. The report data provider class loops through all the found records and insert them all into temporary table for the printout. Yet, when the number of loops becomes too big, this will not work.

Hence, I would like to suggest an idea of performance improvements for SSRS reports in general.

In the location directive, you can configure the strategy "Location aging FIFO" for picking. The system checks the aging date of the location. However, the aging date is updated whenever you move a license plate into a location. The disadvantage is that if you add multiple license plates with different items to a location, the aging date gets updated each time a license plate is added. Let me explain with the following example:

• Item X001 is in location A001 with LP001 dated 1-05-XXXX.
• Item Y002 is in location A001 with LP002 dated 1-10-XXXX.
• Item X001 is in location A002 with LP003 dated 1-07-XXXX.
• Item Y003 is in location A002 with LP004 dated 1-09-XXXX.

In the above scenario, the aging date of location A001 is 1-10-XXXX, and the aging date of location A002 is 1-09-XXXX. If you release a sales order or transfer order for item X001 for picking, Dynamics will propose picking from location A002 because its aging date is older than that of location A001, even though the license plate of item X001 in location A001 is older than that in location A002.

It would be very helpful to have an additional location directive strategy that checks the aging of the license plate in combination with the item, rather than just the aging date of the location.

At our customer we create the internal and external documents by means of the electronic reporting workspace.

As we have the requirement to print GS1-bar codes on the documents we tried setting this up.

However, we noticed that only a limit amount of barcode rendering formats are available of which GS1 formats are not one of them.

We think at least the supported GS1 bar codes provided by the Microsoft documentation should be available in electronic reporting.

And as GS1 format is becoming more the industry standard multiple customers might benefit from this.

https://learn.microsoft.com/en-us/dynamics365/supply-chain/warehousing/gs1-barcodes

For the customer, it is basic functionality to be able to delete old/irrelevant records in the system, however, deleting and old/irrelevant engineering BOM version in local company, when using ECM, seems to be impossible.

Customer aware of this old bug [674851] but having a design leading to impossible scenarios with data inconsistency is not optimal.

If you remove approval and try to remove the old BOM in USMF, this is impossible.

Deleting in USMF does not work since it is not the engineering company and deleting in DEMF and releasing does not do anything to the old BOM, since it only releases the active version of the BOM.

The expectation is that either release from local company includes deletion of the BOMs deleted in engineering company, or deletion of the BOMs in engineering company also deletes it from the local company (since engineering is normally supposed to be the master for BOMs when ECM is used) or, simplest, there is a way to manually delete a BOM in local company. When saying BOM, it means BOM version and BOM.

• When creating non conformances from a batch the site will not fill automatically

• We expect when we create a non conformance from a batch the the site will automatically be filled with the correct info

• When created directly from the non conformance form it is working as expected.