[IMP] sale and sale_* modules:-changed the string 'Sale order' to 'Sales order'
bzr revid: mtr@mtr-20100909052501-ilbxhug0o49a7qu9
This commit is contained in:
parent
4f50060561
commit
648cc18769
|
@ -27,7 +27,7 @@
|
|||
</record>
|
||||
|
||||
<record id="open_board_sales_manager" model="ir.actions.act_window">
|
||||
<field name="name">Sale Dashboard</field>
|
||||
<field name="name">Sales Dashboard</field>
|
||||
<field name="res_model">board.board</field>
|
||||
<field name="view_type">form</field>
|
||||
<field name="view_mode">form</field>
|
||||
|
|
|
@ -108,7 +108,7 @@
|
|||
<field name="invoiced"/>
|
||||
</group>
|
||||
<notebook colspan="5">
|
||||
<page string="Sale Order">
|
||||
<page string="Sales Order">
|
||||
<field name="partner_id" on_change="onchange_partner_id(partner_id)" required="1"/>
|
||||
<field domain="[('partner_id','=',partner_id)]" name="partner_order_id"/>
|
||||
<field domain="[('partner_id','=',partner_id)]" name="partner_invoice_id" groups="base.group_extended"/>
|
||||
|
@ -256,15 +256,15 @@
|
|||
<field name="type">search</field>
|
||||
<field name="arch" type="xml">
|
||||
<search string="Search Sales Order">
|
||||
<filter icon="terp-document-new" string="Quotations" domain="[('state','=','draft')]" help="Sale Orders that haven't yet be confirmed"/>
|
||||
<filter icon="terp-document-new" string="Quotations" domain="[('state','=','draft')]" help="Sales Order that haven't yet been confirmed"/>
|
||||
<filter icon="terp-check" string="Sales" domain="[('state','in',('manual','progress'))]"/>
|
||||
<separator orientation="vertical"/>
|
||||
<filter icon="terp-dolar_ok!" string="To Invoice" domain="[('state','=','manual')]" help="Sale Orders ready to be invoiced"/>
|
||||
<filter icon="terp-dolar_ok!" string="To Invoice" domain="[('state','=','manual')]" help="Sales Order ready to be invoiced"/>
|
||||
<separator orientation="vertical"/>
|
||||
<field name="name" select="1"/>
|
||||
<field name="partner_id" select="1"/>
|
||||
<field name="user_id" select="1">
|
||||
<filter domain="[('user_id','=',uid)]" help="My Sale Orders" icon="terp-personal"/>
|
||||
<filter domain="[('user_id','=',uid)]" help="My Sales Order" icon="terp-personal"/>
|
||||
</field>
|
||||
|
||||
<field name="date_order" select="1" string="Order date" />
|
||||
|
@ -288,11 +288,11 @@
|
|||
<field name="view_type">form</field>
|
||||
<field name="view_mode">tree,form,calendar,graph</field>
|
||||
<field name="search_view_id" ref="view_sales_order_filter"/>
|
||||
<field name="help">The sale order manages the invoicing, the product fullfilment and the
|
||||
<field name="help">The sales order manages the invoicing, the product fullfilment and the
|
||||
delivery processes. OpenERP can handle products, services and
|
||||
consumables so that a sale order can trigger tasks, manufacturing
|
||||
consumables so that a sales order can trigger tasks, manufacturing
|
||||
orders, purchases, etc. It support several invoicing methods according
|
||||
to your configuration: from the sale order, from the pickings, etc.
|
||||
to your configuration: from the sales order, from the pickings, etc.
|
||||
</field>
|
||||
</record>
|
||||
<menuitem action="action_order_form" id="menu_sale_order" parent="base.menu_sales" sequence="3"/>
|
||||
|
@ -438,7 +438,7 @@ to your configuration: from the sale order, from the pickings, etc.
|
|||
<field name="order_partner_id"/>
|
||||
<field name="product_id"/>
|
||||
<field name="salesman_id">
|
||||
<filter icon="terp-personnal" domain="[('salesman_id','=',uid)]" help="Sale Order Lines related to a Sale Order of mine"/>
|
||||
<filter icon="terp-personnal" domain="[('salesman_id','=',uid)]" help="Sale Order Lines related to a Sales Order of mine"/>
|
||||
</field>
|
||||
<newline/>
|
||||
<group expand="context.get('report',False)" string="Group By..." colspan="9" col="8">
|
||||
|
@ -519,7 +519,7 @@ to your configuration: from the sale order, from the pickings, etc.
|
|||
<!-- configartion view -->
|
||||
|
||||
<record id="view_config_picking_policy" model="ir.ui.view">
|
||||
<field name="name">Configure Picking Policy for Sale Order </field>
|
||||
<field name="name">Configure Picking Policy for Sales Order </field>
|
||||
<field name="model">sale.config.picking_policy</field>
|
||||
<field name="type">form</field>
|
||||
<field name="inherit_id" ref="base.res_config_view_base"/>
|
||||
|
@ -530,7 +530,7 @@ to your configuration: from the sale order, from the pickings, etc.
|
|||
</form>
|
||||
<separator string="title" position="attributes">
|
||||
<attribute name="string"
|
||||
>Configure Sale Order Logistic</attribute>
|
||||
>Configure Sales Order Logistic</attribute>
|
||||
</separator>
|
||||
<xpath expr="//label[@string='description']" position="attributes">
|
||||
<attribute name="string">Setup your sales workflow and default values.</attribute>
|
||||
|
@ -552,7 +552,7 @@ to your configuration: from the sale order, from the pickings, etc.
|
|||
</record>
|
||||
|
||||
<record id="action_config_picking_policy" model="ir.actions.act_window">
|
||||
<field name="name">Configure Picking Policy for Sale Order</field>
|
||||
<field name="name">Configure Picking Policy for Sales Order</field>
|
||||
<field name="type">ir.actions.act_window</field>
|
||||
<field name="res_model">sale.config.picking_policy</field>
|
||||
<field name="view_id" ref="view_config_picking_policy"/>
|
||||
|
|
|
@ -20,15 +20,15 @@
|
|||
##############################################################################
|
||||
|
||||
{
|
||||
'name': 'Creates Sale orders from Opportunity',
|
||||
'name': 'Creates Sales order from Opportunity',
|
||||
'version': '1.0',
|
||||
'category': 'Generic Modules/Sales & Purchases',
|
||||
'description': """
|
||||
This module adds a shortcut on one or several opportunity cases in the CRM.
|
||||
This shortcut allows you to generate a sale order based on the selected case.
|
||||
This shortcut allows you to generate a sales order based on the selected case.
|
||||
If different cases are open (a list), it generates one sale order by
|
||||
case.
|
||||
The case is then closed and linked to the generated sale order.
|
||||
The case is then closed and linked to the generated sales order.
|
||||
|
||||
We suggest you to install this module if you installed both the sale and the
|
||||
crm modules.
|
||||
|
|
|
@ -33,7 +33,7 @@
|
|||
<field name="inherit_id" ref="sale.view_sales_order_filter"/>
|
||||
<field name="arch" type="xml">
|
||||
<field name="date_order" position="after">
|
||||
<field name="section_id" default="context.get('section_id', False)" widget="selection" string="Sale Team" groups="base.group_extended">
|
||||
<field name="section_id" default="context.get('section_id', False)" widget="selection" string="Sales Team" groups="base.group_extended">
|
||||
<filter icon="terp-personal+"
|
||||
domain="[('section_id.user_id','=',uid)]"
|
||||
groups="base.group_extended"
|
||||
|
|
|
@ -116,11 +116,11 @@
|
|||
<field name="arch" type="xml">
|
||||
<search string="Sales by Journal">
|
||||
<group col="8" colspan="4">
|
||||
<filter icon="terp-document-new" string="Draft" domain="[('state','=','draft')]" help="Sale Journals which are in draft state"/>
|
||||
<filter icon="gtk-open" string="Open" domain="[('state','=','open')]" help="Open Sale Journals"/>
|
||||
<filter icon="gtk-cancel" string="Cancel" domain="[('state','=','cancel')]" help="Sale Journals which are cancelled"/>
|
||||
<filter icon="terp-check" string="Confirm" domain="[('state','=','confirm')]" help="Confirmed Sale Journals"/>
|
||||
<filter icon="terp-camera_test" string="Close" domain="[('state','=','done')]" help="Sale Journals which are closed"/>
|
||||
<filter icon="terp-document-new" string="Draft" domain="[('state','=','draft')]" help="Sales Journal which are in draft state"/>
|
||||
<filter icon="gtk-open" string="Open" domain="[('state','=','open')]" help="Open Sales Journal"/>
|
||||
<filter icon="gtk-cancel" string="Cancel" domain="[('state','=','cancel')]" help="Sales Journal which are cancelled"/>
|
||||
<filter icon="terp-check" string="Confirm" domain="[('state','=','confirm')]" help="Confirmed Sales Journal"/>
|
||||
<filter icon="terp-camera_test" string="Close" domain="[('state','=','done')]" help="Sales Journal which are closed"/>
|
||||
<separator orientation="vertical"/>
|
||||
<field name="name"/>
|
||||
<field name="code"/>
|
||||
|
|
|
@ -24,7 +24,7 @@
|
|||
"depends" : ["sale", "account_invoice_layout"],
|
||||
"author" : "OpenERP SA",
|
||||
"description": """
|
||||
This module provides features to improve the layout of the Sale Order.
|
||||
This module provides features to improve the layout of the Sales Order.
|
||||
|
||||
It gives you the possibility to
|
||||
* order all the lines of an sale order
|
||||
|
|
|
@ -19,7 +19,7 @@
|
|||
##############################################################################
|
||||
|
||||
{
|
||||
"name":"Margins in Sale Orders",
|
||||
"name":"Margins in Sales Order",
|
||||
"version":"1.0",
|
||||
"category" : "Generic Modules/Sales & Purchases",
|
||||
"description": """
|
||||
|
|
|
@ -27,8 +27,8 @@
|
|||
'description': """
|
||||
This module provides facility to the user to install mrp and sale modules
|
||||
at a time. It is basically used when we want to keep track of production
|
||||
orders generated from sale orders.
|
||||
It adds sale name and sale Reference on production order
|
||||
orders generated from sales order.
|
||||
It adds sales name and sales Reference on production order
|
||||
""",
|
||||
'author': 'OpenERP SA',
|
||||
'website': 'http://www.openerp.com',
|
||||
|
|
|
@ -25,7 +25,7 @@
|
|||
'version': '1.0',
|
||||
'category': 'Generic Modules/CRM & SRM',
|
||||
'description': """
|
||||
Add commitment, requested and effective dates on the sale order.
|
||||
Add commitment, requested and effective dates on the sales order.
|
||||
""",
|
||||
'author': 'OpenERP SA',
|
||||
'website': 'http://www.openerp.com',
|
||||
|
|
Loading…
Reference in New Issue