On 14/02/13 22:09 +0100, Dr. Axel Braun wrote: > Am Donnerstag, 14. Februar 2013, 21:17:54 schrieb Cédric Krier: > > On 14/02/13 21:12 +0100, Dr. Axel Braun wrote: > > > > > These criteria can be combined, for example to set an analytic > > > > > account for an specific partner and company. > > > > > > > > > > I think this kind of module is very flexible and could be useful for > > > > > several people. It is worth to code it for Tryton. > > > > > > > > As I already explain, such behavior doesn't add any information to the > > > > system indeed it just duplicate it which is always bad. > > > > > > This sounds to me as some kind of pre-aggregation is made with this > > > account: During a business transaction some information is written into > > > this 'account' or whatever we want to call it (other ERP call this > > > 'information-structures'). Afterwards is it much faster to report on this > > > than running a report over all sales documents. So it is a kind of light > > > BI-structure. > > > > Still wrong solution, better to have a *real* BI. > > Well, a real BI is in most cases not online and realtime - ETL is mostly only > once a day. And requires a second system.
Perhaps but only on big system, for SME you can run such queries on the production database (this is the job of a database). But the big flaw in what you propose is that it doesn't survive to change in the configuration, if a product was wrongly configured, you can not fix it unless you update all the analytic move but how can you know about it? You will need to write the same queries as I proposed so it is useless to do analytic accounting for such purpose. So I still maintain that duplicate information is *WRONG*. -- Cédric Krier B2CK SPRL Rue de Rotterdam, 4 4000 Liège Belgium Tel: +32 472 54 46 59 Email/Jabber: [email protected] Website: http://www.b2ck.com/
pgpLH3_LcKDNF.pgp
Description: PGP signature
