Technical module to retrieve party information for EDI exchanges.
It's based on partner_identification so that the party information will include allowed ID numbers for a given exchange.
You can configure which ID number categories are allowed on the exchange type.
auto_awesome What this module does
AI-generated from the code · Odoo 18.0Configure which partner ID categories are allowed for EDI exchanges and automatically build party information (name, identifiers, endpoint, language) from a partner for each exchange record.
This module adds party configuration to EDI exchange types and provides a helper that builds the party data used in EDI messages.
On an EDI exchange type form, a new "Party config" group lets you choose: - ID categories: the partner identification categories allowed when generating party information. - Endpoint ID category: only shown for output exchanges; the ID number in this category is used as the party's EndpointID.
The helper model edi.party.helper exposes a get_party method that, given an exchange record and a partner, returns a party object. That object computes:
- name from the partner (or a chosen name field),
- identifiers from the partner's ID numbers, filtered by the allowed categories (all ID numbers if none are configured),
- endpoint from the endpoint ID category, if set,
- language from the partner or an override, using Odoo's language data.
Each identifier is rendered with its scheme (or code) and value. The party object behaves like a dictionary, so it can be used in code snippets and templates. No new menus or reports are added; the changes appear inside the existing EDI exchange type configuration screen.
Depends on
Required by other modules
Models and fields (2)
- edi.party.helper · new model
- edi.exchange.type · extends an existing modelid_category_ids (ID categories), endpoint_partner_category_id (Endpoint ID category)
Text generated by AI (DeepSeek) from reading the Odoo 18.0 code on GitHub; it may contain mistakes, so check the code before deciding. View the code on GitHub
Availability by version
Reviewed: 2026-11-03Confirmation status: 1 confirmed, 8 with no information of 9 versions.
Sources · Odoo 18.0
Confirmed on 2026-11-03 in branch 18.0 of OCA/edi-framework.
terminal Installation and usage
OCA documentation · Odoo 18.0Configuration
Source · Odoo 18.0ID numbers selection
On the exchange type form, find the field "ID categories" and set the categories allowed for that exchange type.
If not set, all the IDs of the partner will be exposed.
Usage
Source · Odoo 18.0Via the edi.party.helper abstract model:
party = self.env["edi.party.helper"].get_party(exchange_record, partner)
Or directly, with no ORM registry lookup involved:
from odoo.addons.edi_party_helper_oca.utils import EDIParty
party = EDIParty(exchange_record=exchange_record, partner=partner)
Both return an EDIParty instance: the party data (name, identifiers, endpoint, lang) is exposed directly as attributes, alongside partner. It also behaves like a read-only dict of those same keys (party["name"], dict(party), equality against a plain dict), for backward compatibility with code expecting the old DotDict-based party data.
Both accept the same optional keyword arguments: name_field (defaults to "name") and lang_code (a language code overriding the partner's own).
No verified information in OCA: Installation.
Installation instructions, the distribution package, dependencies and configuration steps are not shown because they have not yet been verified in the module documentation for any version.
Data imported from GitHub: this sheet reflects the latest catalog review, not a live lookup. Always check the module documentation and staging before installing in production.