[IMP] improved menu tips - 10 firsts clicks
bzr revid: fp@openerp.com-20120804132136-2b18cfkwv0njsglj
This commit is contained in:
parent
1f88244a68
commit
4e69bdd6fc
|
@ -42,7 +42,17 @@
|
|||
<field name="view_type">form</field>
|
||||
<field name="view_mode">tree,form</field>
|
||||
<field name="context" eval="{'default_partner_id':ref('base.main_partner'), 'company_hide':False, 'default_company_id':ref('base.main_company'), 'search_default_my_bank':1}"/>
|
||||
<field name="help">Configure your company's bank account and select those that must appear on the report footer. You can reorder banks in the list view. If you use the accounting application of OpenERP, journals and accounts will be created automatically based on these data.</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to setup a new bank account.
|
||||
</p><p>
|
||||
Configure your company's bank account and select those that must
|
||||
appear on the report footer.
|
||||
<p></p>
|
||||
If you use the accounting application of OpenERP, journals and
|
||||
accounts will be created automatically based on these data.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
<menuitem
|
||||
sequence="0"
|
||||
|
|
|
@ -509,11 +509,18 @@
|
|||
<field name="domain">[('type','=','out_invoice')]</field>
|
||||
<field name="context">{'default_type':'out_invoice', 'type':'out_invoice', 'journal_type': 'sale'}</field>
|
||||
<field name="search_view_id" ref="view_account_invoice_filter"/>
|
||||
<field name="help">
|
||||
Click here to create a new Invoice.
|
||||
<p>
|
||||
An invoice can be generated automatically from a sale order or a delivery order.
|
||||
The invoice can be send by email.
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to create a customer invoice.
|
||||
</p><p>
|
||||
OpenERP's electronic invoicing allows to ease and fasten the
|
||||
collection of customer payments. Your customer receives the
|
||||
invoice by email and he can pay online and/or import it
|
||||
in his own system.
|
||||
</p><p>
|
||||
The discussions with your customer are automatically displayed at
|
||||
the bottom of each invoice.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
|
@ -542,11 +549,14 @@
|
|||
<field name="domain">[('type','=','in_invoice')]</field>
|
||||
<field name="context">{'default_type': 'in_invoice', 'type': 'in_invoice', 'journal_type': 'purchase'}</field>
|
||||
<field name="search_view_id" ref="view_account_invoice_filter"/>
|
||||
<field name="help">
|
||||
Click here to create Supplier invoice.
|
||||
<p>
|
||||
You can control the invoice from your supplier according to what you purchased or received.
|
||||
OpenERP can also generate draft invoices automatically from purchase orders or receipts.
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to record a new supplier invoice.
|
||||
</p><p>
|
||||
You can control the invoice from your supplier according to
|
||||
what you purchased or received. OpenERP can also generate
|
||||
draft invoices automatically from purchase orders or receipts.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
<menuitem action="action_invoice_tree2" id="menu_action_invoice_tree2" parent="menu_finance_payables"/>
|
||||
|
@ -560,11 +570,16 @@
|
|||
<field name="domain">[('type','=','out_refund')]</field>
|
||||
<field name="context">{'default_type':'out_refund', 'type':'out_refund', 'journal_type': 'sale_refund'}</field>
|
||||
<field name="search_view_id" ref="view_account_invoice_filter"/>
|
||||
<field name="help">
|
||||
Click here to create a new customer refund.
|
||||
<p>
|
||||
A refund is a document that credits an invoice completely or partially.
|
||||
You can also generate refunds and reconcile them directly from the invoice form.
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to create a customer refund.
|
||||
</p><p>
|
||||
A refund is a document that credits an invoice completely or
|
||||
partially.
|
||||
</p><p>
|
||||
Instead of manually creating a customer refund, you
|
||||
can generate it directly from the related customer invoice.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
|
@ -591,11 +606,13 @@
|
|||
<field name="domain">[('type','=','in_refund')]</field>
|
||||
<field name="context">{'default_type': 'in_refund', 'type': 'in_refund', 'journal_type': 'purchase_refund'}</field>
|
||||
<field name="search_view_id" ref="view_account_invoice_filter"/>
|
||||
<field name="help">
|
||||
Click here to create a new supplier refund.
|
||||
<p>
|
||||
Track refunds you receive from your suppliers.
|
||||
You can also generate refunds and reconcile them directly from the invoice form.
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to register a refund you received from a supplier.
|
||||
</p><p>
|
||||
Instead of creating the supplier refund manually, you can generate
|
||||
refunds and reconcile them directly from the related supplier invoice.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
<menuitem action="action_invoice_tree4" id="menu_action_invoice_tree4" parent="menu_finance_payables"/>
|
||||
|
|
|
@ -78,7 +78,19 @@
|
|||
<field name="res_model">account.fiscalyear</field>
|
||||
<field name="view_type">form</field>
|
||||
<field name="view_mode">tree,form</field>
|
||||
<field name="help">Define your company's financial year according to your needs. A financial year is a period at the end of which a company's accounts are made up (usually 12 months). The financial year is usually referred to by the date in which it ends. For example, if a company's financial year ends November 30, 2011, then everything between December 1, 2010 and November 30, 2011 would be referred to as FY 2011. You are not obliged to follow the actual calendar year.</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to start a new fiscal year.
|
||||
</p><p>
|
||||
Define your company's financial year according to your needs. A
|
||||
financial year is a period at the end of which a company's
|
||||
accounts are made up (usually 12 months). The financial year is
|
||||
usually referred to by the date in which it ends. For example,
|
||||
if a company's financial year ends November 30, 2011, then
|
||||
everything between December 1, 2010 and November 30, 2011
|
||||
would be referred to as FY 2011.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
<menuitem id="next_id_23" name="Periods" parent="account.menu_finance_configuration" sequence="5" />
|
||||
<menuitem action="action_account_fiscalyear_form" id="menu_action_account_fiscalyear_form" parent="next_id_23"/>
|
||||
|
@ -153,7 +165,14 @@
|
|||
<field name="view_type">form</field>
|
||||
<field name="view_mode">tree,form</field>
|
||||
<field name="context">{'search_default_draft': 1}</field>
|
||||
<field name="help">Here you can define a financial period, an interval of time in your company's financial year. An accounting period typically is a month or a quarter. It usually corresponds to the periods of the tax declaration. Create and manage periods from here and decide whether a period should be closed or left open depending on your company's activities over a specific period.</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to add a fiscal period.
|
||||
</p><p>
|
||||
An accounting period typically is a month or a quarter. It
|
||||
usually corresponds to the periods of the tax declaration.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
<menuitem action="action_account_period_form" id="menu_action_account_period_form" parent="account.next_id_23" groups="base.group_no_one"/>
|
||||
|
||||
|
@ -260,7 +279,18 @@
|
|||
<field name="view_mode">tree,form,graph</field>
|
||||
<field name="search_view_id" ref="view_account_search"/>
|
||||
<field name="view_id" ref="view_account_list"/>
|
||||
<field name="help">Create and manage the accounts you need to record journal entries. An account is part of a ledger allowing your company to register all kinds of debit and credit transactions. Companies present their annual accounts in two main parts: the balance sheet and the income statement (profit and loss account). The annual accounts of a company are required by law to disclose a certain amount of information. They have to be certified by an external auditor annually.</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to add an account.
|
||||
</p><p>
|
||||
An account is part of a ledger allowing your company
|
||||
to register all kinds of debit and credit transactions.
|
||||
Companies present their annual accounts in two main parts: the
|
||||
balance sheet and the income statement (profit and loss
|
||||
account). The annual accounts of a company are required by law
|
||||
to disclose a certain amount of information.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
<menuitem id="account_account_menu" name="Accounts" parent="account.menu_finance_configuration" sequence="15"/>
|
||||
<menuitem action="action_account_form" id="menu_action_account_form" parent="account_account_menu"/>
|
||||
|
@ -320,7 +350,17 @@
|
|||
<field name="view_mode">tree</field>
|
||||
<field name="view_id" ref="view_account_gain_loss_tree"/>
|
||||
<field name="domain">[('currency_id','!=',False)]</field>
|
||||
<field name="help">When doing multi-currency transactions, you may loose or gain some amount due to changes of exchange rate. This menu gives you a forecast of the Gain or Loss you'd realized if those transactions were ended today. Only for accounts having a secondary currency set.</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to add an account.
|
||||
</p><p>
|
||||
When doing multi-currency transactions, you may loose or gain
|
||||
some amount due to changes of exchange rate. This menu gives
|
||||
you a forecast of the Gain or Loss you'd realized if those
|
||||
transactions were ended today. Only for accounts having a
|
||||
secondary currency set.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
<menuitem
|
||||
|
@ -397,7 +437,18 @@
|
|||
<field name="view_type">form</field>
|
||||
<field name="view_mode">tree,form</field>
|
||||
<field name="search_view_id" ref="view_account_journal_view_search"/>
|
||||
<field name="help">Here you can customize an existing journal view or create a new view. Journal views determine the way you can record entries in your journal. Select the fields you want to appear in a journal and determine the sequence in which they will appear. Then you can create a new journal and link your view to it.</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to specify lists of columns to display for a type of journal.
|
||||
</p><p>
|
||||
Journal views determine the way you can record entries in
|
||||
your journal. Select the fields you want to appear in a journal
|
||||
and determine the sequence in which they will appear.
|
||||
</p><p>
|
||||
On the journal definition form, you can select the view you
|
||||
want to use to display journal items related to this journal.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
<menuitem action="action_account_journal_view" id="menu_action_account_journal_view" parent="account.menu_journals" sequence="20"/>
|
||||
|
@ -512,7 +563,18 @@
|
|||
<field name="res_model">account.journal</field>
|
||||
<field name="view_type">form</field>
|
||||
<field name="view_mode">tree,form</field>
|
||||
<field name="help">Create and manage your company's journals from this menu. A journal is used to record transactions of all accounting data related to the day-to-day business of your company using double-entry bookkeeping system. Depending on the nature of its activities and the number of daily transactions, a company may keep several types of specialized journals such as a cash journal, purchase journal, sales journal...</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to add a journal.
|
||||
</p><p>
|
||||
A journal is used to record transactions of all accounting data
|
||||
related to the day-to-day business.
|
||||
</p><p>
|
||||
A typical company may use one journal per payment method (cash,
|
||||
bank accounts, checks), one purchase journal, one sale journal
|
||||
and one for miscellaneous information.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
<menuitem action="action_account_journal_form" id="menu_action_account_journal_form" parent="menu_journals"/>
|
||||
|
||||
|
@ -662,7 +724,18 @@
|
|||
<field name="domain">[('journal_id.type', '=', 'bank')]</field>
|
||||
<field name="context">{'journal_type':'bank'}</field>
|
||||
<field name="search_view_id" ref="view_bank_statement_search"/>
|
||||
<field name="help">A bank statement is a summary of all financial transactions occurring over a given period of time on a deposit account, a credit card or any other type of financial account. The starting balance will be proposed automatically and the closing balance is to be found on your statement. When you are in the Payment column of a line, you can press F1 to open the reconciliation form.</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to register a bank statement.
|
||||
</p><p>
|
||||
A bank statement is a summary of all financial transactions
|
||||
occurring over a given period of time on a bank account. You
|
||||
should receive this periodicaly from your bank.
|
||||
</p><p>
|
||||
OpenERP allows you to reconcile a statement line directly with
|
||||
the related sale or puchase invoices.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
<record model="ir.actions.act_window.view" id="action_bank_statement_tree_bank">
|
||||
<field name="sequence" eval="1"/>
|
||||
|
@ -741,7 +814,17 @@
|
|||
<field name="view_type">form</field>
|
||||
<field name="view_mode">tree,form</field>
|
||||
<field name="search_view_id" ref="view_account_type_search"/>
|
||||
<field name="help">An account type is used to determine how an account is used in each journal. The deferral method of an account type determines the process for the annual closing. Reports such as the Balance Sheet and the Profit and Loss report use the category (profit/loss or balance sheet). For example, the account type could be linked to an asset account, expense account or payable account. From this view, you can create and manage the account types you need for your company.</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to define a new account type.
|
||||
</p><p>
|
||||
An account type is used to determine how an account is used in
|
||||
each journal. The deferral method of an account type determines
|
||||
the process for the annual closing. Reports such as the Balance
|
||||
Sheet and the Profit and Loss report use the category
|
||||
(profit/loss or balance sheet).
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
<menuitem action="action_account_type_form" sequence="20" id="menu_action_account_type_form" parent="account_account_menu" groups="base.group_no_one"/>
|
||||
<!--
|
||||
|
@ -853,7 +936,16 @@
|
|||
<field name="view_mode">tree,form</field>
|
||||
<field name="view_id" ref="view_tax_code_tree"/>
|
||||
<field name="search_view_id" ref="view_tax_code_search"/>
|
||||
<field name="help">The tax code definition depends on the tax declaration of your country. OpenERP allows you to define the tax structure and manage it from this menu. You can define both numeric and alphanumeric tax codes.</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to define a new tax code.
|
||||
</p><p>
|
||||
Depending on the country, a tax code is usually a cell to fill
|
||||
in your legal tax statement. OpenERP allows you to define the
|
||||
tax structure and each tax computation will be registered in
|
||||
one or several tax code.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
<menuitem id="next_id_27" name="Taxes" parent="account.menu_finance_configuration" sequence="20"/>
|
||||
<menuitem action="action_tax_code_list" id="menu_action_tax_code_list" parent="next_id_27" sequence="12" groups="base.group_no_one"/>
|
||||
|
@ -984,7 +1076,6 @@
|
|||
<field name="domain">[('parent_id','=',False)]</field>
|
||||
<field name="view_type">tree</field>
|
||||
<field name="view_id" ref="view_tax_code_tree"/>
|
||||
<field name="help">The chart of taxes is used to generate your periodical tax statement. You will see the taxes with codes related to your legal statement according to your country.</field>
|
||||
</record>
|
||||
|
||||
<!--
|
||||
|
@ -1190,7 +1281,17 @@
|
|||
<field name="view_mode">tree,form</field>
|
||||
<field name="context">{}</field>
|
||||
<field name="search_view_id" ref="view_account_move_line_filter"/>
|
||||
<field name="help">This view can be used by accountants in order to quickly record entries in OpenERP. If you want to record a supplier invoice, start by recording the line of the expense account. OpenERP will propose to you automatically the Tax related to this account and the counterpart "Account Payable".</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to register a new journal item.
|
||||
</p><p>
|
||||
This view can be used by accountants in order to quickly record
|
||||
entries in OpenERP. If you want to record a supplier invoice,
|
||||
start by recording the line of the expense account. OpenERP
|
||||
will propose to you automatically the Tax related to this
|
||||
account and the counterpart "Account Payable".
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
<menuitem
|
||||
|
@ -1423,7 +1524,19 @@
|
|||
<field name="view_mode">tree,form,graph</field>
|
||||
<field name="view_id" ref="view_move_tree"/>
|
||||
<field name="search_view_id" ref="view_account_move_filter"/>
|
||||
<field name="help">A journal entry consists of several journal items, each of which is either a debit or a credit transaction. OpenERP automatically creates one journal entry per accounting document: invoice, refund, supplier payment, bank statements, etc.</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to create a journal entry.
|
||||
</p><p>
|
||||
A journal entry consists of several journal items, each of
|
||||
which is either a debit or a credit transaction.
|
||||
</p><p>
|
||||
OpenERP automatically creates one journal entry per accounting
|
||||
document: invoice, refund, supplier payment, bank statements,
|
||||
etc. So, you should record journal entries manually only/mainly
|
||||
for miscellaneous operations.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
<menuitem
|
||||
|
@ -1531,7 +1644,6 @@
|
|||
<field name="name">Journals</field>
|
||||
<field name="res_model">account.journal.period</field>
|
||||
<field name="view_type">tree</field>
|
||||
<field name="help">You can search for individual account entries through useful information. To search for account entries, open a journal, then select a record line.</field>
|
||||
</record>
|
||||
|
||||
<!--
|
||||
|
@ -1842,7 +1954,16 @@
|
|||
<field name="view_type">form</field>
|
||||
<field name="view_mode">tree,form</field>
|
||||
<field name="search_view_id" ref="view_subscription_search"/>
|
||||
<field name="help">A recurring entry is a miscellaneous entry that occurs on a recurrent basis from a specific date, i.e. corresponding to the signature of a contract or an agreement with a customer or a supplier. With Define Recurring Entries, you can create such entries to automate the postings in the system.</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to define a new recurring entry.
|
||||
</p><p>
|
||||
A recurring entry occurs on a recurrent basis from a specific
|
||||
date, i.e. corresponding to the signature of a contract or an
|
||||
agreement with a customer or a supplier. You can create such
|
||||
entries to automate the postings in the system.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
<menuitem
|
||||
name="Define Recurring Entries" action="action_subscription_form"
|
||||
|
@ -2621,7 +2742,17 @@ action = pool.get('res.config').next(cr, uid, [], context)
|
|||
<field name="search_view_id" ref="view_account_bank_statement_filter"/>
|
||||
<field name="domain">[('journal_id.type', '=', 'cash')]</field>
|
||||
<field name="context">{'journal_type':'cash'}</field>
|
||||
<field name="help">A Cash Register allows you to manage cash entries in your cash journals. This feature provides an easy way to follow up cash payments on a daily basis. You can enter the coins that are in your cash box, and then post entries when money comes in or goes out of the cash box.</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to create a new cash log.
|
||||
</p><p>
|
||||
A Cash Register allows you to manage cash entries in your cash
|
||||
journals. This feature provides an easy way to follow up cash
|
||||
payments on a daily basis. You can enter the coins that are in
|
||||
your cash box, and then post entries when money comes in or
|
||||
goes out of the cash box.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
<record model="ir.actions.act_window.view" id="act_cash_statement1_all">
|
||||
<field name="sequence" eval="1"/>
|
||||
|
@ -2723,7 +2854,6 @@ action = pool.get('res.config').next(cr, uid, [], context)
|
|||
<field name="view_mode">tree,form</field>
|
||||
<field name="search_view_id" ref="view_account_financial_report_search"/>
|
||||
<field name="view_id" ref="view_account_financial_report_tree"/>
|
||||
<field name="help">Makes a generic system to draw financial reports easily.</field>
|
||||
</record>
|
||||
|
||||
<menuitem id="menu_account_financial_reports_tree" name="Account Reports" parent="menu_account_reports" action="action_account_financial_report_tree"/>
|
||||
|
|
|
@ -100,7 +100,21 @@
|
|||
<field name="view_type">tree</field>
|
||||
<field name="view_id" ref="view_account_analytic_account_tree"/>
|
||||
<field name="domain">[('parent_id','=',False)]</field>
|
||||
<field name="help">The normal chart of accounts has a structure defined by the legal requirement of the country. The analytic chart of accounts structure should reflect your own business needs in term of costs/revenues reporting. They are usually structured by contracts, projects, products or departements. Most of the OpenERP operations (invoices, timesheets, expenses, etc) generate analytic entries on the related account.</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to add a new analytic account.
|
||||
</p><p>
|
||||
The normal chart of accounts has a structure defined by the
|
||||
legal requirement of the country. The analytic chart of
|
||||
accounts structure should reflect your own business needs in
|
||||
term of costs/revenues reporting.
|
||||
</p><p>
|
||||
They are usually structured by contracts, projects, products or
|
||||
departements. Most of the OpenERP operations (invoices,
|
||||
timesheets, expenses, etc) generate analytic entries on the
|
||||
related account.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
<menuitem groups="analytic.group_analytic_accounting" id="next_id_40"
|
||||
|
|
|
@ -36,7 +36,6 @@
|
|||
<field name="view_mode">tree,form</field>
|
||||
<field name="view_id" ref="view_account_chart"/>
|
||||
<field name="target">new</field>
|
||||
<field name="help">Display your company chart of accounts per fiscal year and filter by period. Have a complete tree view of all journal items per account code by clicking on an account.</field>
|
||||
</record>
|
||||
|
||||
<menuitem icon="STOCK_INDENT" action="action_account_chart"
|
||||
|
|
|
@ -26,7 +26,6 @@
|
|||
<field name="view_mode">tree,form</field>
|
||||
<field name="view_id" ref="view_account_move_bank_reconcile"/>
|
||||
<field name="target">new</field>
|
||||
<field name="help">Bank Reconciliation consists of verifying that your bank statement corresponds with the entries (or records) of that account in your accounting system.</field>
|
||||
</record>
|
||||
|
||||
</data>
|
||||
|
|
|
@ -27,7 +27,6 @@
|
|||
<field name="view_id" ref="account_partner_balance_view"/>
|
||||
<field name="context">{}</field>
|
||||
<field name="target">new</field>
|
||||
<field name="help">This report is analysis by partner. It is a PDF report containing one line per partner representing the cumulative credit balance.</field>
|
||||
</record>
|
||||
|
||||
<menuitem icon="STOCK_PRINT"
|
||||
|
|
|
@ -32,7 +32,6 @@
|
|||
<field name="view_mode">tree,form</field>
|
||||
<field name="domain">[]</field>
|
||||
<field name="view_id" ref="view_account_tax_chart"/>
|
||||
<field name="help">Chart of Taxes is a tree view reflecting the structure of the Tax Cases (or tax codes) and shows the current tax situation. The tax chart represents the amount of each area of the tax declaration for your country. It’s presented in a hierarchical structure, which can be modified to fit your needs.</field>
|
||||
<field name="target">new</field>
|
||||
</record>
|
||||
|
||||
|
|
|
@ -36,7 +36,6 @@
|
|||
<field name="view_type">form</field>
|
||||
<field name="view_mode">form</field>
|
||||
<field name="target">new</field>
|
||||
<field name="help">This menu print a tax declaration based on invoices or payments. You can select one or several periods of the fiscal year. Information required for a tax declaration is automatically generated by OpenERP from invoices (or payments, in some countries). This data is updated in real time. That’s very useful because it enables you to preview at any time the tax that you owe at the start and end of the month or quarter.</field>
|
||||
</record>
|
||||
|
||||
<menuitem
|
||||
|
|
|
@ -53,7 +53,19 @@
|
|||
<field name="context">{'search_default_user_id':uid, 'search_default_draft':1, 'search_default_pending':1, 'search_default_open':1, 'search_default_renew':1}</field>
|
||||
<field name="domain">[('type','=','contract')]</field>
|
||||
<field name="search_view_id" ref="view_account_analytic_account_overdue_search"/>
|
||||
<field name="help">You will find here the contracts to be renewed because the deadline is passed or the working hours are higher than the allocated hours. OpenERP automatically sets these analytic accounts to the pending state, in order to raise a warning during the timesheets recording. Salesmen should review all pending accounts and reopen or close the according to the negotiation with the customer.</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to define a new contract.
|
||||
</p><p>
|
||||
You will find here the contracts to be renewed because the
|
||||
end date is passed or the working effort is higher than the
|
||||
maximum authorized one.
|
||||
</p><p>
|
||||
OpenERP automatically sets contracts to be renewed in a pending
|
||||
state. After the negociation, the salesman should close or renew
|
||||
pending contracts.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
<menuitem action="action_account_analytic_overdue" id="menu_action_account_analytic_overdue" sequence="50" parent="base.menu_invoiced"/>
|
||||
|
||||
|
|
|
@ -75,7 +75,13 @@
|
|||
<field name="view_mode">tree,graph</field>
|
||||
<field name="search_view_id" ref="view_asset_asset_report_search"/>
|
||||
<field name="context">{'search_default_year':1,'search_default_this_month':1,'search_default_asset_category':1, 'search_default_posted':1, 'group_by':[], 'group_by_no_leaf':1}</field>
|
||||
<field name="help">From this report, you can have an overview on all depreciation. The tool search can also be used to personalise your Assets reports and so, match this analysis to your needs;</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
From this report, you can have an overview on all depreciation. The
|
||||
tool search can also be used to personalise your Assets reports and
|
||||
so, match this analysis to your needs;
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
<menuitem action="action_asset_asset_report"
|
||||
|
|
|
@ -27,7 +27,6 @@
|
|||
<field name="view_type">form</field>
|
||||
<field name="view_mode">tree,form</field>
|
||||
<field name="view_id" ref="view_confirm_statement_line"/>
|
||||
<field name="help">Confirm selected statement lines.</field>
|
||||
<field name="target">new</field>
|
||||
</record>
|
||||
|
||||
|
|
|
@ -218,7 +218,20 @@
|
|||
<field name="view_mode">tree,form</field>
|
||||
<field name="view_id" ref="crossovered_budget_view_tree"/>
|
||||
<field name="search_view_id" ref="view_crossovered_budget_search"/>
|
||||
<field name="help">A budget is a forecast of your company's income and expenses expected for a period in the future. With a budget, a company is able to carefully look at how much money they are taking in during a given period, and figure out the best way to divide it among various categories. By keeping track of where your money goes, you may be less likely to overspend, and more likely to meet your financial goals. Forecast a budget by detailing the expected revenue per analytic account and monitor its evolution based on the actuals realised during that period.</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
A budget is a forecast of your company's income and/or expenses
|
||||
expected for a period in the future. A budget is defined on some
|
||||
financial accounts and/or analytic accounts (that may represent
|
||||
projects, departments, categories of products, etc.)
|
||||
</p><p>
|
||||
By keeping track of where your money goes, you may be less
|
||||
likely to overspend, and more likely to meet your financial
|
||||
goals. Forecast a budget by detailing the expected revenue per
|
||||
analytic account and monitor its evolution based on the actuals
|
||||
realised during that period.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
<menuitem parent="next_id_31"
|
||||
id="menu_act_crossovered_budget_view"
|
||||
|
|
|
@ -34,7 +34,17 @@
|
|||
<field name="context">{'type':'payment','write_check':True}</field>
|
||||
<field name="search_view_id" ref="account_voucher.view_voucher_filter"/>
|
||||
<field name="target">current</field>
|
||||
<field name="help">The check payment form allows you to track the payment you do to your suppliers specially by check. When you select a supplier, the payment method and an amount for the payment, OpenERP will propose to reconcile your payment with the open supplier invoices or bills.You can print the check</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to create a new check.
|
||||
</p><p>
|
||||
The check payment form allows you to track the payment you do
|
||||
to your suppliers using checks. When you select a supplier, the
|
||||
payment method and an amount for the payment, OpenERP will
|
||||
propose to reconcile your payment with the open supplier
|
||||
invoices or bills.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
<record id="action_write_check_form" model="ir.actions.act_window.view">
|
||||
|
|
|
@ -83,7 +83,16 @@
|
|||
<field name="res_model">account_followup.followup</field>
|
||||
<field name="search_view_id" ref="view_account_followup_filter"/>
|
||||
<field name="view_type">form</field>
|
||||
<field name="help">Define follow-up levels and their related messages and delay. For each step, specify the message and the day of delay. Use the legend to know the using code to adapt the email content to the good context (good name, good date) and you can manage the multi language of messages.</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to define follow-up levels and their related messages.
|
||||
</p><p>
|
||||
For each step, specify the message and the day of delay. Use
|
||||
the legend to know the using code to adapt the email content to
|
||||
the good context (good name, good date) and you can manage the
|
||||
multi language of messages.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
<menuitem action="action_account_followup_definition_form" id="account_followup_menu" parent="account.menu_configuration_misc"/>
|
||||
|
||||
|
|
|
@ -66,7 +66,6 @@
|
|||
<field name="view_mode">tree,graph</field>
|
||||
<field name="context">{'search_default_followup_level':1}</field>
|
||||
<field name="search_view_id" ref="view_account_followup_stat_search"/>
|
||||
<field name="help">Follow-up on the reminders sent over to your partners for unpaid invoices.</field>
|
||||
</record>
|
||||
|
||||
<menuitem action="action_followup_stat" id="menu_action_followup_stat_follow" parent="account.next_id_22" groups="account.group_account_user"/>
|
||||
|
|
|
@ -234,7 +234,14 @@
|
|||
<field name="view_type">form</field>
|
||||
<field name="view_mode">tree,form</field>
|
||||
<field name="search_view_id" ref="view_payment_order_search"/>
|
||||
<field name="help">A payment order is a payment request from your company to pay a supplier invoice or a customer credit note. Here you can register all payment orders that should be done, keep track of all payment orders and mention the invoice reference and the partner the payment should be done for.</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to create a payment order.
|
||||
</p><p>
|
||||
A payment order is a payment request from your company to pay a
|
||||
supplier invoice or a customer refund.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
<menuitem action="action_payment_order_tree" id="menu_action_payment_order_form" parent="menu_main_payment" sequence="3"/>
|
||||
|
|
|
@ -83,7 +83,14 @@
|
|||
<field name="view_mode">tree,graph</field>
|
||||
<field name="context">{'search_default_year':1,'search_default_month':1,'search_default_current':1, 'search_default_partner':1, 'search_default_customer':1, 'group_by':[], 'group_by_no_leaf':1,}</field>
|
||||
<field name="search_view_id" ref="view_sale_receipt_report_search"/>
|
||||
<field name="help">From this report, you can have an overview of the amount invoiced to your customer as well as payment delays. The tool search can also be used to personalise your Invoices reports and so, match this analysis to your needs.</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
From this report, you can have an overview of the amount invoiced
|
||||
to your customer as well as payment delays. The tool search can
|
||||
also be used to personalise your Invoices reports and so, match
|
||||
this analysis to your needs.
|
||||
</p>
|
||||
</field>
|
||||
|
||||
</record>
|
||||
|
||||
|
|
|
@ -258,9 +258,14 @@
|
|||
<field name="view_id" eval="False"/>
|
||||
<field name="search_view_id" ref="view_voucher_filter_vendor_pay"/>
|
||||
<field name="target">current</field>
|
||||
<field name="help">Click on "Create" to register a supplier payment.
|
||||
<p>
|
||||
Track payments you do to your supplier and amounts you pay.</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to create a new supplier payment.
|
||||
</p><p>
|
||||
OpenERP helps you easily track payments you do and remining
|
||||
balance to pay to your supplier.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
<record id="action_vendor_payment_tree" model="ir.actions.act_window.view">
|
||||
<field eval="1" name="sequence"/>
|
||||
|
@ -422,10 +427,15 @@
|
|||
<field name="search_view_id" ref="view_voucher_filter_customer_pay"/>
|
||||
<field name="view_id" eval="False"/>
|
||||
<field name="target">current</field>
|
||||
<field name="help">
|
||||
Click on create to register a payment.
|
||||
<p>
|
||||
Enter the customer and the payment method and then, either create manually a payment record or OpenERP will propose to you automatically the reconciliation of this payment with the open invoices or sales receipts.
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to register a new payment.
|
||||
</p><p>
|
||||
Enter the customer and the payment method and then, either
|
||||
create manually a payment record or OpenERP will propose to you
|
||||
automatically the reconciliation of this payment with the open
|
||||
invoices or sales receipts.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
<record id="action_vendor_receipt_tree" model="ir.actions.act_window.view">
|
||||
|
|
|
@ -165,10 +165,13 @@
|
|||
<field name="view_id" eval="False"/>
|
||||
<field name="search_view_id" ref="view_voucher_filter_sale"/>
|
||||
<field name="target">current</field>
|
||||
<field name="help">
|
||||
Click here to create a sale receipt.
|
||||
<p>
|
||||
When the sales receipt is confirmed, you can record the customer payment related to this sales receipt.
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to create a sale receipt.
|
||||
</p><p>
|
||||
When the sale receipt is confirmed, you can record the customer
|
||||
payment related to this sales receipt.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
<record id="action_sale_receipt_tree" model="ir.actions.act_window.view">
|
||||
|
@ -315,10 +318,13 @@
|
|||
<field name="view_id" eval="False"/>
|
||||
<field name="search_view_id" eval="view_voucher_filter_vendor"/>
|
||||
<field name="target">current</field>
|
||||
<field name="help">
|
||||
Click here to create a purchase receipt.
|
||||
<p>
|
||||
When the purchase receipt is confirmed, you can record the supplier payment related to this purchase receipt.
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to register a purchase receipt.
|
||||
</p><p>
|
||||
When the purchase receipt is confirmed, you can record the
|
||||
supplier payment related to this purchase receipt.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
<record id="action_purchase_receipt_tree" model="ir.actions.act_window.view">
|
||||
|
|
|
@ -110,17 +110,27 @@
|
|||
|
||||
<!-- Action Rule Action -->
|
||||
|
||||
<record id="base_action_rule_act" model="ir.actions.act_window">
|
||||
<record id="base_action_rule_act" model="ir.actions.act_window">
|
||||
<field name="name">Automated Actions</field>
|
||||
<field name="res_model">base.action.rule</field>
|
||||
<field name="view_type">form</field>
|
||||
<field name="view_mode">tree,form</field>
|
||||
<field name="view_id" ref="view_base_action_rule_tree"/>
|
||||
<field name="help">Use automated actions to automatically trigger actions for various screens. Example: a lead created by a specific user may be automatically set to a specific sales team, or an opportunity which still has status pending after 14 days might trigger an automatic reminder email.</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to setup a new automated action rule.
|
||||
</p><p>
|
||||
Use automated actions to automatically trigger actions for
|
||||
various screens. Example: a lead created by a specific user may
|
||||
be automatically set to a specific sales team, or an
|
||||
opportunity which still has status pending after 14 days might
|
||||
trigger an automatic reminder email.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
<menuitem id="menu_base_action_rule_form"
|
||||
parent="base.menu_base_action_rule_admin" action="base_action_rule_act" sequence="1"/>
|
||||
<menuitem id="menu_base_action_rule_form"
|
||||
parent="base.menu_base_action_rule_admin" action="base_action_rule_act" sequence="1"/>
|
||||
|
||||
|
||||
</data>
|
||||
|
|
|
@ -167,7 +167,14 @@
|
|||
<field name="res_model">res.alarm</field>
|
||||
<field name="view_type">form</field>
|
||||
<field name="view_mode">tree,form</field>
|
||||
<field name="help">Create specific calendar alarms that may be assigned to calendar events or meetings.</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to setup a new alarm type.
|
||||
</p><p>
|
||||
You can define a customized type of calendar alarm that may be
|
||||
assigned to calendar events or meetings.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
<!-- Menu for Alarms-->
|
||||
|
|
|
@ -58,7 +58,6 @@
|
|||
<field name="res_model">crm.meeting.type</field>
|
||||
<field name="view_type">form</field>
|
||||
<field name="view_id" ref="view_crm_meeting_type_tree"/>
|
||||
<field name="help">Create different meeting categories to better organize and classify your meetings.</field>
|
||||
</record>
|
||||
|
||||
<menuitem id="menu_crm_meeting_type" parent="base.menu_calendar_configuration" sequence="1"
|
||||
|
@ -321,10 +320,14 @@
|
|||
<field name="view_id" ref="view_crm_meeting_calendar"/>
|
||||
<field name="search_view_id" ref="view_crm_meeting_search"/>
|
||||
<field name="context">{"calendar_default_user_id": uid}</field>
|
||||
<field name="help">
|
||||
The meeting calendar is shared between the sales teams and fully integrated with other applications
|
||||
such as the employee holidays or the business opportunities.
|
||||
You can also synchronize meetings with your mobile phone using the caldav interface.
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to schedule a new meeting.
|
||||
</p><p>
|
||||
The agenda is shared between employees and fully integrated with
|
||||
other applications such as the employee holidays or the business
|
||||
opportunities.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
<record model="ir.actions.act_window.view" id="action_view_crm_meeting_calendar">
|
||||
|
|
|
@ -24,14 +24,14 @@
|
|||
<field name="view_mode">form</field>
|
||||
<field name="usage">menu</field>
|
||||
<field name="view_id" ref="board_my_dash_view"/>
|
||||
<field name="help">
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
This is your personal dashboard.
|
||||
To customize it, go to any view in OpenERP, fill in the desired search filter,
|
||||
and click on 'Add to Dashboard' in the search options.
|
||||
The view will appear as an element in your dashboard.
|
||||
<p>
|
||||
You can drag and drop the elements to get your preferred dashboard layout.
|
||||
Click on the cross (in the upper right corner) to remove an element.
|
||||
</p><p>
|
||||
To customize it, go to any OpenERP screen, fill in the search
|
||||
filter, and click on <i>'Add to Dashboard'</i> in the advanced
|
||||
search options.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
|
|
|
@ -178,7 +178,6 @@
|
|||
<field name="res_model">basic.calendar</field>
|
||||
<field name="view_type">form</field>
|
||||
<field name="view_mode">tree,form</field>
|
||||
<field name="help">"Calendars" allow you to Customize calendar event and todo attribute with any of OpenERP model.Caledars provide iCal Import/Export functionality.Webdav server that provides remote access to calendar.Help You to synchronize Meeting with Calendars client.You can access Calendars using CalDAV clients, like sunbird, Calendar Evaluation, Mobile.</field>
|
||||
</record>
|
||||
|
||||
<record id="action_caldav_view1" model="ir.actions.act_window.view">
|
||||
|
|
|
@ -10,13 +10,17 @@
|
|||
<field name="view_id" ref="crm_case_tree_view_leads"/>
|
||||
<field name="search_view_id" ref="crm.view_crm_case_leads_filter"/>
|
||||
<field name="context">{'default_type':'lead', 'stage_type':'lead'}</field>
|
||||
<field name="help">
|
||||
<img src="http://www.thaicrmsoftware.com/wp-content/uploads/2011/11/lead-conversion.jpg" align="right" style="padding: 6px" width="306" height="223">
|
||||
<h2>Click here to create a Lead. </h2>
|
||||
<p>
|
||||
A lead is usually the first step in your sales cycle.
|
||||
<p>
|
||||
Once qualified, a lead may be converted into a business opportunity, while creating the related partner for further detailed tracking of any linked activities.
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to create an unqualified lead.
|
||||
</p><p>
|
||||
A lead is usually the first step in your sales cycle. It can be
|
||||
a contact with a new prospect, a company you target, a contact form
|
||||
filled in your website, etc.
|
||||
</p><p>
|
||||
Once qualified, the lead can be converted into a business
|
||||
opportunity and a new customer in your address book.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
|
@ -42,9 +46,18 @@
|
|||
<field name="context">{'stage_type': 'opportunity', 'default_type': 'opportunity'}</field>
|
||||
<field name="view_id" eval="False"/>
|
||||
<field name="search_view_id" ref="crm.view_crm_case_opportunities_filter"/>
|
||||
<field name="help">With opportunities you can manage and keep track of your sales pipeline by creating specific customer- or prospect-related sales documents to follow up potential sales. Information such as expected revenue, opportunity stage, expected closing date, communication history and much more can be stored. Opportunities can be connected to the email gateway: new emails may create opportunities, each of them automatically gets the history of the conversation with the customer.
|
||||
|
||||
You and your team(s) will be able to plan meetings and phone calls from opportunities, convert them into quotations, manage related documents, track all customer related activities, and much more.</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to create a new opportunity.
|
||||
</p><p>
|
||||
OpenERP helps you keep track of your sales pipeline to follow
|
||||
up potential sales and better forecast your future revenues.
|
||||
</p><p>
|
||||
You will be able to plan meetings and phone calls from
|
||||
opportunities, convert them into quotations, attach related
|
||||
documents, track all discussions, and much more.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
<record model="ir.actions.act_window.view" id="action_crm_tag_kanban_view_oppor11">
|
||||
|
|
|
@ -63,7 +63,14 @@
|
|||
<field name="res_model">crm.case.stage</field>
|
||||
<field name="view_type">form</field>
|
||||
<field name="view_id" ref="crm.crm_case_stage_tree"/>
|
||||
<field name="help">Add specific stages to leads and opportunities allowing your sales to better organise their sales pipeline. Stages will allow them to easily track how a specific lead or opportunity is positioned in the sales cycle.</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to set a new stage in your lead/opportunity pipeline.
|
||||
</p><p>
|
||||
Stages will allow salespersons to easily track how a specific
|
||||
lead or opportunity is positioned in the sales cycle.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
<menuitem action="crm_lead_stage_act" id="menu_crm_lead_stage_act" name="Stages" sequence="0" parent="base.menu_crm_config_lead" groups="base.group_no_one"/>
|
||||
|
@ -74,13 +81,22 @@
|
|||
|
||||
<!-- Categories Form View -->
|
||||
<record id="crm_lead_categ_action" model="ir.actions.act_window">
|
||||
<field name="name">Categories</field>
|
||||
<field name="name">Sales Tags</field>
|
||||
<field name="res_model">crm.case.categ</field>
|
||||
<field name="view_type">form</field>
|
||||
<field name="view_id" ref="crm_case_categ_tree-view"/>
|
||||
<field name="context" eval="{'object_id': ref('model_crm_lead')}"/>
|
||||
<field name="domain">[('object_id.model', '=', 'crm.lead')]</field>
|
||||
<field name="help">Create specific categories that fit your company's activities to better classify and analyse your leads and opportunities. Such categories could for instance reflect your product structure or the different types of sales you do.</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to define a new sales tag.
|
||||
</p><p>
|
||||
Create specific tags that fit your company's activities
|
||||
to better classify and analyse your leads and opportunities.
|
||||
Such categories could for instance reflect your product
|
||||
structure or the different types of sales you do.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
<menuitem action="crm_lead_categ_action"
|
||||
|
|
|
@ -68,14 +68,18 @@
|
|||
<field name="domain">[]</field>
|
||||
<field name="context">{}</field>
|
||||
<field name="search_view_id" ref="crm.view_crm_case_phonecalls_filter"/>
|
||||
<field name="help">
|
||||
Click on "Create" to log a new call.
|
||||
<p>
|
||||
This tool allows you to log your calls on the fly.
|
||||
<p>
|
||||
From this feature, you can trigger a request for another call, a meeting or an opportunity.
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to log the summary of a phone call.
|
||||
</p><p>
|
||||
OpenERP allows you to log inbound calls on the fly to track the
|
||||
history of the communication with a customer or to inform another
|
||||
team member.
|
||||
</p><p>
|
||||
In order to follow up on the call, you can trigger a request for
|
||||
another call, a meeting or an opportunity.
|
||||
</p>
|
||||
</field>
|
||||
|
||||
</record>
|
||||
|
||||
<record model="ir.actions.act_window.view" id="action_crm_tag_tree_phone_incoming0">
|
||||
|
@ -112,12 +116,16 @@
|
|||
<field name="domain">[('state','!=','done')]</field>
|
||||
<field name="context" eval="'{\'default_state\':\'open\'}'"/>
|
||||
<field name="search_view_id" ref="crm.view_crm_case_phonecalls_filter"/>
|
||||
<field name="help">
|
||||
Click here to schedule a new call.
|
||||
<p>
|
||||
Scheduled calls list all the calls to be done by your sales team.
|
||||
<p>
|
||||
This information will be stored in the partner form to trace every contact you have with a customer.
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to schedule a call
|
||||
</p><p>
|
||||
OpenERP allows you to easily define all the calls to be done
|
||||
by your sales team and follow up based on their summary.
|
||||
</p><p>
|
||||
You can use the import feature to massicely import a new list of
|
||||
prospects to qualify.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
|
|
|
@ -47,7 +47,14 @@
|
|||
<field name="view_id" ref="crm.crm_case_categ_tree-view"/>
|
||||
<field name="domain">[('object_id.model', '=', 'crm.phonecall')]</field>
|
||||
<field name="context" eval="{'object_id': ref('model_crm_phonecall')}"/>
|
||||
<field name="help">Create specific phone call categories to better define the type of calls tracked in the system.</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to add a new category.
|
||||
</p><p>
|
||||
Create specific phone call categories to better define the type of
|
||||
calls tracked in the system.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
<menuitem action="crm_phonecall_categ_action" name="Categories"
|
||||
|
|
|
@ -59,7 +59,18 @@
|
|||
<field name="res_model">crm.case.channel</field>
|
||||
<field name="view_type">form</field>
|
||||
<field name="view_mode">tree,form</field>
|
||||
<field name="help">Track from where is coming your leads and opportunities by creating specific channels that will be maintained at the creation of a document in the system. Some examples of channels can be: Website, Phone Call, Reseller, etc.</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to define a new channel.
|
||||
</p><p>
|
||||
Use channels to track the soure of your leads and opportunities. Channels
|
||||
are mostly used in reporting to analyse sales performance
|
||||
related to marketing efforts.
|
||||
</p><p>
|
||||
Some examples of channels: company website, phone call
|
||||
campaign, reseller, etc.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
<menuitem action="crm_case_channel_action" id="menu_crm_case_channel" parent="base.menu_crm_config_lead" sequence="4" groups="base.group_no_one"/>
|
||||
|
@ -133,7 +144,15 @@
|
|||
<field name="res_model">crm.case.section</field>
|
||||
<field name="view_type">form</field>
|
||||
<field name="view_id" ref="crm_case_section_view_tree"/>
|
||||
<field name="help">Define a Sales Team to organize your different salesmen or sales departments into separate teams. Each team will work in its own list of opportunities, sales orders, etc. Each user can set a default team in his user preferences. The opportunities and sales order displayed, will automatically be filtered according to his team.</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to define a new sales team.
|
||||
</p><p>
|
||||
Use sales team to organize your different salespersons or
|
||||
departments into separate teams. Each team will work in
|
||||
its own list of opportunities.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
<menuitem action="crm_case_section_act"
|
||||
|
@ -380,11 +399,20 @@
|
|||
</record>
|
||||
|
||||
<record id="crm_segmentation_tree-act" model="ir.actions.act_window">
|
||||
<field name="name">Partners Segmentation</field>
|
||||
<field name="name">Contacts Segmentation</field>
|
||||
<field name="res_model">crm.segmentation</field>
|
||||
<field name="view_type">form</field>
|
||||
<field name="view_mode">tree,form</field>
|
||||
<field name="help">Create specific partner categories which you can assign to your partners to better manage your interactions with them. The segmentation tool is able to assign categories to partners according to criteria you set.</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to define a new customer segmentation.
|
||||
</p><p>
|
||||
Create specific categories which you can assign to your
|
||||
contacts to better manage your interactions with them. The
|
||||
segmentation tool is able to assign categories to contacts
|
||||
according to criteria you set.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
<menuitem action="crm_segmentation_tree-act"
|
||||
|
|
|
@ -70,10 +70,17 @@
|
|||
'stage_type': 'opportunity', 'default_type': 'opportunity'}</field>
|
||||
<field name="view_id" eval="False"/>
|
||||
<field name="search_view_id" ref="crm.view_crm_case_opportunities_filter"/>
|
||||
<field name="help">
|
||||
With opportunities you can manage and keep track of your sales pipeline by creating specific customer- or prospect-related sales documents to follow up potential sales. Information such as expected revenue, opportunity stage, expected closing date, communication history and much more can be stored. Opportunities can be connected to the email gateway: new emails may create opportunities, each of them automatically gets the history of the conversation with the customer.
|
||||
|
||||
You and your team(s) will be able to plan meetings and phone calls from opportunities, convert them into quotations, manage related documents, track all customer related activities, and much more.
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to create an opportunity related to this customer.
|
||||
</p><p>
|
||||
Use opportunities to keep track of your sales pipeline, follow
|
||||
up potential sales and better forecast your future revenues.
|
||||
</p><p>
|
||||
You will be able to plan meetings and phone calls from
|
||||
opportunities, convert them into quotations, attach related
|
||||
documents, track all discussions, and much more.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
<record model="ir.actions.act_window.view" id="relate_partner_opportunities_kanban">
|
||||
|
|
|
@ -15,7 +15,15 @@
|
|||
<field name="view_id" ref="crm.crm_case_categ_tree-view"/>
|
||||
<field name="domain">[('object_id.model', '=', 'crm.claim')]</field>
|
||||
<field name="context" eval="{'object_id': ref('model_crm_claim')}"/>
|
||||
<field name="help">Create claim categories to better manage and classify your claims. Some example of claims can be: preventive action, corrective action.</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to create a claim category.
|
||||
</p><p>
|
||||
Create claim categories to better manage and classify your
|
||||
claims. Some example of claims can be: preventive action,
|
||||
corrective action.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
<menuitem action="crm_claim_categ_action" name="Categories"
|
||||
|
@ -57,7 +65,15 @@
|
|||
<field name="res_model">crm.claim.stage</field>
|
||||
<field name="view_type">form</field>
|
||||
<field name="view_id" ref="crm_claim_stage_tree"/>
|
||||
<field name="help">You can create claim stages to categorize the status of every claim entered in the system. The stages define all the steps required for the resolution of a claim.</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to setup a new stage in the processing of the claims.
|
||||
</p><p>
|
||||
You can create claim stages to categorize the status of every
|
||||
claim entered in the system. The stages define all the steps
|
||||
required for the resolution of a claim.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
<!-- Claims -->
|
||||
|
|
|
@ -18,7 +18,18 @@
|
|||
<field name="view_id" ref="crm_case_tree_view_helpdesk"/>
|
||||
<field name="search_view_id" ref="view_crm_case_helpdesk_filter"/>
|
||||
<field name="context">{"search_default_user_id":uid}</field>
|
||||
<field name="help">Helpdesk and Support allow you to track your interventions. Select a customer, add notes and categorize interventions with partners if necessary. You can also assign a priority level. Use the OpenERP Issues system to manage your support activities. Issues can be connected to the email gateway: new emails may create issues, each of them automatically gets the history of the conversation with the customer.</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to create a new request.
|
||||
</p><p>
|
||||
Helpdesk and Support allow you to track your interventions.
|
||||
</p><p>
|
||||
Use the OpenERP Issues system to manage your support
|
||||
activities. Issues can be connected to the email gateway: new
|
||||
emails may create issues, each of them automatically gets the
|
||||
history of the conversation with the customer.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
<record model="ir.actions.act_window.view" id="action_crm_sec_tree_view_act111">
|
||||
|
|
|
@ -97,7 +97,19 @@
|
|||
<field name="res_model">delivery.carrier</field>
|
||||
<field name="view_type">form</field>
|
||||
<field name="view_mode">tree,form</field>
|
||||
<field name="help">Define the delivery methods you are using and their pricing in order to reinvoice the delivery costs when you are doing invoicing based on delivery orders</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to define a new deliver method.
|
||||
</p><p>
|
||||
Each carrier (e.g. UPS) can have several delivery methods (e.g.
|
||||
UPS Express, UPS Standard) with a set of pricing rules attached
|
||||
to each method.
|
||||
</p><p>
|
||||
These methods allows to automaticaly compute the delivery price
|
||||
according to your settings; on the sale order (based on the
|
||||
quotation) or the invoice (based on the delivery orders).
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
<menuitem action="action_delivery_carrier_form" id="menu_action_delivery_carrier_form" parent="stock.menu_stock_configuration" sequence="15"/>
|
||||
|
@ -152,7 +164,17 @@
|
|||
<field name="res_model">delivery.grid</field>
|
||||
<field name="view_type">form</field>
|
||||
<field name="view_mode">tree,form</field>
|
||||
<field name="help">The delivery price list allows you to compute the cost and sales price of the delivery according to the weight of the products and other criteria. You can define several price lists for one delivery method, per country or a zone in a specific country defined by a postal code range.</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to create a delivery price list for a specific region.
|
||||
</p><p>
|
||||
The delivery price list allows you to compute the cost and
|
||||
sales price of the delivery according to the weight of the
|
||||
products and other criteria. You can define several price lists
|
||||
for each delivery method: per country or a zone in a specific
|
||||
country defined by a postal code range.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
<menuitem action="action_delivery_grid_form" id="menu_action_delivery_grid_form" parent="menu_delivery"/>
|
||||
|
||||
|
|
|
@ -315,7 +315,14 @@
|
|||
<field name="type">ir.actions.act_window</field>
|
||||
<field name="res_model">ir.attachment</field>
|
||||
<field name="view_type">form</field>
|
||||
<field name="help">The Documents repository gives you access to all attachments, such as mails, project documents, invoices etc.</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to create a new document.
|
||||
</p><p>
|
||||
The Documents repository gives you access to all attachments, such
|
||||
as mails, project documents, invoices etc.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
<menuitem name="Documents" id="menu_document_doc" parent="knowledge.menu_document" sequence="0"/>
|
||||
<menuitem
|
||||
|
|
|
@ -363,7 +363,15 @@
|
|||
<field name="view_mode">kanban,calendar,tree,form,graph</field>
|
||||
<field name="context">{"search_default_upcoming":1}</field>
|
||||
<field name="search_view_id" ref="view_event_search"/>
|
||||
<field name="help">Event is the low level object used by meeting and others documents that should be synchronized with mobile devices or calendar applications through caldav. Most of the users should work in the Calendar menu, and not in the list of events.</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to add a new event.
|
||||
</p><p>
|
||||
OpenERP helps you schedule and efficiently organize your events:
|
||||
track subscriptions and participations, automate the confirmation emails,
|
||||
sell tickets, etc.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
<act_window
|
||||
|
|
|
@ -50,7 +50,15 @@
|
|||
<field name="res_model">hr.department</field>
|
||||
<field name="view_type">form</field>
|
||||
<field name="search_view_id" ref="view_department_filter"/>
|
||||
<field name="help">Your Company's Department Structure is used to manage all documents related to employees by departments: expenses and timesheet validation, leaves management, recruitments, etc.</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to create a department.
|
||||
</p><p>
|
||||
OpenERP's department structure is used to manage all documents
|
||||
related to employees by departments: expenses, timesheets,
|
||||
leaves and holidays, recruitments, etc.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
<menuitem action="open_module_tree_department" id="menu_hr_department_tree" parent="hr.menu_hr_configuration" sequence="5"/>
|
||||
|
|
|
@ -13,7 +13,15 @@
|
|||
<field name="view_type">form</field>
|
||||
<field name="view_mode">tree,form</field>
|
||||
<field name="view_id" ref="hr.view_department_tree"/>
|
||||
<field name="help">Your departments structure is used to manage all documents related to employees by departments: expenses and timesheet validation, leaves management, recruitments, etc.</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to define a new department.
|
||||
</p><p>
|
||||
Your departments structure is used to manage all documents
|
||||
related to employees by departments: expenses and timesheets,
|
||||
leaves and holidays, recruitments, etc.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
</data>
|
||||
|
|
|
@ -193,7 +193,15 @@
|
|||
<field name="context">{}</field>
|
||||
<field name="view_id" eval="False"/>
|
||||
<field name="search_view_id" ref="view_employee_filter"/>
|
||||
<field name="help">Here you can manage your work force by creating employees and assigning them specific properties in the system. Maintain all employee related information and keep track of anything that needs to be recorded for them. The personal information tab will help you maintain their identity data. The Categories tab gives you the opportunity to assign them related employee categories depending on their position and activities within the company. A category can be a seniority level within the company or a department. The Timesheets tab allows to assign them a specific timesheet and analytic journal where they will be able to enter time through the system. In the note tab, you can enter text data that should be recorded for a specific employee.</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to add a new employee.
|
||||
</p><p>
|
||||
With just a quick glance on the OpenERP employee screen, you
|
||||
can easily find all the information you need for each person;
|
||||
contact data, job position, availability, etc.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
<record id="open_view_employee_list_my_kanban" model="ir.actions.act_window.view">
|
||||
|
@ -443,7 +451,20 @@
|
|||
<field name="view_mode">tree,form</field>
|
||||
<field name="search_view_id" ref="view_job_filter"/>
|
||||
<field name="context">{"search_default_Current":1}</field>
|
||||
<field name="help">Job Positions are used to define jobs and their requirements. You can keep track of the number of employees you have per job position and how many you expect in the future. You can also attach a survey to a job position that will be used in the recruitment process to evaluate the applicants for this job position.</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to define a new job position.
|
||||
</p><p>
|
||||
Job Positions are used to define jobs and their requirements.
|
||||
You can keep track of the number of employees you have per job
|
||||
position and follow the evolution according to what you planned
|
||||
for the future.
|
||||
</p><p>
|
||||
You can attach a survey to a job position. It will be used in
|
||||
the recruitment process to evaluate the applicants for this job
|
||||
position.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
<menuitem name="Recruitment" id="base.menu_crm_case_job_req_main" parent="menu_hr_root" groups="base.group_hr_user"/>
|
||||
|
|
|
@ -7,7 +7,16 @@
|
|||
<field name="res_model">hr_evaluation.plan</field>
|
||||
<field name="view_type">form</field>
|
||||
<field name="view_mode">tree,form</field>
|
||||
<field name="help">You can define appraisal plans (ex: first interview after 6 months, then every year). Then, each employee can be linked to an appraisal plan so that OpenERP can automatically generate interview requests to managers and/or subordinates.</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to define a new appraisal plan.
|
||||
</p><p>
|
||||
You can define appraisal plans (ex: first interview after 6
|
||||
months, then every year). Then, each employee can be linked to
|
||||
an appraisal plan so that OpenERP can automatically generate
|
||||
interview requests to managers and/or subordinates.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
</data>
|
||||
|
|
|
@ -252,7 +252,18 @@
|
|||
<field name="view_mode">tree,form,graph</field>
|
||||
<field name="search_view_id" ref="hr_evaluation.evaluation_search"/>
|
||||
<field name="context">{"search_default_next_month":1}</field>
|
||||
<field name="help">Each employee may be assigned an Appraisal Plan. Such a plan defines the frequency and the way you manage your periodic personnel evaluation. You will be able to define steps and attach interviews to each step. OpenERP manages all kind of evaluations: bottom-up, top-down, self-evaluation and final evaluation by the manager.</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to create a new appraisal.
|
||||
</p><p>
|
||||
Each employee may be assigned an Appraisal Plan. Such a plan
|
||||
defines the frequency and the way you manage your periodic
|
||||
personnel evaluation. You will be able to define steps and
|
||||
attach interviews to each step. OpenERP manages all kind of
|
||||
evaluations: bottom-up, top-down, self-evaluation and final
|
||||
evaluation by the manager.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
<menuitem name="Appraisals" parent="menu_eval_hr" id="menu_open_view_hr_evaluation_tree"
|
||||
|
@ -350,7 +361,16 @@
|
|||
<field name="domain">[('is_evaluation' ,'=', True)]</field>
|
||||
<field name="context">{'default_is_evaluation': True, "search_default_todo":1,"search_default_user_id":uid}</field>
|
||||
<field name="search_view_id" ref="view_hr_evaluation_interview_search"/>
|
||||
<field name="help">Interview Requests are generated automatically by OpenERP according to an employee's Appraisal Plan. Each user receives automatic emails and requests to evaluate their colleagues periodically.</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to create a new interview request related to a personnal evaluation.
|
||||
</p><p>
|
||||
Interview requests are usually generated automatically by
|
||||
OpenERP according to an employee's appraisal plan. Each user
|
||||
receives automatic emails and requests to evaluate their
|
||||
colleagues periodically.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
<record model="ir.actions.act_window.view" id="hr_evaluation_interview_tree">
|
||||
|
|
|
@ -159,10 +159,15 @@
|
|||
<field name="view_type">form</field>
|
||||
<field name="search_view_id" ref="view_hr_expense_filter"/>
|
||||
<field name="view_id" ref="view_expenses_tree"/>
|
||||
<field name="help">
|
||||
Click here to create a new expense.
|
||||
<p>
|
||||
After validation of your expense, you will be able to re-invoice costs to your customers.
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to register new expenses.
|
||||
</p><p>
|
||||
OpenERP will ensure the whole process is followed; the expense
|
||||
sheet is validated by manager(s), the employee is reimbursed
|
||||
from his expenses, some expenses must be re-invoiced to the
|
||||
customers.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
|
|
|
@ -301,7 +301,16 @@
|
|||
<field name="context">{}</field>
|
||||
<field name="domain">[('type','=','remove')]</field>
|
||||
<field name="search_view_id" ref="view_hr_holidays_filter"/>
|
||||
<field name="help">Leave requests can be recorded by employees and validated by their managers. Once a leave request is validated, it appears automatically in the agenda of the employee. You can define several allowance types (paid holidays, sickness, etc.) and manage allowances per type.</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to create a new leave request.
|
||||
</p><p>
|
||||
Once you have recorded your leave request, it will be sent
|
||||
to a manager for validation. Be sure to set the right leave
|
||||
type (recuperation, legal holidays, sickness) and the exact
|
||||
number of open days related to your leave.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
<record model="ir.actions.act_window.view" id="action_open_ask_holidays_tree">
|
||||
|
@ -521,7 +530,12 @@
|
|||
<field name="view_type">form</field>
|
||||
<field name="view_mode">tree,form</field>
|
||||
<field name="view_id" ref="hr_holidays_leaves_assign_tree_view"/>
|
||||
<field name="help">You can assign remaining Legal Leaves for each employee, OpenERP will automatically create and validate allocation requests.</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
You can assign remaining Legal Leaves for each employee, OpenERP
|
||||
will automatically create and validate allocation requests.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
<!-- Hr employee inherit Legal Leaves -->
|
||||
|
|
|
@ -529,7 +529,15 @@
|
|||
<field name="name">Contribution Registers</field>
|
||||
<field name="res_model">hr.contribution.register</field>
|
||||
<field name="view_type">form</field>
|
||||
<field name="help">A contribution register is a third party involved in the salary payment of the employees. It can be the social security, the estate or anyone that collect or inject money on payslips.</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to add a new contribution register.
|
||||
</p><p>
|
||||
A contribution register is a third party involved in the salary
|
||||
payment of the employees. It can be the social security, the
|
||||
estate or anyone that collect or inject money on payslips.
|
||||
</p>
|
||||
</field>
|
||||
<field name="view_id" ref="hr_contribution_register_tree"/>
|
||||
</record>
|
||||
<menuitem
|
||||
|
|
|
@ -9,7 +9,20 @@
|
|||
<field name="view_mode">kanban,tree,form,graph,calendar</field>
|
||||
<field name="view_id" eval="False"/>
|
||||
<field name="search_view_id" ref="view_crm_case_jobs_filter"/>
|
||||
<field name="help">From this menu you can track applicants in the recruitment process and manage all operations: meetings, interviews, phone calls, etc. If you setup the email gateway, applicants and their attached CV are created automatically when an email is sent to jobs@yourcompany.com. If you install the document management modules, all documents (CV and motivation letters) are indexed automatically, so that you can easily search through their content.</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to add a new job applicant.
|
||||
</p><p>
|
||||
OpenERP helps you track applicants in the recruitment
|
||||
process and follow up all operations: meetings, interviews, etc.
|
||||
</p><p>
|
||||
If you setup the email gateway, applicants and their attached
|
||||
CV are created automatically when an email is sent to
|
||||
jobs@yourcompany.com. If you install the document management
|
||||
modules, all resumes are indexed automatically, so that you can
|
||||
easily search through their content.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
<record model="ir.actions.act_window.view" id="action_hr_sec_kanban_view_act_job">
|
||||
|
|
|
@ -22,7 +22,15 @@
|
|||
<field name="view_type">form</field>
|
||||
<field name="domain">[]</field>
|
||||
<field name="context">{}</field>
|
||||
<field name="help">Define here your stages of the recruitment process, for example: qualification call, first interview, second interview, refused, hired.</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to add a new stage in the recruitment process.
|
||||
</p><p>
|
||||
Define here your stages of the recruitment process, for example:
|
||||
qualification call, first interview, second interview, refused,
|
||||
hired.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
|
||||
|
@ -383,7 +391,14 @@
|
|||
<field name="res_model">hr.recruitment.stage</field>
|
||||
<field name="view_type">form</field>
|
||||
<field name="view_id" ref="hr_recruitment_stage_tree"/>
|
||||
<field name="help"> Check if the following stages are matching your recruitment process. Don't forget to specify the department if your recruitment process is different according to the job position.</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to add a new stage in the recruitment process.
|
||||
</p><p>
|
||||
Don't forget to specify the department if your recruitment process
|
||||
is different according to the job position.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
<menuitem
|
||||
|
|
|
@ -104,7 +104,14 @@
|
|||
<field name="view_mode">tree,form</field>
|
||||
<field name="context">{"search_default_today":1}</field>
|
||||
<field name="search_view_id" ref="hr_timesheet_line_search"/>
|
||||
<field name="help">Through this menu you can register and follow your workings hours by project every day.</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to your timesheets.
|
||||
</p><p>
|
||||
Through this menu you can register and follow your workings
|
||||
hours by project every day.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
<menuitem id="menu_hr_working_hours" parent="hr_attendance.menu_hr_time_tracking" action="act_hr_timesheet_line_evry1_all_form"/>
|
||||
|
|
|
@ -130,7 +130,15 @@
|
|||
<field name="domain">[]</field>
|
||||
<field name="context">{'search_default_to_invoice': 1}</field>
|
||||
<field name="search_view_id" ref="account.view_account_analytic_line_filter"/>
|
||||
<field name="help">This list shows you every task you can invoice to the customer. Select the lines and click the Action button to generate the invoices automatically.</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to add some tasks work to be invoiced.
|
||||
</p><p>
|
||||
This list shows every task you can invoice to the customer.
|
||||
Select the lines and invoice from the '<i>more...</i>' contextual
|
||||
menu to generate invoices automatically.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
<menuitem
|
||||
action="action_hr_analytic_timesheet_open_tree"
|
||||
|
@ -181,7 +189,17 @@
|
|||
<field name="view_type">form</field>
|
||||
<field name="view_id" ref="view_hr_timesheet_invoice_factor_tree"/>
|
||||
<field name="search_view_id" ref="view_hr_timesheet_invoice_factor_search"/>
|
||||
<field name="help">OpenERP allows you to create default invoicing types. You might have to regularly assign discounts because of a specific contract or agreement with a customer. From this menu, you can create additional types of invoicing to speed up your invoicing.</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to add a new type of invoicing.
|
||||
</p><p>
|
||||
OpenERP allows you to create default invoicing types. You might
|
||||
have to regularly assign discounts because of a specific
|
||||
contract or agreement with a customer. From this menu, you can
|
||||
create additional types of invoicing to speed up your
|
||||
invoicing.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
<menuitem
|
||||
action="action_hr_timesheet_invoice_factor_form"
|
||||
|
|
|
@ -177,7 +177,18 @@
|
|||
<field name="view_id" eval="False"/>
|
||||
<field name="context">{'search_default_my_timesheet':1}</field>
|
||||
<field name="search_view_id" ref="view_hr_timesheet_sheet_filter"/>
|
||||
<field name="help">Check your timesheets for a specific period. You can also encode time spent on a project (i.e. an analytic account) thus generating costs in the analytic account concerned.</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to go to your timesheet.
|
||||
</p><p>
|
||||
You must record timesheets every day and confirm at the end
|
||||
of the week. Once the timesheet is confirmed, it his sent to
|
||||
the manager for validation.
|
||||
</p><p>
|
||||
Timesheets can also be invoiced to customers, depending on the
|
||||
configuration of the project.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
<menuitem action="act_hr_timesheet_sheet_form" id="menu_act_hr_timesheet_sheet_form" parent="hr_attendance.menu_hr_time_tracking"
|
||||
|
|
|
@ -69,7 +69,14 @@
|
|||
<field name="view_type">form</field>
|
||||
<field name="view_mode">tree,graph</field>
|
||||
<field name="context">{'search_default_year':1,'search_default_month':1,'search_default_group_user_id':1,'group_by_no_leaf':1,'group_by':[]}</field>
|
||||
<field name="help">This report performs analysis on timesheets created by your human resources in the system. It allows you to have a full overview of entries done by your employees. You can group them by specific selection criteria thanks to the search tool.</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
This report performs analysis on timesheets created by your
|
||||
human resources in the system. It allows you to have a full
|
||||
overview of entries done by your employees. You can group them
|
||||
by specific selection criteria thanks to the search tool.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
<menuitem
|
||||
action="action_hr_timesheet_report_stat_all"
|
||||
|
|
|
@ -7,7 +7,19 @@
|
|||
<field name="view_type">form</field>
|
||||
<field name="view_mode">tree,form</field>
|
||||
<field name="view_id" eval="False"/>
|
||||
<field name="help">Define all products that the employees can order for the lunch time. If you order lunch at several places, you can use the product categories to split by supplier. It will be easier for the lunch manager to filter lunch orders by categories.</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to add a new product that can be ordered for the lunch.
|
||||
</p><p>
|
||||
We suggest you to put the real price so that the exact due
|
||||
amount is deduced from each employee's cash boxes when they
|
||||
order.
|
||||
</p><p>
|
||||
If you order lunch at several places, you can use the product
|
||||
categories to split by supplier. It will be easier to filter
|
||||
lunch orders.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
<record id="view_lunch_product_form_todo" model="ir.actions.todo">
|
||||
|
@ -22,7 +34,15 @@
|
|||
<field name="res_model">lunch.cashbox</field>
|
||||
<field name="view_type">form</field>
|
||||
<field name="view_mode">tree,form</field>
|
||||
<field name="help">You can create on cashbox by employee if you want to keep track of the amount due by employee according to what have been ordered.</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to add a new cash box.
|
||||
</p><p>
|
||||
You can create on cash box by employee if you want to keep
|
||||
track of the amount due by employee according to what have been
|
||||
ordered.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
<record id="action_create_cashbox_todo" model="ir.actions.todo">
|
||||
|
|
|
@ -133,7 +133,20 @@
|
|||
<field name="view_id" ref="view_marketing_campaign_tree"/>
|
||||
<field name="context">{'group_by': []}</field>
|
||||
<field name="search_view_id" ref="view_marketing_campaign_search"/>
|
||||
<field name="help">A marketing campaign is an event or activity that will help you manage and reach your partners with specific messages. A campaign can have many activities that will be triggered from a specific situation. One action could be sending an email template that has previously been created in the system.</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to create a marketing campaign.
|
||||
</p><p>
|
||||
OpenERP's marketing campaign allows you to automate communication
|
||||
to your prospects. You can define a segment (set of conditions) on
|
||||
your leads and partners to fullfil the campaign.
|
||||
</p><p>
|
||||
A campaign can have many activities like sending an email, printing
|
||||
a letter, assigning to a team, etc. These activities are triggered
|
||||
from specific situations; contact form, 10 days after first
|
||||
contact, if a lead is not closed yet, etc.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
<menuitem name="Campaigns" id="menu_marketing_campaign" parent="base.marketing_menu"/>
|
||||
|
|
|
@ -41,8 +41,20 @@
|
|||
<field name="res_model">mrp.property.group</field>
|
||||
<field name="view_type">form</field>
|
||||
<field name="view_mode">tree,form</field>
|
||||
<field name="help">
|
||||
Define specific property groups that can be assigned to the properties of your bill of materials.
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to create a group of properties.
|
||||
</p><p>
|
||||
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.
|
||||
</p><p>
|
||||
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
|
||||
schedule a production using the matching bill of materials.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
<menuitem
|
||||
|
@ -105,12 +117,18 @@
|
|||
<field name="view_type">form</field>
|
||||
<field name="view_mode">tree,form</field>
|
||||
<field name="search_view_id" ref="view_mrp_property_search"/>
|
||||
<field name="help">
|
||||
The Properties in OpenERP are used to select the right bill of 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
|
||||
and OpenERP will automatically select the BoM to use according the needs.
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to create a new property.
|
||||
</p><p>
|
||||
The Properties in OpenERP are used to select the right bill of
|
||||
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
|
||||
and OpenERP will automatically select the BoM to use according
|
||||
the needs.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
<menuitem name="Master Bill of Materials"
|
||||
|
@ -317,10 +335,15 @@
|
|||
<field name="view_type">form</field>
|
||||
<field name="view_id" ref="mrp_routing_tree_view"/>
|
||||
<field name="search_view_id" ref="mrp_routing_search_view"/>
|
||||
<field name="help">
|
||||
Routings allow you to create and manage the manufacturing operations that should be
|
||||
followed within your work centers in order to produce a product.
|
||||
They are attached to bills of materials that will define the required raw materials.
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to create a routing.
|
||||
</p><p>
|
||||
Routings allow you to create and manage the manufacturing
|
||||
operations that should be followed within your work centers in
|
||||
order to produce a product. They are attached to bills of
|
||||
materials that will define the required raw materials.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
<menuitem action="mrp_routing_action" id="menu_mrp_routing_action" parent="mrp.menu_mrp_bom" groups="mrp.group_mrp_routings" sequence="15"/>
|
||||
|
@ -471,12 +494,17 @@
|
|||
<field name="view_type">form</field>
|
||||
<field name="domain">[('bom_id','=',False)]</field>
|
||||
<field name="search_view_id" ref="view_mrp_bom_filter"/>
|
||||
<field name="help">
|
||||
Master Bills of Materials allow you to create and manage the list of necessary
|
||||
raw materials used to make a finished product.
|
||||
OpenERP uses these BoMs to automatically propose manufacturing orders according to product needs.
|
||||
You can either create a bill of materials to define specific production steps,
|
||||
or define a single multi-level bill of materials.
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to create a bill of material.
|
||||
</p><p>
|
||||
Bills of Materials allow you to define the list of required raw
|
||||
materials used to make a finished product; through a manufacturing
|
||||
order or a pack of products.
|
||||
</p><p>
|
||||
OpenERP uses these BoMs to automatically propose manufacturing
|
||||
orders according to procurement needs.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
<record id="mrp_bom_form_action2" model="ir.actions.act_window">
|
||||
|
@ -486,9 +514,14 @@
|
|||
<field name="view_type">form</field>
|
||||
<field name="view_id" ref="mrp_bom_component_tree_view"/>
|
||||
<field name="domain">[('bom_id','!=',False)]</field>
|
||||
<field name="help">
|
||||
Bills of materials components are components and sub-products used to create master bills of materials.
|
||||
Use this menu to search in which BoM a specific component is used.
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to add a component to a bill of material.
|
||||
</p><p>
|
||||
Bills of materials components are components and sub-products
|
||||
used to create master bills of materials. Use this menu to
|
||||
search in which BoM a specific component is used.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
|
@ -850,11 +883,17 @@
|
|||
<field name="view_id" eval="False"/>
|
||||
<field name="search_view_id" ref="view_mrp_production_filter"/>
|
||||
<field name="context">{}</field>
|
||||
<field name="help">
|
||||
Click here to create a new Manufacturing Order.
|
||||
<p>
|
||||
To process the production, do not forget to create a Bill of Material.
|
||||
Manufacturing orders can be automatically generated based on procurement rules specified on the product.
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to create a manufacturing order.
|
||||
</p><p>
|
||||
A manufacuring order, based on a bill of materials, will
|
||||
consume raw materials and produce finished products.
|
||||
</p><p>
|
||||
Manufacturing orders are usually proposed automatically based
|
||||
on customer requirements or automated rules like the minimum
|
||||
stock rule.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
<menuitem action="mrp_production_action" id="menu_mrp_production_action"
|
||||
|
@ -867,13 +906,17 @@
|
|||
<field name="view_type">form</field>
|
||||
<field name="view_mode">calendar,tree,form,graph</field>
|
||||
<field name="domain">[('state','in',('ready','confirmed','in_production'))]</field>
|
||||
<field name="help">
|
||||
Manufacturing Orders describe the operations that need to be carried out,
|
||||
and the raw materials usage for each production stage.
|
||||
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, OpenERP is capable of automatically deciding
|
||||
on the manufacturing route depending on the needs of the company.
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to start a new manufacturing order.
|
||||
</p><p>
|
||||
A manufacuring order, based on a bill of materials, will
|
||||
consume raw materials and produce finished products.
|
||||
</p><p>
|
||||
Manufacturing orders are usually proposed automatically based
|
||||
on customer requirements or automated rules like the minimum
|
||||
stock rule.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
|
@ -1016,11 +1059,15 @@
|
|||
<field name="view_type">form</field>
|
||||
<field name="view_id" ref="mrp_workcenter_tree_view"/>
|
||||
<field name="search_view_id" ref="view_mrp_workcenter_search"/>
|
||||
<field name="help">
|
||||
Work Centers allow you to create and manage manufacturing units.
|
||||
They consist of workers and/or machines, which are considered as units for capacity and planning forecast.
|
||||
Keep in mind that the working time and resource leave are not taken into account in the time computation
|
||||
of the work center.
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to add a work center.
|
||||
</p><p>
|
||||
Work Centers allow you to create and manage manufacturing
|
||||
units. They consist of workers and/or machines, which are
|
||||
considered as units for task assignation as well as capacity
|
||||
and planning forecast.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
|
|
|
@ -177,7 +177,18 @@
|
|||
<field name="view_type">form</field>
|
||||
<field name="view_mode">tree,form,gantt,calendar,graph</field>
|
||||
<field name="search_view_id" ref="view_mrp_production_workcenter_form_view_filter"/>
|
||||
<field name="help">Work Orders is the list of operations to be performed for each manufacturing order. Once you start the first work order of a manufacturing order, the manufacturing order is automatically marked as started. Once you finish the latest operation of a manufacturing order, the MO is automatically done and the related products are produced.</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to start a new work order.
|
||||
</p><p>
|
||||
Work Orders is the list of operations to be performed for each
|
||||
manufacturing order. Once you start the first work order of a
|
||||
manufacturing order, the manufacturing order is automatically
|
||||
marked as started. Once you finish the latest operation of a
|
||||
manufacturing order, the MO is automatically done and the related
|
||||
products are produced.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
<record model="ir.actions.act_window" id="mrp_production_wc_action_planning">
|
||||
|
@ -187,7 +198,17 @@
|
|||
<field name="view_type">form</field>
|
||||
<field name="domain">[('production_state','in',('ready','confirmed','in_production'))]</field>
|
||||
<field name="view_mode">gantt,tree,form,graph,calendar</field>
|
||||
<field name="help">To manufacture or assemble products, and use raw materials and finished products you must also handle manufacturing operations. Manufacturing operations are often called Work Orders. The various operations will have different impacts on the costs of manufacturing and planning depending on the available workload.</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to start a new work order.
|
||||
</p><p>
|
||||
To manufacture or assemble products, and use raw materials and
|
||||
finished products you must also handle manufacturing operations.
|
||||
Manufacturing operations are often called Work Orders. The various
|
||||
operations will have different impacts on the costs of
|
||||
manufacturing and planning depending on the available workload.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
|
||||
|
|
|
@ -218,7 +218,19 @@
|
|||
<field name="view_type">form</field>
|
||||
<field name="view_mode">tree,form</field>
|
||||
<field name="search_view_id" ref="view_repair_order_form_filter"/>
|
||||
<field name="help">Repair orders allow you to organize your product repairs. In a repair order, you can detail the components you remove, add or replace and record the time you spent on the different operations. The repair order uses the warranty date on the Serial Number in order to know if whether the repair should be invoiced to the customer or not.</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to create a reparation order.
|
||||
</p><p>
|
||||
In a repair order, you can detail the components you remove,
|
||||
add or replace and record the time you spent on the different
|
||||
operations.
|
||||
</p><p>
|
||||
The repair order uses the warranty date on the Serial Number in
|
||||
order to know if whether the repair should be invoiced to the
|
||||
customer or not.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
<menuitem action="action_repair_order_tree" id="menu_repair_order" parent="mrp.menu_mrp_manufacturing" groups="mrp.group_mrp_user" name="Repair Orders" sequence="50"/>
|
||||
|
|
|
@ -168,7 +168,19 @@
|
|||
<field name="context" eval="{'default_pos_categ_id': ref('point_of_sale.categ_others')}"/>
|
||||
<field name="view_id" ref="product.product_product_tree_view"/>
|
||||
<field name="search_view_id" ref="product.product_search_form_view"/>
|
||||
<field name="help">You must define a Product for everything you buy or sell. Products can be raw materials, stockable products, consumables or services. The Product form contains detailed information about your products related to procurement logistics, sales price, product category, suppliers and so on.</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to add a new product.
|
||||
</p><p>
|
||||
You must define a product for everything you sell through
|
||||
the point of sale interface.
|
||||
</p><p>
|
||||
Do not forget to set the price and the point of sale category
|
||||
in which it should appear. If a product has no point of sale
|
||||
category, you can not sell it through the point of sale
|
||||
interface.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
<menuitem
|
||||
action="product_normal_action"
|
||||
|
@ -693,7 +705,14 @@
|
|||
<field name="view_mode">tree,form</field>
|
||||
<field name="context" eval="{'default_journal_user': 1, 'default_type': 'cash'}"/>
|
||||
<field name="domain">[('journal_user','=', 1)]</field>
|
||||
<field name="help">Payment methods are defined by accounting journals having the field Payment Method checked.</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to add a payment method.
|
||||
</p><p>
|
||||
Payment methods are defined by accounting journals having the
|
||||
field <i>Payment Method</i> checked.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
<menuitem action="action_account_journal_form"
|
||||
|
|
|
@ -55,10 +55,14 @@
|
|||
<field name="view_mode">tree,form</field>
|
||||
<!-- a context is necessary to get the right portal form view -->
|
||||
<field name="context">{'form_view_ref': 'portal.portal_form_view'}</field>
|
||||
<field name="help">
|
||||
A portal helps defining specific views and rules for a group of users (the
|
||||
portal group). A portal menu, widgets and specific groups may be assigned to
|
||||
the portal's users.
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to create a new portal.
|
||||
</p><p>
|
||||
A portal helps defining specific views and rules for a group of
|
||||
users (the portal group). A portal menu, widgets and specific
|
||||
groups may be assigned to the portal's users.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
<!-- menu Administration/Portals/Portals -->
|
||||
|
|
|
@ -70,7 +70,14 @@
|
|||
<field name="domain" eval=""/>
|
||||
<field name="context">{"search_default_user_id":'', "search_default_draft":'', "search_default_todo":''}</field>
|
||||
<field name="search_view_id" ref="project_issue.view_project_issue_filter"/>
|
||||
<field name="help">Issues such as system bugs, customer complaints, and material breakdowns are collected here. You can define the stages assigned when solving the project issue (analysis, development, done). With the mailgateway module, issues can be integrated through an email address (example: support@mycompany.com)</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to create an issue.
|
||||
</p><p>
|
||||
OpenERP's kanban view will help you track easily your current
|
||||
pipeline of issues to fix.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
<menuitem name="Issues" id="portal_after_sales_issues" parent="portal.portal_projects"
|
||||
|
|
|
@ -11,7 +11,7 @@
|
|||
<field name="domain">[('type','=','out')]</field>
|
||||
<field name="context">{'default_type': 'out', 'contact_display': 'partner_address'}</field>
|
||||
<field name="search_view_id" ref="stock.view_picking_out_search"/>
|
||||
<field name="help">This is the list of all delivery orders that have to be prepared, according to your different sales orders and your logistics rules.</field>
|
||||
<field name="help">This is the list of all delivery orders that have to be prepared, according to your different orders.</field>
|
||||
</record>
|
||||
|
||||
<record id="product_normal_action" model="ir.actions.act_window">
|
||||
|
@ -22,7 +22,6 @@
|
|||
<field name="view_mode">kanban,tree,form</field>
|
||||
<field name="view_id" ref="product.product_kanban_view"/>
|
||||
<field name="search_view_id" ref="product.product_search_form_view"/>
|
||||
<field name="help">You must define a Product for everything you buy or sell. Products can be raw materials, stockable products, consumables or services. The Product form contains detailed information about your products related to procurement logistics, sales price, product category, suppliers and so on.</field>
|
||||
</record>
|
||||
|
||||
<menuitem name="Quotations" id="portal_quotations" parent="portal.portal_orders"
|
||||
|
|
|
@ -145,7 +145,20 @@
|
|||
<field name="view_id" eval="False"/>
|
||||
<field name="search_view_id" ref="view_procurement_filter"/>
|
||||
<field name="context">{'search_default_current':1}</field>
|
||||
<field name="help">A procurement order is used to record a need for a specific product at a specific location. A procurement order is usually created automatically from sales orders, a Pull Logistics rule or Minimum Stock Rules. When the procurement order is confirmed, it automatically creates the necessary operations to fullfil the need: purchase order proposition, manufacturing order, etc.</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to create a procurement order.
|
||||
</p><p>
|
||||
A procurement order is used to record a need for a specific
|
||||
product at a specific location. Procurement orders are usually
|
||||
created automatically from sales orders, pull logistic rules or
|
||||
minimum stock rules.
|
||||
</p><p>
|
||||
When the procurement order is confirmed, it automatically
|
||||
creates the necessary operations to fullfil the need: purchase
|
||||
order proposition, manufacturing order, etc.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
<record id="procurement_exceptions" model="ir.actions.act_window">
|
||||
|
|
|
@ -45,7 +45,16 @@
|
|||
<field name="res_model">product.pricelist.version</field>
|
||||
<field name="view_type">form</field>
|
||||
<field name="view_id" ref="product_pricelist_version_tree_view"/>
|
||||
<field name="help">There can be more than one version of a pricelist. Here you can create and manage new versions of a price list. Some examples of versions: 2010, 2011, Summer Promotion, etc.</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to add a pricelist version.
|
||||
</p><p>
|
||||
There can be more than one version of a pricelist, each of
|
||||
these must be valid during a certain period of time. Some
|
||||
examples of versions: Main Prices, 2010, 2011, Summer Sales,
|
||||
etc.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
<menuitem
|
||||
action="product_pricelist_action" id="menu_product_pricelist_action"
|
||||
|
@ -178,7 +187,19 @@
|
|||
<field name="view_mode">tree,form</field>
|
||||
<field name="search_view_id" ref="product_pricelist_view_search" />
|
||||
<field name="context">{"default_type":"sale", "search_default_type":"sale"}</field>
|
||||
<field name="help">A price list contains rules to be evaluated in order to compute the purchase or sales price for all the partners assigned to a price list. Price lists have several versions (2010, 2011, Promotion of February 2010, etc.) and each version has several rules. Example: the customer price of a product category will be based on the supplier price multiplied by 1.80.</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to create a pricelist.
|
||||
</p><p>
|
||||
A price list contains rules to be evaluated in order to compute
|
||||
the sales price of the products.
|
||||
</p><p>
|
||||
Price lists may have several versions (2010, 2011, Promotion of
|
||||
February 2010, etc.) and each version may have several rules.
|
||||
(e.g. the customer price of a product category will be based on
|
||||
the supplier price multiplied by 1.80).
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
<record id="product_pricelist_action_for_purchase" model="ir.actions.act_window">
|
||||
<field name="name">Pricelists</field>
|
||||
|
@ -188,7 +209,20 @@
|
|||
<field name="view_mode">tree,form</field>
|
||||
<field name="search_view_id" ref="product_pricelist_view_search" />
|
||||
<field name="context">{"default_type":"purchase", "search_default_type":"purchase"}</field>
|
||||
<field name="help">A price list contains rules to be evaluated in order to compute the purchase or sales price for all the partners assigned to a price list. Price lists have several versions (2010, 2011, Promotion of February 2010, etc.) and each version has several rules. Example: the customer price of a product category will be based on the supplier price multiplied by 1.80.</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to create a pricelist.
|
||||
</p><p>
|
||||
A price list contains rules to be evaluated in order to compute
|
||||
the purchase price. The default price list has only one rule; use
|
||||
the cost price defined on the product form, so that you do not have to
|
||||
worry about supplier pricelists if you have very simple needs.
|
||||
</p><p>
|
||||
But you can also import complex price lists form your supplier
|
||||
that may depends on the quantities ordered or the current
|
||||
promotions.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
<menuitem
|
||||
action="product_pricelist_action2" id="menu_product_pricelist_action2"
|
||||
|
|
|
@ -239,7 +239,14 @@
|
|||
<field name="view_mode">tree,form,kanban</field>
|
||||
<field name="view_id" ref="product_product_tree_view"/>
|
||||
<field name="search_view_id" ref="product_search_form_view"/>
|
||||
<field name="help">You must define a Product for everything you buy or sell. Products can be raw materials, stockable products, consumables or services. The Product form contains detailed information about your products related to procurement logistics, sales price, product category, suppliers and so on.</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to define a new product.
|
||||
</p><p>
|
||||
You must define a product for everything you buy or sell,
|
||||
wether it's a physical product, a consumable or service.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
<record id="product_normal_action_sell" model="ir.actions.act_window">
|
||||
<field name="name">Products</field>
|
||||
|
@ -250,7 +257,19 @@
|
|||
<field name="context">{"search_default_filter_to_sell":1}</field>
|
||||
<field name="view_id" ref="product_product_tree_view"/>
|
||||
<field name="search_view_id" ref="product_search_form_view"/>
|
||||
<field name="help">You must define a Product for everything you buy or sell. Products can be raw materials, stockable products, consumables or services. The Product form contains detailed information about your products related to procurement logistics, sales price, product category, suppliers and so on.</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to define a new product.
|
||||
</p><p>
|
||||
You must define a product for everything you sell, wether it's
|
||||
a physical product, a consumable or a service you offer to
|
||||
customers.
|
||||
</p><p>
|
||||
The product form contains information to simplify the sale
|
||||
process: price, notes in the quotation, accounting data,
|
||||
procurement methods, etc.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
<record id="open_view_product_tree1" model="ir.actions.act_window.view">
|
||||
|
@ -286,7 +305,19 @@
|
|||
<field name="context">{"search_default_filter_to_purchase":1}</field>
|
||||
<field name="view_id" ref="product_product_tree_view"/>
|
||||
<field name="search_view_id" ref="product_search_form_view"/>
|
||||
<field name="help">Products can be purchased and/or sold. They can be raw materials, stockable products, consumables or services. The Product form contains detailed information about your products related to procurement logistics, sales price, product category, suppliers and so on.</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to define a new product.
|
||||
</p><p>
|
||||
You must define a product for everything you purchase, wheter
|
||||
it's a physical product, a consumable or services you buy to
|
||||
subcontractants.
|
||||
</p><p>
|
||||
The product form contains detailed information to improve the
|
||||
purchase process: prices, procurement logistics, accounting data,
|
||||
available suppliers, etc.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
<record id="product_category_search_view" model="ir.ui.view">
|
||||
|
@ -358,7 +389,13 @@
|
|||
<field name="domain">[('parent_id','=',False)]</field>
|
||||
<field name="view_type">tree</field>
|
||||
<field name="view_id" ref="product_category_tree_view"/>
|
||||
<field name="help">Here is a list of all your products classified by category. You can click a category to get the list of all products linked to this category or to a child of this category.</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Here is a list of all your products classified by category. You
|
||||
can click a category to get the list of all products linked to
|
||||
this category or to a child of this category.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
<menuitem
|
||||
action="product_category_action"
|
||||
|
@ -440,7 +477,14 @@
|
|||
<field name="res_model">product.uom</field>
|
||||
<field name="view_type">form</field>
|
||||
<field name="view_id" ref="product_uom_tree_view"/>
|
||||
<field name="help">Create and manage the units of measure you want to be used in your system. You can define a conversion rate between several Units of Measure within the same category.</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to add a new unit of measure.
|
||||
</p><p>
|
||||
You must define a conversion rate between several Units of
|
||||
Measure within the same category.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
<menuitem id="next_id_16" name="Units of Measure" parent="prod_config_main" sequence="30" groups="product.group_uom"/>
|
||||
<menuitem action="product_uom_form_action" id="menu_product_uom_form_action" parent="base.menu_base_config" sequence="30" groups="product.group_uom"/>
|
||||
|
@ -463,7 +507,16 @@
|
|||
<field name="res_model">product.uom.categ</field>
|
||||
<field name="view_type">form</field>
|
||||
<field name="view_mode">tree,form</field>
|
||||
<field name="help">Create and manage the units of measure categories you want to be used in your system. If several units of measure are in the same category, they can be converted to each other. For example, in the unit of measure category "Time", you will have the following UoM: Hours, Days.</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to add a new unit of measure category.
|
||||
</p><p>
|
||||
Units of measure belonging to the same category can be
|
||||
converted between each others. For example, in the category
|
||||
<i>'Time'</i>, you will have the following units of measure:
|
||||
Hours, Days.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
<menuitem action="product_uom_categ_form_action" id="menu_product_uom_categ_form_action" parent="base.menu_base_config" sequence="25" groups="base.group_no_one"/>
|
||||
|
||||
|
@ -497,7 +550,15 @@
|
|||
<field name="res_model">product.ul</field>
|
||||
<field name="view_type">form</field>
|
||||
<field name="view_mode">tree,form</field>
|
||||
<field name="help">Create and manage your packaging dimensions and types you want to be maintained in your system.</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to add a new packaging type.
|
||||
</p><p>
|
||||
The packaging type define the dimensions as well as the number
|
||||
of products per package. This will ensure salesperson sell the
|
||||
right number of products according to the package selected.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
<menuitem
|
||||
action="product_ul_form_action" groups="product.group_stock_packaging" id="menu_product_ul_form_action" parent="prod_config_main" sequence="3"/>
|
||||
|
|
|
@ -691,7 +691,15 @@
|
|||
<field name="view_id" eval="False"/>
|
||||
<field name="context">{}</field>
|
||||
<field name="search_view_id" ref="view_task_search_form"/>
|
||||
<field name="help">Tasks allow you to organize your work into a project. Click on button "Create" to create a new task.</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to create a new task.
|
||||
</p><p>
|
||||
OpenERP's project management allows you to manage the pipeline
|
||||
of tasks in order to get things done efficiently. You can
|
||||
track progress, discuss on tasks, attach documents, etc.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
<record id="open_view_task_list_kanban" model="ir.actions.act_window.view">
|
||||
<field name="sequence" eval="0"/>
|
||||
|
@ -786,7 +794,16 @@
|
|||
<field name="res_model">project.task.type</field>
|
||||
<field name="view_type">form</field>
|
||||
<field name="view_id" ref="task_type_tree"/>
|
||||
<field name="help">Define the steps that will be used in the project from the creation of the task, up to the closing of the task or issue. You will use these stages in order to track the progress in solving a task or an issue.</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to add a stage in the task pipeline.
|
||||
</p><p>
|
||||
Define the steps that will be used in the project from the
|
||||
creation of the task, up to the closing of the task or issue.
|
||||
You will use these stages in order to track the progress in
|
||||
solving a task or an issue.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
<menuitem id="menu_tasks_config" name="GTD" parent="base.menu_definitions" sequence="1"/>
|
||||
|
|
|
@ -13,7 +13,15 @@
|
|||
<field name="view_id" eval="False"/>
|
||||
<field name="domain" eval=""/>
|
||||
<field name="search_view_id" ref="view_project_issue_filter"/>
|
||||
<field name="help">Issues such as system bugs, customer complaints, and material breakdowns are collected here. You can define the stages assigned when solving the project issue (analysis, development, done). With the mailgateway module, issues can be integrated through an email address (example: support@mycompany.com)</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to report a new issue.
|
||||
</p><p>
|
||||
The OpenERP issues tacker allows you to efficiantly manage things
|
||||
like internal requests, software development bugs, customer
|
||||
complaints, project troubles, material breakdowns, etc.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
<record model="ir.actions.act_window.view" id="action_crm_tag_kanban_view0">
|
||||
|
|
|
@ -69,7 +69,14 @@
|
|||
<field name="name">Versions</field>
|
||||
<field name="res_model">project.issue.version</field>
|
||||
<field name="view_type">form</field>
|
||||
<field name="help">You can use the issues tracker in OpenERP to handle bugs in the software development project, to handle claims in after-sales services, etc. Define here the different versions of your products on which you can work on issues.</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to add a new version.
|
||||
</p><p>
|
||||
Define here the different versions of your products on which
|
||||
you can work on issues.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
<menuitem action="project_issue_version_action" id="menu_project_issue_version_act" parent="menu_project_confi" groups="base.group_no_one"/>
|
||||
|
||||
|
|
|
@ -96,10 +96,14 @@
|
|||
<field name="domain">[]</field>
|
||||
<field name="context">{'search_default_to_invoice': 1}</field>
|
||||
<field name="view_id" ref="view_account_analytic_line_tree_inherit_account_id"/>
|
||||
<field name="help">You will find here all works made on tasks that you can invoice.
|
||||
In order to invoice the time spent on a project, you must define the
|
||||
pricelist and the field 'Invoice Task Work' on the tab 'Billing' of
|
||||
the project form.</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to add a work to invoice.
|
||||
</p><p>
|
||||
You will find here all works made on tasks that you can
|
||||
invoice.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
<menuitem action="hr_timesheet.action_hr_timesheet_sign_in"
|
||||
id="menu_hr_timesheet_sign_in"
|
||||
|
@ -124,7 +128,14 @@ the project form.</field>
|
|||
<field name="context">{}</field>
|
||||
<field name="domain">[('type','=','normal')]</field>
|
||||
<field name="search_view_id" ref="account_analytic_analysis.view_account_analytic_account_overdue_search"/>
|
||||
<field name="help">You will find here the contracts related to your customer projects in order to track the invoicing progress.</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to add a customer contract.
|
||||
</p><p>
|
||||
You will find here the contracts related to your customer
|
||||
projects in order to track the invoicing progress.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
<menuitem id="menu_invoicing_contracts" parent="menu_project_billing" sequence="4"
|
||||
action="account_analytic_analysis.action_account_analytic_overdue"/>
|
||||
|
|
|
@ -81,10 +81,17 @@
|
|||
<field name="domain">[('type','=','in_invoice')]</field>
|
||||
<field name="context">{'default_type':'in_invoice', 'type':'in_invoice', 'journal_type': 'purchase', 'search_default_draft': 1}</field>
|
||||
<field name="search_view_id" ref="account.view_account_invoice_filter"/>
|
||||
<field name="help">
|
||||
Use this menu to control the invoices to be received from your supplier.
|
||||
OpenERP generates draft invoices from your purchase orders or receptions, according to your settings.
|
||||
Once you receive a supplier invoice, you can match it with the draft invoice and validate it.
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to create a draft invoice.
|
||||
</p><p>
|
||||
Use this menu to control the invoices to be received from your
|
||||
supplier. OpenERP generates draft invoices from your purchase
|
||||
orders or receptions, according to your settings.
|
||||
</p><p>
|
||||
Once you receive a supplier invoice, you can match it with the
|
||||
draft invoice and validate it.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
|
@ -346,14 +353,17 @@
|
|||
<field name="context">{'search_default_draft': 1}</field>
|
||||
<field name="view_mode">tree,form,graph,calendar</field>
|
||||
<field name="search_view_id" ref="view_purchase_order_filter"/>
|
||||
<field name="help">
|
||||
Create a request for quotation when you want to buy products from a supplier.
|
||||
You can also use this menu to review requests for quotation created automatically
|
||||
(based on logistic rules, like minimum stock, MTO, etc.)
|
||||
<p>
|
||||
Once confirmed, a request for quotation becomes a purchase order.
|
||||
In the Purchase Settings, you can select the way to control supplier invoicing:
|
||||
based on the order, based on receptions, or manual.
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to create a request for quotation.
|
||||
</p><p>
|
||||
The quotation contains the history of the discussion/negociation
|
||||
you had with your supplier. Once confirmed, a request for
|
||||
quotation is converted into a purchase order.
|
||||
</p><p>
|
||||
Most propositions of purchase orders are created automatically
|
||||
by OpenERP based on inventory needs.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
<menuitem action="purchase_rfq" id="menu_purchase_rfq"
|
||||
|
@ -367,7 +377,16 @@
|
|||
<field name="view_mode">tree,form,graph,calendar</field>
|
||||
<field name="context">{'search_default_approved': 1}</field>
|
||||
<field name="search_view_id" ref="view_purchase_order_filter"/>
|
||||
<field name="help">Use this menu to search within your purchase orders by references, supplier, products, etc. For each purchase order, you can track the products received, and control the supplier invoices.</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to create a quotation that will be converted into a purchase order.
|
||||
</p><p>
|
||||
Use this menu to search within your purchase orders by
|
||||
references, supplier, products, etc. For each purchase order,
|
||||
you can track the related discussion with the supplier, control
|
||||
the products received and control the supplier invoices.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
<menuitem action="purchase_form_action" id="menu_purchase_form_action" parent="menu_procurement_management" sequence="6"/>
|
||||
|
||||
|
@ -516,10 +535,13 @@
|
|||
<field name="view_type">form</field>
|
||||
<field name="view_mode">tree,form</field>
|
||||
<field name="search_view_id" ref="purchase_order_line_search"/>
|
||||
<field name="help">
|
||||
Here you can track all the lines of purchase orders where the invoicing is "Based on Purchase Order Lines",
|
||||
and for which you have not received a supplier invoice yet.
|
||||
You can generate a draft supplier invoice based on the lines from this list.
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Here you can track all the lines of purchase orders where the
|
||||
invoicing is "Based on Purchase Order Lines", and for which you
|
||||
have not received a supplier invoice yet. You can generate a
|
||||
draft supplier invoice based on the lines from this list.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
<record id="purchase_line_form_action_tree2" model="ir.actions.act_window.view">
|
||||
|
|
|
@ -101,10 +101,13 @@
|
|||
<field name="domain">[('type','=','in')]</field>
|
||||
<field name="context">{"default_type": "in", "contact_display": "partner_address", "search_default_done": 1, "search_default_to_invoice": 1}</field>
|
||||
<field name="search_view_id" ref="view_picking_in_search_picking_to_invoice"/>
|
||||
<field name="help">
|
||||
Here you can track all the product receptions of purchase orders where the invoicing is "Based on Incoming Shipments",
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Here you can track all the product receptions of purchase
|
||||
orders where the invoicing is "Based on Incoming Shipments",
|
||||
and for which you have not received a supplier invoice yet.
|
||||
You can generate a supplier invoice based on those receptions.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
|
|
|
@ -162,7 +162,17 @@
|
|||
<field name="view_mode">tree,form</field>
|
||||
<field name="context">{"search_default_create_uid":uid}</field>
|
||||
<field name="search_view_id" ref="view_purchase_requisition_filter"/>
|
||||
<field name="help">A purchase requisition is the step before a request for quotation. In a purchase requisition (or purchase tender), you can record the products you need to buy and trigger the creation of RfQs to suppliers. After the negotiation, once you have reviewed all the supplier's offers, you can validate some and cancel others.</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to start a new purchase requisition process.
|
||||
</p><p>
|
||||
A purchase requisition is the step before a request for quotation.
|
||||
In a purchase requisition (or purchase tender), you can record the
|
||||
products you need to buy and trigger the creation of RfQs to
|
||||
suppliers. After the negotiation, once you have reviewed all the
|
||||
supplier's offers, you can validate some and cancel others.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
<menuitem
|
||||
|
|
|
@ -8,13 +8,18 @@
|
|||
<field name="view_mode">tree,form,graph</field>
|
||||
<field name="context">{'search_default_partner_id': active_id}</field>
|
||||
<field name="groups_id" eval="[(4, ref('base.group_sale_salesman'))]"/>
|
||||
<field name="help">
|
||||
This customer has no quotation or sale order.
|
||||
Click here to create a new quotation.
|
||||
<p>
|
||||
The "Quotation" is the first step of the Sales flow. Manage your sales from quotation to invoice.
|
||||
<p>
|
||||
You will be able to sell products (manage deliveries) as well as services (create projects).
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to create a quotation or sale order for this customer.
|
||||
</p><p>
|
||||
OpenERP will help you efficiently handle the complete sale flow:
|
||||
quotation, sale order, delivery, invoicing and
|
||||
payment.
|
||||
</p><p>
|
||||
The social feature helps you organize discussions on each sale
|
||||
order, and allow your customer to keep track of the evolution
|
||||
of the sale order.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
|
|
|
@ -58,7 +58,15 @@
|
|||
<field name="view_type">form</field>
|
||||
<field name="view_mode">tree,form</field>
|
||||
<field name="view_id" ref="view_shop_tree"/>
|
||||
<field name="help">If you have more than one shop reselling your company products, you can create and manage that from here. Whenever you will record a new quotation or sales order, it has to be linked to a shop. The shop also defines the warehouse from which the products will be delivered for each particular sales.</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to define a new sale shop.
|
||||
</p><p>
|
||||
Each quotation or sale order must be linked to a shop. The
|
||||
shop also defines the warehouse from which the products will be
|
||||
delivered for each particular sales.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
<menuitem action="action_shop_form" id="menu_action_shop_form" parent="base.menu_base_config" sequence="35"
|
||||
|
@ -391,7 +399,15 @@
|
|||
<field name="view_mode">tree,form,calendar,graph</field>
|
||||
<field name="search_view_id" ref="view_sales_order_filter"/>
|
||||
<field name="context">{"search_default_sales":1}</field>
|
||||
<field name="help">Sales Orders help you manage quotations and orders from your customers. OpenERP suggests that you start by creating a quotation. Once it is confirmed, the quotation will be converted into a Sales Order. OpenERP can handle several types of products so that a sales order may trigger tasks, delivery orders, manufacturing orders, purchases and so on. Based on the configuration of the sales order, a draft invoice will be generated so that you just have to confirm it when you want to bill your customer.</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to create a quotation that can be converted into a sale
|
||||
order.
|
||||
</p><p>
|
||||
OpenERP will help you efficiently handle the complete sales flow:
|
||||
quotation, sale order, delivery, invoicing and payment.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
<menuitem action="action_order_form" id="menu_sale_order" parent="base.menu_sales" sequence="5" groups="base.group_sale_salesman,base.group_sale_manager"/>
|
||||
|
||||
|
@ -425,13 +441,20 @@
|
|||
<field name="view_mode">tree,form,calendar,graph</field>
|
||||
<field name="context">{"search_default_draft":1}</field>
|
||||
<field name="search_view_id" ref="view_sales_order_filter"/>
|
||||
<field name="help">
|
||||
Click here to create a new quotation.
|
||||
<p>
|
||||
The "Quotation" is the first step of the Sales flow. Manage your sales from quotation to invoice.
|
||||
<p>
|
||||
You will be able to sell products (manage deliveries) as well as services (create projects).
|
||||
</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to create a quotation, the first step of a new sale.
|
||||
</p><p>
|
||||
OpenERP will help you handle efficiently the complete sale flow:
|
||||
from the quotation to the sale order, the
|
||||
delivery, the invoicing and the payment collection.
|
||||
</p><p>
|
||||
The social feature helps you organize discussions on each sale
|
||||
order, and allow your customers to keep track of the evolution
|
||||
of the sale order.
|
||||
</p>
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
<menuitem id="menu_sale_quotations"
|
||||
|
@ -580,7 +603,14 @@
|
|||
<field name="search_view_id" ref="view_sales_order_uninvoiced_line_filter"/>
|
||||
<field name="context">{"search_default_uninvoiced":1}</field>
|
||||
<field name="filter" eval="True"/>
|
||||
<field name="help">Here is a list of each sales order line to be invoiced. You can invoice sales orders partially, by lines of sales order. You do not need this list if you invoice from the delivery orders or if you invoice sales totally.</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Here is a list of each sales order line to be invoiced. You can
|
||||
invoice sales orders partially, by lines of sales order. You do
|
||||
not need this list if you invoice from the delivery orders or
|
||||
if you invoice sales totally.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
<record id="action_order_line_tree3" model="ir.actions.act_window">
|
||||
|
|
|
@ -125,7 +125,7 @@
|
|||
</record>
|
||||
|
||||
<record id="action_receive_move" model="ir.actions.act_window">
|
||||
<field name="name">Receive Products</field>
|
||||
<field name="name">Receptions</field>
|
||||
<field name="res_model">stock.move</field>
|
||||
<field name="type">ir.actions.act_window</field>
|
||||
<field name="view_type">form</field>
|
||||
|
@ -134,11 +134,19 @@
|
|||
<field name="view_id" ref="view_move_tree_reception_picking"/>
|
||||
<field name="context" eval="'{\'search_default_product_id\': [active_id]}'"/>
|
||||
<field name="search_view_id" ref="view_move_search_reception_incoming_picking"/>
|
||||
<field name="help">Here you can receive individual products, no matter what purchase order or picking order they come from. You will find the list of all products you are waiting for. Once you receive an order, you can filter based on the name of the supplier or the purchase order reference. Then you can confirm all products received using the buttons on the right of each line.</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to register a reception for this product.
|
||||
</p><p>
|
||||
Here you will find the history of all receptions related to
|
||||
this product, as well as all future receptions you are waiting
|
||||
from your suppliers.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
<record id="action_deliver_move" model="ir.actions.act_window">
|
||||
<field name="name">Receive Products</field>
|
||||
<field name="name">Deliveries</field>
|
||||
<field name="res_model">stock.move</field>
|
||||
<field name="type">ir.actions.act_window</field>
|
||||
<field name="view_type">form</field>
|
||||
|
@ -147,7 +155,15 @@
|
|||
<field name="view_id" ref="view_move_tree_reception_picking"/>
|
||||
<field name="context" eval="'{\'search_default_product_id\': [active_id]}'"/>
|
||||
<field name="search_view_id" ref="view_move_search_reception_outcoming_picking"/>
|
||||
<field name="help">You will find in this list all products you have to deliver to your customers. You can process the deliveries directly from this list using the buttons on the right of each line. You can filter the products to deliver by customer, products or sale order (using the Origin field).</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to add a delivery order for this product.
|
||||
</p><p>
|
||||
Here you will find the history of all past deliveries related to
|
||||
this product, as well as all the products you must deliver to
|
||||
customers.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
<record model="ir.ui.view" id="product.product_kanban_view">
|
||||
|
|
|
@ -200,7 +200,16 @@
|
|||
<field name="view_type">form</field>
|
||||
<field name="view_id" ref="view_inventory_tree"/>
|
||||
<field name="search_view_id" ref="view_inventory_filter"/>
|
||||
<field name="help">Periodical Inventories are used to count the number of products available per location. You can use it once a year when you do the general inventory or whenever you need it, to correct the current stock level of a product.</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to start an inventory.
|
||||
</p><p>
|
||||
Periodical Inventories are used to count the number of products
|
||||
available per location. You can use it once a year when you do
|
||||
the general inventory or whenever you need it, to adapt the
|
||||
current inventory level of a product.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
<menuitem action="action_inventory_form" id="menu_action_inventory_form" parent="menu_stock_inventory_control" sequence="30"/>
|
||||
|
||||
|
@ -255,7 +264,15 @@
|
|||
<field name="res_model">stock.tracking</field>
|
||||
<field name="view_type">form</field>
|
||||
<field name="view_id" ref="view_tracking_tree"/>
|
||||
<field name="help">This is the list of all your packs. When you select a Pack, you can get the upstream or downstream traceability of the products contained in the pack.</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to add a tracking number.
|
||||
</p><p>
|
||||
This is the list of all your packs. When you select a Pack, you
|
||||
can get the upstream or downstream traceability of the products
|
||||
contained in the pack.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
<menuitem id="menu_traceability" name="Traceability" parent="menu_stock_root" sequence="3"/>
|
||||
<menuitem action="action_tracking_form" id="menu_action_tracking_form"
|
||||
|
@ -413,7 +430,19 @@
|
|||
<field name="view_id" ref="view_production_lot_tree"/>
|
||||
<field name="search_view_id" ref="search_product_lot_filter"/>
|
||||
<field name="context">{}</field>
|
||||
<field name="help">This is the list of all the production lots (serial numbers) you recorded. When you select a lot, you can get the upstream or downstream traceability of the products contained in lot. By default, the list is filtred on the serial numbers that are available in your warehouse but you can uncheck the 'Available' button to get all the lots you produced, received or delivered to customers.</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to add a serial number.
|
||||
</p><p>
|
||||
This is the list of all the production lots you recorded. When
|
||||
you select a lot, you can get the upstream or downstream
|
||||
traceability of the products contained in lot. By default, the
|
||||
list is filtred on the serial numbers that are available in
|
||||
your warehouse but you can uncheck the 'Available' button to
|
||||
get all the lots you produced, received or delivered to
|
||||
customers.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
<menuitem action="action_production_lot_form" id="menu_action_production_lot_form"
|
||||
parent="menu_traceability" groups="stock.group_production_lot"
|
||||
|
@ -584,7 +613,24 @@
|
|||
<field name="view_id" ref="view_location_tree2"/>
|
||||
<field name="search_view_id" ref="view_location_search"/>
|
||||
<field name="context">{'search_default_in_location':1}</field>
|
||||
<field name="help">Define your locations to reflect your warehouse structure and organization. OpenERP is able to manage physical locations (warehouses, shelves, bin, etc), partner locations (customers, suppliers) and virtual locations which are the counterpart of the stock operations like the manufacturing orders consumptions, inventories, etc. Every stock operation in OpenERP moves the products from one location to another one. For instance, if you receive products from a supplier, OpenERP will move products from the Supplier location to the Stock location. Each report can be performed on physical, partner or virtual locations.</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to add a location.
|
||||
</p><p>
|
||||
Define your locations to reflect your warehouse structure and
|
||||
organization. OpenERP is able to manage physical locations
|
||||
(warehouses, shelves, bin, etc), partner locations (customers,
|
||||
suppliers) and virtual locations which are the counterpart of
|
||||
the stock operations like the manufacturing orders
|
||||
consumptions, inventories, etc.
|
||||
</p><p>
|
||||
Every stock operation in OpenERP moves the products from one
|
||||
location to another one. For instance, if you receive products
|
||||
from a supplier, OpenERP will move products from the Supplier
|
||||
location to the Stock location. Each report can be performed on
|
||||
physical, partner or virtual locations.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
<menuitem action="action_location_form" id="menu_action_location_form" groups="stock.group_locations"
|
||||
parent="menu_stock_configuration" sequence="5"/>
|
||||
|
@ -607,7 +653,16 @@
|
|||
<field name="domain">[('location_id','=',False)]</field>
|
||||
<field name="view_type">tree</field>
|
||||
<field name="view_id" ref="view_location_tree"/>
|
||||
<field name="help">This is the structure of your company's warehouses and locations. You can click on a location to get the list of the products and their stock level in this particular location and all its children.</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to add a location.
|
||||
</p><p>
|
||||
This is the structure of your company's warehouses and
|
||||
locations. You can click on a location to get the list of the
|
||||
products and their stock level in this particular location and
|
||||
all its children.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
<menuitem action="action_location_tree"
|
||||
id="menu_action_location_tree"
|
||||
|
@ -656,7 +711,11 @@
|
|||
<field name="type">ir.actions.act_window</field>
|
||||
<field name="view_type">form</field>
|
||||
<field name="view_id" ref="view_warehouse_tree"/>
|
||||
<field name="help">Create and manage your warehouses and assign them a location from here</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to define a new warehouse.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
<menuitem action="action_warehouse_form" id="menu_action_warehouse_form" groups="stock.group_locations"
|
||||
parent="menu_stock_configuration" sequence="1"/>
|
||||
|
@ -896,7 +955,15 @@
|
|||
<field name="domain">[('type','=','internal')]</field>
|
||||
<field name="context">{'contact_display': 'partner_address', 'search_default_available': 1}</field>
|
||||
<field name="search_view_id" ref="view_picking_internal_search"/>
|
||||
<field name="help">Internal Moves display all inventory operations you have to perform in your warehouse. All operations can be categorized into stock journals, so that each worker has his own list of operations to perform in his own journal. Most operations are prepared automatically by OpenERP according to your preconfigured logistics rules, but you can also record manual stock operations.</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to create an internal move request.
|
||||
</p><p>
|
||||
Most operations are prepared automatically by OpenERP according
|
||||
to your preconfigured logistics rules, but you can also record
|
||||
manual stock movements.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
<record model="ir.actions.act_window.view" id="action_picking_tree6_tree_view">
|
||||
|
@ -999,7 +1066,15 @@
|
|||
<field name="domain">[('type','=','out')]</field>
|
||||
<field name="context">{'default_type': 'out', 'contact_display': 'partner_address'}</field>
|
||||
<field name="search_view_id" ref="view_picking_out_search"/>
|
||||
<field name="help">This is the list of all delivery orders that have to be prepared, according to your different sales orders and your logistics rules.</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to create a delivery order.
|
||||
</p><p>
|
||||
This is the list of all delivery orders that have to be
|
||||
prepared, according to your different sales orders and your
|
||||
logistics rules.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
<record id="action_picking_tree_out_view1_waiting" model="ir.actions.act_window.view">
|
||||
<field eval="1" name="sequence"/>
|
||||
|
@ -1101,7 +1176,16 @@
|
|||
<field name="domain">[('type','=','in')]</field>
|
||||
<field name="context">{'contact_display': 'partner_address', 'default_type': 'in'}</field>
|
||||
<field name="search_view_id" ref="view_picking_in_search"/>
|
||||
<field name="help">The Incoming Shipments is the list of all orders you will receive from your suppliers. An incoming shipment contains a list of products to be received according to the original purchase order. You can validate the shipment totally or partially.</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to create an incoming shipment.
|
||||
</p><p>
|
||||
The Incoming Shipments is the list of all orders you will
|
||||
receive from your suppliers. An incoming shipment contains a
|
||||
list of products to be received according to the original
|
||||
purchase order.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
<record id="action_invoice_tree5_view1" model="ir.actions.act_window.view">
|
||||
<field eval="1" name="sequence"/>
|
||||
|
@ -1287,7 +1371,15 @@
|
|||
<field name="view_id" ref="view_move_tree"/>
|
||||
<field name="search_view_id" ref="view_move_search"/>
|
||||
<field name="context">{}</field>
|
||||
<field name="help">This menu gives you the full traceability of inventory operations on a specific product. You can filter on the product to see all the past or future movements for the product.</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to create a stock movement.
|
||||
</p><p>
|
||||
This menu gives you the full traceability of inventory
|
||||
operations on a specific product. You can filter on the product
|
||||
to see all the past or future movements for the product.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
<menuitem action="action_move_form2" id="menu_action_move_form2" parent="menu_traceability" sequence="3"/>
|
||||
|
||||
|
@ -1409,7 +1501,18 @@
|
|||
<field name="view_id" ref="view_move_tree_reception_picking"/>
|
||||
<field name="context" eval="'{\'product_receive\' : True, \'default_location_id\':%d, \'default_location_dest_id\':%d}' % (ref('stock_location_suppliers'),ref('stock_location_stock') )"/>
|
||||
<field name="search_view_id" ref="view_move_search_reception_incoming_picking"/>
|
||||
<field name="help">Here you can receive individual products, no matter what purchase order or picking order they come from. You will find the list of all products you are waiting for. Once you receive an order, you can filter based on the name of the supplier or the purchase order reference. Then you can confirm all products received using the buttons on the right of each line.</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to register a product reception.
|
||||
</p><p>
|
||||
Here you can receive individual products, no matter what
|
||||
purchase order or picking order they come from. You will find
|
||||
the list of all products you are waiting for. Once you receive
|
||||
an order, you can filter based on the name of the supplier or
|
||||
the purchase order reference. Then you can confirm all products
|
||||
received using the buttons on the right of each line.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
<record model="ir.actions.act_window.view" id="action_move_reception_picking_tree">
|
||||
|
@ -1536,7 +1639,15 @@
|
|||
<field name="view_id" ref="view_move_tree_reception_picking"/>
|
||||
<field name="context" eval="'{\'default_location_id\':%d, \'default_location_dest_id\':%d}' % (ref('stock_location_stock'),ref('stock_location_customers'))"/>
|
||||
<field name="search_view_id" ref="view_move_search_reception_outcoming_picking"/>
|
||||
<field name="help">You will find in this list all products you have to deliver to your customers. You can process the deliveries directly from this list using the buttons on the right of each line. You can filter the products to deliver by customer, products or sale order (using the Origin field).</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
You will find in this list all products you have to deliver to
|
||||
your customers. You can process the deliveries directly from
|
||||
this list using the buttons on the right of each line. You can
|
||||
filter the products to deliver by customer, products or sale
|
||||
order (using the Origin field).
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
<record model="ir.actions.act_window.view" id="action_move_out_picking_tree">
|
||||
|
@ -1596,7 +1707,17 @@
|
|||
<field name="res_model">stock.journal</field>
|
||||
<field name="type">ir.actions.act_window</field>
|
||||
<field name="view_type">form</field>
|
||||
<field name="help">The stock journal system allows you to assign each stock operation to a specific journal according to the type of operation to perform or the worker/team that should perform the operation. Examples of stock journals may be: quality control, pick lists, packing, etc.</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to create a new journal.
|
||||
</p><p>
|
||||
The stock journal system allows you to assign each stock
|
||||
operation to a specific journal according to the type of
|
||||
operation to perform or the worker/team that should perform the
|
||||
operation. Examples of stock journals may be: quality control,
|
||||
pick lists, packing, etc.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
<menuitem
|
||||
action="action_stock_journal_form"
|
||||
|
|
|
@ -345,7 +345,18 @@
|
|||
<field name="view_mode">kanban,tree,form</field>
|
||||
<field name="view_id" ref="view_survey_kanban"></field>
|
||||
<field name="search_view_id" ref="survey_search"/>
|
||||
<field name="help">You can create survey for different purposes: recruitment interviews, employee's periodical evaluations, marketing campaigns, etc. A survey is made of pages containing questions of several types: text, multiple choices, etc. You can edit survey manually or click on the 'Edit Survey' for a WYSIWYG interface.</field>
|
||||
<field name="help" type="xml">
|
||||
<p>
|
||||
Click to create a new survey.
|
||||
</p><p>
|
||||
You can create survey for different purposes: recruitment
|
||||
interviews, employee's periodical evaluations, marketing
|
||||
campaigns, etc.
|
||||
</p><p>
|
||||
A survey is made of pages containing questions
|
||||
of several types: text, multiple choices, etc.
|
||||
</p>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
|
||||
|
|
Loading…
Reference in New Issue