Subversion Repositories SmartDukaan

Last modification

• Rev 37703 2026-09-18 04:10:51
• Author: amit

• Log message:

  GRN price mismatch: ask for the original PO to be reopened instead of stranding a correction PO
  
  Resolving a price mismatch raised a correction PO dated to the supplier invoice, and stored its id
  on the GRN request item to receive against. But by then the stock has already arrived and the PO it
  corrects is closed - every one of the 54 raised this way had its mapped PO in CLOSED. The
  correction therefore had nowhere to land: the GRN completed against the original, nothing was ever
  received against the correction, and it sat holding a reservation for stock that was not coming.
  Backdated by nature, it also parked in INIT under the old approval gate, so it could not have been
  received even if anyone tried.
  
  Resolving a mismatch against a closed PO now says so and names it, asking for that purchase order
  to be reopened first, rather than silently creating a second PO that cannot be used.
  
  WarehousePurchaseOrder.isOpen() names the open set - INIT, READY, PARTIALLY_FULFILLED - that the
  movement and commitment queries already read, so it stops being restated per caller.