[MERGE, IMP] improve and merge cha branch to update desc formatting
bzr revid: psi@tinyerp.com-20120716094548-xx1ip3eljal3ffvl
This commit is contained in:
Purnendu Singh (OpenERP)
commit
2e2f7188d3
|
|
@ -29,20 +29,20 @@ Accounting and Financial Management.
|
|||
|
||||
Financial and accounting module that covers:
|
||||
--------------------------------------------
|
||||
General accountings
|
||||
Cost/Analytic accounting
|
||||
Third party accounting
|
||||
Taxes management
|
||||
Budgets
|
||||
Customer and Supplier Invoices
|
||||
Bank statements
|
||||
Reconciliation process by partner
|
||||
* General accountings
|
||||
* Cost/Analytic accounting
|
||||
* Third party accounting
|
||||
* Taxes management
|
||||
* Budgets
|
||||
* Customer and Supplier Invoices
|
||||
* Bank statements
|
||||
* Reconciliation process by partner
|
||||
|
||||
Creates a dashboard for accountants that includes:
|
||||
--------------------------------------------------
|
||||
* List of Customer Invoice to Approve
|
||||
* Company Analysis
|
||||
* Graph of Treasury
|
||||
* List of Customer Invoice to Approve
|
||||
* Company Analysis
|
||||
* Graph of Treasury
|
||||
|
||||
The processes like maintaining of general ledger is done through the defined financial Journals (entry move line orgrouping is maintained through journal) for a particular
|
||||
financial year and for preparation of vouchers there is a module named account_voucher.
|
||||
|
|
|
|||
|
|
@ -28,10 +28,10 @@
|
|||
Accounting Access Rights.
|
||||
=========================
|
||||
|
||||
This module gives the admin user the access to all the accounting features
|
||||
This module gives the Admin user the access to all the accounting features
|
||||
like the journal items and the chart of accounts.
|
||||
|
||||
It assigns manager and user access rights to the Administrator, and only
|
||||
It assigns manager and user access rights to the Administrator and only
|
||||
user rights to Demo user.
|
||||
""",
|
||||
'website': 'http://www.openerp.com',
|
||||
|
|
|
|||
|
|
@ -30,7 +30,7 @@ This module is for modifying account analytic view to show important data to pro
|
|||
|
||||
Adds menu to show relevant information to each manager.
|
||||
You can also view the report of account analytic summary
|
||||
user-wise as well as month wise.
|
||||
user-wise as well as month-wise.
|
||||
""",
|
||||
"author": "Camptocamp",
|
||||
"website": "http://www.camptocamp.com/",
|
||||
|
|
|
|||
|
|
@ -23,15 +23,17 @@
|
|||
'name' : 'Account Analytic Defaults',
|
||||
'version' : '1.0',
|
||||
"category": 'Accounting & Finance',
|
||||
'description': """Set default values for your analytic accounts
|
||||
Allows to automatically select analytic accounts based on criterions:
|
||||
=====================================================================
|
||||
'description': """
|
||||
Set default values for your analytic accounts.
|
||||
=============================================
|
||||
|
||||
* Product
|
||||
* Partner
|
||||
* User
|
||||
* Company
|
||||
* Date
|
||||
Allows to automatically select analytic accounts based on criterions:
|
||||
---------------------------------------------------------------------
|
||||
* Product
|
||||
* Partner
|
||||
* User
|
||||
* Company
|
||||
* Date
|
||||
""",
|
||||
'author' : 'OpenERP SA',
|
||||
'website' : 'http://www.openerp.com',
|
||||
|
|
|
|||
|
|
@ -25,7 +25,7 @@
|
|||
'version': '1.0',
|
||||
'category': 'Accounting & Finance',
|
||||
'description': """
|
||||
This module allows to use several analytic plans, according to the general journal.
|
||||
This module allows to use several analytic plans according to the general journal.
|
||||
===================================================================================
|
||||
|
||||
Here multiple analytic lines are created when the invoice or the entries
|
||||
|
|
@ -55,6 +55,7 @@ Plan2:
|
|||
|
||||
So when this line of invoice will be confirmed, it will generate 3 analytic lines,
|
||||
for one account entry.
|
||||
|
||||
The analytic plan validates the minimum and maximum percentage at the time of creation
|
||||
of distribution models.
|
||||
""",
|
||||
|
|
|
|||
|
|
@ -27,12 +27,15 @@
|
|||
This module supports the Anglo-Saxon accounting methodology by changing the accounting logic with stock transactions.
|
||||
=====================================================================================================================
|
||||
|
||||
The difference between the Anglo-Saxon accounting countries
|
||||
and the Rhine or also called Continental accounting countries is the moment of taking the Cost of Goods Sold versus Cost of Sales.
|
||||
Anglo-Saxons accounting does take the cost when sales invoice is created, Continental accounting will take the cost at the moment the goods are shipped.
|
||||
This module will add this functionality by using a interim account, to store the value of shipped goods and will contra book this interim account
|
||||
when the invoice is created to transfer this amount to the debtor or creditor account.
|
||||
Secondly, price differences between actual purchase price and fixed product standard price are booked on a separate account""",
|
||||
The difference between the Anglo-Saxon accounting countries and the Rhine (or also called
|
||||
Continental accounting) countries is the moment of taking the Cost of Goods Sold versus
|
||||
Cost of Sales. Anglo-Saxons accounting does take the cost when sales invoice is created,
|
||||
Continental accounting will take the cost at the moment the goods are shipped.
|
||||
|
||||
This module will add this functionality by using a interim account, to store the value of
|
||||
shipped goods and will contra book this interim account when the invoice is created to
|
||||
transfer this amount to the debtor or creditor account. Secondly, price differences between
|
||||
actual purchase price and fixed product standard price are booked on a separate account.""",
|
||||
"images": ["images/account_anglo_saxon.jpeg"],
|
||||
"depends": ["product", "purchase"],
|
||||
"category": "Hidden/Dependency",
|
||||
|
|
|
|||
|
|
@ -27,6 +27,7 @@
|
|||
"description": """
|
||||
Financial and accounting asset management.
|
||||
==========================================
|
||||
|
||||
This Module manages the assets owned by a company or an individual. It will keep track of depreciation's occurred on those assets.
|
||||
And it allows to create Move's of the depreciation lines.
|
||||
|
||||
|
|
|
|||
|
|
@ -27,15 +27,16 @@
|
|||
'category': 'Generic Modules/Accounting',
|
||||
'description': '''
|
||||
Module that extends the standard account_bank_statement_line object for improved e-banking support.
|
||||
===================================================================================================
|
||||
|
||||
Adds
|
||||
- valuta date
|
||||
- batch payments
|
||||
- traceability of changes to bank statement lines
|
||||
- bank statement line views
|
||||
- bank statements balances report
|
||||
- performance improvements for digital import of bank statement (via 'ebanking_import' context flag)
|
||||
- name_search on res.partner.bank enhanced to allow search on bank and iban account numbers
|
||||
This module adds:
|
||||
- valuta date
|
||||
- batch payments
|
||||
- traceability of changes to bank statement lines
|
||||
- bank statement line views
|
||||
- bank statements balances report
|
||||
- performance improvements for digital import of bank statement (via 'ebanking_import' context flag)
|
||||
- name_search on res.partner.bank enhanced to allow search on bank and iban account numbers
|
||||
''',
|
||||
'depends': ['account'],
|
||||
'demo_xml': [],
|
||||
|
|
|
|||
|
|
@ -28,19 +28,20 @@
|
|||
This module allows accountants to manage analytic and crossovered budgets.
|
||||
==========================================================================
|
||||
|
||||
Once the Budgets are defined (in Invoicing/Budgets/Budgets),
|
||||
the Project Managers can set the planned amount on each Analytic Account.
|
||||
Once the Budgets are defined (in Invoicing/Budgets/Budgets), the Project Managers
|
||||
can set the planned amount on each Analytic Account.
|
||||
|
||||
The accountant has the possibility to see the total of amount planned for each
|
||||
Budget in order to ensure the total planned is not greater/lower than what he planned
|
||||
for this Budget. Each list of record can also be switched to a graphical view of it.
|
||||
|
||||
Three reports are available:
|
||||
|
||||
1. The first is available from a list of Budgets. It gives the spreading, for these Budgets, of the Analytic Accounts.
|
||||
|
||||
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',
|
||||
'website': 'http://www.openerp.com',
|
||||
|
|
|
|||
|
|
@ -28,7 +28,8 @@
|
|||
Allows cancelling accounting entries.
|
||||
=====================================
|
||||
|
||||
This module adds 'Allow Cancelling Entries' field on form view of account journal. If set to true it allows user to cancel entries & invoices.
|
||||
This module adds 'Allow Cancelling Entries' field on form view of account journal.
|
||||
If set to true it allows user to cancel entries & invoices.
|
||||
""",
|
||||
'website': 'http://www.openerp.com',
|
||||
"images" : ["images/account_cancel.jpeg"],
|
||||
|
|
|
|||
|
|
@ -24,7 +24,7 @@
|
|||
"author" : "OpenERP SA, NovaPoint Group",
|
||||
"category": "Generic Modules/Accounting",
|
||||
"description": """
|
||||
Module for the Check writing and check printing
|
||||
Module for the Check Writing and Check Printing.
|
||||
""",
|
||||
'website': 'http://www.openerp.com',
|
||||
'init_xml': [],
|
||||
|
|
|
|||
|
|
@ -29,37 +29,40 @@ Module to import CODA bank statements.
|
|||
======================================
|
||||
|
||||
Supported are CODA flat files in V2 format from Belgian bank accounts.
|
||||
* CODA v1 support.
|
||||
* CODA v2.2 support.
|
||||
* Foreign Currency support.
|
||||
* Support for all data record types (0, 1, 2, 3, 4, 8, 9).
|
||||
* Parsing & logging of all Transaction Codes and Structured Format Communications.
|
||||
* Automatic Financial Journal assignment via CODA configuration parameters.
|
||||
* Support for multiple Journals per Bank Account Number.
|
||||
* Support for multiple statements from different bank accounts in a single CODA file.
|
||||
* Support for 'parsing only' CODA Bank Accounts (defined as type='info' in the CODA Bank Account configuration records).
|
||||
* Multi-language CODA parsing, parsing configuration data provided for EN, NL, FR.
|
||||
* CODA v1 support.
|
||||
* CODA v2.2 support.
|
||||
* Foreign Currency support.
|
||||
* Support for all data record types (0, 1, 2, 3, 4, 8, 9).
|
||||
* Parsing & logging of all Transaction Codes and Structured Format Communications.
|
||||
* Automatic Financial Journal assignment via CODA configuration parameters.
|
||||
* Support for multiple Journals per Bank Account Number.
|
||||
* Support for multiple statements from different bank accounts in a single CODA file.
|
||||
* Support for 'parsing only' CODA Bank Accounts (defined as type='info' in the CODA Bank Account configuration records).
|
||||
* Multi-language CODA parsing, parsing configuration data provided for EN, NL, FR.
|
||||
|
||||
The machine readable CODA Files are parsed and stored in human readable format in CODA Bank Statements.
|
||||
Also Bank Statements are generated containing a subset of the CODA information (only those transaction lines
|
||||
that are required for the creation of the Financial Accounting records).
|
||||
The CODA Bank Statement is a 'read-only' object, hence remaining a reliable representation of the original CODA file
|
||||
whereas the Bank Statement will get modified as required by accounting business processes.
|
||||
The machine readable CODA Files are parsed and stored in human readable format in
|
||||
CODA Bank Statements. Also Bank Statements are generated containing a subset of
|
||||
the CODA information (only those transaction lines that are required for the creation
|
||||
of the Financial Accounting records). The CODA Bank Statement is a 'read-only'
|
||||
object, hence remaining a reliable representation of the original CODA file whereas
|
||||
the Bank Statement will get modified as required by accounting business processes.
|
||||
|
||||
CODA Bank Accounts configured as type 'Info' will only generate CODA Bank Statements.
|
||||
|
||||
A removal of one object in the CODA processing results in the removal of the associated objects.
|
||||
The removal of a CODA File containing multiple Bank Statements will also remove those associated
|
||||
statements.
|
||||
A removal of one object in the CODA processing results in the removal of the associated
|
||||
objects. The removal of a CODA File containing multiple Bank Statements will also
|
||||
remove those associated statements.
|
||||
|
||||
The following reconciliation logic has been implemented in the CODA processing:
|
||||
|
||||
1) The Company's Bank Account Number of the CODA statement is compared against the Bank Account Number field of the Company's CODA Bank Account configuration records (whereby bank accounts defined in type='info' configuration records are ignored). If this is the case an 'internal transfer' transaction is generated using the 'Internal Transfer Account' field of the CODA File Import wizard.
|
||||
2) As a second step the 'Structured Communication' field of the CODA transaction line is matched against the reference field of in- and outgoing invoices (supported : Belgian Structured Communication Type).
|
||||
3) When the previous step doesn't find a match, the transaction counterparty is located via the Bank Account Number configured on the OpenERP Customer and Supplier records.
|
||||
4) In case the previous steps are not successful, the transaction is generated by using the 'Default Account for Unrecognized Movement' field of the CODA File Import wizard in order to allow further manual processing.
|
||||
|
||||
In stead of a manual adjustment of the generated Bank Statements, you can also re-import the CODA
|
||||
after updating the OpenERP database with the information that was missing to allow automatic reconciliation.
|
||||
In stead of a manual adjustment of the generated Bank Statements, you can also
|
||||
re-import the CODA after updating the OpenERP database with the information that
|
||||
was missing to allow automatic reconciliation.
|
||||
|
||||
Remark on CODA V1 support:
|
||||
In some cases a transaction code, transaction category or structured communication code has been given a new or clearer description in CODA V2.
|
||||
|
|
|
|||
|
|
@ -28,16 +28,21 @@ Module to automate letters for unpaid invoices, with multi-level recalls.
|
|||
==========================================================================
|
||||
|
||||
You can define your multiple levels of recall through the menu:
|
||||
|
||||
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
|
||||
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 of recall defined. You can define different policies
|
||||
for different companies. You can also send mail to the customer.
|
||||
It will generate a PDF with all the letters according to the the different levels
|
||||
of recall defined. You can define different policies for different companies. You
|
||||
can also send mail to the customer.
|
||||
|
||||
Note that if you want to check the follow-up level for a given partner/account
|
||||
entry, you can do from in the menu:
|
||||
|
||||
Note that if you want to check the follow-up level for a given partner/account entry, you can do from in the menu:
|
||||
Invoicing/Reporting/Generic Reporting/Partners/Follow-ups Sent
|
||||
|
||||
""",
|
||||
|
|
|
|||
|
|
@ -29,8 +29,8 @@ Module to manage the payment of your supplier invoices.
|
|||
=======================================================
|
||||
|
||||
This module allows you to create and manage your payment orders, with purposes to
|
||||
* serve as base for an easy plug-in of various automated payment mechanisms.
|
||||
* provide a more efficient way to manage invoice payment.
|
||||
* serve as base for an easy plug-in of various automated payment mechanisms.
|
||||
* provide a more efficient way to manage invoice payment.
|
||||
|
||||
Warning:
|
||||
--------
|
||||
|
|
|
|||
|
|
@ -27,7 +27,6 @@
|
|||
eInvoicing & Payments module manage all Voucher Entries such as "Reconciliation Entries", "Adjustment Entries", "Closing or Opening Entries" for Sales, Purchase, Bank, Cash, Expense, Contra.
|
||||
==============================================================================================================================================================================================
|
||||
|
||||
|
||||
* Voucher Entry
|
||||
* Voucher Receipt [Sales & Purchase]
|
||||
* Voucher Payment [Customer & Supplier]
|
||||
|
|
|
|||
|
|
@ -31,7 +31,7 @@ Module for defining analytic accounting object.
|
|||
===============================================
|
||||
|
||||
In OpenERP, analytic accounts are linked to general accounts but are treated
|
||||
totally independently. So you can enter various different analytic operations
|
||||
totally independently. So, you can enter various different analytic operations
|
||||
that have no counterpart in the general financial accounts.
|
||||
""",
|
||||
"init_xml" : [],
|
||||
|
|
|
|||
|
|
@ -26,7 +26,6 @@
|
|||
'category': 'Hidden',
|
||||
'description': """
|
||||
This module is for modifying project view to show some data related to the hr_expense module.
|
||||
======================================================================================================
|
||||
|
||||
""",
|
||||
"author": "OpenERP S.A.",
|
||||
|
|
|
|||
|
|
@ -26,7 +26,6 @@
|
|||
'category': 'Hidden',
|
||||
'description': """
|
||||
This module is for modifying account analytic view to show some data related to the hr_expense module.
|
||||
======================================================================================================
|
||||
|
||||
""",
|
||||
"author": "OpenERP S.A.",
|
||||
|
|
|
|||
|
|
@ -27,7 +27,7 @@
|
|||
"website" : "http://www.openerp.com",
|
||||
"depends" : ["project", "account_analytic_analysis"],
|
||||
"description": """
|
||||
Add "Contract Data" in project view.
|
||||
Add "Contract Data" in project view.
|
||||
""",
|
||||
"init_xml" : [],
|
||||
"update_xml": ["analytic_contract_project_view.xml"],
|
||||
|
|
|
|||
|
|
@ -28,9 +28,13 @@
|
|||
This module allows you to define what is the default function of a specific user on a given account.
|
||||
====================================================================================================
|
||||
|
||||
This is mostly used when a user encodes his timesheet: the values are retrieved and the fields are auto-filled. But the possibility to change these values is still available.
|
||||
This is mostly used when a user encodes his timesheet: the values are retrieved
|
||||
and the fields are auto-filled. But the possibility to change these values is
|
||||
still available.
|
||||
|
||||
Obviously if no data has been recorded for the current account, the default value is given as usual by the employee data so that this module is perfectly compatible with older configurations.
|
||||
Obviously if no data has been recorded for the current account, the default
|
||||
value is given as usual by the employee data so that this module is perfectly
|
||||
compatible with older configurations.
|
||||
|
||||
""",
|
||||
'author': 'OpenERP SA',
|
||||
|
|
|
|||
|
|
@ -30,7 +30,7 @@ This module allows you to anonymize a database.
|
|||
===============================================
|
||||
|
||||
This module allows you to keep your data confidential for a given database.
|
||||
This process is useful if you want to use the migration process and protect
|
||||
This process is useful, if you want to use the migration process and protect
|
||||
your own or your customer’s confidential data. The principle is that you run
|
||||
an anonymization tool which will hide your confidential data(they are replaced
|
||||
by ‘XXX’ characters). Then you can send the anonymized database to the migration
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
{
|
||||
'name': 'Anonymous',
|
||||
'description': 'Allow anonymous access to OpenERP',
|
||||
'description': 'Allow anonymous access to OpenERP.',
|
||||
'author': 'OpenERP SA',
|
||||
'version': '1.0',
|
||||
'category': 'Tools',
|
||||
|
|
|
|||
|
|
@ -28,7 +28,8 @@
|
|||
This module is to configure modules related to an association.
|
||||
==============================================================
|
||||
|
||||
It installs the profile for associations to manage events, registrations, memberships, membership products (schemes).
|
||||
It installs the profile for associations to manage events, registrations, memberships,
|
||||
membership products (schemes).
|
||||
""",
|
||||
'author': 'OpenERP SA',
|
||||
'depends': ['base_setup', 'membership', 'event'],
|
||||
|
|
|
|||
|
|
@ -28,8 +28,8 @@
|
|||
This module lets administrator track every user operation on all the objects of the system.
|
||||
===========================================================================================
|
||||
|
||||
The administrator can subscribe to rules for read, write and
|
||||
delete on objects and can check logs.
|
||||
The administrator can subscribe to rules for read, write and delete on objects
|
||||
and can check logs.
|
||||
""",
|
||||
'author': 'OpenERP SA',
|
||||
'website': 'http://www.openerp.com',
|
||||
|
|
|
|||
|
|
@ -29,7 +29,7 @@ This module allows to implement action rules for any object.
|
|||
|
||||
Use automated actions to automatically trigger actions for various screens.
|
||||
|
||||
Example: a lead created by a specific user may be automatically set to a specific
|
||||
Example: A lead created by a specific user may be automatically set to a specific
|
||||
sales team, or an opportunity which still has status pending after 14 days might
|
||||
trigger an automatic reminder email.
|
||||
""",
|
||||
|
|
|
|||
|
|
@ -26,35 +26,34 @@
|
|||
"website" : "http://www.openerp.com",
|
||||
"category" : "Tools",
|
||||
"description": """
|
||||
Replaces cleartext passwords in the database with a secure hash
|
||||
===============================================================
|
||||
For your existing user base, the removal of the cleartext
|
||||
passwords occurs immediately when you instal base_crypt.
|
||||
Replaces cleartext passwords in the database with a secure hash.
|
||||
================================================================
|
||||
|
||||
All passwords will be replaced by a secure, salted, cryptographic
|
||||
hash, preventing anyone from reading the original password in
|
||||
the database.
|
||||
For your existing user base, the removal of the cleartext passwords occurs
|
||||
immediately when you instal base_crypt.
|
||||
|
||||
After installing this module it won't be possible to recover a
|
||||
forgotten password for your users, the only solution is for an
|
||||
admin to set a new password.
|
||||
All passwords will be replaced by a secure, salted, cryptographic hash,
|
||||
preventing anyone from reading the original password in the database.
|
||||
|
||||
Security Warning
|
||||
++++++++++++++++
|
||||
After installing this module, it won't be possible to recover a forgotten password
|
||||
for your users, the only solution is for an admin to set a new password.
|
||||
|
||||
Security Warning:
|
||||
-----------------
|
||||
Installing this module does not mean you can ignore other security measures,
|
||||
as the password is still transmitted unencrypted on the network, unless you
|
||||
are using a secure protocol such as XML-RPCS or HTTPS.
|
||||
|
||||
It also does not protect the rest of the content of the database, which may
|
||||
contain critical data. Appropriate security measures need to be implemented
|
||||
by the system administrator in all areas, such as: protection of database
|
||||
backups, system files, remote shell access, physical server access.
|
||||
|
||||
Interation with LDAP authentication
|
||||
+++++++++++++++++++++++++++++++++++
|
||||
Interation with LDAP authentication:
|
||||
------------------------------------
|
||||
This module is currently not compatible with the ``user_ldap`` module and
|
||||
will disable LDAP authentication completely if installed at the same time.
|
||||
|
||||
""",
|
||||
""",
|
||||
"depends" : ["base"],
|
||||
"data" : [],
|
||||
"auto_install": False,
|
||||
|
|
|
|||
|
|
@ -23,10 +23,11 @@
|
|||
'version': '1.0',
|
||||
"category": 'Hidden/Dependency',
|
||||
'description': """
|
||||
This module installs the base for IBAN (International Bank Account Number) bank accounts and checks for its validity.
|
||||
This module installs the base for IBAN (International Bank Account Number) bank accounts and checks for it's validity.
|
||||
=====================================================================================================================
|
||||
|
||||
The ability to extract the correctly represented local accounts from IBAN accounts with a single statement.
|
||||
The ability to extract the correctly represented local accounts from IBAN accounts
|
||||
with a single statement.
|
||||
""",
|
||||
'author': 'OpenERP SA',
|
||||
'website': 'http://www.openerp.com',
|
||||
|
|
|
|||
|
|
@ -28,18 +28,17 @@
|
|||
This module allows you to create a new module without any development.
|
||||
======================================================================
|
||||
|
||||
It records all operations on objects during the recording session and
|
||||
produce a .ZIP module. So you can create your own module directly from
|
||||
the OpenERP client.
|
||||
It records all operations on objects during the recording session and produce a
|
||||
.ZIP module. So you can create your own module directly from the OpenERP client.
|
||||
|
||||
This version works for creating and updating existing records. It recomputes
|
||||
dependencies and links for all types of widgets (many2one, many2many, ...).
|
||||
It also support workflows and demo/update data.
|
||||
|
||||
This should help you to easily create reusable and publishable modules
|
||||
for custom configurations and demo/testing data.
|
||||
This should help you to easily create reusable and publishable modules for custom
|
||||
configurations and demo/testing data.
|
||||
|
||||
How to use it:
|
||||
How to use it?:
|
||||
Run Settings/Technical/Module Creation/Export Customizations As a Module wizard.
|
||||
Select datetime criteria of recording and objects to be recorded and Record module.
|
||||
""",
|
||||
|
|
|
|||
|
|
@ -28,9 +28,8 @@
|
|||
This module is used along with OpenERP OpenOffice Plugin.
|
||||
=========================================================
|
||||
|
||||
This module adds wizards to Import/Export .sxw report that
|
||||
you can modify in OpenOffice. Once you have modified it you can
|
||||
upload the report using the same wizard.
|
||||
This module adds wizards to Import/Export .sxw report that you can modify in OpenOffice.
|
||||
Once you have modified it you can upload the report using the same wizard.
|
||||
""",
|
||||
'author': 'OpenERP SA',
|
||||
'website': 'http://www.openerp.com',
|
||||
|
|
|
|||
|
|
@ -26,6 +26,7 @@
|
|||
'description': """
|
||||
This module handles state and stage. It is derived from the crm_base and
|
||||
crm_case classes from crm.
|
||||
========================================================================
|
||||
|
||||
* ``base_state``: state management
|
||||
* ``base_stage``: stage management
|
||||
|
|
|
|||
|
|
@ -24,8 +24,8 @@
|
|||
'version': '1.0',
|
||||
"category": 'Hidden/Dependency',
|
||||
'description': """
|
||||
VAT validation for Partners' VAT numbers
|
||||
========================================
|
||||
VAT validation for Partner's VAT numbers.
|
||||
=========================================
|
||||
|
||||
After installing this module, values entered in the VAT field of Partners will
|
||||
be validated for all supported countries. The country is inferred from the
|
||||
|
|
@ -50,7 +50,6 @@ There are two different levels of VAT number validation:
|
|||
Supported countries currently include EU countries, and a few non-EU countries
|
||||
such as Chile, Colombia, Mexico, Norway or Russia. For unsupported countries,
|
||||
only the country code will be validated.
|
||||
|
||||
""",
|
||||
'author': 'OpenERP SA',
|
||||
'depends': ['account'],
|
||||
|
|
|
|||
|
|
@ -31,6 +31,7 @@ The generic OpenERP Customer Relationship Management.
|
|||
|
||||
This system enables a group of people to intelligently and efficiently manage
|
||||
leads, opportunities, meeting, phonecall.
|
||||
|
||||
It manages key tasks such as communication, identification, prioritization,
|
||||
assignment, resolution and notification.
|
||||
|
||||
|
|
@ -41,13 +42,14 @@ specific methods and lots of other actions based on your own enterprise rules.
|
|||
The greatest thing about this system is that users don't need to do anything
|
||||
special. They can just send email to the request tracker. OpenERP will take
|
||||
care of thanking them for their message, automatically routing it to the
|
||||
appropriate staff, and make sure all future correspondence gets to the right
|
||||
appropriate staff and make sure all future correspondence gets to the right
|
||||
place.
|
||||
|
||||
The CRM module has a email gateway for the synchronisation interface
|
||||
between mails and OpenERP.
|
||||
|
||||
Creates a dashboard for CRM that includes:
|
||||
------------------------------------------
|
||||
* List of New Leads
|
||||
* List of My Opportunities
|
||||
* List of My Next Meetings
|
||||
|
|
|
|||
|
|
@ -29,7 +29,7 @@
|
|||
Caldav features in Meeting.
|
||||
===========================
|
||||
|
||||
* Share meeting with other calendar clients like sunbird
|
||||
* Share meeting with other calendar clients like sunbird
|
||||
""",
|
||||
'author': 'OpenERP SA',
|
||||
'website': 'http://www.openerp.com',
|
||||
|
|
|
|||
|
|
@ -28,11 +28,15 @@
|
|||
This module allows users to perform segmentation within partners.
|
||||
=================================================================
|
||||
|
||||
It uses the profiles criteria from the earlier segmentation module and improve it. Thanks to the new concept of questionnaire. You can now regroup questions into a questionnaire and directly use it on a partner.
|
||||
It uses the profiles criteria from the earlier segmentation module and improve it.
|
||||
Thanks to the new concept of questionnaire. You can now regroup questions into a
|
||||
questionnaire and directly use it on a partner.
|
||||
|
||||
It also has been merged with the earlier CRM & SRM segmentation tool because they were overlapping.
|
||||
It also has been merged with the earlier CRM & SRM segmentation tool because they
|
||||
were overlapping.
|
||||
|
||||
* Note: this module is not compatible with the module segmentation, since it's the same which has been renamed.
|
||||
* Note: this module is not compatible with the module segmentation, since
|
||||
it's the same which has been renamed.
|
||||
""",
|
||||
'author': 'OpenERP SA',
|
||||
'website': 'http://www.openerp.com',
|
||||
|
|
|
|||
|
|
@ -28,10 +28,9 @@
|
|||
Allows you to add delivery methods in sale orders and picking.
|
||||
==============================================================
|
||||
|
||||
You can define your own carrier and delivery grids for prices.
|
||||
When creating invoices from picking, OpenERP is able to add and compute the shipping line.
|
||||
|
||||
""",
|
||||
You can define your own carrier and delivery grids for prices. When creating
|
||||
invoices from picking, OpenERP is able to add and compute the shipping line.
|
||||
""",
|
||||
'author': 'OpenERP SA',
|
||||
'depends': ['sale', 'purchase', 'stock'],
|
||||
'init_xml': ['delivery_data.xml'],
|
||||
|
|
|
|||
|
|
@ -29,7 +29,7 @@ This is a complete document management system.
|
|||
==============================================
|
||||
|
||||
* User Authentication
|
||||
* Document Indexation :- .pptx and .docx files are not supported in Windows platform.
|
||||
* Document Indexation:- .pptx and .docx files are not supported in Windows platform.
|
||||
* Dashboard for Document that includes:
|
||||
* New Files (list)
|
||||
* Files by Resource Type (graph)
|
||||
|
|
@ -37,8 +37,8 @@ This is a complete document management system.
|
|||
* Files Size by Month (graph)
|
||||
|
||||
ATTENTION:
|
||||
- When you install this module in a running company that have already PDF files stored into the database,
|
||||
you will lose them all.
|
||||
- When you install this module in a running company that have already PDF
|
||||
files stored into the database, you will lose them all.
|
||||
- After installing this module PDF's are no longer stored into the database,
|
||||
but in the servers rootpad like /server/bin/filestore.
|
||||
""",
|
||||
|
|
|
|||
|
|
@ -40,7 +40,8 @@ With this module, the WebDAV server for documents is activated.
|
|||
|
||||
You can then use any compatible browser to remotely see the attachments of OpenObject.
|
||||
|
||||
After installation, the WebDAV server can be controlled by a [webdav] section in the server's config.
|
||||
After installation, the WebDAV server can be controlled by a [webdav] section in
|
||||
the server's config.
|
||||
Server Configuration Parameter:
|
||||
|
||||
[webdav]
|
||||
|
|
@ -55,7 +56,7 @@ Server Configuration Parameter:
|
|||
; these options on
|
||||
|
||||
Also implements IETF RFC 5785 for services discovery on a http server,
|
||||
which needs explicit configuration in openerp-server.conf, too.
|
||||
which needs explicit configuration in openerp-server.conf too.
|
||||
""",
|
||||
"depends" : ["base", "document"],
|
||||
"init_xml" : [],
|
||||
|
|
|
|||
|
|
@ -23,15 +23,14 @@
|
|||
'version': '1.0',
|
||||
'category': 'Tools',
|
||||
'description': """
|
||||
Provides a common EDI platform that other Applications can use
|
||||
==============================================================
|
||||
Provides a common EDI platform that other Applications can use.
|
||||
===============================================================
|
||||
|
||||
OpenERP specifies a generic EDI format for exchanging business
|
||||
documents between different systems, and provides generic
|
||||
mechanisms to import and export them.
|
||||
OpenERP specifies a generic EDI format for exchanging business documents between
|
||||
different systems, and provides generic mechanisms to import and export them.
|
||||
|
||||
More details about OpenERP's EDI format may be found in the
|
||||
technical OpenERP documentation at http://doc.openerp.com
|
||||
More details about OpenERP's EDI format may be found in the technical OpenERP
|
||||
documentation at http://doc.openerp.com.
|
||||
""",
|
||||
'author': 'OpenERP SA',
|
||||
'website': 'http://www.openerp.com',
|
||||
|
|
|
|||
|
|
@ -28,8 +28,8 @@
|
|||
"category" : "Marketing",
|
||||
"depends" : ['mail'],
|
||||
"description": """
|
||||
Email Templating (simplified version of the original Power Email by Openlabs)
|
||||
=============================================================================
|
||||
Email Templating (simplified version of the original Power Email by Openlabs).
|
||||
==============================================================================
|
||||
|
||||
Lets you design complete email templates related to any OpenERP document (Sale
|
||||
Orders, Invoices and so on), including sender, recipient, subject, body (HTML and
|
||||
|
|
@ -54,8 +54,7 @@ These email templates are also at the heart of the marketing campaign system
|
|||
campaigns on any OpenERP document.
|
||||
|
||||
Technical note: only the templating system of the original Power Email by
|
||||
Openlabs was kept
|
||||
|
||||
Openlabs was kept.
|
||||
""",
|
||||
"data": [
|
||||
'wizard/email_template_preview_view.xml',
|
||||
|
|
|
|||
|
|
@ -31,7 +31,8 @@ Organization and management of Events.
|
|||
|
||||
This module allows you
|
||||
* to manage your events and their registrations
|
||||
* to use emails to automatically confirm and send acknowledgements for any registration to an event
|
||||
* to use emails to automatically confirm and send acknowledgements for any
|
||||
registration to an event
|
||||
|
||||
Note that:
|
||||
- You can define new types of events in
|
||||
|
|
|
|||
|
|
@ -25,33 +25,32 @@
|
|||
'version': '0.1',
|
||||
'category': 'Tools',
|
||||
'description': """
|
||||
Configure your moodle server
|
||||
Configure your moodle server.
|
||||
=============================
|
||||
|
||||
With this module you are able to connect your OpenERP with a moodle plateform.
|
||||
This module will create courses and students automatically in your moodle plateform to avoid wasting time.
|
||||
Now you have a simple way to create training or courses with OpenERP and moodle
|
||||
This module will create courses and students automatically in your moodle plateform
|
||||
to avoid wasting time.
|
||||
Now you have a simple way to create training or courses with OpenERP and moodle.
|
||||
|
||||
|
||||
STEPS TO CONFIGURE
|
||||
STEPS TO CONFIGURE:
|
||||
------------------
|
||||
|
||||
1. activate web service in moodle
|
||||
1. Activate web service in moodle.
|
||||
----------------------------------
|
||||
>site administration >plugins>web sevices >manage protocols
|
||||
activate the xmlrpc web service
|
||||
>site administration >plugins >web sevices >manage protocols activate the xmlrpc web service
|
||||
|
||||
|
||||
>site administration >plugins>web sevices >manage tokens
|
||||
create a token
|
||||
>site administration >plugins >web sevices >manage tokens create a token
|
||||
|
||||
|
||||
>site administration >plugins>web sevices >overview
|
||||
activate webservice
|
||||
>site administration >plugins >web sevices >overview activate webservice
|
||||
|
||||
|
||||
2. Create confirmation email with login and password
|
||||
----------------------------------------------------
|
||||
we strongly suggest you to add those following lines at the bottom of your event confirmation email to communicate the login/password of moodle to your subscribers.
|
||||
2. Create confirmation email with login and password.
|
||||
-----------------------------------------------------
|
||||
We strongly suggest you to add those following lines at the bottom of your event
|
||||
confirmation email to communicate the login/password of moodle to your subscribers.
|
||||
|
||||
|
||||
........your configuration text.......
|
||||
|
|
|
|||
|
|
@ -28,9 +28,14 @@
|
|||
Creating registration with sale orders.
|
||||
=======================================
|
||||
|
||||
This module allows you to automatize and connect your registration creation with your main sale flow and, therefore, to enable the invoicing feature of registrations.
|
||||
This module allows you to automatize and connect your registration creation with
|
||||
your main sale flow and therefore, to enable the invoicing feature of registrations.
|
||||
|
||||
It defines a new kind of service products that offers you the possibility to choose an event category associated with it. When you encode a sale order for that product, you will be able to choose an existing event of that category and when you confirm your sale order it will automatically create a registration for this event.
|
||||
It defines a new kind of service products that offers you the possibility to
|
||||
choose an event category associated with it. When you encode a sale order for
|
||||
that product, you will be able to choose an existing event of that category and
|
||||
when you confirm your sale order it will automatically create a registration for
|
||||
this event.
|
||||
""",
|
||||
'author': 'OpenERP SA',
|
||||
'depends': ['event','sale','sale_crm'],
|
||||
|
|
|
|||
|
|
@ -27,35 +27,33 @@
|
|||
"author" : "OpenERP SA",
|
||||
"category": 'Tools',
|
||||
"description": """
|
||||
Retrieve incoming email on POP / IMAP servers
|
||||
=============================================
|
||||
Retrieve incoming email on POP/IMAP servers.
|
||||
============================================
|
||||
|
||||
Enter the parameters of your POP/IMAP account(s), and any incoming
|
||||
emails on these accounts will be automatically downloaded into your OpenERP
|
||||
system. All POP3/IMAP-compatible servers are supported, included those
|
||||
that require an encrypted SSL/TLS connection.
|
||||
Enter the parameters of your POP/IMAP account(s), and any incoming emails on
|
||||
these accounts will be automatically downloaded into your OpenERP system. All
|
||||
POP3/IMAP-compatible servers are supported, included those that require an
|
||||
encrypted SSL/TLS connection.
|
||||
|
||||
This can be used to easily create email-based workflows for many
|
||||
email-enabled OpenERP documents, such as:
|
||||
This can be used to easily create email-based workflows for many email-enabled
|
||||
OpenERP documents, such as:
|
||||
|
||||
* CRM Leads/Opportunities
|
||||
* CRM Claims
|
||||
* Project Issues
|
||||
* Project Tasks
|
||||
* Human Resource Recruitments (Applicants)
|
||||
* CRM Leads/Opportunities
|
||||
* CRM Claims
|
||||
* Project Issues
|
||||
* Project Tasks
|
||||
* Human Resource Recruitments (Applicants)
|
||||
|
||||
Just install the relevant application, and you can assign any of
|
||||
these document types (Leads, Project Issues.) to your incoming
|
||||
email accounts. New emails will automatically spawn new documents
|
||||
of the chosen type, so it's a snap to create a mailbox-to-OpenERP
|
||||
integration. Even better: these documents directly act as mini
|
||||
conversations synchronized by email. You can reply from within
|
||||
OpenERP, and the answers will automatically be collected when
|
||||
they come back, and attached to the same *conversation* document.
|
||||
Just install the relevant application, and you can assign any of these document
|
||||
types (Leads, Project Issues) to your incoming email accounts. New emails will
|
||||
automatically spawn new documents of the chosen type, so it's a snap to create a
|
||||
mailbox-to-OpenERP integration. Even better: these documents directly act as mini
|
||||
conversations synchronized by email. You can reply from within OpenERP, and the
|
||||
answers will automatically be collected when they come back, and attached to the
|
||||
same *conversation* document.
|
||||
|
||||
For more specific needs, you may also assign custom-defined actions
|
||||
(technically: Server Actions) to be triggered for each incoming
|
||||
mail.
|
||||
(technically: Server Actions) to be triggered for each incoming mail.
|
||||
""",
|
||||
'website': 'http://www.openerp.com',
|
||||
'init_xml': [],
|
||||
|
|
|
|||
|
|
@ -24,7 +24,7 @@
|
|||
'name': 'Google Users',
|
||||
'version': '1.0',
|
||||
'category': 'Tools',
|
||||
'description': """The module adds google user in res user""",
|
||||
'description': """The module adds google user in res user.""",
|
||||
'author': 'OpenERP SA',
|
||||
'website': 'http://www.openerp.com',
|
||||
'depends': ['base'],
|
||||
|
|
|
|||
|
|
@ -28,9 +28,10 @@
|
|||
Add all information on the employee form to manage contracts.
|
||||
=============================================================
|
||||
|
||||
* Marital status,
|
||||
* Security number,
|
||||
* Place of birth, birth date, ...
|
||||
* Contract
|
||||
* Place of Birth,
|
||||
* Medical Examination Date
|
||||
* Company Vehicle
|
||||
|
||||
You can assign several contracts per employee.
|
||||
""",
|
||||
|
|
|
|||
|
|
@ -31,12 +31,11 @@
|
|||
Ability to create employees evaluation.
|
||||
=======================================
|
||||
|
||||
An evaluation can be created by employee for subordinates,
|
||||
juniors as well as his manager. The evaluation is done under a plan
|
||||
in which various surveys can be created and it can be defined which
|
||||
level of employee hierarchy fills what and final review and evaluation
|
||||
is done by the manager. Every evaluation filled by the employees can be viewed
|
||||
in the form of pdf file.
|
||||
An evaluation can be created by employee for subordinates, juniors as well as
|
||||
his manager. The evaluation is done under a plan in which various surveys can be
|
||||
created and it can be defined which level of employee hierarchy fills what and
|
||||
final review and evaluation is done by the manager. Every evaluation filled by
|
||||
the employees can be viewed in the form of pdf file.
|
||||
""",
|
||||
"demo": ["hr_evaluation_demo.xml"],
|
||||
"data": [
|
||||
|
|
|
|||
|
|
@ -28,16 +28,20 @@
|
|||
"sequence": 28,
|
||||
"website": "http://www.openerp.com",
|
||||
"description": """
|
||||
This module allows you to manage leaves and leaves' requests.
|
||||
This module allows you to manage leaves and leave's requests.
|
||||
=============================================================
|
||||
|
||||
Implements a dashboard for human resource management that includes.
|
||||
Implements a dashboard for human resource management that includes:
|
||||
-------------------------------------------------------------------
|
||||
* Leaves
|
||||
|
||||
Note that:
|
||||
- A synchronisation with an internal agenda (use of the CRM module) is possible: in order to automatically create a case when an holiday request is accepted, you have to link the holidays status to a case section. You can set up this info and your colour preferences in
|
||||
- A synchronisation with an internal agenda (use of the CRM module) is
|
||||
possible: in order to automatically create a case when an holiday request
|
||||
is accepted, you have to link the holidays status to a case section. You
|
||||
can setup this info and your colour preferences in
|
||||
Human Resources/Configuration/Leave Type
|
||||
- An employee can make an ask for more off-days by making a new Allocation It will increase his total of that leave type available (if the request is accepted).
|
||||
- An employee can make an ask for more off-days by making a new Allocation. It will increase his total of that leave type available (if the request is accepted).
|
||||
- There are two ways to print the employee's holidays:
|
||||
* The first will allow to choose employees by department and is used by clicking the menu item located in
|
||||
Reporting/Human Resources/Leaves/Leaves by Department
|
||||
|
|
|
|||
|
|
@ -34,8 +34,8 @@ the analytic account.
|
|||
|
||||
Lots of reporting on time and employee tracking are provided.
|
||||
|
||||
It is completely integrated with the cost accounting module. It allows you
|
||||
to set up a management by affair.
|
||||
It is completely integrated with the cost accounting module. It allows you to set
|
||||
up a management by affair.
|
||||
""",
|
||||
'author': 'OpenERP SA',
|
||||
'website': 'http://www.openerp.com',
|
||||
|
|
|
|||
|
|
@ -24,9 +24,11 @@
|
|||
'name': 'Invoice on Timesheets',
|
||||
'version': '1.0',
|
||||
'category': 'Sales Management',
|
||||
'description': """Generate your Invoices from Expenses, Timesheet Entries, ...
|
||||
'description': """
|
||||
Generate your Invoices from Expenses, Timesheet Entries.
|
||||
========================================================
|
||||
|
||||
Module to generate invoices based on costs (human resources, expenses, ...).
|
||||
============================================================================
|
||||
|
||||
You can define price lists in analytic account, make some theoretical revenue
|
||||
reports.""",
|
||||
|
|
|
|||
|
|
@ -29,22 +29,22 @@
|
|||
This module helps you to easily encode and validate timesheet and attendances within the same view.
|
||||
===================================================================================================
|
||||
|
||||
* It will mentain attendances and track (sign in/sign out) events.
|
||||
* Track the timesheet lines.
|
||||
* It will mentain attendances and track (sign in/sign out) events.
|
||||
* Track the timesheet lines.
|
||||
|
||||
Other tabs contains statistics views to help you analyse your
|
||||
time or the time of your team:
|
||||
* Time spent by day (with attendances)
|
||||
* Time spent by project
|
||||
* Time spent by day (with attendances)
|
||||
* Time spent by project
|
||||
|
||||
This module also implements a complete timesheet validation process:
|
||||
* Draft sheet
|
||||
* Confirmation at the end of the period by the employee
|
||||
* Validation by the project manager
|
||||
* Draft sheet
|
||||
* Confirmation at the end of the period by the employee
|
||||
* Validation by the project manager
|
||||
|
||||
The validation can be configured in the company:
|
||||
* Period size (day, week, month, year)
|
||||
* Maximal difference between timesheet and attendances
|
||||
* Period size (day, week, month, year)
|
||||
* Maximal difference between timesheet and attendances
|
||||
""",
|
||||
'author': 'OpenERP SA',
|
||||
'website': 'http://www.openerp.com',
|
||||
|
|
|
|||
|
|
@ -25,8 +25,8 @@
|
|||
'version': '0.1',
|
||||
'category': 'Tools',
|
||||
'description': """
|
||||
This module allows your user to easily and efficiently participate in enterprise innovation.
|
||||
============================================================================================
|
||||
This module allows user to easily and efficiently participate in enterprise innovation.
|
||||
=======================================================================================
|
||||
|
||||
It allows everybody to express ideas about different subjects.
|
||||
Then, other users can comment on these ideas and vote for particular ideas.
|
||||
|
|
|
|||
|
|
@ -24,8 +24,8 @@
|
|||
'version': '0.9',
|
||||
'category': 'Hidden/Dependency',
|
||||
'description': """
|
||||
This module provide a class import_framework to help importing
|
||||
complex data from other software
|
||||
This module provide a class import_framework to help importing complex data from
|
||||
other software.
|
||||
""",
|
||||
'author': 'OpenERP SA',
|
||||
'website': 'http://www.openerp.com',
|
||||
|
|
|
|||
|
|
@ -23,8 +23,9 @@
|
|||
'name': 'SugarCRM Import',
|
||||
'version': '1.0',
|
||||
'category': 'Customer Relationship Management',
|
||||
'description': """This Module Import SugarCRM "Leads", "Opportunities", "Users", "Accounts",
|
||||
"Contacts", "Employees", Meetings, Phonecalls, Emails, and Project, Project Tasks Data into OpenERP Module.""",
|
||||
'description': """
|
||||
This Module Import SugarCRM Leads, Opportunities, Users, Accounts, Contacts, Employees,
|
||||
Meetings, Phonecalls, Emails, Project and Project Tasks Data into OpenERP Module.""",
|
||||
'author': 'OpenERP SA',
|
||||
'website': 'http://www.openerp.com',
|
||||
'depends': ['import_base','crm', 'document'],
|
||||
|
|
|
|||
|
|
@ -26,7 +26,10 @@
|
|||
"website" : "http://www.conexus.at",
|
||||
"category" : "Localization/Account Charts",
|
||||
"depends" : ["account_chart", 'base_vat'],
|
||||
"description": "This module provides the standard Accounting Chart for Austria which is based on the Template from BMF.gv.at. Please keep in mind that you should review and adapt it with your Accountant, before using it in a live Environment.",
|
||||
"description": """
|
||||
This module provides the standard Accounting Chart for Austria which is based on
|
||||
the Template from BMF.gv.at. Please keep in mind that you should review and adapt
|
||||
it with your Accountant, before using it in a live Environment.""",
|
||||
"demo_xml" : [],
|
||||
"update_xml" : ['account_tax_code.xml',"account_chart.xml",'account_tax.xml',"l10n_chart_at_wizard.xml"],
|
||||
"auto_install": False,
|
||||
|
|
|
|||
|
|
@ -27,17 +27,23 @@ This is the base module to manage the accounting chart for Belgium in OpenERP.
|
|||
|
||||
After installing this module, the Configuration wizard for accounting is launched.
|
||||
* We have the account templates which can be helpful to generate Charts of Accounts.
|
||||
* On that particular wizard, you will be asked to pass the name of the company, the chart template to follow, the no. of digits to generate, the code for your account and bank account, currency to create journals.
|
||||
* On that particular wizard, you will be asked to pass the name of the company,
|
||||
the chart template to follow, the no. of digits to generate, the code for your
|
||||
account and bank account, currency to create journals.
|
||||
|
||||
Thus, the pure copy of Chart Template is generated.
|
||||
|
||||
Wizards provided by this module:
|
||||
* Partner VAT Intra: Enlist the partners with their related VAT and invoiced amounts.Prepares an XML file format.
|
||||
Path to access : Accounting/Reporting//Legal Statements/Belgium Statements/Partner VAT Listing
|
||||
* Periodical VAT Declaration: Prepares an XML file for Vat Declaration of the Main company of the User currently Logged in.
|
||||
Path to access : Accounting/Reporting/Legal Statements/Belgium Statements/Periodical VAT Declaration
|
||||
* Annual Listing Of VAT-Subjected Customers: Prepares an XML file for Vat Declaration of the Main company of the User currently Logged in.Based on Fiscal year
|
||||
Path to access : Accounting/Reporting/Legal Statements/Belgium Statements/Annual Listing Of VAT-Subjected Customers
|
||||
* Partner VAT Intra: Enlist the partners with their related VAT and invoiced
|
||||
amounts. Prepares an XML file format.
|
||||
Path to access : Invoicing/Reporting/Legal Reports/Belgium Statements/Partner VAT Intra
|
||||
* Periodical VAT Declaration: Prepares an XML file for Vat Declaration of
|
||||
the Main company of the User currently Logged in.
|
||||
Path to access : Invoicing/Reporting/Legal Reports/Belgium Statements/Periodical VAT Declaration
|
||||
* Annual Listing Of VAT-Subjected Customers: Prepares an XML file for Vat
|
||||
Declaration of the Main company of the User currently Logged in Based on
|
||||
Fiscal year.
|
||||
Path to access : Invoicing/Reporting/Legal Reports/Belgium Statements/Annual Listing Of VAT-Subjected Customers
|
||||
|
||||
""",
|
||||
'author': 'Noviat & OpenERP SA',
|
||||
|
|
|
|||
|
|
@ -25,14 +25,14 @@
|
|||
'depends': ['hr_payroll'],
|
||||
'version': '1.0',
|
||||
'description': """
|
||||
Belgian Payroll Rules
|
||||
=====================
|
||||
Belgian Payroll Rules.
|
||||
======================
|
||||
|
||||
* Employee Details
|
||||
* Employee Contracts
|
||||
* Passport based Contract
|
||||
* Allowances / Deductions
|
||||
* Allow to configure Basic / Gross / Net Salary
|
||||
* Allowances/Deductions
|
||||
* Allow to configure Basic/Gross/Net Salary
|
||||
* Employee Payslip
|
||||
* Monthly Payroll Register
|
||||
* Integrated with Holiday Management
|
||||
|
|
|
|||
|
|
@ -25,7 +25,7 @@
|
|||
'depends': ['l10n_be_hr_payroll', 'hr_payroll_account', 'l10n_be'],
|
||||
'version': '1.0',
|
||||
'description': """
|
||||
Accounting Data for Belgian Payroll Rules
|
||||
Accounting Data for Belgian Payroll Rules.
|
||||
""",
|
||||
|
||||
'auto_install': True,
|
||||
|
|
|
|||
|
|
@ -32,7 +32,9 @@ Belgian localisation for in- and outgoing invoices (prereq to account_coda):
|
|||
- Rename 'reference' field labels to 'Communication'
|
||||
- Add support for Belgian Structured Communication
|
||||
|
||||
A Structured Communication can be generated automatically on outgoing invoices according to the following algorithms:
|
||||
A Structured Communication can be generated automatically on outgoing invoices
|
||||
according to the following algorithms:
|
||||
|
||||
1) Random : +++RRR/RRRR/RRRDD+++
|
||||
R..R = Random Digits, DD = Check Digits
|
||||
2) Date : +++DOY/YEAR/SSSDD+++
|
||||
|
|
@ -40,8 +42,9 @@ A Structured Communication can be generated automatically on outgoing invoices a
|
|||
3) Customer Reference +++RRR/RRRR/SSSDDD+++
|
||||
R..R = Customer Reference without non-numeric characters, SSS = Sequence Number, DD = Check Digits)
|
||||
|
||||
The preferred type of Structured Communication and associated Algorithm can be specified on the Partner records.
|
||||
A 'random' Structured Communication will generated if no algorithm is specified on the Partner record.
|
||||
The preferred type of Structured Communication and associated Algorithm can be
|
||||
specified on the Partner records. A 'random' Structured Communication will
|
||||
generated if no algorithm is specified on the Partner record.
|
||||
|
||||
""",
|
||||
'depends': ['account'],
|
||||
|
|
|
|||
|
|
@ -22,8 +22,8 @@
|
|||
'name': 'Brazilian - Accounting',
|
||||
'category': 'Localization/Account Charts',
|
||||
'description': """
|
||||
Base module for the Brazilian localization
|
||||
==========================================
|
||||
Base module for the Brazilian localization.
|
||||
===========================================
|
||||
|
||||
This module consists in:
|
||||
|
||||
|
|
@ -41,9 +41,23 @@ This module consists in:
|
|||
|
||||
- Tax Situation Code (CST) required for the electronic fiscal invoicing (NFe)
|
||||
|
||||
The field tax_discount has also been added in the account.tax.template and account.tax objects to allow the proper computation of some Brazilian VATs such as ICMS. The chart of account creation wizard has been extended to propagate those new data properly.
|
||||
The field tax_discount has also been added in the account.tax.template and account.tax
|
||||
objects to allow the proper computation of some Brazilian VATs such as ICMS. The
|
||||
chart of account creation wizard has been extended to propagate those new data properly.
|
||||
|
||||
It's important to note however that this module lack many implementations to use OpenERP properly in Brazil. Those implementations (such as the electronic fiscal Invoicing which is already operational) are brought by more than 15 additional modules of the Brazilian Launchpad localization project https://launchpad.net/openerp.pt-br-localiz and their dependencies in the extra addons branch. Those modules aim at not breaking with the remarkable OpenERP modularity, this is why they are numerous but small. One of the reasons for maintaining those modules apart is that Brazilian Localization leaders need commit rights agility to complete the localization as companies fund the remaining legal requirements (such as soon fiscal ledgers, accounting SPED, fiscal SPED and PAF ECF that are still missing as September 2011). Those modules are also strictly licensed under AGPL V3 and today don't come with any additional paid permission for online use of 'private modules'.""",
|
||||
It's important to note however that this module lack many implementations to use
|
||||
OpenERP properly in Brazil. Those implementations (such as the electronic fiscal
|
||||
Invoicing which is already operational) are brought by more than 15 additional
|
||||
modules of the Brazilian Launchpad localization project
|
||||
https://launchpad.net/openerp.pt-br-localiz and their dependencies in the extra
|
||||
addons branch. Those modules aim at not breaking with the remarkable OpenERP
|
||||
modularity, this is why they are numerous but small. One of the reasons for
|
||||
maintaining those modules apart is that Brazilian Localization leaders need commit
|
||||
rights agility to complete the localization as companies fund the remaining legal
|
||||
requirements (such as soon fiscal ledgers, accounting SPED, fiscal SPED and PAF
|
||||
ECF that are still missing as September 2011). Those modules are also strictly
|
||||
licensed under AGPL V3 and today don't come with any additional paid permission
|
||||
for online use of 'private modules'.""",
|
||||
'license': 'AGPL-3',
|
||||
'author': 'Akretion, OpenERP Brasil',
|
||||
'website': 'http://openerpbrasil.org',
|
||||
|
|
|
|||
|
|
@ -36,10 +36,11 @@ You can also add ZIP and bank completion with:
|
|||
|
||||
------------------------------------------------------------------------
|
||||
|
||||
Module incluant la localisation Suisse de TinyERP revu et corrigé par Camptocamp. Cette nouvelle version
|
||||
comprend la gestion et l'émissionde BVR, le paiement électronique via DTA (pour les banques, le système postal est en développement)
|
||||
et l'import du relevé de compte depuis la banque de manière automatisée.
|
||||
De plus, nous avons intégré la définition de toutes les banques Suisses(adresse, swift et clearing).
|
||||
Module incluant la localisation Suisse de TinyERP revu et corrigé par Camptocamp.
|
||||
Cette nouvelle version comprend la gestion et l'émissionde BVR, le paiement
|
||||
électronique via DTA (pour les banques, le système postal est en développement)
|
||||
et l'import du relevé de compte depuis la banque de manière automatisée. De plus,
|
||||
nous avons intégré la définition de toutes les banques Suisses(adresse, swift et clearing).
|
||||
|
||||
Par ailleurs, conjointement à ce module, nous proposons la complétion NPA:
|
||||
|
||||
|
|
@ -52,12 +53,11 @@ Vous pouvez ajouter la completion des banques et des NPA avec with:
|
|||
|
||||
--------------------------------------------------------------------------
|
||||
TODO :
|
||||
- Implement bvr import partial reconciliation
|
||||
- Replace wizard by osv_memory when possible
|
||||
- Add mising HELP
|
||||
- Finish code comment
|
||||
- Improve demo data
|
||||
|
||||
- Implement bvr import partial reconciliation
|
||||
- Replace wizard by osv_memory when possible
|
||||
- Add mising HELP
|
||||
- Finish code comment
|
||||
- Improve demo data
|
||||
|
||||
""",
|
||||
"version": "6.1",
|
||||
|
|
|
|||
|
|
@ -26,9 +26,9 @@
|
|||
"website":"http://openerp-china.org",
|
||||
"url":"http://code.google.com/p/openerp-china/source/browse/#svn/trunk/l10n_cn",
|
||||
"description": """
|
||||
添加中文省份数据
|
||||
科目类型\会计科目表模板\增值税\辅助核算类别\管理会计凭证簿\财务会计凭证簿
|
||||
============================================================
|
||||
添加中文省份数据
|
||||
科目类型\会计科目表模板\增值税\辅助核算类别\管理会计凭证簿\财务会计凭证簿
|
||||
============================================================
|
||||
""",
|
||||
"depends" : ["base","account"],
|
||||
'init_xml': [
|
||||
|
|
|
|||
|
|
@ -44,14 +44,14 @@ Chart of accounts for Costa Rica.
|
|||
=================================
|
||||
|
||||
Includes:
|
||||
* account.type
|
||||
* account.account.template
|
||||
* account.tax.template
|
||||
* account.tax.code.template
|
||||
* account.chart.template
|
||||
* account.type
|
||||
* account.account.template
|
||||
* account.tax.template
|
||||
* account.tax.code.template
|
||||
* account.chart.template
|
||||
|
||||
Everything is in English with Spanish translation. Further translations are welcome, please go to
|
||||
http://translations.launchpad.net/openerp-costa-rica
|
||||
Everything is in English with Spanish translation. Further translations are welcome,
|
||||
please go to http://translations.launchpad.net/openerp-costa-rica.
|
||||
""",
|
||||
'depends': ['account', 'account_chart', 'base'],
|
||||
'init_xml': [],
|
||||
|
|
|
|||
|
|
@ -31,14 +31,14 @@
|
|||
Spanish Charts of Accounts (PGCE 2008).
|
||||
=======================================
|
||||
|
||||
* Defines the following chart of account templates:
|
||||
* Spanish General Chart of Accounts 2008.
|
||||
* Spanish General Chart of Accounts 2008 for small and medium companies.
|
||||
* Defines templates for sale and purchase VAT.
|
||||
* Defines tax code templates.
|
||||
* Defines the following chart of account templates:
|
||||
* Spanish General Chart of Accounts 2008
|
||||
* Spanish General Chart of Accounts 2008 for small and medium companies
|
||||
* Defines templates for sale and purchase VAT
|
||||
* Defines tax code templates
|
||||
|
||||
Note: You should install the l10n_ES_account_balance_report module
|
||||
for yearly account reporting (balance, profit & losses).
|
||||
Note: You should install the l10n_ES_account_balance_report module for yearly
|
||||
account reporting (balance, profit & losses).
|
||||
""",
|
||||
"license" : "GPL-3",
|
||||
"depends" : ["account", "base_vat", "base_iban"],
|
||||
|
|
|
|||
|
|
@ -35,11 +35,21 @@
|
|||
This is the module to manage the accounting chart for France in OpenERP.
|
||||
========================================================================
|
||||
|
||||
This module applies to companies based in France mainland. It doesn't apply to companies based in the DOM-TOMs (Guadeloupe, Martinique, Guyane, Réunion, Mayotte)
|
||||
This module applies to companies based in France mainland. It doesn't apply to
|
||||
companies based in the DOM-TOMs (Guadeloupe, Martinique, Guyane, Réunion, Mayotte).
|
||||
|
||||
This localisation module creates the VAT taxes of type "tax included" for purchases (it is notably required when you use the module "hr_expense"). Beware that these "tax included" VAT taxes are not managed by the fiscal positions provided by this module (because it is complex to manage both "tax excluded" and "tax included" scenarios in fiscal positions).
|
||||
This localisation module creates the VAT taxes of type "tax included" for purchases
|
||||
(it is notably required when you use the module "hr_expense"). Beware that these
|
||||
"tax included" VAT taxes are not managed by the fiscal positions provided by this
|
||||
module (because it is complex to manage both "tax excluded" and "tax included"
|
||||
scenarios in fiscal positions).
|
||||
|
||||
This localisation module doesn't properly handle the scenario when a France-mainland company sells services to a company based in the DOMs. We could manage it in the fiscal positions, but it would require to differentiate between "product" VAT taxes and "service" VAT taxes. We consider that it is too "heavy" to have this by default in l10n_fr ; companies that sell services to DOM-based companies should update the configuration of their taxes and fiscal positions manually.
|
||||
This localisation module doesn't properly handle the scenario when a France-mainland
|
||||
company sells services to a company based in the DOMs. We could manage it in the
|
||||
fiscal positions, but it would require to differentiate between "product" VAT taxes
|
||||
and "service" VAT taxes. We consider that it is too "heavy" to have this by default
|
||||
in l10n_fr; companies that sell services to DOM-based companies should update the
|
||||
configuration of their taxes and fiscal positions manually.
|
||||
|
||||
Credits: Sistheo, Zeekom, CrysaLEAD, Akretion and Camptocamp.
|
||||
""",
|
||||
|
|
|
|||
|
|
@ -25,19 +25,22 @@
|
|||
'depends': ['hr_payroll', 'l10n_fr'],
|
||||
'version': '1.0',
|
||||
'description': """
|
||||
French Payroll Rules
|
||||
=======================
|
||||
French Payroll Rules.
|
||||
=====================
|
||||
|
||||
-Configuration of hr_payroll for french localization
|
||||
-All main contributions rules for french payslip, for 'cadre' and 'non-cadre'
|
||||
-New payslip report
|
||||
- Configuration of hr_payroll for french localization
|
||||
- All main contributions rules for french payslip, for 'cadre' and 'non-cadre'
|
||||
- New payslip report
|
||||
|
||||
TODO :
|
||||
-Integration with holidays module for deduction and allowance
|
||||
-Integration with hr_payroll_account for the automatic account_move_line creation from the payslip
|
||||
-Continue to integrate the contribution. Only the main contribution are currently implemented
|
||||
-Remake the report under webkit
|
||||
-The payslip.line with appears_in_payslip = False should appears in the payslip interface, but not in the payslip report
|
||||
TODO :
|
||||
- Integration with holidays module for deduction and allowance
|
||||
- Integration with hr_payroll_account for the automatic account_move_line
|
||||
creation from the payslip
|
||||
- Continue to integrate the contribution. Only the main contribution are
|
||||
currently implemented
|
||||
- Remake the report under webkit
|
||||
- The payslip.line with appears_in_payslip = False should appears in the
|
||||
payslip interface, but not in the payslip report
|
||||
""",
|
||||
|
||||
'active': False,
|
||||
|
|
|
|||
|
|
@ -25,17 +25,26 @@
|
|||
"category": 'Hidden/Dependency',
|
||||
'description': '''
|
||||
This module lets users enter the banking details of Partners in the RIB format (French standard for bank accounts details).
|
||||
RIB Bank Accounts can be entered in the "Accounting" tab of the Partner form by specifying the account type "RIB". The four standard RIB fields will then become mandatory:
|
||||
- Bank Code
|
||||
- Office Code
|
||||
- Account number
|
||||
- RIB key
|
||||
As a safety measure, OpenERP will check the RIB key whenever a RIB is saved, and will refuse to record the data if the key is incorrect. Please bear in mind that this can only happen when the user presses the "save" button, for example on the Partner Form.
|
||||
Since each bank account may relate to a Bank, users may enter the RIB Bank Code in the Bank form - it will the pre-fill the Bank Code on the RIB when they select the Bank.
|
||||
To make this easier, this module will also let users find Banks using their RIB code.
|
||||
===========================================================================================================================
|
||||
|
||||
The module base_iban can be a useful addition to this module, because French banks are now progressively adopting the international IBAN format instead of the RIB format.
|
||||
The RIB and IBAN codes for a single account can be entered by recording two Bank Accounts in OpenERP: the first with the type "RIB", the second with the type "IBAN".
|
||||
RIB Bank Accounts can be entered in the "Accounting" tab of the Partner form by specifying
|
||||
the account type "RIB". The four standard RIB fields will then become mandatory:
|
||||
- Bank Code
|
||||
- Office Code
|
||||
- Account number
|
||||
- RIB key
|
||||
As a safety measure, OpenERP will check the RIB key whenever a RIB is saved, and
|
||||
will refuse to record the data if the key is incorrect. Please bear in mind that
|
||||
this can only happen when the user presses the "save" button, for example on the
|
||||
Partner Form. Since each bank account may relate to a Bank, users may enter the
|
||||
RIB Bank Code in the Bank form - it will the pre-fill the Bank Code on the RIB
|
||||
when they select the Bank. To make this easier, this module will also let users
|
||||
find Banks using their RIB code.
|
||||
|
||||
The module base_iban can be a useful addition to this module, because French banks
|
||||
are now progressively adopting the international IBAN format instead of the RIB format.
|
||||
The RIB and IBAN codes for a single account can be entered by recording two Bank
|
||||
Accounts in OpenERP: the first with the type "RIB", the second with the type "IBAN".
|
||||
''',
|
||||
'author' : u'Numérigraphe SARL',
|
||||
'depends': ['account', 'base_iban'],
|
||||
|
|
|
|||
|
|
@ -40,7 +40,9 @@
|
|||
This is the base module to manage the accounting chart for Guatemala.
|
||||
=====================================================================
|
||||
|
||||
Agrega una nomenclatura contable para Guatemala. También icluye impuestos y la moneda del Quetzal. -- Adds accounting chart for Guatemala. It also includes taxes and the Quetzal currency""",
|
||||
Agrega una nomenclatura contable para Guatemala. También icluye impuestos y
|
||||
la moneda del Quetzal. -- Adds accounting chart for Guatemala. It also includes
|
||||
taxes and the Quetzal currency.""",
|
||||
'author': 'José Rodrigo Fernández Menegazzo',
|
||||
'website': 'http://solucionesprisma.com/',
|
||||
'depends': ['base', 'account', 'account_chart'],
|
||||
|
|
|
|||
|
|
@ -36,7 +36,10 @@
|
|||
'name': 'Honduras - Accounting',
|
||||
'version': '0.1',
|
||||
'category': 'Localization/Account Charts',
|
||||
'description': """Agrega una nomenclatura contable para Honduras. También incluye impuestos y la moneda Lempira. -- Adds accounting chart for Honduras. It also includes taxes and the Lempira currency""",
|
||||
'description': """
|
||||
Agrega una nomenclatura contable para Honduras. También incluye impuestos y la
|
||||
moneda Lempira. -- Adds accounting chart for Honduras. It also includes taxes
|
||||
and the Lempira currency.""",
|
||||
'author': 'Salvatore Josue Trimarchi Pinto',
|
||||
'website': 'http://trimarchi.co.cc',
|
||||
'depends': ['base', 'account', 'account_chart'],
|
||||
|
|
|
|||
|
|
@ -23,8 +23,8 @@
|
|||
"name": "India - Accounting",
|
||||
"version": "1.0",
|
||||
"description": """
|
||||
Indian Accounting : Chart of Account.
|
||||
=====================================
|
||||
Indian Accounting: Chart of Account.
|
||||
====================================
|
||||
|
||||
Indian accounting chart and localization.
|
||||
""",
|
||||
|
|
|
|||
|
|
@ -28,7 +28,7 @@
|
|||
This is the base module to manage the accounting chart for Luxembourg.
|
||||
======================================================================
|
||||
|
||||
* the KLUWER Chart of Accounts,
|
||||
* the KLUWER Chart of Accounts
|
||||
* the Tax Code Chart for Luxembourg
|
||||
* the main taxes used in Luxembourg""",
|
||||
'author': 'OpenERP SA',
|
||||
|
|
|
|||
|
|
@ -28,7 +28,11 @@
|
|||
This is the base module to manage the accounting chart for Maroc.
|
||||
=================================================================
|
||||
|
||||
Ce Module charge le modèle du plan de comptes standard Marocain et permet de générer les états comptables aux normes marocaines (Bilan, CPC (comptes de produits et charges), balance générale à 6 colonnes, Grand livre cumulatif...). L'intégration comptable a été validé avec l'aide du Cabinet d'expertise comptable Seddik au cours du troisième trimestre 2010""",
|
||||
Ce Module charge le modèle du plan de comptes standard Marocain et permet de
|
||||
générer les états comptables aux normes marocaines (Bilan, CPC (comptes de
|
||||
produits et charges), balance générale à 6 colonnes, Grand livre cumulatif...).
|
||||
L'intégration comptable a été validé avec l'aide du Cabinet d'expertise comptable
|
||||
Seddik au cours du troisième trimestre 2010.""",
|
||||
"website": "http://www.kazacube.com",
|
||||
"depends" : ["base", "account"],
|
||||
"init_xml" : [],
|
||||
|
|
|
|||
|
|
@ -25,10 +25,11 @@
|
|||
"author" : "OpenERP SA",
|
||||
"category": 'Hidden/Dependency',
|
||||
"description": """
|
||||
* Multi language support for Chart of Accounts, Taxes, Tax Codes , Journals, Accounting Templates,
|
||||
Analytic Chart of Accounts and Analytic Journals.
|
||||
* Multi language support for Chart of Accounts, Taxes, Tax Codes, Journals,
|
||||
Accounting Templates, Analytic Chart of Accounts and Analytic Journals.
|
||||
* Setup wizard changes
|
||||
- Copy translations for COA, Tax, Tax Code and Fiscal Position from templates to target objects.
|
||||
- Copy translations for COA, Tax, Tax Code and Fiscal Position from
|
||||
templates to target objects.
|
||||
""",
|
||||
'website': 'http://www.openerp.com',
|
||||
'init_xml': [],
|
||||
|
|
|
|||
|
|
@ -94,19 +94,25 @@ This is the module to manage the accounting chart for Netherlands in OpenERP.
|
|||
=============================================================================
|
||||
|
||||
Read changelog in file __openerp__.py for version information.
|
||||
Dit is een basismodule om een uitgebreid grootboek- en BTW schema voor Nederlandse bedrijven te installeren in OpenERP versie 5.
|
||||
Dit is een basismodule om een uitgebreid grootboek- en BTW schema voor
|
||||
Nederlandse bedrijven te installeren in OpenERP versie 5.
|
||||
|
||||
De BTW rekeningen zijn waar nodig gekoppeld om de juiste rapportage te genereren, denk b.v. aan intracommunautaire verwervingen
|
||||
waarbij u 19% BTW moet opvoeren, maar tegelijkertijd ook 19% als voorheffing weer mag aftrekken.
|
||||
De BTW rekeningen zijn waar nodig gekoppeld om de juiste rapportage te genereren,
|
||||
denk b.v. aan intracommunautaire verwervingen waarbij u 19% BTW moet opvoeren,
|
||||
maar tegelijkertijd ook 19% als voorheffing weer mag aftrekken.
|
||||
|
||||
Na installatie van deze module word de configuratie wizard voor "Accounting" aangeroepen.
|
||||
* U krijgt een lijst met grootboektemplates aangeboden waarin zich ook het Nederlandse grootboekschema bevind.
|
||||
* U krijgt een lijst met grootboektemplates aangeboden waarin zich ook het
|
||||
Nederlandse grootboekschema bevind.
|
||||
|
||||
* Als de configuratie wizard start, wordt u gevraagd om de naam van uw bedrijf in te voeren, welke grootboekschema te installeren, uit hoeveel cijfers een grootboekrekening mag bestaan, het rekeningnummer van uw bank en de currency om Journalen te creeren.
|
||||
* Als de configuratie wizard start, wordt u gevraagd om de naam van uw bedrijf
|
||||
in te voeren, welke grootboekschema te installeren, uit hoeveel cijfers een
|
||||
grootboekrekening mag bestaan, het rekeningnummer van uw bank en de currency
|
||||
om Journalen te creeren.
|
||||
|
||||
Let op!! -> De template van het Nederlandse rekeningschema is opgebouwd uit 4 cijfers. Dit is het minimale aantal welk u moet invullen, u mag het aantal verhogen. De extra cijfers worden dan achter het rekeningnummer aangevult met "nullen"
|
||||
|
||||
* Dit is dezelfe configuratie wizard welke aangeroepen kan worden via Financial Management/Configuration/Financial Accounting/Financial Accounts/Generate Chart of Accounts from a Chart Template.
|
||||
Let op!! -> De template van het Nederlandse rekeningschema is opgebouwd uit 4
|
||||
cijfers. Dit is het minimale aantal welk u moet invullen, u mag het aantal verhogen.
|
||||
De extra cijfers worden dan achter het rekeningnummer aangevult met "nullen".
|
||||
|
||||
""",
|
||||
"author" : "Veritos - Jan Verlaan",
|
||||
|
|
|
|||
|
|
@ -22,9 +22,10 @@
|
|||
"name": "Peru Localization Chart Account",
|
||||
"version": "1.0",
|
||||
"description": """
|
||||
Peruvian accounting chart and tax localization. Acording the PCGE 2010
|
||||
Peruvian accounting chart and tax localization. Acording the PCGE 2010.
|
||||
|
||||
Plan contable peruano e impuestos de acuerdo a disposiciones vigentes de la SUNAT 2011 (PCGE 2010)
|
||||
Plan contable peruano e impuestos de acuerdo a disposiciones vigentes de la
|
||||
SUNAT 2011 (PCGE 2010).
|
||||
|
||||
""",
|
||||
"author": ["Cubic ERP"],
|
||||
|
|
|
|||
|
|
@ -24,12 +24,15 @@
|
|||
"version" : "1.0",
|
||||
"author" : "Baamtu Senegal",
|
||||
"category" : "Localization/Account Charts",
|
||||
"description": """This module implements the accounting chart for OHADA area.
|
||||
It allows any company or association to manage its financial accounting.
|
||||
Countries that use OHADA are the following:
|
||||
"description": """
|
||||
This module implements the accounting chart for OHADA area.
|
||||
===========================================================
|
||||
|
||||
It allows any company or association to manage its financial accounting.
|
||||
Countries that use OHADA are the following:
|
||||
Benin, Burkina Faso, Cameroon, Central African Republic, Comoros, Congo,
|
||||
Ivory Coast, Gabon, Guinea, Guinea Bissau,
|
||||
Equatorial Guinea, Mali, Niger, Replica of Democratic Congo, Senegal, Chad, Togo.
|
||||
Ivory Coast, Gabon, Guinea, Guinea Bissau, Equatorial Guinea, Mali, Niger,
|
||||
Replica of Democratic Congo, Senegal, Chad, Togo.
|
||||
""",
|
||||
"website": "http://www.baamtu.com",
|
||||
"depends" : ["account", "base_vat"],
|
||||
|
|
|
|||
|
|
@ -23,10 +23,11 @@
|
|||
'category': 'Localization/Account Charts',
|
||||
'description': """
|
||||
Türkiye için Tek düzen hesap planı şablonu OpenERP Modülü.
|
||||
==============================================================================
|
||||
==========================================================
|
||||
|
||||
Bu modül kurulduktan sonra, Muhasebe yapılandırma sihirbazı çalışır
|
||||
* Sihirbaz sizden hesap planı şablonu, planın kurulacağı şirket,banka hesap bilgileriniz,ilgili para birimi gibi bilgiler isteyecek.
|
||||
* Sihirbaz sizden hesap planı şablonu, planın kurulacağı şirket, banka hesap
|
||||
bilgileriniz, ilgili para birimi gibi bilgiler isteyecek.
|
||||
""",
|
||||
'author': 'Ahmet Altınışık',
|
||||
'maintainer':'https://launchpad.net/~openerp-turkey',
|
||||
|
|
|
|||
|
|
@ -23,7 +23,9 @@
|
|||
'name': 'UK - Accounting',
|
||||
'version': '1.0',
|
||||
'category': 'Localization/Account Charts',
|
||||
'description': """This is the latest UK OpenERP localisation necesary to run OpenERP accounting for UK SME's with:
|
||||
'description': """
|
||||
This is the latest UK OpenERP localisation necesary to run OpenERP accounting
|
||||
for UK SME's with:
|
||||
- a CT600-ready chart of accounts
|
||||
- VAT100-ready tax structure
|
||||
- InfoLogic UK counties listing
|
||||
|
|
|
|||
|
|
@ -24,7 +24,7 @@
|
|||
"author": "OpenERP SA",
|
||||
"category": 'Localization/Account Charts',
|
||||
"description": """
|
||||
United States - Chart of accounts
|
||||
United States - Chart of accounts.
|
||||
""",
|
||||
'website': 'http://www.openerp.com',
|
||||
'init_xml': [],
|
||||
|
|
|
|||
|
|
@ -28,10 +28,10 @@
|
|||
"category" : "Localization/Account Charts",
|
||||
"website" : "https://launchpad.net/openerp-uruguay",
|
||||
"description": """
|
||||
General Chart of Accounts
|
||||
=========================
|
||||
General Chart of Accounts.
|
||||
==========================
|
||||
|
||||
Provide Templates for Chart of Accounts, Taxes for Uruguay
|
||||
Provide Templates for Chart of Accounts, Taxes for Uruguay.
|
||||
|
||||
""",
|
||||
"license" : "AGPL-3",
|
||||
|
|
|
|||
|
|
@ -22,22 +22,15 @@
|
|||
{
|
||||
"name": "Lunch Orders",
|
||||
"author": "OpenERP SA",
|
||||
"Description": """
|
||||
The lunch module is for keeping a record of the order placed and payment of the orders.
|
||||
=======================================================================================
|
||||
|
||||
The products are defined under categories and the payment records are maintained user-wise.
|
||||
Every user has a cashbox which keeps track of the amount paid for a particular order.
|
||||
|
||||
""",
|
||||
"version": "0.1",
|
||||
"depends": ["base_tools"],
|
||||
"category" : "Tools",
|
||||
'description': """
|
||||
The base module to manage lunch.
|
||||
The base module to manage lunch.
|
||||
================================
|
||||
|
||||
keep track for the Lunch Order, Cash Moves, CashBox, Product.
|
||||
Apply Different Category for the product.
|
||||
keep track for the Lunch Order, Cash Moves, CashBox, Product. Apply Different
|
||||
Category for the product.
|
||||
""",
|
||||
"init_xml": [],
|
||||
"update_xml": [
|
||||
|
|
|
|||
|
|
@ -28,19 +28,19 @@
|
|||
A bussiness oriented Social Networking with a fully-integrated email
|
||||
and message management.
|
||||
=====================================================================
|
||||
|
||||
The Social Networking module provides an unified social network
|
||||
abstraction layer allowing applications to display a complete
|
||||
communication history on documents.It gives the users the possibility
|
||||
communication history on documents. It gives the users the possibility
|
||||
to read and send messages and emails in an unified way.
|
||||
|
||||
It also provides a feeds page combined to a subscription mechanism, that
|
||||
allows to follow documents, and to be constantly updated about recent
|
||||
news.
|
||||
|
||||
The main features of the module are :
|
||||
|
||||
The main features of the module are:
|
||||
* a clean and renewed communication history for any OpenERP
|
||||
document that can act as a discussion topic,
|
||||
document that can act as a discussion topic,
|
||||
* a discussion mean on documents,
|
||||
* a subscription mechanism to be updated about new messages on
|
||||
interesting documents,
|
||||
|
|
|
|||
|
|
@ -35,15 +35,23 @@ This module provides leads automation through marketing campaigns (campaigns can
|
|||
=========================================================================================================================================
|
||||
|
||||
The campaigns are dynamic and multi-channels. The process is as follows:
|
||||
* Design marketing campaigns like workflows, including email templates to send, reports to print and send by email, custom actions.
|
||||
* Define input segments that will select the items that should enter the campaign (e.g leads from certain countries.)
|
||||
* Run you campaign in simulation mode to test it real-time or accelerated, and fine-tune it
|
||||
* You may also start the real campaign in manual mode, where each action requires manual validation
|
||||
* Finally launch your campaign live, and watch the statistics as the campaign does everything fully automatically.
|
||||
* Design marketing campaigns like workflows, including email templates to
|
||||
send, reports to print and send by email, custom actions
|
||||
* Define input segments that will select the items that should enter the
|
||||
campaign (e.g leads from certain countries.)
|
||||
* Run you campaign in simulation mode to test it real-time or accelerated,
|
||||
and fine-tune it
|
||||
* You may also start the real campaign in manual mode, where each action
|
||||
requires manual validation
|
||||
* Finally launch your campaign live, and watch the statistics as the
|
||||
campaign does everything fully automatically.
|
||||
|
||||
While the campaign runs you can of course continue to fine-tune the parameters, input segments, workflow.
|
||||
While the campaign runs you can of course continue to fine-tune the parameters,
|
||||
input segments, workflow.
|
||||
|
||||
Note: If you need demo data, you can install the marketing_campaign_crm_demo module, but this will also install the CRM application as it depends on CRM Leads.
|
||||
Note: If you need demo data, you can install the marketing_campaign_crm_demo
|
||||
module, but this will also install the CRM application as it depends on
|
||||
CRM Leads.
|
||||
""",
|
||||
'website': 'http://www.openerp.com',
|
||||
'init_xml': [],
|
||||
|
|
|
|||
|
|
@ -29,10 +29,10 @@ This module allows you to manage all operations for managing memberships.
|
|||
=========================================================================
|
||||
|
||||
It supports different kind of members:
|
||||
* Free member
|
||||
* Associated member (eg.: a group subscribes to a membership for all subsidiaries)
|
||||
* Paid members,
|
||||
* Special member prices, ...
|
||||
* Free member
|
||||
* Associated member (eg.: a group subscribes to a membership for all subsidiaries)
|
||||
* Paid members
|
||||
* Special member prices
|
||||
|
||||
It is integrated with sales and accounting to allow you to automatically
|
||||
invoice and send propositions for membership renewal.
|
||||
|
|
|
|||
|
|
@ -30,14 +30,13 @@ This module allows Just In Time computation of procurement orders.
|
|||
|
||||
If you install this module, you will not have to run the regular procurement
|
||||
scheduler anymore (but you still need to run the minimum order point rule
|
||||
scheduler, or for example let it run daily.)
|
||||
scheduler, or for example let it run daily).
|
||||
All procurement orders will be processed immediately, which could in some
|
||||
cases entail a small performance impact.
|
||||
|
||||
It may also increase your stock size because products are reserved as soon
|
||||
as possible and the scheduler time range is not taken into account anymore.
|
||||
In that case, you can not use priorities any more on the different picking.
|
||||
|
||||
""",
|
||||
'author': 'OpenERP SA',
|
||||
'depends': ['procurement'],
|
||||
|
|
|
|||
|
|
@ -26,10 +26,11 @@
|
|||
'category': 'Manufacturing',
|
||||
'description': """
|
||||
This module adds state, date_start, date_stop in manufacturing order operation lines (in the "Work Orders" tab).
|
||||
=============================================================================================================
|
||||
================================================================================================================
|
||||
|
||||
Status: draft, confirm, done, cancel
|
||||
When finishing/confirming, cancelling manufacturing orders set all state lines to the according state
|
||||
When finishing/confirming, cancelling manufacturing orders set all state lines
|
||||
to the according state.
|
||||
|
||||
Create menus:
|
||||
Manufacturing > Manufacturing > Work Orders
|
||||
|
|
@ -47,7 +48,7 @@ become 'confirmed'. When the manufacturing order is done, all operations
|
|||
must become done.
|
||||
|
||||
The field 'Working Hours' is the delay(stop date - start date).
|
||||
So that we can compare the theoretic delay and real delay.
|
||||
So, that we can compare the theoretic delay and real delay.
|
||||
""",
|
||||
'author': 'OpenERP SA',
|
||||
'website': 'http://www.openerp.com',
|
||||
|
|
|
|||
|
|
@ -25,9 +25,10 @@
|
|||
'version': '1.0',
|
||||
'category': 'Manufacturing',
|
||||
'description': """
|
||||
The aim is to have a complete module to manage all products repairs. The following topics should be covered by this module:
|
||||
===========================================================================================================================
|
||||
The aim is to have a complete module to manage all products repairs.
|
||||
====================================================================
|
||||
|
||||
The following topics should be covered by this module:
|
||||
* Add/remove products in the reparation
|
||||
* Impact for stocks
|
||||
* Invoicing (products and/or services)
|
||||
|
|
|
|||
|
|
@ -7,8 +7,8 @@
|
|||
Adds enhanced support for (Ether)Pad attachments in the web client.
|
||||
===================================================================
|
||||
|
||||
Lets the company customize which Pad installation should be used to link to new pads
|
||||
(by default, http://ietherpad.com/).
|
||||
Lets the company customize which Pad installation should be used to link to new
|
||||
pads (by default, http://ietherpad.com/).
|
||||
""",
|
||||
'author': 'OpenERP SA',
|
||||
'website': 'http://openerp.com',
|
||||
|
|
|
|||
|
|
@ -24,8 +24,7 @@
|
|||
'version': '1.0',
|
||||
"category": "Project Management",
|
||||
'description': """
|
||||
This module adds a PAD in all project kanban views
|
||||
==================================================
|
||||
This module adds a PAD in all project kanban views.
|
||||
""",
|
||||
'author': 'OpenERP SA',
|
||||
'website': 'http://www.openerp.com',
|
||||
|
|
|
|||
|
|
@ -25,9 +25,7 @@
|
|||
'version': '1.0',
|
||||
'category': 'Hidden/Dependency',
|
||||
'description': """
|
||||
The common interface for pugin.
|
||||
=====================================================
|
||||
|
||||
The common interface for plug-in.
|
||||
""",
|
||||
'author': 'OpenERP SA',
|
||||
'website': 'http://www.openerp.com',
|
||||
|
|
|
|||
|
|
@ -30,10 +30,11 @@
|
|||
'description': '''
|
||||
This module provides the Outlook Plug-in.
|
||||
=========================================
|
||||
Outlook plug-in allows you to select an object that you would like to add
|
||||
to your email and its attachments from MS Outlook. You can select a partner, a task,
|
||||
a project, an analytical account, or any other object and archive selected
|
||||
mail into mail.message with attachments.
|
||||
|
||||
Outlook plug-in allows you to select an object that you would like to add to
|
||||
your email and its attachments from MS Outlook. You can select a partner, a task,
|
||||
a project, an analytical account, or any other object and archive selected mail
|
||||
into mail.message with attachments.
|
||||
''',
|
||||
'init_xml' : [],
|
||||
'demo_xml' : [],
|
||||
|
|
|
|||
|
|
@ -29,14 +29,14 @@
|
|||
This module provides a quick and easy sale process.
|
||||
===================================================
|
||||
|
||||
Main features :
|
||||
---------------
|
||||
* Fast encoding of the sale.
|
||||
* Allow to choose one payment mode (the quick way) or to split the payment between several payment mode.
|
||||
* Computation of the amount of money to return.
|
||||
* Create and confirm picking list automatically.
|
||||
* Allow the user to create invoice automatically.
|
||||
* Allow to refund former sales.
|
||||
Main features:
|
||||
--------------
|
||||
* Fast encoding of the sale
|
||||
* Allow to choose one payment mode (the quick way) or to split the payment between several payment mode
|
||||
* Computation of the amount of money to return
|
||||
* Create and confirm picking list automatically
|
||||
* Allow the user to create invoice automatically
|
||||
* Allow to refund former sales
|
||||
""",
|
||||
'author': 'OpenERP SA',
|
||||
'images': ['images/cash_registers.jpeg', 'images/pos_analysis.jpeg','images/register_analysis.jpeg','images/sale_order_pos.jpeg','images/product_pos.jpeg'],
|
||||
|
|
|
|||
|
|
@ -26,8 +26,8 @@
|
|||
'author' : "OpenERP SA",
|
||||
'category': 'Portal',
|
||||
'description': """
|
||||
This module defines 'portals' to customize the access to your OpenERP database
|
||||
for external users.
|
||||
This module defines 'portals' to customize the access to your OpenERP database for external users.
|
||||
==================================================================================================
|
||||
|
||||
A portal defines customized user menu and access rights for a group of users
|
||||
(the ones associated to that portal). It also associates user groups to the
|
||||
|
|
|
|||
|
|
@ -28,8 +28,8 @@
|
|||
This module shows the basic processes involved in the selected modules and in the sequence they occur.
|
||||
======================================================================================================
|
||||
|
||||
Note: This applies to the modules containing modulename_process.xml
|
||||
e.g product/process/product_process.xml
|
||||
Note: This applies to the modules containing modulename_process.xml.
|
||||
e.g product/process/product_process.xml.
|
||||
|
||||
""",
|
||||
'author': 'OpenERP SA',
|
||||
|
|
|
|||
|
|
@ -32,17 +32,16 @@
|
|||
This is the base module for managing products and pricelists in OpenERP.
|
||||
========================================================================
|
||||
|
||||
Products support variants, different pricing methods, suppliers
|
||||
information, make to stock/order, different unit of measures,
|
||||
packaging and properties.
|
||||
Products support variants, different pricing methods, suppliers information,
|
||||
make to stock/order, different unit of measures, packaging and properties.
|
||||
|
||||
Pricelists support:
|
||||
* Multiple-level of discount (by product, category, quantities)
|
||||
* Compute price based on different criteria:
|
||||
* Other pricelist,
|
||||
* Cost price,
|
||||
* List price,
|
||||
* Supplier price, ...
|
||||
* Other pricelist
|
||||
* Cost price
|
||||
* List price
|
||||
* Supplier price
|
||||
|
||||
Pricelists preferences by product and/or partners.
|
||||
|
||||
|
|
|
|||
|
|
@ -29,9 +29,11 @@ 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.
|
||||
|
||||
Example:
|
||||
For the product PC1 and the partner "Asustek": if listprice=450, and the price calculated using Asustek's pricelist is 225
|
||||
If the check box is checked, we will have on the sale order line: Unit price=450, Discount=50,00, Net price=225
|
||||
If the check box is unchecked, we will have on Sale Order and Invoice lines: Unit price=225, Discount=0,00, Net price=225
|
||||
For the product PC1 and the partner "Asustek": if listprice=450, and the price
|
||||
calculated using Asustek's pricelist is 225. If the check box is checked, we
|
||||
will have on the sale order line: Unit price=450, Discount=50,00, Net price=225.
|
||||
If the check box is unchecked, we will have on Sale Order and Invoice lines:
|
||||
Unit price=225, Discount=0,00, Net price=225.
|
||||
""",
|
||||
"depends": ["sale"],
|
||||
"demo_xml": [],
|
||||
|
|
|
|||
|
|
@ -36,7 +36,7 @@ Project Management module tracks multi-level projects, tasks, work done on tasks
|
|||
It is able to render planning, order tasks.
|
||||
|
||||
Dashboard for project management that includes:
|
||||
--------------------------------------------
|
||||
-----------------------------------------------
|
||||
* List of My Open Tasks
|
||||
* Graph of My Remaining Hours by Project
|
||||
""",
|
||||
|
|
|
|||
|
|
@ -31,14 +31,18 @@
|
|||
Long Term Project management module that tracks planning, scheduling, resources allocation.
|
||||
===========================================================================================
|
||||
|
||||
Features
|
||||
--------
|
||||
* Manage Big project.
|
||||
* Define various Phases of Project.
|
||||
* Compute Phase Scheduling: Compute start date and end date of the phases which are in draft,open and pending state of the project given.
|
||||
If no project given then all the draft,open and pending state phases will be taken.
|
||||
* Compute Task Scheduling: This works same as the scheduler button on project.phase. It takes the project as argument and computes all the open,draft and pending tasks.
|
||||
* Schedule Tasks: All the tasks which are in draft,pending and open state are scheduled with taking the phase's start date
|
||||
Features:
|
||||
---------
|
||||
* Manage Big project
|
||||
* Define various Phases of Project
|
||||
* Compute Phase Scheduling: Compute start date and end date of the phases
|
||||
which are in draft, open and pending state of the project given. If no
|
||||
project given then all the draft, open and pending state phases will be taken.
|
||||
* Compute Task Scheduling: This works same as the scheduler button on
|
||||
project.phase. It takes the project as argument and computes all the open,
|
||||
draft and pending tasks.
|
||||
* Schedule Tasks: All the tasks which are in draft, pending and open state
|
||||
are scheduled with taking the phase's start date.
|
||||
""",
|
||||
"init_xml": [],
|
||||
"demo_xml": ["project_long_term_demo.xml"],
|
||||
|
|
|
|||
|
|
@ -29,19 +29,17 @@
|
|||
"images": ["images/project_mailgate_task.jpeg"],
|
||||
"depends": ["project", "mail"],
|
||||
"description": """
|
||||
This module can automatically create Project Tasks based on incoming emails
|
||||
===========================================================================
|
||||
This module can automatically create Project Tasks based on incoming emails.
|
||||
============================================================================
|
||||
|
||||
Allows creating tasks based on new emails arriving at a given mailbox,
|
||||
similarly to what the CRM application has for Leads/Opportunities.
|
||||
|
||||
There are two common alternatives to configure the mailbox integration:
|
||||
|
||||
* Install the ``fetchmail`` module and configure a new mailbox, then select
|
||||
``Project Tasks`` as the target for incoming emails.
|
||||
* Set it up manually on your mail server based on the 'mail gateway' script
|
||||
provided in the ``mail`` module - and connect it to the `project.task` model.
|
||||
|
||||
|
||||
* Install the ``fetchmail`` module and configure a new mailbox, then select
|
||||
``Project Tasks`` as the target for incoming emails.
|
||||
* Set it up manually on your mail server based on the 'mail gateway' script
|
||||
provided in the ``mail`` module - and connect it to the `project.task` model.
|
||||
""",
|
||||
"init_xml": [],
|
||||
"update_xml": ["security/ir.model.access.csv",
|
||||
|
|
|
|||
|
|
@ -25,27 +25,26 @@
|
|||
'version': '1.0',
|
||||
"category": "Project Management",
|
||||
'description': """
|
||||
Automatically creates project tasks from procurement lines
|
||||
==========================================================
|
||||
Automatically creates project tasks from procurement lines.
|
||||
===========================================================
|
||||
|
||||
This module will automatically create a new task for each procurement
|
||||
order line (e.g. for sale order lines), if the corresponding product
|
||||
meets the following characteristics:
|
||||
This module will automatically create a new task for each procurement order line
|
||||
(e.g. for sale order lines), if the corresponding product meets the following
|
||||
characteristics:
|
||||
|
||||
* Type = Service
|
||||
* Procurement method (Order fulfillment) = MTO (make to order)
|
||||
* Supply/Procurement method = Produce
|
||||
* Type = Service
|
||||
* Procurement method (Order fulfillment) = MTO (make to order)
|
||||
* Supply/Procurement method = Produce
|
||||
|
||||
If on top of that a projet is specified on the product form (in the Procurement
|
||||
tab), then the new task will be created in that specific project.
|
||||
Otherwise, the new task will not belong to any project, and may be added to a
|
||||
project manually later.
|
||||
tab), then the new task will be created in that specific project. Otherwise, the
|
||||
new task will not belong to any project, and may be added to a project manually
|
||||
later.
|
||||
|
||||
When the project task is completed or cancelled, the workflow of the corresponding
|
||||
procurement line is updated accordingly. For example if this procurement corresponds
|
||||
procurement line is updated accordingly. For example, if this procurement corresponds
|
||||
to a sale order line, the sale order line will be considered delivered when the
|
||||
task is completed.
|
||||
|
||||
""",
|
||||
'author': 'OpenERP SA',
|
||||
'website': 'http://www.openerp.com',
|
||||
|
|
|
|||
|
|
@ -27,7 +27,8 @@
|
|||
Changes dates according to change in project End Date.
|
||||
======================================================
|
||||
|
||||
If end date of project is changed then the deadline date and start date for all the tasks will change accordingly.
|
||||
If end date of project is changed then the deadline date and start date for all
|
||||
the tasks will change accordingly.
|
||||
""",
|
||||
'author': 'OpenERP SA',
|
||||
'depends': ['base', 'project'],
|
||||
|
|
|
|||
Some files were not shown because too many files have changed in this diff Show More
Loading…
Reference in New Issue