[
https://issues.apache.org/jira/browse/OFBIZ-5282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13856306#comment-13856306
]
Rupert Howell commented on OFBIZ-5282:
--------------------------------------
I have spent the morning reviewing the accounting segmentation code against the
trunk (rev 1553089). I have also read back through this thread and have
attached an updated patch with some really minor changes which are outlined
below.
Accounting Segments / Tags are extra data marked against the individual
transactions and are used to provide a more granular view of the transactions
when reported on. Jacopo is correct - in a perfect world they really should
not be needed and proper modelling of the accounts should take of them.
However, in my experience of working with OFBiz accounts, the larger the
organisation the more likely the modelling of the accounts and the accounting
processes will lie with an external (to the ERP) source, or the business will
require extra reporting on a piece of data that lies outside the scope of the
current transaction.
One good example of this is something I am currently implementing - a non-stock
purchase order system that covers anything non inventory. In this case when the
items are ordered the user must choose a whole list of attributes that are
assigned ultimately to the transactions and passed to a third party payment
system. These include which "product code" the line item falls under, what
project the item or service will be used for - which stops everything going
into a "Miscellaneous" bucket from a reporting point of view.
The Ledger Segment patch allows multiple series of a limitless number of
attributes to be attached to the transactions when inputting an order through
the Order Manager screens by selecting the information in the drop downs that
appear. To not use the Ledger Segments switching the ledgerSegmentLines flag to
0 will stop them appearing.
The demo data provides the ability to add 3 segment lines with the option of
assigning different percentages to each. However - this would be incredibly
rare and I found it much harder to understand what was going on. While this
functionality does work, in the updated patch I have set this to 1 with 100% of
the value of the transaction attributed to these segments. It's much less
confusing and assigning percentages at this level is kind of stepping over into
cost centres.
When it comes to applying the patch watch out for the AccountingUiLabels,
OrderUiLabels and OrderErrorUiLabels.xml. I think the Chinese characters are
stopping Eclipse's ability to apply the patches correctly. I had to exclude
them, then reapply the patch and guess the fuzz factor before they could be
applied correctly.
> 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.5#6160)
