Subversion Repositories SmartDukaan

Last modification

• Rev 37615 2026-09-14 04:56:50
• Author: amit

• Log message:

  Receive internal transfers the way the portal does, not via the Excel upload
  
  The live run failed on every invoice with "Column 'status' cannot be null". The Excel upload path it
  was calling, addPORowModels, persists a supplier invoice without ever setting a status, and the
  column does not allow one to be absent, so that route cannot complete a receipt at all.
  
  Rather than change a path the portal shares, this follows what the Receive Invoice screens actually
  do: record the supplier invoice, record its items through InvoiceService.createInvoiceItem, then hand
  it to PurchaseOrderService.grnPoModels, the call behind the Create GRN button. grnPoModels sets the
  invoice to received itself, so the status is never left for the caller to remember.
  
  Recording the invoice items matters beyond the receipt: warehouse.invoice_item is what the buying
  reports join against, and the Excel path never wrote those rows either.
  
  An invoice is carried as one entry per item rather than one per order, since that is the shape
  grnPoModels expects - every serial of an item arrives together and a non serialised item arrives as a
  single quantity. There is no supplier document to attach, which is ordinary here; most existing
  warehouse invoices carry none.
  
  Resolving the purchase order now uses the mapping recorded when the internal PO was raised - the
  transaction it created, held on the purchase order - instead of walking every order to find it.
  An invoice whose orders do not share that one transaction is skipped rather than guessed at.