[
https://issues.apache.org/jira/browse/OFBIZ-5282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13893260#comment-13893260
]
simon maskell commented on OFBIZ-5282:
--------------------------------------
We are just starting to look at this topic in more detail and I will be able to
spend more time looking into what we need and I will love to be able to push
back any changes the community feel would be a benefit to Ofbiz. The first
thing we need to look at is how to associated segments(departments/costs
centres/analysis codes) to an accounting transaction. Hans has already done
some work on this in the Patch which we could use or we look to go down the
same route as Opentaps. Hans has created some new entities which build the
segments and then associates these segments to a list and assigns the list id
to the accounting transaction. Opentaps have gone down the route of adding 10
new fields to the accounting transaction entity to record the segments. We
would never use more than 10 but would this cause a problem going down this
route or should we look to make it an unlimited number?
> 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
> Fix For: SVN trunk
>
> Attachments: ledgersegment-2013-12-24.patch, 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.5#6160)
