OCA modules for Odoo

This module provides an example on how to configure and exchange type for EDIFACT standard, as well as some test coverage for importing orders with the same standard.

Glue module between edi_sale_oca and edi_endpoint_oca.

Inbound Receive sale orders from EDI channels. Control sale order confirmation You can decide if the order should be confirmed by exchange type. On your exchange type, go to advanced settings and add the following: [...] components: process: usage: input.process.sale.order env_ctx: # Values for the wizard default_confirm_order: true default_price_source: order # Custom keys, whatever you need random_one: true Note that env_ctx will propagate all keys to the whole env so you…

Handle sale orders via EDI. This is a base module to plug sales processes with the EDI framework. To handle inbound/outbound sale orders, you need to use edi_sale_input_oca or edi_sale_output_oca modules, or create your own modules.

DEPRECATED: use edi_sale_input_oca. Plug sale_order_import into EDI machinery. Control sale order confirmation You can decide if the order should be confirmed by exchange type. On your exchange type, go to advanced settings and add the following: [...] components: process: usage: input.process.sale.order [...] sale_order: confirm_order: true TODO: shall we add an exchange type example as demo?

Plug sale_order_import into EDI machinery. This module creates a default EDI exchange type needed to import sale orders.

Provide default endpoint for importing sale orders. This module is more an example on how you can create your own endpoint to manage such exchanges.

Glue module between edi_sale_oca and edi_stock_oca.

TODO

Configuration and special behaviors for EDI UBL exchanges related to sales. Takes care of: · define SO and SO line states (according to PEPPOL states definition) · compute the edi state for SO and SO line · add state info on SO views

Provides some basic templates for generating order responses in UBL format within the EDI framework. Templates qweb_tmpl_ubl_party: to be used to render a party (res.partner) qweb_tmpl_ubl_address: to be used to render a party's address (aka res.partner) qwb_tmpl_ubl_order_response_out: example for a full ORDRSP output. NOTE: the latter is not fully complete and above all should not be used directly to avoid overrides. Always define your own template for the customer.

Technical module for the EDI suite to provide additional states for any records. Example: a SO is generated via UBL file and you want to provide an ORDRSP with the right state on the order and on each line. It provides 2 new models: · EDI state workflow > - groups states together > - limit states to a specific model · EDI state > - describe the state of the record

This module intends to create a base to be extended by local edi rules for stock. In order to add a new integration for an stock picking, you need to create a listener:

Allow exchange files using storage backends from OCA/storage. This module adds a storage backend relation on the EDI backend. There you can configure the backend to be used (most often and SFTP) and the paths where to read or put files. Often the convention when exchanging files via SFTP is to have one input forder (to receive files) and an output folder (to send files). Inside this folder you have this hierarchy: input/output folder |- pending |- done |- error · pending…

Allow exchange files using storage backends from OCA/storage. This module adds a storage backend relation on the EDI backend. There you can configure the backend to be used (most often and SFTP) and the paths where to read or put files. Often the convention when exchanging files via SFTP is to have one input forder (to receive files) and an output folder (to send files). Inside this folder you have this hierarchy: input/output folder |- pending |- done |- error · pending…

Integrates EDI Storage with Queue Job.

Provide basic configuration for UBL with EDI framework.

Generic UBL party/address qweb templates for use with the EDI framework (edi_exchange_template_oca), split out of edi_sale_ubl_output_oca so they can be reused (e.g. by purchase-side UBL output) without depending on sale. Templates · qweb_tmpl_ubl_party: renders a cac:Party block (EndpointID, PartyIdentification, PartyName) from the party vals shape produced by edi_party_data_oca/edi_exchange_template_party_data's get_party_data(). · qweb_tmpl_ubl_address: renders the…

This module automatically assigns the EDI source to records created through the EDI mechanism.

This is a base module that allows you to send and receive documents such as Invoices, Sales Orders, Delivery Orders in XML format using the baVel electronic platform belonging to Voxel Group. Voxel Group is a company that offers leading solutions for B2B payments, eInvoicing, VAT refund and supply chain via its baVel Platform. For more information visit https://www.voxelgroup.net/. This module doesn't do anything useful by itself, but it is used by other modules: ·…