Skip to main content

EDI

Beta License: LGPL-3 OCA/edi Translate me on Weblate Try me on Runbot

Base EDI backend.

Provides following models:

  1. EDI Backend, to centralize configuration

  2. EDI Backend Type, to classify EDI backends (eg: UBL, GS1, e-invoice, pick-yours)

  3. EDI Exchange Type, to define file types of exchange

  4. EDI Exchange Record, to define a record exchanged between systems

Also define a mixin to be inherited by records that will generate EDIs

Table of contents

Configuration

This module aims to provide an infrastructure to simplify interchangability of documents between systems providing a configuration platform. It will be inherited by other modules in order to define the proper implementations of components.

In order to define a new Exchange Record, we need to configure:

  • Backend Type

  • Exchange Type

  • Backend

  • Components

Component definition

The component usage must be defined like edi.{direction}.{kind}.{code} where:

  • direction is output or input

  • kind can be: generate, send, check, process, receive

  • code is the {backend type code} or {backend type code}.{exchange type code}

User EDI generation

On the exchange type, it might be possible to define a set of models, a domain and a snippet of code. After defining this fields, we will automatically see buttons on the view to generate the exchange records. This configuration is useful to define a way of generation managed by user.

Usage

After certain operations or manual execution, Exchange records will be generated. This Exchange records might be input records or outputs records.

The change of state can be manually executed by the system or be managed through by ir.cron.

Output Exchange records

An output record is intended to be used for exchange information from Odoo to another system.

The flow of an output record should be:

  • Creation

  • Generation of data

  • Validation of data

  • Sending data

  • Validation of data processed properly by the other party

Input Exchange records

An input record is intended to be used for exchange information another system to odoo.

The flow of an input record should be:

  • Creation

  • Reception of data

  • Checking data

  • Processing data

Bug Tracker

Bugs are tracked on GitHub Issues. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us smashing it by providing a detailed and welcomed feedback.

Do not contact contributors directly about support or help with technical issues.

Credits

Authors

  • ACSONE

Contributors

Maintainers

This module is maintained by the OCA.

Odoo Community Association

OCA, or the Odoo Community Association, is a nonprofit organization whose mission is to support the collaborative development of Odoo features and promote its widespread use.

Current maintainer:

simahawk

This module is part of the OCA/edi project on GitHub.

You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.

Metadata

Release files for odoo13-addon-edi 13.0.1.24.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Built distribution (wheel)

Table of built distributions (wheels) for odoo13-addon-edi 13.0.1.24.0
File Interpreter ABI Platform Actions
odoo13_addon_edi-13.0.1.24.0-py3-none-any.whl Python 3 none any Details for odoo13_addon_edi-13.0.1.24.0-py3-none-any.whl

Release files / odoo13_addon_edi-13.0.1.24.0-py3-none-any.whl

Download URL odoo13_addon_edi-13.0.1.24.0-py3-none-any.whl
Size 72.1 kB
Tags Python 3
SHA-256 checksum
How to use checksums
030713b3d79913c6a225f2c72baf2375b3ba3d89727b33d912aa77fe97b2a791
BLAKE2b-256 checksum
How to use checksums
bf5305309f012a50d386d44594141a691c78cd53f9db0169d9c3be3a9dd84b5a
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/4.0.0 CPython/3.8.5

Security for odoo13-addon-edi 13.0.1.24.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

13.0.1.24.0 This release

1 release file No provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page