You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ofbiz.apache.org by "Shankar Soni (JIRA)" <ji...@apache.org> on 2008/01/03 11:18:34 UTC
[jira] Commented: (OFBIZ-1541) Implement ability to map parties to
GlAccounts
[ https://issues.apache.org/jira/browse/OFBIZ-1541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12555524#action_12555524 ]
Shankar Soni commented on OFBIZ-1541:
-------------------------------------
Hi,
I've read the issue and here you want to add a new entity "PartyGlAccount" is it the only task you wana do?
please give me some more detail so that I prepare the implementation plaan.
> Implement ability to map parties to GlAccounts
> ----------------------------------------------
>
> Key: OFBIZ-1541
> URL: https://issues.apache.org/jira/browse/OFBIZ-1541
> Project: OFBiz
> Issue Type: Sub-task
> Components: accounting
> Affects Versions: SVN trunk
> Reporter: Jacopo Cappellato
> Assignee: Ashish Vijaywargiya
> Priority: Minor
>
> What about adding the ability to define mappings for GlAccountTypeId-->GlAccountId, within the context of an organization, specific for parties (or party groups/party classifications?) in a specified role?
> The idea is to define a mapping like these:
> * "sales invoice transactions for the customer party id 10001 are posted to the account id 999999"
> * "sales invoice transactions for the customers with classification 'important customers' are posted to the account id 8888888"
> * "purchase invoices transactions for supplier 120000 are posted to the account 876555"
> We should define a new entity (entities?), but I'm not sure about the best layout; maybe:
> PartyGlAccount:
> organizationPartyId (PK)
> partyId (PK)
> roleTypeId (PK)
> glAccountTypeId (PK)
> glAccountId
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.