On 07/12/13 11:59 +0100, Sergi Almacellas Abellana wrote: > El 07/12/13 10:11, Cédric Krier ha escrit: > >On 06/12/13 20:22 +0100, Sergi Almacellas Abellana wrote: > >>>Hello, > >>> > >>>Let me first introduce the account chart situation on Spain: > >>> > >>>As initially exposed in [1] in Spain we have two charts of accounts > >>>(account_es[2] and account_es_pyme[3]), but both contain a subset of > >>>common accounts. I will provide an example as I think it's clearer to > >>>understand: > >>> > >>>account_es have accounts (A, A1, A2, B, B1, B2) > >>>account_es_pyme have accounts (A, A1,A2, C, C1) > >>> > >>>On both cases numbered accounts are child of their letters accounts. > >>>Also the name of the account A2 is different on both charts, so they > >>>have the same code, but can be considered as different accounts. > >>> > >>>So in my example both plans have in common accounts (A, A1). In the > >>>real account_es and account_es_pyme modules there are more than 1000 > >>>accounts in common. > >>> > >>>Having said that, for us will be great to have some kind of mechanism > >>>to apply inheritance to a chart of accounts, so both charts will > >>>"inherit" all the common accounts and create their specific accounts. > >>> > >>>Also the root account must be different on each chart, so the can be > >>>installed separately. So what I asking for is that common accounts > >>>should inherit from both root accounts (but only defined one time). > >>> > >>>This will allow us to have all the common records of both plans in a > >>>unique place (I'm not sure to have it on a separate module), and have > >>>on each module all they customizations they need. > >>> > >>>There is some other country that have a similar problem with their > >>>chart of accounts? Have anyone covered a situation like this? > >>> > >>>Can this fit into tryton's core modules? > >Why not just have two modules where you put in a separate XML the common > >part. So you just have to keep in sync (with a simple copy) both files. > That's moreless what we have now (two modules with duplicate data). > And when you develop other modules that adds configuration to the > original modules (see [1]) you end up duplicating information another > time. > > So we will end up having a ton of modules with _es and es_pyme > suffixes. So we are trying to improve this situation.
That's the normal implication because what you name shared data is not shared by your definition. Or you have to change your chart definition to have real shared data. Also if you want to reduce the number of modules, just move your two charts into the same module. -- Cédric Krier - B2CK SPRL Email/Jabber: [email protected] Tel: +32 472 54 46 59 Website: http://www.b2ck.com/
pgpYxGMJfyZgq.pgp
Description: PGP signature
