PMIS Export Maver (Opty-Way)

Export manufacturing components to ASC and XLSX, and print component worklists.

Features

• Download a ZIP containing one fixed-width ASC file per material reference for Opty-Way Maver integration.

• Export XLSX reports with one sheet per component, ordered by source order and manufacturing order.

• Print a PDF component worklist from manufacturing orders or work orders.

• ASC output uses noncanceled move lines when present, otherwise the component move. It prefers PMIS pieces; fallback quantities depend on the fields available on that record. XLSX quantities come from component-move PMIS pieces.

Configuration

The module requires mrp, stock, pmis_quant_measurements, and report_xlsx. Measurement support is a required dependency.

Ensure component products have an Internal Reference (default_code). ASC skips components without one and groups references after uppercasing and truncating them to 16 characters. Use distinct references within that limit.

Usage

1. Open a manufacturing order and select Export Maver (Components) for ASC output or Export Components (XLSX) for a spreadsheet.

2. For multiple manufacturing orders or work orders, select the records in the list and use Export ASC V4 (Components) or Export Components (XLSX) from the action menu.

These actions generate files for download. They do not submit them to Opty-Way.

The ASC export considers noncanceled raw moves with positive demand and stores its ZIP as an Odoo attachment. Review pieces and dimensions before importing the download into the cutting software. It does not derive missing dimensions from the finished product.

ASC writes width + 2 mm and height + 2 mm, a fixed grinding value of 2.0, rotation Y, and an empty SHAPE field. The first manufacturing tag, when available, is sanitized and truncated to eight characters for the note, not the SHAPE field. These values are hard-coded, not configurable allowances. Missing dimensions therefore become 2.0 in the export rather than blocking it. Quantities are rounded to integers; zero-quantity rows are not removed. Text is truncated to its fixed field width and non-ASCII characters become ?. Review the downloaded file against the cutting job before use.

When move lines exist, the quantity fallback checks qty_done and product_uom_qty after PMIS pieces; it does not read the Odoo 18 move-line quantity field. An unmeasured move line can consequently export zero even when its native operation quantity is positive.

Production XLSX output omits rows without a usable deadline. Its date candidates are the component move's deadline, expected date, and move date. A zero PMIS piece count remains zero in the spreadsheet. Work-order XLSX exports retain rows without deadlines. In both exports, the sheet identifies the component while the Product column identifies the finished manufacturing product.

The component PDF action uses work orders. Printing from manufacturing orders requires at least one related work order.

Use Print Components in the manufacturing-order list header or Components (per component) in a work order's Print menu. Work-order PDF and XLSX output repeat each production's noncanceled raw moves for every selected work order; these are operation worklists, so their totals can duplicate component demand. ASC from work orders instead exports their distinct related productions.

Bug Tracker

Bugs are tracked on PMISuite Repository Issues. Before opening a new issue, check whether it has already been reported. Include the module and Odoo versions, steps to reproduce, and expected and actual results. Use synthetic examples and redact sensitive information.

Credits

Maintainers

Current maintainer:

Luxim is an independent R&D and deployment company focused on solving complex problems in the Odoo ecosystem.

Luxim is an active member of OCA (Odoo Community Association).