edi_voxel_sale_order_import_oca

Purpose

Import sales orders from Voxel by periodically fetching their XML documents and creating Odoo quotations through background jobs.

Features

res.company: Each company can store the Voxel sale order login that the importer uses when fetching documents.
res.config.settings: Administrators can configure the company-specific Voxel sale order login directly from the Voxel settings panel.
sale.order: The scheduled import routine scans enabled companies, finds their Voxel login, and enqueues background jobs to fetch pending documents.
ir.cron: A recurring server action runs every ten minutes to trigger the Voxel sale order import routine without manual intervention.
sale.order: Imported orders keep links to their queue jobs and reflect whether the owning company has Voxel integration enabled.
sale.order: XML parsing populates order references, commitment and validity dates, partner data, and posts chatter summaries listing any validation issues.
sale.order: Client and delivery partners are matched via references, geography, and contact info, raising user errors if no suitable partner can be found.
sale.order.line: ProductList entries resolve to products using supplier SKUs, customer-specific codes, or item names before running onchange logic to finalize line values.
sale.order.line: Quantities, units of measure, discounts, and taxes are mapped from Voxel codes, enforcing matches with existing UoMs and taxes to keep fiscal data consistent.
sale.order: Form and search views add a Voxel tab with the imported filename and XML payload plus a filter to list quotations sourced from Voxel.
queue.job: Managers get a dedicated menu, action, and record rule to monitor Voxel sale order import jobs restricted to the root.voxel_import channel.