After digging a little into the modules related to hr, I feel the need for a generic tree structure that could be of help in quite a few case.
I explain myself with a short example. When you define the employees in a company, to will define the manager (his superior) for each employee. Now if your manager leaves the company and is replaced by another one, you will have to edit each subordinate of the leaving manager to change it to the new one. The risk is that you forget one with consequences such as not receiving timesheet validation requests for example. I therefore propose to define and develop a generic tree structure that may solve this type of problem and serve a few other cases. The idea is to split the relational part and the content part of a situation. Taking the previous example, this means that the tree structure would define the hierarchy in the company without using the effective employees but only the structure. This structure, the organizational chart, is much more stable in time and thus requires little maintenance. The employees in turn would then be related to a position in this structure. Now when a manager leaves and is replaced by another, you simply deactivate the leaving manager employee structure and create the new manager employee structure and link it to the right position in the tree. Designing the tree in a generic way, you can do the same thing with: - a matrix organization by adding a second (product oriented) tree structure - a group of interest in the company that is not directly related to the functional hierarchy - the office organization (who is allocated in which office, phone number, etc.) - inventory/assets by providing a generic structure to which an item can be attached - budget tree for head count - etc. The linking of an object to a tree structure should contain a start date (required), end date (optional) and ratio (percentage of the object allocated to the position in the tree) and could be handled by a small module that adds these fields to the specific object. Reporting should allow to show relations in a full tree, filtered on attributes, giving total number of allocations or details of the allocations. Please give me your opinion/feedback on this item. If this topic interests a few, we could make a detailed specification first and work on it. Thanks. -------------------- m2f -------------------- -- http://www.openobject.com/forum/viewtopic.php?p=51092#51092 -------------------- m2f -------------------- _______________________________________________ Tinyerp-users mailing list http://tiny.be/mailman2/listinfo/tinyerp-users
