Saravanan666/pypi-org huggingface dataset:
Package: odoo13-addon-purchase-last-price-info
This module adds the last purchase info of the product.Table of contentsUsageBug TrackerCreditsAuthorsContributorsMaintainersUsageIn order to use this module, go to:Products -> Tab Purchase (see screenshot)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.CreditsAuthorsOdooMRP teamAvanzOSCTecnativa - Pedro M. BaezaContributorsAlfredo de la Fuente <alfredodelafuente@avanzosc.es>Oihane Crucelaegui <oihanecrucelaegi@avanzosc.es>Ana Juaristi <anajuaristi@avanzosc.es>Carlos Lopez Mite <celm1990@hotmail.com>Adria Gil Sorribes <adria.gil@forgeflow.com>Lois Rilo <lois.rilo@forgeflow.com>Rattapong Chokmasermkul <rattapongc@ecosoft.co.th>Tecnativa:Víctor MartínezPedro 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/purchase-workflowproject on GitHub.You are welcome to contribute. To learn how please visithttps://odoo-community.org/page/Contribute.
Package: odoo13-addon-purchase-line-procurement-group
This module changes the way procurements generate purchase order lines.
If some procurements are run for the same products and locations, but have
different procurement groups, these won’t be merged in the same purchase order
line and will instead generate a purchase order line per procurement group.Moreover this module ensures that generated stock move won’t be merged together
if they come from purchase order lines with different procurement groups.Table of contentsBug TrackerCreditsAuthorsContributorsOther creditsMaintainersBug 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>Kitti Upariphutthiphong <kittiu@ecosoft.co.th>Phuc Tran Thanh <phuc@trobz.com>Other creditsThe development of this module has been 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: odoo13-addon-purchase-location-by-line
Allows to define a specific destination location on each Purchase Order line.
When the PO is confirmed, it will generate one Incoming Shipment per
combination of destination location and expected date indicated in the
Purchase Order Lines.This module is used to send the products to different locations, that may
not be children of the default location of the same PO picking type. Not be confused.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.CreditsAuthorsForgeFlowContributorsJordi Ballester Alomar <jordi.ballester@forgeflow.com>Hizbul Bahar <hizbul25@gmail.com>Harald Panten <harald.panten@sygel.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/purchase-workflowproject on GitHub.You are welcome to contribute. To learn how please visithttps://odoo-community.org/page/Contribute.
Package: odoo13-addon-purchase-manual-currency
This module allows users to update the currency manual of Purchase Order in draft state.Example, The company will make a deal with vendor before buy product
that process maybe not same day.
So, currency rate in purchase order will calculated from order date
but Company get currency rate from date of make a deal or special currency rate.Table of contentsUsageBug TrackerCreditsAuthorsContributorsMaintainersUsageTo use this module, the company have to access rights Multi Currencies.Step to used manual currency:
#. Go to Invoicing > Configuration > Settings > Currencies > Multi-Currencies
#. Go to Purchase > Create new purchase.
#. Change to other currency (not main currency)
#. Check Manual Currency and specify your currency rateBug 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.CreditsAuthorsEcosoftContributorsSaran Lim. <saranl@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.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: odoo13-addon-purchase-manual-delivery
The goal of this module is to allow the manual creation of incoming shipments.  When installed,
a purchase order won’t impact directly the stock. It will not create the pickings upon order confirmation.
It allows the reception and the impact on stock to be done manually when needed.
The goal is to be used when a supplier does not confirm the full order at once. As the supplier
confirms the different purchase order lines, the user can manually create the incoming
shipments for those specific lines.Table of contentsUsageBug TrackerCreditsAuthorsContributorsMaintainersUsageThere are two main ways to use this module:From Purchase OrderWhen creating a purchase order and confirming it, no picking will be automatically created.
Lines with pending quantities to receive will appear in blue color, to create
the manual picking press the button “Create Incoming Shipment”:This will trigger the wizard that lets the user choose which lines should be taken for the
creation of the picking and also the quantities. Clicking on the “Create and View Picking”
will create the reception and redirect the user to the picking form.From Purchase Order LineThe module adds a new list view for Purchase Order Lines (in Purchase Menu). From there you can select multiple
PO lines (in this base module only PO lines from same PO can be selected) and create the
manual delivery. Follow the same steps as above to manually generate the incoming shipment.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.CreditsAuthorsForgeFlow S.L.ContributorsAdria Gil Sorribes <adria.gil@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: odoo13-addon-purchase-minimum-amount
This module allows you to establish and automate a specific Purchase Order
Approval Block Reason in the system: the ‘Minimum Purchase Order Amount per
Vendor’.Table of contentsConfigurationUsageSet the Purchase Approval BlockSearch existing RFQConfirm the RFQRelease the purchase approval blockNotifications to followersBug TrackerCreditsAuthorsContributorsMaintainersConfigurationGo to ‘Purchases / Purchase / Vendors’Click on a Vendor and inside the ‘Sales & Purchases’ page specify the
non-required field ‘Minimum Purchase Amount’.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 upon saving if the Untaxed Amount is below the
Purchase Minimum Amount specified in that vendor, then the Approval Block
Reason is automatically set and the Approval Block Reason is not editable
anymore.Search existing RFQThere is a filter ‘Blocked’ to search for orders that are blocked.
It is also possible to search RFQ’s with the Approval Block Reason ‘Minimum
Purchase Order Amount per Vendor’.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 blockAll the RFQ’s with a total amount surpassing the specified Minimum Purchase
Order Amount for that vendor (excluding taxes) are automatically released.If a blocked RFQ without surpassing the minimum amount wants to be
released, a user member of the security group ‘Release RFQ with approval
block’ can see a button ‘Release Approval Block’. When pressing it, anyone
seeing that RFQ is 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 smashing 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>Nikul Chaudhary <nikulchaudhary2112@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: odoo13-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 TrackerCreditsAuthorsContributorsMaintainersUsageTo 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 smashing 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>Tecnativa:Carlos RocaMaintainersThis 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: odoo13-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.The operating unit is copied to the stock picking.It implements user’s security rules.Table of contentsUsageKnown issues / RoadmapBug 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 Pickings and
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.Known issues / RoadmapProcurement Orders were removed. Procurement Operating Unit module is
deprecated. Stock Operating Unit ensures consistency between the operating unit
from different models.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.CreditsAuthorsEficentSerpent Consulting Services Pvt. Ltd.ContributorsJordi Ballester Alomar <jordi.ballester@eficent.com>Aaron Henriquez <aheficent@eficent.com>Sudhir Arya <sudhir.arya@serpentcs.com>Nicola Studer <nicola.studer@braintec-group.com>Nikul Chaudhary <nikul.chaudhary.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/operating-unitproject on GitHub.You are welcome to contribute. To learn how please visithttps://odoo-community.org/page/Contribute.
Package: odoo13-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 smashing 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: odoo13-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.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)Bug TrackerCreditsAuthorsContributorsMaintainersConfigurationTo configure this module:Go to ‘Purchase > Configuration > Settings’.In theOrderssection you can set theState ‘Approved’ in Purchase
Orders.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.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.CreditsAuthorsForgeFlowContributorsLois Rilo <lois.rilo@forgeflow.com>Rattapong Chokmasermkul <rattapongc@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.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: odoo13-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>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: odoo13-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 wich
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 RocaMaintainersThis 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.