Saravanan666/pypi-org huggingface dataset:
Package: odoo13-addon-mrp-production-putaway-strategy
This module allows to apply putaway strategies to the products resulting from
the manufacturing orders.The finished products will be placed in the location designated by the putaway
strategy (if they do not have another destination move), based on the
finished products location that was defined in the manufacturing order.Table of contentsConfigurationUsageBug TrackerCreditsAuthorsContributorsMaintainersConfigurationTo configure a putaway strategy follow the next steps:Go to ‘Inventory / Settings’. Activate the option ‘Multi-Step Routes’ and
save.Go again to ‘Inventory / Settings’ and press
‘Set Putaway Strategies on Locations’. Then define a putaway strategy in
the location zone where the finished products are supposed to be placed,
and indicate the specific sub-location/bin where the products should
be placed.UsageTo use this module proceed as follows:Create a manufacturing order and indicate the product and the finished
products location zone.Confirm the manufacturing order.You will notice that the finished products location has changed to the
putaway location, and the chatter shows a message indicating that the
putaway strategy was applied.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 <jordi.ballester@forgeflow.com>Lois Rilo <lois.rilo@forgeflow.com>Sudhir Arya <sudhir@erpharbor.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/manufactureproject on GitHub.You are welcome to contribute. To learn how please visithttps://odoo-community.org/page/Contribute.
Package: odoo13-addon-mrp-sale-info
This module extends the functionality of Odoo for adding related fields to
Manufacturing Orders and Work Orders:Sale orderCustomerCommitment DateTable of contentsUsageBug TrackerCreditsAuthorsContributorsMaintainersUsageNew fields are displayed in tree and in form views (Extra information tab).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.CreditsAuthorsAvanzOSCTecnativaContributorsAvanzOsc:Oihane Crucelaegui <oihanecrucelaegi@avanzosc.es>Ana Juaristi <anajuaristi@avanzosc.es>Tecnativa:Antonio EspinosaRafael BlascoPedro M. BaezaRubén Bravo <rubenred18@gmail.com>Bhavesh Odedra <bodedra@opensourceintegrators.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/manufactureproject on GitHub.You are welcome to contribute. To learn how please visithttps://odoo-community.org/page/Contribute.
Package: odoo13-addon-mrp-stock-orderpoint-manual-procurement
This module updates a new fieldRequested byin Manufacturing Orders
in the case the MO has been created as a result of a manual procurement from
an orderpoint.Table of contentsUsageBug TrackerCreditsAuthorsContributorsMaintainersUsageGo to an orderpoint and do a manual procurement for a manufactured product.
Your user will be set asRequeste byin the newly created MO.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.CreditsAuthorsForgeflowContributorsAdria Gil Sorribes <adria.gil@forgeflow.com>Lois Rilo Antelo <lois.rilo@forgeflow.com>Pimolnat Suntian <pimolnats@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/manufactureproject on GitHub.You are welcome to contribute. To learn how please visithttps://odoo-community.org/page/Contribute.
Package: odoo13-addon-mrp-unbuild-tracked-raw-material
Odoo has a limitation on tracked product’s components
which are not manufactured in the ERP.When you try to do it, you get this warning:Some of your components are tracked, you have to specify a manufacturing order in order to retrieve the correct components.Unfortunately, it doesn’t cover all the use cases.Example:
You receive eggs and you want to unbuild them in 2 parts:yellow partwhite partEach of the parts are tracked and not linked to a previous manufacturing order
because, you don’t build the eggs yourself, you subcontract it to a chicken.Table of contentsConfigurationUsageKnown issues / RoadmapBug TrackerCreditsAuthorsContributorsMaintainersConfigurationCustomize method_prepare_lots_for_purchased_unbuild()to define your own data lotUsage# Check ‘Allow Unbuild Purchased’ field in Inventory tab on product form
for any product with a bom you didn’t manufactured but you want unbuild.# Go to Manufacturing > Operations > Unbuild Orders# Encode an unbuild order with the product used in first stepKnown issues / RoadmapThis module doesn’t take account productallow_unbuild_purchasedchecked
which useserialtrackingBug 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.CreditsAuthorsAkretionContributorsAkretion:David Béal <david.beal@akretion.com>Pimolnat Suntian <pimolnats@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/manufactureproject on GitHub.You are welcome to contribute. To learn how please visithttps://odoo-community.org/page/Contribute.
Package: odoo13-addon-mrp-warehouse-calendar
With this module the manufacturing orders created from procurements consider
the calendar assigned to the warehouse of the picking type of the
manufacturing order to determine, based on the product’s manufacturing
lead time, the planned start date of the manufacturing order.Further manual replannings of start/end date of the manufacturing order
also consider the lead time using the warehouse calendar days.Table of contentsConfigurationUsageBug TrackerCreditsAuthorsContributorsMaintainersConfigurationThis module depends onstock_warehouse_calendarGo toSettingsand activate the developer mode.Go toSettings > Technical > Resource > Working Timeand define your
resource calendar.Go toInventory > Configuration > Warehouse Management > Warehousesand assign the Resource Calendar.UsageWhen a manufacturing order is created out of a procurement evaluation
(from an orderpoint, MTO,…) the calendar is considered in the computation
of the planned start date of the manufacturing order.For example, if it takes 1 day to manufacture a product and it is required
for Monday, the manufacturing order will be created with planned start date
on the previous Friday, if the warehouse operates under a Mo-Fri working
calendar.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 <jordi.ballester@forgeflow.com>Lois 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.Currentmaintainer:This module is part of theOCA/manufactureproject on GitHub.You are welcome to contribute. To learn how please visithttps://odoo-community.org/page/Contribute.
Package: odoo13-addon-mrp-workorder-sequence
Provide a new field sequence on production orders’s work orders, that provides
clear information on the process order of those.Table of contentsUsageBug TrackerCreditsAuthorsContributorsMaintainersUsageGo to any production order with a routing set and check its work 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.CreditsAuthorsForgeFlowContributorsLois Rilo <lois.rilo@forgeflow.com>Pimolnat Suntian <pimolnats@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/manufactureproject on GitHub.You are welcome to contribute. To learn how please visithttps://odoo-community.org/page/Contribute.
Package: odoo13-addon-mrp-workorder-update-component
Allows to update the components in the work 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.CreditsAuthorsForgeFlowContributorsDavid Jiménez <david.jimenez@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.Currentmaintainer:This module is part of theOCA/manufactureproject on GitHub.You are welcome to contribute. To learn how please visithttps://odoo-community.org/page/Contribute.
Package: odoo13-addon-multi-step-wizard
This module is a base for creating multi-steps wizards. It does nothing by
itself.Table of contentsUsageBug TrackerCreditsAuthorsContributorsMaintainersUsageExample of class:classMyWizard(models.TransientModel):_name='my.wizard'_inherit=['multi.step.wizard.mixin']project_id=fields.Many2one(comodel_name='project.project',name="Project",required=True,ondelete='cascade',default=lambdaself:self._default_project_id(),)name=fields.Char()field1=fields.Char()field2=fields.Char()field3=fields.Char()@api.modeldef_selection_state(self):return[('start','Start'),('configure','Configure'),('custom','Customize'),('final','Final'),]@api.modeldef_default_project_id(self):returnself.env.context.get('active_id')defstate_exit_start(self):self.state='configure'defstate_exit_configure(self):self.state='custom'defstate_exit_custom(self):self.state='final'Example of view (note the mode, must be primary):<?xml version="1.0" encoding="utf-8"?><odoo><recordid="my_wizard_form"model="ir.ui.view"><fieldname="name">my.wizard.form</field><fieldname="model">my.wizard</field><fieldname="mode">primary</field><fieldname="inherit_id"ref="multi_step_wizard.multi_step_wizard_form"/><fieldname="arch"type="xml"><xpathexpr="//footer"position="before"><h1><fieldname="name"attrs="{'readonly': [('state', '!=', 'start')]}"class="oe_inline"placeholder="Name"/></h1><groupname="configure"attrs="{'invisible': [('state', '!=', 'configure')]}"><group><fieldname="field1"/><fieldname="field2"/></group></group><groupname="custom"attrs="{'invisible': [('state', '!=', 'custom')]}"><group><fieldname="field3"/></group></group><divname="final"attrs="{'invisible': [('state', '!=', 'final')]}"><p>Theprojectisnowconfigured.</p></div></xpath></field></record><act_windowid="open_my_wizard"name="My Wizard"res_model="my.wizard"src_model="project.project"view_mode="form"target="new"view_type="form"/></odoo>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.CreditsAuthorsCamptocampContributorsGuewen Baconnier <guewen.baconnier@camptocamp.com>CorporateHubAlexey Pelykh <alexey.pelykh@corphub.eu>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/server-uxproject on GitHub.You are welcome to contribute. To learn how please visithttps://odoo-community.org/page/Contribute.
Package: odoo13-addon-nsca-client
This is a technical module to send passive alerts to your favorite NSCA daemon
(Nagios, Shinken…).
This module is based on the Odoo cron system and requires a NSCA client
installed on the system to satisfy the/usr/sbin/send_nscacommand.Table of contentsInstallationConfigurationBug TrackerCreditsAuthorsContributorsMaintainersInstallationTo use this module, you need to install a NSCA client.On Debian/Ubuntu:$ sudo apt-get install nsca-clientConfigurationTo configure this module, you need to:Configure your server and a passive service in your monitoring tool
(e.g serviceOdoo Mail Queueon hostMY-SERVER).Declare your NSCA server in the menu Configuration / Technical / NSCA Client / ServersCreate NSCA checks in the menu Configuration / Technical / NSCA Client / ChecksCode the methods which will be called by the NSCA checks.Such methods must return a tuple(RC, MESSAGE, PERFORMANCE_DATA)whereRCis an integer,MESSAGEa unicode string ANDPERFOMANCE_DATAis a dictionary.RCvalues and the corresponding status are:0: OK1: WARNING2: CRITICAL3: UNKNOWNPERFORMANCE_DATAis not mandatory, so it could be possible to send(RC, MESSAGE).
Each element ofPERFORMANCE_DATAwill be a dictionary that could contain:value: value of the data (required)max: Max value on the chartmin: Minimum value on the chartwarn: Warning value on the chartcrit: Critical value on the chartuom: Unit of Measure on the chart (s - Seconds, % - Percentage, B - Bytes, c - Continuous)The key of the dictionary will be used as the performance_data label.E.g:classMailMail(models.Model):_inherit='mail.mail'@api.modeldefnsca_check_mails(self):mails=self.search([('state','=','exception')])ifmails:return(1,u"%smails not sent"%len(mails),{'exceptions':{'value':len(mails)}})return(0,u"OK",{'exceptions':{'value':len(mails)}})On the example, the performance data will use the labelexceptionsand the
value will be the number of exception of mails.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.CreditsAuthorsABF OSIELLContributorsSébastien Alix <sebastien.alix@osiell.com>Enric Tobella <etobella@creublanca.es>Jaime Arroyo <jaime.arroyo@creublanca.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/server-toolsproject on GitHub.You are welcome to contribute. To learn how please visithttps://odoo-community.org/page/Contribute.
Package: odoo13-addon-oca-custom
Custom module for OCA Instance.Table of contentsKnown issues / RoadmapBug TrackerCreditsAuthorsContributorsMaintainersKnown issues / RoadmapMake the github_login field from connector_github editable so it can be set
manually (eg when registering new CLA’s)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.CreditsAuthorsGRAPAkretionContributorsSylvain LE GAL (https://twitter.com/legalsylvain)Benoit GUILLOT (benoit.guillot@akretion.com)Stéphane Bidoul (stephane.bidoul@acsone.eu)Tecnativa:Vicent CubellsCristina Martin R.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/oca-customproject on GitHub.You are welcome to contribute. To learn how please visithttps://odoo-community.org/page/Contribute.
Package: odoo13-addon-oca-event-badge
This module allows to add specific tags for OCA partners.
These tags are printed on the badge attendee.Table of contentsUsageBug TrackerCreditsAuthorsContributorsOther creditsMaintainersUsageTo use this module, you need to create the tags in partner form (‘board’, ‘member’, ‘delegate’)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.CreditsAuthorsACSONE SA/NVContributorsGilles Meyomessegilles.meyomesse@acsone.eu(https://acsone.eu)TecnativaCristina Martin R.Manuel CaleroCarlos RocaOther creditsThe development of this module has been financially supported by:ACSONEThis module is maintained by:Odoo Community AssociationMaintainersThis 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/oca-customproject on GitHub.You are welcome to contribute. To learn how please visithttps://odoo-community.org/page/Contribute.
Package: odoo13-addon-oca-psc-team
The purpose of this module is to classify the projects according to PSC teams.Table of contentsUsageBug TrackerCreditsAuthorsContributorsMaintainersUsageGo to ‘Project’ menu > Configuration > ‘PSC Categories’ menu and create PSC categories.Go to ‘Project’ menu > Configuration > Projects and follow below steps:Go to ‘PSC Details’ tab and fill details.Upload image for your project.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.CreditsAuthorsSurekha TechnologiesContributorsSurekha Technologies (https://www.surekhatech.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/oca-customproject on GitHub.You are welcome to contribute. To learn how please visithttps://odoo-community.org/page/Contribute.
Package: odoo13-addon-odoo-web-login
This project aims to give to you the new Odoo Web Login ScreenContactBlog:www.xubi.meLinkedin:binhnguyenxuanSkype:xubi.uitEmail:kid.uit.1412@gmail.comInstallationInstallation process is at present stage only possible in manual way.
Then go to you odoo webinterface to the module section and start “Update module list”. Then look for the “Odoo Web Login Screen” in Apps (module list) and install.
I hope you enjoy checking out what all you can do with this application.PrerequisiteBefore installing the module make sure that the you have configured an addon path for custom addons. In a Linux system the parameter in the config file usually looks similar as the following example:
specify additional addons paths (separated by commas)
addons_path = /opt/odoo/odoo-server/addons, /opt/odoo/custom/addons
In this case you have to install the modules into /opt/odoo/custom/addons. At the present stage on dependency could not automatically resolved so you have to install one extra module that vertical community depends on.UsageMaybe images in github do not fit with the Odoo apps, so you can check:https://apps.odoo.com/apps/modules/13.0/odoo_web_login/for more details.
Thank you.New FeatureApply for module website (if installed).NoteRemmember that, installodoo_web_loginafterinstall modulewebsite. Or pleaseupgradeodoo_web_loginafter install modulewebsiteConfigurationDisable Manage DatabasesDisable FooterDefault Login ScreenChange Background by HoursNight (from 0h -> 3h and 18h -> 23h):Dawn (from 3h -> 7h):Day (from 7h -> 16h):Dusk (from 16h -> 18h):
Package: odoo13-addon-onchange-helper
This is a technical module. Its goal is to ease the play of onchange method directly called from Python code.Table of contentsUsageBug TrackerCreditsAuthorsContributorsMaintainersUsageTo use this module, you need to:depend on this modulecallyourmodel.play_onchanges(values, [‘field’])Example if you want to create a sale order and you want to get the values relative to partner_id field (as if you fill the field from UI)vals = {‘partner_id’: 1}vals = self.env[‘sale.order’].play_onchanges(vals, [‘partner_id’])Then,valswill be updated with partner_invoice_id, partner_shipping_id, pricelist_id, etc…Default values will be used to process onchange methods, if respective fields are not set invals.
You can get them if you pass fields name in the list of fields.vals = {‘partner_id’: 1}vals = self.env[‘sale.order’].play_onchanges(vals, [‘partner_id’, ‘date_order’])valswill contain, in addition to the changed values, the default value fordate_orderYou can also use it on existing record for example:vals = {‘partner_shipping_id’: 1}vals = sale.play_onchanges(vals, [‘partner_shipping_id’])Then the onchange will be played with the vals passed and the existing vals of the sale.valswill be updated with partner_invoice_id, pricelist_id, etc..Behind the scene,play_onchangeswill executeall the methodsregistered for the list of changed fields, so you do not have to call manually each onchange. To avoid performance issue when the method is called on a record, the record will be transformed into a memory record before calling the registered methods to avoid to trigger SQL updates command when values are assigned to the record by the onchangeNotes:Order in onchange_fields is very important as onchanges methods will be played in that order.If you use memory object invals, be award that onchange method in base model callself.invalidate_cache()that reset it.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.CreditsAuthorsAkretionCamptocampContributorsGuewen Baconnier <guewen.baconnier@camptocamp.com>Florian da Costa <florian.dacosta@akretion.com>Andrea Stirpe <a.stirpe@onestein.nl>Souheil Bejaoui <souheil.bejaoui@acsone.eu>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/server-toolsproject on GitHub.You are welcome to contribute. To learn how please visithttps://odoo-community.org/page/Contribute.