152ed86c3a
Per client direction: every order is a thickness RANGE (e.g. "0.0005-0.0008 mils" or "5-10 mils"), never a single value. The old picker model (fp.recipe.thickness with a single 'value' Float) was modelling the wrong concept and overcrowding the order entry UI. Replaced with one free-text Char field that auto-fills from last-used or part default. DELETED entirely: - fp.recipe.thickness model (file + view + ACL + manifest entry) - recipe.thickness_option_ids One2many (the picker source) - "Thickness Options" inline list on the recipe form - sale.order.line.x_fc_thickness_id (M2O picker) - account.move.line.x_fc_thickness_id - fp.delivery.x_fc_thickness_id - fp.direct.order.line.thickness_id ADDED: - sale.order.line.x_fc_thickness_range (Char) — operator types range - account.move.line.x_fc_thickness_range — for invoice rendering - fp.delivery.x_fc_thickness_range — for packing slip - fp.direct.order.line.thickness_range — for the wizard - fp.part.catalog.x_fc_default_thickness_range — part default AUTO-FILL CHAIN (sale.order.line + wizard line): 1. Operator already typed → keep 2. Most recent SO line for (this part, this customer) with a non-empty thickness_range → copy that 3. part.x_fc_default_thickness_range → copy 4. Blank — operator types Implemented as both an @api.onchange (interactive) AND a create() override (programmatic — wizard, sale_mrp bridge, imports). Same logic in both paths. WIZARD push-to-defaults: when "Save as Default" toggle is ticked on a wizard line, persist the line's thickness_range to part.x_fc_default_thickness_range so future first-customer orders get a sensible starting point. REPORTS: customer_line_header.xml + report_fp_wo_sticker.xml now print the Char range as-typed (no display_name lookup needed). KEPT (admin documentation only — doesn't affect order entry): - recipe.thickness_min, thickness_max, thickness_uom on the recipe root: documents the recipe's CAPABILITY range. No UI gate; just for spec authors to record what the chemistry can produce. JOB GROUPING: fp.job auto-create groups SO lines by (recipe, part, spec, thickness, serial). Updated to key on the thickness_range Char (stripped) instead of the deleted thickness_id integer. DB cleanup: --update=base ran on the upgrade, dropping the fp_recipe_thickness table + the four x_fc_thickness_id columns. Existing data was already nulled in earlier dev work. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
72 lines
2.8 KiB
Python
72 lines
2.8 KiB
Python
# -*- coding: utf-8 -*-
|
|
# Copyright 2026 Nexa Systems Inc.
|
|
# License OPL-1 (Odoo Proprietary License v1.0)
|
|
{
|
|
'name': 'Fusion Plating — Reports',
|
|
'version': '19.0.11.1.0',
|
|
'category': 'Manufacturing/Plating',
|
|
'summary': 'PDF reports for Fusion Plating: quote, SO, WO, packing, BoL, CoC, invoice, receipt, quality + compliance.',
|
|
'depends': [
|
|
'sale',
|
|
'sale_pdf_quote_builder',
|
|
'account',
|
|
'stock',
|
|
# 'mrp' dep dropped post-Sub 11 (MRP cutout). Plating uses fp.job
|
|
# exclusively now. Re-introducing this dep silently pulls mrp +
|
|
# cascade back to `installed` on any -u base rescan.
|
|
'fusion_plating',
|
|
'fusion_plating_quality',
|
|
'fusion_plating_compliance',
|
|
'fusion_plating_safety',
|
|
'fusion_plating_portal',
|
|
'fusion_plating_configurator',
|
|
# NB: fusion_plating_jobs intentionally NOT depended on. Jobs depends
|
|
# on us (uses report_fp_wo_sticker_inner). Adding the reverse dep
|
|
# creates a cycle. Our only fp.job touchpoint is wo_scan.py which
|
|
# uses runtime env.get('fp.job') — safe without the manifest dep.
|
|
'fusion_plating_logistics',
|
|
],
|
|
'data': [
|
|
'security/ir.model.access.csv',
|
|
'report/report_base_styles.xml',
|
|
'report/report_actions.xml',
|
|
# Quality + compliance reports
|
|
'report/report_coc.xml',
|
|
'report/report_coc_chronological.xml',
|
|
'report/report_fp_rack_travel.xml',
|
|
'report/report_ncr.xml',
|
|
'report/report_capa.xml',
|
|
'report/report_bath_chemistry_log.xml',
|
|
'report/report_calibration_cert.xml',
|
|
'report/report_fair.xml',
|
|
'report/report_audit.xml',
|
|
'report/report_incident.xml',
|
|
'report/report_spill.xml',
|
|
'report/report_waste_manifest.xml',
|
|
'report/report_discharge_sample.xml',
|
|
'report/report_wo_margin.xml',
|
|
# Quote-to-cash reports (portrait + landscape)
|
|
'report/customer_line_header.xml',
|
|
'report/report_fp_sale.xml',
|
|
'report/report_fp_work_order.xml',
|
|
'report/report_fp_wo_sticker.xml',
|
|
'report/report_fp_job_traveller.xml',
|
|
'report/report_fp_packing_slip.xml',
|
|
'report/report_fp_bol.xml',
|
|
'report/report_fp_invoice.xml',
|
|
'report/report_fp_receipt.xml',
|
|
# Sub 12 Phase E — quality/RMA reports.
|
|
'report/report_fp_rma_authorisation.xml',
|
|
'report/report_fp_8d.xml',
|
|
'report/report_fp_quality_monthly.xml',
|
|
# Hide Odoo's default reports from the Print menu wherever FP
|
|
# ships an equivalent (loaded last so it overrides any earlier
|
|
# binding declarations from base modules).
|
|
'data/fp_hide_default_reports.xml',
|
|
],
|
|
'installable': True,
|
|
'application': False,
|
|
'auto_install': False,
|
|
'license': 'OPL-1',
|
|
}
|