When we enable the new feature Price management in version 33, then a new menu item – Complete - appears on the sales order detail form. The sales order header is then created with label set to “Do not process = Yes”.

The sales order needs to be “Complete” before you can run Order confirmation, Packing slip, etc, or Release to Warehouse. And then you need to use Modify if you need to change or add more lines.

Scenario:

1. In the procurement and sourcing parameter > General > Calculate purchase order delivery date based on lead time and working days is "Yes".
2. When create a new purchase order, on the items where the Vendors do step up the trade agreement on the items with lead time plus the working days.
3. In the PO lines > Delivery fields lead time is always "0" and not updated from the trade agreement.

Expectation:

If the lead time is displayed, users will immediately know the lines Requested ship date taken how many days in calculation.

Business Justification:

The display of the lead time is able to view and immediately to know the lead time taken when purchase on the items. If the lead time is wrongly configured and users can immediate rectified and confirm with their buyer.

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"

Our client has standard item coverage and warehouse item settings for product templates which they would like to be inherited to the newly created items.

Currently they would have to create a released product and separately update the item coverage and warehouse item settings. It would ease some of their work if there is a parameter which can enable this functionality.

Thanks!

Current Limitation:

In D365FO, the only way to control automatic cycle count approval is through parameters set at the worker level. This approach is too broad and fails to account for the varying financial impact of discrepancies across different products. High-value items, for example, should be handled with much greater scrutiny than low-value items.

Proposed Enhancement:

Add functionality to set cycle count approval parameters at the released product or product variant level. This would allow businesses to define specific thresholds for automatic approval based on both quantity and value deviations tailored to each item.

Why This Matters:

• Critical Risk Management: High-value items should not be automatically approved if even minor discrepancies occur. Allowing item-level control ensures that these items are flagged for manual review, reducing financial risk.
• Operational Efficiency: For low-value items, automatic approval of minor deviations can streamline operations, freeing up resources to focus on more critical areas.
• Flexibility and Precision: Businesses can fine-tune their cycle count processes, aligning them more closely with the financial significance of their inventory, leading to more accurate and reliable inventory management.

Call to Action:

Implementing this feature would greatly enhance the control and efficiency of inventory management in D365FO, making it a valuable addition for all users. By allowing item-specific parameters, we can better manage risks, optimize resources, and improve overall accuracy in the cycle count process.

• Existing functionality is that a Vendor can upload a Purchase order Invoice via their workspace. If there is a Vendor invoice workflow configured Vendor will submit Invoice to Workflow.
• Under non-collaboration workspace scenarios the Vendor invoice workflow can be configured to auto post if the Matching process passes.
• However, if the Invoice is created in the Collaboration Workspace and submitted to workflow, the standard functionality does not behave in the same way and the matching fails and the AP Clerk must manually match and post the invoice.
• This was reported as bug but Microsoft state that the behaviour is by design. The rationale behind this design is that “it allows the Vendor the possibility of adjusting invoices even after their initial creation”.
• What is required by Dynamics customers is the introduction of a parameter or indicator that allows Vendors to specify whether the invoice is complete when they upload the invoice in the Collaboration Workspace. If this parameter is set to YES this signifies the Vendor has confirmed the Invoice is correct and the system will then automatically initiates the submission for the automatic matching process.

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