[MERGE] Merged SSU's branch to improve module description with respect of rst format
bzr revid: pso@tinyerp.com-20120821111356-abyhw484xe2nkzyi
This commit is contained in:
commit
72ec57d5d4
|
@ -44,8 +44,8 @@ Creates a dashboard for accountants that includes:
|
||||||
* Company Analysis
|
* Company Analysis
|
||||||
* Graph of Treasury
|
* Graph of Treasury
|
||||||
|
|
||||||
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
|
The processes like maintaining of general ledger is done through the defined financial Journals (entry move line orgrouping is maintained through journal)
|
||||||
financial year and for preparation of vouchers there is a module named account_voucher.
|
for a particular financial year and for preparation of vouchers there is a module named account_voucher.
|
||||||
""",
|
""",
|
||||||
'website': 'http://www.openerp.com',
|
'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'],
|
'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'],
|
||||||
|
|
|
@ -28,9 +28,7 @@
|
||||||
This module is for modifying account analytic view to show important data to project manager of services companies.
|
This module is for modifying account analytic view to show important data to project manager of services companies.
|
||||||
===================================================================================================================
|
===================================================================================================================
|
||||||
|
|
||||||
Adds menu to show relevant information to each manager.
|
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.
|
||||||
You can also view the report of account analytic summary
|
|
||||||
user-wise as well as month-wise.
|
|
||||||
""",
|
""",
|
||||||
"author": "Camptocamp",
|
"author": "Camptocamp",
|
||||||
"website": "http://www.camptocamp.com/",
|
"website": "http://www.camptocamp.com/",
|
||||||
|
|
|
@ -25,7 +25,7 @@
|
||||||
"category": 'Accounting & Finance',
|
"category": 'Accounting & Finance',
|
||||||
'description': """
|
'description': """
|
||||||
Set default values for your analytic accounts.
|
Set default values for your analytic accounts.
|
||||||
=============================================
|
==============================================
|
||||||
|
|
||||||
Allows to automatically select analytic accounts based on criterions:
|
Allows to automatically select analytic accounts based on criterions:
|
||||||
---------------------------------------------------------------------
|
---------------------------------------------------------------------
|
||||||
|
|
|
@ -26,38 +26,42 @@
|
||||||
'category': 'Accounting & Finance',
|
'category': 'Accounting & Finance',
|
||||||
'description': """
|
'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
|
Here multiple analytic lines are created when the invoice or the entries
|
||||||
are confirmed.
|
are confirmed.
|
||||||
|
|
||||||
For example, you can define the following analytic structure:
|
For example, you can define the following analytic structure:
|
||||||
Projects
|
-------------------------------------------------------------
|
||||||
Project 1
|
* **Projects**
|
||||||
SubProj 1.1
|
* Project 1
|
||||||
SubProj 1.2
|
+ SubProj 1.1
|
||||||
|
|
||||||
|
+ SubProj 1.2
|
||||||
|
|
||||||
Project 2
|
* Project 2
|
||||||
Salesman
|
|
||||||
Eric
|
* **Salesman**
|
||||||
Fabien
|
* Eric
|
||||||
|
|
||||||
|
* Fabien
|
||||||
|
|
||||||
Here, we have two plans: Projects and Salesman. An invoice line must
|
Here, we have two plans: Projects and Salesman. An invoice line must be able to write analytic entries in the 2 plans: SubProj 1.1 and Fabien. The amount can also be split.
|
||||||
be able to write analytic entries in the 2 plans: SubProj 1.1 and
|
|
||||||
Fabien. The amount can also be split. The following example is for
|
The following example is for an invoice that touches the two subprojects and assigned to one salesman:
|
||||||
an invoice that touches the two subproject and assigned to one salesman:
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||||
|
**Plan1:**
|
||||||
|
|
||||||
Plan1:
|
* SubProject 1.1 : 50%
|
||||||
SubProject 1.1 : 50%
|
|
||||||
SubProject 1.2 : 50%
|
* SubProject 1.2 : 50%
|
||||||
Plan2:
|
|
||||||
|
**Plan2:**
|
||||||
Eric: 100%
|
Eric: 100%
|
||||||
|
|
||||||
So when this line of invoice will be confirmed, it will generate 3 analytic lines,
|
So when this line of invoice will be confirmed, it will generate 3 analytic lines,for one account entry.
|
||||||
for one account entry.
|
|
||||||
|
|
||||||
The analytic plan validates the minimum and maximum percentage at the time of creation
|
The analytic plan validates the minimum and maximum percentage at the time of creation of distribution models.
|
||||||
of distribution models.
|
|
||||||
""",
|
""",
|
||||||
'author': 'OpenERP SA',
|
'author': 'OpenERP SA',
|
||||||
'website': 'http://www.openerp.com',
|
'website': 'http://www.openerp.com',
|
||||||
|
|
|
@ -27,15 +27,18 @@
|
||||||
This module supports the Anglo-Saxon accounting methodology by changing the accounting logic with stock transactions.
|
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
|
The difference between the Anglo-Saxon accounting countries and the Rhine
|
||||||
Continental accounting) countries is the moment of taking the Cost of Goods Sold versus
|
(or also called Continental accounting) countries is the moment of taking
|
||||||
Cost of Sales. Anglo-Saxons accounting does take the cost when sales invoice is created,
|
the Cost of Goods Sold versus Cost of Sales. Anglo-Saxons accounting does
|
||||||
Continental accounting will take the cost at the moment the goods are shipped.
|
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
|
This module will add this functionality by using a interim account, to
|
||||||
shipped goods and will contra book this interim account when the invoice is created to
|
store the value of shipped goods and will contra book this interim
|
||||||
transfer this amount to the debtor or creditor account. Secondly, price differences between
|
account when the invoice is created to transfer this amount to the
|
||||||
actual purchase price and fixed product standard price are booked on a separate account.""",
|
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"],
|
"images": ["images/account_anglo_saxon.jpeg"],
|
||||||
"depends": ["product", "purchase"],
|
"depends": ["product", "purchase"],
|
||||||
"category": "Accounting & Finance",
|
"category": "Accounting & Finance",
|
||||||
|
|
|
@ -28,8 +28,9 @@
|
||||||
Financial and accounting asset management.
|
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.
|
This Module manages the assets owned by a company or an individual. It will keep
|
||||||
And it allows to create Move's of the depreciation lines.
|
track of depreciation's occurred on those assets. And it allows to create Move's
|
||||||
|
of the depreciation lines.
|
||||||
|
|
||||||
""",
|
""",
|
||||||
"website" : "http://www.openerp.com",
|
"website" : "http://www.openerp.com",
|
||||||
|
|
|
@ -30,13 +30,16 @@ Module that extends the standard account_bank_statement_line object for improved
|
||||||
===================================================================================================
|
===================================================================================================
|
||||||
|
|
||||||
This module adds:
|
This module adds:
|
||||||
|
-----------------
|
||||||
- valuta date
|
- valuta date
|
||||||
- batch payments
|
- batch payments
|
||||||
- traceability of changes to bank statement lines
|
- traceability of changes to bank statement lines
|
||||||
- bank statement line views
|
- bank statement line views
|
||||||
- bank statements balances report
|
- bank statements balances report
|
||||||
- performance improvements for digital import of bank statement (via 'ebanking_import' context flag)
|
- performance improvements for digital import of bank statement (via
|
||||||
- name_search on res.partner.bank enhanced to allow search on bank and iban account numbers
|
'ebanking_import' context flag)
|
||||||
|
- name_search on res.partner.bank enhanced to allow search on bank
|
||||||
|
and iban account numbers
|
||||||
''',
|
''',
|
||||||
'depends': ['account'],
|
'depends': ['account'],
|
||||||
'demo_xml': [],
|
'demo_xml': [],
|
||||||
|
|
|
@ -32,16 +32,20 @@ Once the Budgets are defined (in Invoicing/Budgets/Budgets), the Project Manager
|
||||||
can set the planned amount on each Analytic Account.
|
can set the planned amount on each Analytic Account.
|
||||||
|
|
||||||
The accountant has the possibility to see the total of amount planned for each
|
The accountant has the possibility to see the total of amount planned for each
|
||||||
Budget in order to ensure the total planned is not greater/lower than what he planned
|
Budget in order to ensure the total planned is not greater/lower than what he
|
||||||
for this Budget. Each list of record can also be switched to a graphical view of it.
|
planned for this Budget. Each list of record can also be switched to a graphical
|
||||||
|
view of it.
|
||||||
|
|
||||||
Three reports are available:
|
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.
|
||||||
|
|
||||||
1. The first is available from a list of Budgets. It gives the spreading, for these Budgets, of the Analytic Accounts.
|
2. The second is a summary of the previous one, it only gives the spreading,
|
||||||
|
for the selected Budgets, of the Analytic Accounts.
|
||||||
|
|
||||||
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.
|
||||||
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',
|
'author': 'OpenERP SA',
|
||||||
'website': 'http://www.openerp.com',
|
'website': 'http://www.openerp.com',
|
||||||
|
|
|
@ -25,10 +25,10 @@
|
||||||
"author" : "OpenERP SA",
|
"author" : "OpenERP SA",
|
||||||
"category": 'Accounting & Finance',
|
"category": 'Accounting & Finance',
|
||||||
"description": """
|
"description": """
|
||||||
Allows cancelling accounting entries.
|
Allows canceling accounting entries.
|
||||||
=====================================
|
=====================================
|
||||||
|
|
||||||
This module adds 'Allow Cancelling Entries' field on form view of account journal.
|
This module adds 'Allow Canceling Entries' field on form view of account journal.
|
||||||
If set to true it allows user to cancel entries & invoices.
|
If set to true it allows user to cancel entries & invoices.
|
||||||
""",
|
""",
|
||||||
'website': 'http://www.openerp.com',
|
'website': 'http://www.openerp.com',
|
||||||
|
|
|
@ -25,6 +25,7 @@
|
||||||
"category": "Generic Modules/Accounting",
|
"category": "Generic Modules/Accounting",
|
||||||
"description": """
|
"description": """
|
||||||
Module for the Check Writing and Check Printing.
|
Module for the Check Writing and Check Printing.
|
||||||
|
================================================
|
||||||
""",
|
""",
|
||||||
'website': 'http://www.openerp.com',
|
'website': 'http://www.openerp.com',
|
||||||
'init_xml': [],
|
'init_xml': [],
|
||||||
|
|
|
@ -29,44 +29,64 @@ Module to import CODA bank statements.
|
||||||
======================================
|
======================================
|
||||||
|
|
||||||
Supported are CODA flat files in V2 format from Belgian bank accounts.
|
Supported are CODA flat files in V2 format from Belgian bank accounts.
|
||||||
|
----------------------------------------------------------------------
|
||||||
* CODA v1 support.
|
* CODA v1 support.
|
||||||
* CODA v2.2 support.
|
* CODA v2.2 support.
|
||||||
* Foreign Currency support.
|
* Foreign Currency support.
|
||||||
* Support for all data record types (0, 1, 2, 3, 4, 8, 9).
|
* Support for all data record types (0, 1, 2, 3, 4, 8, 9).
|
||||||
* Parsing & logging of all Transaction Codes and Structured Format Communications.
|
* Parsing & logging of all Transaction Codes and Structured Format
|
||||||
|
Communications.
|
||||||
* Automatic Financial Journal assignment via CODA configuration parameters.
|
* Automatic Financial Journal assignment via CODA configuration parameters.
|
||||||
* Support for multiple Journals per Bank Account Number.
|
* Support for multiple Journals per Bank Account Number.
|
||||||
* Support for multiple statements from different bank accounts in a single CODA file.
|
* Support for multiple statements from different bank accounts in a single
|
||||||
* Support for 'parsing only' CODA Bank Accounts (defined as type='info' in the CODA Bank Account configuration records).
|
CODA file.
|
||||||
* Multi-language CODA parsing, parsing configuration data provided for EN, NL, FR.
|
* 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
|
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
|
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
|
the CODA information (only those transaction lines that are required for the
|
||||||
of the Financial Accounting records). The CODA Bank Statement is a 'read-only'
|
creation of the Financial Accounting records). The CODA Bank Statement is a
|
||||||
object, hence remaining a reliable representation of the original CODA file whereas
|
'read-only' object, hence remaining a reliable representation of the original
|
||||||
the Bank Statement will get modified as required by accounting business processes.
|
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.
|
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
|
A removal of one object in the CODA processing results in the removal of the
|
||||||
objects. The removal of a CODA File containing multiple Bank Statements will also
|
associated objects. The removal of a CODA File containing multiple Bank
|
||||||
remove those associated statements.
|
Statements will also remove those associated statements.
|
||||||
|
|
||||||
The following reconciliation logic has been implemented in the CODA processing:
|
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.
|
1) The Company's Bank Account Number of the CODA statement is compared against
|
||||||
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).
|
the Bank Account Number field of the Company's CODA Bank Account
|
||||||
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.
|
configuration records (whereby bank accounts defined in type='info'
|
||||||
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.
|
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
|
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
|
re-import the CODA after updating the OpenERP database with the information that
|
||||||
was missing to allow automatic reconciliation.
|
was missing to allow automatic reconciliation.
|
||||||
|
|
||||||
Remark on CODA V1 support:
|
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.
|
~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||||
The description provided by the CODA configuration tables is based upon the CODA V2.2 specifications.
|
In some cases a transaction code, transaction category or structured
|
||||||
|
communication code has been given a new or clearer description in CODA V2.The
|
||||||
|
description provided by the CODA configuration tables is based upon the CODA
|
||||||
|
V2.2 specifications.
|
||||||
If required, you can manually adjust the descriptions via the CODA configuration menu.
|
If required, you can manually adjust the descriptions via the CODA configuration menu.
|
||||||
''',
|
''',
|
||||||
"images" : ["images/coda_logs.jpeg","images/import_coda_logs.jpeg"],
|
"images" : ["images/coda_logs.jpeg","images/import_coda_logs.jpeg"],
|
||||||
|
|
|
@ -28,22 +28,20 @@ Module to automate letters for unpaid invoices, with multi-level recalls.
|
||||||
==========================================================================
|
==========================================================================
|
||||||
|
|
||||||
You can define your multiple levels of recall through the menu:
|
You can define your multiple levels of recall through the menu:
|
||||||
|
---------------------------------------------------------------
|
||||||
|
**Invoicing** / **Configuration** / **Miscellaneous** / **Follow-ups**
|
||||||
|
|
||||||
Invoicing/Configuration/Miscellaneous/Follow-ups
|
Once it is defined, you can automatically print recalls every day through simply clicking on the menu:
|
||||||
|
------------------------------------------------------------------------------------------------------
|
||||||
Once it is defined, you can automatically print recalls every day through simply
|
**Invoicing** / **Periodical Processing** / **Billing** / **Send follow-ups**
|
||||||
clicking on the menu:
|
|
||||||
|
|
||||||
Invoicing/Periodical Processing/Billing/Send follow-ups
|
|
||||||
|
|
||||||
It will generate a PDF with all the letters according to the the different levels
|
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
|
of recall defined. You can define different policies for different companies. You
|
||||||
can also send mail to the customer.
|
can also send mail to the customer.
|
||||||
|
|
||||||
Note that if you want to check the follow-up level for a given partner/account
|
Note that if you want to check the follow-up level for a given partner/account entry, you can do from in the menu:
|
||||||
entry, you can do from in the menu:
|
------------------------------------------------------------------------------------------------------------------
|
||||||
|
**Invoicing** / **Reporting** / **Generic Reporting** / **Partners** / **Follow-ups Sent**
|
||||||
Invoicing/Reporting/Generic Reporting/Partners/Follow-ups Sent
|
|
||||||
|
|
||||||
""",
|
""",
|
||||||
'author': 'OpenERP SA',
|
'author': 'OpenERP SA',
|
||||||
|
|
|
@ -28,13 +28,19 @@
|
||||||
Module to manage the payment of your supplier invoices.
|
Module to manage the payment of your supplier invoices.
|
||||||
=======================================================
|
=======================================================
|
||||||
|
|
||||||
This module allows you to create and manage your payment orders, with purposes to
|
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.
|
* serve as base for an easy plug-in of various automated payment mechanisms.
|
||||||
* provide a more efficient way to manage invoice payment.
|
* provide a more efficient way to manage invoice payment.
|
||||||
|
|
||||||
Warning:
|
Warning:
|
||||||
--------
|
~~~~~~~~
|
||||||
The confirmation of a payment order does _not_ create accounting entries, it just records the fact that you gave your payment order to your bank. The booking of your order must be encoded as usual through a bank statement. Indeed, it's only when you get the confirmation from your bank that your order has been accepted that you can book it in your accounting. To help you with that operation, you have a new option to import payment orders as bank statement lines.
|
The confirmation of a payment order does _not_ create accounting entries, it just
|
||||||
|
records the fact that you gave your payment order to your bank. The booking of
|
||||||
|
your order must be encoded as usual through a bank statement. Indeed, it's only
|
||||||
|
when you get the confirmation from your bank that your order has been accepted
|
||||||
|
that you can book it in your accounting. To help you with that operation, you
|
||||||
|
have a new option to import payment orders as bank statement lines.
|
||||||
""",
|
""",
|
||||||
'images': ['images/payment_mode.jpeg','images/payment_order.jpeg'],
|
'images': ['images/payment_mode.jpeg','images/payment_order.jpeg'],
|
||||||
'depends': ['account','account_voucher'],
|
'depends': ['account','account_voucher'],
|
||||||
|
|
|
@ -30,6 +30,7 @@ This module maintains internal sequence number for accounting entries.
|
||||||
Allows you to configure the accounting sequences to be maintained.
|
Allows you to configure the accounting sequences to be maintained.
|
||||||
|
|
||||||
You can customize the following attributes of the sequence:
|
You can customize the following attributes of the sequence:
|
||||||
|
-----------------------------------------------------------
|
||||||
* Prefix
|
* Prefix
|
||||||
* Suffix
|
* Suffix
|
||||||
* Next Number
|
* Next Number
|
||||||
|
|
|
@ -26,7 +26,7 @@
|
||||||
'category': 'Hidden',
|
'category': 'Hidden',
|
||||||
'description': """
|
'description': """
|
||||||
This module is for modifying project view to show some data related to the hr_expense module.
|
This module is for modifying project view to show some data related to the hr_expense module.
|
||||||
|
=============================================================================================
|
||||||
""",
|
""",
|
||||||
"author": "OpenERP S.A.",
|
"author": "OpenERP S.A.",
|
||||||
"website": "http://www.openerp.com/",
|
"website": "http://www.openerp.com/",
|
||||||
|
|
|
@ -26,7 +26,7 @@
|
||||||
'category': 'Hidden',
|
'category': 'Hidden',
|
||||||
'description': """
|
'description': """
|
||||||
This module is for modifying account analytic view to show some data related to the hr_expense module.
|
This module is for modifying account analytic view to show some data related to the hr_expense module.
|
||||||
|
======================================================================================================
|
||||||
""",
|
""",
|
||||||
"author": "OpenERP S.A.",
|
"author": "OpenERP S.A.",
|
||||||
"website": "http://www.openerp.com/",
|
"website": "http://www.openerp.com/",
|
||||||
|
|
|
@ -28,6 +28,7 @@
|
||||||
"depends" : ["project", "account_analytic_analysis"],
|
"depends" : ["project", "account_analytic_analysis"],
|
||||||
"description": """
|
"description": """
|
||||||
Add "Contract Data" in project view.
|
Add "Contract Data" in project view.
|
||||||
|
====================================
|
||||||
""",
|
""",
|
||||||
"init_xml" : [],
|
"init_xml" : [],
|
||||||
"update_xml": ["analytic_contract_project_view.xml"],
|
"update_xml": ["analytic_contract_project_view.xml"],
|
||||||
|
|
|
@ -1,6 +1,9 @@
|
||||||
{
|
{
|
||||||
'name': 'Anonymous',
|
'name': 'Anonymous',
|
||||||
'description': 'Allow anonymous access to OpenERP.',
|
'description': """
|
||||||
|
Allow anonymous access to OpenERP.
|
||||||
|
==================================
|
||||||
|
""",
|
||||||
'author': 'OpenERP SA',
|
'author': 'OpenERP SA',
|
||||||
'version': '1.0',
|
'version': '1.0',
|
||||||
'category': 'Authentication',
|
'category': 'Authentication',
|
||||||
|
|
|
@ -30,7 +30,7 @@ Adds support for authentication by LDAP server.
|
||||||
This module allows users to login with their LDAP username and password, and
|
This module allows users to login with their LDAP username and password, and
|
||||||
will automatically create OpenERP users for them on the fly.
|
will automatically create OpenERP users for them on the fly.
|
||||||
|
|
||||||
Note: This module only work on servers who have Python's ``ldap`` module installed.
|
**Note:** This module only work on servers who have Python's ``ldap`` module installed.
|
||||||
|
|
||||||
Configuration:
|
Configuration:
|
||||||
--------------
|
--------------
|
||||||
|
@ -64,7 +64,7 @@ It is also possible to have local OpenERP users in the database along with
|
||||||
LDAP-authenticated users (the Administrator account is one obvious example).
|
LDAP-authenticated users (the Administrator account is one obvious example).
|
||||||
|
|
||||||
Here is how it works:
|
Here is how it works:
|
||||||
|
---------------------
|
||||||
* The system first attempts to authenticate users against the local OpenERP
|
* The system first attempts to authenticate users against the local OpenERP
|
||||||
database;
|
database;
|
||||||
* if this authentication fails (for example because the user has no local
|
* if this authentication fails (for example because the user has no local
|
||||||
|
@ -84,7 +84,7 @@ 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
|
whenever someone authenticates for the first time via LDAP authentication. This
|
||||||
allows pre-setting the default groups and menus of the first-time users.
|
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
|
**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
|
assigned as local password for each new LDAP user, effectively setting
|
||||||
a *master password* for these users (until manually changed). You
|
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
|
usually do not want this. One easy way to setup a template user is to
|
||||||
|
|
|
@ -24,7 +24,10 @@
|
||||||
'name': 'OAuth2 Authentication',
|
'name': 'OAuth2 Authentication',
|
||||||
'version': '1.0',
|
'version': '1.0',
|
||||||
'category': 'Tools',
|
'category': 'Tools',
|
||||||
'description': """Allow users to login through Google OAuth2.""",
|
'description': """
|
||||||
|
Allow users to login through Google OAuth2.
|
||||||
|
===========================================
|
||||||
|
""",
|
||||||
'author': 'Victor Tabuenca',
|
'author': 'Victor Tabuenca',
|
||||||
'maintainer': 'OpenERP s.a.',
|
'maintainer': 'OpenERP s.a.',
|
||||||
'website': 'http://www.openerp.com',
|
'website': 'http://www.openerp.com',
|
||||||
|
|
|
@ -24,7 +24,10 @@
|
||||||
'name': 'OpenID Authentification',
|
'name': 'OpenID Authentification',
|
||||||
'version': '2.0',
|
'version': '2.0',
|
||||||
'category': 'Tools',
|
'category': 'Tools',
|
||||||
'description': """Allow users to login through OpenID.""",
|
'description': """
|
||||||
|
Allow users to login through OpenID.
|
||||||
|
====================================
|
||||||
|
""",
|
||||||
'author': 'OpenERP s.a.',
|
'author': 'OpenERP s.a.',
|
||||||
'maintainer': 'OpenERP s.a.',
|
'maintainer': 'OpenERP s.a.',
|
||||||
'website': 'http://www.openerp.com',
|
'website': 'http://www.openerp.com',
|
||||||
|
|
|
@ -1,6 +1,9 @@
|
||||||
{
|
{
|
||||||
'name': 'Reset Password',
|
'name': 'Reset Password',
|
||||||
'description': 'Allow users to reset their password from the login page',
|
'description': """
|
||||||
|
Allow users to reset their password from the login page.
|
||||||
|
========================================================
|
||||||
|
""",
|
||||||
'author': 'OpenERP SA',
|
'author': 'OpenERP SA',
|
||||||
'version': '1.0',
|
'version': '1.0',
|
||||||
'category': 'Authentication',
|
'category': 'Authentication',
|
||||||
|
|
|
@ -21,7 +21,10 @@
|
||||||
|
|
||||||
{
|
{
|
||||||
'name': 'Signup',
|
'name': 'Signup',
|
||||||
'description': 'Allow users to sign up',
|
'description': """
|
||||||
|
Allow users to sign up.
|
||||||
|
=======================
|
||||||
|
""",
|
||||||
'author': 'OpenERP SA',
|
'author': 'OpenERP SA',
|
||||||
'version': '1.0',
|
'version': '1.0',
|
||||||
'category': 'Authentication',
|
'category': 'Authentication',
|
||||||
|
|
|
@ -29,7 +29,7 @@ This module allows to implement action rules for any object.
|
||||||
|
|
||||||
Use automated actions to automatically trigger actions for various screens.
|
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
|
sales team, or an opportunity which still has status pending after 14 days might
|
||||||
trigger an automatic reminder email.
|
trigger an automatic reminder email.
|
||||||
""",
|
""",
|
||||||
|
|
|
@ -28,6 +28,7 @@ This is a full-featured calendar system.
|
||||||
========================================
|
========================================
|
||||||
|
|
||||||
It supports:
|
It supports:
|
||||||
|
------------
|
||||||
- Calendar of events
|
- Calendar of events
|
||||||
- Alerts (create requests)
|
- Alerts (create requests)
|
||||||
- Recurring events
|
- Recurring events
|
||||||
|
|
|
@ -30,7 +30,7 @@ Replaces cleartext passwords in the database with a secure hash.
|
||||||
================================================================
|
================================================================
|
||||||
|
|
||||||
For your existing user base, the removal of the cleartext passwords occurs
|
For your existing user base, the removal of the cleartext passwords occurs
|
||||||
immediately when you instal base_crypt.
|
immediately when you install base_crypt.
|
||||||
|
|
||||||
All passwords will be replaced by a secure, salted, cryptographic hash,
|
All passwords will be replaced by a secure, salted, cryptographic hash,
|
||||||
preventing anyone from reading the original password in the database.
|
preventing anyone from reading the original password in the database.
|
||||||
|
@ -49,8 +49,8 @@ contain critical data. Appropriate security measures need to be implemented
|
||||||
by the system administrator in all areas, such as: protection of database
|
by the system administrator in all areas, such as: protection of database
|
||||||
backups, system files, remote shell access, physical server access.
|
backups, system files, remote shell access, physical server access.
|
||||||
|
|
||||||
Interation with LDAP authentication:
|
Interaction with LDAP authentication:
|
||||||
------------------------------------
|
-------------------------------------
|
||||||
This module is currently not compatible with the ``user_ldap`` module and
|
This module is currently not compatible with the ``user_ldap`` module and
|
||||||
will disable LDAP authentication completely if installed at the same time.
|
will disable LDAP authentication completely if installed at the same time.
|
||||||
""",
|
""",
|
||||||
|
|
|
@ -24,7 +24,7 @@
|
||||||
"category": 'Hidden/Dependency',
|
"category": 'Hidden/Dependency',
|
||||||
'description': """
|
'description': """
|
||||||
This module installs the base for IBAN (International Bank Account Number) bank accounts and checks for it's 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
|
The ability to extract the correctly represented local accounts from IBAN accounts
|
||||||
with a single statement.
|
with a single statement.
|
||||||
|
|
|
@ -39,6 +39,7 @@ This should help you to easily create reusable and publishable modules for custo
|
||||||
configurations and demo/testing data.
|
configurations and demo/testing data.
|
||||||
|
|
||||||
How to use it?:
|
How to use it?:
|
||||||
|
---------------
|
||||||
Run Settings/Technical/Module Creation/Export Customizations As a Module wizard.
|
Run Settings/Technical/Module Creation/Export Customizations As a Module wizard.
|
||||||
Select datetime criteria of recording and objects to be recorded and Record module.
|
Select datetime criteria of recording and objects to be recorded and Record module.
|
||||||
""",
|
""",
|
||||||
|
|
|
@ -24,12 +24,11 @@
|
||||||
'version': '1.0',
|
'version': '1.0',
|
||||||
'category': 'Hidden',
|
'category': 'Hidden',
|
||||||
'description': """
|
'description': """
|
||||||
This module handles state and stage. It is derived from the crm_base and
|
This module handles state and stage. It is derived from the crm_base and crm_case classes from crm.
|
||||||
crm_case classes from crm.
|
===================================================================================================
|
||||||
========================================================================
|
|
||||||
|
|
||||||
* ``base_state``: state management
|
* ``base_state``: state management
|
||||||
* ``base_stage``: stage management
|
* ``base_stage``: stage management
|
||||||
""",
|
""",
|
||||||
'author': 'OpenERP SA',
|
'author': 'OpenERP SA',
|
||||||
'website': 'http://www.openerp.com',
|
'website': 'http://www.openerp.com',
|
||||||
|
|
|
@ -33,19 +33,20 @@ be validated for all supported countries. The country is inferred from the
|
||||||
will be validated using the Belgian rules.
|
will be validated using the Belgian rules.
|
||||||
|
|
||||||
There are two different levels of VAT number validation:
|
There are two different levels of VAT number validation:
|
||||||
|
--------------------------------------------------------
|
||||||
* By default, a simple off-line check is performed using the known validation
|
* By default, a simple off-line check is performed using the known validation
|
||||||
rules for the country, usually a simple check digit. This is quick and
|
rules for the country, usually a simple check digit. This is quick and
|
||||||
always available, but allows numbers that are perhaps not truly allocated,
|
always available, but allows numbers that are perhaps not truly allocated,
|
||||||
or not valid anymore.
|
or not valid anymore.
|
||||||
* When the "VAT VIES Check" option is enabled (in the configuration of the user's
|
|
||||||
Company), VAT numbers will be instead submitted to the online EU VIES
|
* When the "VAT VIES Check" option is enabled (in the configuration of the user's
|
||||||
database, which will truly verify that the number is valid and currently
|
Company), VAT numbers will be instead submitted to the online EU VIES
|
||||||
allocated to a EU company. This is a little bit slower than the simple
|
database, which will truly verify that the number is valid and currently
|
||||||
off-line check, requires an Internet connection, and may not be available
|
allocated to a EU company. This is a little bit slower than the simple
|
||||||
all the time. If the service is not available or does not support the
|
off-line check, requires an Internet connection, and may not be available
|
||||||
requested country (e.g. for non-EU countries), a simple check will be performed
|
all the time. If the service is not available or does not support the
|
||||||
instead.
|
requested country (e.g. for non-EU countries), a simple check will be performed
|
||||||
|
instead.
|
||||||
|
|
||||||
Supported countries currently include EU countries, and a few non-EU countries
|
Supported countries currently include EU countries, and a few non-EU countries
|
||||||
such as Chile, Colombia, Mexico, Norway or Russia. For unsupported countries,
|
such as Chile, Colombia, Mexico, Norway or Russia. For unsupported countries,
|
||||||
|
|
|
@ -37,16 +37,21 @@ This module contains basic functionality for Caldav system.
|
||||||
- Provides iCal Import/Export functionality
|
- Provides iCal Import/Export functionality
|
||||||
|
|
||||||
To access Calendars using CalDAV clients, point them to:
|
To access Calendars using CalDAV clients, point them to:
|
||||||
|
--------------------------------------------------------
|
||||||
http://HOSTNAME:PORT/webdav/DATABASE_NAME/calendars/users/USERNAME/c
|
http://HOSTNAME:PORT/webdav/DATABASE_NAME/calendars/users/USERNAME/c
|
||||||
|
|
||||||
To access OpenERP Calendar using WebCal to remote site use the URL like:
|
To access OpenERP Calendar using WebCal to remote site use the URL like:
|
||||||
|
------------------------------------------------------------------------
|
||||||
http://HOSTNAME:PORT/webdav/DATABASE_NAME/Calendars/CALENDAR_NAME.ics
|
http://HOSTNAME:PORT/webdav/DATABASE_NAME/Calendars/CALENDAR_NAME.ics
|
||||||
|
|
||||||
Where,
|
Where,
|
||||||
HOSTNAME: Host on which OpenERP server(With webdav) is running
|
**HOSTNAME:** Host on which OpenERP server(With webdav) is running
|
||||||
PORT : Port on which OpenERP server is running (By Default : 8069)
|
|
||||||
DATABASE_NAME: Name of database on which OpenERP Calendar is created
|
**PORT :** Port on which OpenERP server is running (By Default : 8069)
|
||||||
CALENDAR_NAME: Name of calendar to access
|
|
||||||
|
**DATABASE_NAME:** Name of database on which OpenERP Calendar is created
|
||||||
|
|
||||||
|
**CALENDAR_NAME:** Name of calendar to access
|
||||||
""",
|
""",
|
||||||
'category': 'Hidden/Dependency',
|
'category': 'Hidden/Dependency',
|
||||||
"author": "OpenERP SA",
|
"author": "OpenERP SA",
|
||||||
|
|
|
@ -32,6 +32,7 @@ You can geolocalize your opportunities by using this module.
|
||||||
|
|
||||||
Use geolocalization when assigning opportunities to partners.
|
Use geolocalization when assigning opportunities to partners.
|
||||||
Determine the GPS coordinates according to the address of the partner.
|
Determine the GPS coordinates according to the address of the partner.
|
||||||
|
|
||||||
The most appropriate partner can be assigned.
|
The most appropriate partner can be assigned.
|
||||||
You can also use the geolocalization without using the GPS coordinates.
|
You can also use the geolocalization without using the GPS coordinates.
|
||||||
""",
|
""",
|
||||||
|
|
|
@ -35,8 +35,7 @@ questionnaire and directly use it on a partner.
|
||||||
It also has been merged with the earlier CRM & SRM segmentation tool because they
|
It also has been merged with the earlier CRM & SRM segmentation tool because they
|
||||||
were overlapping.
|
were overlapping.
|
||||||
|
|
||||||
* Note: this module is not compatible with the module segmentation, since
|
**Note:** this module is not compatible with the module segmentation, since it's the same which has been renamed.
|
||||||
it's the same which has been renamed.
|
|
||||||
""",
|
""",
|
||||||
'author': 'OpenERP SA',
|
'author': 'OpenERP SA',
|
||||||
'website': 'http://www.openerp.com',
|
'website': 'http://www.openerp.com',
|
||||||
|
|
|
@ -26,6 +26,7 @@
|
||||||
"category": 'Customer Relationship Management',
|
"category": 'Customer Relationship Management',
|
||||||
'description': """
|
'description': """
|
||||||
Todo list for CRM leads and opportunities.
|
Todo list for CRM leads and opportunities.
|
||||||
|
==========================================
|
||||||
""",
|
""",
|
||||||
'author': 'OpenERP SA',
|
'author': 'OpenERP SA',
|
||||||
'depends': ['crm','project_gtd'],
|
'depends': ['crm','project_gtd'],
|
||||||
|
|
|
@ -37,6 +37,7 @@ This is a complete document management system.
|
||||||
* Files Size by Month (graph)
|
* Files Size by Month (graph)
|
||||||
|
|
||||||
ATTENTION:
|
ATTENTION:
|
||||||
|
----------
|
||||||
- When you install this module in a running company that have already PDF
|
- When you install this module in a running company that have already PDF
|
||||||
files stored into the database, you will lose them all.
|
files stored into the database, you will lose them all.
|
||||||
- After installing this module PDF's are no longer stored into the database,
|
- After installing this module PDF's are no longer stored into the database,
|
||||||
|
|
|
@ -42,18 +42,20 @@ You can then use any compatible browser to remotely see the attachments of OpenO
|
||||||
|
|
||||||
After installation, the WebDAV server can be controlled by a [webdav] section in
|
After installation, the WebDAV server can be controlled by a [webdav] section in
|
||||||
the server's config.
|
the server's config.
|
||||||
Server Configuration Parameter:
|
|
||||||
|
|
||||||
[webdav]
|
Server Configuration Parameter:
|
||||||
; enable = True ; Serve webdav over the http(s) servers
|
-------------------------------
|
||||||
; vdir = webdav ; the directory that webdav will be served at
|
[webdav]:
|
||||||
; this default val means that webdav will be
|
+++++++++
|
||||||
; on "http://localhost:8069/webdav/
|
* enable = True ; Serve webdav over the http(s) servers
|
||||||
; verbose = True ; Turn on the verbose messages of webdav
|
* vdir = webdav ; the directory that webdav will be served at
|
||||||
; debug = True ; Turn on the debugging messages of webdav
|
* this default val means that webdav will be
|
||||||
; since the messages are routed to the python logging, with
|
* on "http://localhost:8069/webdav/
|
||||||
; levels "debug" and "debug_rpc" respectively, you can leave
|
* verbose = True ; Turn on the verbose messages of webdav
|
||||||
; these options on
|
* debug = True ; Turn on the debugging messages of webdav
|
||||||
|
* since the messages are routed to the python logging, with
|
||||||
|
* levels "debug" and "debug_rpc" respectively, you can leave
|
||||||
|
* these options on
|
||||||
|
|
||||||
Also implements IETF RFC 5785 for services discovery on a http server,
|
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.
|
||||||
|
|
|
@ -53,8 +53,7 @@ These email templates are also at the heart of the marketing campaign system
|
||||||
(see the ``marketing_campaign`` application), if you need to automate larger
|
(see the ``marketing_campaign`` application), if you need to automate larger
|
||||||
campaigns on any OpenERP document.
|
campaigns on any OpenERP document.
|
||||||
|
|
||||||
Technical note: only the templating system of the original Power Email by
|
**Technical note:** only the templating system of the original Power Email by Openlabs was kept.
|
||||||
Openlabs was kept.
|
|
||||||
""",
|
""",
|
||||||
"data": [
|
"data": [
|
||||||
'wizard/email_template_preview_view.xml',
|
'wizard/email_template_preview_view.xml',
|
||||||
|
|
|
@ -30,14 +30,16 @@
|
||||||
Organization and management of Events.
|
Organization and management of Events.
|
||||||
======================================
|
======================================
|
||||||
|
|
||||||
This module allows you
|
This module allows you:
|
||||||
|
-----------------------
|
||||||
* to manage your events and their registrations
|
* to manage your events and their registrations
|
||||||
* to use emails to automatically confirm and send acknowledgements for any
|
* to use emails to automatically confirm and send acknowledgements for any
|
||||||
registration to an event
|
registration to an event
|
||||||
|
|
||||||
Note that:
|
Note that:
|
||||||
|
----------
|
||||||
- You can define new types of events in
|
- You can define new types of events in
|
||||||
Events/Configuration/Types of Events
|
**Events** / **Configuration** / **Types of Events**
|
||||||
""",
|
""",
|
||||||
'author': 'OpenERP SA',
|
'author': 'OpenERP SA',
|
||||||
'depends': ['base_setup', 'board', 'email_template', 'google_map'],
|
'depends': ['base_setup', 'board', 'email_template', 'google_map'],
|
||||||
|
|
|
@ -34,10 +34,10 @@ to avoid wasting time.
|
||||||
Now you have a simple way to create training or courses with OpenERP and moodle.
|
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 services >manage protocols activate the xmlrpc web service
|
>site administration >plugins >web services >manage protocols activate the xmlrpc web service
|
||||||
|
|
||||||
|
|
||||||
|
@ -48,16 +48,18 @@ STEPS TO CONFIGURE:
|
||||||
|
|
||||||
|
|
||||||
2. Create confirmation email with login and password.
|
2. Create confirmation email with login and password.
|
||||||
-----------------------------------------------------
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||||
We strongly suggest you to add those following lines at the bottom of your event
|
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.
|
confirmation email to communicate the login/password of moodle to your subscribers.
|
||||||
|
|
||||||
|
|
||||||
........your configuration text.......
|
........your configuration text.......
|
||||||
|
|
||||||
URL: your moodle link for exemple: http://openerp.moodle.com
|
**URL:** your moodle link for exemple: http://openerp.moodle.com
|
||||||
LOGIN: ${object.moodle_username}
|
|
||||||
PASSWORD: ${object.moodle_user_password}
|
**LOGIN:** ${object.moodle_username}
|
||||||
|
|
||||||
|
**PASSWORD:** ${object.moodle_user_password}
|
||||||
""",
|
""",
|
||||||
'author': 'OpenERP SA',
|
'author': 'OpenERP SA',
|
||||||
'depends': ['event'],
|
'depends': ['event'],
|
||||||
|
|
|
@ -35,9 +35,8 @@ these accounts will be automatically downloaded into your OpenERP system. All
|
||||||
POP3/IMAP-compatible servers are supported, included those that require an
|
POP3/IMAP-compatible servers are supported, included those that require an
|
||||||
encrypted SSL/TLS connection.
|
encrypted SSL/TLS connection.
|
||||||
|
|
||||||
This can be used to easily create email-based workflows for many email-enabled
|
This can be used to easily create email-based workflows for many email-enabled OpenERP documents, such as:
|
||||||
OpenERP documents, such as:
|
----------------------------------------------------------------------------------------------------------
|
||||||
|
|
||||||
* CRM Leads/Opportunities
|
* CRM Leads/Opportunities
|
||||||
* CRM Claims
|
* CRM Claims
|
||||||
* Project Issues
|
* Project Issues
|
||||||
|
|
|
@ -24,7 +24,10 @@
|
||||||
'name': 'Google Users',
|
'name': 'Google Users',
|
||||||
'version': '1.0',
|
'version': '1.0',
|
||||||
'category': 'Tools',
|
'category': 'Tools',
|
||||||
'description': """The module adds google user in res user.""",
|
'description': """
|
||||||
|
The module adds google user in res user.
|
||||||
|
========================================
|
||||||
|
""",
|
||||||
'author': 'OpenERP SA',
|
'author': 'OpenERP SA',
|
||||||
'website': 'http://www.openerp.com',
|
'website': 'http://www.openerp.com',
|
||||||
'depends': ['base'],
|
'depends': ['base'],
|
||||||
|
|
|
@ -34,5 +34,8 @@
|
||||||
'res_config_user_view.xml'
|
'res_config_user_view.xml'
|
||||||
],
|
],
|
||||||
'depends': ['google_base_account'],
|
'depends': ['google_base_account'],
|
||||||
'description': 'Module to attach a google document to any model.'
|
'description': """
|
||||||
|
Module to attach a google document to any model.
|
||||||
|
================================================
|
||||||
|
"""
|
||||||
}
|
}
|
||||||
|
|
|
@ -32,6 +32,7 @@ Module for Human Resource Management.
|
||||||
=====================================
|
=====================================
|
||||||
|
|
||||||
You can manage:
|
You can manage:
|
||||||
|
---------------
|
||||||
* Employees and hierarchies : You can define your employee with User and display hierarchies
|
* Employees and hierarchies : You can define your employee with User and display hierarchies
|
||||||
* HR Departments
|
* HR Departments
|
||||||
* HR Jobs
|
* HR Jobs
|
||||||
|
|
|
@ -31,6 +31,7 @@ This module aims to manage employee's expenses.
|
||||||
===============================================
|
===============================================
|
||||||
|
|
||||||
The whole workflow is implemented:
|
The whole workflow is implemented:
|
||||||
|
----------------------------------
|
||||||
* Draft expense
|
* Draft expense
|
||||||
* Confirmation of the sheet by the employee
|
* Confirmation of the sheet by the employee
|
||||||
* Validation by his manager
|
* Validation by his manager
|
||||||
|
|
|
@ -37,21 +37,24 @@ Implements a dashboard for human resource management that includes:
|
||||||
* Leaves
|
* Leaves
|
||||||
|
|
||||||
Note that:
|
Note that:
|
||||||
|
~~~~~~~~~~
|
||||||
- A synchronisation with an internal agenda (use of the CRM module) is
|
- A synchronisation with an internal agenda (use of the CRM module) is
|
||||||
possible: in order to automatically create a case when an holiday request
|
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
|
is accepted, you have to link the holidays status to a case section. You
|
||||||
can setup this info and your colour preferences in
|
can setup this info and your colour preferences in
|
||||||
Human Resources/Configuration/Leave Type
|
|
||||||
|
**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).
|
- 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:
|
- 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
|
* The first will allow to choose employees by department and is used by clicking the menu item located in
|
||||||
Reporting/Human Resources/Leaves/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
|
* The second will allow you to choose the holidays report for specific employees. Go on the list
|
||||||
Human Resources/Human Resources/Employees
|
**Human Resources** / **Human Resources** / **Employees**
|
||||||
then select the ones you want to choose, click on the print icon and select the option
|
then select the ones you want to choose, click on the print icon and select the option
|
||||||
'Leaves Summary'
|
'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
|
- 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
|
**Settings** / **Users** / **Users**
|
||||||
|
|
||||||
for example, you maybe will do it for the user 'admin'.
|
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'],
|
'images': ['images/hr_allocation_requests.jpeg', 'images/hr_leave_requests.jpeg', 'images/leaves_analysis.jpeg'],
|
||||||
|
|
|
@ -25,7 +25,7 @@
|
||||||
'category': 'Human Resources',
|
'category': 'Human Resources',
|
||||||
'description': """
|
'description': """
|
||||||
Generic Payroll system Integrated with Accounting.
|
Generic Payroll system Integrated with Accounting.
|
||||||
===================================================
|
==================================================
|
||||||
|
|
||||||
* Expense Encoding
|
* Expense Encoding
|
||||||
* Payment Encoding
|
* Payment Encoding
|
||||||
|
|
|
@ -33,17 +33,19 @@ This module helps you to easily encode and validate timesheet and attendances wi
|
||||||
* It will maintain attendances and track (sign in/sign out) events.
|
* It will maintain attendances and track (sign in/sign out) events.
|
||||||
* Track the timesheet lines.
|
* Track the timesheet lines.
|
||||||
|
|
||||||
Other tabs contains statistics views to help you analyse your
|
Other tabs contains statistics views to help you analyse your time or the time of your team:
|
||||||
time or the time of your team:
|
--------------------------------------------------------------------------------------------
|
||||||
* Time spent by day (with attendances)
|
* Time spent by day (with attendances)
|
||||||
* Time spent by project
|
* Time spent by project
|
||||||
|
|
||||||
This module also implements a complete timesheet validation process:
|
This module also implements a complete timesheet validation process:
|
||||||
|
--------------------------------------------------------------------
|
||||||
* Draft sheet
|
* Draft sheet
|
||||||
* Confirmation at the end of the period by the employee
|
* Confirmation at the end of the period by the employee
|
||||||
* Validation by the project manager
|
* Validation by the project manager
|
||||||
|
|
||||||
The validation can be configured in the company:
|
The validation can be configured in the company:
|
||||||
|
------------------------------------------------
|
||||||
* Period size (day, week, month, year)
|
* Period size (day, week, month, year)
|
||||||
* Maximal difference between timesheet and attendances
|
* Maximal difference between timesheet and attendances
|
||||||
""",
|
""",
|
||||||
|
|
|
@ -24,8 +24,8 @@
|
||||||
'version': '0.9',
|
'version': '0.9',
|
||||||
'category': 'Hidden/Dependency',
|
'category': 'Hidden/Dependency',
|
||||||
'description': """
|
'description': """
|
||||||
This module provide a class import_framework to help importing complex data from
|
This module provide a class import_framework to help importing complex data from other software.
|
||||||
other software.
|
================================================================================================
|
||||||
""",
|
""",
|
||||||
'author': 'OpenERP SA',
|
'author': 'OpenERP SA',
|
||||||
'website': 'http://www.openerp.com',
|
'website': 'http://www.openerp.com',
|
||||||
|
|
|
@ -23,7 +23,10 @@
|
||||||
'name': 'Google Import',
|
'name': 'Google Import',
|
||||||
'version': '1.0',
|
'version': '1.0',
|
||||||
'category': 'Customer Relationship Management',
|
'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',
|
'author': 'OpenERP SA',
|
||||||
'website': 'http://www.openerp.com',
|
'website': 'http://www.openerp.com',
|
||||||
'depends': ['base', 'import_base', 'google_base_account', 'base_calendar'],
|
'depends': ['base', 'import_base', 'google_base_account', 'base_calendar'],
|
||||||
|
|
|
@ -24,8 +24,9 @@
|
||||||
'version': '1.0',
|
'version': '1.0',
|
||||||
'category': 'Customer Relationship Management',
|
'category': 'Customer Relationship Management',
|
||||||
'description': """
|
'description': """
|
||||||
This Module Import SugarCRM Leads, Opportunities, Users, Accounts, Contacts, Employees,
|
This Module Import SugarCRM Leads, Opportunities, Users, Accounts, Contacts, Employees, Meetings, Phonecalls, Emails, Project and Project Tasks Data into OpenERP Module.
|
||||||
Meetings, Phonecalls, Emails, Project and Project Tasks Data into OpenERP Module.""",
|
=========================================================================================================================================================================
|
||||||
|
""",
|
||||||
'author': 'OpenERP SA',
|
'author': 'OpenERP SA',
|
||||||
'website': 'http://www.openerp.com',
|
'website': 'http://www.openerp.com',
|
||||||
'depends': ['import_base','crm', 'document'],
|
'depends': ['import_base','crm', 'document'],
|
||||||
|
|
|
@ -23,6 +23,7 @@
|
||||||
"version": "1.0",
|
"version": "1.0",
|
||||||
"description": """
|
"description": """
|
||||||
Argentinian accounting chart and tax localization.
|
Argentinian accounting chart and tax localization.
|
||||||
|
==================================================
|
||||||
|
|
||||||
Plan contable argentino e impuestos de acuerdo a disposiciones vigentes
|
Plan contable argentino e impuestos de acuerdo a disposiciones vigentes
|
||||||
|
|
||||||
|
|
|
@ -27,9 +27,10 @@
|
||||||
"category" : "Localization/Account Charts",
|
"category" : "Localization/Account Charts",
|
||||||
"depends" : ["account_chart", 'base_vat'],
|
"depends" : ["account_chart", 'base_vat'],
|
||||||
"description": """
|
"description": """
|
||||||
This module provides the standard Accounting Chart for Austria which is based on
|
This module provides the standard Accounting Chart for Austria which is based on the Template from BMF.gv.at.
|
||||||
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.""",
|
Please keep in mind that you should review and adapt it with your Accountant, before using it in a live Environment.
|
||||||
|
""",
|
||||||
"demo_xml" : [],
|
"demo_xml" : [],
|
||||||
"update_xml" : ['account_tax_code.xml',"account_chart.xml",'account_tax.xml',"l10n_chart_at_wizard.xml"],
|
"update_xml" : ['account_tax_code.xml',"account_chart.xml",'account_tax.xml',"l10n_chart_at_wizard.xml"],
|
||||||
"auto_install": False,
|
"auto_install": False,
|
||||||
|
|
|
@ -34,16 +34,20 @@ After installing this module, the Configuration wizard for accounting is launche
|
||||||
Thus, the pure copy of Chart Template is generated.
|
Thus, the pure copy of Chart Template is generated.
|
||||||
|
|
||||||
Wizards provided by this module:
|
Wizards provided by this module:
|
||||||
|
--------------------------------
|
||||||
* Partner VAT Intra: Enlist the partners with their related VAT and invoiced
|
* Partner VAT Intra: Enlist the partners with their related VAT and invoiced
|
||||||
amounts. Prepares an XML file format.
|
amounts. Prepares an XML file format.
|
||||||
Path to access : Invoicing/Reporting/Legal Reports/Belgium Statements/Partner VAT Intra
|
|
||||||
|
**Path to access :** Invoicing/Reporting/Legal Reports/Belgium Statements/Partner VAT Intra
|
||||||
* Periodical VAT Declaration: Prepares an XML file for Vat Declaration of
|
* Periodical VAT Declaration: Prepares an XML file for Vat Declaration of
|
||||||
the Main company of the User currently Logged in.
|
the Main company of the User currently Logged in.
|
||||||
Path to access : Invoicing/Reporting/Legal Reports/Belgium Statements/Periodical VAT Declaration
|
|
||||||
|
**Path to access :** Invoicing/Reporting/Legal Reports/Belgium Statements/Periodical VAT Declaration
|
||||||
* Annual Listing Of VAT-Subjected Customers: Prepares an XML file for Vat
|
* 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
|
Declaration of the Main company of the User currently Logged in Based on
|
||||||
Fiscal year.
|
Fiscal year.
|
||||||
Path to access : Invoicing/Reporting/Legal Reports/Belgium Statements/Annual Listing Of VAT-Subjected Customers
|
|
||||||
|
**Path to access :** Invoicing/Reporting/Legal Reports/Belgium Statements/Annual Listing Of VAT-Subjected Customers
|
||||||
|
|
||||||
""",
|
""",
|
||||||
'author': 'Noviat & OpenERP SA',
|
'author': 'Noviat & OpenERP SA',
|
||||||
|
|
|
@ -26,6 +26,7 @@
|
||||||
'version': '1.0',
|
'version': '1.0',
|
||||||
'description': """
|
'description': """
|
||||||
Accounting Data for Belgian Payroll Rules.
|
Accounting Data for Belgian Payroll Rules.
|
||||||
|
==========================================
|
||||||
""",
|
""",
|
||||||
|
|
||||||
'auto_install': True,
|
'auto_install': True,
|
||||||
|
|
|
@ -28,19 +28,19 @@
|
||||||
'category' : 'Localization',
|
'category' : 'Localization',
|
||||||
'description': """
|
'description': """
|
||||||
|
|
||||||
Belgian localisation for in- and outgoing invoices (prereq to account_coda):
|
Belgian localization for in- and outgoing invoices (prereq to account_coda):
|
||||||
|
============================================================================
|
||||||
- Rename 'reference' field labels to 'Communication'
|
- Rename 'reference' field labels to 'Communication'
|
||||||
- Add support for Belgian Structured Communication
|
- Add support for Belgian Structured Communication
|
||||||
|
|
||||||
A Structured Communication can be generated automatically on outgoing invoices
|
A Structured Communication can be generated automatically on outgoing invoices according to the following algorithms:
|
||||||
according to the following algorithms:
|
---------------------------------------------------------------------------------------------------------------------
|
||||||
|
|
||||||
1) Random : +++RRR/RRRR/RRRDD+++
|
1) Random : +++RRR/RRRR/RRRDD+++
|
||||||
R..R = Random Digits, DD = Check Digits
|
**R..R =** Random Digits, **DD =** Check Digits
|
||||||
2) Date : +++DOY/YEAR/SSSDD+++
|
2) Date : +++DOY/YEAR/SSSDD+++
|
||||||
DOY = Day of the Year, SSS = Sequence Number, DD = Check Digits)
|
**DOY =** Day of the Year, **SSS =** Sequence Number, **DD =** Check Digits
|
||||||
3) Customer Reference +++RRR/RRRR/SSSDDD+++
|
3) Customer Reference +++RRR/RRRR/SSSDDD+++
|
||||||
R..R = Customer Reference without non-numeric characters, SSS = Sequence Number, DD = Check Digits)
|
**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
|
The preferred type of Structured Communication and associated Algorithm can be
|
||||||
specified on the Partner records. A 'random' Structured Communication will
|
specified on the Partner records. A 'random' Structured Communication will
|
||||||
|
|
|
@ -26,7 +26,7 @@ Base module for the Brazilian localization.
|
||||||
===========================================
|
===========================================
|
||||||
|
|
||||||
This module consists in:
|
This module consists in:
|
||||||
|
------------------------
|
||||||
- Generic Brazilian chart of accounts
|
- Generic Brazilian chart of accounts
|
||||||
- Brazilian taxes such as:
|
- Brazilian taxes such as:
|
||||||
|
|
||||||
|
|
|
@ -21,20 +21,21 @@
|
||||||
|
|
||||||
{"name" : "Switzerland - Accounting",
|
{"name" : "Switzerland - Accounting",
|
||||||
"description" : """
|
"description" : """
|
||||||
Swiss localisation :
|
Swiss localization :
|
||||||
- DTA generation for a lot of payment types
|
====================
|
||||||
- BVR management (number generation, report.)
|
- DTA generation for a lot of payment types
|
||||||
- Import account move from the bank file (like v11)
|
- BVR management (number generation, report.)
|
||||||
- Simplify the way you handle the bank statement for reconciliation
|
- 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:
|
You can also add ZIP and bank completion with:
|
||||||
- l10n_ch_zip
|
----------------------------------------------
|
||||||
- l10n_ch_bank
|
- l10n_ch_zip
|
||||||
|
- l10n_ch_bank
|
||||||
|
|
||||||
Author: Camptocamp SA
|
**Author:** Camptocamp SA
|
||||||
Donors: Hasa Sàrl, Open Net Sàrl and Prisme Solutions Informatique SA
|
|
||||||
|
**Donors:** Hasa Sàrl, Open Net Sàrl and Prisme Solutions Informatique SA
|
||||||
------------------------------------------------------------------------
|
|
||||||
|
|
||||||
Module incluant la localisation Suisse de OpenERP revu et corrigé par Camptocamp.
|
Module incluant la localisation Suisse de OpenERP revu et corrigé par Camptocamp.
|
||||||
Cette nouvelle version comprend la gestion et l'émissionde BVR, le paiement
|
Cette nouvelle version comprend la gestion et l'émissionde BVR, le paiement
|
||||||
|
@ -43,16 +44,18 @@ et l'import du relevé de compte depuis la banque de manière automatisée. De p
|
||||||
nous avons intégré la définition de toutes les banques Suisses(adresse, swift et clearing).
|
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:
|
Par ailleurs, conjointement à ce module, nous proposons la complétion NPA:
|
||||||
|
|
||||||
Vous pouvez ajouter la completion des banques et des NPA avec with:
|
|
||||||
- l10n_ch_zip
|
|
||||||
- l10n_ch_bank
|
|
||||||
|
|
||||||
Auteur: Camptocamp SA
|
|
||||||
Donateurs: Hasa Sàrl, Open Net Sàrl and Prisme Solutions Informatique SA
|
|
||||||
|
|
||||||
--------------------------------------------------------------------------
|
--------------------------------------------------------------------------
|
||||||
|
Vous pouvez ajouter la completion des banques et des NPA avec with:
|
||||||
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||||
|
- l10n_ch_zip
|
||||||
|
- l10n_ch_bank
|
||||||
|
|
||||||
|
**Auteur:** Camptocamp SA
|
||||||
|
|
||||||
|
**Donateurs:** Hasa Sàrl, Open Net Sàrl and Prisme Solutions Informatique SA
|
||||||
|
|
||||||
TODO :
|
TODO :
|
||||||
|
------
|
||||||
- Implement bvr import partial reconciliation
|
- Implement bvr import partial reconciliation
|
||||||
- Replace wizard by osv_memory when possible
|
- Replace wizard by osv_memory when possible
|
||||||
- Add mising HELP
|
- Add mising HELP
|
||||||
|
|
|
@ -23,7 +23,7 @@
|
||||||
"version": "1.0",
|
"version": "1.0",
|
||||||
"description": """
|
"description": """
|
||||||
Chilean accounting chart and tax localization.
|
Chilean accounting chart and tax localization.
|
||||||
|
==============================================
|
||||||
Plan contable chileno e impuestos de acuerdo a disposiciones vigentes
|
Plan contable chileno e impuestos de acuerdo a disposiciones vigentes
|
||||||
|
|
||||||
""",
|
""",
|
||||||
|
|
|
@ -44,6 +44,7 @@ Chart of accounts for Costa Rica.
|
||||||
=================================
|
=================================
|
||||||
|
|
||||||
Includes:
|
Includes:
|
||||||
|
---------
|
||||||
* account.type
|
* account.type
|
||||||
* account.account.template
|
* account.account.template
|
||||||
* account.tax.template
|
* account.tax.template
|
||||||
|
|
|
@ -37,7 +37,7 @@ Spanish Charts of Accounts (PGCE 2008).
|
||||||
* Defines templates for sale and purchase VAT
|
* Defines templates for sale and purchase VAT
|
||||||
* Defines tax code templates
|
* Defines tax code templates
|
||||||
|
|
||||||
Note: You should install the l10n_ES_account_balance_report module for yearly
|
**Note:** You should install the l10n_ES_account_balance_report module for yearly
|
||||||
account reporting (balance, profit & losses).
|
account reporting (balance, profit & losses).
|
||||||
""",
|
""",
|
||||||
"license" : "GPL-3",
|
"license" : "GPL-3",
|
||||||
|
|
|
@ -51,7 +51,7 @@ and "service" VAT taxes. We consider that it is too "heavy" to have this by defa
|
||||||
in l10n_fr; companies that sell services to DOM-based companies should update the
|
in l10n_fr; companies that sell services to DOM-based companies should update the
|
||||||
configuration of their taxes and fiscal positions manually.
|
configuration of their taxes and fiscal positions manually.
|
||||||
|
|
||||||
Credits: Sistheo, Zeekom, CrysaLEAD, Akretion and Camptocamp.
|
**Credits:** Sistheo, Zeekom, CrysaLEAD, Akretion and Camptocamp.
|
||||||
""",
|
""",
|
||||||
"depends" : ['base_iban', 'account', 'account_chart', 'base_vat', 'l10n_fr_rib'],
|
"depends" : ['base_iban', 'account', 'account_chart', 'base_vat', 'l10n_fr_rib'],
|
||||||
"init_xml" : [],
|
"init_xml" : [],
|
||||||
|
|
|
@ -33,6 +33,7 @@ French Payroll Rules.
|
||||||
- New payslip report
|
- New payslip report
|
||||||
|
|
||||||
TODO :
|
TODO :
|
||||||
|
------
|
||||||
- Integration with holidays module for deduction and allowance
|
- Integration with holidays module for deduction and allowance
|
||||||
- Integration with hr_payroll_account for the automatic account_move_line
|
- Integration with hr_payroll_account for the automatic account_move_line
|
||||||
creation from the payslip
|
creation from the payslip
|
||||||
|
|
|
@ -27,12 +27,15 @@
|
||||||
This module lets users enter the banking details of Partners in the RIB format (French standard for bank accounts details).
|
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
|
RIB Bank Accounts can be entered in the "Accounting" tab of the Partner form by specifying the account type "RIB".
|
||||||
the account type "RIB". The four standard RIB fields will then become mandatory:
|
|
||||||
|
The four standard RIB fields will then become mandatory:
|
||||||
|
--------------------------------------------------------
|
||||||
- Bank Code
|
- Bank Code
|
||||||
- Office Code
|
- Office Code
|
||||||
- Account number
|
- Account number
|
||||||
- RIB key
|
- RIB key
|
||||||
|
|
||||||
As a safety measure, OpenERP will check the RIB key whenever a RIB is saved, and
|
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
|
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
|
this can only happen when the user presses the "save" button, for example on the
|
||||||
|
|
|
@ -37,6 +37,9 @@
|
||||||
'version': '0.1',
|
'version': '0.1',
|
||||||
'category': 'Localization/Account Charts',
|
'category': 'Localization/Account Charts',
|
||||||
'description': """
|
'description': """
|
||||||
|
This is the base module to manage the accounting chart for Honduras.
|
||||||
|
====================================================================
|
||||||
|
|
||||||
Agrega una nomenclatura contable para Honduras. También incluye impuestos y la
|
Agrega una nomenclatura contable para Honduras. También incluye impuestos y la
|
||||||
moneda Lempira. -- Adds accounting chart for Honduras. It also includes taxes
|
moneda Lempira. -- Adds accounting chart for Honduras. It also includes taxes
|
||||||
and the Lempira currency.""",
|
and the Lempira currency.""",
|
||||||
|
|
|
@ -22,8 +22,8 @@
|
||||||
"name": "Peru Localization Chart Account",
|
"name": "Peru Localization Chart Account",
|
||||||
"version": "1.0",
|
"version": "1.0",
|
||||||
"description": """
|
"description": """
|
||||||
Peruvian accounting chart and tax localization. Acording the PCGE 2010.
|
Peruvian accounting chart and tax localization. According the PCGE 2010.
|
||||||
|
========================================================================
|
||||||
Plan contable peruano e impuestos de acuerdo a disposiciones vigentes de la
|
Plan contable peruano e impuestos de acuerdo a disposiciones vigentes de la
|
||||||
SUNAT 2011 (PCGE 2010).
|
SUNAT 2011 (PCGE 2010).
|
||||||
|
|
||||||
|
|
|
@ -29,9 +29,13 @@ This module implements the accounting chart for OHADA area.
|
||||||
===========================================================
|
===========================================================
|
||||||
|
|
||||||
It allows any company or association to manage its financial accounting.
|
It allows any company or association to manage its financial accounting.
|
||||||
|
|
||||||
Countries that use OHADA are the following:
|
Countries that use OHADA are the following:
|
||||||
|
-------------------------------------------
|
||||||
Benin, Burkina Faso, Cameroon, Central African Republic, Comoros, Congo,
|
Benin, Burkina Faso, Cameroon, Central African Republic, Comoros, Congo,
|
||||||
|
|
||||||
Ivory Coast, Gabon, Guinea, Guinea Bissau, Equatorial Guinea, Mali, Niger,
|
Ivory Coast, Gabon, Guinea, Guinea Bissau, Equatorial Guinea, Mali, Niger,
|
||||||
|
|
||||||
Replica of Democratic Congo, Senegal, Chad, Togo.
|
Replica of Democratic Congo, Senegal, Chad, Togo.
|
||||||
""",
|
""",
|
||||||
"website": "http://www.baamtu.com",
|
"website": "http://www.baamtu.com",
|
||||||
|
|
|
@ -24,8 +24,8 @@
|
||||||
'version': '1.0',
|
'version': '1.0',
|
||||||
'category': 'Localization/Account Charts',
|
'category': 'Localization/Account Charts',
|
||||||
'description': """
|
'description': """
|
||||||
This is the latest UK OpenERP localisation necessary to run OpenERP accounting
|
This is the latest UK OpenERP localisation necessary to run OpenERP accounting for UK SME's with:
|
||||||
for UK SME's with:
|
=================================================================================================
|
||||||
- a CT600-ready chart of accounts
|
- a CT600-ready chart of accounts
|
||||||
- VAT100-ready tax structure
|
- VAT100-ready tax structure
|
||||||
- InfoLogic UK counties listing
|
- InfoLogic UK counties listing
|
||||||
|
|
|
@ -25,6 +25,7 @@
|
||||||
"category": 'Localization/Account Charts',
|
"category": 'Localization/Account Charts',
|
||||||
"description": """
|
"description": """
|
||||||
United States - Chart of accounts.
|
United States - Chart of accounts.
|
||||||
|
==================================
|
||||||
""",
|
""",
|
||||||
'website': 'http://www.openerp.com',
|
'website': 'http://www.openerp.com',
|
||||||
'init_xml': [],
|
'init_xml': [],
|
||||||
|
|
|
@ -26,9 +26,8 @@
|
||||||
"sequence": 2,
|
"sequence": 2,
|
||||||
"summary": "Discussions, Mailing Lists, News",
|
"summary": "Discussions, Mailing Lists, News",
|
||||||
'description': """
|
'description': """
|
||||||
A business oriented Social Networking with a fully-integrated email
|
A business oriented Social Networking with a fully-integrated email and message management.
|
||||||
and message management.
|
===========================================================================================
|
||||||
=====================================================================
|
|
||||||
|
|
||||||
The Social Networking module provides an unified social network
|
The Social Networking module provides an unified social network
|
||||||
abstraction layer allowing applications to display a complete
|
abstraction layer allowing applications to display a complete
|
||||||
|
@ -40,6 +39,7 @@ allows to follow documents, and to be constantly updated about recent
|
||||||
news.
|
news.
|
||||||
|
|
||||||
The main features of the module are:
|
The main features of the module are:
|
||||||
|
------------------------------------
|
||||||
* a clean and renewed communication history for any OpenERP
|
* 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 discussion mean on documents,
|
||||||
|
|
|
@ -35,6 +35,7 @@ This module provides leads automation through marketing campaigns (campaigns can
|
||||||
=========================================================================================================================================
|
=========================================================================================================================================
|
||||||
|
|
||||||
The campaigns are dynamic and multi-channels. The process is as follows:
|
The campaigns are dynamic and multi-channels. The process is as follows:
|
||||||
|
------------------------------------------------------------------------
|
||||||
* Design marketing campaigns like workflows, including email templates to
|
* Design marketing campaigns like workflows, including email templates to
|
||||||
send, reports to print and send by email, custom actions
|
send, reports to print and send by email, custom actions
|
||||||
* Define input segments that will select the items that should enter the
|
* Define input segments that will select the items that should enter the
|
||||||
|
@ -49,7 +50,7 @@ The campaigns are dynamic and multi-channels. The process is as follows:
|
||||||
While the campaign runs you can of course continue to fine-tune the parameters,
|
While the campaign runs you can of course continue to fine-tune the parameters,
|
||||||
input segments, workflow.
|
input segments, workflow.
|
||||||
|
|
||||||
Note: If you need demo data, you can install the marketing_campaign_crm_demo
|
**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
|
module, but this will also install the CRM application as it depends on
|
||||||
CRM Leads.
|
CRM Leads.
|
||||||
""",
|
""",
|
||||||
|
|
|
@ -29,6 +29,7 @@ This module allows you to manage all operations for managing memberships.
|
||||||
=========================================================================
|
=========================================================================
|
||||||
|
|
||||||
It supports different kind of members:
|
It supports different kind of members:
|
||||||
|
--------------------------------------
|
||||||
* Free member
|
* Free member
|
||||||
* Associated member (e.g.: a group subscribes to a membership for all subsidiaries)
|
* Associated member (e.g.: a group subscribes to a membership for all subsidiaries)
|
||||||
* Paid members
|
* Paid members
|
||||||
|
|
|
@ -33,11 +33,13 @@ When finishing/confirming, cancelling manufacturing orders set all state lines
|
||||||
to the according state.
|
to the according state.
|
||||||
|
|
||||||
Create menus:
|
Create menus:
|
||||||
Manufacturing > Manufacturing > Work Orders
|
-------------
|
||||||
|
**Manufacturing** > **Manufacturing** > **Work Orders**
|
||||||
|
|
||||||
Which is a view on "Work Orders" lines in manufacturing order.
|
Which is a view on "Work Orders" lines in manufacturing order.
|
||||||
|
|
||||||
Add buttons in the form view of manufacturing order under workorders tab:
|
Add buttons in the form view of manufacturing order under workorders tab:
|
||||||
|
-------------------------------------------------------------------------
|
||||||
* start (set state to confirm), set date_start
|
* start (set state to confirm), set date_start
|
||||||
* done (set state to done), set date_stop
|
* done (set state to done), set date_stop
|
||||||
* set to draft (set state to draft)
|
* set to draft (set state to draft)
|
||||||
|
|
|
@ -29,6 +29,7 @@ The aim is to have a complete module to manage all products repairs.
|
||||||
====================================================================
|
====================================================================
|
||||||
|
|
||||||
The following topics should be covered by this module:
|
The following topics should be covered by this module:
|
||||||
|
------------------------------------------------------
|
||||||
* Add/remove products in the reparation
|
* Add/remove products in the reparation
|
||||||
* Impact for stocks
|
* Impact for stocks
|
||||||
* Invoicing (products and/or services)
|
* Invoicing (products and/or services)
|
||||||
|
|
|
@ -31,9 +31,11 @@ This module allows you to produce several products from one production order.
|
||||||
You can configure sub-products in the bill of material.
|
You can configure sub-products in the bill of material.
|
||||||
|
|
||||||
Without this module:
|
Without this module:
|
||||||
|
--------------------
|
||||||
A + B + C -> D
|
A + B + C -> D
|
||||||
|
|
||||||
With this module:
|
With this module:
|
||||||
|
-----------------
|
||||||
A + B + C -> D + E
|
A + B + C -> D + E
|
||||||
""",
|
""",
|
||||||
'author': 'OpenERP SA',
|
'author': 'OpenERP SA',
|
||||||
|
|
|
@ -25,6 +25,7 @@
|
||||||
"category": "Project Management",
|
"category": "Project Management",
|
||||||
'description': """
|
'description': """
|
||||||
This module adds a PAD in all project kanban views.
|
This module adds a PAD in all project kanban views.
|
||||||
|
===================================================
|
||||||
""",
|
""",
|
||||||
'author': 'OpenERP SA',
|
'author': 'OpenERP SA',
|
||||||
'website': 'http://www.openerp.com',
|
'website': 'http://www.openerp.com',
|
||||||
|
|
|
@ -26,6 +26,7 @@
|
||||||
'category': 'Hidden/Dependency',
|
'category': 'Hidden/Dependency',
|
||||||
'description': """
|
'description': """
|
||||||
The common interface for plug-in.
|
The common interface for plug-in.
|
||||||
|
=================================
|
||||||
""",
|
""",
|
||||||
'author': 'OpenERP SA',
|
'author': 'OpenERP SA',
|
||||||
'website': 'http://www.openerp.com',
|
'website': 'http://www.openerp.com',
|
||||||
|
|
|
@ -31,7 +31,7 @@
|
||||||
'category': 'Portal',
|
'category': 'Portal',
|
||||||
'description': """
|
'description': """
|
||||||
Customize access to your OpenERP database to external users by creating portals.
|
Customize access to your OpenERP database to external users by creating portals.
|
||||||
|
================================================================================
|
||||||
A portal defines a specific user menu and access rights for its members. This
|
A portal defines a specific user menu and access rights for its members. This
|
||||||
menu can ben seen by portal members, anonymous users and any other user that
|
menu can ben seen by portal members, anonymous users and any other user that
|
||||||
have the access to technical features (e.g. the administrator).
|
have the access to technical features (e.g. the administrator).
|
||||||
|
|
|
@ -26,8 +26,8 @@
|
||||||
'category': 'Tools',
|
'category': 'Tools',
|
||||||
'complexity': "easy",
|
'complexity': "easy",
|
||||||
'description': """
|
'description': """
|
||||||
This module adds claim menu and features to your portal if claim and portal are
|
This module adds claim menu and features to your portal if claim and portal are installed.
|
||||||
installed.
|
==========================================================================================
|
||||||
""",
|
""",
|
||||||
'author': 'OpenERP SA',
|
'author': 'OpenERP SA',
|
||||||
'depends': ['crm_claim','portal'],
|
'depends': ['crm_claim','portal'],
|
||||||
|
|
|
@ -26,8 +26,8 @@
|
||||||
'category': 'Tools',
|
'category': 'Tools',
|
||||||
'complexity': "easy",
|
'complexity': "easy",
|
||||||
'description': """
|
'description': """
|
||||||
This module adds a contact page (with a contact form creating a lead when
|
This module adds a contact page (with a contact form creating a lead when submitted) to your portal if crm and portal are installed.
|
||||||
submitted) to your portal if crm and portal are installed.
|
====================================================================================================================================
|
||||||
""",
|
""",
|
||||||
'author': 'OpenERP SA',
|
'author': 'OpenERP SA',
|
||||||
'depends': ['crm','portal'],
|
'depends': ['crm','portal'],
|
||||||
|
|
|
@ -26,8 +26,8 @@
|
||||||
'category': 'Tools',
|
'category': 'Tools',
|
||||||
'complexity': "easy",
|
'complexity': "easy",
|
||||||
'description': """
|
'description': """
|
||||||
This module adds event menu and features to your portal if event and portal are
|
This module adds event menu and features to your portal if event and portal are installed.
|
||||||
installed.
|
==========================================================================================
|
||||||
""",
|
""",
|
||||||
'author': 'OpenERP SA',
|
'author': 'OpenERP SA',
|
||||||
'depends': ['event','portal'],
|
'depends': ['event','portal'],
|
||||||
|
|
|
@ -26,8 +26,8 @@
|
||||||
'category': 'Tools',
|
'category': 'Tools',
|
||||||
'complexity': "easy",
|
'complexity': "easy",
|
||||||
'description': """
|
'description': """
|
||||||
This module adds a list of employees to your portal's contact page if hr and
|
This module adds a list of employees to your portal's contact page if hr and portal_crm (which creates the contact page) are installed.
|
||||||
portal_crm (which creates the contact page) are installed.
|
=======================================================================================================================================
|
||||||
""",
|
""",
|
||||||
'author': 'OpenERP SA',
|
'author': 'OpenERP SA',
|
||||||
'depends': ['hr','portal_crm'],
|
'depends': ['hr','portal_crm'],
|
||||||
|
|
|
@ -26,8 +26,8 @@
|
||||||
'category': 'Tools',
|
'category': 'Tools',
|
||||||
'complexity': "easy",
|
'complexity': "easy",
|
||||||
'description': """
|
'description': """
|
||||||
This module adds project menu and features (tasks) to your portal if project
|
This module adds project menu and features (tasks) to your portal if project and portal are installed.
|
||||||
and portal are installed.
|
======================================================================================================
|
||||||
""",
|
""",
|
||||||
'author': 'OpenERP SA',
|
'author': 'OpenERP SA',
|
||||||
'depends': ['project','portal'],
|
'depends': ['project','portal'],
|
||||||
|
|
|
@ -26,8 +26,8 @@
|
||||||
'category': 'Tools',
|
'category': 'Tools',
|
||||||
'complexity': "easy",
|
'complexity': "easy",
|
||||||
'description': """
|
'description': """
|
||||||
This module adds issue menu and features to your portal if project_issue and
|
This module adds issue menu and features to your portal if project_issue and portal are installed.
|
||||||
portal are installed.
|
==================================================================================================
|
||||||
""",
|
""",
|
||||||
'author': 'OpenERP SA',
|
'author': 'OpenERP SA',
|
||||||
'depends': ['project_issue','portal'],
|
'depends': ['project_issue','portal'],
|
||||||
|
|
|
@ -26,8 +26,8 @@
|
||||||
'category': 'Tools',
|
'category': 'Tools',
|
||||||
'complexity': "easy",
|
'complexity': "easy",
|
||||||
'description': """
|
'description': """
|
||||||
This module adds sale menu and features to your portal if sale and portal are
|
This module adds sale menu and features to your portal if sale and portal are installed.
|
||||||
installed.
|
========================================================================================
|
||||||
""",
|
""",
|
||||||
'author': 'OpenERP SA',
|
'author': 'OpenERP SA',
|
||||||
'depends': ['sale','portal'],
|
'depends': ['sale','portal'],
|
||||||
|
|
|
@ -28,8 +28,9 @@
|
||||||
This module shows the basic processes involved in the selected modules and in the sequence they occur.
|
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.
|
**Note:** This applies to the modules containing modulename_process.xml.
|
||||||
e.g product/process/product_process.xml.
|
|
||||||
|
**e.g.** product/process/product_process.xml.
|
||||||
|
|
||||||
""",
|
""",
|
||||||
'author': 'OpenERP SA',
|
'author': 'OpenERP SA',
|
||||||
|
|
|
@ -36,6 +36,7 @@ Products support variants, different pricing methods, suppliers information,
|
||||||
make to stock/order, different unit of measures, packaging and properties.
|
make to stock/order, different unit of measures, packaging and properties.
|
||||||
|
|
||||||
Pricelists support:
|
Pricelists support:
|
||||||
|
-------------------
|
||||||
* Multiple-level of discount (by product, category, quantities)
|
* Multiple-level of discount (by product, category, quantities)
|
||||||
* Compute price based on different criteria:
|
* Compute price based on different criteria:
|
||||||
* Other pricelist
|
* Other pricelist
|
||||||
|
|
|
@ -30,6 +30,7 @@ Track different dates on products and production lots.
|
||||||
======================================================
|
======================================================
|
||||||
|
|
||||||
Following dates can be tracked:
|
Following dates can be tracked:
|
||||||
|
-------------------------------
|
||||||
- end of life
|
- end of life
|
||||||
- best before date
|
- best before date
|
||||||
- removal date
|
- removal date
|
||||||
|
|
|
@ -30,6 +30,7 @@ A module that adds manufacturers and attributes on the product form.
|
||||||
====================================================================
|
====================================================================
|
||||||
|
|
||||||
You can now define the following for a product:
|
You can now define the following for a product:
|
||||||
|
-----------------------------------------------
|
||||||
* Manufacturer
|
* Manufacturer
|
||||||
* Manufacturer Product Name
|
* Manufacturer Product Name
|
||||||
* Manufacturer Product Code
|
* Manufacturer Product Code
|
||||||
|
|
|
@ -28,7 +28,7 @@ This module lets you calculate discounts on Sale Order lines and Invoice lines b
|
||||||
|
|
||||||
To this end, a new check box named "Visible Discount" is added to the pricelist form.
|
To this end, a new check box named "Visible Discount" is added to the pricelist form.
|
||||||
|
|
||||||
Example:
|
**Example:**
|
||||||
For the product PC1 and the partner "Asustek": if listprice=450, and the price
|
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
|
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.
|
will have on the sale order line: Unit price=450, Discount=50,00, Net price=225.
|
||||||
|
|
|
@ -36,6 +36,7 @@ Allows creating tasks based on new emails arriving at a given mailbox,
|
||||||
similarly to what the CRM application has for Leads/Opportunities.
|
similarly to what the CRM application has for Leads/Opportunities.
|
||||||
|
|
||||||
There are two common alternatives to configure the mailbox integration:
|
There are two common alternatives to configure the mailbox integration:
|
||||||
|
-----------------------------------------------------------------------
|
||||||
* Install the ``fetchmail`` module and configure a new mailbox, then select
|
* Install the ``fetchmail`` module and configure a new mailbox, then select
|
||||||
``Project Tasks`` as the target for incoming emails.
|
``Project Tasks`` as the target for incoming emails.
|
||||||
* Set it up manually on your mail server based on the 'mail gateway' script
|
* Set it up manually on your mail server based on the 'mail gateway' script
|
||||||
|
|
|
@ -38,6 +38,7 @@ This module adds a new Report Engine based on WebKit library (wkhtmltopdf) to su
|
||||||
The module structure and some code is inspired by the report_openoffice module.
|
The module structure and some code is inspired by the report_openoffice module.
|
||||||
|
|
||||||
The module allows:
|
The module allows:
|
||||||
|
------------------
|
||||||
- HTML report definition
|
- HTML report definition
|
||||||
- Multi header support
|
- Multi header support
|
||||||
- Multi logo
|
- Multi logo
|
||||||
|
@ -56,7 +57,7 @@ For a sample report see also the webkit_report_sample module, and this video:
|
||||||
http://files.me.com/nbessi/06n92k.mov
|
http://files.me.com/nbessi/06n92k.mov
|
||||||
|
|
||||||
Requirements and Installation:
|
Requirements and Installation:
|
||||||
-----------------------------
|
------------------------------
|
||||||
This module requires the ``wkthtmltopdf`` library to render HTML documents as
|
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
|
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).
|
http://code.google.com/p/wkhtmltopdf/ for Linux, Mac OS X (i386) and Windows (32bits).
|
||||||
|
|
|
@ -31,7 +31,7 @@ The base module to manage quotations and sales orders.
|
||||||
|
|
||||||
Workflow with validation steps:
|
Workflow with validation steps:
|
||||||
-------------------------------
|
-------------------------------
|
||||||
* Quotation -> Sales order -> Invoice
|
* **Quotation** -> **Sales order** -> **Invoice**
|
||||||
|
|
||||||
Create Invoice:
|
Create Invoice:
|
||||||
---------------
|
---------------
|
||||||
|
@ -46,10 +46,10 @@ Partners preferences:
|
||||||
* Invoicing
|
* Invoicing
|
||||||
|
|
||||||
Products stocks and prices:
|
Products stocks and prices:
|
||||||
--------------------------
|
---------------------------
|
||||||
|
|
||||||
Delivery method:
|
Delivery method:
|
||||||
-----------------
|
----------------
|
||||||
* The Poste
|
* The Poste
|
||||||
* Free Delivery Charges
|
* Free Delivery Charges
|
||||||
* Normal Delivery Charges
|
* Normal Delivery Charges
|
||||||
|
|
|
@ -30,17 +30,19 @@ The sales journal modules allows you to categorise your sales and deliveries (pi
|
||||||
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:
|
You can use journal for different purposes, some examples:
|
||||||
|
----------------------------------------------------------
|
||||||
* isolate sales of different departments
|
* isolate sales of different departments
|
||||||
* journals for deliveries by truck or by UPS
|
* journals for deliveries by truck or by UPS
|
||||||
|
|
||||||
Journals have a responsible and evolves between different status:
|
Journals have a responsible and evolves between different status:
|
||||||
|
-----------------------------------------------------------------
|
||||||
* draft, open, cancel, done.
|
* draft, open, cancel, done.
|
||||||
|
|
||||||
Batch operations can be processed on the different journals to confirm all sales
|
Batch operations can be processed on the different journals to confirm all sales
|
||||||
at once, to validate or invoice packing.
|
at once, to validate or invoice packing.
|
||||||
|
|
||||||
It also supports batch invoicing methods that can be configured by partners and
|
It also supports batch invoicing methods that can be configured by partners and sales orders, examples:
|
||||||
sales orders, examples:
|
-------------------------------------------------------------------------------------------------------
|
||||||
* daily invoicing
|
* daily invoicing
|
||||||
* monthly invoicing
|
* monthly invoicing
|
||||||
|
|
||||||
|
|
|
@ -29,6 +29,7 @@ Add additional date information to the sales order.
|
||||||
===================================================
|
===================================================
|
||||||
|
|
||||||
You can add the following additional dates to a sale order:
|
You can add the following additional dates to a sale order:
|
||||||
|
-----------------------------------------------------------
|
||||||
* Requested Date
|
* Requested Date
|
||||||
* Commitment Date
|
* Commitment Date
|
||||||
* Effective Date
|
* Effective Date
|
||||||
|
|
|
@ -29,6 +29,7 @@ OpenERP Inventory Management module can manage multi-warehouses, multi and struc
|
||||||
======================================================================================================
|
======================================================================================================
|
||||||
|
|
||||||
Thanks to the double entry management, the inventory controlling is powerful and flexible:
|
Thanks to the double entry management, the inventory controlling is powerful and flexible:
|
||||||
|
------------------------------------------------------------------------------------------
|
||||||
* Moves history and planning,
|
* Moves history and planning,
|
||||||
* Stock valuation (standard or average price, ...)
|
* Stock valuation (standard or average price, ...)
|
||||||
* Robustness faced with Inventory differences
|
* Robustness faced with Inventory differences
|
||||||
|
|
|
@ -29,12 +29,13 @@ This module supplements the Warehouse application by effectively implementing Pu
|
||||||
============================================================================================================
|
============================================================================================================
|
||||||
|
|
||||||
Typically this could be used to:
|
Typically this could be used to:
|
||||||
|
--------------------------------
|
||||||
* Manage product manufacturing chains
|
* Manage product manufacturing chains
|
||||||
* Manage default locations per product
|
* Manage default locations per product
|
||||||
* Define routes within your warehouse according to business needs, such as:
|
* Define routes within your warehouse according to business needs, such as:
|
||||||
- Quality Control
|
- Quality Control
|
||||||
- After Sales Services
|
- After Sales Services
|
||||||
- Supplier Returns
|
- Supplier Returns
|
||||||
|
|
||||||
* Help rental management, by generating automated return moves for rented products
|
* Help rental management, by generating automated return moves for rented products
|
||||||
|
|
||||||
|
@ -84,9 +85,10 @@ Use-Case:
|
||||||
---------
|
---------
|
||||||
|
|
||||||
You can use the demo data as follow:
|
You can use the demo data as follow:
|
||||||
CPU1: Sell some CPU1 from Chicago Shop and run the scheduler
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||||
|
**CPU1:** Sell some CPU1 from Chicago Shop and run the scheduler
|
||||||
- Warehouse: delivery order, Chicago Shop: reception
|
- Warehouse: delivery order, Chicago Shop: reception
|
||||||
CPU3:
|
**CPU3:**
|
||||||
- When receiving the product, it goes to Quality Control location then
|
- When receiving the product, it goes to Quality Control location then
|
||||||
stored to shelf 2.
|
stored to shelf 2.
|
||||||
- When delivering the customer: Pick List -> Packing -> Delivery Order from Gate A
|
- When delivering the customer: Pick List -> Packing -> Delivery Order from Gate A
|
||||||
|
|
|
@ -46,17 +46,20 @@ Forecast" and "Stock Planning" to emphasize that we use quantity values.
|
||||||
Where to begin:
|
Where to begin:
|
||||||
---------------
|
---------------
|
||||||
Using this module is done in three steps:
|
Using this module is done in three steps:
|
||||||
* Create Stock Periods via the Warehouse>Configuration>Stock Periods menu
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||||
|
* Create Stock Periods via the **Warehouse** > **Configuration** > **Stock Periods** menu
|
||||||
(Mandatory step)
|
(Mandatory step)
|
||||||
* Create Sale Forecasts fill them with forecast quantities, via the
|
* Create Sale Forecasts fill them with forecast quantities, via the
|
||||||
Sales > Sales Forecast menu. (Optional step but useful for further planning)
|
**Sales** > **Sales Forecast** menu. (Optional step but useful for further planning)
|
||||||
* Create the actual MPS plan, check the balance and trigger the procurements
|
* 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.
|
as required. The actual procurement is the final step for the Stock Period.
|
||||||
|
|
||||||
Stock Period configuration:
|
Stock Period configuration:
|
||||||
---------------------------
|
---------------------------
|
||||||
You have two menu items for Periods in "Warehouse > Configuration > Stock Periods".
|
You have two menu items for Periods in "**Warehouse** > **Configuration** > **Stock Periods**".
|
||||||
|
|
||||||
There are:
|
There are:
|
||||||
|
~~~~~~~~~~
|
||||||
* "Create Stock Periods" - can automatically creating daily, weekly or
|
* "Create Stock Periods" - can automatically creating daily, weekly or
|
||||||
monthly periods.
|
monthly periods.
|
||||||
* "Stock Periods" - allows to create any type of periods, change the dates
|
* "Stock Periods" - allows to create any type of periods, change the dates
|
||||||
|
@ -67,6 +70,7 @@ button in "Stock Periods", but it is recommended to use the automatic assistant
|
||||||
"Create Stock Periods".
|
"Create Stock Periods".
|
||||||
|
|
||||||
Remarks:
|
Remarks:
|
||||||
|
++++++++
|
||||||
- These periods (Stock Periods) are completely distinct from Financial or
|
- These periods (Stock Periods) are completely distinct from Financial or
|
||||||
other periods in the system.
|
other periods in the system.
|
||||||
- Periods are not assigned to companies (when you use multicompany). Module
|
- Periods are not assigned to companies (when you use multicompany). Module
|
||||||
|
@ -86,7 +90,8 @@ Remarks:
|
||||||
|
|
||||||
Sales Forecasts configuration:
|
Sales Forecasts configuration:
|
||||||
------------------------------
|
------------------------------
|
||||||
You have few menus for Sales forecast in "Sales > Sales Forecasts":
|
You have few menus for Sales forecast in "**Sales** > **Sales Forecasts**":
|
||||||
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||||
- "Create Sales Forecasts" - can automatically create forecast lines
|
- "Create Sales Forecasts" - can automatically create forecast lines
|
||||||
according to your needs
|
according to your needs
|
||||||
- "Sales Forecasts" - for managing the Sales forecasts
|
- "Sales Forecasts" - for managing the Sales forecasts
|
||||||
|
@ -96,6 +101,7 @@ Category, for selected Period and for selected Warehouse.
|
||||||
It is also possible to copy the previous forecast.
|
It is also possible to copy the previous forecast.
|
||||||
|
|
||||||
Remarks:
|
Remarks:
|
||||||
|
++++++++
|
||||||
- This tool doesn't duplicate lines if you already have an entry for the same
|
- 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
|
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
|
wish to create another forecast, if relevant lines exists you have to do it
|
||||||
|
@ -130,8 +136,9 @@ MPS or Procurement Planning:
|
||||||
----------------------------
|
----------------------------
|
||||||
An MPS planning consists in Stock Planning lines, used to analyze and possibly
|
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.
|
drive the procurement of products for each relevant Stock Period and Warehouse.
|
||||||
The menu is located in "Warehouse > Schedulers > Master Procurement Schedule":
|
|
||||||
|
|
||||||
|
The menu is located in "**Warehouse** > **Schedulers** > **Master Procurement Schedule**":
|
||||||
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||||
- "Create Stock Planning Lines" - a wizard to help automatically create many
|
- "Create Stock Planning Lines" - a wizard to help automatically create many
|
||||||
planning lines
|
planning lines
|
||||||
- "Master Procurement Schedule" - management of your planning lines
|
- "Master Procurement Schedule" - management of your planning lines
|
||||||
|
@ -186,16 +193,14 @@ Computation of Stock Simulation quantities:
|
||||||
The Stock Simulation value is the estimated stock quantity at the end of the
|
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
|
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.
|
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 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:
|
When you calculate period next to current:
|
||||||
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||||
Stock Simulation = Stock of beginning of current Period - Planned Out of current 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 .
|
||||||
+ 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
|
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
|
the calculation in the current Period is a little bit different. First you should
|
||||||
|
@ -204,18 +209,14 @@ that you should complete the planning and procurement of the current Period befo
|
||||||
going to the next one.
|
going to the next one.
|
||||||
|
|
||||||
When you plan for future Periods:
|
When you plan for future Periods:
|
||||||
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||||
Stock Simulation = Stock of beginning of current 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.
|
||||||
- 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
|
Here "Periods before calculated" designates all periods starting with the current
|
||||||
until the period before the one being calculated.
|
until the period before the one being calculated.
|
||||||
|
|
||||||
Remarks:
|
Remarks:
|
||||||
|
++++++++
|
||||||
- Remember to make the proceed with the planning of each period in chronological
|
- Remember to make the proceed with the planning of each period in chronological
|
||||||
order, otherwise the numbers will not reflect the reality
|
order, otherwise the numbers will not reflect the reality
|
||||||
- If you planned for future periods and find that real Confirmed Out is larger
|
- If you planned for future periods and find that real Confirmed Out is larger
|
||||||
|
|
|
@ -31,6 +31,7 @@ Create recurring documents.
|
||||||
This module allows to create new documents and add subscriptions on that document.
|
This module allows to create new documents and add subscriptions on that document.
|
||||||
|
|
||||||
e.g. To have an invoice generated automatically periodically:
|
e.g. To have an invoice generated automatically periodically:
|
||||||
|
-------------------------------------------------------------
|
||||||
* Define a document type based on Invoice object
|
* Define a document type based on Invoice object
|
||||||
* Define a subscription whose source document is the document defined as
|
* Define a subscription whose source document is the document defined as
|
||||||
above. Specify the interval information and partner to be invoice.
|
above. Specify the interval information and partner to be invoice.
|
||||||
|
|
|
@ -5,8 +5,9 @@
|
||||||
'complexity': "easy",
|
'complexity': "easy",
|
||||||
"description":
|
"description":
|
||||||
"""
|
"""
|
||||||
OpenERP Web LinkedIn module.
|
OpenERP Web LinkedIn module.
|
||||||
This module provides the Integration of the LinkedIn with OpenERP.
|
============================
|
||||||
|
This module provides the Integration of the LinkedIn with OpenERP.
|
||||||
""",
|
""",
|
||||||
'update_xml': [
|
'update_xml': [
|
||||||
'web_linkedin_view.xml',
|
'web_linkedin_view.xml',
|
||||||
|
|
|
@ -27,6 +27,7 @@ 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 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.
|
Add a Shortcut icon besides the views title in order to add/remove a shortcut.
|
||||||
""",
|
""",
|
||||||
'author': 'OpenERP SA',
|
'author': 'OpenERP SA',
|
||||||
|
|
Loading…
Reference in New Issue