OCA modules for Odoo

Base module allowing configuration of custom endpoints for EDI framework.

This module adds options for deduplication of exchange records on the exchange type: · deduplicate_on_exchange: when a record is created, check if older records for the same record are still pending. If so, mark them as obsolete, so only the freshest one is sent or processed. Records without a related record match on the exchange type alone, which suits full-dump payloads where only the latest one matters. · delete_obsolete_records: Delete records marked as obsolete.

Adds a "Manage File" button on EDI exchange records that contain a file and are in an error state (validate_error, output_sent_and_error or input_processed_error). The button opens a wizard that lets the user either replace the exchange file with a new one, or edit its content directly (with a code editor). At the end the user can safely close the wizard.

Provide EDI exchange templates to control input/output records contents. Provides following models: · EDI exchange output template, generates output using QWeb templates · [TODO] EDI exchange input template

Provide EDI exchange templates to control input/output records contents. Provides following models: · EDI exchange output template, generates output using QWeb templates · [TODO] EDI exchange input template In order to use it, the echange type must have the handler: Exchange Template Handler for EDI

Glue module betweeb edi_exchange_template and edi_party_data. Exposes a get_party_data function to the rendering context of the template. This way you can retrieve party data on the fly. Deprecated: edi_party_data_oca (and this glue module) are superseded by edi_party_helper_oca, which has no dependency on the component framework. Use its edi.party.helper model (or the EDIParty class directly) instead of the get_party_data render context shortcut. A deprecation notice is…

Provide basic configuration for manufacturing orders with EDI framework.

This module creates activities for users when an exchange record's process fails. It also installs an edi.configuration rule (Notify Users On Exchange Error) that calls edi.notification.tool on process errors. Exchange types must be configured properly to create such activities: · field "Notify On Process Error" must be checked to activate the feature for the current exchange type · field "Activity Type Used When Notify On Process Error" is used to define the type of the…

Minimal module used only to avoid issues on the migration to the new splitted model of edi_oca. Might be removed on 19 but we keep it as part of the transition after the split between EDI and components.

This module intends to create a base to be extended by local edi rules for partner.

Technical module for the EDI suite module to retrieve data for parties of an exchange. This module provides default component and a mixin to be used for registering new components for specific backends. Deprecated: the actual party data lookup logic has moved to edi_party_helper_oca, which has no dependency on the component framework. This module now only wraps it in a component for backward compatibility and will be removed once its usages are ported over. A deprecation…

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.

This module allows to define templates used to process pdfs. It could be used to import invoices or other kinds of PDFs.

Provide basic configuration for product barcodes with EDI framework.

Provide basic configuration for products and product packaging with EDI framework.

This module intends to create a base to be extended by local EDI rules for project management. In order to add customizations for projects, create a listener: In order to add customizations for tasks, create a listener: Use @skip_if() decorator to avoid triggering a listener's method if necessary:

Handle purchase orders via EDI. This is a base module to plug purchase processes with the EDI framework. To handle inbound/outbound purchase orders, you need to create your own integration modules on top of this base module.

Handle purchase exchanges with the EDI framework. This module is mostly a glue module for purchase_order_ubl with edi_oca. Allows you to generate and send purchase orders as UBL XML files with a simple configuration.

This module integrates EDI exchange records with Queue Job, so that the four core exchange actions — generate, send, receive, and process — are dispatched as background jobs instead of running synchronously. Each exchange type can optionally route its jobs to a specific channel, set a priority, or hold all jobs until a fixed time of day — useful when a trading partner's receiving system has a nightly processing window or when the operator wants to concentrate…

Allow to store metadata for related records.