1

Problem / Behavior

When a Purchase Requisition is created with Quantity = 0, converting that PR to a Purchase Order results in the PO line quantity being auto-populated as 1.

This behavior happens consistently for all PRs with zero quantity, and we are not using any custom workflow or customizations.

This can lead to unintended orders and downstream issues in planning, inventory, receiving, vendor invoicing, and compliance.


Impact / Why This Matters

  • Financial risk: Accidental commitments for items not intended to be purchased.
  • Operational noise: Extra work to cancel/close unintended orders; confusion for planners and buyers.
  • Inventory integrity: Discrepancies between demand signals (PRs) and actual POs.
  • Compliance & audit: PR-to-PO traceability and approvals are undermined if quantities silently change.
  • Vendor relationship: Unnecessary orders can trigger shipments and invoice mismatches.

Proposed Change / Feature Request

Introduce robust validation and inheritance consistency for PR → PO conversion:

  1. Validation at PR creation/editing
  • Prevent saving/approving PR lines with Quantity = 0, or warn with explicit guidance.
  • Validation at PR → PO conversion
  • If any PR line has Quantity = 0, block conversion and show an actionable error.
  • Optional UX prompt
  • Provide a guided prompt allowing buyers to enter the intended quantity before PO line creation if business processes require exceptions.
  • System parameterization
  • Add a Procurement & sourcing parameter:
  • “Allow conversion of PR lines with zero quantity”
  • Off (default): Block conversion with error.
  • On: Prompt for quantity override with audit trail.
  • Auditability
  • Log any user override and capture who/when/what for compliance reporting.


STATUS DETAILS
New