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 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. |
[ https://issues.apache.org/jira/browse/OFBIZ-1541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Vijaywargiya reassigned OFBIZ-1541: ------------------------------------------ Assignee: Ashish Vijaywargiya > 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. |
In reply to this post by Nicolas Malin (Jira)
[ 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. |
In reply to this post by Nicolas Malin (Jira)
[ https://issues.apache.org/jira/browse/OFBIZ-1541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12557573#action_12557573 ] Jacopo Cappellato commented on OFBIZ-1541: ------------------------------------------ Hi Shankar, the task is about: 1) define the PartyGlAccount entity 2) implement CRUD services to create/update/delete entries in PartyGlAccount 3) create a new setup screen and menu item ("Party Gl Accounts") in Accounting>General Ledger>Setup>GL Account Defaults where a list of records in the PartyGlAccount entity (filtered by organizationPartyId) is shown, with the ability to update the glAccountId and under it an add form to create new records For #3, you can use as a template for example the screen Accounting>General Ledger>Setup>GL Account Defaults>Product Category Gl Accounts: https://demo.hotwaxmedia.com/accounting/control/editProductCategoryGlAccounts?organizationPartyId=Company After this is done I will take care of adding the new mapping rule to the mapping service. > 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. |
In reply to this post by Nicolas Malin (Jira)
[ https://issues.apache.org/jira/browse/OFBIZ-1541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vikas Mayur reassigned OFBIZ-1541: ---------------------------------- Assignee: Vikas Mayur (was: Ashish Vijaywargiya) > 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: Vikas Mayur > Priority: Minor > Attachments: MapPartiesToGlAccounts.patch > > > 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. |
In reply to this post by Nicolas Malin (Jira)
[ https://issues.apache.org/jira/browse/OFBIZ-1541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vikas Mayur updated OFBIZ-1541: ------------------------------- Attachment: MapPartiesToGlAccounts.patch Patch from Shankar Soni > 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: Vikas Mayur > Priority: Minor > Attachments: MapPartiesToGlAccounts.patch > > > 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. |
In reply to this post by Nicolas Malin (Jira)
[ https://issues.apache.org/jira/browse/OFBIZ-1541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vikas Mayur closed OFBIZ-1541. ------------------------------ Resolution: Fixed Thanks Shankar, your patch is in rev. 613389 with few modifications. > 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: Vikas Mayur > Priority: Minor > Attachments: MapPartiesToGlAccounts.patch > > > 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. |
Free forum by Nabble | Edit this page |