Features

The sales import step supports:

• Creating sales orders
• Reusing existing sales orders via search fields
• Creating sales order lines
• Reusing existing sales order lines via search fields
• Shared import state integration
• Automatic order-line linking
• Integration with imported contacts and products
• Sequential import chaining

The module depends on:

• import_core
• sale
• import_step_contacts
• import_step_products

Import step registration

The module registers the following import step:

<record id="generic_import_step_sale" model="generic.import.step">
    <field name="name">Sales Orders + Lines</field>
    <field name="code">sale</field>
    <field name="sequence">40</field>
    <field name="required_models">
        sale.order,sale.order.line
    </field>
</record>

This means:

• The dispatcher executes runner:

  generic.import.runner.sale

• The step is only available when models:

  • sale.order
  • sale.order.line

  are installed.

Configuration

1. Install modules:

   • import_core
   • sale
   • import_step_contacts
   • import_step_products
   • import_step_sale

2. Open:

   Imports -> Templates

3. Create or edit a template

4. Add import step:

   • Sales Orders + Lines

5. Configure field mappings for models:

   • sale.order
   • sale.order.line

6. Optionally mark fields as:

   • Is search field

Search fields are used to find existing records before creating new ones.

Usage

Customer,Product,Quantity
Example Customer,Test Product,2

Automatic linking

The runner automatically stores created records into shared state.

Sales order:

state = self._set_state_record(
    state,
    "sale_order",
    sale_order,
)

Sales order line:

state = self._set_state_record(
    state,
    "sale_order_line",
    sale_order_line,
)

This allows state links to assign relations automatically.

Typical state link examples:

source_state_key = partner
target_model     = sale.order
target_field     = partner_id

source_state_key = product
target_model     = sale.order.line
target_field     = product_id

source_state_key = sale_order
target_model     = sale.order.line
target_field     = order_id

Shared import state

The step integrates with previous import steps.

Typical import chain:

1. Contact step imports partner
2. Product step imports product
3. Sale step imports order and lines

The step commonly consumes:

• state["partner"]
• state["product"]

The step stores:

• state["sale_order"]
• state["sale_order_line"]

Automatic model-based state keys are also generated by generic.import.runner.base.

Example:

state["sale_order"]
state["sale_order_line"]
state["sale_order_line"]

Technical implementation

The runner inherits:

_inherit = "generic.import.runner.base"

Available helper methods include:

• _get_or_create()
• _get_or_create_from_lines()
• _build_domain()
• _clean_vals()
• _set_state_record()

Search field behavior

Fields marked as Is search field are used to build lookup domains.

Example:

• client_order_ref marked as search field

The runner performs:

self.env["sale.order"].search([
    ("client_order_ref", "=", value)
], limit=1)

If a matching record is found:

• Existing record is reused
• Duplicate creation is avoided

Dependencies

Python dependencies:

• None

Odoo dependencies:

• import_core
• sale
• import_step_contacts
• import_step_products

Known issues / Roadmap

Credits

Maintainer

This module is maintained by Oy Tawasta OS Technologies Ltd.