[
https://issues.apache.org/jira/browse/OFBIZ-1539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12554886
]
Jacopo Cappellato commented on OFBIZ-1539:
------------------------------------------
I'd say that the first step is the decision about the DepreciationMethod
entity: should we remove it and use the CustomMethod entity instead?
I think it would be a good idea.
What others think about this?
If we get positive feedback, the next steps will be:
1) modify the FixedAssetDepMethod entity to point to CustomMethod instead of
DepreciationMethod; suppress DepreciationMethod
2) create seed data for DEPRECIATION_FORMULA for the CustomMethodType entity
3) implement a small set of depreciation methods (so that the user can select
the most appropriate one for the fixed asset); the most common ones are
"straight-line depreciation" and "double-declining balance depreciation" (from
the Data Model Resource Book)
formula for straight-line depreciation: (purchase cost - salvage cost) /
estimated life in years of the asset
formula for double-declining balance depreciation: (purchase cost - salvage
cost) * (1 / estimated life in years of the asset) * 2
In this process we should verify if we have all the required fields in the
FixedAsset* data model (salvage cost, purchase cost, estimated life in years of
the asset).
Feedback is welcome.
> Implement fixed asset depreciation (methods)
> --------------------------------------------
>
> Key: OFBIZ-1539
> URL: https://issues.apache.org/jira/browse/OFBIZ-1539
> Project: OFBiz
> Issue Type: Sub-task
> Components: accounting
> Affects Versions: SVN trunk
> Reporter: Jacopo Cappellato
> Assignee: Ashish Vijaywargiya
> Priority: Minor
>
> New entity, crud services and ui, and pluggable services for account
> depreciation algorithms.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
