Description:

When modifying date fields at the header level of a sales document (e.g., Requested Delivery Date), the system does not consistently revalidate existing reservations or provide detailed feedback about potential conflicts.

Specifically:

• If sales lines are already reserved against purchase orders and the header date is changed, the system only shows a generic warning indicating that conflicts may cancel reservations.
• The system does not specify:
• Whether a conflict actually exists
• Which sales lines are impacted
• Which linked purchase lines are causing the conflict

In contrast, when the same change is performed at the sales line level, the system provides a more explicit validation/error to prevent unintended loss of reservations.

This creates inconsistency in behavior between header-level and line-level changes and makes it difficult for users to identify and resolve reservation conflicts—especially in documents with a high volume of lines.

Business Impact:

• Users cannot easily identify which lines are affected by date conflicts
• Increased risk of unintentionally losing reservations
• Manual effort required to validate each line individually
• Reduced efficiency when working with large sales or purchase documents
• Confusion due to inconsistent behavior between header and line updates

Suggested Enhancement:

• Introduce detailed validation when header date fields are modified
• Provide a clear and actionable message indicating:
• Whether conflicts exist
• The exact sales lines impacted
• The related purchase document conflicts
• Align the behavior of header-level changes with line-level validation to ensure consistency