[jira] Updated: (OFBIZ-562) Generic Item Schema Review

["Chris Howe (JIRA)" <ji...@apache.org>]

     [ http://issues.apache.org/jira/browse/OFBIZ-562?page=all ]

Chris Howe updated OFBIZ-562:
-----------------------------

    Attachment: entitymodel.xml

entitymodel.xml

This entity model for the generic Item presents two ideas that i would like feedback from anyone who has time or expertise to offer.

First a mostly complete representation of an Item.

Second the introduction of an approach to seperate denormalized data from normalized entities.  There is a lot of benefit of having things like Item.ownerPartyId easily to reference, but this data should be normalized in ItemRole.  Separating into an entity ItemDenormRoles with a one to one relationship with ItemRole creates a nice balance as a view entity can be easily created to make this easy to program with.

> Generic Item Schema Review
> --------------------------
>
>                 Key: OFBIZ-562
>                 URL: http://issues.apache.org/jira/browse/OFBIZ-562
>             Project: OFBiz (The Open for Business Project)
>          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.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira