Skip to content

Fix warehouse propagation in MTO procurements#928

Open
jcadhoc wants to merge 1 commit into
ingadhoc:18.0from
adhoc-dev:18.0-h-118573-jc
Open

Fix warehouse propagation in MTO procurements#928
jcadhoc wants to merge 1 commit into
ingadhoc:18.0from
adhoc-dev:18.0-h-118573-jc

Conversation

@jcadhoc
Copy link
Copy Markdown
Contributor

@jcadhoc jcadhoc commented May 21, 2026

Summary

  • override stock.move._prepare_procurement_values() in stock_ux to propagate the warehouse that owns the physical source location
  • avoid reusing draft RFQs from a different warehouse in multi-warehouse MTO chains
  • prevent purchase orders from mixing destinations from different warehouses and later failing the operation type consistency check

Why

In some multi-warehouse MTO flows the move still carries the commercial warehouse in warehouse_id even though its real source location belongs to another warehouse. That stale value is propagated to the next procurement and can attach buy procurements to a draft RFQ from the wrong warehouse.

@roboadhoc
Copy link
Copy Markdown
Collaborator

Pull request status dashboard

@jcadhoc jcadhoc force-pushed the 18.0-h-118573-jc branch from 0f17c7b to 8cf5065 Compare May 21, 2026 15:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants