Description of the Flaw:

Currently, if a there is a reservation set up between a sales order and a purchase order, the system issues a generic warning when a user changes the requested receipt date on a purchase order. The warning states that the date change may break existing reservations. The warning is issue regardless of whether the date change will actually cause any reservations to be broken or not. It does not explicitly notify the user that the reservation has been broken or invalidated. This lack of clear feedback can result in users overlooking broken reservations, leading to potential fulfillment errors. The constant issuance of the message also causes users to ignore it so they may not notice when a reservation is actually broken.

Business Context:

Accurate reservation management is critical for operational efficiency, order fulfillment, and compliance with customer delivery commitments. In environments where reservations link sales orders to purchase or transfer orders, users rely on the system to maintain and communicate reservation status. Ambiguous warnings increase the risk of missed shipments, inventory discrepancies, and manual rework, negatively impacting customer satisfaction and business performance.

Suggested Expected Behavior:

The system should actually recognize when a date change will actually break a reservation and should only warn a user when it will be broken. If the change will not cause the reservation to be broken, there should be no messaging at all. When a date change causes a reservation to break, Business Central should provide a clear, actionable notification to the user. The system should:

• Explicitly state that the reservation has been invalidated.
• Identify the affected sales order(s) and item(s).
• Offer options to resolve the issue, such as re-establishing the reservation or adjusting dates.
• This enhancement would improve usability, reduce errors, and support better compliance with business processes.