thanks, but sorry I do not agree (yet)
product_template:
'property_stock_account_input': fields.property('account.account',
type='many2one', relation='account.account',
string='Stock Input Account', view_load=True,
help='When doing real-time inventory valuation, counterpart Journal
Items for all incoming stock moves will be posted in this account. If not set
on the product, the one from the product category is used.'),
product_category
'property_stock_account_input_categ': fields.property('account.account',
type='many2one', relation='account.account',
string='Stock Input Account', view_load=True,
help='When doing real-time inventory valuation, counterpart Journal
Items for all incoming stock moves will be posted in this account. This is the
default value for all products in this category, it can also directly be set on
each product.'),
'valuation':fields.selection([('manual_periodic', 'Periodical
(manual)'),
('real_time','Real Time
(automated)'),], 'Inventory Valuation',
help="If real-time valuation is enabled
for a product, the system will automatically write journal entries
corresponding to stock moves." \
"The inventory variation account
set on the product category will represent the current inventory value, and the
stock input and stock output account will hold the counterpart moves for
incoming and outgoing products."
, required=True),
stock_location
'valuation_in_account_id': fields.many2one('account.account', 'Stock
Input Account',domain = [('type','=','other')], help='This account will be used
to value stock moves that have this location as destination, instead of the
stock output account from the product.'),
the following account move should be created in real time accounting
receipt:
debit: valuation
credit: valuation_in_account_id or property_stock_account_input or
property_stock_account_input_categ
invoice
debit: valuation_in_account_id or property_stock_account_input or
property_stock_account_input_categ
credit: "Account Payable" from partner
I do not see a good reason of using the valuation_out_account_id instead of
valuation_in_account_id especially as the label
"Stock Input Account"
indicates the same purpose for all 3 fields.
the definition of the valuation_in_account_id seems to be there only to
allow separate treatment of incoming goods for each stock_location
whereas the valuation is again defined for the product category.
IMHO in any case the help text for product and prod category must be
modified to describe, that the account is in any case overwritten by
'valuation_in/out_account_id' of stock_location.
** Changed in: openobject-addons
Status: Invalid => New
--
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to OpenERP Project Group.
https://bugs.launchpad.net/bugs/890193
Title:
stock wrong help text
Status in OpenERP Addons (modules):
New
Bug description:
IMHO the help text is wrong for both accounts
in must match in and out must match out
stock/stock.py
'valuation_in_account_id': fields.many2one('account.account', 'Stock
Input Account',domain = [('type','=','other')], help='This account will be used
to value stock moves that have this location as destination, instead of the
stock output account from the product.'),
'valuation_out_account_id': fields.many2one('account.account', 'Stock
Output Account',domain = [('type','=','other')], help='This account will be
used to value stock moves that have this location as source, instead of the
stock input account from the product.'),
To manage notifications about this bug go to:
https://bugs.launchpad.net/openobject-addons/+bug/890193/+subscriptions
_______________________________________________
Mailing list: https://launchpad.net/~c2c-oerpscenario
Post to : [email protected]
Unsubscribe : https://launchpad.net/~c2c-oerpscenario
More help : https://help.launchpad.net/ListHelp
