@jocho: > in the development of a real case online book, products don't have a > default account assigned, neither in the demo. No, there shouldn't necessarily be. It's best to group products into categories and assign accounts there (if different than what is in the properties), as is done in the real case testing.
> and i tried to make an account but no transaction is recorded Note on the page http://doc.openerp.com/book/1/1_3_Real_Case/1_3_Real_Case_testing_wf.html "Testing a Purchase-Sale workflow" that "Accounting entries are generated automatically once the invoice is validated. ..." (paragraph "Control of purchase invoices"). ... > The values on the product form are used (only) to overrride the default > value. > > It is the line that lack on the online book > i will make a sugestion about that. I don't think anything is missing. Just note, that the http://doc.openerp.com/book/1/1_3_Real_Case/1_3_Real_Case_db_setup.html#creating-products-and-their-categories "development of a real case" suggests not to enter accounting properties in products - a good idea - but rather define them in the product categories, e. g. leave the default (if possible). The default is taken from the properties. This means, that if you follow the case strictly, only a purchase account is filled in the product category in the field "expense account" (since no chart of accounts was to be loaded from the repository as would usually be in a real real case ... Thus, normally you will already have a basic suggestion configured for you and therefore not that many empty account property fields in the product categories etc. etc. ... -------------------- m2f -------------------- -- http://www.openobject.com/forum/viewtopic.php?p=37403#37403 -------------------- m2f -------------------- _______________________________________________ Tinyerp-users mailing list http://tiny.be/mailman2/listinfo/tinyerp-users
