Dear Fabien, Yes I checked the entire hr structure including hr_department. Even though it supports the creation of a hierarchical structure, it has a few severe limitations : - it only defines one simple hierarchy in the company and does not include a mechanism to handle part-time allocations (50% secretary in 2 departments for example) - it is linked to res.users (and not directly to hr.employee) which means that every employee should have an account in order to be present in the structure - you can only define a single structure in the company but you will need more than one if you want to capture the organizational structure (people, department, IT comitee, office structure, assets, ...). - there is a time aspect missing so you cannot track who was at which position in the company at which time. This is for example important when you make a promotion.
Still the principle of using an indirection level between an instance and the relation between the instances is the same between my proposal and the hr_department. I just would propose to make the approach more powerful and generic so you will be able to define more organizational issues efficiently. -------------------- m2f -------------------- -- http://www.openobject.com/forum/viewtopic.php?p=51096#51096 -------------------- m2f -------------------- _______________________________________________ Tinyerp-users mailing list http://tiny.be/mailman2/listinfo/tinyerp-users
