OCA modules for Odoo

This module provides a generic tool to have the possibility to see a list of records associated to a given selection of records. This is basically the UI version of recordset.mapped('field1.field2'). For example, if you use the sale module, you can configure an action to see all the products that have been sold for a given selection of sale orders.

This module provides a generic tools to have the possibility to sort the lines of a list of items. For exemple, if you use the sale module, you can want to reorder the sale order lines, by any criterias.

This module is based on the server_environment module to use files for configuration. Thus we can have a different configuration for each environment (dev, test, integration, prod). This module define the config variables for the connector_jira module.

This module is based on the server_environment module to use files for configuration. So we can have a different configuration for each environment (dev, test, integration, prod). This module define the config variables for the ebill_paynet module. Exemple of the section to put in the configuration file: [paynet_service.name_of_the_service] use_test_service": True, client_pid": 123456789, service_type": b2b, username": username, password": password,

This module allows the configuration of the fields "Address", "Port", "User" and "Password" on Printing Server from server environment.

This module provides a way to define an environment in the main Odoo configuration file and to read some configurations from files depending on the configured environment: you define the environment in the main configuration file, and the values for the various possible environments are stored in the server_environment_files companion module. The server_environment_files module is optional, the values can be set using an environment variable with a fallback on default values…

This module adds a way to create automaticaly records using server_environment server.env.mixin.

This module changes a little the behavior of server_environment modules. When Odoo does not find the value of the field in the configuration file, it will fallback on a Odoo encrypted field instead. Also it allows you to configure the environment dependent fields for all your environments from the production server.

This module allows to configure shipping methods according to server environment.

This is an example module to be used for server_environment_files. Check that module's README for more information.

This module allows to configure the IAP Accounts using the server_environment mechanism: you can then have different IAP Accounts for the production and the test environment.

Override System Parameters from server environment file.

Store sessions in a database instead of the filesystem. This simplifies the configuration of horizontally scalable deployments, by avoiding the need for a distributed filesystem to store the Odoo sessions.

Manage your (un)loading process through shipment advices.

This module adds the possibility to generate vendor bill lines from incoming shipment advice. Only shipment advice that are in state done can be selected. Shipment advice related to multiple suppliers are not supported. The bill lines are generated from the shipment move line and NO check are being done to prevent over billing. The bill needs to be checked manually.

This is a glue module between mrp and shipment_advice_bill_auto_complete It fixes the computation of the quantity to invoices for kits.

This module is used to plan ready transfers in shipment advices. As this is the base module, it provides only a simple planning mode. Transfers are grouped to have a single shipment advice by warehouse.

This module extend the shipment advice planner engine to add a new planning method based on geo-localization. It uses the GEOCONCEPT solution called TourSolver to plan the shipment advices according to the location of the customers by calculating the best route according to the available resources.

This module makes TourSolver tasks of shipment planning process runs in queue jobs.

Allows to plan stock moves in incoming shipment advice from the shipment. There is a Plan Reception button on the shipment form and the related wizard allows to split the quantity to receive.