Saravanan666/pypi-org huggingface dataset:
Package: odoo8-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>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: odoo8-addon-purchase-stock-analysis
Purchase Stock AnalysisThis module provides a new “Purchase Stock Analysis” report that extends the
one called “Purchase Analysis” included in the standard Purchase module, adding
a few metrics to assess the performance of suppliers.UsageThis module adds a new report “Purchase Stock Analysis” under
Reporting/Purchase. In addition to the information found in
“Purchase Analysis”, some new measures are added:Days from initial to updated scheduleDays from initial to updated Scheduled Date of deliveryDays from the updated Scheduled Date to the actual Delivery DateFor further information, please visit:https://www.odoo.com/forum/help-1Bug 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 welcomed feedbackhere.CreditsContributorsLeonardo Pistone <leonardo.pistone@camptocamp.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 visithttp://odoo-community.org.
Package: odoo8-addon-purchase-supplier-rounding-method
Purchase Supplier Rounding MethodThis module extend account module, to add new rounding method used by some
suppliers. The new rounding method is used for purchase orders and In invoices.Use CaseSome of suppliers compute invoice line subtotal differently than Odoo.In Odoo, by default:` price_subtotal = round(unit_price * (1 - discount / 100) * qty)`For some suppliers:` price_subtotal = round(round(unit_price * (1 - discount / 100)) * qty)`This module manage this second case to generate supplier invoices with the
same value.ConfigurationAdd a new field ‘rounding_method’ on a partner with two keys:‘normal’: classical computation method, by default.‘round_net_price’: round a firt time the net price, and then round again.CreditsContributorsSylvain LE GAL <https://twitter.com/legalsylvain>
Package: odoo8-addon-purchase-supplier-rounding-method-triple-discount
Purchase Supplier Rounding Method - Triple DiscountThis module is a glue module to make compatible the modules`purchase_supplier_rounding_method`and`account_invoice_triple_discount`and is automatically installed if both
modules are installed.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 smash it by providing detailed and welcomed feedback.Known issues / RoadmapFor inheritance reasons, the following function will be overwritten,
removing the call of super.`purchase.order.line`:`_calc_line_base_price()``account.nvoice.line`:`_compute_price()`CreditsContributorsSylvain LE GAL <https://twitter.com/legalsylvain>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: odoo8-addon-purchase-transport-multi-address
Purchase - Transport AddressesDescriptionThis module - together withStock - Transport Addresses(stock_transport_multi_address)
andSale - Transport Addresses(sale_transport_multi_address) - manages in a
coherent way the following addresses in the standard Odoo workflows:origin addressdestination addressconsigneeDelivery addresses management:This module adds a delivery address to the purchase order, which is
automatically propagated to a corresponding field in the generated picking.Some of this logic was present in the core, but is not functioning properly.
More specifically, in the core, a dropshipping purchase order has two fields:
partner_id is used for the supplier, and dest_address_id contains the address
of the customer. This works, except that the address is not visible because of
odoo/odoo#2950).On the other hand, the picking has only one field: the partner_id. By default,
it takes the delivery address of the PO if there is one, or else the supplier.
The stock.move also has a partner_id field that is filled with the same
partner.  To make things even more confusing, in v7 the partner_id of the move
is the supplier, while the partner_id of the picking is the customer address.This means that in v8 with core modules, we do not clearly see the supplier and
the customer address of a picking. Those two fields are important to handle
dropshipping.With this module, in dropshipping mode the generated picking will have the
supplier in the partner_id field, and the customer address in the new
delivery_address_id field.CreditsContributorsAlexandre Fayolle <alexandre.fayolle@camptocamp.com>Leonardo Pistone <leonardo.pistone@camptocamp.com>Yannick Vaucher <yannick.vaucher@camptocamp.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 visithttp://odoo-community.org.
Package: odoo8-addon-purchase-triple-discount
Purchase Triple DiscountThis module allows to have three successive discounts on every purchase order
line.UsageCreate a new purchase order and add discounts in any of the three discount
fields given. They go in order of precedence so discount 2 will be calculated
over discount 1 and discount 3 over the result of discount 2. For example,
let’s divide by two on every discount:Unit price: 600.00 ->Disc. 1 = 50% -> Amount = 300.00Disc. 2 = 50% -> Amount = 150.00Disc. 3 = 50% -> Amount = 75.00You can also use negative values to charge instead of discount:Unit price: 600.00 ->Disc. 1 = 50% -> Amount = 300.00Disc. 2 = -5% -> Amount = 315.00Bug 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.Known issues / RoadmapInclude second and third discount in purchase order report.CreditsImagesOdoo Community Association:Icon.ContributorsDavid Vidal <david.vidal@tecnativa.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: odoo8-addon-purchase-update-proposal
Allow for any user with only read only grants on Purchase Orders to suggest/ask for modification.Use cases:in case of EDI like an Order Response flow (i.e. UBL) which require to deal with update conditions on purchase lines.external user like a vendor which can readonly access to its own purchase order but want to ask for modifications.internal user with no write access on Purchase Order.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 contentsUsageBug TrackerCreditsAuthorsMaintainersUsageGo to the supplier menu
This document is modified by the supplier with specific right on its own purchase documentThis document is modified by the purchaser pending approbationFeatures:asked modifications allowed are: quantity, date or priceupdate price is optionnal according to supplierproposal with quantity set to 0 impact purchase line by cancelling line instead of update quantityexternal users are added to confirmed purchasesif proposing a null quantity, the purchase order line will be cancelled and the other line’s fields not updatedupdate quantity require to reset order to draft while price and date can be set at any timeBug 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.CreditsAuthorsAkretionMaintainersThis 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: odoo8-addon-quality-control
Quality control management for OdooThis module provides a generic infrastructure for quality tests. The idea is
that it can be later reused for doing quality inspections on production lots
or any other area of the company.DefinitionsQuestion: The thing to be checked. We have two types of questions:Qualitative: The result is a description, color, yes, no…Quantitative: The result must be within a range.Possible values: The values chosen in qualitative questions.Test: The set of questions to be used in inspections.Once these values are set, we define the inspection.We have agenerictest that can be applied to any model: shipments,
invoices or product, or atest related, making it specific to a particular
product and that eg apply whenever food is sold or when creating a batch.Once these parameters are set, we can just pass the test. We create a
new inspection, selecting a relationship with the model (sale, stock move…),
and pressing “Select test” button to choose the test to pass. Then, you must
fill the lines depending on the chosen test.The complete inspection workflow is:Draft -> Confirmed -> Success-> Failure (Pending approval) -> ApprovedBased on the nan_quality_control_* modules from NaN·tic.UsageKnown issues / RoadmapMake translatable the trigger name.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 welcomed feedbackhere.CreditsContributorsPedro M. Baeza <pedro.baeza@serviciobaeza.com>Oihane Crucelaegui <oihanecrucelaegi@avanzosc.es>Ana Juaristi <anajuaristi@avanzosc.es>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 visithttp://odoo-community.org.
Package: odoo8-addon-quality-control-force-valid
Manual validation for quality control inspectionsThis module adds a manual validation flag which allows to override the result
of the inspection.InstallationTo install this module, you need to:Clone the branch 8.0 of the repositoryhttps://github.com/OCA/manufactureAdd the path to this repository in your configuration (addons-path)Update the module listGo to menuSetting -> Modules -> Local ModulesSearch ForQuality control - Manual validationInstall the moduleUsageTo override quality control result, you need to:Go to menuQuality Control -> Inspection -> InspectionOpen inspection data with status other than Success or FailedActivateForce ValidflagInspection data with force valid always result in success when approved,
even if some inspection question are not succedBug 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 welcomed feedback.CreditsImagesOdoo Community Association:Icon.ContributorsAlfredo de la Fuente <alfredodelafuente@avanzosc.es>Pedro M. Baeza <pedro.baeza@tecnativa.com>Ana Juaristi <ajuaristio@gmail.com>OpenSynergy Indonesia <https://opensynergy-indonesia.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: odoo8-addon-quality-control-mrp
MRP extension for quality controlThis module defines a trigger that creates quality control inspections when a
production order is finished.It also adds the shortcuts related to these inspections on production orders.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 smashing it by providing a detailed and welcomed feedbackhere.CreditsContributorsPedro M. Baeza <pedro.baeza@serviciobaeza.com>Oihane Crucelaegui <oihanecrucelaegi@avanzosc.es>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 visithttp://odoo-community.org.
Package: odoo8-addon-quality-control-stock
Stock extension for quality controlThis module defines triggers that creates inspections when stock moves are done.It also adds some shortcuts on picking and lots to these inspections.UsageKnown issues / RoadmapPut trigger in all languages.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 welcomed feedbackhere.CreditsContributorsPedro M. Baeza <pedro.baeza@serviciobaeza.com>Oihane Crucelaegui <oihanecrucelaegi@avanzosc.es>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 visithttp://odoo-community.org.
Package: odoo8-addon-quick-purchase
Quick PurchaseThis module gives the possibility
to add easily product into the purchase order (mass line add/update).UsageInside a purchase order, you can click on “Add products”, to open a product tree view, then update “qty to purchase” field.The update of “qty to purchase” will add new purchase line or update the existing line. If qty to purchase is 0 it purchase line will deleted if it exists.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 smash it by providing detailed and welcomed feedback.ImagesOdoo Community Association:Icon.ContributorsSébastien BEAU <sebastien.beau@akretion.com>Mourad EL HADJ MIMOUNE <mourad.elhadj.mimoune@akretion.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: odoo8-addon-qweb-usertime
QWeb Usertime TagThis module adds a new tag renderer to QWeb, “usertime”, which allows adding
the current time in the timezone of the user. It can be used as:<t t-usertime="%Y-%m-%d %H:%M:%S" />or, if you want to use the default date and time formats based on the users
language:<t t-usertime="" />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 welcomed feedbackhere.CreditsContributorsVincent Vinet <vincent.vinet@savoirfairelinux.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 visithttp://odoo-community.org.
Package: odoo8-addon-redmine-import-time-entry
Redmine Import Time EntryConnector used to import Redmine time entries as Odoo analytic timesheets in batch.To use this module, you must add a custom field on your Redmine projects. You can give the name you want
to this field, but every project must have a different value for this field.In Odoo, you must create an analytic account for each Redmine project.
The value of the custom field must be written in the field ref (‘Reference’) of the analytic account.InstallationNothing to do.Configuration# Go to Connectors -> Redmine -> Backends and select your Redmine backend# Enter the name of the custom field used to identify projects in Redmine# Click on the button to test the custom field# The field “Time Entries - Number of days” is by default set to 14. This means that the connector willonly fetch time entries that have a date between 2 weeks ago and now. Of course, the connector will only
create single jobs for Redmine records that have been updated since the last update.You must set one Redmine service as the default one. For this, you may check the boxDefault Redmine Service.
By default, the timesheets of every user will be imported from that redmine service. If a user needs to
import his timesheets from a different redmine service, he may change it in his preference settings,
the same way you switch companies.UsageTo use this module, you need to:Go to …Known issues / RoadmapThe Redmine API does not allow to fetch time entry records based on the last update field.
For this reason, the connector fetches every records for a period of time (e.g. 2 weeks) as explained in Configuration.Timesheet Entries UpdateIn vanilla Odoo, there is a flaw of design with the timesheet widget. When you modify a time entry using
the widget, instead of updating the existing records, Odoo deletes all records and creates all of them from
the begginning. Not only it has a performance impact, but it also conflicts with the Redmine Connector. This is
why the widget is fixed in this module so that entries are updated intead of recreated.This issue has another impact. The field partner_id on analytic.timesheet.line is related and it is not readonly.
This is a flaw of design but in vanilla Odoo, it does not cause issues because of the entries are not updated.
Therefore, the field partner_id is set to readonly to prevent access errors.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 welcomed feedback.CreditsContributorsMaxime Chambreuil <maxime.chambreuil@savoirfairelinux.com>David Dufresne <david.dufresne@savoirfairelinux.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: odoo8-addon-report-custom-filename
Custom report filenamesThis addon allows for custom filenames for reports.ConfigurationTo configure this module, open the report whose filename you want to change and fill in theDownload filenamefield. This field is evaluated as jinja2 template withobjectsbeing a list of browse records of the records to print, andothe first record. If your model contains a name field, you might write something like${o.name}_report.pdfas filename.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 welcomed feedbackhere.CreditsContributorsHolger Brunn <hbrunn@therp.nl>IconIcon courtesy ofhttp://www.picol.org/(download_settings.svg)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 visithttp://odoo-community.org.
Package: odoo8-addon-report-qweb-element-page-visibility
Report Qweb Element Page VisibilityThis module allows you to use 4 classes in QWEB reports:not-first-page: shows element in every page but firstnot-last-page: shows element in every page but lastfirst-page: shows element only on first pagelast-page: shows element only on last pageUsageTo use this module, you need to:In the QWEBir.ui.viewsused by your report,
you can add an element with css class with any of the classes described above.
For example if you need to improve invoice report header with
invoice’s number in every page but first, and sale order report header
with order’s name in every page but last, add this code to external_layout_header:<t t-if="o._table=='account_invoice'">
    <div class="not-first-page">
        <span t-esc="o.number"/>
    </div>
</t>
<t t-if="o._table=='sale_order'">
    <div class="not-last-page">
        <span t-esc="o.name"/>
    </div>
</t>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 welcomed feedbackhere.CreditsContributorsNicola Malcontenti <nicola.malcontenti@agilebg.com>Lorenzo Battistini <lorenzo.battistini@agilebg.com>Alessio Gerace <alessio.gerace@agilebg.com>Alex Comba <alex.comba@agilebg.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 visithttp://odoo-community.org.