Licenseplate label (re-)printing from production floor execution:

When printing a license plate label from PFE we would like to use the default label printers functionality.

We would also like to use the change printer functionality, because when a label was originally printed via PFE on a label printer then we should have the possibility to do a reprint from the newly selected printer. In the current situation this is not possible and the label will be printed on the original printer.

Proposed solution: Add a resource to printer mapping to support PFE use cases

In the Tech Talk it seemed everything in the demo had to do with the Order to Cash/Sales side of trade to supply pricing, discounts, rebates, etc. to customers on sales transactions. 80%+ of the functionality demonstrated is needed on the Source to Pay/Procurement side in managing pricing and rebates with Vendors. It is great to see the progress on the sales side but without nearly the identical functionality on the Vendor side this does not meet the needs of most Distributors and many Retailers.

This also includes providing the various Pricing Attributes functionality on both the Customer and Vendor side as well. Here is an example that shows the extent of the capabilities leveraging both the Customer and Vendor side together for what is referred to as a "pass through rebate".

• In this example the organization using D365 is the Distributor. A computer manufacturer sells their computers normally to the Distributor at $1,000 a piece. Rebates are not determined during the procurement transaction. When the Distributor sells these laptops to their Retailers the Manufacturer has made an agreement with the Retailer and Distributor that for Retailer A they will provide a $50 rebate per laptop but for Retailer B they have approved a $100 rebate. Upon the Sales Invoice being posted a Customer Discount (included in price) or Rebate (accrued for later consumption) will be generated for the $50 or $100 according to the Retailer. At the same time a Vendor Rebate will be generated to accrue the receivable from the Vendor for each of the laptops sold for $50 or $100 according to which Retailer purchased the goods. The Customer Discount/Rebate is funded by the Pass Through Rebate with the Vendor. This would need to be supported for both inventory that has been received by the Distributor as well as inventory that is on Vendor Consignment that is still on the Vendor's balance sheet until sold.

When a Quality order is created as a result of a Rejected Quality check on the mobile device, the batch number is missing in the quality order (despite the item sampling associated with the test group having Per Batch number checked and product has reservation setup with batch above).

It would be more interesting if the batch number were linked to the Quality order created so that, among other things, batches could be tracked using batch disposition codes.

Issue 964515 - By design

While creating a manual production order Location and Inventory status are not captured from the defined Active BOM

On

Creation of manual workorder the Bom with many lines need to be added again

manually with Location and inventory status every time

In Italian legal entity, we can follow the following setup to print packing slip with transportation delivery details: Post and print a packing slip with transportation delivery details for Italy - Finance | Dynamics 365 | Microsoft Learn

However, we cannot post packing slip in transfer orders, we would like a way to print transportation delivery details when processing transfer orders as well.

The value (Amount) and the Amount field on the product receipt journal display the same exact value in the accounting currency, although the help text of the amount field indicates that this should be displayed in the transactional currency (which is not correct). The value of the amount field should be changed so it's displayed in the transactional currency . Currently there is no notion of the received amount in the transactional currency on the product receipt journal.

In Procurement and sourcing > Purchase orders > Purchase order follow-up > Open purchase order lines, the information in the grid only displays the vendor account number and not the vendor's name. It would be greatly beneficial for anyone using this report to have the vendor account name able to be displayed for quick reference. The vendor's name is only available on the Header and not the Lines for a purchase order. Our buyer's reference the open purchase orders report daily for vendor follow-up and accuracy of live orders across the network.

Extend the functionality related to Unified Pricing Managements also to Sales Agreements. When a sales agreement is of the "Product quantity commitment" type, the system should read the "new" price lists, currently it reads the "old" price lists, forcing you to have two populated price lists. It should remain possible to manually change the price on the "Sales Agreement"

In the subcontracted overview the vendor account that is viewed in the grid is the vendor account for the BOM line, not for the purchase order connected to the production order.

Changing the vendor account on the purchase order will then not be reflected in the subcontracted grid/overview.

Changing the vendor account on the BOM line on the production order will change the vendor account in the subcontracted overview/grid.

Working in this overview means that you can start and also do report as finished the production order from the view, but not change the vendor on the BOM line or add the vendor account field for the purchase order to be viewed in the subcontracted work view.

If you have more than one subcontracting vendor that can do the same job this will be time consuming and not so good way of working on daily bases.

Idea:

1. The button BOM line in the subcontracted work view should link you directly to the BOM line so you can change the vendor account for the line.
2. Add the vendor account to the fields and grid in the subcontracted work overview/grid so you can view the vendor account from the connected purchase order

The Pricing Management module (both the current to-be deprecated SCM- and to-be released Unified Pricing management modules) includes a discount feature, called Quantity discount, that allows companies to set up a rule where a discount (expressed as a percentage or amount) will apply to individual order lines, but be based on the order quantity (as totaled across all lines, also with different product SKUs, that share the same unit of measure) being equal to or above a preset minimum threshold. Such a logic works well in business contexts where most SKUs are being sold in the same units of measure, so that all product lines’ quantities on the order can be included in total quantity summation. In addition, and related to the previous point, it is also a condition of the quantity discount applicability that the unit of measure in the discount rule setup must match the unit of measure on the order line for it to quality for that discount (and contribute its quantity to the calculated order total).

For manufacturers in CPG industries, particularly food and beverage, the following two factors make the Quantity discount feature unfit to their commercial needs, if used out-of-the-box:

1. products are sold in different (packaged) units of measure, e.g. beverages are in kegs, cases, bottles etc., all potentially being entered on the same sales order.
2. for this very reason, the minimum order quantity as a qualifier for a quantity discount given to distributors is often expressed in a shared unit of measure, e.g. hectoliter. However, and importantly, products are never sold in hectoliters, i.e. the quantity on sales orders will never be specified in hectoliters.

The Quantity discounts as well as potentially other types of discounts are expected to have a Unit Conversion option (similar to the Allow unit conversion on the Trade agreements; or built-in functionality in the Rebate management deals) to support quantity discounting practices common in the CPG industries.