I've thinking about this and decided to implement it the following way. 1) Create new entities Center (Administrative Department, Business Unit) and CenterRole (Cost Center, Expense Center, Profit Center, Funds Center). 1.1) Create relations from Center to Party (Internal Organizations) and any other Entity (Product Category, Project, Marketing Campaign) that could represent a Center in a company. 1.2) Create relations from Center to GlAccount. This way I will be able to limit the use of each Center in Accounting Transactions. 2) Add relation from AcctgTransItem to Center and CenterRole 3) When adding an item to a transaction a drop down will list all the Centers related to that GlAccount. 3.1) It will be possible to do things such as distribute an expense between multiple centers.
Daniel. On Mon, Oct 13, 2008 at 7:27 PM, Jacques Le Roux < [EMAIL PROTECTED]> wrote: > Maybe, since they are both primariry keys of PartyGlAccount, both are > needed ? > Though in DemoGlSetupData.xml organizationPartyId is much more used > And partyId seems more used to define a party than to relate it with > something else (usually done through a role). > Note also that in entity FinAccount organizationPartyId is descripted as > "The internal organization Party that owns (or rather, is liable for) the > account." > > So I'd say organizationPartyId, but it's more a guess from what I quickly > found tonight > > HTH > > Jacques > > From: "Daniel Riquelme" <[EMAIL PROTECTED]> > > Regarding Vikrant's first suggestion, >> >> Which field has to be used to link the accounting entries with the >> different >> organizations, partyId or organizationPartyId ? >> I realize that organizationPartyId is used for the relationship with >> GlAccountOrganization. >> >> >> Daniel. >> >> >
