[jira] [Commented] (OFBIZ-5542) Fixed Asset Management Functionality

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

[jira] [Commented] (OFBIZ-5542) Fixed Asset Management Functionality

Nicolas Malin (Jira)

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

Pierre Smits commented on OFBIZ-5542:
-------------------------------------

It seems to me that it would be better to have a field extension to the PartyAcctgPreference entity, where you would set the type of accounting reporting period (e.g. month, quarter, and other possibilities).

This could then be used as a basis for doing the regular accounting transactions related to fixed assets (depreciation transactions) and others. This could be a scheduled event/action/transaction and could run on a specific day of the period selected (e.g. last day).

As for conversion to the appropriate period type a new function/service would be required to determine that based on purchase (start) date and disposal (end) date and the selected period.

Based on the above, you could then be able to set the exception to the default on class or type level, and even individual fixed asset, but that could be in violation of (your) general accounting principles. But may be applicable in subsidiaries.

> Fixed Asset Management Functionality
> ------------------------------------
>
>                 Key: OFBIZ-5542
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-5542
>             Project: OFBiz
>          Issue Type: Improvement
>          Components: accounting
>    Affects Versions: SVN trunk
>            Reporter: David Hughes-Owens
>
> I have started looking at the Ofbiz capabilities for managing fixed assets and capital expenditure.
> The functionality around adding asset records seems ok in terms of data capture, but there does not appear to be any provision for creating background accounting transactions.
> For depreciation, there are only two methods available and both charge on an annual basis, whereas we charge depreciation monthly. They also charge depreciation in year of acquisition, whereas we do not charge in period of acquisition but do in the period of disposal. There does not appear to be much user-definable flexibility in the depreciation functionality. In addition there does not appear to be a process for performing a mass depreciation run? It appears to calculate each asset individually once acquisition date, expected end of life and depn method are provided.
> There does not appear to be any obvious option for the disposal of an asset. I see an actual end of life date, but cannot see what effect this has? No transactions are created when a date is added? Also how does profit/loss on disposal get calculated and charged to P&L? I see there are separate mappings for profit on disposal and loss on disposal, but where are the proceeds? and how does it know whether a profit or loss is to be generated?
> For transfers, I assume that transfers between departments within the same company are handled by changing ownership or assignment, and future depreciation charges would post to the new owner. However, what about transfers between group companies? (i.e. different legal entities). An inter-company transfer should initiate a disposal in one company and an addition to the other.
> Finally, there is no reporting functionality at all currently. e.g. fixed asset register, additons, depreciation reports etc..
> I would be interested to hear your thoughts on the issues I have raised and if there are any plans to address any of these points in the immediate future.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)