As there are several different kinds of id values for
reasons outsides of product identification and some of
those values need to be used by different entities I
would like to propose and get a bit of feedback on
expanding on the good identification model.
1) Identification entity
a)identificationId
b)identTypeId
c)idValue
2) IdentificationType
a)identTypeId
b)description
c)parentTypeId
d)hasTable
3) ProductIdentification (was GoodIdentification)
a)productId
b)identificationId
c)productIdentTypeId
4) ProductIdentType (was GoodIdentificationType)
a)productIdentTypeId
b)description
c)parentTypeId
d)hasTable
The following is my need for it
5) InventItemIdent
a)identificationId
b)inventoryItemId
c)inventItemIdentTypeId
6) InventItemIdentType
a)InventItemIdentTypeId
b)description
c)parentTypeId
d)hasTable
7) FixedAssetIdent
a)fixedAssetId
b)identificationId
c)fixedAssetIdentTypeId
8) FixedAssetIdentType
a)fixedAssetIdentTypeId
b)description
c)parentTypeId
d)hasTable
This is the easiest solution that I can come up with
for allowing rental of fixed assets that end up in
inventory from PO (think Rent-A-Center style). The
use of "production capacity" for rental to demonstrate
quantity on hand that OpenSourceTravel uses doesn't
mesh well in my mind for renting of items that leave
the company's physical possession.
There would probably also be a FixedAssetInventoryItem
entity to accomplish this but at the moment I'm
concerned about the duplication/ability to go out of
sync of the serialized inventory that's
assigned/recorded at receiving a shipment and the
rerecording of those idValues for the fixed asset.
Any Feedback on this would be much appreciated!!
