Laura Cojan SUPPORT ENG

When an item is set to ‘Stopped’ at ‘Default order settings’ level, the creation of inventory transactions will be halted per the intentional implemented functionality.

However, while adding a line to a sales agreement, upon adding a new line, the system will not issue an Infolog per intent, unless a sales order is released from the sales agreement.

There are customers who would benefit from a change in the way the process is implemented, which would provide the option of triggering the Infolog, upon adding the sales agreement line, rather than when an inventory transaction is attempted to be created.

The current way the system is behavior is causing in many fast-operating businesses, disruptions, since, it is allowing users to create agreement lines, and only later notice the items added are for stopped products creating inefficiency by performing multiple steps e.g. removing the items and unnecessarily creating sales agreements. 

With reference to LCS Issue: 1023238

When invoicing sales orders with summary update based on packing slip quantity and late selection enabled , and process is executed in batch, the invoicing fails in error due to incorrect summary update calculations. 

Error experienced:

♣ 'The line has quantity 1.00, and total delivery of 2.00. This results in 100.00 percent over delivery of the line. The line only allows over delivery of 0.00 percent. You can adjust this value on the order line.'

This issue has a significant impact on business operations. The inability to invoice leads to delayed payments, which in turn affects the companies cash flow. With over 5000 lines requiring invoicing daily, this problem presents a substantial operational challenge.

Customers, using a similar business context configuration need, would greatly benefit from having the behavior amended or adapted as such to best accommodate the daily operations.

With reference to LCS Issue 991106:

Issue Description

When change tracking is enabled on Sales Order Header and Sales Order Lines entities, and the export is performed using “Incremental push only”, the export job does not include the sales order lines once the related invoice has been paid.

The export works as expected when the sales order is created, updated, or invoiced. However, it fails to capture the necessary data after payment is completed.

Business Impact

There are customer business requirements in which customers rely on exporting sales order information to integrate with other systems. These systems require accurate and complete data to manage customer sales orders effectively. Without this information:

Sales orders in the production system remain open until confirmation of invoice payment is received from D365.

Certain downstream systems cannot initiate legal tasks related to paid services without confirmation that the invoice has been settled.

This delay directly impacts operational efficiency and may result in revenue loss, as critical processes cannot proceed without payment status updates.

All affected customers and associated revenue streams are impacted.

A change in the current way the system is intended to work would be of great value for customers using a similar business process and requirement.