Saravanan666/pypi-org huggingface dataset:
Package: odoo13-addon-edi
Base EDI backend.Provides following models:EDI Backend, to centralize configurationEDI Backend Type, to classify EDI backends (eg: UBL, GS1, e-invoice, pick-yours)EDI Exchange Type, to define file types of exchangeEDI Exchange Record, to define a record exchanged between systemsAlso define a mixin to be inherited by records that will generate EDIsTable of contentsConfigurationComponent definitionUser EDI generationUsageOutput Exchange recordsInput Exchange recordsBug TrackerCreditsAuthorsContributorsMaintainersConfigurationThis 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 TypeExchange TypeBackendComponentsComponent definitionThe component usage must be defined likeedi.{direction}.{kind}.{code}where:direction isoutputorinputkind can be:generate,send,check,process,receivecode is the{backend type code}or{backend type code}.{exchange type code}User EDI generationOn 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.UsageAfter 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 byir.cron.Output Exchange recordsAn output record is intended to be used for exchange information from Odoo to another
system.The flow of an output record should be:CreationGeneration of dataValidation of dataSending dataValidation of data processed properly by the other partyInput Exchange recordsAn input record is intended to be used for exchange information another system to odoo.The flow of an input record should be:CreationReception of dataChecking dataProcessing dataBug TrackerBugs are tracked onGitHub 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 welcomedfeedback.Do not contact contributors directly about support or help with technical issues.CreditsAuthorsACSONEContributorsSimone Orsi <simahawk@gmail.com>Enric Tobella <etobella@creublanca.es>MaintainersThis module is maintained by the OCA.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.Currentmaintainer:This module is part of theOCA/ediproject on GitHub.You are welcome to contribute. To learn how please visithttps://odoo-community.org/page/Contribute.
Package: odoo13-addon-edi-account
This module intends to create a base to be extended by local edi rules
for accounting.In order to add a new integration for an account, you need to create a listener:classMyEventListener(Component):_name="account.move.event.listener.demo"_inherit="base.event.listener"_apply_on=["account.move"]defon_post_account_move(self,move):"""Add your code here about creation of record"""A skip if decorator can be added in order to make some checks on the state of the moveTable of contentsBug TrackerCreditsAuthorsContributorsMaintainersBug TrackerBugs are tracked onGitHub 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 welcomedfeedback.Do not contact contributors directly about support or help with technical issues.CreditsAuthorsCreu BlancaContributorsEnric Tobella <etobella@creublanca.es>MaintainersThis module is maintained by the OCA.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.This module is part of theOCA/ediproject on GitHub.You are welcome to contribute. To learn how please visithttps://odoo-community.org/page/Contribute.
Package: odoo13-addon-edi-backend-partner
This module add the a “Partner” field in EDI backend, this can be useful in
some situation in which a backend is restricted to only a given partner or
to have another criteria to search edi backends.Table of contentsBug TrackerCreditsAuthorsContributorsMaintainersBug TrackerBugs are tracked onGitHub 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 welcomedfeedback.Do not contact contributors directly about support or help with technical issues.CreditsAuthorsForgeFlowContributorsLois Rilo <lois.rilo@forgeflow.com>MaintainersThis module is maintained by the OCA.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.Currentmaintainer:This module is part of theOCA/ediproject on GitHub.You are welcome to contribute. To learn how please visithttps://odoo-community.org/page/Contribute.
Package: odoo13-addon-edi-bank-statement-oca
This module intends to create a base to be extended by local edi rules
for bank statements.In order to add a new integration, you need to create a listener:classMyEventListener(Component):_name="account.bank.statement.event.listener.demo"_inherit="base.event.listener"_apply_on=["account.bank.statement"]defaction_bank_reconcile_bank_statements(self,bank_statement):"""Add your code here"""Table of contentsBug TrackerCreditsAuthorsContributorsMaintainersBug TrackerBugs are tracked onGitHub 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 welcomedfeedback.Do not contact contributors directly about support or help with technical issues.CreditsAuthorsForgeFlowContributorsJaume Bernaus <jaume.bernaus@forgeflow.com>MaintainersThis module is maintained by the OCA.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.This module is part of theOCA/ediproject on GitHub.You are welcome to contribute. To learn how please visithttps://odoo-community.org/page/Contribute.
Package: odoo13-addon-edi-exchange-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 templateImportantThis is an alpha version, the data model and design can change at any time without warning.
Only for development or testing purpose, do not use in production.More details on development statusTable of contentsBug TrackerCreditsAuthorsContributorsMaintainersBug TrackerBugs are tracked onGitHub 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 welcomedfeedback.Do not contact contributors directly about support or help with technical issues.CreditsAuthorsACSONEContributorsSimone Orsi <simahawk@gmail.com>MaintainersThis module is maintained by the OCA.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.Currentmaintainer:This module is part of theOCA/ediproject on GitHub.You are welcome to contribute. To learn how please visithttps://odoo-community.org/page/Contribute.
Package: odoo13-addon-edi-purchase-oca
This module intends to create a base to be extended by local edi rules
for purchase.In order to add a new integration, you need to create a listener:classMyEventListener(Component):_name="purchase.order.event.listener.demo"_inherit="base.event.listener"_apply_on=["purchase.order"]defon_button_confirm_purchase_order(self,move):"""Add your code here"""Table of contentsBug TrackerCreditsAuthorsContributorsMaintainersBug TrackerBugs are tracked onGitHub Issues.
In case of trouble, please check there if your issue has already been reported.
If you spotted it first, help us to smash it by providing a detailed and welcomedfeedback.Do not contact contributors directly about support or help with technical issues.CreditsAuthorsForgeFlowContributorsLois Rilo <lois.rilo@forgeflow.com>MaintainersThis module is maintained by the OCA.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.This module is part of theOCA/ediproject on GitHub.You are welcome to contribute. To learn how please visithttps://odoo-community.org/page/Contribute.
Package: odoo13-addon-edi-stock-oca
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:classMyEventListener(Component):_name="stock.picking.event.listener.demo"_inherit="base.event.listener"_apply_on=["stock.picking"]defon_validate(self,picking):"""Add your code here about creation of record"""Table of contentsBug TrackerCreditsAuthorsContributorsMaintainersBug TrackerBugs are tracked onGitHub 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 welcomedfeedback.Do not contact contributors directly about support or help with technical issues.CreditsAuthorsOdoo Community AssociationContributorsAlba Riera <alba.riera@creublanca.es>MaintainersThis module is maintained by the OCA.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.This module is part of theOCA/ediproject on GitHub.You are welcome to contribute. To learn how please visithttps://odoo-community.org/page/Contribute.
Package: odoo13-addon-edi-storage
Allow exchange files using storage backends fromOCA/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
    |- errorpendingfolder contains files that have been just sentdonefolder contains files that have been processes successfullyerrorfolder contains files with errors and cannot be processedThe storage handlers take care of reading files and putting files
