diff --git a/addons/account/account.py b/addons/account/account.py
index a724ebc3cc7..5f20c858cf8 100644
--- a/addons/account/account.py
+++ b/addons/account/account.py
@@ -705,7 +705,7 @@ class account_journal(osv.osv):
'with_last_closing_balance' : fields.boolean('Opening With Last Closing Balance'),
'name': fields.char('Journal Name', size=64, required=True),
'code': fields.char('Code', size=5, required=True, help="The code will be displayed on reports."),
- 'type': fields.selection([('sale', 'Sale'),('sale_refund','Sale Refund'), ('purchase', 'Purchase'), ('purchase_refund','Purchase Refund'), ('cash', 'Cash'), ('bank', 'Bank and Cheques'), ('general', 'General'), ('situation', 'Opening/Closing Situation')], 'Type', size=32, required=True,
+ 'type': fields.selection([('sale', 'Sale'),('sale_refund','Sale Refund'), ('purchase', 'Purchase'), ('purchase_refund','Purchase Refund'), ('cash', 'Cash'), ('bank', 'Bank and Checks'), ('general', 'General'), ('situation', 'Opening/Closing Situation')], 'Type', size=32, required=True,
help="Select 'Sale' for customer invoices journals."\
" Select 'Purchase' for supplier invoices journals."\
" Select 'Cash' or 'Bank' for journals that are used in customer or supplier payments."\
@@ -715,7 +715,7 @@ class account_journal(osv.osv):
'account_control_ids': fields.many2many('account.account', 'account_account_type_rel', 'journal_id','account_id', 'Account', domain=[('type','<>','view'), ('type', '<>', 'closed')]),
'default_credit_account_id': fields.many2one('account.account', 'Default Credit Account', domain="[('type','!=','view')]", help="It acts as a default account for credit amount"),
'default_debit_account_id': fields.many2one('account.account', 'Default Debit Account', domain="[('type','!=','view')]", help="It acts as a default account for debit amount"),
- 'centralisation': fields.boolean('Centralised Counterpart', help="Check this box to determine that each entry of this journal won't create a new counterpart but will share the same counterpart. This is used in fiscal year closing."),
+ 'centralisation': fields.boolean('Centralized Counterpart', help="Check this box to determine that each entry of this journal won't create a new counterpart but will share the same counterpart. This is used in fiscal year closing."),
'update_posted': fields.boolean('Allow Cancelling Entries', help="Check this box if you want to allow the cancellation the entries related to this journal or of the invoice related to this journal"),
'group_invoice_lines': fields.boolean('Group Invoice Lines', help="If this box is checked, the system will try to group the accounting lines when generating them from invoices."),
'sequence_id': fields.many2one('ir.sequence', 'Entry Sequence', help="This field contains the information related to the numbering of the journal entries of this journal.", required=True),
diff --git a/addons/account/account_bank_statement.py b/addons/account/account_bank_statement.py
index d1e25029f4f..8e1a5dd26c6 100644
--- a/addons/account/account_bank_statement.py
+++ b/addons/account/account_bank_statement.py
@@ -547,7 +547,7 @@ class account_bank_statement_line(osv.osv):
_name = "account.bank.statement.line"
_description = "Bank Statement Line"
_columns = {
- 'name': fields.char('Communication', required=True),
+ 'name': fields.char('OBI', required=True, help="Originator to Beneficiary Information"),
'date': fields.date('Date', required=True),
'amount': fields.float('Amount', digits_compute=dp.get_precision('Account')),
'type': fields.selection([
diff --git a/addons/account/account_invoice.py b/addons/account/account_invoice.py
index 7843a096940..c9cf90789cb 100644
--- a/addons/account/account_invoice.py
+++ b/addons/account/account_invoice.py
@@ -229,7 +229,7 @@ class account_invoice(osv.osv):
help="If you use payment terms, the due date will be computed automatically at the generation "\
"of accounting entries. The payment term may compute several due dates, for example 50% now and 50% in one month, but if you want to force a due date, make sure that the payment term is not set on the invoice. If you keep the payment term and the due date empty, it means direct payment."),
'partner_id': fields.many2one('res.partner', 'Partner', change_default=True, readonly=True, required=True, states={'draft':[('readonly',False)]}, track_visibility='always'),
- 'payment_term': fields.many2one('account.payment.term', 'Payment Term',readonly=True, states={'draft':[('readonly',False)]},
+ 'payment_term': fields.many2one('account.payment.term', 'Payment Terms',readonly=True, states={'draft':[('readonly',False)]},
help="If you use payment terms, the due date will be computed automatically at the generation "\
"of accounting entries. If you keep the payment term and the due date empty, it means direct payment. "\
"The payment term may compute several due dates, for example 50% now, 50% in one month."),
@@ -240,7 +240,7 @@ class account_invoice(osv.osv):
'tax_line': fields.one2many('account.invoice.tax', 'invoice_id', 'Tax Lines', readonly=True, states={'draft':[('readonly',False)]}),
'move_id': fields.many2one('account.move', 'Journal Entry', readonly=True, select=1, ondelete='restrict', help="Link to the automatically generated Journal Items."),
- 'amount_untaxed': fields.function(_amount_all, digits_compute=dp.get_precision('Account'), string='Untaxed', track_visibility='always',
+ 'amount_untaxed': fields.function(_amount_all, digits_compute=dp.get_precision('Account'), string='Subtotal', track_visibility='always',
store={
'account.invoice': (lambda self, cr, uid, ids, c={}: ids, ['invoice_line'], 20),
'account.invoice.tax': (_get_invoice_tax, None, 20),
@@ -1380,7 +1380,7 @@ class account_invoice_line(osv.osv):
'product_id': fields.many2one('product.product', 'Product', ondelete='set null', select=True),
'account_id': fields.many2one('account.account', 'Account', required=True, domain=[('type','<>','view'), ('type', '<>', 'closed')], help="The income or expense account related to the selected product."),
'price_unit': fields.float('Unit Price', required=True, digits_compute= dp.get_precision('Product Price')),
- 'price_subtotal': fields.function(_amount_line, string='Subtotal', type="float",
+ 'price_subtotal': fields.function(_amount_line, string='Amount', type="float",
digits_compute= dp.get_precision('Account'), store=True),
'quantity': fields.float('Quantity', digits_compute= dp.get_precision('Product Unit of Measure'), required=True),
'discount': fields.float('Discount (%)', digits_compute= dp.get_precision('Discount')),
diff --git a/addons/account/account_menuitem.xml b/addons/account/account_menuitem.xml
index d868043db64..f7bf33476bf 100644
--- a/addons/account/account_menuitem.xml
+++ b/addons/account/account_menuitem.xml
@@ -12,7 +12,7 @@
-
+
diff --git a/addons/account_analytic_analysis/account_analytic_analysis.py b/addons/account_analytic_analysis/account_analytic_analysis.py
index b6cbd1a459c..23d8faaffce 100644
--- a/addons/account_analytic_analysis/account_analytic_analysis.py
+++ b/addons/account_analytic_analysis/account_analytic_analysis.py
@@ -459,7 +459,7 @@ class account_analytic_account(osv.osv):
context = {}
sale_ids = self.pool.get('sale.order').search(cr,uid,[('project_id','=',context.get('search_default_project_id',False)),('partner_id','in',context.get('search_default_partner_id',False))])
names = [record.name for record in self.browse(cr, uid, ids, context=context)]
- name = _('Sale Order Lines of %s') % ','.join(names)
+ name = _('Sales Order Lines of %s') % ','.join(names)
return {
'type': 'ir.actions.act_window',
'name': name,
diff --git a/addons/account_analytic_analysis/account_analytic_analysis_view.xml b/addons/account_analytic_analysis/account_analytic_analysis_view.xml
index eaadbe0fa83..61c18abdae6 100644
--- a/addons/account_analytic_analysis/account_analytic_analysis_view.xml
+++ b/addons/account_analytic_analysis/account_analytic_analysis_view.xml
@@ -168,7 +168,7 @@
- Template of Contract
+ Contract Templateir.actions.act_windowaccount.analytic.accountform
diff --git a/addons/account_analytic_default/account_analytic_default.py b/addons/account_analytic_default/account_analytic_default.py
index 0fe3e9f2c14..9d7df0aa010 100644
--- a/addons/account_analytic_default/account_analytic_default.py
+++ b/addons/account_analytic_default/account_analytic_default.py
@@ -31,10 +31,10 @@ class account_analytic_default(osv.osv):
_columns = {
'sequence': fields.integer('Sequence', help="Gives the sequence order when displaying a list of analytic distribution"),
'analytic_id': fields.many2one('account.analytic.account', 'Analytic Account'),
- 'product_id': fields.many2one('product.product', 'Product', ondelete='cascade', help="Select a product which will use analytic account specified in analytic default (e.g. create new customer invoice or Sale order if we select this product, it will automatically take this as an analytic account)"),
- 'partner_id': fields.many2one('res.partner', 'Partner', ondelete='cascade', help="Select a partner which will use analytic account specified in analytic default (e.g. create new customer invoice or Sale order if we select this partner, it will automatically take this as an analytic account)"),
+ 'product_id': fields.many2one('product.product', 'Product', ondelete='cascade', help="Select a product which will use analytic account specified in analytic default (e.g. create new customer invoice or Sales order if we select this product, it will automatically take this as an analytic account)"),
+ 'partner_id': fields.many2one('res.partner', 'Partner', ondelete='cascade', help="Select a partner which will use analytic account specified in analytic default (e.g. create new customer invoice or Sales order if we select this partner, it will automatically take this as an analytic account)"),
'user_id': fields.many2one('res.users', 'User', ondelete='cascade', help="Select a user which will use analytic account specified in analytic default."),
- 'company_id': fields.many2one('res.company', 'Company', ondelete='cascade', help="Select a company which will use analytic account specified in analytic default (e.g. create new customer invoice or Sale order if we select this company, it will automatically take this as an analytic account)"),
+ 'company_id': fields.many2one('res.company', 'Company', ondelete='cascade', help="Select a company which will use analytic account specified in analytic default (e.g. create new customer invoice or Sales order if we select this company, it will automatically take this as an analytic account)"),
'date_start': fields.date('Start Date', help="Default start date for this Analytic Account."),
'date_stop': fields.date('End Date', help="Default end date for this Analytic Account."),
}
diff --git a/addons/account_bank_statement_extensions/account_bank_statement.py b/addons/account_bank_statement_extensions/account_bank_statement.py
index ee2988bab6f..60dcc6dfa25 100644
--- a/addons/account_bank_statement_extensions/account_bank_statement.py
+++ b/addons/account_bank_statement_extensions/account_bank_statement.py
@@ -63,7 +63,7 @@ class account_bank_statement_line_global(osv.osv):
_description = 'Batch Payment Info'
_columns = {
- 'name': fields.char('Communication', size=128, required=True),
+ 'name': fields.char('OBI', size=128, required=True, help="Originator to Beneficiary Information"),
'code': fields.char('Code', size=64, required=True),
'parent_id': fields.many2one('account.bank.statement.line.global', 'Parent Code', ondelete='cascade'),
'child_ids': fields.one2many('account.bank.statement.line.global', 'parent_id', 'Child Codes'),
diff --git a/addons/account_check_writing/account.py b/addons/account_check_writing/account.py
index 1600898fc3a..62b7336dc5f 100644
--- a/addons/account_check_writing/account.py
+++ b/addons/account_check_writing/account.py
@@ -38,7 +38,7 @@ class res_company(osv.osv):
('top', 'Check on Top'),
('middle', 'Check in middle'),
('bottom', 'Check on bottom'),
- ],"Choose Check layout",
+ ],"Check Layout",
help="Check on top is compatible with Quicken, QuickBooks and Microsoft Money. Check in middle is compatible with Peachtree, ACCPAC and DacEasy. Check on bottom is compatible with Peachtree, ACCPAC and DacEasy only" ),
}
diff --git a/addons/account_voucher/report/account_voucher_sales_receipt_view.xml b/addons/account_voucher/report/account_voucher_sales_receipt_view.xml
index fbd40ee17ba..e2be4939be8 100644
--- a/addons/account_voucher/report/account_voucher_sales_receipt_view.xml
+++ b/addons/account_voucher/report/account_voucher_sales_receipt_view.xml
@@ -6,7 +6,7 @@
sale.receipt.report.treesale.receipt.report
-
+
@@ -33,7 +33,7 @@
sale.receipt.report.graphsale.receipt.report
-
+
@@ -44,7 +44,7 @@
sale.receipt.report.searchsale.receipt.report
-
+
@@ -74,7 +74,7 @@
- Sales Receipt Analysis
+ Sales Receipts Analysissale.receipt.reportformtree,graph
diff --git a/addons/account_voucher/voucher_payment_receipt_view.xml b/addons/account_voucher/voucher_payment_receipt_view.xml
index e4da7b673d3..5a204d605d6 100644
--- a/addons/account_voucher/voucher_payment_receipt_view.xml
+++ b/addons/account_voucher/voucher_payment_receipt_view.xml
@@ -250,7 +250,7 @@
- Supplier Payment
+ Supplier Paymentsaccount.voucherform[('journal_id.type', 'in', ['bank', 'cash']), ('type','=','payment')]
@@ -262,8 +262,7 @@
Click to create a new supplier payment.
- OpenERP helps you easily track payments you do and remining
- balance to pay to your supplier.
+ OpenERP helps you easily track payments you make and the remaining balances you need to pay your suppliers.
If you want to import sales order having several
order lines; for each order line, you need to reserve
diff --git a/addons/crm/crm_data.xml b/addons/crm/crm_data.xml
index 282622d2ad2..3726c744b2e 100644
--- a/addons/crm/crm_data.xml
+++ b/addons/crm/crm_data.xml
@@ -39,7 +39,7 @@
- Cheque
+ Check
diff --git a/addons/delivery/delivery_view.xml b/addons/delivery/delivery_view.xml
index ff19659a830..1ad729d9c09 100644
--- a/addons/delivery/delivery_view.xml
+++ b/addons/delivery/delivery_view.xml
@@ -104,7 +104,7 @@
to each method.
These methods allows to automaticaly compute the delivery price
- according to your settings; on the sale order (based on the
+ according to your settings; on the sales order (based on the
quotation) or the invoice (based on the delivery orders).
diff --git a/addons/event/event.py b/addons/event/event.py
index 5d010bf0760..9e50128c592 100644
--- a/addons/event/event.py
+++ b/addons/event/event.py
@@ -292,7 +292,7 @@ class event_registration(osv.osv):
_inherit = ['mail.thread', 'ir.needaction_mixin']
_columns = {
'id': fields.integer('ID'),
- 'origin': fields.char('Source Document', size=124,readonly=True,help="Name of the sale order which create the registration"),
+ 'origin': fields.char('Source Document', size=124,readonly=True,help="Reference of the sales order which created the registration"),
'nb_register': fields.integer('Number of Participants', required=True, readonly=True, states={'draft': [('readonly', False)]}),
'event_id': fields.many2one('event.event', 'Event', required=True, readonly=True, states={'draft': [('readonly', False)]}),
'partner_id': fields.many2one('res.partner', 'Partner', states={'done': [('readonly', True)]}),
diff --git a/addons/event_sale/__openerp__.py b/addons/event_sale/__openerp__.py
index 2f191bad062..c274669af98 100644
--- a/addons/event_sale/__openerp__.py
+++ b/addons/event_sale/__openerp__.py
@@ -28,7 +28,7 @@
Creating registration with sale orders.
=======================================
-This module allows you to automatize and connect your registration creation with
+This module allows you to automate and connect your registration creation with
your main sale flow and therefore, to enable the invoicing feature of registrations.
It defines a new kind of service products that offers you the possibility to
diff --git a/addons/event_sale/event_sale.py b/addons/event_sale/event_sale.py
index 66dcbc78f13..4f32620e667 100644
--- a/addons/event_sale/event_sale.py
+++ b/addons/event_sale/event_sale.py
@@ -25,8 +25,8 @@ from openerp.tools.translate import _
class product(osv.osv):
_inherit = 'product.product'
_columns = {
- 'event_ok': fields.boolean('Event Subscription', help='Determine if a product needs to create automatically an event registration at the confirmation of a sale order line.'),
- 'event_type_id': fields.many2one('event.type', 'Type of Event', help='Select event types so when we use this product in Sale order line, it will filter events of this type only.'),
+ 'event_ok': fields.boolean('Event Subscription', help='Determine if a product needs to create automatically an event registration at the confirmation of a sales order line.'),
+ 'event_type_id': fields.many2one('event.type', 'Type of Event', help='Select event types so when we use this product in sales order lines, it will filter events of this type only.'),
}
def onchange_event_ok(self, cr, uid, ids, event_ok, context=None):
@@ -69,7 +69,7 @@ class sale_order_line(osv.osv):
def button_confirm(self, cr, uid, ids, context=None):
'''
- create registration with sale order
+ create registration with sales order
'''
registration_obj = self.pool.get('event.registration')
sale_obj = self.pool.get('sale.order')
@@ -85,6 +85,6 @@ class sale_order_line(osv.osv):
'event_id': order_line.event_id.id,
}
registration_id = registration_obj.create(cr, uid, dic, context=context)
- message = _("The registration %s has been created from the Sale Order %s.") % (registration_id, order_line.order_id.name)
+ message = _("The registration %s has been created from the Sales Order %s.") % (registration_id, order_line.order_id.name)
registration_obj.message_post(cr, uid, [registration_id], body=message, context=context)
return super(sale_order_line, self).button_confirm(cr, uid, ids, context=context)
diff --git a/addons/fleet/fleet.py b/addons/fleet/fleet.py
index 7474455d6d8..83f96bd71b5 100644
--- a/addons/fleet/fleet.py
+++ b/addons/fleet/fleet.py
@@ -124,7 +124,7 @@ class fleet_vehicle_state(osv.Model):
_order = 'sequence asc'
_columns = {
'name': fields.char('Name', required=True),
- 'sequence': fields.integer('Order', help="Used to order the note stages")
+ 'sequence': fields.integer('Sequence', help="Used to order the note stages")
}
_sql_constraints = [('fleet_state_name_unique','unique(name)', 'State name already exists')]
diff --git a/addons/hr_evaluation/hr_evaluation_view.xml b/addons/hr_evaluation/hr_evaluation_view.xml
index 82ef2aa83f4..54baee5f538 100644
--- a/addons/hr_evaluation/hr_evaluation_view.xml
+++ b/addons/hr_evaluation/hr_evaluation_view.xml
@@ -379,7 +379,7 @@
- Click to create a new interview request related to a personnal evaluation.
+ Click to create a new interview request related to a personal evaluation.
Interview requests are usually generated automatically by
OpenERP according to an employee's appraisal plan. Each user
diff --git a/addons/hr_expense/hr_expense_view.xml b/addons/hr_expense/hr_expense_view.xml
index 2c206589ac2..0324388786f 100644
--- a/addons/hr_expense/hr_expense_view.xml
+++ b/addons/hr_expense/hr_expense_view.xml
@@ -212,7 +212,7 @@
-
+
diff --git a/addons/hr_timesheet_invoice/hr_timesheet_invoice.py b/addons/hr_timesheet_invoice/hr_timesheet_invoice.py
index 53a6bbbc26b..1cb5c57e67e 100644
--- a/addons/hr_timesheet_invoice/hr_timesheet_invoice.py
+++ b/addons/hr_timesheet_invoice/hr_timesheet_invoice.py
@@ -72,7 +72,7 @@ class account_analytic_account(osv.osv):
'amount_invoiced': fields.function(_invoiced_calc, string='Invoiced Amount',
help="Total invoiced"),
'to_invoice': fields.many2one('hr_timesheet_invoice.factor', 'Timesheet Invoicing Ratio',
- help="You usually invoice 100% of the timesheets. But if you mix fixed price and timesheet invoicing, you may use another ratio. For instance, if you do a 20% advance invoice (fixed price, based on a sale order), you should invoice the rest on timesheet with a 80% ratio."),
+ help="You usually invoice 100% of the timesheets. But if you mix fixed price and timesheet invoicing, you may use another ratio. For instance, if you do a 20% advance invoice (fixed price, based on a sales order), you should invoice the rest on timesheet with a 80% ratio."),
}
_defaults = {
'pricelist_id': lambda self, cr, uid, ctx: ctx.get('pricelist_id', False),
diff --git a/addons/lunch/lunch_view.xml b/addons/lunch/lunch_view.xml
index b8e30cf356e..8974099a294 100644
--- a/addons/lunch/lunch_view.xml
+++ b/addons/lunch/lunch_view.xml
@@ -203,7 +203,7 @@
-
+
diff --git a/addons/mail/data/mail_group_data.xml b/addons/mail/data/mail_group_data.xml
index 84258d619ba..d61c883f447 100644
--- a/addons/mail/data/mail_group_data.xml
+++ b/addons/mail/data/mail_group_data.xml
@@ -16,7 +16,7 @@
Welcome to OpenERP!Your homepage is a summary of messages you received and key information about documents you follow.
-
The top menu bar contains all applications you installed. You can use the Settings menu to install more applications, activate others features or give access to new users.
+
The top menu bar contains all applications you installed. You can use the Settings menu to install more applications, activate other features or give access to new users.
To setup your preferences (name, email signature, avatar), click on the top right corner.
diff --git a/addons/mrp/mrp_view.xml b/addons/mrp/mrp_view.xml
index d5bc6d94507..00e8369e6b7 100644
--- a/addons/mrp/mrp_view.xml
+++ b/addons/mrp/mrp_view.xml
@@ -47,11 +47,11 @@
Define specific property groups that can be assigned to your
bill of materials and sales orders. Properties allows OpenERP
to automatically select the right bill of materials according
- to properties selected in the sale order by salesperson.
+ to properties selected in the sales order by salesperson.
For instance, in the property group "Warranty", you an have
two properties: 1 year warranty, 3 years warranty. Depending
- on the propoerties selected in the sale order, OpenERP will
+ on the propoerties selected in the sales order, OpenERP will
schedule a production using the matching bill of materials.
@@ -121,7 +121,7 @@
materials for manufacturing a product when you have different
ways of building the same product. You can assign several
properties to each bill of materials. When a salesperson
- creates a sale order, they can relate it to several properties
+ creates a sales order, they can relate it to several properties
and OpenERP will automatically select the BoM to use according
the needs.
@@ -370,7 +370,7 @@
- When processing a sale order for this product, the delivery order
+ When processing a sales order for this product, the delivery order
will contain the raw materials, instead of the finished product.
@@ -1031,7 +1031,7 @@
diff --git a/addons/mrp/res_config.py b/addons/mrp/res_config.py
index 52c56acf3d7..c780576099c 100644
--- a/addons/mrp/res_config.py
+++ b/addons/mrp/res_config.py
@@ -63,7 +63,7 @@ class mrp_config_settings(osv.osv_memory):
that will define the required raw materials."""),
'group_mrp_properties': fields.boolean("Allow several bill of materials per products using properties",
implied_group='product.group_mrp_properties',
- help="""The selection of the right Bill of Material to use will depend on the properties specified on the sale order and the Bill of Material."""),
+ help="""The selection of the right Bill of Material to use will depend on the properties specified on the sales order and the Bill of Material."""),
'module_product_manufacturer': fields.boolean("Define manufacturers on products ",
help="""This allows you to define the following for a product:
* Manufacturer
diff --git a/addons/portal/acquirer_view.xml b/addons/portal/acquirer_view.xml
index a415a431ad2..53e0591009e 100644
--- a/addons/portal/acquirer_view.xml
+++ b/addons/portal/acquirer_view.xml
@@ -21,7 +21,7 @@
kind: the kind of document on which the payment form is rendered (translated to user language, e.g. "Invoice")
currency: the currency record in which the document is issued (e.g. currency.name could be EUR)
amount: the total amount to pay, as a float
-
object: the document on which the payment form is rendered (usually an invoice or sale order record)
+
object: the document on which the payment form is rendered (usually an invoice or sales order record)
quote(): a method to quote special string character to make them suitable for inclusion in a URL
cr: the current database cursor
uid: the current user id
diff --git a/addons/portal/portal_data.xml b/addons/portal/portal_data.xml
index 3cfe808aff3..ac36bbde15e 100644
--- a/addons/portal/portal_data.xml
+++ b/addons/portal/portal_data.xml
@@ -14,7 +14,7 @@
- Company's news
+ Company Newspublic
@@ -46,7 +46,7 @@
- Company's jobs
+ Company Jobspublic
diff --git a/addons/portal_sale/portal_sale_data.xml b/addons/portal_sale/portal_sale_data.xml
index 0ef9b1ec5cc..31a2f19ef28 100644
--- a/addons/portal_sale/portal_sale_data.xml
+++ b/addons/portal_sale/portal_sale_data.xml
@@ -5,7 +5,7 @@
- Sale Order - Send by Email (Portal)
+ Sales Order - Send by Email (Portal)${object.user_id.email or ''}${object.company_id.name} ${object.state in ('draft', 'sent') and 'Quotation' or 'Order'} (Ref ${object.name or 'n/a' })${object.partner_invoice_id.id}
@@ -180,4 +180,4 @@
-
\ No newline at end of file
+
diff --git a/addons/portal_sale/portal_sale_view.xml b/addons/portal_sale/portal_sale_view.xml
index 0a10c80e3ef..3e2fc18d877 100644
--- a/addons/portal_sale/portal_sale_view.xml
+++ b/addons/portal_sale/portal_sale_view.xml
@@ -46,7 +46,7 @@
tree,form{"search_default_sales":1}
- We haven't sent you any sale order.
+ We haven't sent you any sales order.
diff --git a/addons/process/process_demo.xml b/addons/process/process_demo.xml
index e0333feeefa..c1c4b5536c1 100644
--- a/addons/process/process_demo.xml
+++ b/addons/process/process_demo.xml
@@ -13,8 +13,8 @@
Quotation
- Quotations are sale orders in draft mode
-
+ Quotations are sales orders in draft mode
+ stateobject.state == 'draft'
@@ -22,9 +22,9 @@
- Sale Order
+ Sales OrderManages the delivery in invoicing process
-
+ stateobject.state == 'manual'
@@ -33,7 +33,7 @@
Invoice
- In case you invoiced on Sale Order
+ In case you invoiced on Sales Orderstate
@@ -85,14 +85,14 @@
Invoice on order
-
+ object.order_policy != 'picking'Invoice on delivery
-
+ object.order_policy == 'picking'
diff --git a/addons/project_long_term/project_long_term_view.xml b/addons/project_long_term/project_long_term_view.xml
index 18e471ddd40..e8e21caab0a 100644
--- a/addons/project_long_term/project_long_term_view.xml
+++ b/addons/project_long_term/project_long_term_view.xml
@@ -60,7 +60,7 @@
project.user.allocation.searchproject.user.allocation
-
+
@@ -73,7 +73,7 @@
- Planning of Users
+ Team Planningproject.user.allocationformgantt,tree,form,calendar
@@ -171,7 +171,7 @@
-
+
diff --git a/addons/project_mrp/process/project_mrp_process.xml b/addons/project_mrp/process/project_mrp_process.xml
index 729f107b755..e2195c6f61b 100644
--- a/addons/project_mrp/process/project_mrp_process.xml
+++ b/addons/project_mrp/process/project_mrp_process.xml
@@ -22,8 +22,8 @@
-
-
+
+
diff --git a/addons/project_mrp/project_mrp.py b/addons/project_mrp/project_mrp.py
index d42cf1e7565..a6f0495a962 100644
--- a/addons/project_mrp/project_mrp.py
+++ b/addons/project_mrp/project_mrp.py
@@ -27,7 +27,7 @@ class project_task(osv.osv):
_inherit = "project.task"
_columns = {
'procurement_id': fields.many2one('procurement.order', 'Procurement', ondelete='set null'),
- 'sale_line_id': fields.related('procurement_id', 'sale_line_id', type='many2one', relation='sale.order.line', store=True, string='Sale Order Line'),
+ 'sale_line_id': fields.related('procurement_id', 'sale_line_id', type='many2one', relation='sale.order.line', store=True, string='Sales Order Line'),
}
def _validate_subflows(self, cr, uid, ids):
diff --git a/addons/project_mrp/project_mrp_view.xml b/addons/project_mrp/project_mrp_view.xml
index be6bae8ca61..881ed9b6b29 100644
--- a/addons/project_mrp/project_mrp_view.xml
+++ b/addons/project_mrp/project_mrp_view.xml
@@ -43,7 +43,7 @@
When you sell this service to a customer, a task will be
created to follow up the job to do. This task will appear
- in the project related to the contract of the sale order.
+ in the project related to the contract of the sales order.
diff --git a/addons/project_mrp/project_procurement.py b/addons/project_mrp/project_procurement.py
index 701b888f5c2..25e88da298a 100644
--- a/addons/project_mrp/project_procurement.py
+++ b/addons/project_mrp/project_procurement.py
@@ -27,7 +27,7 @@ class procurement_order(osv.osv):
_inherit = "procurement.order"
_columns = {
'task_id': fields.many2one('project.task', 'Task'),
- 'sale_line_id': fields.many2one('sale.order.line', 'Sale order line')
+ 'sale_line_id': fields.many2one('sale.order.line', 'Sales order line')
}
def action_check_finished(self, cr, uid, ids):
@@ -59,7 +59,7 @@ class procurement_order(osv.osv):
project_project = self.pool.get('project.project')
project = procurement.product_id.project_id
if not project and procurement.sale_line_id:
- # find the project corresponding to the analytic account of the sale order
+ # find the project corresponding to the analytic account of the sales order
account = procurement.sale_line_id.order_id.project_id
project_ids = project_project.search(cr, uid, [('analytic_account_id', '=', account.id)])
projects = project_project.browse(cr, uid, project_ids, context=context)
diff --git a/addons/project_timesheet/process/project_timesheet_process.xml b/addons/project_timesheet/process/project_timesheet_process.xml
index 755560d947b..1bff69b603e 100644
--- a/addons/project_timesheet/process/project_timesheet_process.xml
+++ b/addons/project_timesheet/process/project_timesheet_process.xml
@@ -32,7 +32,7 @@
-
+
diff --git a/addons/project_timesheet/project_timesheet_view.xml b/addons/project_timesheet/project_timesheet_view.xml
index 0f6c8f3340b..548264eb07b 100644
--- a/addons/project_timesheet/project_timesheet_view.xml
+++ b/addons/project_timesheet/project_timesheet_view.xml
@@ -78,7 +78,7 @@
- Invoice Tasks Work
+ Invoice Tasksaccount.analytic.lineformtree,form
@@ -100,7 +100,7 @@
-
- Sale Order - Send by Email
+ Sales Order - Send by Email${object.user_id.email or ''}${object.company_id.name} ${object.state in ('draft', 'sent') and 'Quotation' or 'Order'} (Ref ${object.name or 'n/a' })${object.partner_invoice_id.id}
diff --git a/addons/sale/report/sale_order.rml b/addons/sale/report/sale_order.rml
index f32c558c5e1..a00d2d4e3ef 100644
--- a/addons/sale/report/sale_order.rml
+++ b/addons/sale/report/sale_order.rml
@@ -1,6 +1,6 @@
-
-
+
+
diff --git a/addons/sale/res_config.py b/addons/sale/res_config.py
index 52f38a23486..f87841e1338 100644
--- a/addons/sale/res_config.py
+++ b/addons/sale/res_config.py
@@ -27,9 +27,9 @@ class sale_configuration(osv.osv_memory):
_inherit = 'sale.config.settings'
_columns = {
- 'group_invoice_so_lines': fields.boolean('Generate invoices based on the sale order lines',
+ 'group_invoice_so_lines': fields.boolean('Generate invoices based on the sales order lines',
implied_group='sale.group_invoice_so_lines',
- help="To allow your salesman to make invoices for sale order lines using the menu 'Lines to Invoice'."),
+ help="To allow your salesman to make invoices for sales order lines using the menu 'Lines to Invoice'."),
'timesheet': fields.boolean('Prepare invoices based on timesheets',
help = """For modifying account analytic view to show important data to project manager of services companies.
You can also view the report of account analytic summary user-wise as well as month wise.
@@ -48,9 +48,9 @@ Example: 10% for retailers, promotion of 5 EUR on this product, etc."""),
'group_uom':fields.boolean("Allow using different units of measures",
implied_group='product.group_uom',
help="""Allows you to select and maintain different units of measure for products."""),
- 'group_discount_per_so_line': fields.boolean("Allow setting a discount on the sale order lines",
+ 'group_discount_per_so_line': fields.boolean("Allow setting a discount on the sales order lines",
implied_group='sale.group_discount_per_so_line',
- help="Allows you to apply some discount per sale order line."),
+ help="Allows you to apply some discount per sales order line."),
'module_warning': fields.boolean("Allow configuring alerts by customer or products",
help="""Allow to configure notification on products and trigger them when a user wants to sale a given product or a given customer.
Example: Product: this product is deprecated, do not purchase more than 5.
@@ -69,7 +69,7 @@ Example: Product: this product is deprecated, do not purchase more than 5.
But the possibility to change these values is still available.
This installs the module analytic_user_function."""),
'module_project': fields.boolean("Project"),
- 'module_sale_stock': fields.boolean("Trigger delivery orders automatically from sale orders",
+ 'module_sale_stock': fields.boolean("Trigger delivery orders automatically from sales orders",
help="""Allows you to Make Quotation, Sale Order using different Order policy and Manage Related Stock.
This installs the module sale_stock."""),
}
@@ -126,7 +126,7 @@ class account_config_settings(osv.osv_memory):
help="""This allows install module sale_analytic_plans."""),
'group_analytic_account_for_sales': fields.boolean('Analytic accounting for sales',
implied_group='sale.group_analytic_accounting',
- help="Allows you to specify an analytic account on sale orders."),
+ help="Allows you to specify an analytic account on sales orders."),
}
def onchange_sale_analytic_plans(self, cr, uid, ids, module_sale_analytic_plans, context=None):
diff --git a/addons/sale/res_partner_view.xml b/addons/sale/res_partner_view.xml
index 58d337350ba..54a9813eea9 100644
--- a/addons/sale/res_partner_view.xml
+++ b/addons/sale/res_partner_view.xml
@@ -10,15 +10,15 @@
- Click to create a quotation or sale order for this customer.
+ Click to create a quotation or sales order for this customer.
OpenERP will help you efficiently handle the complete sale flow:
- quotation, sale order, delivery, invoicing and
+ quotation, sales order, delivery, invoicing and
payment.
- The social feature helps you organize discussions on each sale
+ The social feature helps you organize discussions on each sales
order, and allow your customer to keep track of the evolution
- of the sale order.
+ of the sales order.
diff --git a/addons/sale/sale.py b/addons/sale/sale.py
index e22b99656c2..78541efa989 100644
--- a/addons/sale/sale.py
+++ b/addons/sale/sale.py
@@ -189,12 +189,12 @@ class sale_order(osv.osv):
('sent', 'Quotation Sent'),
('cancel', 'Cancelled'),
('waiting_date', 'Waiting Schedule'),
- ('progress', 'Sale Order'),
+ ('progress', 'Sales Order'),
('manual', 'Sale to Invoice'),
('invoice_except', 'Invoice Exception'),
('done', 'Done'),
], 'Status', readonly=True, track_visibility='onchange',
- help="Gives the status of the quotation or sales order. \nThe exception status is automatically set when a cancel operation occurs in the processing of a document linked to the sale order. \nThe 'Waiting Schedule' status is set when the invoice is confirmed but waiting for the scheduler to run on the order date.", select=True),
+ help="Gives the status of the quotation or sales order. \nThe exception status is automatically set when a cancel operation occurs in the processing of a document linked to the sales order. \nThe 'Waiting Schedule' status is set when the invoice is confirmed but waiting for the scheduler to run on the order date.", select=True),
'date_order': fields.date('Date', required=True, readonly=True, select=True, states={'draft': [('readonly', False)], 'sent': [('readonly', False)]}),
'create_date': fields.datetime('Creation Date', readonly=True, select=True, help="Date on which sales order is created."),
'date_confirm': fields.date('Confirmation Date', readonly=True, select=True, help="Date on which sales order is confirmed."),
@@ -217,7 +217,7 @@ class sale_order(osv.osv):
'invoiced': fields.function(_invoiced, string='Paid',
fnct_search=_invoiced_search, type='boolean', help="It indicates that an invoice has been paid."),
'invoice_exists': fields.function(_invoice_exists, string='Invoiced',
- fnct_search=_invoiced_search, type='boolean', help="It indicates that sale order has at least one invoice."),
+ fnct_search=_invoiced_search, type='boolean', help="It indicates that sales order has at least one invoice."),
'note': fields.text('Terms and conditions'),
'amount_untaxed': fields.function(_amount_all, digits_compute=dp.get_precision('Account'), string='Untaxed Amount',
@@ -239,7 +239,7 @@ class sale_order(osv.osv):
},
multi='sums', help="The total amount."),
- 'invoice_quantity': fields.selection([('order', 'Ordered Quantities')], 'Invoice on', help="The sale order will automatically create the invoice proposition (draft invoice).", required=True, readonly=True, states={'draft': [('readonly', False)]}),
+ 'invoice_quantity': fields.selection([('order', 'Ordered Quantities')], 'Invoice on', help="The sales order will automatically create the invoice proposition (draft invoice).", required=True, readonly=True, states={'draft': [('readonly', False)]}),
'payment_term': fields.many2one('account.payment.term', 'Payment Term'),
'fiscal_position': fields.many2one('account.fiscal.position', 'Fiscal Position'),
'company_id': fields.related('shop_id','company_id',type='many2one',relation='res.company',string='Company',store=True,readonly=True)
@@ -267,7 +267,7 @@ class sale_order(osv.osv):
if s['state'] in ['draft', 'cancel']:
unlink_ids.append(s['id'])
else:
- raise osv.except_osv(_('Invalid Action!'), _('In order to delete a confirmed sale order, you must cancel it before !'))
+ raise osv.except_osv(_('Invalid Action!'), _('In order to delete a confirmed sales order, you must cancel it before !'))
return osv.osv.unlink(self, cr, uid, unlink_ids, context=context)
@@ -342,7 +342,7 @@ class sale_order(osv.osv):
def _prepare_invoice(self, cr, uid, order, lines, context=None):
"""Prepare the dict of values to create the new invoice for a
- sale order. This method may be overridden to implement custom
+ sales order. This method may be overridden to implement custom
invoice generation (making sure to call super() to establish
a clean extension chain).
@@ -407,7 +407,7 @@ class sale_order(osv.osv):
def print_quotation(self, cr, uid, ids, context=None):
'''
- This function prints the sale order and mark it as sent, so that we can see more easily the next step of the workflow
+ This function prints the sales order and mark it as sent, so that we can see more easily the next step of the workflow
'''
assert len(ids) == 1, 'This option should only be used for a single id at a time'
wf_service = netsvc.LocalService("workflow")
@@ -420,13 +420,13 @@ class sale_order(osv.osv):
return {'type': 'ir.actions.report.xml', 'report_name': 'sale.order', 'datas': datas, 'nodestroy': True}
def manual_invoice(self, cr, uid, ids, context=None):
- """ create invoices for the given sale orders (ids), and open the form
+ """ create invoices for the given sales orders (ids), and open the form
view of one of the newly created invoices
"""
mod_obj = self.pool.get('ir.model.data')
wf_service = netsvc.LocalService("workflow")
- # create invoices through the sale orders' workflow
+ # create invoices through the sales orders' workflow
inv_ids0 = set(inv.id for sale in self.browse(cr, uid, ids, context) for inv in sale.invoice_ids)
for id in ids:
wf_service.trg_validate(uid, 'sale.order', id, 'manual_invoice', cr)
@@ -452,7 +452,7 @@ class sale_order(osv.osv):
def action_view_invoice(self, cr, uid, ids, context=None):
'''
- This function returns an action that display existing invoices of given sale order ids. It can either be a in a list or in a form view, if there is only one invoice to show.
+ This function returns an action that display existing invoices of given sales order ids. It can either be a in a list or in a form view, if there is only one invoice to show.
'''
mod_obj = self.pool.get('ir.model.data')
act_obj = self.pool.get('ir.actions.act_window')
@@ -570,7 +570,7 @@ class sale_order(osv.osv):
wf_service = netsvc.LocalService('workflow')
wf_service.trg_validate(uid, 'sale.order', ids[0], 'order_confirm', cr)
- # redisplay the record as a sale order
+ # redisplay the record as a sales order
view_ref = self.pool.get('ir.model.data').get_object_reference(cr, uid, 'sale', 'view_order_form')
view_id = view_ref and view_ref[1] or False,
return {
@@ -589,7 +589,7 @@ class sale_order(osv.osv):
context = context or {}
for o in self.browse(cr, uid, ids):
if not o.order_line:
- raise osv.except_osv(_('Error!'),_('You cannot confirm a sale order which has no line.'))
+ raise osv.except_osv(_('Error!'),_('You cannot confirm a sales order which has no line.'))
noprod = self.test_no_product(cr, uid, o, context)
if (o.order_policy == 'manual') or noprod:
self.write(cr, uid, [o.id], {'state': 'manual', 'date_confirm': fields.date.context_today(self, cr, uid, context=context)})
@@ -735,7 +735,7 @@ class sale_order_line(osv.osv):
def _prepare_order_line_invoice_line(self, cr, uid, line, account_id=False, context=None):
"""Prepare the dict of values to create the new invoice line for a
- sale order line. This method may be overridden to implement custom
+ sales order line. This method may be overridden to implement custom
invoice generation (making sure to call super() to establish
a clean extension chain).
@@ -809,7 +809,7 @@ class sale_order_line(osv.osv):
def button_cancel(self, cr, uid, ids, context=None):
for line in self.browse(cr, uid, ids, context=context):
if line.invoiced:
- raise osv.except_osv(_('Invalid Action!'), _('You cannot cancel a sale order line that has already been invoiced.'))
+ raise osv.except_osv(_('Invalid Action!'), _('You cannot cancel a sales order line that has already been invoiced.'))
return self.write(cr, uid, ids, {'state': 'cancel'})
def button_confirm(self, cr, uid, ids, context=None):
diff --git a/addons/sale/sale_data.xml b/addons/sale/sale_data.xml
index 3176c1e7212..6d7cd043c39 100644
--- a/addons/sale/sale_data.xml
+++ b/addons/sale/sale_data.xml
@@ -51,7 +51,7 @@
Quotation send
- Sale Order Confirmed
+ Sales Order Confirmedsale.orderQuotation confirmed
diff --git a/addons/sale/sale_view.xml b/addons/sale/sale_view.xml
index 2c2fdd6991f..0edda45b6d1 100644
--- a/addons/sale/sale_view.xml
+++ b/addons/sale/sale_view.xml
@@ -58,7 +58,7 @@
Click to define a new sale shop.
- Each quotation or sale order must be linked to a shop. The
+ Each quotation or sales order must be linked to a shop. The
shop also defines the warehouse from which the products will be
delivered for each particular sales.
- Click to create a quotation that can be converted into a sale
+ Click to create a quotation that can be converted into a sales
order.
OpenERP will help you efficiently handle the complete sales flow:
- quotation, sale order, delivery, invoicing and payment.
+ quotation, sales order, delivery, invoicing and payment.
@@ -379,12 +379,12 @@
Click to create a quotation, the first step of a new sale.
OpenERP will help you handle efficiently the complete sale flow:
- from the quotation to the sale order, the
+ from the quotation to the sales order, the
delivery, the invoicing and the payment collection.
- The social feature helps you organize discussions on each sale
+ The social feature helps you organize discussions on each sales
order, and allow your customers to keep track of the evolution
- of the sale order.
+ of the sales order.
@@ -468,7 +468,7 @@
sale.order.line
-
+
@@ -490,11 +490,11 @@
sale.order.line
-
-
-
+
+
+
-
+
diff --git a/addons/sale/security/sale_security.xml b/addons/sale/security/sale_security.xml
index bf38d31b156..49bd0e8716b 100644
--- a/addons/sale/security/sale_security.xml
+++ b/addons/sale/security/sale_security.xml
@@ -25,12 +25,12 @@
- Enable Invoicing Sale order lines
+ Enable Invoicing Sales order lines
- Addresses in Sale Orders
+ Addresses in Sales Orders
@@ -65,14 +65,14 @@
- Sale Order multi-company
+ Sales Order multi-company['|',('company_id','=',False),('company_id','child_of',[user.company_id.id])]
- Sale Order Line multi-company
+ Sales Order Line multi-company['|',('company_id','=',False),('company_id','child_of',[user.company_id.id])]
diff --git a/addons/sale/wizard/sale_line_invoice.xml b/addons/sale/wizard/sale_line_invoice.xml
index 720586e638c..70693215be0 100644
--- a/addons/sale/wizard/sale_line_invoice.xml
+++ b/addons/sale/wizard/sale_line_invoice.xml
@@ -7,8 +7,8 @@
sale.advance.payment.inv
-
- Sale Order Confirmed
+ Sales Order Confirmedcrm.case.sectionsection_id
diff --git a/addons/sale_crm/wizard/crm_make_sale.py b/addons/sale_crm/wizard/crm_make_sale.py
index 02d36f14c21..a052f47ca1f 100644
--- a/addons/sale_crm/wizard/crm_make_sale.py
+++ b/addons/sale_crm/wizard/crm_make_sale.py
@@ -145,7 +145,7 @@ class crm_make_sale(osv.osv_memory):
_columns = {
'shop_id': fields.many2one('sale.shop', 'Shop', required=True),
'partner_id': fields.many2one('res.partner', 'Customer', required=True, domain=[('customer','=',True)]),
- 'close': fields.boolean('Mark Won', help='Check this to close the opportunity after having created the sale order.'),
+ 'close': fields.boolean('Mark Won', help='Check this to close the opportunity after having created the sales order.'),
}
_defaults = {
'shop_id': _get_shop_id,
diff --git a/addons/sale_order_dates/__openerp__.py b/addons/sale_order_dates/__openerp__.py
index 6db8f2b27d9..3fa9fba0ecf 100644
--- a/addons/sale_order_dates/__openerp__.py
+++ b/addons/sale_order_dates/__openerp__.py
@@ -28,8 +28,8 @@
Add additional date information to the sales order.
===================================================
-You can add the following additional dates to a sale order:
------------------------------------------------------------
+You can add the following additional dates to a sales order:
+------------------------------------------------------------
* Requested Date
* Commitment Date
* Effective Date
diff --git a/addons/sale_stock/res_config.py b/addons/sale_stock/res_config.py
index 53cb0c2b8fa..3a6dcb404dd 100644
--- a/addons/sale_stock/res_config.py
+++ b/addons/sale_stock/res_config.py
@@ -29,7 +29,7 @@ class sale_configuration(osv.osv_memory):
_columns = {
'group_sale_delivery_address': fields.boolean("Allow a different address for delivery and invoicing ",
implied_group='sale.group_delivery_invoice_address',
- help="Allows you to specify different delivery and invoice addresses on a sale order."),
+ help="Allows you to specify different delivery and invoice addresses on a sales order."),
'group_invoice_deli_orders': fields.boolean('Generate invoices after and based on delivery orders',
implied_group='sale_stock.group_invoice_deli_orders',
help="To allow your salesman to make invoices for Delivery Orders using the menu 'Deliveries to Invoice'."),
@@ -43,14 +43,14 @@ class sale_configuration(osv.osv_memory):
'The default invoicing method is', default_model='sale.order',
help="You can generate invoices based on sales orders or based on shippings."),
'module_delivery': fields.boolean('Allow adding shipping costs',
- help ="""Allows you to add delivery methods in sale orders and delivery orders.
+ help ="""Allows you to add delivery methods in sales orders and delivery orders.
You can define your own carrier and delivery grids for prices.
This installs the module delivery."""),
'default_picking_policy' : fields.boolean("Deliver all at once when all products are available.",
help = "Sales order by default will be configured to deliver all products at once instead of delivering each product when it is available. This may have an impact on the shipping price."),
'group_mrp_properties': fields.boolean('Product properties on order lines',
implied_group='sale.group_mrp_properties',
- help="Allows you to tag sale order lines with properties."),
+ help="Allows you to tag sales order lines with properties."),
'group_multiple_shops': fields.boolean("Manage multiple shops",
implied_group='stock.group_locations',
help="This allows to configure and use multiple shops."),
diff --git a/addons/sale_stock/sale_stock.py b/addons/sale_stock/sale_stock.py
index 3c45feb5604..1b5ddefbe74 100644
--- a/addons/sale_stock/sale_stock.py
+++ b/addons/sale_stock/sale_stock.py
@@ -118,7 +118,7 @@ class sale_order(osv.osv):
('sent', 'Quotation Sent'),
('cancel', 'Cancelled'),
('waiting_date', 'Waiting Schedule'),
- ('progress', 'Sale Order'),
+ ('progress', 'Sales Order'),
('manual', 'Sale to Invoice'),
('shipping_except', 'Shipping Exception'),
('invoice_except', 'Invoice Exception'),
@@ -141,7 +141,7 @@ class sale_order(osv.osv):
'shipped': fields.boolean('Delivered', readonly=True, help="It indicates that the sales order has been delivered. This field is updated only after the scheduler(s) have been launched."),
'picked_rate': fields.function(_picked_rate, string='Picked', type='float'),
'invoice_quantity': fields.selection([('order', 'Ordered Quantities'), ('procurement', 'Shipped Quantities')], 'Invoice on',
- help="The sale order will automatically create the invoice proposition (draft invoice).\
+ help="The sales order will automatically create the invoice proposition (draft invoice).\
You have to choose if you want your invoice based on ordered ", required=True, readonly=True, states={'draft': [('readonly', False)]}),
}
_defaults = {
@@ -164,7 +164,7 @@ class sale_order(osv.osv):
def action_view_delivery(self, cr, uid, ids, context=None):
'''
- This function returns an action that display existing delivery orders of given sale order ids. It can either be a in a list or in a form view, if there is only one delivery order to show.
+ This function returns an action that display existing delivery orders of given sales order ids. It can either be a in a list or in a form view, if there is only one delivery order to show.
'''
mod_obj = self.pool.get('ir.model.data')
act_obj = self.pool.get('ir.actions.act_window')
@@ -329,8 +329,8 @@ class sale_order(osv.osv):
# FIXME: deals with potentially cancelled shipments, seems broken (specially if shipment has production lot)
"""
Define ship_recreate for process after shipping exception
- param order: sale order to which the order lines belong
- param line: sale order line records to procure
+ param order: sales order to which the order lines belong
+ param line: sales order line records to procure
param move_id: the ID of stock move
param proc_id: the ID of procurement
"""
@@ -353,9 +353,9 @@ class sale_order(osv.osv):
return date_planned
def _create_pickings_and_procurements(self, cr, uid, order, order_lines, picking_id=False, context=None):
- """Create the required procurements to supply sale order lines, also connecting
+ """Create the required procurements to supply sales order lines, also connecting
the procurements to appropriate stock moves in order to bring the goods to the
- sale order's requested location.
+ sales order's requested location.
If ``picking_id`` is provided, the stock moves will be added to it, otherwise
a standard outgoing picking will be created to wrap the stock moves, as returned
@@ -365,8 +365,8 @@ class sale_order(osv.osv):
multiple stock pickings may override this method and call ``super()`` with
different subsets of ``order_lines`` and/or preset ``picking_id`` values.
- :param browse_record order: sale order to which the order lines belong
- :param list(browse_record) order_lines: sale order line records to procure
+ :param browse_record order: sales order to which the order lines belong
+ :param list(browse_record) order_lines: sales order line records to procure
:param int picking_id: optional ID of a stock picking to which the created stock moves
will be added. A new picking will be created if ommitted.
:return: True
diff --git a/addons/sale_stock/stock.py b/addons/sale_stock/stock.py
index 3faa2ea31b0..93acf8579f5 100644
--- a/addons/sale_stock/stock.py
+++ b/addons/sale_stock/stock.py
@@ -50,7 +50,7 @@ class stock_picking(osv.osv):
def _get_partner_to_invoice(self, cr, uid, picking, context=None):
""" Inherit the original function of the 'stock' module
- We select the partner of the sale order as the partner of the customer invoice
+ We select the partner of the sales order as the partner of the customer invoice
"""
if picking.sale_id:
return picking.sale_id.partner_id
@@ -63,7 +63,7 @@ class stock_picking(osv.osv):
def _prepare_invoice(self, cr, uid, picking, partner, inv_type, journal_id, context=None):
""" Inherit the original function of the 'stock' module in order to override some
- values if the picking has been generated by a sale order
+ values if the picking has been generated by a sales order
"""
invoice_vals = super(stock_picking, self)._prepare_invoice(cr, uid, picking, partner, inv_type, journal_id, context=context)
if picking.sale_id:
diff --git a/addons/stock/res_config.py b/addons/stock/res_config.py
index 9653c284b4b..4c15fcf1732 100644
--- a/addons/stock/res_config.py
+++ b/addons/stock/res_config.py
@@ -49,7 +49,7 @@ This installs the module product_expiry."""),
'group_uom': fields.boolean("Manage different units of measure for products",
implied_group='product.group_uom',
help="""Allows you to select and maintain different units of measure for products."""),
- 'group_uos': fields.boolean("Invoice products in a different unit of measure than the sale order",
+ 'group_uos': fields.boolean("Invoice products in a different unit of measure than the sales order",
implied_group='product.group_uos',
help="""Allows you to sell units of a product, but invoice based on a different unit of measure.
For instance, you can sell pieces of meat that you invoice based on their weight."""),
diff --git a/addons/stock/stock.py b/addons/stock/stock.py
index da383c2fe29..7198c89e286 100644
--- a/addons/stock/stock.py
+++ b/addons/stock/stock.py
@@ -2048,7 +2048,7 @@ class stock_move(osv.osv):
# name of new picking according to its type
new_pick_name = seq_obj.get(cr, uid, 'stock.picking.' + ptype)
pickid = self._create_chained_picking(cr, uid, new_pick_name, picking, ptype, todo, context=context)
- # Need to check name of old picking because it always considers picking as "OUT" when created from Sale Order
+ # Need to check name of old picking because it always considers picking as "OUT" when created from Sales Order
old_ptype = location_obj.picking_type_get(cr, uid, picking.move_lines[0].location_id, picking.move_lines[0].location_dest_id)
if old_ptype != picking.type:
old_pick_name = seq_obj.get(cr, uid, 'stock.picking.' + old_ptype)
diff --git a/addons/warning/warning.py b/addons/warning/warning.py
index 76516769e5b..4bdada396bc 100644
--- a/addons/warning/warning.py
+++ b/addons/warning/warning.py
@@ -34,8 +34,8 @@ WARNING_HELP = _('Selecting the "Warning" option will notify user with the messa
class res_partner(osv.osv):
_inherit = 'res.partner'
_columns = {
- 'sale_warn' : fields.selection(WARNING_MESSAGE, 'Sale Order', help=WARNING_HELP, required=True),
- 'sale_warn_msg' : fields.text('Message for Sale Order'),
+ 'sale_warn' : fields.selection(WARNING_MESSAGE, 'Sales Order', help=WARNING_HELP, required=True),
+ 'sale_warn_msg' : fields.text('Message for Sales Order'),
'purchase_warn' : fields.selection(WARNING_MESSAGE, 'Purchase Order', help=WARNING_HELP, required=True),
'purchase_warn_msg' : fields.text('Message for Purchase Order'),
'picking_warn' : fields.selection(WARNING_MESSAGE, 'Stock Picking', help=WARNING_HELP, required=True),
@@ -232,8 +232,8 @@ class stock_picking_out(osv.osv):
class product_product(osv.osv):
_inherit = 'product.product'
_columns = {
- 'sale_line_warn' : fields.selection(WARNING_MESSAGE,'Sale Order Line', help=WARNING_HELP, required=True),
- 'sale_line_warn_msg' : fields.text('Message for Sale Order Line'),
+ 'sale_line_warn' : fields.selection(WARNING_MESSAGE,'Sales Order Line', help=WARNING_HELP, required=True),
+ 'sale_line_warn_msg' : fields.text('Message for Sales Order Line'),
'purchase_line_warn' : fields.selection(WARNING_MESSAGE,'Purchase Order Line', help=WARNING_HELP, required=True),
'purchase_line_warn_msg' : fields.text('Message for Purchase Order Line'),
}
diff --git a/addons/warning/warning_view.xml b/addons/warning/warning_view.xml
index d88dc8101a5..1df38771e9c 100644
--- a/addons/warning/warning_view.xml
+++ b/addons/warning/warning_view.xml
@@ -10,7 +10,7 @@
-
+