Saravanan666/pypi-org huggingface dataset:
Package: odoo-addon-purchase-only-by-packaging
This module provides different configuration option to manage packagings on
purchase orders.The creation/update of purchase order line will be blocked (by constraints) if the data on the
purchase.order.line does not fit with the configuration of the product’s packagings.It’s also possible to force the quantity to purchase during creation/modification of the purchase order line
if the “Force purchase quantity” is ticked on the packaging and the “Purchase only by packaging” is ticked on product.For example, if your packaging is set to purchase by 5 units and the employee fill
the quantity with 3, the quantity will be automatically replaced by 5 (it always rounds up).ImportantThis 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 contentsConfigurationBug TrackerCreditsAuthorsContributorsOther creditsMaintainersConfigurationFollowing options are available to define which packaging level can be purchased and
which product can only be purchased by packaging.Purchase only by packaging: On product template model, this checkbox restricts
purchases of these products if no packaging is selected on the purchase order line.
If no packaging is selected, it will either be auto-assigned if the quantity
on the purchase order line matches a packaging quantity or an error will be raised.Force purchase quantity (on the packaging): force rounds up the quantity during
creation/modification of the purchase order line with the factor set on the packaging.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.CreditsAuthorsCamptocampBCIMContributorsAkim Juillerat <akim.juillerat@camptocamp.com>Thomas Nowicki <thomas.nowicki@camptocamp.com>François Honoré <francois.honore@acsone.eu>Hiep (Nguyen Hoang) <hiepnh@trobz.com>Phuc (Tran Thanh) <phuc@trobz.com>Duong (Tran Quoc) <duongtq@trobz.com>Telmo Santos <telmo.santos@camptocamp.com>Jacques-Etienne Baudoux (BCIM) <je@bcim.be>Other creditsThe development of this module has been financially supported by:CamptocampThis module feature was extracted from the originalsale-workflow/sale_by_packagingmodule.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: odoo-addon-purchase-open-qty
This module allows purchase users to identify what are the purchase
orders that currently have quantities pending to invoice or to receive.Table of contentsUsageBug TrackerCreditsAuthorsContributorsOther creditsMaintainersUsageTo use this module, you need to go to Purchase Orders and select the new
filters in the search.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.CreditsAuthorsForgeFlowContributorsMiquel Raïch <miquel.raich@forgeflow.com>Andreas Dian Sukarno Putro <andreasdian777@gmail.com>Kitti Upariphutthiphong <kittiu@ecosoft.co.th>Eric Antones <eantones@nuobit.com>Juany Davila <juany.davila@forgeflow.com>Tecnativa:Carlos RocaTrobz<https://trobz.com>_:Son Hosonhd@trobz.comOther creditsThe migration of this module from 16.0 to 17.0 was financially supported
by CamptocampMaintainersThis 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: odoo-addon-purchase-operating-unit
This module introduces the following features:It introduces the operating unit to the purchase order.The operating unit is copied to the invoice.It implements user’s security rules.Table of contentsUsageBug TrackerCreditsAuthorsContributorsMaintainersUsageCreate a PO: the Default Operating Unit is assigned to the PO. If you want,
you can change to another Operating Unit.Validate the PO: the Operating Unit is propagated to the Invoices.From the invoice, it is not possible to change the Operating Unit, it has to
be the same as the one of the PO.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.CreditsAuthorsForgeFlowSerpent Consulting Services Pvt. Ltd.ContributorsJordi Ballester Alomar <jordi.ballester@forgeflow.com>Aaron Henriquez <ahforgeflow@forgeflow.com>Sudhir Arya <sudhir.arya@serpentcs.com>Nicola Studer <nicola.studer@braintec-group.com>Nikul Chaudhary <nikul.chaudhary.serpentcs@gmail.com>Kitti U. <kittiu@ecosoft.co.th>Alan Ramos <alan.ramos@jarsa.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/operating-unitproject on GitHub.You are welcome to contribute. To learn how please visithttps://odoo-community.org/page/Contribute.
Package: odoo-addon-purchase-operating-unit-access-all
This module allow a user to have Access all OUs’ purchase orders,
without having to add OUs in user setting.Example use case, a shared procurement team under an OU
but need to work on purchase orders of all OUs.Table of contentsConfigurationBug TrackerCreditsAuthorsContributorsMaintainersConfigurationTo configure a user to have access to all OUs’ purchase orders (without all OUs access):Go toSettings / Users & Companies / UsersFor a user, select checkbox “Access all OUs’ purchase orders”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.CreditsAuthorsEcosoftContributorsKitti U. <kittiu@ecosoft.co.th>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/operating-unitproject on GitHub.You are welcome to contribute. To learn how please visithttps://odoo-community.org/page/Contribute.
Package: odoo-addon-purchase-order-analytic-search
Organizations often require to quickly find the purchase orders associated to
an analytic account, searching by it’s code, name or project/account manager.This module introduces the possibility to search purchase orders by analytic
account.It also introduces a new menu entry in Purchasing to list purchase order lines.Table of contentsUsageBug TrackerCreditsAuthorsContributorsMaintainersUsageTo use this module, you need to:Check ‘Analytic Accounting’ on user settingsAdd analytic account to purchase order lineFilter purchase orders by analytic accountsBug 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.CreditsAuthorsForgeFlowCamptocampContributorsGisela Mora <gisela.mora@forgeflow.com>Serpent Consulting Services Pvt. Ltd. <support@serpentcs.com>Alexandre Fayolle <alexandre.fayolle@camptocamp.com>Watcharaporn Charamrum <watcharapornc@ecosoft.co.th>Juany Davila <juany.davila@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: odoo-addon-purchase-order-approval-block
This module allows you to block the approval of an RFQ when an Approval
Block Reason has been provided. Upon confirmation of an RFQ the orders will be
waiting for approval by a Manager.Table of contentsConfigurationUsageSet the Purchase Approval BlockSearch existing RFQConfirm the RFQRelease the purchase approval blockNotifications to followersBug TrackerCreditsAuthorsContributorsMaintainersConfigurationGo to ‘Purchases / Configuration / Purchase Approval Block Reasons’ and create
the blocking reasons as needed, providing a name and a description. A field
‘Active’ allows you to deactivate the reason if you do not plan to use it
any more.Assign the security group ‘Release RFQ with approval block’ to users that
should be able to release the block. Users in group ‘Purchase / Managers’
are by default assigned to this group.UsageSet the Purchase Approval BlockGo to ‘Purchases / Purchase / Requests for Quotation’Create a new RFQ and indicate the approval block reason (found in the
right hand side of the screen, below the order date).Search existing RFQThere is a filter ‘Blocked’ to search for orders that are blocked for approval.
It is also possible to search RFQ’s with a specific block reason.Confirm the RFQPress the button ‘Confirm’. If there’s an approval block, the order will
be set to status ‘To Approve’. You will then need to request a Purchase
Manager to approve it.Release the purchase approval blockWhile the RFQ is in draft, members of security group ‘Release RFQ with approval block’,
can see a button ‘Release Approval Block’. From this point and on, anyone
seeing that RFQ will be able to validate it.Notifications to followersFollowers of the RFQ receive notifications when an approval block has been
set or released.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.CreditsAuthorsForgeFlowContributorsJordi Ballester Alomar <jordi.ballester@forgeflow.com>Roser Garcia <roser.garcia@forgeflow.com>Darshan Patel <darshan.patel.serpentcs@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.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: odoo-addon-purchase-order-approved
This module extends the functionality of purchases adding a new stateApprovedin purchase orders before thePurchase Orderstate. Additionally
add the possibility to set back to draft a purchase order in all the states
previous toPurchase Order. From a user point of view, this change introduces
a two-step validation process of the purchase order.In this newApprovedstate:You cannot modify the purchase order.However, you can go back to draft and pass through the workflow again.The incoming shipments are not created. You can create them by clicking theConvert to Purchase Orderbutton, also moving to statePurchase Order.The new state diagram is depicted below:Table of contentsConfigurationUsageChangelog11.0.1.0.0 (2018-06-06)12.0.1.0.0 (2019-06-13)12.0.1.0.0 (2020-07-16)15.0.1.0.0 (2021-12-05)16.0.1.0.0 (2023-02-28)Bug TrackerCreditsAuthorsContributorsMaintainersConfigurationThis new workflow can be activated by company and by supplier.To activate the new workflow by company:Go to ‘Purchase > Configuration > Settings’.In theOrderssection you can set theState ‘Approved’ in Purchase
Orders.To activate the new workflow by supplier:Open the supplier form view.In thePurchasesection in theSales & Purchasestab the fieldPurchase requires second approvalallows you to select the policy to
apply for the current supplier. ‘Never’ | ‘Always’ | ‘Based on company policy’UsageTo use this module, you need to:Go to a Request for Quotation.ClickConfirm Order. The state is nowApproved(if no order approval
is not set).To move forward to the statePurchase Orderand release the creation
of the deliveries, click onConvert to Purchase Order.Changelog11.0.1.0.0 (2018-06-06)[MIG] Migrated to v11.12.0.1.0.0 (2019-06-13)[MIG] Migrated to v12.12.0.1.0.0 (2020-07-16)[MIG] Migrated to v13.15.0.1.0.0 (2021-12-05)[MIG] Migrated to v15.16.0.1.0.0 (2023-02-28)[MIG] Migrated to v16.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.CreditsAuthorsForgeFlowACSONE SA/NVContributorsLois Rilo <lois.rilo@forgeflow.com>Rattapong Chokmasermkul <rattapongc@ecosoft.co.th>Laurent Mignon <laurent.mignon@acsone.eu>Moaad Bourhim <moaad.bourhim@gmail.com>Rolando Duarte <rolando@vauxoo.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: odoo-addon-purchase-order-archive
On a system with a high volume of purchases, the number of purchase orders displayed in the list view can become huge.
This module allows to archive Purchase Orders that are in status Locked or Cancelled.If a purchase order is archived, it will be hidden from the purchase orders list view.This module only depends on module purchase, but it could be used in combination with OCA module ‘record_archiver’
in order to automatically archive old purchase orders.Table of contentsUsageBug TrackerCreditsAuthorsContributorsMaintainersUsageTo archive purchase orders, you need to:Open the tree view of purchase orders.Select a purchase order (in status Locked or Cancelled) you want to archive.Click on Action > Archive. Confirm.The purchase order is now archived.To unarchive purchase orders, you need to:Open the tree view of purchase orders.In the filter box select the Archived filter. The list of archived purchase orders will be displayed.Select the purchase order (in status Locked or Cancelled) you want to restore to Active.Click on Action > Unarchive.The purchase order is now active.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.CreditsAuthorsOnesteinContributorsAndrea Stirpe <a.stirpe@onestein.nl>Christihan Laurel <laurel@vauxoo.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: odoo-addon-purchase-order-general-discount
This module allows to set a general discount in a purchase order. This general
discount is applied to each line order.You can also set a default general discount on suppliers and configure to which
line field the discount will be applied.Table of contentsConfigurationUsageBug TrackerCreditsAuthorsContributorsMaintainersConfigurationYou can set in settings another discount field to be applied.
For example, if we hadpurchase_triple_discount, we could set the general
discount in discount3 to be applied after all other discounts.To do so:Go toPurchases > Configuration > SettingsandPurchase Discount FieldSelect the discount you’d wish to use.purchase_triple_discountfields
will appear when the module is installed.There’s a method atres.companycalled_get_purchase_discount_fieldsthat
can be used to extend more line discount fields. For example, if we had the
fielddiscount4, we could extend it like this:@api.modeldef_get_purchase_discount_fields(self):discount_fields=super()._get_purchase_discount_fields()discount_fields+=[('discount4',_('Discount 4'))]returndiscount_fieldsUsageTo set a partner default general discount you need to:Go to a partner and set the general discount inSales & Purchasestab.To set a general discount in a purchase order you need to:Create a purchase order.Either select a partner with a purchase general discount defined or set one
in the summary section of the order.This discount will be applied to every line.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:David VidalPedro M. BaezaRafael BlascoCarlos RocaPilar VargasAures TIC:Jose ZambudioAnna MartinezKomit:Cuong Nguyen Mtm <cuong.nmtm@komit-consulting.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: odoo-addon-purchase-order-hide-receipt-status
This module is designed to enhance the user experience by hiding the “receipt_status” field
in purchase order form view and tree view. The purpose is to avoid any confusion that may arise
when ‘reception_status’ field becomes visible once the ‘purchase_reception_status’ module is installed.Table of contentsBug TrackerCreditsAuthorsMaintainersBug 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.CreditsAuthorsQuartile LimitedMaintainersThis 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: odoo-addon-purchase-order-line-deep-sort
This module was written to extend the functionality of purchase order and allow
you to manage sort of lines.You can set the default sort order for the current company or you can set sort
order for a particular purchase order.Table of contentsConfigurationUsageKnown issues / RoadmapBug TrackerCreditsAuthorsContributorsMaintainersConfigurationSort criteria items can be defined with a dot notation. This means that you
can define an order as follows:product_id.default_code. But the field
defined must exist in database. If you define, e.g., a calculated field, sort
criteria won’t work.UsageGo toPurchase > Settings > Default Sort Criteriaand select one.You must select sort direction too.Create a new purchase and add several lines.On saving purchase order you must see how the purchase lines are ordered
with your selected sort order.Known issues / RoadmapAdd support for ordering purchase lines by partner.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:Vicent Cubells <vicent.cubells@tecnativa.com>Pedro M. BaezaStefan UngureanuProthai:Prapassorn Sornkaew <prapassorn.s@prothaitechnology.com> (migrate to v14)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: odoo-addon-purchase-order-line-menu
Adds a menu item and some views to navigate through Purchase Order lines.Table of contentsUsageBug TrackerCreditsAuthorsContributorsMaintainersUsageMenu option available at Purchase > Orders > Purchase Order Lines.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.CreditsAuthorsOpen Source IntegratorsContributorsOpen Source Integrators <https://opensourceintegrators.com>:Daniel Reis <dreis@opensourceintegrators.com>Freni Patel <fpatel@opensourceintegrators.com>Murtaza Mithaiwala <mmithaiwala@opensourceintegrators.com>Moduon Team <https://moduon.team>:Eduardo de Miguel <edu@moduon.team>Emilio Pascual <emilio@moduon.team>Rafael Blasco <rblasco@moduon.team>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.