Files

gsinghpal 25c3f6f8d1 feat(plating): Sub 5 — order-line fields (serial, job#, thickness, revision)

Four new fields on every sale.order.line, propagated through to MO,
Delivery, and Invoice for end-to-end traceability:

- fp.serial registry (new model in configurator) with smart-button
  traceability to Sale Order, MO, Delivery, Invoice, Part. M2O on SO
  line; optional; user types a customer serial or clicks Generate
  Serial for a sequence-backed one. Reverse O2M links split across
  configurator (invoice) / bridge_mrp (MO) / logistics (delivery) so
  module load order is respected.
- x_fc_job_number on SO line, auto-sequenced FP-JOB-NNNNN on SO
  confirm. Editable — shops can override for customer/legacy schemes.
- fp.coating.thickness (new child of fp.coating.config) with per-
  config discrete thickness options; x_fc_thickness_id on SO line
  domain-filtered to the line's coating. Auto-clears when coating
  changes.
- x_fc_revision_snapshot Char on SO line, frozen from
  x_fc_part_catalog_id.revision at save. Protects historical SOs from
  later catalog edits. Secondary "Revision" picker on the tree view
  lets users switch between prior revisions of the same part number;
  the Part M2O still surfaces only is_latest_revision rows.

Reports (CoC, packing slip, invoice, BoL) pick up all four via the
Sub 2 customer_line_header macro — one macro edit, four reports.

Smoke on entech: 11 assertions pass including revision snapshot,
generate-serial button, typed-serial create-on-fly, coating→thickness
domain reset, SO confirm auto job#, and MO traceability carry.

Module version bumps:
  fusion_plating_configurator  → 19.0.12.0.0
  fusion_plating_bridge_mrp    → 19.0.11.0.0
  fusion_plating_logistics     → 19.0.2.0.0 (+depends configurator)
  fusion_plating_reports       → 19.0.5.1.0

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

2026-04-22 23:04:44 -04:00

data

folder rename

2026-04-16 20:53:53 -04:00

models

feat(plating): Sub 5 — order-line fields (serial, job#, thickness, revision)

2026-04-22 23:04:44 -04:00

security

folder rename

2026-04-16 20:53:53 -04:00

static/src/scss

folder rename

2026-04-16 20:53:53 -04:00

views

folder rename

2026-04-16 20:53:53 -04:00

__init__.py

folder rename

2026-04-16 20:53:53 -04:00

__manifest__.py

feat(plating): Sub 5 — order-line fields (serial, job#, thickness, revision)

2026-04-22 23:04:44 -04:00

README.md

folder rename

2026-04-16 20:53:53 -04:00

README.md

Fusion Plating — Logistics

Part of the Fusion Plating product family by Nexa Systems Inc.

Adds pickup & delivery management on top of the fusion_plating core:

Vehicle master — insurance, registration, service, TDG status, home facility, current driver
Driver tracking — extends hr.employee with licence class, licence expiry, TDG certification and expiry (x_fc_* fields)
Pickup requests — customer-initiated pickup of parts to be processed, with full state machine (new → scheduled → en_route → picked_up → received)
Deliveries — scheduled delivery of finished parts back to the customer (draft → scheduled → en_route → delivered / refused / returned)
Routes — combine pickups and deliveries into a single run for one driver and vehicle, with drag-to-reorder stops, calendar view, and total km tracking
Chain of custody — append-only audit trail written automatically as pickups and deliveries move through their lifecycle
Proof of delivery — recipient signature, photos, GPS, delivery timestamp

Dependencies

fusion_plating (core)
hr
mail

Works on both Odoo Community and Enterprise. The Enterprise fleet module is not required — the vehicle master is a lightweight CE-compatible model sized to what a plating shop needs.

Security

Reuses the core fusion_plating groups (Operator / Supervisor / Manager / Administrator) via the res.groups.privilege mechanism. No new groups are defined by this module.

Operators: read-only on all logistics records
Supervisors: read / write / create on routes, deliveries, pickup requests, vehicles, route stops, custody events, PODs
Managers: full CRUD (adds unlink)

Multi-company isolation is enforced by global ir.rule records on every new model.

Adds a Logistics section under the Plating app menu with:

Pickup Requests
Deliveries
Routes
Chain of Custody
Proof of Delivery

Adds Vehicles under Plating → Configuration.

Field naming

New dedicated models use the fusion.plating.* namespace consistent with the core module.
Extensions of base Odoo models (hr.employee) use the x_fc_ prefix per the Fusion Central convention.

Odoo 19 compliance

res.groups.privilege is reused from the core module — no category_id on res.groups.
No users field on groups.
All models inherit mail.thread / mail.activity.mixin via the _inherit list.
<chatter/> tag used in form views.
SCSS is theme-aware — no hardcoded colours, only CSS custom properties from Odoo / Bootstrap, and color-mix() for semantic tints.

README.md

Fusion Plating — Logistics

Dependencies

Security

Menu

Field naming

Odoo 19 compliance