When Purchase Order Change Management is enabled, changing the Delivery date or Confirmed receipt date on a confirmed Purchase Order always forces the order back to Draft and requires full workflow reapproval.

In real business scenarios, buyers often need to make minor date adjustments (for example, a 1–2 day shift agreed with the vendor) that do not change price, quantity, or financial commitment. However, today the system treats all date changes as high‑impact and triggers reapproval every time.

This causes:

• Unnecessary workflow cycles for small, operational changes
• Delays in processing confirmed purchase orders
• Increased workload for approvers with no real business risk
• Frustration for procurement teams who need flexibility after confirmation

Expected / Desired Behavior

Provide more flexibility in reapproval rules, for example:

• Allow configuration to exclude Delivery date / Confirmed receipt date from reapproval evaluation, or
• Allow defining thresholds (e.g. only reapprove if date change exceeds X days), or
• Allow a separate option to mark certain date changes as “low impact” so they do not force workflow reapproval

This would help customers balance governance with operational efficiency, while still keeping strong controls on financial and contractual changes.

Business Impact

High. This behavior affects daily procurement operations and leads to avoidable delays, especially in environments with frequent supplier date adjustments.