Dynamics 365 Supply Chain Management

It would be preferable to have default financial dimensions on the transfer order lines to be filled in by a user, so they can be automatically populated when a transfer order is sent/received.

Currently, when we create a purchase requisition with the following settings:

• Insert item X with an active purchase agreement for vendor A
• Insert item Y without any purchase agreement, also choose vendor A

-> When we generate a purchase order from the above purchase requisition, it will create 2 purchase orders: 1 with item X and 1 with item Y, even though both are using the same vendor A.

Hence, we would like to request development to ensure that this business requirement is fulfilled by allowing one purchase order to be created from a purchase requisition that includes one item under a purchase agreement and one item that is not, given that they have the same vendor.

This is to record the Yammer group - Pricing management request:

The Rebate management for Vendor rebate on sales should support the attribute-based in Pricing management.

"The scenario at the beginning of this thread is extremely common and in fact its borderline tale stakes for wholesale distribution. Wholesale ditributor have extremely complex pricing, as complex as retail, and vendor rebates are typically tied to some sales program.

In Transfer Journal (Inventory Management > Journal entries > Items > Transfer) the Line details > Inventory Dimension > TO Inventory Dimension > Inventory Status is disabled/greyed out, which limits the ability to update the Inventory status in the transfer inventory process.

Enabling this would allow for greater flexibility and align with the overall solution where Inventory status updates are allowed in the Transfer Order receiving process.

A new extension of the "Rename item number" function is required to also rename the product number if the product has not already been released in other legal entities. With the functionality in preview 10.0.42 it is possible to rename only the item number.

• The customer tries to submit a workflow it reflects with the error message below:

Stopped (error): Accounting distribution validation failed. Please recall purchase order workflow and rectify accounting distributions. This action can only be completed after the line number 10 is fully distributed.

• While checking the lines we found all lines are distributed.
• Throw investigation we found a raised fix request related to that error, it will not be fix and there is a workaround had been provided
• Our customer tested the workaround that had been mentioned in the fix request, and it did not resolve the issue as expected, please find the feedback below:

 if we Disable the Parameter Auto Calculate Totals and Accounting Distribution from Accounts Payable Parameters -> General -> Purchase Order Workflow, this will also affect all PO's with actual errors in distribution that we would like the system to stop. For example if a PO is missing a financial dimension as Department, we need the PO to stop in WF and give a warning to correct the PO before approval. If this stop/validation is skipped, we will have issues later in the process when trying to post PO against vendor invoice. The error we have reported now is a bug and should be taken care of. 

• As a result for the above please advise with another workaround as the mentioned did not fit our customer gap.

Add a new Data Entity in the Data Management addressed to import the 'Included in configurations' (ConfigChoice) within the Bill of Materials (BOM).

Concerning all forms in which label layouts are created and maintained. E.g.

- wave labels layouts

- container label layouts

It is very impractical to create ZPL codes in these tables. You are forced to work with external programmes (Labelary, ZPL designer, ...), which requires constant copying and pasting, which in turn is time-consuming and error-prone. Furthermore, the text fields in which the ZPL codes are maintained are usually too small for common ZPL code lengths, which reduces the overview. 

If you could extend the label layout forms so that you can see the finished label directly (similar to Labelary.com), this would be already a huge step forward. 

If it were also possible to see not only the data field ‘placeholder’, but also validate whether the data field is correctly linked via the label layout data source, this would save a significant amount of time when testing labels designs. (particularly beneficial if label layout data sources consist of several table joins)

Currently :

I have a PO with 2 PO lines. The 2 PO lines do not have the same Delivery Dates.

Load is created at the Reception, as I am using the "Receiving Completed" setup.

The vendor finally delivers both PO lines together.

I receive the 2 PO lines.

It generates one single Load -> ok

But I get 2 Shipments, one per PO line. -> Not Ok

If the delivery dates of the 2 PO lines would have been the same, I would have get the both PO lines in the same Shipment.

As an impact, if I have 2 Shipments, I have to enter two times the same vendor Packing Slips ID. Furthermore, having the same Packing Slip ID on 2 Shipments means that if I have a setup which "Check for product receipt number use"= "Reject duplicate" in Procurement and sourcing parameters, the Product Receipt process will fall in error...

Requirement : create just one shipment on an inbound load created at reception, even if the Delivery dates of the differents PO lines are differents 

Landed cost

Context:

I created a purchase order with a unit that is different from the inventory unit of the product

Item's inventory unit = Metric Ton

Purchase order's unit = Cubic meter

The conversion exists therefore, the system accepts to create the line in the purchase order with this unit.

Conversion is: 1MT for 2 cubic meter

I placed the purchase order on a voyage. On the voyage, I estimate a landed costs of 10 EUR per PCS (category : PCS).

As my purchase order line have a quantity of 10 cubic meter, I am thus expecting an estimated cost of 10 cubic meter multiplied by 10 EUR, which makes 100 EUR in cost inquiry.

However, the system calculates the costs based on the inventory unit of the product, i.e. MT and thus the cost inquiry gives me a cost of 5 MT multiplied by 10 EUR, which makes 50 EUR thanks to the conversion.

We would like to change the behavior so that the system can take into account the purchase unit rather than the inventory unit only.