Files

gsinghpal db8b79d22e feat(plating): close 6 compliance gaps from required-fields audit

Following the workforce-E2E + required-fields audit, ship the first 6
high-priority gates so critical workflow + compliance fields can no
longer be left empty by accident.

**1. Invoice payment terms (account.move)**
- create() now auto-inherits `invoice_payment_term_id` from
  partner.property_payment_term_id when missing
- action_post() raises UserError if still missing — accountant must
  pick one before posting (prevents silent "immediate" due-date)

**2. MO facility (mrp.production)**
- action_confirm() auto-derives `x_fc_facility_id` if unset, in order:
  SO override → res.company.x_fc_default_facility_id → first active
  facility — then HARD GATES: raises UserError if still empty.
  Without facility every downstream record (WO, batch, bath log,
  cert) is missing the "where" half of the audit trail.

**3. WO facility (mrp.workorder)**
- Switched `x_fc_facility_id` from related (workcenter only) to a
  proper compute that falls back to production_id.x_fc_facility_id.
  Stub workcenters auto-created from process node names usually have
  no facility — the MO always does (from #2 above).

**4. Thickness reading calibration_std (fp.thickness.reading)**
- `calibration_std_ref` is now `required=True` with sensible default
  ("NiP/Al STD SET SN 100174568"). Nadcap mandates which calibration
  standard the gauge was checked against — without it the cert
  data has no chain back to a metrology record.

**5. Delivery POD gate (fusion.plating.delivery)**
- action_mark_delivered() raises UserError if no `pod_id`. Driver
  must capture POD on the iPad (recipient signature + photos +
  notes) BEFORE marking delivered. Without POD there's no signed
  receipt to back the invoice or defend a delivery dispute.

**6. Certificate spec_reference gate (fp.certificate)**
- action_issue() raises UserError if no `spec_reference`. The cert
  ATTESTS to a spec — leaving it blank produces a piece of paper
  that AS9100 / Nadcap auditors will (rightfully) reject.

**Simulator updated**: scripts/fp_e2e_workforce.py
- Sets net-30 on the test customer + ensures a default facility
- New PHASE 4c: 5 negative tests (one per new gate), each wrapped
  in a SAVEPOINT so SQL constraint violations don't abort the txn
- Driver now creates POD on iPad BEFORE marking delivered

**Final E2E**: 48 PASS / 2 WARN / 0 FAIL out of 50 checks.
The 2 remaining WARNs (bake-window auto-create, first-piece gate)
are expected behaviour — both are coating-driven and the test
coating intentionally doesn't trigger them.

All 7 negative tests now pass:
  ✓ Test 1: WO start without operator → blocked
  ✓ Test 2: WO start on wet WO without bath/tank → blocked
  ✓ Test 3: MO confirm without facility → blocked
  ✓ Test 4: Cert issue without spec_reference → blocked
  ✓ Test 5: Delivery delivered without POD → blocked
  ✓ Test 6: Invoice post without payment terms → blocked
  ✓ Test 7: Thickness reading without cal std → blocked (DB NOT NULL)

Audit script (scripts/fp_required_fields_audit.py) committed too —
it's the diagnostic that surfaced these gaps and can be re-run to
catch new ones.

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

2026-04-19 10:07:00 -04:00

data

folder rename

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

models

feat(plating): close 6 compliance gaps from required-fields audit

2026-04-19 10:07:00 -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): close 6 compliance gaps from required-fields audit

2026-04-19 10:07:00 -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