• When Per updated quantity is enabled, the system generates a new Quality Order every time the batch job runs, even when there is no true quantity update.
• The system keeps generating duplicate Quality Orders as long as the previous one is not validated (Pass/Fail).
• This leads to multiple Quality Orders being created for the same batch / same inventory transaction.
• Microsoft has confirmed that the system treats every batch‑job‑triggered update as a new quality‑associated event, which causes repeated Quality Order creation.
• This behavior matches internal design logic:

“A Quality Order is created for each updated‑quantity event when Per updated quantity is enabled.”

Business Impact:

The current behavior results in multiple unnecessary Quality Orders being automatically created whenever the batch job runs while an existing Quality Order remains open. This leads to:

• Significant administrative overhead, as users must manually close, delete, or manage duplicate Quality Orders.
• Process inefficiency, where quality teams spend time sorting through irrelevant QOs instead of focusing on actual inspections.
• Operational confusion, as duplicates clutter the Quality Orders list and increase the risk of validating or processing the wrong order.
• Downstream disruptions, since multiple open Quality Orders affect inventory workflows, blocking status changes, delaying next operational steps, and creating data inconsistencies.
• Scalability issues, especially in environments where batch jobs run frequently, causing QOs to multiply rapidly.

This behavior negatively affects productivity, accuracy, and user experience, making a configurable option to prevent repeated/duplicate Quality Orders essential for real‑world quality processes.