Saravanan666/pypi-org huggingface dataset:
Package: odoo14-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.CreditsAuthorsForgeFlowContributorsGisela Mora Comas <gisela.mora@forgeflow.com>Héctor Villarreal <hector.villarreal@forgeflow.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: odoo14-addon-purchase-request-exception
This module allows you attach several customizable exceptions to your
purchase request in a way that you can filter requests by exceptions type and fix them.This is especially useful in an scenario for mass purchases requests import, because it’s likely some orders have
errors when you import them (like product not found in Odoo, wrong line
format etc.)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.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.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: odoo14-addon-purchase-request-operating-unit
This module introduces the following features:Adds the Operating Unit (OU) to the Purchase Request.The user’s default Operating Unit (OU) is proposed at the time of creating the Purchase Request.Security rules are defined to ensure that users can only see the Purchase Request of that Operating Units in which they are allowed access to.Table of contentsUsageBug TrackerCreditsAuthorsContributorsMaintainersUsageFollow these steps:Create or use an existing Operating Unit (OU) in Settings ->
Users & Configuration -> Operating Unit.Change the configuration of the Users. In Application Accesses, put an User
as Request manager and another one as Request User.Create a Purchase Request Order. By default, if there is no Approver, any
Manager with the same OU can accept the PO. If you specify an Approver, he
must be in the same Operating Unit as the Purchase Request.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.CreditsAuthorsEficentSerpentCSContributorsJordi Ballester Alomar <jordi.ballester@eficent.com>Serpent Consulting Services Pvt. Ltd. <support@serpentcs.com>Saran 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/operating-unitproject on GitHub.You are welcome to contribute. To learn how please visithttps://odoo-community.org/page/Contribute.
Package: odoo14-addon-purchase-request-operating-unit-access-all
This module allow a user to have Access all OUs’ purchase requests,
without having to add OUs in user setting.Example use case, a shared procurement team under an OU
but need to work on purchase requests of all OUs.Table of contentsConfigurationBug TrackerCreditsAuthorsContributorsMaintainersConfigurationTo configure a user to have access to all OUs’ purchase requests (without all OUs access):Go toSettings / Users & Companies / UsersFor a user, select checkbox “Access all OUs’ purchase requests”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: odoo14-addon-purchase-request-substate
This module allows to add a substate to purchase request.
For each purchase request state you can define a substate.
We this module you can define substate which allow you to extend purchase request workflow.
For example, you can add substate “To Verify” if
the order can not be approved without document checked and verifiedTable of contentsUsageBug TrackerCreditsAuthorsContributorsMaintainersUsageGo to ** Settings > Technical > Database Structure ** and Add  “Base substate”.If necessery you can add “target State values” (ex define a substate for “cancel”
state).
Substate sequence is very important.Create a purchae request and check if the substate are displayed on the header of
form view. Check if you can’t set substate defined for purchase request if sate is a To be approved.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.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: odoo14-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.CreditsAuthorsForgeFlowContributorsAdria Gil <adria.gil@forgeflow.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: odoo14-addon-purchase-request-to-requisition
This module introduces the possibility to create or extend a Purchase Agreement
from Purchase Request Lines.Table of contentsUsageBug TrackerCreditsAuthorsContributorsMaintainersUsageGo to the Purchase Request Lines from the menu entry ‘Purchase Requests’,
and also from the ‘Purchase’ menu.Select the lines that you wish to initiate the Purchase Agreement for, then go to
‘More’ and press ‘Create Purchase Agreement’. You can choose to select an existing
Draft Call for Bids or create a new one.The application attempts to consolidate the lines in the Purchase Agreement in
in as few lines as possible, for the same product, UoM and analytic account.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.CreditsAuthorsEficentAcsone SA/NVContributorsJordi Ballester Alomar <jordi.ballester@eficent.com>Jonathan Nemry <jonathan.nemry@acsone.eu>Aarón Henríquez <ahenriquez@eficent.com>Adrien Peiffer <adrien.peiffer@acsone.eu>Kitti 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.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: odoo14-addon-purchase-request-to-requisition-operating-unit
This module introduces the following features:This module pass the Operating Unit from the purchase request to the purchase agreementTable 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.CreditsAuthorsForgeflowEcosoftSerpent Consulting Services Pvt. Ltd.ContributorsJordi Ballester Alomar <jordi.ballester@forgeflow.com>Aaron Henriquez <ahenriquez@forgeflow.com>Serpent Consulting Services Pvt. Ltd. <support@serpentcs.com>Kitti 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.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: odoo14-addon-purchase-request-type
This module adds the following functions:Adds a configurabletypeon the purchase requests.Choose reduce step not to create rfq.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 Request typesModify / create the purchase request typesUsageTo use this module, you need to:Attribute a type when editing purchase requestsKnown 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.CreditsAuthorsProThaiContributorsPrapassorn Sornkaew <prapassorn.s@prothaitechnology.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: odoo14-addon-purchase-requisition-auto-rfq
This module adds a button on the purchase requisition form to create RFQs
using the suppliers configured in the products listed in the requisition.
The RFQ creation automatically detects if have duplicate suppliers in the requisition products.Table of contentsUsageBug TrackerCreditsAuthorsContributorsMaintainersUsageTo use this module, you need to:Go to PurchasesCreate a new Purchase AgreementAdd some products having suppliers configured in their templatesIn the purchase agreement the red lines indicate products without suppliersIf the purchase manager is blank, the RFQs are created with the user as purchase representativeIf the purchase manager is established, the RFQs are created with the same purchase representative as the purchase agreementConfirm the Purchase AgreementClick on the “Generate quotations from suppliers” button.New Requests for Quotations are created!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.CreditsAuthorsCamptocampMétal SartiganContributorsCamptocampJérôme Thériault <jtheriault@metalsartigan.com> (http://www.metalsartigan.com)Andrea Cattalani (Moduon)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: odoo14-addon-purchase-requisition-operating-unit
This module introduces the following features:Security rules are defined to ensure that users can only see the Purchase Requisition of that Operating Units in which they are allowed access to.Ensures that Purchase Requisition and the Warehouse in picking type belongs to the same Operating Unit (OU) .When the user creates a Purchase Order (PO) from the purchase requisition the operating unit is passed to that PO.Sets default Picking type whoes Operating Unit (OU) in Warehouse matches to that of the User.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.CreditsAuthorsForgeFlow S.L.Serpent Consulting Services Pvt. Ltd.ContributorsForgeFlow S.L. (https://www.forgeflow.com)Serpent Consulting Services Pvt. Ltd. <support@serpentcs.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: odoo14-addon-purchase-requisition-operating-unit-access-all
This module allow a user to have Access all OUs’ purchase agreement,
without having to add OUs in user setting.Table of contentsConfigurationBug TrackerCreditsAuthorsContributorsMaintainersConfigurationTo configure a user to have access to all OUs’ purchase agreement (without all OUs access):Go toSettings / Users & Companies / UsersFor a user, select checkbox “Access all OUs’ Purchase Agreement”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: odoo14-addon-purchase-requisition-tier-validation
This module extends the functionality of Purchase Agreements to support a tier validation process.Table of contentsInstallationConfigurationUsageBug TrackerCreditsAuthorsContributorsMaintainersInstallationThis module depends onbase_tier_validation. You can find it atOCA/server-uxConfigurationIn 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 Requisition model.UsageTo use this module, you need to:Create a Purchase Agreements 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 Agreements requesting your review through the filterNeeds my
Review.User with rights to confirm the Purchase Agreements (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 to smash it by providing a detailed and welcomedfeedback.Do not contact contributors directly about support or help with technical issues.CreditsAuthorsEcosoftContributorsEcosoft:Pimolnat Suntian <pimolnats@ecosoft.co.th>Kitti U. <kittiu@ecosoft.co.th> (migration 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: odoo14-addon-purchase-rfq-number
Note: This module is similar to sale_quotation_number, but for purchase/rfqPurchase for Quotation:Purchase process in draft stage just informing prices and element of communication.Purchase Order:Purchase process confirmed, the customer already have a compromise with us in terms of pay an invoice and receive our product or service.Technical ExplanationWhen you create a purchase quotation, it is numbered using the ‘purchase.rfq’
sequence.  When you confirm a purchase quotation, its rfq number is saved in the
‘rfq_number’ field and the purchase order gets a new number, retrieving it from
‘purchase.order’ sequence.With Odoo Base:Purchase for Quotation 1 Number = PO001Purchase for Quotation 2 Number = PO002With Odoo + This Module:Purchase for Quotation 1 Number = RFQ001Purchase for Quotation 2 Number = RFQ002Purchase for Quotation 1 Confirmed = Number for Purchase Order PO001 from Purchase for Quotation RFQ001Purchase for Quotation 2 Confirmed = Number for Purchase Order PO002 from Purchase for Quotation RFQ002Table of contentsConfigurationBug TrackerCreditsAuthorsContributorsOther creditsMaintainersConfigurationTo configure this module, you need to:Go toPurchases -> Configuration and uncheck ‘Use same enumeration for purchase rfq and purchase orders’.Go toPurchases -> Configuration and check ‘Auto attachment requests for quotation after confirm’.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.CreditsAuthorsProThaiContributorsPrapassorn Sornkaew <prapassorn.s@prothaitechnology.com>Other creditsOdoo Community Association:Icon.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.