in/from the right place and update exchange records data accordingly.Table of contentsUsageBug TrackerCreditsAuthorsContributorsMaintainersUsageGo to “EDI -> EDI backend” then configure your backend to use a storage backend.Bug TrackerBugs are tracked onGitHub 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 welcomedfeedback.Do not contact contributors directly about support or help with technical issues.CreditsAuthorsACSONEContributorsSimone Orsi <simahawk@gmail.com>Lois Rilo <lois.rilo@forgeflow.com>MaintainersThis module is maintained by the OCA.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.This module is part of theOCA/ediproject on GitHub.You are welcome to contribute. To learn how please visithttps://odoo-community.org/page/Contribute.
Package: odoo13-addon-edi-voxel
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 visithttps://www.voxelgroup.net/.This module doesn’t do anything useful by itself, but it is used by other modules:edi_voxel_account_invoiceto send invoices to Voxel.edi_voxel_stock_pickingto send delivery orders to Voxel.edi_voxel_sale_order_importto import a sale order received from Voxel.Table of contentsBug TrackerCreditsAuthorsContributorsMaintainersBug TrackerBugs are tracked onGitHub 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 welcomedfeedback.Do not contact contributors directly about support or help with technical issues.CreditsAuthorsTecnativaContributorsTecnativa:Ernesto TejedaPedro M. BaezaMaintainersThis module is maintained by the OCA.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.This module is part of theOCA/ediproject on GitHub.You are welcome to contribute. To learn how please visithttps://odoo-community.org/page/Contribute.
Package: odoo13-addon-edi-voxel-account-invoice
This module allows you to send invoices to Voxel. Sending are queued in jobs
running in the background.Table of contentsConfigurationUsageBug TrackerCreditsAuthorsContributorsMaintainersConfigurationTo configure this module you have to belong to the access group
‘Voxel manager’ under ‘Technical Settings’, then:Open a customer form view. In ‘Sales & Purchases’ page,
check ‘Enable Voxel’ if you want to send invoices to this
customer through Voxel.Go toSettings > Users & Companies > Companies, open the companies you
want to enable Voxel communication and set ‘Enable Voxel’ field to True.In the login list, add the corresponding login for connecting with
Voxel to send the invoices. The final URL where the invoices are going
to be sent is ‘<Login URL>/Outbox’.Save the form and edit it again, find ‘invoice login’ field and select
the login to be used in the invoice sending.Select also the ‘Send mode’ to set when the Invoice will be sent:On validate: The invoice will be sent to Voxel automatically when
the invoice is validated.At fixed time: The invoice will be sent to Voxel automatically at
a fixed time.With delay: The invoice will be sent to Voxel automatically a certain
time after the invoice is validated.Note:This module enqueue the sending invoices to Voxel in jobs in the background.
To do that it uses queue_job module, so a configuration is required
according to that.
The jobs for sending invoices to Voxel are queued in the channelroot.voxel_export channel.
The sending status check jobs are queued in the channelroot.voxel_status.UsageTo use this module, you need to:Go toInvoicing > Customers > Invoicesand create a
new Invoice or open an existing draft invoice. Make sure that the customer
has ‘Enable Voxel’ field checkbox (See configuration section).Validate the invoice and it will be send to Voxel immediately or later,
depending on the Voxel ‘Send mode’ chosen in the company configuration.A new tab will be visible on the invoice form with the label ‘Voxel’
to show the information regarding sending the invoice to Voxel.When the report is sent, you will be able to see the XML report in another
tab next to the jobs tab.Bug TrackerBugs are tracked onGitHub 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 welcomedfeedback.Do not contact contributors directly about support or help with technical issues.CreditsAuthorsTecnativaContributorsTecnativa:Ernesto TejedaPedro M. BaezaMaintainersThis module is maintained by the OCA.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.This module is part of theOCA/ediproject on GitHub.You are welcome to contribute. To learn how please visithttps://odoo-community.org/page/Contribute.
Package: odoo13-addon-edi-voxel-sale-order-import
This module allows you to import sales orders from Voxel. Imports
are queued in jobs running in the background.Table of contentsConfigurationUsageBug TrackerCreditsAuthorsContributorsMaintainersConfigurationTo configure this module you have to belong to the access group
‘Voxel manager’ under ‘Technical Settings’, then:Go toSettings > Users & Companies > Companies, open the companies you
want to enable Voxel communication and set ‘Enable Voxel’ field to True.In the login list, add the corresponding login for connecting with
Voxel to import sales orders. The final URL from where sales order will be
imported is ‘<Login URL>/Outbox’.Save the form and edit it again, find ‘Sale Order login’ field and select
the login to be used in the imports.If you have the right access, go toSettings > Technical > Automation > Scheduled Actions, find the record
named ‘Edi Voxel: Get voxel sale order’ and Adjust the data corresponding
to that scheduled action, such as the frequency with which that action will
be executed.Note:This module enqueue the imports in jobs in the background.
To do that it uses queue_job module, so a configuration is required
according to that.
The jobs for impots are queued in the channelroot.voxel_import.UsageTo use this module, you don’t need to do anything. Automatically every so
often a ‘scheduled action’ will be executed that will try to import from
Voxel the sales orders that have not been imported previously.Imports will be performed for the companies that have the ‘Voxel’
field checked (See configuration section).Bug TrackerBugs are tracked onGitHub 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 welcomedfeedback.Do not contact contributors directly about support or help with technical issues.CreditsAuthorsTecnativaContributorsTecnativa:Ernesto TejedaPedro M. BaezaMaintainersThis module is maintained by the OCA.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.This module is part of theOCA/ediproject on GitHub.You are welcome to contribute. To learn how please visithttps://odoo-community.org/page/Contribute.
Package: odoo13-addon-edi-voxel-sale-secondary-unit
This module extends the functionality of ‘Voxel sale order’ module
to match secondary units of measure instead of standard units of measure
during sale order import process.During the process of a sales order import from voxel, for each sales
order line, the following flow is followed:If there is a matching ‘secondary unit of measure’, this is set and
the imported qty is set as ‘secondary qty’. Based on these data, the
standard ‘unit of measure’ and ‘quantity’ are computed.If there is no matching ‘secondary unit of measure’, standard quantity
and the matching standard unit of measure are set.Table of contentsUsageBug TrackerCreditsAuthorsContributorsMaintainersUsageTo use this module, you don’t need to do anything. The import process is
the same as in the ‘Voxel sale order’ module. the only thing that can
change is the imported sales order data.Bug TrackerBugs are tracked onGitHub Issues.
In case of trouble, please check there if your issue has already been reported.
If you spotted it first, help us to smash it by providing a detailed and welcomedfeedback.Do not contact contributors directly about support or help with technical issues.CreditsAuthorsTecnativaContributorsTecnativa:Ernesto TejedaPedro M. BaezaMaintainersThis module is maintained by the OCA.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.Currentmaintainer:This module is part of theOCA/ediproject on GitHub.You are welcome to contribute. To learn how please visithttps://odoo-community.org/page/Contribute.
Package: odoo13-addon-edi-voxel-secondary-unit
This module extends the functionality of ‘Product Secondary Unit’ module
to support Voxel Units of Measure codes in ‘Secondary Units of measure’.This is a base module for the following modules:edi_voxel_sale_secondary_unitedi_voxel_stock_picking_secondary_unitTable of contentsUsageBug TrackerCreditsAuthorsContributorsMaintainersUsageTo use this module, you need to:Go to aProduct > General Information tab.Create or edit a “Secondary unit of measure”.Set the corresponding ‘Voxel code’.If ‘Sale Order Secondary Unit’ module is installed, you can create or
edit a “Secondary unit of measure” by going toSales > Configuration > Products > Secondary Units of MeasureBug TrackerBugs are tracked onGitHub Issues.
In case of trouble, please check there if your issue has already been reported.
If you spotted it first, help us to smash it by providing a detailed and welcomedfeedback.Do not contact contributors directly about support or help with technical issues.CreditsAuthorsTecnativaContributorsTecnativa:Ernesto TejedaPedro M. BaezaMaintainersThis module is maintained by the OCA.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.Currentmaintainer:This module is part of theOCA/ediproject on GitHub.You are welcome to contribute. To learn how please visithttps://odoo-community.org/page/Contribute.