Saravanan666/pypi-org huggingface dataset:
Package: odoo11-addon-purchase-order-type
Adds a configurabletypeon the purchase orders.
This type can be used in filters and groupbys.Table of contentsConfigurationUsageKnown issues / RoadmapBug TrackerCreditsAuthorsContributorsMaintainersConfigurationTo configure this module, you need to:Go toPurchases > Configuration > Purchase typesModify / create the purchase order typesUsageTo use this module, you need to:Attribute a type when editing purchase ordersKnown issues / RoadmapSuggestion: add a default configuration attached to the typesBug 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.CreditsAuthorsCamptocampContributorsGuewen Baconnier <guewen.baconnier@camptocamp.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/purchase-workflowproject on GitHub.You are welcome to contribute. To learn how please visithttps://odoo-community.org/page/Contribute.
Package: odoo11-addon-purchase-order-ubl
This module adds support for UBL, theUniversal Business Language (UBL)standard,
on purchase orders. The UBL 2.1 standard became theISO/IEC 19845standard
in December 2015 (cf theofficial announce).With this module, when you generate the purchase order or RFQ report:on a draft/RFQ/Bid Received purchase order, the PDF file will have an embedded XMLRequest For Quotationfile compliant with the UBL 2.1 or 2.0 standard.on an approved purchase order, the PDF file will have an embedded XMLOrderfile compliant with the UBL 2.1 or 2.0 standard.If your supplier has Odoo and has installed the modulesale_order_import_ubl, he will be able to import the PDF file and it will automatically create the quotation/sale order.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.CreditsAuthorsAkretionContributorsAlexis de Lattre <alexis.delattre@akretion.com>Andrea Stirpe <a.stirpe@onestein.nl>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: odoo11-addon-purchase-order-variant-mgmt
This module allows to add/modify of all the variants of a product in a direct
screen without the need of handling them one by oneTable of contentsInstallationConfigurationUsageBug TrackerCreditsAuthorsContributorsMaintainersInstallationThis module requires the module web_widget_x2many_2d_matrix, which is located
at OCA/web repository.ConfigurationConfigure your user to have any permission from “Sales” group.Create a product with 2 attributes and several values.UsageGo to Purchases > Purchases > Request for QuotationCreate a new quotation or edit an existing one.Press “Add variants” button located in the upper right corner of the
“Order Lines” tab.A new screen will appear allowing you to select the products that have
variants.Once you select the product, a 2D matrix will appear with the first
attribute values as columns and the second one as rows.If there are already order lines for the product variants, the current
quantity will be pre-filled in the matrix.Change the quantities for the variant you want and click on “Transfer to
order”Order lines for the variants will be created/removed to comply with the
input you have done.As extra feature for saving steps, there’s also a button on each existing line
that corresponds to a variant that opens the dialog directly with the product
selected.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:Pedro M. BaezaJairo LlopisComunitea:Javier Colmenero <javier@comunitea.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/product-variantproject on GitHub.You are welcome to contribute. To learn how please visithttps://odoo-community.org/page/Contribute.
Package: odoo11-addon-purchase-procurement-run-buy-hook
Purchase Procurement Run Buy HookThis module adds hooks to method ‘_run_buy’ of model ‘procurement.rule’. The
currently supported hooks are:Allow to add more data to an existing purchase order line, when a
procurement is extending it.UsageBug 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 smash it by providing detailed and welcomed feedback.CreditsContributorsJordi Ballester <jordi.ballester@eficent.com>.MaintainerThis 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.To contribute to this module, please visithttps://odoo-community.org.
Package: odoo11-addon-purchase-product-usage
When purchasing, users can indicate a usage from a list, for every item in the
purchase order.Usages can be associated with specific accounts. When the supplier invoice is
created from that purchase order line, the account defined for that usage
will be proposed, instead of the product’s default expense account. This
proposal will only be effective if the product is a consumable or a service.Usages can be very diverse, like internal use, marketing use, testing use.
So a product “Paper” could potentially translate to marketing expense,
or an office expense, irrespective of what is the expense account defined in
the product “Paper”.Table of contentsConfigurationUsageBug TrackerCreditsAuthorsContributorsMaintainersConfigurationIn order to be able to define usages, assign users to the group
“Define Purchase Product Usages”. The group is proposed by default to users
in the group “Purchase Manager”Go toPurchases / Configuration / Purchase Product Usagesand define
the usages, indicating the description and optionally the code, default
product and account to use.UsageIn the PO line set the usage of the purchased product.
If the usage has a default product it will be set in the PO line.
If the product is a consumable or a service then the invoice will take the
account from the usage. In any other case the normal behavior is expected.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.CreditsAuthorsEficentContributorsJordi Ballester Alomar <jordi.ballester@eficent.com>Aaron Henriquez <ahenriquez@eficent.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/purchase-workflowproject on GitHub.You are welcome to contribute. To learn how please visithttps://odoo-community.org/page/Contribute.
Package: odoo11-addon-purchase-reception-notify
This module notifies to the employees following a the purchase order
when the associated products have been received into stock.This module creates a new message subtype specifically created for those
notifications. This subtype is internal activated by default when subscribing.
The old purchase orders will be updated to assign this new subtype to the
existing followers, as long as they are still active employees.Table of contentsUsageBug TrackerCreditsAuthorsContributorsMaintainersUsageIntegrated in the normal flow.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.CreditsAuthorsEficentContributorsAaron Henriquez <ahenriquez@eficent.com>Jordi Ballester <jordi.ballester@eficent.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/purchase-workflowproject on GitHub.You are welcome to contribute. To learn how please visithttps://odoo-community.org/page/Contribute.
Package: odoo11-addon-purchase-representative
This module adds the fieldPurchase Representativeto Purchase
Orders. This field is present in Standard Odoo v12. The user specified will
be the contact person for the purchase order.Additionally, it defaults it to the user doing a procurement to overcome the
known flaw of Odoo (until v13) which changes the user in the transaction when
usingsudo.Table of contentsUsageKnown issues / RoadmapBug TrackerCreditsAuthorsContributorsMaintainersUsageJust set thePurchase Representativein the Purchase Order header.
Then when sending the RFQ/PO to the vendor the Purchase Representative will be
the contact person (email from and reply to).Known issues / RoadmapMigration notes:The fielduser_idis out-of-the-box in v12.In v13 the user doing the transaction is respected. Check if emails are
also sent to the correct user.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.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/purchase-workflowproject on GitHub.You are welcome to contribute. To learn how please visithttps://odoo-community.org/page/Contribute.
Package: odoo11-addon-purchase-request-department
This module adds the user department in a new field in the purchase request
form and allows to group by department on the tree view.Table of contentsUsageBug TrackerCreditsAuthorsContributorsOther creditsMaintainersUsageWhen editing the ‘purchase request’ form and choosing the ‘requested_by’ field
the requester’s department will be automatically set.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.CreditsAuthorsEficentContributorsGisela Mora Comas <gisela.mora@eficent.com>Héctor Villarreal <hector.villarreal@eficent.com>Other creditsThe development of this module has been financially supported by: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/purchase-workflowproject on GitHub.You are welcome to contribute. To learn how please visithttps://odoo-community.org/page/Contribute.
Package: odoo11-addon-purchase-request-order-approved
This module computes the new PO state ‘Approved’ related to a Purchase
Request Line to display it in the Purchase Request Line tree view and adds a
‘Purchase Approved’ filter.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.CreditsAuthorsEficentContributorsGisela Mora <gisela.mora@eficent.com>Lois Rilo <lois.rilo@eficent.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/purchase-workflowproject on GitHub.You are welcome to contribute. To learn how please visithttps://odoo-community.org/page/Contribute.
Package: odoo11-addon-purchase-request-product-usage
When creating purchase requests, users can indicate a usage from a list,
for every item.This usage will then be subsequently added to the purchase order.For more information about purchase product usage please review the module
‘Purchase Product Usage’.Table of contentsUsageBug TrackerCreditsAuthorsContributorsMaintainersUsageIn the Purchase Request line set the usage of the requested product.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.CreditsAuthorsEficentContributorsJordi Ballester Alomar <jordi.ballester@eficent.com>Aaron Henriquez <ahenriquez@eficent.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/purchase-workflowproject on GitHub.You are welcome to contribute. To learn how please visithttps://odoo-community.org/page/Contribute.
Package: odoo11-addon-purchase-request-tier-validation
This module extends the functionality of Purchase Requests to support a tier validation process.Table of contentsInstallationConfigurationUsageBug TrackerCreditsAuthorsContributorsOther creditsMaintainersInstallationThis module depends onbase_tier_validation. You can find it atOCA/server-uxConfigurationA default tier is created allowing Purchase Request Manager to approve Purchase
Requests.In addition, you may want to add more tiers, so:Go toSettings > Technical > Tier Validations > Tier Definition.Create as many tiers as you want for Purchase Order model.UsageTo use this module, you need to:Create a Purchase Request triggering at least one “Tier Definition”.Click onRequest Validationbutton.Under the tabReviewshave a look to pending reviews and their statuses.Once all reviews are validated button toConfirmwill be shown.Additional features:You can filter the Purchase Request requesting your review through the filterNeeds my
Review.User with rights to confirm the Purchase Request (validate all tiers that would
be generated) can directly do the operation, this is, there is no need for
her/him to request a validation.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.CreditsAuthorsEficentContributorsAdria Gil <adria.gil@eficent.com>Other creditsImagesEnric Tobella (logo)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/purchase-workflowproject on GitHub.You are welcome to contribute. To learn how please visithttps://odoo-community.org/page/Contribute.
Package: odoo11-addon-purchase-request-usage-department
Introduce usages in hr departments.
It automatically selects the default usage of the department of the user when
creating purchase requests.Table of contentsUsageBug TrackerCreditsAuthorsContributorsOther creditsMaintainersUsageAdd a default usage to departments. When creating purchase requests the usage
is auto selected.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.CreditsAuthorsEficentContributorsAaron Henriquez <ahenriquez@eficent.com>Other creditsThe development of this module has been financially supported by: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/purchase-workflowproject on GitHub.You are welcome to contribute. To learn how please visithttps://odoo-community.org/page/Contribute.
Package: odoo11-addon-purchase-sale-inter-company
Purchase Sale Inter CompanyThis module is useful if there are multiple companies in the same Odoo database and those companies sell goods or services among themselves.
It allows to create a sale order in company A from a purchase order in company B.Imagine you have company A and company B in the same Odoo database:Company A purchase goods from company B.Company A will create a purchase order with company B as supplier.This module automate the creation of the sale order in company B with company A as customer.ConfigurationTo configure this module, you need to go to the menuSettings > Companies > Companies.Select one of the companies.Go to the tabInter-Companythen the groupPurchase To Sale.Select theWarehouse For Sale Orders, it is the warehouse that will be used to automatically generate the sale order in the other company.If you check the optionSale Auto Validationin the configuration of company B, then when you validate aPurchase Orderin company A with company B as supplier, then theSale Orderwill be automatically validated in company B with company A as customer.UsageBug 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 smash it by providing detailed and welcomed
feedback.CreditsContributorsOdoo S.A.Chafique Delli <chafique.delli@akretion.com>Alexis de Lattre <alexis.delattre@akretion.com>Lorenzo Battistini <lorenzo.battistini@agilebg.com>Tecnativa:Carlos DaudenJairo LlopisMaintainerThis 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.To contribute to this module, please visithttps://odoo-community.org.
Package: odoo11-addon-purchase-stock-picking-restrict-cancel
This module extends stock_picking_restrict_cancel_with_orig_move to consider
blocking purchase orders.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.CreditsAuthorsCamptocampContributorsAkim Juillerat <akim.juillerat@camptocamp.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/stock-logistics-workflowproject on GitHub.You are welcome to contribute. To learn how please visithttps://odoo-community.org/page/Contribute.
Package: odoo11-addon-purchase-stock-picking-return-invoicing-force-invoiced
This module forces the status of the purchase order to remain in ‘Invoiced’
even when you have returned items into stock, if you indicated in the purchase
order that you wanted to force the invoiced status.It is a glue module between the module ‘Purchase Force Invoiced’ and
‘Purchase Stock Picking Return Invoicing’.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.CreditsAuthorsEficentContributorsEficent <http://www.eficent.com>:Jordi Ballester Alomar <jordi.ballester@eficent.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/account-invoicingproject on GitHub.You are welcome to contribute. To learn how please visithttps://odoo-community.org/page/Contribute.
Package: odoo11-addon-purchase-stock-price-unit-sync
This module allows to sync picking cost prices with purchase order line
price when moves are already done.Can be used with product_cost_price_avco_sync.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.CreditsAuthorsTecnativaContributorsTecnativa:Carlos Dauden <carlos.dauden@tecnativa.com>Sergio Teruel <sergio.teruel@tecnativa.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/purchase-workflowproject on GitHub.You are welcome to contribute. To learn how please visithttps://odoo-community.org/page/Contribute.