[
https://issues.apache.org/jira/browse/OFBIZ-562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jacopo Cappellato closed OFBIZ-562.
-----------------------------------
Resolution: Incomplete
If any work will be done in this area, it's better to discuss in the mailing list.
However there seem to be objections (at least David and me) to this patch and not a huge interest from the community.
I'm closing this as 'Incomplete' because the patch is just for the data model and not for the processes/ui.
> Generic Item Schema Review
> --------------------------
>
> Key: OFBIZ-562
> URL:
https://issues.apache.org/jira/browse/OFBIZ-562> Project: OFBiz
> Issue Type: Wish
> Components: product
> Reporter: Chris Howe
> Priority: Minor
> Attachments: entitymodel.xml
>
>
> The current data model treats inventory item and fixed asset as if they have nothing in common. And because there is nothing generic binding the physical item they have even been separated into the notion that the fixed asset physical item is dependent on accounting and the physical inventory item is dependent on product. There is a bit of confusion because of the naming of the entities.
> Of course fixed asset is an accounting term, however I believe the accounting data model has overstepped it's role on the physical item. Applications that have to do with accounting should have no concern on whether the fixed asset was moved from storage area A to facility B, as long as ownership hasn't changed. Likewise accounting shouldn't be concerned on when the last time the item classified as a fixed asset was washed or serviced (however it should be concerned with the charges for those washings and services) In business these departments that take care of these things are different. The dock workers care about what isle the item is stored at; the maintenance department cares about the servicing of the equipment; the bean counter is only concerned about the depreciation of the item and the receipts.
> Because the physical item classified as the fixed asset is an accounting data schema, the product entity depends on accounting. This should not be. Because the physical item is in the accounting schema, manufacturing is now dependent on accounting. This also, should not be. This model prevents Apache OFBiz from supporting the rental of items as well as modularization. Both are features that would greatly enhance the value of Apache OFBiz.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Locked
