Financial and accounting module that covers:
--------------------------------------------
-General accountings
-Cost / Analytic accounting
-Third party accounting
-Taxes management
-Budgets
-Customer and Supplier Invoices
-Bank statements
-Reconciliation process by partner
+ * General Accounting
+ * Cost/Analytic accounting
+ * Third party accounting
+ * Taxes management
+ * Budgets
+ * Customer and Supplier Invoices
+ * Bank statements
+ * Reconciliation process by partner
Creates a dashboard for accountants that includes:
--------------------------------------------------
-* List of Customer Invoice to Approve
-* Company Analysis
-* Graph of Aged Receivables
-* Graph of Treasury
+ * List of Customer Invoice to Approve
+ * Company Analysis
+ * Graph of Treasury
-The processes like maintaining of general ledger is done through the defined financial Journals (entry move line or
-grouping is maintained through journal) for a particular financial year and for preparation of vouchers there is a
-module named account_voucher.
+The processes like maintaining of general ledger is done through the defined financial Journals (entry move line orgrouping is maintained through journal) for a particular
+financial year and for preparation of vouchers there is a module named account_voucher.
""",
'website': 'http://www.openerp.com',
'images' : ['images/accounts.jpeg','images/bank_statement.jpeg','images/cash_register.jpeg','images/chart_of_accounts.jpeg','images/customer_invoice.jpeg','images/journal_entries.jpeg'],
'value': fields.selection([('procent', 'Percent'),
('balance', 'Balance'),
('fixed', 'Fixed Amount')], 'Valuation',
- required=True, help="""Select here the kind of valuation related to this payment term line. Note that you should have your last line with the type 'Balance' to ensure that the whole amount will be threated."""),
+ required=True, help="""Select here the kind of valuation related to this payment term line. Note that you should have your last line with the type 'Balance' to ensure that the whole amount will be treated."""),
'value_amount': fields.float('Amount To Pay', digits_compute=dp.get_precision('Payment Term'), help="For percent enter a ratio between 0-1."),
'days': fields.integer('Number of Days', required=True, help="Number of days to add before computation of the day of month." \
'centralisation': fields.boolean('Centralised counterpart', help="Check this box to determine that each entry of this journal won't create a new counterpart but will share the same counterpart. This is used in fiscal year closing."),
'update_posted': fields.boolean('Allow Cancelling Entries', help="Check this box if you want to allow the cancellation the entries related to this journal or of the invoice related to this journal"),
'group_invoice_lines': fields.boolean('Group Invoice Lines', help="If this box is checked, the system will try to group the accounting lines when generating them from invoices."),
- 'sequence_id': fields.many2one('ir.sequence', 'Entry Sequence', help="This field contains the informatin related to the numbering of the journal entries of this journal.", required=True),
+ 'sequence_id': fields.many2one('ir.sequence', 'Entry Sequence', help="This field contains the information related to the numbering of the journal entries of this journal.", required=True),
'user_id': fields.many2one('res.users', 'User', help="The user responsible for this journal"),
'groups_id': fields.many2many('res.groups', 'account_journal_group_rel', 'journal_id', 'group_id', 'Groups'),
'currency': fields.many2one('res.currency', 'Currency', help='The currency used to enter statement'),
'period_id': fields.many2one('account.period', 'Period', required=True, states={'posted':[('readonly',True)]}),
'journal_id': fields.many2one('account.journal', 'Journal', required=True, states={'posted':[('readonly',True)]}),
'state': fields.selection([('draft','Unposted'), ('posted','Posted')], 'Status', required=True, readonly=True,
- help='All manually created new journal entries are usually in the state \'Unposted\', but you can set the option to skip that state on the related journal. In that case, they will be behave as journal entries automatically created by the system on document validation (invoices, bank statements...) and will be created in \'Posted\' state.'),
+ help='All manually created new journal entries are usually in the state \'Unposted\', but you can set the option to skip that state on the related journal. In that case, they will behave as journal entries automatically created by the system on document validation (invoices, bank statements...) and will be created in \'Posted\' state.'),
'line_id': fields.one2many('account.move.line', 'move_id', 'Entries', states={'posted':[('readonly',True)]}),
'to_check': fields.boolean('To Review', help='Check this box if you are unsure of that journal entry and if you want to note it as \'to be reviewed\' by an accounting expert.'),
'partner_id': fields.related('line_id', 'partner_id', type="many2one", relation="res.partner", string="Partner", store=True),
'period_to_cmp': fields.many2one('account.period', 'End Period'),
'date_from_cmp': fields.date("Start Date"),
'date_to_cmp': fields.date("End Date"),
- 'debit_credit': fields.boolean('Display Debit/Credit Columns', help="This option allow you to get more details about your the way your balances are computed. Because it is space consumming, we do not allow to use it while doing a comparison"),
+ 'debit_credit': fields.boolean('Display Debit/Credit Columns', help="This option allows you to get more details about the way your balances are computed. Because it is space consuming, we do not allow to use it while doing a comparison."),
}
def _get_account_report(self, cr, uid, context=None):
_description = 'Account Common Journal Report'
_inherit = "account.common.report"
_columns = {
- 'amount_currency': fields.boolean("With Currency", help="Print Report with the currency column if the currency is different then the company currency"),
+ 'amount_currency': fields.boolean("With Currency", help="Print Report with the currency column if the currency differs from the company currency."),
}
def _build_contexts(self, cr, uid, ids, data, context=None):
'landscape': fields.boolean("Landscape Mode"),
'initial_balance': fields.boolean('Include Initial Balances',
help='If you selected to filter by date or period, this field allow you to add a row to display the amount of debit/credit/balance that precedes the filter you\'ve set.'),
- 'amount_currency': fields.boolean("With Currency", help="It adds the currency column if the currency is different then the company currency"),
+ 'amount_currency': fields.boolean("With Currency", help="It adds the currency column on report if the currency differs from the company currency."),
'sortby': fields.selection([('sort_date', 'Date'), ('sort_journal_partner', 'Journal & Partner')], 'Sort by', required=True),
'journal_ids': fields.many2many('account.journal', 'account_report_general_ledger_journal_rel', 'account_id', 'journal_id', 'Journals', required=True),
}
help='If you selected to filter by date or period, this field allow you to add a row to display the amount of debit/credit/balance that precedes the filter you\'ve set.'),
'filter': fields.selection([('filter_no', 'No Filters'), ('filter_date', 'Date'), ('filter_period', 'Periods'), ('unreconciled', 'Unreconciled Entries')], "Filter by", required=True),
'page_split': fields.boolean('One Partner Per Page', help='Display Ledger Report with One partner per page'),
- 'amount_currency': fields.boolean("With Currency", help="It adds the currency column if the currency is different then the company currency"),
+ 'amount_currency': fields.boolean("With Currency", help="It adds the currency column on report if the currency differs from the company currency."),
'journal_ids': fields.many2many('account.journal', 'account_partner_ledger_journal_rel', 'account_id', 'journal_id', 'Journals', required=True),
}
_defaults = {
Accounting Access Rights.
=========================
-This module gives the admin user the access to all the accounting features
+This module gives the Admin user the access to all the accounting features
like the journal items and the chart of accounts.
-It assigns manager and user access rights to the Administrator, and only
+It assigns manager and user access rights to the Administrator and only
user rights to Demo user.
""",
'website': 'http://www.openerp.com',
Adds menu to show relevant information to each manager.
You can also view the report of account analytic summary
-user-wise as well as month wise.
+user-wise as well as month-wise.
""",
"author": "Camptocamp",
"website": "http://www.camptocamp.com/",
help="Computed using the formula: Invoiced Amount - Total Costs.",
digits_compute=dp.get_precision('Account')),
'theorical_margin': fields.function(_theorical_margin_calc, type='float', string='Theoretical Margin',
- help="Computed using the formula: Theorial Revenue - Total Costs",
+ help="Computed using the formula: Theoretical Revenue - Total Costs",
digits_compute=dp.get_precision('Account')),
'real_margin_rate': fields.function(_real_margin_rate_calc, type='float', string='Real Margin Rate (%)',
help="Computes using the formula: (Real Margin / Total Costs) * 100.",
'name' : 'Account Analytic Defaults',
'version' : '1.0',
"category": 'Accounting & Finance',
- 'description': """Set default values for your analytic accounts
-Allows to automatically select analytic accounts based on criterions:
-=====================================================================
+ 'description': """
+Set default values for your analytic accounts.
+=============================================
-* Product
-* Partner
-* User
-* Company
-* Date
+Allows to automatically select analytic accounts based on criterions:
+---------------------------------------------------------------------
+ * Product
+ * Partner
+ * User
+ * Company
+ * Date
""",
'author' : 'OpenERP SA',
'website' : 'http://www.openerp.com',
_order = "sequence"
_columns = {
'sequence': fields.integer('Sequence', help="Gives the sequence order when displaying a list of analytic distribution"),
- 'analytic_id': fields.many2one('account.analytic.account', 'Analytic Account' , help="Analytical Account"),
- 'product_id': fields.many2one('product.product', 'Product', ondelete='cascade', help="select a product which will use analytical account specified in analytic default (eg. create new cutomer invoice or Sale order if we select this product, it will automatically take this as an analytical account)"),
- 'partner_id': fields.many2one('res.partner', 'Partner', ondelete='cascade', help="select a partner which will use analytical account specified in analytic default (eg. create new cutomer invoice or Sale order if we select this partner, it will automatically take this as an analytical account)"),
- 'user_id': fields.many2one('res.users', 'User', ondelete='cascade', help="select a user which will use analytical account specified in analytic default"),
- 'company_id': fields.many2one('res.company', 'Company', ondelete='cascade', help="select a company which will use analytical account specified in analytic default (eg. create new cutomer invoice or Sale order if we select this company, it will automatically take this as an analytical account)"),
- 'date_start': fields.date('Start Date', help="Default start date for this Analytical Account"),
- 'date_stop': fields.date('End Date', help="Default end date for this Analytical Account"),
+ 'analytic_id': fields.many2one('account.analytic.account', 'Analytic Account'),
+ 'product_id': fields.many2one('product.product', 'Product', ondelete='cascade', help="Select a product which will use analytic account specified in analytic default (e.g. create new customer invoice or Sale order if we select this product, it will automatically take this as an analytic account)"),
+ 'partner_id': fields.many2one('res.partner', 'Partner', ondelete='cascade', help="Select a partner which will use analytic account specified in analytic default (e.g. create new customer invoice or Sale order if we select this partner, it will automatically take this as an analytic account)"),
+ 'user_id': fields.many2one('res.users', 'User', ondelete='cascade', help="Select a user which will use analytic account specified in analytic default."),
+ 'company_id': fields.many2one('res.company', 'Company', ondelete='cascade', help="Select a company which will use analytic account specified in analytic default (e.g. create new customer invoice or Sale order if we select this company, it will automatically take this as an analytic account)"),
+ 'date_start': fields.date('Start Date', help="Default start date for this Analytic Account."),
+ 'date_stop': fields.date('End Date', help="Default end date for this Analytic Account."),
}
def account_get(self, cr, uid, product_id=None, partner_id=None, user_id=None, date=None, context=None):
'version': '1.0',
'category': 'Accounting & Finance',
'description': """
-This module allows to use several analytic plans, according to the general journal.
+This module allows to use several analytic plans according to the general journal.
===================================================================================
Here multiple analytic lines are created when the invoice or the entries
So when this line of invoice will be confirmed, it will generate 3 analytic lines,
for one account entry.
+
The analytic plan validates the minimum and maximum percentage at the time of creation
of distribution models.
""",
This module supports the Anglo-Saxon accounting methodology by changing the accounting logic with stock transactions.
=====================================================================================================================
-The difference between the Anglo-Saxon accounting countries
-and the Rhine or also called Continental accounting countries is the moment of taking the Cost of Goods Sold versus Cost of Sales.
-Anglo-Saxons accounting does take the cost when sales invoice is created, Continental accounting will take the cost at the moment the goods are shipped.
-This module will add this functionality by using a interim account, to store the value of shipped goods and will contra book this interim account
-when the invoice is created to transfer this amount to the debtor or creditor account.
-Secondly, price differences between actual purchase price and fixed product standard price are booked on a separate account""",
+The difference between the Anglo-Saxon accounting countries and the Rhine (or also called
+Continental accounting) countries is the moment of taking the Cost of Goods Sold versus
+Cost of Sales. Anglo-Saxons accounting does take the cost when sales invoice is created,
+Continental accounting will take the cost at the moment the goods are shipped.
+
+This module will add this functionality by using a interim account, to store the value of
+shipped goods and will contra book this interim account when the invoice is created to
+transfer this amount to the debtor or creditor account. Secondly, price differences between
+actual purchase price and fixed product standard price are booked on a separate account.""",
"images": ["images/account_anglo_saxon.jpeg"],
"depends": ["product", "purchase"],
"category": "Hidden/Dependency",
"version" : "1.0",
"depends" : ["account"],
"author" : "OpenERP S.A.",
- "description": """Financial and accounting asset management.
- This Module manages the assets owned by a company or an individual. It will keep track of depreciation's occurred on
- those assets. And it allows to create Move's of the depreciation lines.
+ "description": """
+Financial and accounting asset management.
+==========================================
+
+This Module manages the assets owned by a company or an individual. It will keep track of depreciation's occurred on those assets.
+And it allows to create Move's of the depreciation lines.
+
""",
"website" : "http://www.openerp.com",
"category" : "Accounting & Finance",
#
##############################################################################
{
- 'name': 'Bank Statement extensions to support e-banking',
+ 'name': 'Bank Statement Extensions to Support e-banking',
'version': '0.3',
'license': 'AGPL-3',
'author': 'Noviat',
'category': 'Generic Modules/Accounting',
'description': '''
Module that extends the standard account_bank_statement_line object for improved e-banking support.
+===================================================================================================
-Adds
-- valuta date
-- batch payments
-- traceability of changes to bank statement lines
-- bank statement line views
-- bank statements balances report
-- performance improvements for digital import of bank statement (via 'ebanking_import' context flag)
-- name_search on res.partner.bank enhanced to allow search on bank and iban account numbers
+This module adds:
+ - valuta date
+ - batch payments
+ - traceability of changes to bank statement lines
+ - bank statement line views
+ - bank statements balances report
+ - performance improvements for digital import of bank statement (via 'ebanking_import' context flag)
+ - name_search on res.partner.bank enhanced to allow search on bank and iban account numbers
''',
'depends': ['account'],
'demo_xml': [],
This module allows accountants to manage analytic and crossovered budgets.
==========================================================================
-Once the Master Budgets and the Budgets are defined (in Accounting/Budgets/),
-the Project Managers can set the planned amount on each Analytic Account.
+Once the Budgets are defined (in Invoicing/Budgets/Budgets), the Project Managers
+can set the planned amount on each Analytic Account.
The accountant has the possibility to see the total of amount planned for each
-Budget and Master Budget in order to ensure the total planned is not
-greater/lower than what he planned for this Budget/Master Budget. Each list of
-record can also be switched to a graphical view of it.
+Budget in order to ensure the total planned is not greater/lower than what he planned
+for this Budget. Each list of record can also be switched to a graphical view of it.
Three reports are available:
- 1. The first is available from a list of Budgets. It gives the spreading, for these Budgets, of the Analytic Accounts per Master Budgets.
- 2. The second is a summary of the previous one, it only gives the spreading, for the selected Budgets, of the Analytic Accounts.
+ 1. The first is available from a list of Budgets. It gives the spreading, for these Budgets, of the Analytic Accounts.
- 3. The last one is available from the Analytic Chart of Accounts. It gives the spreading, for the selected Analytic Accounts, of the Master Budgets per Budgets.
+ 2. The second is a summary of the previous one, it only gives the spreading, for the selected Budgets, of the Analytic Accounts.
+ 3. The last one is available from the Analytic Chart of Accounts. It gives the spreading, for the selected Analytic Accounts of Budgets.
""",
'author': 'OpenERP SA',
'website': 'http://www.openerp.com',
Allows cancelling accounting entries.
=====================================
-This module adds 'Allow cancelling entries' field on form view of account journal. If set to true it allows user to cancel entries & invoices.
+This module adds 'Allow Cancelling Entries' field on form view of account journal.
+If set to true it allows user to cancel entries & invoices.
""",
'website': 'http://www.openerp.com',
"images" : ["images/account_cancel.jpeg"],
#
##############################################################################
{
- "name" : "Check writing",
+ "name" : "Check Writing",
"version" : "1.1",
"author" : "OpenERP SA, NovaPoint Group",
"category": "Generic Modules/Accounting",
"description": """
- Module for the Check writing and check printing
+Module for the Check Writing and Check Printing.
""",
'website': 'http://www.openerp.com',
'init_xml': [],
#
##############################################################################
{
- "name": 'Belgium - Import bank CODA statements',
+ "name": 'Belgium - Import Bank CODA Statements',
"version": '2.1',
"author": 'Noviat',
"category": 'Accounting & Finance',
======================================
Supported are CODA flat files in V2 format from Belgian bank accounts.
-* CODA v1 support.
-* CODA v2.2 support.
-* Foreign Currency support.
-* Support for all data record types (0, 1, 2, 3, 4, 8, 9).
-* Parsing & logging of all Transaction Codes and Structured Format Communications.
-* Automatic Financial Journal assignment via CODA configuration parameters.
-* Support for multiple Journals per Bank Account Number.
-* Support for multiple statements from different bank accounts in a single CODA file.
-* Support for 'parsing only' CODA Bank Accounts (defined as type='info' in the CODA Bank Account configuration records).
-* Multi-language CODA parsing, parsing configuration data provided for EN, NL, FR.
+ * CODA v1 support.
+ * CODA v2.2 support.
+ * Foreign Currency support.
+ * Support for all data record types (0, 1, 2, 3, 4, 8, 9).
+ * Parsing & logging of all Transaction Codes and Structured Format Communications.
+ * Automatic Financial Journal assignment via CODA configuration parameters.
+ * Support for multiple Journals per Bank Account Number.
+ * Support for multiple statements from different bank accounts in a single CODA file.
+ * Support for 'parsing only' CODA Bank Accounts (defined as type='info' in the CODA Bank Account configuration records).
+ * Multi-language CODA parsing, parsing configuration data provided for EN, NL, FR.
-The machine readable CODA Files are parsed and stored in human readable format in CODA Bank Statements.
-Also Bank Statements are generated containing a subset of the CODA information (only those transaction lines
-that are required for the creation of the Financial Accounting records).
-The CODA Bank Statement is a 'read-only' object, hence remaining a reliable representation of the original CODA file
-whereas the Bank Statement will get modified as required by accounting business processes.
+The machine readable CODA Files are parsed and stored in human readable format in
+CODA Bank Statements. Also Bank Statements are generated containing a subset of
+the CODA information (only those transaction lines that are required for the creation
+of the Financial Accounting records). The CODA Bank Statement is a 'read-only'
+object, hence remaining a reliable representation of the original CODA file whereas
+the Bank Statement will get modified as required by accounting business processes.
CODA Bank Accounts configured as type 'Info' will only generate CODA Bank Statements.
-A removal of one object in the CODA processing results in the removal of the associated objects.
-The removal of a CODA File containing multiple Bank Statements will also remove those associated
-statements.
+A removal of one object in the CODA processing results in the removal of the associated
+objects. The removal of a CODA File containing multiple Bank Statements will also
+remove those associated statements.
The following reconciliation logic has been implemented in the CODA processing:
+
1) The Company's Bank Account Number of the CODA statement is compared against the Bank Account Number field of the Company's CODA Bank Account configuration records (whereby bank accounts defined in type='info' configuration records are ignored). If this is the case an 'internal transfer' transaction is generated using the 'Internal Transfer Account' field of the CODA File Import wizard.
2) As a second step the 'Structured Communication' field of the CODA transaction line is matched against the reference field of in- and outgoing invoices (supported : Belgian Structured Communication Type).
3) When the previous step doesn't find a match, the transaction counterparty is located via the Bank Account Number configured on the OpenERP Customer and Supplier records.
4) In case the previous steps are not successful, the transaction is generated by using the 'Default Account for Unrecognized Movement' field of the CODA File Import wizard in order to allow further manual processing.
-In stead of a manual adjustment of the generated Bank Statements, you can also re-import the CODA
-after updating the OpenERP database with the information that was missing to allow automatic reconciliation.
+In stead of a manual adjustment of the generated Bank Statements, you can also
+re-import the CODA after updating the OpenERP database with the information that
+was missing to allow automatic reconciliation.
Remark on CODA V1 support:
In some cases a transaction code, transaction category or structured communication code has been given a new or clearer description in CODA V2.
==========================================================================
You can define your multiple levels of recall through the menu:
- Accounting/Configuration/Miscellaneous/Follow-ups
-Once it is defined, you can automatically print recalls every day through simply clicking on the menu:
- Accounting/Periodical Processing/Billing/Send follow-ups
+ Invoicing/Configuration/Miscellaneous/Follow-ups
-It will generate a PDF with all the letters according to the the
-different levels of recall defined. You can define different policies
-for different companies. You can also send mail to the customer.
+Once it is defined, you can automatically print recalls every day through simply
+clicking on the menu:
-Note that if you want to check the follow-up level for a given partner/account entry, you can do from in the menu:
- Accounting/Reporting/Generic Reporting/Partners/Follow-ups Sent
+ Invoicing/Periodical Processing/Billing/Send follow-ups
+
+It will generate a PDF with all the letters according to the the different levels
+of recall defined. You can define different policies for different companies. You
+can also send mail to the customer.
+
+Note that if you want to check the follow-up level for a given partner/account
+entry, you can do from in the menu:
+
+ Invoicing/Reporting/Generic Reporting/Partners/Follow-ups Sent
""",
'author': 'OpenERP SA',
=======================================================
This module allows you to create and manage your payment orders, with purposes to
-* serve as base for an easy plug-in of various automated payment mechanisms.
-* provide a more efficient way to manage invoice payment.
+ * serve as base for an easy plug-in of various automated payment mechanisms.
+ * provide a more efficient way to manage invoice payment.
Warning:
--------
"author" : 'OpenERP SA',
"summary": 'Supplier & Customer Invoices, Payments',
"description": """
-Account Voucher module includes all the basic requirements of Voucher Entries for Bank, Cash, Sales, Purchase, Expanse, Contra, etc.
-====================================================================================================================================
+eInvoicing & Payments module manage all Voucher Entries such as "Reconciliation Entries", "Adjustment Entries", "Closing or Opening Entries" for Sales, Purchase, Bank, Cash, Expense, Contra.
+==============================================================================================================================================================================================
* Voucher Entry
- * Voucher Receipt
+ * Voucher Receipt [Sales & Purchase]
+ * Voucher Payment [Customer & Supplier]
* Cheque Register
""",
"category": 'Accounting & Finance',
===============================================
In OpenERP, analytic accounts are linked to general accounts but are treated
-totally independently. So you can enter various different analytic operations
+totally independently. So, you can enter various different analytic operations
that have no counterpart in the general financial accounts.
""",
"init_xml" : [],
'category': 'Hidden',
'description': """
This module is for modifying project view to show some data related to the hr_expense module.
-======================================================================================================
""",
"author": "OpenERP S.A.",
'category': 'Hidden',
'description': """
This module is for modifying account analytic view to show some data related to the hr_expense module.
-======================================================================================================
""",
"author": "OpenERP S.A.",
##############################################################################
{
- "name" : "Contract On Project",
+ "name" : "Contract on Project",
"version": "1.1",
"author" : "OpenERP SA",
'category': 'Hidden',
"website" : "http://www.openerp.com",
"depends" : ["project", "account_analytic_analysis"],
"description": """
- Add "Contract Data" in project view.
+Add "Contract Data" in project view.
""",
"init_xml" : [],
"update_xml": ["analytic_contract_project_view.xml"],
This module allows you to define what is the default function of a specific user on a given account.
====================================================================================================
-This is mostly used when a user encodes his timesheet: the values are retrieved and the fields are auto-filled. But the possibility to change these values is still available.
+This is mostly used when a user encodes his timesheet: the values are retrieved
+and the fields are auto-filled. But the possibility to change these values is
+still available.
-Obviously if no data has been recorded for the current account, the default value is given as usual by the employee data so that this module is perfectly compatible with older configurations.
+Obviously if no data has been recorded for the current account, the default
+value is given as usual by the employee data so that this module is perfectly
+compatible with older configurations.
""",
'author': 'OpenERP SA',
===============================================
This module allows you to keep your data confidential for a given database.
-This process is useful if you want to use the migration process and protect
+This process is useful, if you want to use the migration process and protect
your own or your customer’s confidential data. The principle is that you run
an anonymization tool which will hide your confidential data(they are replaced
by ‘XXX’ characters). Then you can send the anonymized database to the migration
{
'name': 'Anonymous',
- 'description': 'Allow anonymous access to OpenERP',
+ 'description': 'Allow anonymous access to OpenERP.',
'author': 'OpenERP SA',
'version': '1.0',
'category': 'Tools',
This module is to configure modules related to an association.
==============================================================
-It installs the profile for associations to manage events, registrations, memberships, membership products (schemes), etc.
+It installs the profile for associations to manage events, registrations, memberships,
+membership products (schemes).
""",
'author': 'OpenERP SA',
'depends': ['base_setup', 'membership', 'event'],
This module lets administrator track every user operation on all the objects of the system.
===========================================================================================
-The administrator can subscribe to rules for read, write and
-delete on objects and can check logs.
+The administrator can subscribe to rules for read, write and delete on objects
+and can check logs.
""",
'author': 'OpenERP SA',
'website': 'http://www.openerp.com',
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
+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.
""",
"website" : "http://www.openerp.com",
"category" : "Tools",
"description": """
-Replaces cleartext passwords in the database with a secure hash
-===============================================================
-For your existing user base, the removal of the cleartext
-passwords occurs immediately when you instal base_crypt.
+Replaces cleartext passwords in the database with a secure hash.
+================================================================
-All passwords will be replaced by a secure, salted, cryptographic
-hash, preventing anyone from reading the original password in
-the database.
+For your existing user base, the removal of the cleartext passwords occurs
+immediately when you instal base_crypt.
-After installing this module it won't be possible to recover a
-forgotten password for your users, the only solution is for an
-admin to set a new password.
+All passwords will be replaced by a secure, salted, cryptographic hash,
+preventing anyone from reading the original password in the database.
-Security Warning
-++++++++++++++++
+After installing this module, it won't be possible to recover a forgotten password
+for your users, the only solution is for an admin to set a new password.
+
+Security Warning:
+-----------------
Installing this module does not mean you can ignore other security measures,
as the password is still transmitted unencrypted on the network, unless you
are using a secure protocol such as XML-RPCS or HTTPS.
+
It also does not protect the rest of the content of the database, which may
contain critical data. Appropriate security measures need to be implemented
by the system administrator in all areas, such as: protection of database
-backups, system files, remote shell access, physical server access, etc.
+backups, system files, remote shell access, physical server access.
-Interation with LDAP authentication
-+++++++++++++++++++++++++++++++++++
+Interation with LDAP authentication:
+------------------------------------
This module is currently not compatible with the ``user_ldap`` module and
will disable LDAP authentication completely if installed at the same time.
-
- """,
+""",
"depends" : ["base"],
"data" : [],
"auto_install": False,
'version': '1.0',
"category": 'Hidden/Dependency',
'description': """
-This module installs the base for IBAN (International Bank Account Number) bank accounts and checks for its validity.
+This module installs the base for IBAN (International Bank Account Number) bank accounts and checks for it's validity.
=====================================================================================================================
-The ability to extract the correctly represented local accounts from IBAN accounts with a single statement.
+The ability to extract the correctly represented local accounts from IBAN accounts
+with a single statement.
""",
'author': 'OpenERP SA',
'website': 'http://www.openerp.com',
This module allows you to create a new module without any development.
======================================================================
-It records all operations on objects during the recording session and
-produce a .ZIP module. So you can create your own module directly from
-the OpenERP client.
+It records all operations on objects during the recording session and produce a
+.ZIP module. So you can create your own module directly from the OpenERP client.
This version works for creating and updating existing records. It recomputes
dependencies and links for all types of widgets (many2one, many2many, ...).
It also support workflows and demo/update data.
-This should help you to easily create reusable and publishable modules
-for custom configurations and demo/testing data.
+This should help you to easily create reusable and publishable modules for custom
+configurations and demo/testing data.
-How to use it:
-Run Administration/Customization/Module Creation/Export Customizations As a Module wizard.
+How to use it?:
+Run Settings/Technical/Module Creation/Export Customizations As a Module wizard.
Select datetime criteria of recording and objects to be recorded and Record module.
""",
'author': 'OpenERP SA',
This module is used along with OpenERP OpenOffice Plugin.
=========================================================
-This module adds wizards to Import/Export .sxw report that
-you can modify in OpenOffice. Once you have modified it you can
-upload the report using the same wizard.
+This module adds wizards to Import/Export .sxw report that you can modify in OpenOffice.
+Once you have modified it you can upload the report using the same wizard.
""",
'author': 'OpenERP SA',
'website': 'http://www.openerp.com',
self.win.doModalDialog("lstFields",self.sValue)
else:
- ErrorDialog("Please insert user define field Field-1 or Field-4","Just go to File->Properties->User Define \nField-1 Eg. http://localhost:8069 \nOR \nField-4 Eg. account.invoice")
+ ErrorDialog("Please insert user define field Field-1 or Field-4","Just go to File->Properties->User Define \nField-1 E.g. http://localhost:8069 \nOR \nField-4 E.g. account.invoice")
self.win.endExecute()
def lstbox_selected(self,oItemEvent):
self.win.doModalDialog("lstFields",self.sValue)
else:
- ErrorDialog("Please insert user define field Field-1 or Field-4","Just go to File->Properties->User Define \nField-1 Eg. http://localhost:8069 \nOR \nField-4 Eg. account.invoice")
+ ErrorDialog("Please insert user define field Field-1 or Field-4","Just go to File->Properties->User Define \nField-1 E.g. http://localhost:8069 \nOR \nField-4 E.g. account.invoice")
self.win.endExecute()
def lstbox_selected(self,oItemEvent):
ErrorDialog(
"Please insert user define field Field-1",
"Just go to File->Properties->User Define \n"
- "Field-1 Eg. http://localhost:8069"
+ "Field-1 E.g. http://localhost:8069"
)
exit(1)
ErrorDialog(
"Please insert user define field Field-1 or Field-4",
"Just go to File->Properties->User Define \n"
- "Field-1 Eg. http://localhost:8069 \n"
+ "Field-1 E.g. http://localhost:8069 \n"
"OR \n"
- "Field-4 Eg. account.invoice"
+ "Field-4 E.g. account.invoice"
)
exit(1)
'description': """
This module handles state and stage. It is derived from the crm_base and
crm_case classes from crm.
+========================================================================
* ``base_state``: state management
* ``base_stage``: stage management
Common base for tools modules.
==============================
-Creates menu link for Tools from where tools like survey, lunch, idea, etc. are accessible if installed.
+Creates menu link for Tools from where tools like survey, lunch, idea are accessible if installed.
""",
"init_xml": [],
"update_xml": [
'version': '1.0',
"category": 'Hidden/Dependency',
'description': """
-VAT validation for Partners' VAT numbers
-========================================
+VAT validation for Partner's VAT numbers.
+=========================================
After installing this module, values entered in the VAT field of Partners will
be validated for all supported countries. The country is inferred from the
Supported countries currently include EU countries, and a few non-EU countries
such as Chile, Colombia, Mexico, Norway or Russia. For unsupported countries,
only the country code will be validated.
-
""",
'author': 'OpenERP SA',
'depends': ['account'],
{
- "name": "Share Calendar using CalDAV",
+ "name": "Share Calendar Using CalDAV",
"version": "1.1",
"depends": [
"base",
=====================================================
This system enables a group of people to intelligently and efficiently manage
-leads, opportunities, meeting, phonecall etc.
+leads, opportunities, meeting, phonecall.
+
It manages key tasks such as communication, identification, prioritization,
assignment, resolution and notification.
The greatest thing about this system is that users don't need to do anything
special. They can just send email to the request tracker. OpenERP will take
care of thanking them for their message, automatically routing it to the
-appropriate staff, and make sure all future correspondence gets to the right
+appropriate staff and make sure all future correspondence gets to the right
place.
The CRM module has a email gateway for the synchronisation interface
between mails and OpenERP.
Creates a dashboard for CRM that includes:
- * Opportunities by Categories (graph)
- * Opportunities by Stage (graph)
+------------------------------------------
+ * List of New Leads
+ * List of My Opportunities
+ * List of My Next Meetings
* Planned Revenue by Stage and User (graph)
+ * Opportunities by Stage (graph)
""",
'author': 'OpenERP SA',
'website': 'http://www.openerp.com',
'active': fields.boolean('Active', help="If the active field is set to "\
"true, it will allow you to hide the sales team without removing it."),
'allow_unlink': fields.boolean('Allow Delete', help="Allows to delete non draft cases"),
- 'change_responsible': fields.boolean('Reassign Escalated', help="When escalating to this team override the saleman with the team leader."),
+ 'change_responsible': fields.boolean('Reassign Escalated', help="When escalating to this team override the salesman with the team leader."),
'user_id': fields.many2one('res.users', 'Team Leader'),
'member_ids':fields.many2many('res.users', 'sale_member_rel', 'section_id', 'member_id', 'Team Members'),
'reply_to': fields.char('Reply-To', size=64, help="The email address put in the 'Reply-To' of all emails sent by OpenERP about cases in this sales team"),
Caldav features in Meeting.
===========================
- * Share meeting with other calendar clients like sunbird
+ * Share meeting with other calendar clients like sunbird
""",
'author': 'OpenERP SA',
'website': 'http://www.openerp.com',
This module allows users to perform segmentation within partners.
=================================================================
-It uses the profiles criteria from the earlier segmentation module and improve it. Thanks to the new concept of questionnaire. You can now regroup questions into a questionnaire and directly use it on a partner.
+It uses the profiles criteria from the earlier segmentation module and improve it.
+Thanks to the new concept of questionnaire. You can now regroup questions into a
+questionnaire and directly use it on a partner.
-It also has been merged with the earlier CRM & SRM segmentation tool because they were overlapping.
+It also has been merged with the earlier CRM & SRM segmentation tool because they
+were overlapping.
- * Note: this module is not compatible with the module segmentation, since it's the same which has been renamed.
+ * Note: this module is not compatible with the module segmentation, since
+ it's the same which has been renamed.
""",
'author': 'OpenERP SA',
'website': 'http://www.openerp.com',
{
"name": "Decimal Precision Configuration",
"description": """
-Configure the price accuracy you need for different kinds of usage: accounting, sales, purchases, etc.
-======================================================================================================
+Configure the price accuracy you need for different kinds of usage: accounting, sales, purchases.
+=================================================================================================
The decimal precision is configured per company.
""",
Allows you to add delivery methods in sale orders and picking.
==============================================================
-You can define your own carrier and delivery grids for prices.
-When creating invoices from picking, OpenERP is able to add and compute the shipping line.
-
- """,
+You can define your own carrier and delivery grids for prices. When creating
+invoices from picking, OpenERP is able to add and compute the shipping line.
+""",
'author': 'OpenERP SA',
'depends': ['sale', 'purchase', 'stock'],
'init_xml': ['delivery_data.xml'],
==============================================
* User Authentication
- * Document Indexation :- .pptx and .docx files are not supported in Windows platform.
+ * Document Indexation:- .pptx and .docx files are not supported in Windows platform.
* Dashboard for Document that includes:
* New Files (list)
* Files by Resource Type (graph)
* Files Size by Month (graph)
ATTENTION:
- - When you install this module in a running company that have already PDF files stored into the database,
- you will lose them all.
+ - When you install this module in a running company that have already PDF
+ files stored into the database, you will lose them all.
- After installing this module PDF's are no longer stored into the database,
but in the servers rootpad like /server/bin/filestore.
""",
could do various things.
Should also consider node<->content, dir<->dir moves etc.
- Move operations, as instructed from APIs (eg. request from DAV) could
+ Move operations, as instructed from APIs (e.g. request from DAV) could
use this function.
"""
raise NotImplementedError(repr(self))
You can then use any compatible browser to remotely see the attachments of OpenObject.
-After installation, the WebDAV server can be controlled by a [webdav] section in the server's config.
+After installation, the WebDAV server can be controlled by a [webdav] section in
+the server's config.
Server Configuration Parameter:
[webdav]
; these options on
Also implements IETF RFC 5785 for services discovery on a http server,
-which needs explicit configuration in openerp-server.conf, too.
+which needs explicit configuration in openerp-server.conf too.
""",
"depends" : ["base", "document"],
"init_xml" : [],
'version': '1.0',
'category': 'Tools',
'description': """
-Provides a common EDI platform that other Applications can use
-==============================================================
+Provides a common EDI platform that other Applications can use.
+===============================================================
-OpenERP specifies a generic EDI format for exchanging business
-documents between different systems, and provides generic
-mechanisms to import and export them.
+OpenERP specifies a generic EDI format for exchanging business documents between
+different systems, and provides generic mechanisms to import and export them.
-More details about OpenERP's EDI format may be found in the
-technical OpenERP documentation at http://doc.openerp.com
+More details about OpenERP's EDI format may be found in the technical OpenERP
+documentation at http://doc.openerp.com.
""",
'author': 'OpenERP SA',
'website': 'http://www.openerp.com',
"category" : "Marketing",
"depends" : ['mail'],
"description": """
-Email Templating (simplified version of the original Power Email by Openlabs)
-=============================================================================
+Email Templating (simplified version of the original Power Email by Openlabs).
+==============================================================================
Lets you design complete email templates related to any OpenERP document (Sale
Orders, Invoices and so on), including sender, recipient, subject, body (HTML and
campaigns on any OpenERP document.
Technical note: only the templating system of the original Power Email by
-Openlabs was kept
-
+Openlabs was kept.
""",
"data": [
'wizard/email_template_preview_view.xml',
This module allows you
* to manage your events and their registrations
- * to use emails to automatically confirm and send acknowledgements for any registration to an event
- * ...
+ * to use emails to automatically confirm and send acknowledgements for any
+ registration to an event
Note that:
- You can define new types of events in
- Association / Configuration / Types of Events
+ Events/Configuration/Types of Events
""",
'author': 'OpenERP SA',
'depends': ['base_setup', 'board', 'email_template', 'google_map'],
'version': '0.1',
'category': 'Tools',
'description': """
- Configure your moodle server
+Configure your moodle server.
+=============================
-With this module you are able to connect your OpenERP with a moodle plateform.
-This module will create courses and students automatically in your moodle plateform to avoid wasting time.
-Now you have a simple way to create training or courses with OpenERP and moodle
+With this module you are able to connect your OpenERP with a moodle platform.
+This module will create courses and students automatically in your moodle platform
+to avoid wasting time.
+Now you have a simple way to create training or courses with OpenERP and moodle.
-
-STEPS TO CONFIGURE
+STEPS TO CONFIGURE:
------------------
-1. activate web service in moodle
+1. Activate web service in moodle.
----------------------------------
->site administration >plugins>web sevices >manage protocols
-activate the xmlrpc web service
+>site administration >plugins >web services >manage protocols activate the xmlrpc web service
->site administration >plugins>web sevices >manage tokens
-create a token
+>site administration >plugins >web services >manage tokens create a token
->site administration >plugins>web sevices >overview
-activate webservice
+>site administration >plugins >web services >overview activate webservice
-2. Create confirmation email with login and password
-----------------------------------------------------
-we strongly suggest you to add those following lines at the bottom of your event confirmation email to communicate the login/password of moodle to your subscribers.
+2. Create confirmation email with login and password.
+-----------------------------------------------------
+We strongly suggest you to add those following lines at the bottom of your event
+confirmation email to communicate the login/password of moodle to your subscribers.
........your configuration text.......
Creating registration with sale orders.
=======================================
-This module allows you to automatize and connect your registration creation with your main sale flow and, therefore, to enable the invoicing feature of registrations.
+This module allows you to automatize and connect your registration creation with
+your main sale flow and therefore, to enable the invoicing feature of registrations.
-It defines a new kind of service products that offers you the possibility to choose an event category associated with it. When you encode a sale order for that product, you will be able to choose an existing event of that category and when you confirm your sale order it will automatically create a registration for this event.
+It defines a new kind of service products that offers you the possibility to
+choose an event category associated with it. When you encode a sale order for
+that product, you will be able to choose an existing event of that category and
+when you confirm your sale order it will automatically create a registration for
+this event.
""",
'author': 'OpenERP SA',
'depends': ['event','sale','sale_crm'],
class sale_order_line(osv.osv):
_inherit = 'sale.order.line'
_columns = {
- 'event_id': fields.many2one('event.event', 'Event', help="Choose an event and it will authomaticaly create a registration for this event"),
+ 'event_id': fields.many2one('event.event', 'Event', help="Choose an event and it will automatically create a registration for this event."),
#those 2 fields are used for dynamic domains and filled by onchange
'event_type_id': fields.related('event_type_id', type='many2one', relation="event.type", string="Event Type"),
'event_ok': fields.related('event_ok', string='event_ok', type='boolean'),
"author" : "OpenERP SA",
"category": 'Tools',
"description": """
-Retrieve incoming email on POP / IMAP servers
-=============================================
+Retrieve incoming email on POP/IMAP servers.
+============================================
-Enter the parameters of your POP/IMAP account(s), and any incoming
-emails on these accounts will be automatically downloaded into your OpenERP
-system. All POP3/IMAP-compatible servers are supported, included those
-that require an encrypted SSL/TLS connection.
+Enter the parameters of your POP/IMAP account(s), and any incoming emails on
+these accounts will be automatically downloaded into your OpenERP system. All
+POP3/IMAP-compatible servers are supported, included those that require an
+encrypted SSL/TLS connection.
-This can be used to easily create email-based workflows for many
-email-enabled OpenERP documents, such as:
+This can be used to easily create email-based workflows for many email-enabled
+OpenERP documents, such as:
- * CRM Leads/Opportunities
- * CRM Claims
- * Project Issues
- * Project Tasks
- * Human Resource Recruitments (Applicants)
- * etc.
+ * CRM Leads/Opportunities
+ * CRM Claims
+ * Project Issues
+ * Project Tasks
+ * Human Resource Recruitments (Applicants)
-Just install the relevant application, and you can assign any of
-these document types (Leads, Project Issues, etc.) to your incoming
-email accounts. New emails will automatically spawn new documents
-of the chosen type, so it's a snap to create a mailbox-to-OpenERP
-integration. Even better: these documents directly act as mini
-conversations synchronized by email. You can reply from within
-OpenERP, and the answers will automatically be collected when
-they come back, and attached to the same *conversation* document.
+Just install the relevant application, and you can assign any of these document
+types (Leads, Project Issues) to your incoming email accounts. New emails will
+automatically spawn new documents of the chosen type, so it's a snap to create a
+mailbox-to-OpenERP integration. Even better: these documents directly act as mini
+conversations synchronized by email. You can reply from within OpenERP, and the
+answers will automatically be collected when they come back, and attached to the
+same *conversation* document.
For more specific needs, you may also assign custom-defined actions
-(technically: Server Actions) to be triggered for each incoming
-mail.
+(technically: Server Actions) to be triggered for each incoming mail.
""",
'website': 'http://www.openerp.com',
'init_xml': [],
'name': 'Google Users',
'version': '1.0',
'category': 'Tools',
- 'description': """The module adds google user in res user""",
+ 'description': """The module adds google user in res user.""",
'author': 'OpenERP SA',
'website': 'http://www.openerp.com',
'depends': ['base'],
"website": "http://www.openerp.com",
"summary": "Hierarchy, Jobs, Departments",
"description": """
-Module for human resource management.
+Module for Human Resource Management.
=====================================
You can manage:
Add all information on the employee form to manage contracts.
=============================================================
- * Marital status,
- * Security number,
- * Place of birth, birth date, ...
+ * Contract
+ * Place of Birth,
+ * Medical Examination Date
+ * Company Vehicle
You can assign several contracts per employee.
""",
Ability to create employees evaluation.
=======================================
-An evaluation can be created by employee for subordinates,
-juniors as well as his manager.The evaluation is done under a plan
-in which various surveys can be created and it can be defined which
-level of employee hierarchy fills what and final review and evaluation
-is done by the manager.Every evaluation filled by the employees can be viewed
-in the form of pdf file. Implements a dashboard for My Current Evaluations
+An evaluation can be created by employee for subordinates, juniors as well as
+his manager. The evaluation is done under a plan in which various surveys can be
+created and it can be defined which level of employee hierarchy fills what and
+final review and evaluation is done by the manager. Every evaluation filled by
+the employees can be viewed in the form of pdf file.
""",
"demo": ["hr_evaluation_demo.xml"],
"data": [
('2','Meet expectations'),
('3','Exceeds expectations'),
('4','Significantly exceeds expectations'),
- ], "Appreciation", help="This is the appreciation on that summarize the evaluation"),
+ ], "Appreciation", help="This is the appreciation on which the evaluation is summarized."),
'survey_request_ids': fields.one2many('hr.evaluation.interview','evaluation_id','Appraisal Forms'),
'plan_id': fields.many2one('hr_evaluation.plan', 'Plan', required=True),
'state': fields.selection([
"summary": "Allocation and Leave Requests, Reporting by Department",
"website": "http://www.openerp.com",
"description": """
-This module allows you to manage leaves and leaves' requests.
+This module allows you to manage leaves and leave's requests.
=============================================================
-Implements a dashboard for human resource management that includes.
+Implements a dashboard for human resource management that includes:
+-------------------------------------------------------------------
* Leaves
Note that:
- - A synchronisation with an internal agenda (use of the CRM module) is possible: in order to automatically create a case when an holiday request is accepted, you have to link the holidays status to a case section. You can set up this info and your colour preferences in
- Human Resources/Configuration/Holidays/Leave Type
- - An employee can make an ask for more off-days by making a new Allocation It will increase his total of that leave type available (if the request is accepted).
+ - A synchronisation with an internal agenda (use of the CRM module) is
+ possible: in order to automatically create a case when an holiday request
+ is accepted, you have to link the holidays status to a case section. You
+ can setup this info and your colour preferences in
+ Human Resources/Configuration/Leave Type
+ - An employee can make an ask for more off-days by making a new Allocation. It will increase his total of that leave type available (if the request is accepted).
- There are two ways to print the employee's holidays:
* The first will allow to choose employees by department and is used by clicking the menu item located in
- Human Resources/Reporting/Holidays/Leaves by Department
+ Reporting/Human Resources/Leaves/Leaves by Department
* The second will allow you to choose the holidays report for specific employees. Go on the list
Human Resources/Human Resources/Employees
then select the ones you want to choose, click on the print icon and select the option
- 'Employee's Holidays'
- - The wizard allows you to choose if you want to print either the Confirmed & Validated holidays or only the Validated ones. These states must be set up by a user from the group 'HR'. You can define these features in the security tab from the user data in
- Administration / Users / Users
+ 'Leaves Summary'
+ - The wizard allows you to choose if you want to print either the Approved & Confirmed holidays or both. These states must be set up by a user from the group 'HR'. You can define these features in the security tab from the user data in
+ Settings/Users/Users
for example, you maybe will do it for the user 'admin'.
""",
'images': ['images/hr_allocation_requests.jpeg', 'images/hr_leave_requests.jpeg', 'images/leaves_analysis.jpeg'],
'name': fields.char('Leave Type', size=64, required=True, translate=True),
'categ_id': fields.many2one('crm.meeting.type', 'Meeting Type',
help='Once a leave is validated, OpenERP will create a corresponding meeting of this type in the calendar.'),
- 'color_name': fields.selection([('red', 'Red'),('blue','Blue'), ('lightgreen', 'Light Green'), ('lightblue','Light Blue'), ('lightyellow', 'Light Yellow'), ('magenta', 'Magenta'),('lightcyan', 'Light Cyan'),('black', 'Black'),('lightpink', 'Light Pink'),('brown', 'Brown'),('violet', 'Violet'),('lightcoral', 'Light Coral'),('lightsalmon', 'Light Salmon'),('lavender', 'Lavender'),('wheat', 'Wheat'),('ivory', 'Ivory')],'Color in Report', required=True, help='This color will be used in the leaves summary located in Reporting\Leaves by Departement'),
+ 'color_name': fields.selection([('red', 'Red'),('blue','Blue'), ('lightgreen', 'Light Green'), ('lightblue','Light Blue'), ('lightyellow', 'Light Yellow'), ('magenta', 'Magenta'),('lightcyan', 'Light Cyan'),('black', 'Black'),('lightpink', 'Light Pink'),('brown', 'Brown'),('violet', 'Violet'),('lightcoral', 'Light Coral'),('lightsalmon', 'Light Salmon'),('lavender', 'Lavender'),('wheat', 'Wheat'),('ivory', 'Ivory')],'Color in Report', required=True, help='This color will be used in the leaves summary located in Reporting\Leaves by Department.'),
'limit': fields.boolean('Allow to Override Limit', help='If you select this checkbox, the system allows the employees to take more leaves than the available ones for this type.'),
'active': fields.boolean('Active', help="If the active field is set to false, it will allow you to hide the leave type without removing it."),
'max_leaves': fields.function(_user_left_days, string='Maximum Allowed', help='This value is given by the sum of all holidays requests with a positive value.', multi='user_left_days'),
* Employee Details
* Employee Contracts
* Passport based Contract
- * Allowances / Deductions
- * Allow to configure Basic / Grows / Net Salary
+ * Allowances/Deductions
+ * Allow to configure Basic/Gross/Net Salary
* Employee Payslip
* Monthly Payroll Register
* Integrated with Holiday Management
'quantity': fields.char('Quantity', size=256, help="It is used in computation for percentage and fixed amount.For e.g. A rule for Meal Voucher having fixed amount of 1€ per worked day can have its quantity defined in expression like worked_days.WORK100.number_of_days."),
'category_id':fields.many2one('hr.salary.rule.category', 'Category', required=True),
'active':fields.boolean('Active', help="If the active field is set to false, it will allow you to hide the salary rule without removing it."),
- 'appears_on_payslip': fields.boolean('Appears on Payslip', help="Used for the display of rule on payslip"),
+ 'appears_on_payslip': fields.boolean('Appears on Payslip', help="Used to display the salary rule on payslip."),
'parent_rule_id':fields.many2one('hr.salary.rule', 'Parent Salary Rule', select=True),
'company_id':fields.many2one('res.company', 'Company', required=False),
'condition_select': fields.selection([('none', 'Always True'),('range', 'Range'), ('python', 'Python Expression')], "Condition Based on", required=True),
'version': '1.0',
'category': 'Human Resources',
'description': """
-Generic Payroll system Integrated with Accountings.
+Generic Payroll system Integrated with Accounting.
===================================================
* Expense Encoding
_columns = {
'name': fields.char('Name', size=64, required=True, translate=True),
'sequence': fields.integer('Sequence', help="Gives the sequence order when displaying a list of stages."),
- 'department_id':fields.many2one('hr.department', 'Specific to a Department', help="Stages of the recruitment process may be different per department. If this stage is common to all departments, keep tempy this field."),
- 'state': fields.selection(AVAILABLE_STATES, 'State', required=True, help="The related state for the stage. The state of your document will automatically change regarding the selected stage. Example, a stage is related to the state 'Close', when your document reach this stage, it will be automatically closed."),
+ 'department_id':fields.many2one('hr.department', 'Specific to a Department', help="Stages of the recruitment process may be different per department. If this stage is common to all departments, keep this field empty."),
+ 'state': fields.selection(AVAILABLE_STATES, 'State', required=True, help="The related state for the stage. The state of your document will automatically change according to the selected stage. Example, a stage is related to the state 'Close', when your document reach this stage, it will be automatically closed."),
'fold': fields.boolean('Hide in views if empty', help="This stage is not visible, for example in status bar or kanban view, when there are no records in that stage to display."),
'requirements': fields.text('Requirements'),
}
Lots of reporting on time and employee tracking are provided.
-It is completely integrated with the cost accounting module. It allows you
-to set up a management by affair.
+It is completely integrated with the cost accounting module. It allows you to set
+up a management by affair.
""",
'author': 'OpenERP SA',
'website': 'http://www.openerp.com',
'name': 'Invoice on Timesheets',
'version': '1.0',
'category': 'Sales Management',
- 'description': """Generate your Invoices from Expenses, Timesheet Entries, ...
+ 'description': """
+Generate your Invoices from Expenses, Timesheet Entries.
+========================================================
+
Module to generate invoices based on costs (human resources, expenses, ...).
-============================================================================
You can define price lists in analytic account, make some theoretical revenue
-reports, etc.""",
+reports.""",
'author': 'OpenERP SA',
'website': 'http://www.openerp.com',
'images': ['images/hr_bill_task_work.jpeg','images/hr_type_of_invoicing.jpeg'],
_inherit = "account.analytic.account"
_columns = {
'pricelist_id': fields.many2one('product.pricelist', 'Pricelist',
- help="The product to invoice is defined on the employee form, the price will be deduced by this pricelist on the product."),
+ help="The product to invoice is defined on the employee form, the price will be deducted by this pricelist on the product."),
'amount_max': fields.float('Max. Invoice Price',
help="Keep empty if this contract is not limited to a total fixed price."),
'amount_invoiced': fields.function(_invoiced_calc, string='Invoiced Amount',
'time': fields.boolean('Time spent', help='The time of each work done will be displayed on the invoice'),
'name': fields.boolean('Description', help='The detail of each work done will be displayed on the invoice'),
'price': fields.boolean('Cost', help='The cost of each work done will be displayed on the invoice. You probably don\'t want to check this'),
- 'product': fields.many2one('product.product', 'Product', help='Complete this field only if you want to force to use a specific product. Keep empty to use the real product that comes from the cost.'),
+ 'product': fields.many2one('product.product', 'Product', help='Fill this field only if you want to force to use a specific product. Keep empty to use the real product that comes from the cost.'),
}
_defaults = {
This module helps you to easily encode and validate timesheet and attendances within the same view.
===================================================================================================
-The upper part of the view is for attendances and track (sign in/sign out) events.
-The lower part is for timesheet.
+ * It will maintain attendances and track (sign in/sign out) events.
+ * Track the timesheet lines.
Other tabs contains statistics views to help you analyse your
time or the time of your team:
-* Time spent by day (with attendances)
-* Time spent by project
+ * Time spent by day (with attendances)
+ * Time spent by project
This module also implements a complete timesheet validation process:
-* Draft sheet
-* Confirmation at the end of the period by the employee
-* Validation by the project manager
+ * Draft sheet
+ * Confirmation at the end of the period by the employee
+ * Validation by the project manager
The validation can be configured in the company:
-* Period size (day, week, month, year)
-* Maximal difference between timesheet and attendances
+ * Period size (day, week, month, year)
+ * Maximal difference between timesheet and attendances
""",
'author': 'OpenERP SA',
'website': 'http://www.openerp.com',
'version': '0.1',
'category': 'Tools',
'description': """
-This module allows your user to easily and efficiently participate in enterprise innovation.
-============================================================================================
+This module allows user to easily and efficiently participate in enterprise innovation.
+=======================================================================================
It allows everybody to express ideas about different subjects.
Then, other users can comment on these ideas and vote for particular ideas.
##############################################################################
{
- 'name': 'Framework for complex import',
+ 'name': 'Framework for Complex Import',
'version': '0.9',
'category': 'Hidden/Dependency',
'description': """
- This module provide a class import_framework to help importing
- complex data from other software
+This module provide a class import_framework to help importing complex data from
+other software.
""",
'author': 'OpenERP SA',
'website': 'http://www.openerp.com',
'name': 'Google Import',
'version': '1.0',
'category': 'Customer Relationship Management',
- 'description': """The module adds google contact in partner address and add google calendar events details in Meeting""",
+ 'description': """The module adds google contact in partner address and add google calendar events details in Meeting.""",
'author': 'OpenERP SA',
'website': 'http://www.openerp.com',
'depends': ['base', 'import_base', 'google_base_account', 'base_calendar'],
'name': 'SugarCRM Import',
'version': '1.0',
'category': 'Customer Relationship Management',
- 'description': """This Module Import SugarCRM "Leads", "Opportunities", "Users", "Accounts",
- "Contacts", "Employees", Meetings, Phonecalls, Emails, and Project, Project Tasks Data into OpenERP Module.""",
+ 'description': """
+This Module Import SugarCRM Leads, Opportunities, Users, Accounts, Contacts, Employees,
+Meetings, Phonecalls, Emails, Project and Project Tasks Data into OpenERP Module.""",
'author': 'OpenERP SA',
'website': 'http://www.openerp.com',
'depends': ['import_base','crm', 'document'],
{
- "name" : "Document Management System",
+ "name" : "Knowledge Management System",
"version" : "1.0",
"depends" : ["base","base_setup"],
"author" : "OpenERP SA",
"website" : "http://www.conexus.at",
"category" : "Localization/Account Charts",
"depends" : ["account_chart", 'base_vat'],
- "description": "This module provides the standard Accounting Chart for Austria which is based on the Template from BMF.gv.at. Please keep in mind that you should review and adapt it with your Accountant, before using it in a live Environment.",
+ "description": """
+This module provides the standard Accounting Chart for Austria which is based on
+the Template from BMF.gv.at. Please keep in mind that you should review and adapt
+it with your Accountant, before using it in a live Environment.""",
"demo_xml" : [],
"update_xml" : ['account_tax_code.xml',"account_chart.xml",'account_tax.xml',"l10n_chart_at_wizard.xml"],
"auto_install": False,
After installing this module, the Configuration wizard for accounting is launched.
* We have the account templates which can be helpful to generate Charts of Accounts.
- * On that particular wizard, you will be asked to pass the name of the company, the chart template to follow, the no. of digits to generate, the code for your account and bank account, currency to create journals.
+ * On that particular wizard, you will be asked to pass the name of the company,
+ the chart template to follow, the no. of digits to generate, the code for your
+ account and bank account, currency to create journals.
Thus, the pure copy of Chart Template is generated.
Wizards provided by this module:
- * Partner VAT Intra: Enlist the partners with their related VAT and invoiced amounts.Prepares an XML file format.
- Path to access : Accounting/Reporting//Legal Statements/Belgium Statements/Partner VAT Listing
- * Periodical VAT Declaration: Prepares an XML file for Vat Declaration of the Main company of the User currently Logged in.
- Path to access : Accounting/Reporting/Legal Statements/Belgium Statements/Periodical VAT Declaration
- * Annual Listing Of VAT-Subjected Customers: Prepares an XML file for Vat Declaration of the Main company of the User currently Logged in.Based on Fiscal year
- Path to access : Accounting/Reporting/Legal Statements/Belgium Statements/Annual Listing Of VAT-Subjected Customers
+ * Partner VAT Intra: Enlist the partners with their related VAT and invoiced
+ amounts. Prepares an XML file format.
+ Path to access : Invoicing/Reporting/Legal Reports/Belgium Statements/Partner VAT Intra
+ * Periodical VAT Declaration: Prepares an XML file for Vat Declaration of
+ the Main company of the User currently Logged in.
+ Path to access : Invoicing/Reporting/Legal Reports/Belgium Statements/Periodical VAT Declaration
+ * Annual Listing Of VAT-Subjected Customers: Prepares an XML file for Vat
+ Declaration of the Main company of the User currently Logged in Based on
+ Fiscal year.
+ Path to access : Invoicing/Reporting/Legal Reports/Belgium Statements/Annual Listing Of VAT-Subjected Customers
""",
'author': 'Noviat & OpenERP SA',
'tax_code_id': fields.many2one('account.tax.code', 'Tax Code', domain=[('parent_id', '=', False)], required=True),
'msg': fields.text('File created', size=64, readonly=True),
'file_save': fields.binary('Save File'),
- 'ask_restitution': fields.boolean('Ask Restitution',help='It indicates whether a resitution is to made or not?'),
+ 'ask_restitution': fields.boolean('Ask Restitution',help='It indicates whether a restitution is to made or not?'),
'ask_payment': fields.boolean('Ask Payment',help='It indicates whether a payment is to made or not?'),
'client_nihil': fields.boolean('Last Declaration, no clients in client listing', help='Tick this case only if it concerns only the last statement on the civil or cessation of activity: ' \
'no clients to be included in the client listing.'),
'test_xml': fields.boolean('Test XML file', help="Sets the XML output as test file"),
'mand_id' : fields.char('Reference', size=14, help="Reference given by the Representative of the sending company."),
'msg': fields.text('File created', size=14, readonly=True),
- 'no_vat': fields.text('Partner With No VAT', size=14, readonly=True, help="The Partner whose VAT number is not defined they doesn't include in XML File."),
+ 'no_vat': fields.text('Partner With No VAT', size=14, readonly=True, help="The Partner whose VAT number is not defined and they are not included in XML File."),
'file_save' : fields.binary('Save File', readonly=True),
'country_ids': fields.many2many('res.country', 'vat_country_rel', 'vat_id', 'country_id', 'European Countries'),
'comments': fields.text('Comments'),
'depends': ['hr_payroll'],
'version': '1.0',
'description': """
-Belgian Payroll Rules
-=====================
+Belgian Payroll Rules.
+======================
* Employee Details
* Employee Contracts
* Passport based Contract
- * Allowances / Deductions
- * Allow to configure Basic / Grows / Net Salary
+ * Allowances/Deductions
+ * Allow to configure Basic/Gross/Net Salary
* Employee Payslip
* Monthly Payroll Register
* Integrated with Holiday Management
'depends': ['l10n_be_hr_payroll', 'hr_payroll_account', 'l10n_be'],
'version': '1.0',
'description': """
-Accounting Data for Belgian Payroll Rules
+Accounting Data for Belgian Payroll Rules.
""",
'auto_install': True,
- Rename 'reference' field labels to 'Communication'
- Add support for Belgian Structured Communication
-A Structured Communication can be generated automatically on outgoing invoices according to the following algorithms:
+A Structured Communication can be generated automatically on outgoing invoices
+according to the following algorithms:
+
1) Random : +++RRR/RRRR/RRRDD+++
R..R = Random Digits, DD = Check Digits
2) Date : +++DOY/YEAR/SSSDD+++
3) Customer Reference +++RRR/RRRR/SSSDDD+++
R..R = Customer Reference without non-numeric characters, SSS = Sequence Number, DD = Check Digits)
-The preferred type of Structured Communication and associated Algorithm can be specified on the Partner records.
-A 'random' Structured Communication will generated if no algorithm is specified on the Partner record.
+The preferred type of Structured Communication and associated Algorithm can be
+specified on the Partner records. A 'random' Structured Communication will
+generated if no algorithm is specified on the Partner record.
""",
'depends': ['account'],
'name': 'Brazilian - Accounting',
'category': 'Localization/Account Charts',
'description': """
-Base module for the Brazilian localization
-==========================================
+Base module for the Brazilian localization.
+===========================================
This module consists in:
- Tax Situation Code (CST) required for the electronic fiscal invoicing (NFe)
-The field tax_discount has also been added in the account.tax.template and account.tax objects to allow the proper computation of some Brazilian VATs such as ICMS. The chart of account creation wizard has been extended to propagate those new data properly.
+The field tax_discount has also been added in the account.tax.template and account.tax
+objects to allow the proper computation of some Brazilian VATs such as ICMS. The
+chart of account creation wizard has been extended to propagate those new data properly.
-It's important to note however that this module lack many implementations to use OpenERP properly in Brazil. Those implementations (such as the electronic fiscal Invoicing which is already operational) are brought by more than 15 additional modules of the Brazilian Launchpad localization project https://launchpad.net/openerp.pt-br-localiz and their dependencies in the extra addons branch. Those modules aim at not breaking with the remarkable OpenERP modularity, this is why they are numerous but small. One of the reasons for maintaining those modules apart is that Brazilian Localization leaders need commit rights agility to complete the localization as companies fund the remaining legal requirements (such as soon fiscal ledgers, accounting SPED, fiscal SPED and PAF ECF that are still missing as September 2011). Those modules are also strictly licensed under AGPL V3 and today don't come with any additional paid permission for online use of 'private modules'.""",
+It's important to note however that this module lack many implementations to use
+OpenERP properly in Brazil. Those implementations (such as the electronic fiscal
+Invoicing which is already operational) are brought by more than 15 additional
+modules of the Brazilian Launchpad localization project
+https://launchpad.net/openerp.pt-br-localiz and their dependencies in the extra
+addons branch. Those modules aim at not breaking with the remarkable OpenERP
+modularity, this is why they are numerous but small. One of the reasons for
+maintaining those modules apart is that Brazilian Localization leaders need commit
+rights agility to complete the localization as companies fund the remaining legal
+requirements (such as soon fiscal ledgers, accounting SPED, fiscal SPED and PAF
+ECF that are still missing as September 2011). Those modules are also strictly
+licensed under AGPL V3 and today don't come with any additional paid permission
+for online use of 'private modules'.""",
'license': 'AGPL-3',
'author': 'Akretion, OpenERP Brasil',
'website': 'http://openerpbrasil.org',
"description" : """
Swiss localisation :
- DTA generation for a lot of payment types
- - BVR management (number generation, report, etc..)
- - Import account move from the bank file (like v11 etc..)
+ - BVR management (number generation, report.)
+ - Import account move from the bank file (like v11)
- Simplify the way you handle the bank statement for reconciliation
You can also add ZIP and bank completion with:
------------------------------------------------------------------------
-Module incluant la localisation Suisse de TinyERP revu et corrigé par Camptocamp. Cette nouvelle version
-comprend la gestion et l'émissionde BVR, le paiement électronique via DTA (pour les banques, le système postal est en développement)
-et l'import du relevé de compte depuis la banque de manière automatisée.
-De plus, nous avons intégré la définition de toutes les banques Suisses(adresse, swift et clearing).
+Module incluant la localisation Suisse de TinyERP revu et corrigé par Camptocamp.
+Cette nouvelle version comprend la gestion et l'émissionde BVR, le paiement
+électronique via DTA (pour les banques, le système postal est en développement)
+et l'import du relevé de compte depuis la banque de manière automatisée. De plus,
+nous avons intégré la définition de toutes les banques Suisses(adresse, swift et clearing).
Par ailleurs, conjointement à ce module, nous proposons la complétion NPA:
--------------------------------------------------------------------------
TODO :
-- Implement bvr import partial reconciliation
-- Replace wizard by osv_memory when possible
-- Add mising HELP
-- Finish code comment
-- Improve demo data
-
+ - Implement bvr import partial reconciliation
+ - Replace wizard by osv_memory when possible
+ - Add mising HELP
+ - Finish code comment
+ - Improve demo data
""",
"version": "6.1",
"website":"http://openerp-china.org",
"url":"http://code.google.com/p/openerp-china/source/browse/#svn/trunk/l10n_cn",
"description": """
- 添加中文省份数据
- 科目类型\会计科目表模板\增值税\辅助核算类别\管理会计凭证簿\财务会计凭证簿
- ============================================================
+添加中文省份数据
+科目类型\会计科目表模板\增值税\辅助核算类别\管理会计凭证簿\财务会计凭证簿
+============================================================
""",
"depends" : ["base","account"],
'init_xml': [
=================================
Includes:
-* account.type
-* account.account.template
-* account.tax.template
-* account.tax.code.template
-* account.chart.template
+ * account.type
+ * account.account.template
+ * account.tax.template
+ * account.tax.code.template
+ * account.chart.template
-Everything is in English with Spanish translation. Further translations are welcome, please go to
-http://translations.launchpad.net/openerp-costa-rica
+Everything is in English with Spanish translation. Further translations are welcome,
+please go to http://translations.launchpad.net/openerp-costa-rica.
""",
'depends': ['account', 'account_chart', 'base'],
'init_xml': [],
Spanish Charts of Accounts (PGCE 2008).
=======================================
-* Defines the following chart of account templates:
- * Spanish General Chart of Accounts 2008.
- * Spanish General Chart of Accounts 2008 for small and medium companies.
-* Defines templates for sale and purchase VAT.
-* Defines tax code templates.
+ * Defines the following chart of account templates:
+ * Spanish General Chart of Accounts 2008
+ * Spanish General Chart of Accounts 2008 for small and medium companies
+ * Defines templates for sale and purchase VAT
+ * Defines tax code templates
-Note: You should install the l10n_ES_account_balance_report module
-for yearly account reporting (balance, profit & losses).
+Note: You should install the l10n_ES_account_balance_report module for yearly
+ account reporting (balance, profit & losses).
""",
"license" : "GPL-3",
"depends" : ["account", "base_vat", "base_iban"],
This is the module to manage the accounting chart for France in OpenERP.
========================================================================
-This module applies to companies based in France mainland. It doesn't apply to companies based in the DOM-TOMs (Guadeloupe, Martinique, Guyane, Réunion, Mayotte, etc...)
+This module applies to companies based in France mainland. It doesn't apply to
+companies based in the DOM-TOMs (Guadeloupe, Martinique, Guyane, Réunion, Mayotte).
-This localisation module creates the VAT taxes of type "tax included" for purchases (it is notably required when you use the module "hr_expense"). Beware that these "tax included" VAT taxes are not managed by the fiscal positions provided by this module (because it is complex to manage both "tax excluded" and "tax included" scenarios in fiscal positions).
+This localisation module creates the VAT taxes of type "tax included" for purchases
+(it is notably required when you use the module "hr_expense"). Beware that these
+"tax included" VAT taxes are not managed by the fiscal positions provided by this
+module (because it is complex to manage both "tax excluded" and "tax included"
+scenarios in fiscal positions).
-This localisation module doesn't properly handle the scenario when a France-mainland company sells services to a company based in the DOMs. We could manage it in the fiscal positions, but it would require to differentiate between "product" VAT taxes and "service" VAT taxes. We consider that it is too "heavy" to have this by default in l10n_fr ; companies that sell services to DOM-based companies should update the configuration of their taxes and fiscal positions manually.
+This localisation module doesn't properly handle the scenario when a France-mainland
+company sells services to a company based in the DOMs. We could manage it in the
+fiscal positions, but it would require to differentiate between "product" VAT taxes
+and "service" VAT taxes. We consider that it is too "heavy" to have this by default
+in l10n_fr; companies that sell services to DOM-based companies should update the
+configuration of their taxes and fiscal positions manually.
Credits: Sistheo, Zeekom, CrysaLEAD, Akretion and Camptocamp.
""",
'depends': ['hr_payroll', 'l10n_fr'],
'version': '1.0',
'description': """
-French Payroll Rules
-=======================
+French Payroll Rules.
+=====================
- -Configuration of hr_payroll for french localization
- -All main contributions rules for french payslip, for 'cadre' and 'non-cadre'
- -New payslip report
+ - Configuration of hr_payroll for French localization
+ - All main contributions rules for French payslip, for 'cadre' and 'non-cadre'
+ - New payslip report
- TODO :
- -Integration with holidays module for deduction and allowance
- -Integration with hr_payroll_account for the automatic account_move_line creation from the payslip
- -Continue to integrate the contribution. Only the main contribution are currently implemented
- -Remake the report under webkit
- -The payslip.line with appears_in_payslip = False should appears in the payslip interface, but not in the payslip report
+TODO :
+ - Integration with holidays module for deduction and allowance
+ - Integration with hr_payroll_account for the automatic account_move_line
+ creation from the payslip
+ - Continue to integrate the contribution. Only the main contribution are
+ currently implemented
+ - Remake the report under webkit
+ - The payslip.line with appears_in_payslip = False should appears in the
+ payslip interface, but not in the payslip report
""",
'active': False,
"category": 'Hidden/Dependency',
'description': '''
This module lets users enter the banking details of Partners in the RIB format (French standard for bank accounts details).
-RIB Bank Accounts can be entered in the "Accounting" tab of the Partner form by specifying the account type "RIB". The four standard RIB fields will then become mandatory:
-- Bank Code
-- Office Code
-- Account number
-- RIB key
-As a safety measure, OpenERP will check the RIB key whenever a RIB is saved, and will refuse to record the data if the key is incorrect. Please bear in mind that this can only happen when the user presses the "save" button, for example on the Partner Form.
-Since each bank account may relate to a Bank, users may enter the RIB Bank Code in the Bank form - it will the pre-fill the Bank Code on the RIB when they select the Bank.
-To make this easier, this module will also let users find Banks using their RIB code.
+===========================================================================================================================
-The module base_iban can be a useful addition to this module, because French banks are now progressively adopting the international IBAN format instead of the RIB format.
-The RIB and IBAN codes for a single account can be entered by recording two Bank Accounts in OpenERP: the first with the type "RIB", the second with the type "IBAN".
+RIB Bank Accounts can be entered in the "Accounting" tab of the Partner form by specifying
+the account type "RIB". The four standard RIB fields will then become mandatory:
+ - Bank Code
+ - Office Code
+ - Account number
+ - RIB key
+As a safety measure, OpenERP will check the RIB key whenever a RIB is saved, and
+will refuse to record the data if the key is incorrect. Please bear in mind that
+this can only happen when the user presses the "save" button, for example on the
+Partner Form. Since each bank account may relate to a Bank, users may enter the
+RIB Bank Code in the Bank form - it will the pre-fill the Bank Code on the RIB
+when they select the Bank. To make this easier, this module will also let users
+find Banks using their RIB code.
+
+The module base_iban can be a useful addition to this module, because French banks
+are now progressively adopting the international IBAN format instead of the RIB format.
+The RIB and IBAN codes for a single account can be entered by recording two Bank
+Accounts in OpenERP: the first with the type "RIB", the second with the type "IBAN".
''',
'author' : u'Numérigraphe SARL',
'depends': ['account', 'base_iban'],
This is the base module to manage the accounting chart for Guatemala.
=====================================================================
-Agrega una nomenclatura contable para Guatemala. También icluye impuestos y la moneda del Quetzal. -- Adds accounting chart for Guatemala. It also includes taxes and the Quetzal currency""",
+Agrega una nomenclatura contable para Guatemala. También icluye impuestos y
+la moneda del Quetzal. -- Adds accounting chart for Guatemala. It also includes
+taxes and the Quetzal currency.""",
'author': 'José Rodrigo Fernández Menegazzo',
'website': 'http://solucionesprisma.com/',
'depends': ['base', 'account', 'account_chart'],
'name': 'Honduras - Accounting',
'version': '0.1',
'category': 'Localization/Account Charts',
- 'description': """Agrega una nomenclatura contable para Honduras. También incluye impuestos y la moneda Lempira. -- Adds accounting chart for Honduras. It also includes taxes and the Lempira currency""",
+ 'description': """
+Agrega una nomenclatura contable para Honduras. También incluye impuestos y la
+moneda Lempira. -- Adds accounting chart for Honduras. It also includes taxes
+and the Lempira currency.""",
'author': 'Salvatore Josue Trimarchi Pinto',
'website': 'http://trimarchi.co.cc',
'depends': ['base', 'account', 'account_chart'],
"name": "Indian - Accounting",
"version": "1.0",
"description": """
-Indian Accounting : Chart of Account.
-=====================================
+Indian Accounting: Chart of Account.
+====================================
Indian accounting chart and localization.
""",
This is the base module to manage the accounting chart for Luxembourg.
======================================================================
- * the KLUWER Chart of Accounts,
+ * the KLUWER Chart of Accounts
* the Tax Code Chart for Luxembourg
* the main taxes used in Luxembourg""",
'author': 'OpenERP SA',
This is the base module to manage the accounting chart for Maroc.
=================================================================
-Ce Module charge le modèle du plan de comptes standard Marocain et permet de générer les états comptables aux normes marocaines (Bilan, CPC (comptes de produits et charges), balance générale à 6 colonnes, Grand livre cumulatif...). L'intégration comptable a été validé avec l'aide du Cabinet d'expertise comptable Seddik au cours du troisième trimestre 2010""",
+Ce Module charge le modèle du plan de comptes standard Marocain et permet de
+générer les états comptables aux normes marocaines (Bilan, CPC (comptes de
+produits et charges), balance générale à 6 colonnes, Grand livre cumulatif...).
+L'intégration comptable a été validé avec l'aide du Cabinet d'expertise comptable
+Seddik au cours du troisième trimestre 2010.""",
"website": "http://www.kazacube.com",
"depends" : ["base", "account"],
"init_xml" : [],
"author" : "OpenERP SA",
"category": 'Hidden/Dependency',
"description": """
- * Multi language support for Chart of Accounts, Taxes, Tax Codes , Journals, Accounting Templates,
- Analytic Chart of Accounts and Analytic Journals.
+ * Multi language support for Chart of Accounts, Taxes, Tax Codes, Journals,
+ Accounting Templates, Analytic Chart of Accounts and Analytic Journals.
* Setup wizard changes
- - Copy translations for COA, Tax, Tax Code and Fiscal Position from templates to target objects.
+ - Copy translations for COA, Tax, Tax Code and Fiscal Position from
+ templates to target objects.
""",
'website': 'http://www.openerp.com',
'init_xml': [],
=============================================================================
Read changelog in file __openerp__.py for version information.
-Dit is een basismodule om een uitgebreid grootboek- en BTW schema voor Nederlandse bedrijven te installeren in OpenERP versie 5.
+Dit is een basismodule om een uitgebreid grootboek- en BTW schema voor
+Nederlandse bedrijven te installeren in OpenERP versie 5.
-De BTW rekeningen zijn waar nodig gekoppeld om de juiste rapportage te genereren, denk b.v. aan intracommunautaire verwervingen
-waarbij u 19% BTW moet opvoeren, maar tegelijkertijd ook 19% als voorheffing weer mag aftrekken.
+De BTW rekeningen zijn waar nodig gekoppeld om de juiste rapportage te genereren,
+denk b.v. aan intracommunautaire verwervingen waarbij u 19% BTW moet opvoeren,
+maar tegelijkertijd ook 19% als voorheffing weer mag aftrekken.
Na installatie van deze module word de configuratie wizard voor "Accounting" aangeroepen.
- * U krijgt een lijst met grootboektemplates aangeboden waarin zich ook het Nederlandse grootboekschema bevind.
+ * U krijgt een lijst met grootboektemplates aangeboden waarin zich ook het
+ Nederlandse grootboekschema bevind.
- * Als de configuratie wizard start, wordt u gevraagd om de naam van uw bedrijf in te voeren, welke grootboekschema te installeren, uit hoeveel cijfers een grootboekrekening mag bestaan, het rekeningnummer van uw bank en de currency om Journalen te creeren.
+ * Als de configuratie wizard start, wordt u gevraagd om de naam van uw bedrijf
+ in te voeren, welke grootboekschema te installeren, uit hoeveel cijfers een
+ grootboekrekening mag bestaan, het rekeningnummer van uw bank en de currency
+ om Journalen te creeren.
-Let op!! -> De template van het Nederlandse rekeningschema is opgebouwd uit 4 cijfers. Dit is het minimale aantal welk u moet invullen, u mag het aantal verhogen. De extra cijfers worden dan achter het rekeningnummer aangevult met "nullen"
-
- * Dit is dezelfe configuratie wizard welke aangeroepen kan worden via Financial Management/Configuration/Financial Accounting/Financial Accounts/Generate Chart of Accounts from a Chart Template.
+Let op!! -> De template van het Nederlandse rekeningschema is opgebouwd uit 4
+cijfers. Dit is het minimale aantal welk u moet invullen, u mag het aantal verhogen.
+De extra cijfers worden dan achter het rekeningnummer aangevult met "nullen".
""",
"author" : "Veritos - Jan Verlaan",
"name": "Peru Localization Chart Account",
"version": "1.0",
"description": """
-Peruvian accounting chart and tax localization. Acording the PCGE 2010
+Peruvian accounting chart and tax localization. Acording the PCGE 2010.
-Plan contable peruano e impuestos de acuerdo a disposiciones vigentes de la SUNAT 2011 (PCGE 2010)
+Plan contable peruano e impuestos de acuerdo a disposiciones vigentes de la
+SUNAT 2011 (PCGE 2010).
""",
"author": ["Cubic ERP"],
"version" : "1.0",
"author" : "Baamtu Senegal",
"category" : "Localization/Account Charts",
- "description": """This module implements the accounting chart for OHADA area.
- It allows any company or association to manage its financial accounting.
- Countries that use OHADA are the following:
+ "description": """
+This module implements the accounting chart for OHADA area.
+===========================================================
+
+It allows any company or association to manage its financial accounting.
+Countries that use OHADA are the following:
Benin, Burkina Faso, Cameroon, Central African Republic, Comoros, Congo,
- Ivory Coast, Gabon, Guinea, Guinea Bissau,
- Equatorial Guinea, Mali, Niger, Replica of Democratic Congo, Senegal, Chad, Togo.
+ Ivory Coast, Gabon, Guinea, Guinea Bissau, Equatorial Guinea, Mali, Niger,
+ Replica of Democratic Congo, Senegal, Chad, Togo.
""",
"website": "http://www.baamtu.com",
"depends" : ["account", "base_vat"],
'category': 'Localization/Account Charts',
'description': """
Türkiye için Tek düzen hesap planı şablonu OpenERP Modülü.
-==============================================================================
+==========================================================
Bu modül kurulduktan sonra, Muhasebe yapılandırma sihirbazı çalışır
- * Sihirbaz sizden hesap planı şablonu, planın kurulacağı şirket,banka hesap bilgileriniz,ilgili para birimi gibi bilgiler isteyecek.
+ * Sihirbaz sizden hesap planı şablonu, planın kurulacağı şirket, banka hesap
+ bilgileriniz, ilgili para birimi gibi bilgiler isteyecek.
""",
'author': 'Ahmet Altınışık',
'maintainer':'https://launchpad.net/~openerp-turkey',
'name': 'UK - Accounting',
'version': '1.0',
'category': 'Localization/Account Charts',
- 'description': """This is the latest UK OpenERP localisation necesary to run OpenERP accounting for UK SME's with:
+ 'description': """
+This is the latest UK OpenERP localisation necessary to run OpenERP accounting
+for UK SME's with:
- a CT600-ready chart of accounts
- VAT100-ready tax structure
- InfoLogic UK counties listing
"author": "OpenERP SA",
"category": 'Localization/Account Charts',
"description": """
- United States - Chart of accounts
+United States - Chart of accounts.
""",
'website': 'http://www.openerp.com',
'init_xml': [],
"category" : "Localization/Account Charts",
"website" : "https://launchpad.net/openerp-uruguay",
"description": """
-General Chart of Accounts
-=========================
+General Chart of Accounts.
+==========================
-Provide Templates for Chart of Accounts, Taxes for Uruguay
+Provide Templates for Chart of Accounts, Taxes for Uruguay.
""",
"license" : "AGPL-3",
{
"name": "Lunch Orders",
"author": "OpenERP SA",
- "Description": """
- The lunch module is for keeping a record of the order placed and payment of the orders.
- =======================================================================================
-
- The products are defined under categories and the payment records are maintained user-wise.
- Every user has a cashbox which keeps track of the amount paid for a particular order.
-
- """,
"version": "0.1",
"depends": ["base_tools"],
"category" : "Tools",
'description': """
- The base module to manage lunch
+The base module to manage lunch.
+================================
- keep track for the Lunch Order ,Cash Moves ,CashBox ,Product.
- Apply Different Category for the product.
+keep track for the Lunch Order, Cash Moves, CashBox, Product. Apply Different
+Category for the product.
""",
"init_xml": [],
"update_xml": [
A bussiness oriented Social Networking with a fully-integrated email
and message management.
=====================================================================
+
The Social Networking module provides an unified social network
abstraction layer allowing applications to display a complete
-communication history on documents.It gives the users the possibility
+communication history on documents. It gives the users the possibility
to read and send messages and emails in an unified way.
It also provides a feeds page combined to a subscription mechanism, that
allows to follow documents, and to be constantly updated about recent
news.
-The main features of the module are :
-
+The main features of the module are:
* a clean and renewed communication history for any OpenERP
- document that can act as a discussion topic,
+ document that can act as a discussion topic,
* a discussion mean on documents,
* a subscription mechanism to be updated about new messages on
interesting documents,
=========================================================================================================================================
The campaigns are dynamic and multi-channels. The process is as follows:
- * Design marketing campaigns like workflows, including email templates to send, reports to print and send by email, custom actions, etc.
- * Define input segments that will select the items that should enter the campaign (e.g leads from certain countries, etc.)
- * Run you campaign in simulation mode to test it real-time or accelerated, and fine-tune it
- * You may also start the real campaign in manual mode, where each action requires manual validation
- * Finally launch your campaign live, and watch the statistics as the campaign does everything fully automatically.
+ * Design marketing campaigns like workflows, including email templates to
+ send, reports to print and send by email, custom actions
+ * Define input segments that will select the items that should enter the
+ campaign (e.g leads from certain countries.)
+ * Run you campaign in simulation mode to test it real-time or accelerated,
+ and fine-tune it
+ * You may also start the real campaign in manual mode, where each action
+ requires manual validation
+ * Finally launch your campaign live, and watch the statistics as the
+ campaign does everything fully automatically.
-While the campaign runs you can of course continue to fine-tune the parameters, input segments, workflow, etc.
+While the campaign runs you can of course continue to fine-tune the parameters,
+input segments, workflow.
-Note: If you need demo data, you can install the marketing_campaign_crm_demo module, but this will also install the CRM application as it depends on CRM Leads.
+Note: If you need demo data, you can install the marketing_campaign_crm_demo
+ module, but this will also install the CRM application as it depends on
+ CRM Leads.
""",
'website': 'http://www.openerp.com',
'init_xml': [],
=========================================================================
It supports different kind of members:
-* Free member
-* Associated member (eg.: a group subscribes to a membership for all subsidiaries)
-* Paid members,
-* Special member prices, ...
+ * Free member
+ * Associated member (e.g.: a group subscribes to a membership for all subsidiaries)
+ * Paid members
+ * Special member prices
It is integrated with sales and accounting to allow you to automatically
invoice and send propositions for membership renewal.
Features:
---------
- * Make to Stock / Make to Order (by line)
+ * Make to Stock/Make to Order (by line)
* Multi-level BoMs, no limit
* Multi-level routing, no limit
* Routing and work center integrated with analytic accounting
- * Scheduler computation periodically / Just In Time module
+ * Scheduler computation periodically/Just In Time module
* Multi-pos, multi-warehouse
* Different reordering policies
* Cost method by product: standard price, average price
* Load forecast on Work Centers
* Print a production order
* Stock forecasts
+ * Cost Structure
Dashboard provided by this module:
----------------------------------
- * List of next production orders
* List of procurements in exception
- * Graph of work center load
+ * List of next production orders
* Graph of stock value variation
""",
'init_xml': [],
'time_stop': fields.float('Time after prod.', help="Time in hours for the cleaning."),
'costs_hour': fields.float('Cost per hour', help="Specify Cost of Work Center per hour."),
'costs_hour_account_id': fields.many2one('account.analytic.account', 'Hour Account', domain=[('type','<>','view')],
- help="Complete this only if you want automatic analytic accounting entries on production orders."),
+ help="Fill this only if you want automatic analytic accounting entries on production orders."),
'costs_cycle': fields.float('Cost per cycle', help="Specify Cost of Work Center per cycle."),
'costs_cycle_account_id': fields.many2one('account.analytic.account', 'Cycle Account', domain=[('type','<>','view')],
- help="Complete this only if you want automatic analytic accounting entries on production orders."),
+ help="Fill this only if you want automatic analytic accounting entries on production orders."),
'costs_journal_id': fields.many2one('account.analytic.journal', 'Analytic Journal'),
'costs_general_account_id': fields.many2one('account.account', 'General Account', domain=[('type','<>','view')]),
'resource_id': fields.many2one('resource.resource','Resource', ondelete='cascade', required=True),
- 'product_id': fields.many2one('product.product','Work Center Product', help="Fill this product to track easily your production costs in the analytic accounting."),
+ 'product_id': fields.many2one('product.product','Work Center Product', help="Fill this product to easily track your production costs in the analytic accounting."),
}
_defaults = {
'capacity_per_cycle': 1.0,
If you install this module, you will not have to run the regular procurement
scheduler anymore (but you still need to run the minimum order point rule
-scheduler, or for example let it run daily.)
+scheduler, or for example let it run daily).
All procurement orders will be processed immediately, which could in some
cases entail a small performance impact.
It may also increase your stock size because products are reserved as soon
as possible and the scheduler time range is not taken into account anymore.
In that case, you can not use priorities any more on the different picking.
-
""",
'author': 'OpenERP SA',
'depends': ['procurement'],
'version': '1.0',
'category': 'Manufacturing',
'description': """
-This module adds state, date_start,date_stop in production order operation lines (in the "Work Centers" tab).
-=============================================================================================================
+This module adds state, date_start, date_stop in manufacturing order operation lines (in the "Work Orders" tab).
+================================================================================================================
Status: draft, confirm, done, cancel
-When finishing/confirming,cancelling production orders set all state lines to the according state
+When finishing/confirming, cancelling manufacturing orders set all state lines
+to the according state.
Create menus:
Manufacturing > Manufacturing > Work Orders
-Which is a view on "Work Centers" lines in production order.
+Which is a view on "Work Orders" lines in manufacturing order.
-Add buttons in the form view of production order under workcenter tab:
+Add buttons in the form view of manufacturing order under workorders tab:
* start (set state to confirm), set date_start
* done (set state to done), set date_stop
* set to draft (set state to draft)
* cancel set state to cancel
-When the production order becomes "ready to produce", operations must
-become 'confirmed'. When the production order is done, all operations
+When the manufacturing order becomes "ready to produce", operations must
+become 'confirmed'. When the manufacturing order is done, all operations
must become done.
-The field delay is the delay(stop date - start date).
-So that we can compare the theoretic delay and real delay.
-
+The field 'Working Hours' is the delay(stop date - start date).
+So, that we can compare the theoretic delay and real delay.
""",
'author': 'OpenERP SA',
'website': 'http://www.openerp.com',
'version': '1.0',
'category': 'Manufacturing',
'description': """
-The aim is to have a complete module to manage all products repairs. The following topics should be covered by this module:
-===========================================================================================================================
+The aim is to have a complete module to manage all products repairs.
+====================================================================
+The following topics should be covered by this module:
* Add/remove products in the reparation
* Impact for stocks
* Invoicing (products and/or services)
_columns = {
'name': fields.char('Repair Reference',size=24, required=True),
'product_id': fields.many2one('product.product', string='Product to Repair', required=True, readonly=True, states={'draft':[('readonly',False)]}),
- 'partner_id' : fields.many2one('res.partner', 'Partner', select=True, help='This field allow you to choose the parner that will be invoiced and delivered'),
+ 'partner_id' : fields.many2one('res.partner', 'Partner', select=True, help='Choose partner for whom the order will be invoiced and delivered.'),
'address_id': fields.many2one('res.partner', 'Delivery Address', domain="[('parent_id','=',partner_id)]"),
'default_address_id': fields.function(_get_default_address, type="many2one", relation="res.partner"),
'prodlot_id': fields.many2one('stock.production.lot', 'Lot Number', select=True, domain="[('product_id','=',product_id)]"),
'move_id': fields.many2one('stock.move', 'Move',required=True, domain="[('product_id','=',product_id)]", readonly=True, states={'draft':[('readonly',False)]}),
'guarantee_limit': fields.date('Guarantee limit', help="The guarantee limit is computed as: last move date + warranty defined on selected product. If the current date is below the guarantee limit, each operation and fee you will add will be set as 'not to invoiced' by default. Note that you can change manually afterwards."),
'operations' : fields.one2many('mrp.repair.line', 'repair_id', 'Operation Lines', readonly=True, states={'draft':[('readonly',False)]}),
- 'pricelist_id': fields.many2one('product.pricelist', 'Pricelist', help='The pricelist comes from the selected partner, by default.'),
+ 'pricelist_id': fields.many2one('product.pricelist', 'Pricelist', help='Pricelist of the selected partner.'),
'partner_invoice_id':fields.many2one('res.partner', 'Invoicing Address'),
'invoice_method':fields.selection([
("none","No Invoice"),
("b4repair","Before Repair"),
("after_repair","After Repair")
], "Invoice Method",
- select=True, required=True, states={'draft':[('readonly',False)]}, readonly=True, help='This field allow you to change the workflow of the repair order. If value selected is different from \'No Invoice\', it also allow you to select the pricelist and invoicing address.'),
+ select=True, required=True, states={'draft':[('readonly',False)]}, readonly=True, help='Selecting \'Before Repair\' or \'After Repair\' will allow you to generate invoice before or after the repair is done respectively. \'No invoice\' means you don\'t want to generate invoice for this repair order.'),
'invoice_id': fields.many2one('account.invoice', 'Invoice', readonly=True),
'picking_id': fields.many2one('stock.picking', 'Picking',readonly=True),
'fees_lines': fields.one2many('mrp.repair.fee', 'repair_id', 'Fees Lines', readonly=True, states={'draft':[('readonly',False)]}),
'internal_notes': fields.text('Internal Notes'),
'quotation_notes': fields.text('Quotation Notes'),
'company_id': fields.many2one('res.company', 'Company'),
- 'deliver_bool': fields.boolean('Deliver', help="Check this box if you want to manage the delivery once the product is repaired. If cheked, it will create a picking with selected product. Note that you can select the locations in the Info tab, if you have the extended view."),
+ 'deliver_bool': fields.boolean('Deliver', help="Check this box if you want to manage the delivery once the product is repaired and create a picking with selected product. Note that you can select the locations in the Info tab, if you have the extended view."),
'invoiced': fields.boolean('Invoiced', readonly=True),
'repaired': fields.boolean('Repaired', readonly=True),
'amount_untaxed': fields.function(_amount_untaxed, string='Untaxed Amount',
Adds enhanced support for (Ether)Pad attachments in the web client.
===================================================================
-Lets the company customize which Pad installation should be used to link to new pads
-(by default, http://ietherpad.com/).
+Lets the company customize which Pad installation should be used to link to new
+pads (by default, http://ietherpad.com/).
""",
'author': 'OpenERP SA',
'website': 'http://openerp.com',
'version': '1.0',
"category": "Project Management",
'description': """
-This module adds a PAD in all project kanban views
-==================================================
+This module adds a PAD in all project kanban views.
""",
'author': 'OpenERP SA',
'website': 'http://www.openerp.com',
'version': '1.0',
'category': 'Hidden/Dependency',
'description': """
-The common interface for pugin.
-=====================================================
-
+The common interface for plug-in.
""",
'author': 'OpenERP SA',
'website': 'http://www.openerp.com',
'description': '''
This module provides the Outlook Plug-in.
=========================================
-Outlook plug-in allows you to select an object that you would like to add
-to your email and its attachments from MS Outlook. You can select a partner, a task,
-a project, an analytical account, or any other object and archive selected
-mail into mail.message with attachments.
+
+Outlook plug-in allows you to select an object that you would like to add to
+your email and its attachments from MS Outlook. You can select a partner, a task,
+a project, an analytical account, or any other object and archive selected mail
+into mail.message with attachments.
''',
'init_xml' : [],
'demo_xml' : [],
{
- 'name': 'Point Of Sale',
+ 'name': 'Point of Sale',
'version': '1.0.1',
'category': 'Point Of Sale',
"sequence": 6,
This module provides a quick and easy sale process.
===================================================
-Main features :
----------------
- * Fast encoding of the sale.
- * Allow to choose one payment mode (the quick way) or to split the payment between several payment mode.
- * Computation of the amount of money to return.
- * Create and confirm picking list automatically.
- * Allow the user to create invoice automatically.
- * Allow to refund former sales.
+Main features:
+--------------
+ * Fast encoding of the sale
+ * Allow to choose one payment mode (the quick way) or to split the payment between several payment mode
+ * Computation of the amount of money to return
+ * Create and confirm picking list automatically
+ * Allow the user to create invoice automatically
+ * Allow to refund former sales
""",
'author': 'OpenERP SA',
'images': ['images/cash_registers.jpeg', 'images/pos_analysis.jpeg','images/register_analysis.jpeg','images/sale_order_pos.jpeg','images/product_pos.jpeg'],
'author' : "OpenERP SA",
'category': 'Portal',
'description': """
-This module defines 'portals' to customize the access to your OpenERP database
-for external users.
+This module defines 'portals' to customize the access to your OpenERP database for external users.
+==================================================================================================
A portal defines customized user menu and access rights for a group of users
-(the ones associated to that portal). It also associates user groups to the
+(the ones associated to that portal). It also associates user groups to the
portal users (adding a group in the portal automatically adds it to the portal
-users, etc). That feature is very handy when used in combination with the
+users). That feature is very handy when used in combination with the
module 'share'.
""",
'website': 'http://www.openerp.com',
This module shows the basic processes involved in the selected modules and in the sequence they occur.
======================================================================================================
-Note: This applies to the modules containing modulename_process_xml
-e.g product/process/product_process_xml
+Note: This applies to the modules containing modulename_process.xml.
+e.g product/process/product_process.xml.
""",
'author': 'OpenERP SA',
==============================================
In the MRP process, procurements orders are created to launch manufacturing
-orders, purchase orders, stock allocations, etc. Procurement orders are
+orders, purchase orders, stock allocations. Procurement orders are
generated automatically by the system and unless there is a problem, the
user will not be notified. In case of problems, the system will raise some
procurement exceptions to inform the user about blocking problems that need
This is the base module for managing products and pricelists in OpenERP.
========================================================================
-Products support variants, different pricing methods, suppliers
-information, make to stock/order, different unit of measures,
-packaging and properties.
+Products support variants, different pricing methods, suppliers information,
+make to stock/order, different unit of measures, packaging and properties.
Pricelists support:
* Multiple-level of discount (by product, category, quantities)
* Compute price based on different criteria:
- * Other pricelist,
- * Cost price,
- * List price,
- * Supplier price, ...
+ * Other pricelist
+ * Cost price
+ * List price
+ * Supplier price
Pricelists preferences by product and/or partners.
_columns = {
'name': fields.char('Name', size=128, required=True, translate=True, select=True),
- 'product_manager': fields.many2one('res.users','Product Manager',help="This is use as task responsible"),
+ 'product_manager': fields.many2one('res.users','Product Manager',help="Responsible for product."),
'description': fields.text('Description',translate=True),
'description_purchase': fields.text('Purchase Description',translate=True),
'description_sale': fields.text('Sale Description',translate=True),
('paid','Paid'),('open_paid','Open and Paid'),('draft_open_paid','Draft, Open and Paid')
], string='Invoice State',multi='product_margin', readonly=True),
'sale_avg_price' : fields.function(_product_margin, type='float', string='Avg. Unit Price', multi='product_margin',
- help="Avg. Price in Customer Invoices)"),
+ help="Avg. Price in Customer Invoices."),
'purchase_avg_price' : fields.function(_product_margin, type='float', string='Avg. Unit Price', multi='product_margin',
help="Avg. Price in Supplier Invoices "),
'sale_num_invoiced' : fields.function(_product_margin, type='float', string='# Invoiced', multi='product_margin',
'purchase_gap' : fields.function(_product_margin, type='float', string='Purchase Gap', multi='product_margin',
help="Normal Cost - Total Cost"),
'turnover' : fields.function(_product_margin, type='float', string='Turnover' ,multi='product_margin',
- help="Sum of Multification of Invoice price and quantity of Customer Invoices"),
+ help="Sum of Multiplication of Invoice price and quantity of Customer Invoices"),
'total_cost' : fields.function(_product_margin, type='float', string='Total Cost', multi='product_margin',
- help="Sum of Multification of Invoice price and quantity of Supplier Invoices "),
+ help="Sum of Multiplication of Invoice price and quantity of Supplier Invoices "),
'sale_expected' : fields.function(_product_margin, type='float', string='Expected Sale', multi='product_margin',
- help="Sum of Multification of Sale Catalog price and quantity of Customer Invoices"),
+ help="Sum of Multiplication of Sale Catalog price and quantity of Customer Invoices"),
'normal_cost' : fields.function(_product_margin, type='float', string='Normal Cost', multi='product_margin',
- help="Sum of Multification of Cost price and quantity of Supplier Invoices"),
+ help="Sum of Multiplication of Cost price and quantity of Supplier Invoices"),
'total_margin' : fields.function(_product_margin, type='float', string='Total Margin', multi='product_margin',
- help="Turnorder - Standard price"),
+ help="Turnover - Standard price"),
'expected_margin' : fields.function(_product_margin, type='float', string='Expected Margin', multi='product_margin',
help="Expected Sale - Normal Cost"),
'total_margin_rate' : fields.function(_product_margin, type='float', string='Total Margin (%)', multi='product_margin',
To this end, a new check box named "Visible Discount" is added to the pricelist form.
Example:
- For the product PC1 and the partner "Asustek": if listprice=450, and the price calculated using Asustek's pricelist is 225
- If the check box is checked, we will have on the sale order line: Unit price=450, Discount=50,00, Net price=225
- If the check box is unchecked, we will have on Sale Order and Invoice lines: Unit price=225, Discount=0,00, Net price=225
+ For the product PC1 and the partner "Asustek": if listprice=450, and the price
+ calculated using Asustek's pricelist is 225. If the check box is checked, we
+ will have on the sale order line: Unit price=450, Discount=50,00, Net price=225.
+ If the check box is unchecked, we will have on Sale Order and Invoice lines:
+ Unit price=225, Discount=0,00, Net price=225.
""",
"depends": ["sale"],
"demo_xml": [],
"author" : "OpenERP SA",
"category" : "Hidden/Dependency",
"description": """
-Installer for extra Hidden like lunch, survey, idea, share, etc.
-================================================================
+Installer for extra Hidden like lunch, survey, idea, share.
+===========================================================
Makes the Extra Hidden Configuration available from where you can install
modules like share, lunch, pad, idea, survey and subscription.
"images": ["images/gantt.png", "images/project_dashboard.jpeg","images/project_task_tree.jpeg","images/project_task.jpeg","images/project.jpeg","images/task_analysis.jpeg"],
"depends": ["base_setup", "base_status", "product", "analytic", "board", "mail", "resource","web_kanban"],
"description": """
-Project management module tracks multi-level projects, tasks, work done on tasks, eso.
-======================================================================================
+Project Management module tracks multi-level projects, tasks, work done on tasks.
+=================================================================================
-It is able to render planning, order tasks, eso.
+It is able to render planning, order tasks.
-Dashboard for project members that includes:
---------------------------------------------
- * List of my open tasks
- * List of my delegated tasks
- * Graph of My Projects: Planned vs Total Hours
+Dashboard for project management that includes:
+-----------------------------------------------
+ * List of My Open Tasks
* Graph of My Remaining Hours by Project
""",
"init_xml": [],
'working_hours_open': fields.float('Avg. Working Hours to Open', readonly=True),
'working_hours_close': fields.float('Avg. Working Hours to Close', readonly=True),
'delay_open': fields.float('Avg. Delay to Open', digits=(16,2), readonly=True, group_operator="avg",
- help="Number of Days to close the project issue"),
+ help="Number of Days to open the project issue."),
'delay_close': fields.float('Avg. Delay to Close', digits=(16,2), readonly=True, group_operator="avg",
help="Number of Days to close the project issue"),
'company_id' : fields.many2one('res.company', 'Company'),
Long Term Project management module that tracks planning, scheduling, resources allocation.
===========================================================================================
-Features
---------
- * Manage Big project.
- * Define various Phases of Project.
- * Compute Phase Scheduling: Compute start date and end date of the phases which are in draft,open and pending state of the project given.
- If no project given then all the draft,open and pending state phases will be taken.
- * Compute Task Scheduling: This works same as the scheduler button on project.phase. It takes the project as argument and computes all the open,draft and pending tasks.
- * Schedule Tasks: All the tasks which are in draft,pending and open state are scheduled with taking the phase's start date
+Features:
+---------
+ * Manage Big project
+ * Define various Phases of Project
+ * Compute Phase Scheduling: Compute start date and end date of the phases
+ which are in draft, open and pending state of the project given. If no
+ project given then all the draft, open and pending state phases will be taken.
+ * Compute Task Scheduling: This works same as the scheduler button on
+ project.phase. It takes the project as argument and computes all the open,
+ draft and pending tasks.
+ * Schedule Tasks: All the tasks which are in draft, pending and open state
+ are scheduled with taking the phase's start date.
""",
"init_xml": [],
"demo_xml": ["project_long_term_demo.xml"],
'task_ids': fields.one2many('project.task', 'phase_id', "Project Tasks", states={'done':[('readonly',True)], 'cancelled':[('readonly',True)]}),
'user_force_ids': fields.many2many('res.users', string='Force Assigned Users'),
'user_ids': fields.one2many('project.user.allocation', 'phase_id', "Assigned Users",states={'done':[('readonly',True)], 'cancelled':[('readonly',True)]},
- help="The ressources on the project can be computed automatically by the scheduler"),
+ help="The resources on the project can be computed automatically by the scheduler."),
'state': fields.selection([('draft', 'New'), ('cancelled', 'Cancelled'),('open', 'In Progress'), ('pending', 'Pending'), ('done', 'Done')], 'Status', readonly=True, required=True,
help='If the phase is created the state \'Draft\'.\n If the phase is started, the state becomes \'In Progress\'.\n If review is needed the phase is in \'Pending\' state.\
\n If the phase is over, the states is set to \'Done\'.'),
"images": ["images/project_mailgate_task.jpeg"],
"depends": ["project", "mail"],
"description": """
-This module can automatically create Project Tasks based on incoming emails
-===========================================================================
+This module can automatically create Project Tasks based on incoming emails.
+============================================================================
Allows creating tasks based on new emails arriving at a given mailbox,
similarly to what the CRM application has for Leads/Opportunities.
-There are two common alternatives to configure the mailbox integration:
-
- * Install the ``fetchmail`` module and configure a new mailbox, then select
- ``Project Tasks`` as the target for incoming emails.
- * Set it up manually on your mail server based on the 'mail gateway' script
- provided in the ``mail`` module - and connect it to the `project.task` model.
-
+There are two common alternatives to configure the mailbox integration:
+ * Install the ``fetchmail`` module and configure a new mailbox, then select
+ ``Project Tasks`` as the target for incoming emails.
+ * Set it up manually on your mail server based on the 'mail gateway' script
+ provided in the ``mail`` module - and connect it to the `project.task` model.
""",
"init_xml": [],
"update_xml": [
'version': '1.0',
"category": "Project Management",
'description': """
-Automatically creates project tasks from procurement lines
-==========================================================
+Automatically creates project tasks from procurement lines.
+===========================================================
-This module will automatically create a new task for each procurement
-order line (e.g. for sale order lines), if the corresponding product
-meets the following characteristics:
+This module will automatically create a new task for each procurement order line
+(e.g. for sale order lines), if the corresponding product meets the following
+characteristics:
- * Type = Service
- * Procurement method (Order fulfillment) = MTO (make to order)
- * Supply/Procurement method = Produce
+ * Product Type = Service
+ * Procurement Method (Order fulfillment) = MTO (Make to Order)
+ * Supply/Procurement Method = Manufacture
If on top of that a projet is specified on the product form (in the Procurement
-tab), then the new task will be created in that specific project.
-Otherwise, the new task will not belong to any project, and may be added to a
-project manually later.
+tab), then the new task will be created in that specific project. Otherwise, the
+new task will not belong to any project, and may be added to a project manually
+later.
When the project task is completed or cancelled, the workflow of the corresponding
-procurement line is updated accordingly. For example if this procurement corresponds
+procurement line is updated accordingly. For example, if this procurement corresponds
to a sale order line, the sale order line will be considered delivered when the
task is completed.
-
""",
'author': 'OpenERP SA',
'website': 'http://www.openerp.com',
Changes dates according to change in project End Date.
======================================================
-If end date of project is changed then the deadline date and start date for all the tasks will change accordingly.
+If end date of project is changed then the deadline date and start date for all
+the tasks will change accordingly.
""",
'author': 'OpenERP SA',
'depends': ['base', 'project'],
Synchronization of project task work entries with timesheet entries.
====================================================================
-This module lets you transfer the entries under tasks defined for Project Management to
-the Timesheet line entries for particular date and particular user with the effect of creating, editing and deleting either ways.
-
+This module lets you transfer the entries under tasks defined for Project
+Management to the Timesheet line entries for particular date and particular user
+with the effect of creating, editing and deleting either ways.
""",
'author': 'OpenERP SA',
'website': 'http://www.openerp.com',
"sequence": 19,
"summary": "Requests for Quotation, Invoicing Control",
'description': """
-Purchase module is for generating a purchase order for purchase of goods from a supplier.
-=========================================================================================
+Purchase Management module is for generating a purchase order for purchase of goods from a supplier.
+====================================================================================================
A supplier invoice is created for the particular purchase order.
Dashboard for purchase management that includes:
- * Current Purchase Orders
- * Draft Purchase Orders
- * Graph for quantity and amount per month
-
+------------------------------------------------
+ * Request for Quotations
+ * Monthly Purchases by Category
""",
'author': 'OpenERP SA',
'website': 'http://www.openerp.com',
]
_columns = {
- 'name': fields.char('Order Reference', size=64, required=True, select=True, help="unique number of the purchase order,computed automatically when the purchase order is created"),
+ 'name': fields.char('Order Reference', size=64, required=True, select=True, help="Unique number of the purchase order, computed automatically when the purchase order is created."),
'origin': fields.char('Source Document', size=64,
help="Reference of the document that generated this purchase order request."
),
'validator' : fields.many2one('res.users', 'Validated by', readonly=True),
'notes': fields.text('Terms and Conditions'),
'invoice_ids': fields.many2many('account.invoice', 'purchase_invoice_rel', 'purchase_id', 'invoice_id', 'Invoices', help="Invoices generated for a purchase order"),
- 'picking_ids': fields.one2many('stock.picking.in', 'purchase_id', 'Picking List', readonly=True, help="This is the list of incomming shipments that have been generated for this purchase order."),
+ 'picking_ids': fields.one2many('stock.picking.in', 'purchase_id', 'Picking List', readonly=True, help="This is the list of incoming shipments that have been generated for this purchase order."),
'shipped':fields.boolean('Received', readonly=True, select=True, help="It indicates that a picking has been done"),
'shipped_rate': fields.function(_shipped_rate, string='Received', type='float'),
'invoiced': fields.function(_invoiced, string='Invoice Received', type='boolean', help="It indicates that an invoice has been paid"),
The base module to manage analytic distribution and purchase orders.
====================================================================
-Allows the user to maintain several analysis plans. These let you split
-a line on a supplier purchase order into several accounts and analytic plans.
+Allows the user to maintain several analysis plans. These let you split a line
+on a supplier purchase order into several accounts and analytic plans.
""",
'author': 'OpenERP SA',
'website': 'http://www.openerp.com',
Double-validation for purchases exceeding minimum amount.
=========================================================
-This module modifies the purchase workflow in order to validate purchases
-that exceeds minimum amount set by configuration wizard.
+This module modifies the purchase workflow in order to validate purchases that
+exceeds minimum amount set by configuration wizard.
""",
'website': 'http://www.openerp.com',
'init_xml': [],
This module allows you to manage your Purchase Requisition.
===========================================================
-When a purchase order is created, you now have the opportunity to save the related requisition.
-This new object will regroup and will allow you to easily keep track and order all your purchase orders.
+When a purchase order is created, you now have the opportunity to save the
+related requisition. This new object will regroup and will allow you to easily
+keep track and order all your purchase orders.
""",
"depends" : ["purchase","mrp"],
"init_xml" : [],
A module that adds intrastat reports.
=====================================
-This module gives the details of the goods traded between the countries of European Union """,
+This module gives the details of the goods traded between the countries of
+European Union.""",
'author': 'OpenERP SA',
'website': 'http://www.openerp.com',
'depends': ['base', 'product', 'stock', 'sale', 'purchase'],
The module structure and some code is inspired by the report_openoffice module.
The module allows:
-
- HTML report definition
- Multi header support
- Multi logo
- Margins definition
- Paper size definition
-... and much more
-
-Multiple headers and logos can be defined per company.
-CSS style, header and footer body are defined per company.
+Multiple headers and logos can be defined per company. CSS style, header and
+footer body are defined per company.
For a sample report see also the webkit_report_sample module, and this video:
http://files.me.com/nbessi/06n92k.mov
-Requirements and Installation
+Requirements and Installation:
-----------------------------
This module requires the ``wkthtmltopdf`` library to render HTML documents as
-PDF. Version 0.9.9 or later is necessary, and can be found at http://code.google.com/p/wkhtmltopdf/
-for Linux, Mac OS X (i386) and Windows (32bits).
+PDF. Version 0.9.9 or later is necessary, and can be found at
+http://code.google.com/p/wkhtmltopdf/ for Linux, Mac OS X (i386) and Windows (32bits).
After installing the library on the OpenERP Server machine, you need to set the
path to the ``wkthtmltopdf`` executable file on each Company.
Ubuntu is known to have this issue.
-TODO
-----
-
- * JavaScript support activation deactivation
- * Collated and book format support
- * Zip return for separated PDF
- * Web client WYSIWYG
-
- """,
+TODO:
+-----
+ * JavaScript support activation deactivation
+ * Collated and book format support
+ * Zip return for separated PDF
+ * Web client WYSIWYG
+""",
"version": "0.9",
"depends": ["base"],
"author": "Camptocamp",
You have to create the print buttons by calling the wizard. For more details see:
http://files.me.com/nbessi/06n92k.mov
- """,
+""",
"version": "0.9",
"depends": ["base", "account", "report_webkit"],
"category": "Reporting",
Module for resource management.
===============================
-A resource represent something that can be scheduled
-(a developer on a task or a work center on manufacturing orders).
-This module manages a resource calendar associated to every resource.
-It also manages the leaves of every resource.
-
+A resource represent something that can be scheduled (a developer on a task or a
+work center on manufacturing orders). This module manages a resource calendar
+associated to every resource. It also manages the leaves of every resource.
""",
'author': 'OpenERP SA',
'website': 'http://www.openerp.com',
'company_id' : fields.many2one('res.company', 'Company'),
'resource_type': fields.selection([('user','Human'),('material','Material')], 'Resource Type', required=True),
'user_id' : fields.many2one('res.users', 'User', help='Related user name for the resource to manage its access.'),
- 'time_efficiency' : fields.float('Efficiency Factor', size=8, required=True, help="This field depict the efficiency of the resource to complete tasks. e.g resource put alone on a phase of 5 days with 5 tasks assigned to him, will show a load of 100% for this phase by default, but if we put a efficency of 200%, then his load will only be 50%."),
+ 'time_efficiency' : fields.float('Efficiency Factor', size=8, required=True, help="This field depict the efficiency of the resource to complete tasks. e.g resource put alone on a phase of 5 days with 5 tasks assigned to him, will show a load of 100% for this phase by default, but if we put a efficiency of 200%, then his load will only be 50%."),
'calendar_id' : fields.many2one("resource.calendar", "Working Time", help="Define the schedule of resource"),
}
_defaults = {
-------------------------------
* Quotation -> Sales order -> Invoice
-Invoicing methods:
-------------------
- * Invoice on order (before or after shipping)
- * Invoice on delivery
- * Invoice on timesheets
- * Advance invoice
+Create Invoice:
+---------------
+ * Invoice on Demand
+ * Invoice on Delivery Order
+ * Invoice Before Delivery
Partners preferences:
---------------------
- * shipping
- * invoicing
- * incoterm
+ * Incoterm
+ * Shipping
+ * Invoicing
-Products stocks and prices
+Products stocks and prices:
--------------------------
-Delivery methods:
+Delivery method:
-----------------
- * all at once
- * multi-parcel
- * delivery costs
+ * The Poste
+ * Free Delivery Charges
+ * Normal Delivery Charges
+ * Based on the Delivery Order(if not Add to sale order)
Dashboard for Sales Manager that includes:
------------------------------------------
- * Quotations
- * Sales by Month
- * Graph of Sales by Salesman in last 90 days
- * Graph of Sales per Customer in last 90 days
- * Graph of Sales by Product's Category in last 90 days
+ * My Quotations
+ * Monthly Turnover (Graph)
""",
'author': 'OpenERP SA',
'website': 'http://www.openerp.com',
'product_id': fields.many2one('product.product', 'Advance Product', help="Select a product of type service which is called 'Advance Product'. You may have to create it and set it as a default value on this field."),
'amount': fields.float('Advance Amount', digits_compute= dp.get_precision('Sale Price'), required=True, help="The amount to be invoiced in advance."),
'qtty': fields.float('Quantity', digits=(16, 2), required=True),
- 'advance_payment_method':fields.selection([('percentage','Percentage'), ('fixed','Fixed Price')], 'Type', required=True, help="Use Fixed Price if you want to give specific amound in Advance, Use Percentage if you want to give percentage of Total Invoice Amount."),
+ 'advance_payment_method':fields.selection([('percentage','Percentage'), ('fixed','Fixed Price')], 'Type', required=True, help="Use Fixed Price if you want to give specific amount in Advance. Use Percentage if you want to give percentage of Total Invoice Amount."),
}
_defaults = {
===========================================================================
This shortcut allows you to generate a sales order based on the selected case.
-If different cases are open (a list), it generates one sale order by
-case.
+If different cases are open (a list), it generates one sale order by case.
The case is then closed and linked to the generated sales order.
-We suggest you to install this module if you installed both the sale and the
-crm modules.
+We suggest you to install this module, if you installed both the sale and the crm
+modules.
""",
'author': 'OpenERP SA',
'website': 'http://www.openerp.com',
The sales journal modules allows you to categorise your sales and deliveries (picking lists) between different journals.
========================================================================================================================
-This module is very helpful for bigger companies that
-works by departments.
+This module is very helpful for bigger companies that works by departments.
You can use journal for different purposes, some examples:
* isolate sales of different departments
Journals have a responsible and evolves between different status:
* draft, open, cancel, done.
-Batch operations can be processed on the different journals to
-confirm all sales at once, to validate or invoice packing, ...
+Batch operations can be processed on the different journals to confirm all sales
+at once, to validate or invoice packing.
-It also supports batch invoicing methods that can be configured by partners and sales orders, examples:
- * daily invoicing,
- * monthly invoicing, ...
+It also supports batch invoicing methods that can be configured by partners and
+sales orders, examples:
+ * daily invoicing
+ * monthly invoicing
Some statistics by journals are provided.
""",
This module adds the 'Margin' on sales order.
=============================================
-This gives the profitability by calculating the difference between the Unit Price and Cost Price.
+This gives the profitability by calculating the difference between the Unit
+Price and Cost Price.
""",
"author":"OpenERP SA",
"images":["images/sale_margin.jpeg"],
This module provides facility to the user to install mrp and sales modulesat a time.
====================================================================================
-It is basically used when we want to keep track of production
-orders generated from sales order.
-It adds sales name and sales Reference on production order.
+It is basically used when we want to keep track of production orders generated
+from sales order. It adds sales name and sales Reference on production order.
""",
'author': 'OpenERP SA',
'website': 'http://www.openerp.com',
========================================================================
It specifically adds a 'share' button that is available in the Web client to
-share any kind of OpenERP data with colleagues, customers, friends, etc.
+share any kind of OpenERP data with colleagues, customers, friends.
The system will work by creating new users and groups on the fly, and by
-combining the appropriate access rights and ir.rules to ensure that the
-shared users only have access to the data that has been shared with them.
+combining the appropriate access rights and ir.rules to ensure that the shared
+users only have access to the data that has been shared with them.
This is extremely useful for collaborative work, knowledge sharing,
-synchronization with other companies, etc.
-
+synchronization with other companies.
""",
'website': 'http://www.openerp.com',
'demo_xml': ['share_demo.xml'],
Thanks to the double entry management, the inventory controlling is powerful and flexible:
* Moves history and planning,
- * Different inventory methods (FIFO, LIFO, ...)
* Stock valuation (standard or average price, ...)
* Robustness faced with Inventory differences
* Automatic reordering rules (stock level, JIT, ...)
* Bar code supported
* Rapid detection of mistakes through double entry system
* Traceability (upstream/downstream, production lots, serial number, ...)
- * Dashboard for warehouse that includes:
- * Procurement in exception
- * List of Incoming Products
- * List of Outgoing Products
- * Graph : Products to receive in delay (date < = today)
- * Graph : Products to send in delay (date < = today)
+
+Dashboard for warehouse that includes:
+--------------------------------------
+ * Procurement in exception
+ * List of Incoming Products
+ * List of Outgoing Products
+ * Graph : Products to receive in delay (date <= today)
+ * Graph : Products to send in delay (date <= today)
""",
"website" : "http://www.openerp.com",
"images" : ["images/stock_forecast_report.png", "images/delivery_orders.jpeg", "images/inventory_analysis.jpeg","images/location.jpeg","images/moves_analysis.jpeg","images/physical_inventories.jpeg","images/warehouse_dashboard.jpeg"],
'date': fields.datetime('Date', required=True),
'move_ids' : fields.one2many('stock.partial.picking.line', 'wizard_id', 'Product Moves'),
'picking_id': fields.many2one('stock.picking', 'Picking', required=True, ondelete='CASCADE'),
- 'hide_tracking': fields.function(_hide_tracking, string='Tracking', type='boolean', help='This field is for internal purpose. It is used to decide if the column prodlot has to be shown on the move_ids field or not'),
+ 'hide_tracking': fields.function(_hide_tracking, string='Tracking', type='boolean', help='This field is for internal purpose. It is used to decide if the column production lot has to be shown on the moves or not.'),
}
def fields_view_get(self, cr, uid, view_id=None, view_type='form', context=None, toolbar=False, submenu=False):
Invoice Wizard for Delivery.
============================
-When you send or deliver goods, this module automatically launch
-the invoicing wizard if the delivery is to be invoiced.
+When you send or deliver goods, this module automatically launch the invoicing
+wizard if the delivery is to be invoiced.
""",
'author': 'OpenERP SA',
'website': 'http://www.openerp.com',
* Help rental management, by generating automated return moves for rented products
-Once this module is installed, an additional tab appear on the product form, where you can add
-Push and Pull flow specifications. The demo data of CPU1 product for that push/pull :
+Once this module is installed, an additional tab appear on the product form,
+where you can add Push and Pull flow specifications. The demo data of CPU1
+product for that push/pull :
-Push flows
-----------
-Push flows are useful when the arrival of certain products in a given location should always
-be followed by a corresponding move to another location, optionally after a certain delay.
-The original Warehouse application already supports such Push flow specifications on the
-Locations themselves, but these cannot be refined per-product.
+Push flows:
+-----------
+Push flows are useful when the arrival of certain products in a given location
+should always be followed by a corresponding move to another location, optionally
+after a certain delay. The original Warehouse application already supports such
+Push flow specifications on the Locations themselves, but these cannot be
+refined per-product.
-A push flow specification indicates which location is chained with which location, and with
-what parameters. As soon as a given quantity of products is moved in the source location,
-a chained move is automatically foreseen according to the parameters set on the flow specification
-(destination location, delay, type of move, journal, etc.) The new move can be automatically
-processed, or require a manual confirmation, depending on the parameters.
+A push flow specification indicates which location is chained with which location,
+and with what parameters. As soon as a given quantity of products is moved in the
+source location, a chained move is automatically foreseen according to the
+parameters set on the flow specification (destination location, delay, type of
+move, journal). The new move can be automatically processed, or require a manual
+confirmation, depending on the parameters.
-Pull flows
-----------
-Pull flows are a bit different from Push flows, in the sense that they are not related to
-the processing of product moves, but rather to the processing of procurement orders.
-What is being pulled is a need, not directly products.
-A classical example of Pull flow is when you have an Outlet company, with a parent Company
-that is responsible for the supplies of the Outlet.
+Pull flows:
+-----------
+Pull flows are a bit different from Push flows, in the sense that they are not
+related to the processing of product moves, but rather to the processing of
+procurement orders. What is being pulled is a need, not directly products. A
+classical example of Pull flow is when you have an Outlet company, with a parent
+Company that is responsible for the supplies of the Outlet.
[ Customer ] <- A - [ Outlet ] <- B - [ Holding ] <~ C ~ [ Supplier ]
-When a new procurement order (A, coming from the confirmation of a Sale Order for example) arrives
-in the Outlet, it is converted into another procurement (B, via a Pull flow of type 'move')
-requested from the Holding. When procurement order B is processed by the Holding company, and
-if the product is out of stock, it can be converted into a Purchase Order (C) from the Supplier
-(Pull flow of type Purchase). The result is that the procurement order, the need, is pushed
+When a new procurement order (A, coming from the confirmation of a Sale Order
+for example) arrives in the Outlet, it is converted into another procurement
+(B, via a Pull flow of type 'move') requested from the Holding. When procurement
+order B is processed by the Holding company, and if the product is out of stock,
+it can be converted into a Purchase Order (C) from the Supplier (Pull flow of
+type Purchase). The result is that the procurement order, the need, is pushed
all the way between the Customer and Supplier.
-Technically, Pull flows allow to process procurement orders differently, not only depending on
-the product being considered, but also depending on which location holds the "need" for that
-product (i.e. the destination location of that procurement order).
+Technically, Pull flows allow to process procurement orders differently, not
+only depending on the product being considered, but also depending on which
+location holds the "need" for that product (i.e. the destination location of
+that procurement order).
-Use-Case
---------
+Use-Case:
+---------
You can use the demo data as follow:
CPU1: Sell some CPU1 from Shop 1 and run the scheduler
- Warehouse: delivery order, Shop 1: reception
CPU3:
- - When receiving the product, it goes to Quality Control location then stored to shelf 2.
+ - When receiving the product, it goes to Quality Control location then
+ stored to shelf 2.
- When delivering the customer: Pick List -> Packing -> Delivery Order from Gate A
""",
'author': 'OpenERP SA',
'journal_id': fields.many2one('stock.journal','Journal'),
'procure_method': fields.selection([('make_to_stock','Make to Stock'),('make_to_order','Make to Order')], 'Procure Method', required=True, help="'Make to Stock': When needed, take from the stock or wait until re-supplying. 'Make to Order': When needed, purchase or produce for the procurement request."),
'type_proc': fields.selection([('produce','Produce'),('buy','Buy'),('move','Move')], 'Type of Procurement', required=True),
- 'company_id': fields.many2one('res.company', 'Company', help="Is used to know to which company belong packings and moves"),
+ 'company_id': fields.many2one('res.company', 'Company', help="Is used to know to which company the pickings and moves belong."),
'partner_address_id': fields.many2one('res.partner', 'Partner Address'),
'picking_type': fields.selection([('out','Sending Goods'),('in','Getting Goods'),('internal','Internal')], 'Shipping Type', required=True, select=True, help="Depending on the company, choose whatever you want to receive or send products"),
'product_id':fields.many2one('product.product','Product'),
=================================================================================================
One example of usage of this module is to manage production made by your
-suppliers (sub-contracting). To achieve this, set the assembled product
-which is sub-contracted to "No Auto-Picking" and put the location of the
-supplier in the routing of the assembly operation.
+suppliers (sub-contracting). To achieve this, set the assembled product which is
+sub-contracted to "No Auto-Picking" and put the location of the supplier in the
+routing of the assembly operation.
""",
'author': 'OpenERP SA',
'depends': ['mrp'],
"images": ["images/master_procurement_schedule.jpeg","images/sales_forecast.jpeg","images/stock_planning_line.jpeg","images/stock_sales_period.jpeg"],
"depends": ["crm", "stock","sale"],
"description": """
-MPS allows to create a manual procurement plan apart of the normal MRP scheduling, which works automatically based on minimum stock rules
-=========================================================================================================================================
-
-Quick Glossary
---------------
-- Stock Period - the time boundaries (between Start Date and End Date) for your Sales and Stock forecasts and planning
-- Sales Forecast - the quantity of products you plan to sell during the related Stock Period.
-- Stock Planning - the quantity of products you plan to purchase or produce for the related Stock Period.
-
-To avoid confusion with the terms used by the ``sale_forecast`` module, ("Sales Forecast" and "Planning" are amounts) we use terms "Stock and Sales Forecast" and "Stock Planning" to emphasize that we use quantity values.
-
-Where to begin
---------------
+MPS allows to create a manual procurement plan apart of the normal MRP scheduling, which works automatically based on minimum stock rules.
+==========================================================================================================================================
+
+Quick Glossary:
+---------------
+ - Stock Period - the time boundaries (between Start Date and End Date) for
+ your Sales and Stock forecasts and planning
+ - Sales Forecast - the quantity of products you plan to sell during the
+ related Stock Period.
+ - Stock Planning - the quantity of products you plan to purchase or produce
+ for the related Stock Period.
+
+To avoid confusion with the terms used by the ``sale_forecast`` module,
+("Sales Forecast" and "Planning" are amounts) we use terms "Stock and Sales
+Forecast" and "Stock Planning" to emphasize that we use quantity values.
+
+Where to begin:
+---------------
Using this module is done in three steps:
+ * Create Stock Periods via the Warehouse>Configuration>Stock Periods menu
+ (Mandatory step)
+ * Create Sale Forecasts fill them with forecast quantities, via the
+ Sales > Sales Forecast menu. (Optional step but useful for further planning)
+ * Create the actual MPS plan, check the balance and trigger the procurements
+ as required. The actual procurement is the final step for the Stock Period.
+
+Stock Period configuration:
+---------------------------
+You have two menu items for Periods in "Warehouse > Configuration > Stock Periods".
+There are:
+ * "Create Stock Periods" - can automatically creating daily, weekly or
+ monthly periods.
+ * "Stock Periods" - allows to create any type of periods, change the dates
+ and change the state of period.
- * Create Stock Periods via the Warehouse>Configuration>Stock Periods menu (Mandatory step)
- * Create Sale Forecasts fill them with forecast quantities, via the Sales>Sales Forecast menu. (Optional step but useful for further planning)
- * Create the actual MPS plan, check the balance and trigger the procurements as required. The actual procurement is the final step for the Stock Period.
-
-Stock Period configuration
---------------------------
-You have two menu items for Periods in "Warehouse > Configuration > Stock Periods". There are:
-
- * "Create Stock Periods" - can automatically creating daily, weekly or monthly periods.
- * "Stock Periods" - allows to create any type of periods, change the dates and change the state of period.
-
-Creating periods is the first step. You can create custom periods using the "New" button in "Stock Periods", but it is recommended to use the automatic assistant "Create Stock Periods".
+Creating periods is the first step. You can create custom periods using the "New"
+button in "Stock Periods", but it is recommended to use the automatic assistant
+"Create Stock Periods".
Remarks:
-
- - These periods (Stock Periods) are completely distinct from Financial or other periods in the system.
- - Periods are not assigned to companies (when you use multicompany). Module suppose that you use the same periods across companies. If you wish to use different periods for different companies define them as you wish (they can overlap). Later on in this text will be indications how to use such periods.
- - When periods are created automatically their start and finish dates are with start hour 00:00:00 and end hour 23:59:00. When you create daily periods they will have start date 31.01.2010 00:00:00 and end date 31.01.2010 23:59:00. It works only in automatic creation of periods. When you create periods manually you have to take care about hours because you can have incorrect values form sales or stock.
- - If you use overlapping periods for the same product, warehouse and company results can be unpredictable.
- - If current date doesn't belong to any period or you have holes between periods results can be unpredictable.
-
-Sales Forecasts configuration
------------------------------
+ - These periods (Stock Periods) are completely distinct from Financial or
+ other periods in the system.
+ - Periods are not assigned to companies (when you use multicompany). Module
+ suppose that you use the same periods across companies. If you wish to use
+ different periods for different companies define them as you wish (they can
+ overlap). Later on in this text will be indications how to use such periods.
+ - When periods are created automatically their start and finish dates are with
+ start hour 00:00:00 and end hour 23:59:00. When you create daily periods they
+ will have start date 31.01.2010 00:00:00 and end date 31.01.2010 23:59:00.
+ It works only in automatic creation of periods. When you create periods
+ manually you have to take care about hours because you can have incorrect
+ values form sales or stock.
+ - If you use overlapping periods for the same product, warehouse and company
+ results can be unpredictable.
+ - If current date doesn't belong to any period or you have holes between
+ periods results can be unpredictable.
+
+Sales Forecasts configuration:
+------------------------------
You have few menus for Sales forecast in "Sales > Sales Forecasts":
+ - "Create Sales Forecasts" - can automatically create forecast lines
+ according to your needs
+ - "Sales Forecasts" - for managing the Sales forecasts
- - "Create Sales Forecasts" - can automatically create forecast lines according to your needs
- - "Sales Forecasts" - for managing the Sales forecasts
-
-Menu "Create Sales Forecasts" creates Forecasts for products from selected Category, for selected Period and for selected Warehouse.
+Menu "Create Sales Forecasts" creates Forecasts for products from selected
+Category, for selected Period and for selected Warehouse.
It is also possible to copy the previous forecast.
Remarks:
-
- - This tool doesn't duplicate lines if you already have an entry for the same Product, Period, Warehouse, created or validated by the same user. If you wish to create another forecast, if relevant lines exists you have to do it manually as described below.
- - When created lines are validated by someone else you can use this tool to create another line for the same Period, Product and Warehouse.
- - When you choose "Copy Last Forecast", created line take quantity and other settings from your (validated by you or created by you if not validated yet) forecast which is for last period before period of created forecast.
-
-On "Sales Forecast" form mainly you have to enter a forecast quantity in "Product Quantity".
-Further calculation can work for draft forecasts. But validation can save your data against any accidental changes.
-You can click "Validate" button but it is not mandatory.
-
-Instead of forecast quantity you may enter the amount of forecast sales via the "Product Amount" field.
-The system will count quantity from amount according to Sale price of the Product.
-
-All values on the form are expressed in unit of measure selected on form.
-You can select a unit of measure from the default category or from secondary category.
-When you change unit of measure the forecast product quantity will be re-computed according to new UoM.
+ - This tool doesn't duplicate lines if you already have an entry for the same
+ Product, Period, Warehouse, created or validated by the same user. If you
+ wish to create another forecast, if relevant lines exists you have to do it
+ manually as described below.
+ - When created lines are validated by someone else you can use this tool to
+ create another line for the same Period, Product and Warehouse.
+ - When you choose "Copy Last Forecast", created line take quantity and other
+ settings from your (validated by you or created by you if not validated yet)
+ forecast which is for last period before period of created forecast.
+
+On "Sales Forecast" form mainly you have to enter a forecast quantity in
+"Product Quantity". Further calculation can work for draft forecasts. But
+validation can save your data against any accidental changes. You can click
+"Validate" button but it is not mandatory.
+
+Instead of forecast quantity you may enter the amount of forecast sales via the
+"Product Amount" field. The system will count quantity from amount according to
+Sale price of the Product.
+
+All values on the form are expressed in unit of measure selected on form. You can
+select a unit of measure from the default category or from secondary category.
+When you change unit of measure the forecast product quantity will be re-computed
+according to new UoM.
To work out your Sale Forecast you can use the "Sales History" of the product.
-You have to enter parameters to the top and left of this table and system will count sale quantities according to these parameters.
-So you can get results for a given sales team or period.
+You have to enter parameters to the top and left of this table and system will
+count sale quantities according to these parameters. So you can get results for
+a given sales team or period.
-MPS or Procurement Planning
----------------------------
-An MPS planning consists in Stock Planning lines, used to analyze and possibly drive the procurement of
-products for each relevant Stock Period and Warehouse.
+MPS or Procurement Planning:
+----------------------------
+An MPS planning consists in Stock Planning lines, used to analyze and possibly
+drive the procurement of products for each relevant Stock Period and Warehouse.
The menu is located in "Warehouse > Schedulers > Master Procurement Schedule":
- - "Create Stock Planning Lines" - a wizard to help automatically create many planning lines
- - "Master Procurement Schedule" - management of your planning lines
-
-Similarly to the way Sales forecast serves to define your sales planning, the MPS lets you plan your procurements (Purchase/Manufacturing).
-You can quickly populate the MPS with the "Create Stock Planning Lines" wizard, and then proceed to review them via the "Master Procurement Schedule" menu.
-
-The "Create Stock Planning Lines" wizard lets you to quickly create all MPS lines for a given Product Category, and a given Period and Warehouse.
-When you enable the "All Products with Forecast" option of the wizard, the system creates lines for all products having sales forecast for selected
-Period and Warehouse (the selected Category will be ignored in this case).
-
-Under menu "Master Procurement Schedule" you will usually change the "Planned Out" and "Planned In" quantities and observe the resulting "Stock Simulation" value
-to decide if you need to procure more products for the given Period.
-"Planned Out" will be initially based on "Warehouse Forecast" which is the sum of all outgoing stock moves already planned for the Period and Warehouse.
-Of course you can alter this value to provide your own quantities. It is not necessary to have any forecast.
-"Planned In" quantity is used to calculate field "Incoming Left" which is the quantity to be procured to reach the "Stock Simulation" at the end of Period.
-You can compare "Stock Simulation" quantity to minimum stock rules visible on the form.
-And you can plan different quantity than in Minimum Stock Rules. Calculations are done for whole Warehouse by default,
-if you want to see values for Stock location of calculated warehouse you can check "Stock Location Only".
-
-When you are satisfied with the "Planned Out", "Planned In" and end of period "Stock Simulation",
-you can click on "Procure Incoming Left" to create a procurement for the "Incoming Left" quantity.
-You can decide if procurement will go to the to Stock or Input location of the Warehouse.
-
-If you don't want to Produce or Buy the product but just transfer the calculated quantity from another warehouse
-you can click "Supply from Another Warehouse" (instead of "Procure Incoming Left") and the system will
-create the appropriate picking list (stock moves).
-You can choose to take the goods from the Stock or the Output location of the source warehouse.
-Destination location (Stock or Input) in the destination warehouse will be taken as for the procurement case.
-
-To see update the quantities of "Confirmed In", "Confirmed Out", "Confirmed In Before", "Planned Out Before"
-and "Stock Simulation" you can press "Calculate Planning".
-
-All values on the form are expressed in unit of measure selected on form.
-You can select one of unit of measure from default category or from secondary category.
-When you change unit of measure the editable quantities will be re-computed according to new UoM. The others will be updated after pressing "Calculate Planning".
-
-Computation of Stock Simulation quantities
-------------------------------------------
-The Stock Simulation value is the estimated stock quantity at the end of the period.
-The calculation always starts with the real stock on hand at the beginning of the current period, then
-adds or subtracts the computed quantities.
-When you are in the same period (current period is the same as calculated) Stock Simulation is calculated as follows:
-
-Stock Simulation =
- Stock of beginning of current Period
- - Planned Out
- + Planned In
+ - "Create Stock Planning Lines" - a wizard to help automatically create many
+ planning lines
+ - "Master Procurement Schedule" - management of your planning lines
+
+Similarly to the way Sales forecast serves to define your sales planning, the MPS
+lets you plan your procurements (Purchase/Manufacturing).You can quickly populate
+the MPS with the "Create Stock Planning Lines" wizard, and then proceed to review
+them via the "Master Procurement Schedule" menu.
+
+The "Create Stock Planning Lines" wizard lets you to quickly create all MPS lines
+for a given Product Category, and a given Period and Warehouse.When you enable
+the "All Products with Forecast" option of the wizard, the system creates lines
+for all products having sales forecast for selected Period and Warehouse (the
+selected Category will be ignored in this case).
+
+Under menu "Master Procurement Schedule" you will usually change the "Planned Out"
+and "Planned In" quantities and observe the resulting "Stock Simulation" value
+to decide if you need to procure more products for the given Period. "Planned Out"
+will be initially based on "Warehouse Forecast" which is the sum of all outgoing
+stock moves already planned for the Period and Warehouse. Of course you can alter
+this value to provide your own quantities. It is not necessary to have any forecast.
+"Planned In" quantity is used to calculate field "Incoming Left" which is the
+quantity to be procured to reach the "Stock Simulation" at the end of Period. You
+can compare "Stock Simulation" quantity to minimum stock rules visible on the form.
+And you can plan different quantity than in Minimum Stock Rules. Calculations are
+done for whole Warehouse by default, if you want to see values for Stock location
+of calculated warehouse you can check "Stock Location Only".
+
+When you are satisfied with the "Planned Out", "Planned In" and end of period
+"Stock Simulation", you can click on "Procure Incoming Left" to create a
+procurement for the "Incoming Left" quantity. You can decide if procurement will
+go to the to Stock or Input location of the Warehouse.
+
+If you don't want to Produce or Buy the product but just transfer the calculated
+quantity from another warehouse you can click "Supply from Another Warehouse"
+(instead of "Procure Incoming Left") and the system will create the appropriate
+picking list (stock moves). You can choose to take the goods from the Stock or
+the Output location of the source warehouse. Destination location (Stock or Input)
+in the destination warehouse will be taken as for the procurement case.
+
+To see update the quantities of "Confirmed In", "Confirmed Out", "Confirmed In
+Before", "Planned Out Before" and "Stock Simulation" you can press "Calculate
+Planning".
+
+All values on the form are expressed in unit of measure selected on form. You can
+select one of unit of measure from default category or from secondary category.
+When you change unit of measure the editable quantities will be re-computed
+according to new UoM. The others will be updated after pressing "Calculate Planning".
+
+Computation of Stock Simulation quantities:
+-------------------------------------------
+The Stock Simulation value is the estimated stock quantity at the end of the
+period. The calculation always starts with the real stock on hand at the beginning
+of the current period, then adds or subtracts the computed quantities.
+When you are in the same period (current period is the same as calculated) Stock
+Simulation is calculated as follows:
+
+Stock Simulation = Stock of beginning of current Period - Planned Out + Planned In
When you calculate period next to current:
-Stock Simulation =
- Stock of beginning of current Period
- - Planned Out of current Period
- + Confirmed In of current Period (incl. Already In)
- - Planned Out of calculated Period
- + Planned In of calculated Period .
+Stock Simulation = Stock of beginning of current Period - Planned Out of current Period
+ + Confirmed In of current Period (incl. Already In) - Planned Out of calculated Period
+ + Planned In of calculated Period .
-As you see the calculated Period is taken the same way as in previous case, but the calculation in the current
-Period is a little bit different. First you should note that system takes for only Confirmed moves for the
-current period. This means that you should complete the planning and procurement of the current Period before
+As you see the calculated Period is taken the same way as in previous case, but
+the calculation in the current Period is a little bit different. First you should
+note that system takes for only Confirmed moves for the current period. This means
+that you should complete the planning and procurement of the current Period before
going to the next one.
When you plan for future Periods:
-Stock Simulation =
- Stock of beginning of current Period
- - Sum of Planned Out of Periods before calculated
- + Sum of Confirmed In of Periods before calculated (incl. Already In)
- - Planned Out of calculated Period
- + Planned In of calculated Period.
+Stock Simulation = Stock of beginning of current Period
+ - Sum of Planned Out of Periods before calculated
+ + Sum of Confirmed In of Periods before calculated (incl. Already In)
+ - Planned Out of calculated Period
+ + Planned In of calculated Period.
-Here "Periods before calculated" designates all periods starting with the current until the period before the one being calculated.
+Here "Periods before calculated" designates all periods starting with the current
+until the period before the one being calculated.
Remarks:
- - Remember to make the proceed with the planning of each period in chronological order, otherwise the numbers will not reflect the
- reality
- - If you planned for future periods and find that real Confirmed Out is larger than Planned Out in some periods before,
- you can repeat Planning and make another procurement. You should do it in the same planning line.
- If you create another planning line the suggestions can be wrong.
- - When you wish to work with different periods for some products, define two kinds of periods (e.g. Weekly and Monthly) and use
- them for different products. Example: If you use always Weekly periods for Product A, and Monthly periods for Product B
- all calculations will work correctly. You can also use different kind of periods for the same product from different warehouse
- or companies. But you cannot use overlapping periods for the same product, warehouse and company because results
- can be unpredictable. The same applies to Forecasts lines.
+ - Remember to make the proceed with the planning of each period in chronological
+ order, otherwise the numbers will not reflect the reality
+ - If you planned for future periods and find that real Confirmed Out is larger
+ than Planned Out in some periods before, you can repeat Planning and make
+ another procurement. You should do it in the same planning line. If you
+ create another planning line the suggestions can be wrong.
+ - When you wish to work with different periods for some products, define two
+ kinds of periods (e.g. Weekly and Monthly) and use them for different
+ products. Example: If you use always Weekly periods for Product A, and
+ Monthly periods for Product B all calculations will work correctly. You
+ can also use different kind of periods for the same product from different
+ warehouse or companies. But you cannot use overlapping periods for the same
+ product, warehouse and company because results can be unpredictable. The
+ same applies to Forecasts lines.
""",
"data": [
"security/stock_planning_security.xml",
e.g. To have an invoice generated automatically periodically:
* Define a document type based on Invoice object
- * Define a subscription whose source document is the document defined as above. Specify the interval information and partner to be invoice.
+ * Define a subscription whose source document is the document defined as
+ above. Specify the interval information and partner to be invoice.
""",
'author': 'OpenERP SA',
'depends': ['base_tools'],
This module is used for surveying.
==================================
-It depends on the answers or reviews of some questions by different users.
-A survey may have multiple pages. Each page may contain multiple questions and each question may have multiple answers.
-Different users may give different answers of question and according to that survey is done.
-Partners are also sent mails with user name and password for the invitation of the survey
+It depends on the answers or reviews of some questions by different users. A
+survey may have multiple pages. Each page may contain multiple questions and each
+question may have multiple answers. Different users may give different answers of
+question and according to that survey is done. Partners are also sent mails with
+user name and password for the invitation of the survey.
""",
'author': 'OpenERP SA',
'depends': ['base_tools', 'mail'],
"description": """
Adds support for authentication by LDAP server.
===============================================
-This module allows users to login with their LDAP username and
-password, and will automatically create OpenERP users for them
-on the fly.
-
-**Note**: This module only work on servers who have Python's
-``ldap`` module installed.
-
-Configuration
-+++++++++++++
-After installing this module, you need to configure the LDAP
-parameters in the Configuration tab of the Company details.
-Different companies may have different LDAP servers, as long
-as they have unique usernames (usernames need to be unique in
-OpenERP, even across multiple companies).
-
-Anonymous LDAP binding is also supported (for LDAP servers
-that allow it), by simpling keeping the LDAP user and password
-empty in the LDAP configuration. This does **not** allow
-anonymous authentication for users, it is only for the master
-LDAP account that is used to verify if a user exists before
-attempting to authenticate it.
-
-Securing the connection with STARTTLS is available for LDAP
-servers supporting it, by enabling the TLS option in the LDAP
-configuration.
-
-For further options configuring the LDAP settings, refer to the
-ldap.conf manpage: manpage:`ldap.conf(5)`.
-
-Security Considerations
-+++++++++++++++++++++++
-Users' LDAP passwords are never stored in the OpenERP database,
-the LDAP server is queried whenever a user needs to be
-authenticated. No duplication of the password occurs, and
-passwords are managed in one place only.
-
-OpenERP does not manage password changes in the LDAP, so
-any change of password should be conducted by other means
-in the LDAP directory directly (for LDAP users).
-
-It is also possible to have local OpenERP users in the
-database along with LDAP-authenticated users (the Administrator
-account is one obvious example).
+This module allows users to login with their LDAP username and password, and
+will automatically create OpenERP users for them on the fly.
-Here is how it works:
+Note: This module only work on servers who have Python's ``ldap`` module installed.
+
+Configuration:
+--------------
+After installing this module, you need to configure the LDAP parameters in the
+Configuration tab of the Company details. Different companies may have different
+LDAP servers, as long as they have unique usernames (usernames need to be unique
+in OpenERP, even across multiple companies).
+
+Anonymous LDAP binding is also supported (for LDAP servers that allow it), by
+simply keeping the LDAP user and password empty in the LDAP configuration.
+This does not allow anonymous authentication for users, it is only for the master
+LDAP account that is used to verify if a user exists before attempting to
+authenticate it.
+
+Securing the connection with STARTTLS is available for LDAP servers supporting
+it, by enabling the TLS option in the LDAP configuration.
+
+For further options configuring the LDAP settings, refer to the ldap.conf
+manpage: manpage:`ldap.conf(5)`.
- * The system first attempts to authenticate users against
- the local OpenERP database ;
- * if this authentication fails (for example because the
- user has no local password), the system then attempts
- to authenticate against LDAP ;
-
-As LDAP users have blank passwords by default in the local
-OpenERP database (which means no access), the first step
-always fails and the LDAP server is queried to do the
-authentication.
-
-Enabling STARTTLS ensures that the authentication query to the
-LDAP server is encrypted.
-
-User Template
-+++++++++++++
-In the LDAP configuration on the Company form, it is possible to
-select a *User Template*. If set, this user will be used as
-template to create the local users whenever someone authenticates
-for the first time via LDAP authentication.
-This allows pre-setting the default groups and menus of the
-first-time users.
-
-**Warning**: if you set a password for the user template,
-this password will be assigned as local password for each new
-LDAP user, effectively setting a *master password* for these
-users (until manually changed). You usually do not want this.
-One easy way to setup a template user is to login once with
-a valid LDAP user, let OpenERP create a blank local user with the
-same login (and a blank password), then rename this new user
-to a username that does not exist in LDAP, and setup its
-groups the way you want.
-
-Interaction with base_crypt
-+++++++++++++++++++++++++++
-The base_crypt module is not compatible with this module, and
-will disable LDAP authentication if installed at the same time.
+Security Considerations:
+------------------------
+Users' LDAP passwords are never stored in the OpenERP database, the LDAP server
+is queried whenever a user needs to be authenticated. No duplication of the
+password occurs, and passwords are managed in one place only.
+
+OpenERP does not manage password changes in the LDAP, so any change of password
+should be conducted by other means in the LDAP directory directly (for LDAP users).
+
+It is also possible to have local OpenERP users in the database along with
+LDAP-authenticated users (the Administrator account is one obvious example).
+
+Here is how it works:
+ * The system first attempts to authenticate users against the local OpenERP
+ database;
+ * if this authentication fails (for example because the user has no local
+ password), the system then attempts to authenticate against LDAP;
+
+As LDAP users have blank passwords by default in the local OpenERP database
+(which means no access), the first step always fails and the LDAP server is
+queried to do the authentication.
+
+Enabling STARTTLS ensures that the authentication query to the LDAP server is
+encrypted.
+
+User Template:
+--------------
+In the LDAP configuration on the Company form, it is possible to select a *User
+Template*. If set, this user will be used as template to create the local users
+whenever someone authenticates for the first time via LDAP authentication. This
+allows pre-setting the default groups and menus of the first-time users.
+
+Warning: if you set a password for the user template, this password will be
+ assigned as local password for each new LDAP user, effectively setting
+ a *master password* for these users (until manually changed). You
+ usually do not want this. One easy way to setup a template user is to
+ login once with a valid LDAP user, let OpenERP create a blank local
+ user with the same login (and a blank password), then rename this new
+ user to a username that does not exist in LDAP, and setup its groups
+ the way you want.
+
+Interaction with base_crypt:
+----------------------------
+The base_crypt module is not compatible with this module, and will disable LDAP
+authentication if installed at the same time.
""",
'version': '1.0',
'category': 'Tools',
'description': """
-Enable shortcuts feature in the web client
-==========================================
+Enable shortcuts feature in the web client.
+===========================================
Add a Shortcut icon in the systray in order to access the user's shortcuts (if any).
Add a Shortcut icon besides the views title in order to add/remove a shortcut.
This module provides a Wiki FAQ Template.
=========================================
-It provides demo data, thereby creating a Wiki Group and a Wiki Page
-for Wiki FAQ.
+It provides demo data, thereby creating a Wiki Group and a Wiki Page for Wiki FAQ.
""",
'author': 'OpenERP SA',
'website': 'http://openerp.com',
Quality Manual Template.
========================
-It provides demo data, thereby creating a Wiki Group and a Wiki Page
-for Wiki Quality Manual.
+It provides demo data, thereby creating a Wiki Group and a Wiki Page for Wiki
+Quality Manual.
""",
'author': 'OpenERP SA',
'website': 'http://openerp.com',
This module provides a Wiki Sales FAQ Template.
===============================================
-It provides demo data, thereby creating a Wiki Group and a Wiki Page
-for Wiki Sale FAQ.
+It provides demo data, thereby creating a Wiki Group and a Wiki Page for Wiki
+Sale FAQ.
""",
'author': 'OpenERP SA',
'website': 'http://openerp.com',
projects / odoo / odoo.git / commitdiff