Help Text for Accounting Properties in Product and Prod Category are confused / wrong / misleading

[Geoff Gardiner]

Help Text for Accounting Properties in Product and Prod Category:

Using demo database, minimal profile, no chart, added sale module and dependencies.
Revno 1695 server, 2192 addons.

Prod Category:
Accounting Properties (2x) and Accounting Stock Properties (2x) - all help text misleading - it can't all be right.

Product:
Sales Properties (2x) and Purchase Properties (2x) - all help text misleading - it can't all be right.

Furthermore, the layout of the two forms is confusing because Prod Category organizes by Accounting and Accounting Stock, while the Product organizes by Sales and Purchase.

[Fabien (Open ERP) (fp-tinyerp)]

fixed in trunk.

[Ferdinand (office-chricar)]

branch-server 1738
branch-addons 2323
problem still here
see also topic "Stock Moves - accounts definition - URGENT !" on partners list
./addons/stock/product.py
        'property_stock_account_input_categ': fields.property('account.account',
            type='many2one', relation='account.account',
            string='Stock Input Account', method=True, view_load=True,
            help='This account will be used to value the input stock'),
this account holds the credit move of incoming goods
 in German "bewertete Liferanten Lieferscheine" (priced pickings)

./account/product.py
        'property_account_expense_categ': fields.property(
            'account.account',
            type='many2one',
            relation='account.account',
            string="Expense Account",
            method=True,
            view_load=True,
            help="This account will be used to value outgoing stock for the current product category"),
this accounts holds the debit of the incoming product
the text string is somewhat true if the product is a service, but should read
Stock / Expense Account
in German I put Bestandskonto (Vorrat) / Aufwand (Service)

similar seems to be the case for outgoing products (I'll check soon)

If we just change the strings and help, the rest of the code works fine,
I suggest to adapt the field names for better readability
I do not suggest to change the field (database) content, because users (like me) might have used the wrong names with accounts in a way to produce correct results.

[Jay Vora (Serpent Consulting Services) (jayvora)]

Improved in revision revision-id: <email address hidden> 2304.

Thank you.