2804168d9e
User caught two related issues from screenshots of the WO form:
1. The "Plating Details" tab was meaningless for non-wet WOs —
bath/tank/dwell/thickness all show as empty for masking, oven
bake, racking, and inspection steps. A shop with multiple ovens
had no way to record which oven a bake WO ran in.
2. When there's only ONE option (single oven, single bath), forcing
the manager to pick it on every WO is busywork — pin it
automatically.
**1. WO classification + per-kind equipment**
New `x_fc_wo_kind` (compute, non-stored) Selection field that buckets
each WO into one of: wet / bake / mask / rack / inspect / other.
Classification by priority:
• bath linked → wet
• oven linked → bake
• workcenter's process families wet → wet
• WO name keyword match (bake/oven/cure → bake;
mask/de-mask → mask; rack/de-rack → rack;
inspect/qa/qc/fai → inspect; default → other)
New equipment fields per kind:
• `x_fc_oven_id` (m2o fp.bake.oven) for bake WOs
• `x_fc_bake_temp`, `x_fc_bake_duration_hours` — bake parameters
• Existing bath/tank/rack/thickness reused for wet
• Existing rack reused for rack WOs
**2. Required-fields gate extended**
button_start now also requires `x_fc_oven_id` for bake WOs (alongside
the existing operator + bath/tank rules). Without an oven the
chart-recorder trail can't be tied back to the WO for compliance.
**3. View reorganized**
Process Details tab now shows only the equipment groups that apply
to this WO's kind (using `invisible="x_fc_wo_kind != 'bake'"` etc.).
Mask + Inspection + Other show informational alerts instead of
empty form fields. WO header shows a colour-coded kind badge.
**4. Smart auto-fill defaults**
New `_fp_autofill_default_equipment()` method on mrp.workorder. When
the facility has exactly ONE active option, it pre-pins:
• Bath → if facility has 1 active bath
• Tank → if the chosen bath has 1 active tank
• Oven → if facility has 1 active oven
Hooked from:
• `@api.onchange('workcenter_id', 'x_fc_facility_id', 'x_fc_bath_id')`
→ fills as user edits in the form
• Recipe → WO generation `_generate_workorders_from_recipe()`
→ fills at creation time so single-line shops never see an
empty bath/oven field
None of this overwrites an already-set value. Multi-line shops still
get a blank field to choose from.
**Simulator updates** (scripts/fp_e2e_workforce.py)
• Creates an oven if none exists
• Pins per-kind equipment in Hannah's planning step
• New PASS check: bake-WO auto-pinned to default oven
• New negative test 2b: bake WO with oven stripped → blocked
**Final E2E**: 54 PASS / 2 WARN / 0 FAIL out of 56 checks.
12 negative tests passing — all gates fire when triggered:
Tests 1-2 + 2b: WO start (operator + bath/tank + oven)
Tests 3-7: MO facility, cert spec, delivery POD, invoice
payment terms, thickness cal std
Tests 8-11: NCR close, CAPA close, discharge close, invoice ref
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
76 lines
2.7 KiB
Python
76 lines
2.7 KiB
Python
# -*- coding: utf-8 -*-
|
|
# Copyright 2026 Nexa Systems Inc.
|
|
# License OPL-1 (Odoo Proprietary License v1.0)
|
|
# Part of the Fusion Plating product family.
|
|
|
|
{
|
|
"name": "Fusion Plating — MRP Bridge",
|
|
'version': '19.0.6.6.0',
|
|
'category': 'Manufacturing/Plating',
|
|
'summary': 'Bridge Fusion Plating facilities, baths and tanks to Odoo MRP work orders.',
|
|
'description': """
|
|
Fusion Plating — MRP Bridge
|
|
============================
|
|
|
|
Part of the Fusion Plating product family by Nexa Systems Inc.
|
|
|
|
Links Fusion Plating infrastructure (facilities, work centres, baths, tanks)
|
|
to Odoo's native MRP manufacturing orders and work orders so shops can:
|
|
|
|
* Assign a plating facility and FP work centre to an MRP work centre.
|
|
* Tag each work order with the specific bath, tank, rack/fixture, target
|
|
thickness, and dwell time for traceability.
|
|
* Attach a customer specification and facility to a manufacturing order.
|
|
* Create an MRP work centre directly from a Fusion Plating work centre.
|
|
* Link a portal job to a manufacturing order for customer visibility.
|
|
|
|
Copyright (c) 2026 Nexa Systems Inc. All rights reserved.
|
|
""",
|
|
'author': 'Nexa Systems Inc.',
|
|
'website': 'https://www.nexasystems.ca',
|
|
'maintainer': 'Nexa Systems Inc.',
|
|
'support': 'support@nexasystems.ca',
|
|
'license': 'OPL-1',
|
|
'price': 0.00,
|
|
'currency': 'CAD',
|
|
'depends': [
|
|
'fusion_plating',
|
|
'fusion_plating_portal',
|
|
'fusion_plating_quality',
|
|
'fusion_plating_logistics',
|
|
'fusion_plating_batch',
|
|
'fusion_plating_shopfloor',
|
|
'fusion_plating_configurator',
|
|
'hr',
|
|
# hr_attendance gives us the standard hr.attendance model
|
|
# (check_in / check_out). fusion_clock builds on the same model
|
|
# so this works whether the shop runs vanilla attendance or the
|
|
# full Fusion Clock T&A. Bringing the dep into the bridge keeps
|
|
# the Manager Desk's "show only clocked-in workers" filter
|
|
# working out of the box.
|
|
'hr_attendance',
|
|
'mrp',
|
|
'mrp_workorder',
|
|
'mrp_account',
|
|
'sale_mrp',
|
|
'account',
|
|
],
|
|
'data': [
|
|
'security/ir.model.access.csv',
|
|
'data/fp_work_role_data.xml',
|
|
'wizard/fp_recipe_config_wizard_views.xml',
|
|
'views/mrp_workcenter_views.xml',
|
|
'views/mrp_workorder_views.xml',
|
|
'views/mrp_production_views.xml',
|
|
'views/sale_order_views.xml',
|
|
'views/fp_quality_hold_views.xml',
|
|
'views/fp_batch_views.xml',
|
|
'views/fp_workorder_priority_views.xml',
|
|
'views/fp_job_consumption_views.xml',
|
|
'views/fp_work_role_views.xml',
|
|
],
|
|
'installable': True,
|
|
'application': False,
|
|
'auto_install': False,
|
|
}
|