odoo/odoo#197981

Created by fw-bot
Merged at 58cf23a9289d824694b95ed5641ed4e36f061e06

Statuses:

label
odoo-dev:saas-18.2-17.0-fetch-active-warehouse-picking-type-atp-406542-fw
head
7937aa503ff25b5a08c53d83dfde2df59de64332
merged
4 months ago by POS IoT, Adrien Guilliams (adgu)
odoo/odoo
17.0 #185244
saas-17.2 #188874
saas-17.4 #188882
18.0 #188888
saas-18.1 #191652
saas-18.2 #197981
saas-18.3 #207548 missing statuses missing r+
saas-18.4 #215660 missing r+
19.0 #226518 missing r+
master #188890 missing statuses missing r+

[FW][FIX] point_of_sale: fetch active warehouse pos type only

revert the commit
as when we fetch archived warehouse's pos type
it will raise error for other source or destination loction for newly created stock operation type like

even functinally also there is no need to fetch
archived warehouse's operation type.

quality Control
cross Dock,
Storage type

we got this error during upgrade :

File "/home/odoo/src/odoo/saas-17.4/odoo/sql_db.py", line 347, in execute
    res = self._obj.execute(query, params)
psycopg2.errors.NotNullViolation: null value in column "default_location_src_id" of relation "stock_picking_type" violates not-null constraint
DETAIL:  Failing row contains (33, 0, 28, 56, null, null, null, 4, null, null, 1, 1, 1, QC, internal, at_confirm, FBAQC, ask, {"en_US": "Quality Control"}, null, f, f, t, null, f, null, 2024-10-16 05:14:53.18448, 2024-10-16 05:14:53.18448, optional, optional, no, optional, null, null, t, null, null, 2x7xprice, 4x12_lots, pdf, null, null, null, null, null, null, null, null, null, t, null).

due to this two fix:
#151719/commits
#175838/files

so we need to avoid to fetch archived warehouse's picking type.

ref:
odoo/upgrade#6631

Description of the issue/feature this PR addresses:

Current behavior before PR:

Desired behavior after PR is merged:


I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Forward-Port-Of: #185244