From a424fafcc04385da296808a2c7b4ed5e9c84adbf Mon Sep 17 00:00:00 2001 From: "Vir (Open ERP)" Date: Thu, 22 Jul 2010 15:48:06 +0530 Subject: [PATCH 01/13] [ADD] mrp : help added on menu items bzr revid: vir@tinyerp.com-20100722101806-fz3nmj6ctcpf1igq --- addons/mrp/mrp_view.xml | 6 ++++++ addons/mrp/report/mrp_production_order_view.xml | 3 +-- addons/mrp/report/mrp_report_view.xml | 2 ++ addons/mrp_operations/mrp_operations_view.xml | 2 ++ addons/procurement/procurement_view.xml | 4 +++- 5 files changed, 14 insertions(+), 3 deletions(-) diff --git a/addons/mrp/mrp_view.xml b/addons/mrp/mrp_view.xml index 9d645a17095..470f7c73a03 100644 --- a/addons/mrp/mrp_view.xml +++ b/addons/mrp/mrp_view.xml @@ -204,6 +204,7 @@ form + Work Centers are units of manufacture consisting of one or several people and/or machines that can be considered as a unit for the purposes of forecasting capacity and planning. @@ -398,6 +400,7 @@ form [('bom_id','=',False)] + Master Bills of Materials are documents that describe the list of raw materials used to make a finished product. You can generate documents for a product manufacturing (defining each manufacturing step) or you could define a single multi-level bill of materials. Bill of Material Components @@ -405,6 +408,7 @@ mrp.bom form [('bom_id','!=',False)] + Bills of materials Components are components and sub-product used to create master bills of materials. @@ -762,6 +766,7 @@ {'search_default_Current':1} + Manufacturing Orders describe the operations that need to be carried out and the raw materials usage for each stage of production. You use specifications (bills of materials) to work out the raw material requirements and the manufacturing orders needed for the finished products. Once the bills of materials have been defined, Open ERP becomes capable of automatically deciding on the manufacturing route depending on the needs of the company. @@ -772,6 +777,7 @@ form gantt,tree,form,calendar,graph [('state','in',('ready','confirmed','in_production'))] + Manufacturing Orders describe the operations that need to be carried out and the raw materials usage for each stage of production. You use specifications (bills of materials or BoM) to work out the raw material requirements and the manufacturing orders needed for the finished products. Once the bills of materials have been defined, Open ERP becomes capable of automatically deciding on the manufacturing route depending on the needs of the company. diff --git a/addons/mrp/report/mrp_production_order_view.xml b/addons/mrp/report/mrp_production_order_view.xml index 8172c61e84f..18dc07e4b78 100644 --- a/addons/mrp/report/mrp_production_order_view.xml +++ b/addons/mrp/report/mrp_production_order_view.xml @@ -109,8 +109,7 @@ tree,graph - {'search_default_Product': 1,'search_default_month':1,'group_by_no_leaf':1,'group_by':[]} - + {'search_default_Product': 1,'search_default_month':1,'group_by_no_leaf':1,'group_by':[]} diff --git a/addons/mrp/report/mrp_report_view.xml b/addons/mrp/report/mrp_report_view.xml index cf66f93f0e4..5f28f2ce6f4 100644 --- a/addons/mrp/report/mrp_report_view.xml +++ b/addons/mrp/report/mrp_report_view.xml @@ -49,6 +49,7 @@ report.workcenter.load form graph,tree + Work Center Load is a projection of load in a work center given a period. The load is express in hour and cycle (for machines). @@ -100,6 +101,7 @@ report.mrp.inout form graph,tree + Weekly Stock Value Variation enables you to track stock value evolution as a result of manufacturing activities (consumption of raw materials, production of finished goods, added accounting value of stock by the creation of value following the transformation of products). diff --git a/addons/mrp_operations/mrp_operations_view.xml b/addons/mrp_operations/mrp_operations_view.xml index 5c626b24814..bff88946ead 100644 --- a/addons/mrp_operations/mrp_operations_view.xml +++ b/addons/mrp_operations/mrp_operations_view.xml @@ -194,6 +194,7 @@ form tree,form,gantt,calendar,graph + Work Orders are manufacturing operations required to produce or assemble products. The different work orders will have different impacts on the costs of manufacture and planning depending on the available workload. @@ -203,6 +204,7 @@ form [('production_state','in',('ready','confirmed','in_production'))] tree,form,graph,calendar + To manufacture or assemble products, as well as using raw materials and finished product you must also handle manufacturing operations. Manufacturing operations are often called work orders. The different operations will have different impacts on the costs of manufacture and planning depending on the available workload. diff --git a/addons/procurement/procurement_view.xml b/addons/procurement/procurement_view.xml index fff13e36330..6d4a191807b 100644 --- a/addons/procurement/procurement_view.xml +++ b/addons/procurement/procurement_view.xml @@ -70,7 +70,7 @@ - + @@ -119,6 +119,7 @@ {'search_default_current':1} {'search_default_Current':1} + The procurement order will schedule a proposal for automatic procurement for the product concerned. This procurement will start a task, a purchase order form for the supplier or a production depending on the product configuration. @@ -139,6 +140,7 @@ form tree,form [('state','=','exception')] + For each customer order line or raw materials in a manufacturing order, there is a procurement form . In normal system use, procurement orders are automatically generated by Open ERP. But if there are configuration problems, the system can remain blocked by a procurement without generating a corresponding document. It is a procurement exception. Some problems are link to timing and will be correct automatically by the system. If there is no procurement rule, the exception must be corrected manually. From 6e93201b13e80c45c55e67b821f4288155ae8be8 Mon Sep 17 00:00:00 2001 From: "rpa (Open ERP)" Date: Thu, 22 Jul 2010 16:30:56 +0530 Subject: [PATCH 02/13] [IMP]: crm, crm_claim, crm_fundraising, crm_helpdesk: Improvement for log messages bzr revid: rpa@tinyerp.com-20100722110056-udb2qy6gtwbr5whe --- addons/crm/crm.py | 7 +++++++ addons/crm/crm_lead.py | 6 +++--- addons/crm/crm_meeting.py | 16 +++++++++++++++- addons/crm/crm_opportunity.py | 10 +++++----- addons/crm_claim/crm_claim.py | 2 +- addons/crm_fundraising/crm_fundraising.py | 2 +- addons/crm_helpdesk/crm_helpdesk.py | 2 +- 7 files changed, 33 insertions(+), 12 deletions(-) diff --git a/addons/crm/crm.py b/addons/crm/crm.py index 4b1aad7cce9..478cd7b2986 100644 --- a/addons/crm/crm.py +++ b/addons/crm/crm.py @@ -301,6 +301,13 @@ class crm_case(object): self.write(cr, uid, ids, {'state': 'cancel', 'active': True}) self._action(cr, uid, cases, 'cancel') + for case in cases: + message = "The " + self._description + " '" + case.name + "' has been Cancelled." + #TODO: Need to differentiate lead and opportunity +# if hasattr(case, 'type'): +# #TO CHECK: hasattr gives warning for other crm objects that don't have field 'type' +# message = "The " + (case.type or 'Case').title() + " '" + case.name + "' has been Cancelled." + self.log(cr, uid, case.id, message) return True def case_pending(self, cr, uid, ids, *args): diff --git a/addons/crm/crm_lead.py b/addons/crm/crm_lead.py index 2a469d88baa..9cb5f31d67e 100644 --- a/addons/crm/crm_lead.py +++ b/addons/crm/crm_lead.py @@ -198,8 +198,8 @@ class crm_lead(osv.osv, crm_case): self.write(cr, uid, ids, value) for (id, name) in self.name_get(cr, uid, ids): - type = self.browse(cr, uid, id).type - message = (_('The ') + type.title() or 'Lead') + " '" + name + "' "+ _("has been written as Open.") + type = self.browse(cr, uid, id).type or 'Lead' + message = (_('The ') + type.title()) + " '" + name + "' "+ _("has been Opened.") self.log(cr, uid, id, message) return res @@ -216,7 +216,7 @@ class crm_lead(osv.osv, crm_case): for (id, name) in self.name_get(cr, uid, ids): lead = self.browse(cr, uid, id) if lead.type == 'lead': - message = _('The Lead') + " '" + name + "' "+ _("has been written as Closed.") + message = _('The Lead') + " '" + name + "' "+ _("has been Closed.") self.log(cr, uid, id, message) return res diff --git a/addons/crm/crm_meeting.py b/addons/crm/crm_meeting.py index 79a2c992cdf..798f746f9e3 100644 --- a/addons/crm/crm_meeting.py +++ b/addons/crm/crm_meeting.py @@ -122,7 +122,21 @@ class crm_meeting(osv.osv, crm_case): } return value - + + def case_open(self, cr, uid, ids, *args): + """Confirms meeting + @param self: The object pointer + @param cr: the current row, from the database cursor, + @param uid: the current user’s ID for security checks, + @param ids: List of Meeting Ids + @param *args: Tuple Value for additional Params + """ + res = super(crm_meeting, self).case_open(cr, uid, ids, args) + for (id, name) in self.name_get(cr, uid, ids): + message = _('The Meeting') + " '" + name + "' "+ _("has been Confirmed.") + self.log(cr, uid, id, message) + return res + crm_meeting() class calendar_attendee(osv.osv): diff --git a/addons/crm/crm_opportunity.py b/addons/crm/crm_opportunity.py index a1ca912e20f..c058732a3dd 100644 --- a/addons/crm/crm_opportunity.py +++ b/addons/crm/crm_opportunity.py @@ -36,8 +36,6 @@ AVAILABLE_STATES = [ class crm_opportunity(osv.osv): """ Opportunity Cases """ - _name = "crm.lead" - _description = "Opportunity" _order = "priority,date_action,id desc" _inherit = 'crm.lead' _columns = { @@ -72,8 +70,10 @@ class crm_opportunity(osv.osv): self.write(cr, uid, ids, value) for (id, name) in self.name_get(cr, uid, ids): - message = _('The Opportunity') + " '" + name + "' "+ _("has been written as Won.") - self.log(cr, uid, id, message) + opp = self.browse(cr, uid, id) + if opp.type == 'opportunity': + message = _('The Opportunity') + " '" + name + "' "+ _("has been Won.") + self.log(cr, uid, id, message) return res def case_mark_lost(self, cr, uid, ids, *args): @@ -95,7 +95,7 @@ class crm_opportunity(osv.osv): for (id, name) in self.name_get(cr, uid, ids): opp = self.browse(cr, uid, id) if opp.type == 'opportunity': - message = _('The Opportunity') + " '" + name + "' "+ _("has been written as Lost.") + message = _('The Opportunity') + " '" + name + "' "+ _("has been Lost.") self.log(cr, uid, id, message) return res diff --git a/addons/crm_claim/crm_claim.py b/addons/crm_claim/crm_claim.py index b453ebfc4aa..76a6073b58c 100644 --- a/addons/crm_claim/crm_claim.py +++ b/addons/crm_claim/crm_claim.py @@ -28,7 +28,7 @@ class crm_claim(osv.osv, crm.crm_case): Crm claim """ _name = "crm.claim" - _description = "Claim Cases" + _description = "Claim" _order = "id desc" _inherit = ['mailgate.thread'] _columns = { diff --git a/addons/crm_fundraising/crm_fundraising.py b/addons/crm_fundraising/crm_fundraising.py index 99b8fc06dae..81e16a47ac3 100644 --- a/addons/crm_fundraising/crm_fundraising.py +++ b/addons/crm_fundraising/crm_fundraising.py @@ -26,7 +26,7 @@ class crm_fundraising(osv.osv, crm.crm_case): """ Fund Raising Cases """ _name = "crm.fundraising" - _description = "Fund Raising Cases" + _description = "Fund Raising" _order = "id desc" _inherit = ['mailgate.thread'] _columns = { diff --git a/addons/crm_helpdesk/crm_helpdesk.py b/addons/crm_helpdesk/crm_helpdesk.py index 2894a429865..d4a1e9d59fc 100644 --- a/addons/crm_helpdesk/crm_helpdesk.py +++ b/addons/crm_helpdesk/crm_helpdesk.py @@ -27,7 +27,7 @@ class crm_helpdesk(osv.osv, crm.crm_case): """ Helpdesk Cases """ _name = "crm.helpdesk" - _description = "Helpdesk Cases" + _description = "Helpdesk" _order = "id desc" _inherit = ['mailgate.thread'] _columns = { From 0ffd63135c87f76c866aaaaf04a2c365fedba9a9 Mon Sep 17 00:00:00 2001 From: Mantavya Gajjar Date: Thu, 22 Jul 2010 17:43:42 +0530 Subject: [PATCH 03/13] [FIX]: improvement in hr_payroll and account recurring wizard bzr revid: mga@tinyerp.com-20100722121342-4kx7jv06zonmv5g2 --- .../account/wizard/account_use_model_view.xml | 3 ++- addons/hr_payroll/__init__.py | 3 +-- addons/hr_payroll/__openerp__.py | 8 +++---- addons/hr_payroll/hr_payroll.py | 21 ------------------- addons/hr_payroll/hr_payroll_wizard.xml | 11 ---------- 5 files changed, 6 insertions(+), 40 deletions(-) diff --git a/addons/account/wizard/account_use_model_view.xml b/addons/account/wizard/account_use_model_view.xml index 71f026237ac..560030be2f5 100644 --- a/addons/account/wizard/account_use_model_view.xml +++ b/addons/account/wizard/account_use_model_view.xml @@ -10,7 +10,8 @@
- +