Le 30/10/2013 18:16, [email protected] a écrit : >> 1. Invoice address >> 2. Delivery address >> 3. Consignee >> 4. External handler/service as third party > > and there are many others, depending on your industry. > > ## Please give me an example. I do not believe that there is more than > that. But give me a chance to follow you on this.
I acknowledged your list in what you call "four main points within a single regular business process", but I 've seen specific cases but industry specific and party relationship is a better design for this. > > ## You had mentioned accounting as a reason for using party > relationship. I wanted to explain to you, why party relation cannot have > anything to do with accounting, as we are not allowed to consolidate > anything by that means. It is different in controlling. I understand what you meant, In my mind, controlling is part of accounting. Rules you mention don't apply to analytics anyway but it was not my point. When I mentionned "consolidate accounting situations", I was thinking about cases like risk exposure to failure of a party, but there are probably many other usages of party relationship. > > Yes. This is my case. Party relationships can only be used in > controlling, not accounting. It is important to keep these separate by > all means. I'm interested in understanding this point. So far, most accountant activity is called accounting. Can you elaborate on this separation ? is it a standard ? any idea how we should consider this in Tryton design ? in Tryton user interface and documentation ? regards -- Dominique Chabord - SISalp
