[jira] [Commented] (OFBIZ-5282) Introduce Accounting ledger segmentation

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

[jira] [Commented] (OFBIZ-5282) Introduce Accounting ledger segmentation

Nicolas Malin (Jira)

    [ https://issues.apache.org/jira/browse/OFBIZ-5282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13853887#comment-13853887 ]

Adrian Crum commented on OFBIZ-5282:
------------------------------------

Hans - please stop being a drama queen. Many OFBiz service providers cater to large organizations, so they would be interested in this feature. Several people have said they would review your patch when they have the time. Jacopo has assigned himself to this issue - so clearly he has interest in it.

Sometimes issues can't be resolved right away - due to busy work schedules or other factors. Some of my patches sat in Jira for 3-4 years before they were committed. So, your experience with this issue is neither unique nor new.


> Introduce Accounting ledger segmentation
> ----------------------------------------
>
>                 Key: OFBIZ-5282
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-5282
>             Project: OFBiz
>          Issue Type: Improvement
>          Components: accounting
>    Affects Versions: SVN trunk
>         Environment: any
>            Reporter: Hans Bakker
>            Assignee: Jacopo Cappellato
>             Fix For: SVN trunk
>
>         Attachments: ledgersegmentOct18.patch
>
>
> We have the possibility here to be able to introduce Apache OFBiz accounting in a large multi company organization. This organization is evaluating the several alternatives and after evaluation of OFBiz, came up with a function which OFBiz needs to have, in order to be considered.
> The user story:
> Although OFBiz accounting has the 'costcenter' function, it is not fine-grained enough, we need to be able to segment the ledger to a lower level that the GL accounts namely to the accounting transaction.. Further, all existing reports should have the facility to be able to select a segment of the ledger for either costing, profit or other purposes like special projects.
> The proposed user interface.
> We need at least at the order item level the ability to specify a parent-segment/segment and a percentage, if the percentange is not 100% the remainder to 100% should be assigned to another segment.
> These segments can be defined and assigned by the user to the order item upon entry. When the related invoice is created the segment(s) will be copied and can overridden before posting when these segment names will be copied to the accounting transaction.
> The proposed user reporting.
> All existing ledger reports will have the additional ability to select these segments and will only incorporate accounting transactions where this segment is specified.
> The proposed technical implementation.
> 1. add a new entity called LedgerSegment with fields: ledgerSegmentId, parentSegmentId, description
> 2. add another 3 similar entities: OrderItemSegment, InvoiceItemSegment, AcctTransSegment to make the relation to the LedgerSegment entity and to specify the percentage.
> 3. Change the order, invoice, accounting transaction screens and ledger report entity views to be able to use the segment names when available in the LedgerSegment entity
> As i said , please let me know what you think, this is a great opportunity for OFBiz accounting.
> Regards,
> Hans Bakker
> CEO AntWebsystems.com



--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
Reply | Threaded
Open this post in threaded view
|

Re: [jira] [Commented] (OFBIZ-5282) Introduce Accounting ledger segmentation

Pierre Smits
Hans,

You forgot (or maybe even neglected) a few key ingredients in your process
to get this improvement adopted.

First it seems you assumed that the hand full committers and other
developers in the community that follow the JIRA issues (or this mailing
list) equals as the community. Sparrows are birds, but birds are not
sparrows. Had you been promoting your ideas and subsequently your progress
in the general mailing list of the project you might have enticed more
proponents of this improvement.

Secondly, it seems that you also assumed that you could force the adoption
of this patch - with bugs - without proper documentation regarding
functionality and usage. Stating in a JIRA comment that the patch is out of
date doesn't help adoption.


Pierre Smits

*ORRTIZ.COM <http://www.orrtiz.com>*
Services & Solutions for Cloud-
Based Manufacturing, Professional
Services and Retail & Trade
http://www.orrtiz.com