When allocate cost for multiple voyages, it will show multiple voyages in the field of description instead of voyage id. customer expected if there any way did not combine the voyaged info together. Customer mentioned that the old- landed cost module support the function and user could add each vendor invoice journal line manually.

Business impact:

When show as multiple voyages, It is posting combining all into one transaction in GL and hard for customer to do reconciliation. Such as when try to check account balance, could not tell how much portion is belong to which voyage.

Business scenario:

Customer could not apply the work around to create separate voyage invoice journal for different voyages due to following scenario.

Scenario details:

We have three purchase orders for same Vendor from Australia. We may have 3 voyages. For the vendor know that the 3 PO is for the same customer, so the vendor will ship the 3 PO to the same shipping company. The shipping company will only give one invoice for it belong to the same customer, so we will only create one invoice journal for the 3-voyage cost.

When creates a new purchase order for one item and with following lines, the PO's delivery terms FOB marked with Goods in transit management.

Line 3: the Variant number is VN-000156, size: L

Line 2: the Variant number is VN-000154, size: M

Line 3: the Variant number is VN-000156, size: S

when try to create a new voyage. On Voyage editor form, we could see the three lines to be select as following, insert a new column: Size and then sort the column Size from A to Z and then sort from Z to A

Actual result:

The result is the same and not sorted.

Expected result:

The result could be sorted the same as purchase order line.

D365 Purchase Order Cancellation Behavior is inconsistent – when it comes to cancelling purchase orders. When Purchase Orders are cancelled via the Cancel Button on the Ribbon (Purchase Order -> Maintain) the Purchase Order is only pushed to ‘Approved’ status. However, if a user cancels all lines via the Update Line -> Update Delivery Remainder -> Cancel Quantity then the Purchase Orders is auto-approved and auto-confirmed.

Currently line cancellations that lead to full cancellations of Purchase Orders are in confirmation status and customer could not generate a confirmation journal.

Currently the financial dimension is disabled on purchaser order header when the purchaser order is partially invoiced. Customer requests the purchase order header' financial dimension could be updated when purchase order is partially invoiced, customer could click no button to not update the purchase order line financial dimension.

Customer business scenario:

Currently purchase orders created from purchase requisitions do not put dimensions on the header - this is standard functionality. Any orders from MRP do not put dimensions on the header - also standard functionality.

When customer need to modify one of these purchase orders. Eg to change pricing or add freight. The user clicks on PO > Request change and edits the order. If there have not been any invoices, then they can add the financial dimension: department on the PO header and put it through workflow. no problem. 

If there has been a partial invoice and customer need to edit the PO in order to process the final invoice, then they can't edit the department on the header. The financial dimension is not editable when purchase orders are partially invoiced. for customer use the info from financial department to find proper approve in their workflow, If they try to submit to workflow then it fails because it can't find an approver without the department. They are stuck! 

Currently they have to modify the workflow every time to allow that particular PO number to auto approve. This is NOT a long-term solution. 

Release products physical product dimensions Volume is calculating incorrectly. The calculated Volume ignore the Length unit and Volume unit. It should be as per below: 200mm x 440mm x 55mm should be 0.48 m3

Current behavior:

Currently when set the coverage period of 30 days. the planned purchase orders are not merged to be one planned purchase order with requirement date within 30 days.

As the minimal requirement quantity has been set for the item but planned purchase order still create with quantity below the minimal require quantity.

Expected result:

Hope the behavior will works the same ad demand forecast which will consider for coverage settings and obeys the min order qty as well as coverage group.

We have new function of shipment consolidates, while the policies are only available for sales order and transfer order. There is none for purchase order. we have checked that the shipment consolidation has been disabled for inbound shipments due to following issue: Details for issue 518152 (dynamics.com)

Our customer wants this function to be implemented in the near further and it will also benefit other customer which has the same business need. and following is the similar ideal has been posted before Microsoft Idea (dynamics.com)

After purchase order is confirmed. User will add a note attachment or edit the Note. The confirmation button is not enabled, and user could not confirm the purchase order. and the update will not be included in the confirmation journal. Customer has customization report and hope there would be an option for user to select the update in the attachment could be included in the purchase order confirmation.

Issue description：

There is an error message that auto charges need to be applied to the PO lines when confirm the PO with Auto charges set as percentage on header. Charges set on purchase order header with category parentage is requested to be allocated to purchase order line when confirm the purchase order.

Product team suggestion:

This has been working like it does for a long time, all the way back to AX 2012.AX 2012. and the design most likely due to the accounting distribution and it is an feature limitation.

Product team suggest this is a great candidate for the idea's portal.

.Details for issue 774002 (dynamics.com)

Customer wants to build a packing hierarchy (such as Pallet contains Box) when using outbound sorting when release sales order. when perform sales picking, one LP is generated, then during outbound sorting, there is another LP been generated. for the two related license plate on license plate form, we could see the two fields: license plate level and parent license plate have no value.

Customer expects the two LPs has parent and child relationship and would be easy for tracking.