[
https://issues.apache.org/jira/browse/OFBIZ-5282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13856378#comment-13856378
]
Pierre Smits commented on OFBIZ-5282:
-------------------------------------
In my past experiences as a financial controller, I came across several aspects
that are (somewhat) applicable.
First: analysts and budgetteers work with percentages. Staff of the
accounting/bookkeeping department work with amounts/money (actual numbers, not
percentages) and order entry staff work with quantities.
Registering the percentages is solved in the accounting module - cost centers
sections.
But while it is good regarding budgetting, forecasting and analysis it is not
that perfect for entering/processing gl transactions of actuals. Only for
automated periodical transaction processing (of overheads and other indirect
costs). But with regards to manual registrations of gl transactions, it is a
bit short sighted as there will always be situations that a specific
transaction item needs to be allocated differently than what the cost center
definitions dictates.
When transactions of actuals are processed per the division is in the cost
centers definition, it will be very hard to analyse where the differences
precisely occurred.
Secondly, on purchase order level it was common to set/select the (available)
cost center per line item. But, the only options available was to set the
quantity applicable for the cost center of the good ordered (translating to an
line item amount base on quantiy * price) or on the total amount of the line
item for those that didn't relate to goods in a purchase catalog.
Thirdly, with regards to purchases on projects (sub contracts - project
specific consumables/rentals), it was common to set the project and task id per
line item.
Fourthly, no matter what order entry staff did the accounting department was
the final gatekeeper to ensure that everything was registered with the right
codes, allocated to the right costcenter and projects. Again, also here often
reality (the chaos of change) kicks in and (last minute) corrections need to
be made.
While I accept the concept of tagging for reporting purposes to be useful, I
believe that the proposition (the patch) of Hans is both to simplistic (only
percentages) and to complex (from a business process point of view) resulting
in screens that are not user friendly.
> 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: 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)
