Jacopo, i do not know what to say, we already finished implemented it and what you propose we actually did however without the serialized inventory because we already have a serial number on the asset....
Regards, Hans On Wed, 2011-10-05 at 08:19 +0200, Jacopo Cappellato wrote: > Hi Hans, > > I can't see what in my notes would prevent from doing this, since you have > already added the fixedAssetId to the InventoryItem entity (as a side note, I > would have preferred the other way round, i.e. if the field inventoryItemId > was added to the FixedAsset entity)? > > Regards, > > Jacopo > > On Oct 5, 2011, at 6:01 AM, Hans Bakker wrote: > > > Hi Jacopo, > > > > thanks for you comment. I did look into this but decided to not > > duplicate data in the system. > > > > In the case where assets for maintenance and depreciation is not > > connected with a serialized inventory item we will have a number of > > fields duplicated (cost, serial number etc) and we do not know where the > > asset is stored in inventory when not in use. > > > > Regards, > > Hans > > > > On Mon, 2011-10-03 at 12:35 +0200, Jacopo Cappellato wrote: > >> Hi Hans, > >> > >> I have read the threads and the blog posts, and considering the > >> requirements: > >> > >> * the need to maintain (serialized) inventory items and ship/receive them > >> * the need to depreciate the items as assets > >> > >> I am wondering if you have considered the design of: > >> > >> * using product/inventory items (mostly) as in standard OFBiz (add to cart > >> products then reserve,pick,ship inventory items then return product/item) > >> * using fixed assets only for the depreciation > >> > >> Without looking at the details (and I guess I may be missing some of them) > >> this seems to me a simpler approach that would have caused a smaller > >> impact in the existing code. > >> > >> Kind regards, > >> > >> Jacopo > >> > >> On Sep 27, 2011, at 4:59 AM, Hans Bakker wrote: > >> > >>> Thanks Adrian and Paul for the valuable comments. > >>> > >>> Taking all comments into account, we will do the following: (most is > >>> already done) > >>> > >>> 1. a single product can refer to one or more assets. (as is now) > >>> 2. An asset can refer to a single inventory item. (is added) > >>> 3. With this product type, the assetid will be shown on the orderitem, > >>> picklist and shipping slip which also will show the RA# (return auth #) > >>> 4. the item can be received in the facility -> receive return option. > >>> > >>> more info at: > >>> http://www.antwebsystems.com/control/ViewBlogArticle?contentId=91048 > >>> > >>> Regards, > >>> Hans > >>> > >>> > >>> On Fri, 2011-09-23 at 12:20 +0700, Hans Bakker wrote: > >>>> Now we can have rental products where the asset can be rented.... > >>>> > >>>> In this product type the product is a group of video rentals of the same > >>>> rental price referring to many video assets. > >>>> > >>>> However now we also want to categorize these assets in order to display > >>>> them on the e-commerce website. > >>>> > >>>> Is adding a fixedAssetid field to the ProductCategoryMember entity a > >>>> solution? > >>>> > >>>> > >>> > >>> -- > >>> Ofbiz on twitter: http://twitter.com/apache_ofbiz > >>> Alternative ofbiz website: http://www.ofbiz.info > >>> http://www.antwebsystems.com : Quality services for competitive rates. > >>> > >> > > > > -- > > Ofbiz on twitter: http://twitter.com/apache_ofbiz > > Alternative ofbiz website: http://www.ofbiz.info > > http://www.antwebsystems.com : Quality services for competitive rates. > > > -- Ofbiz on twitter: http://twitter.com/apache_ofbiz Alternative ofbiz website: http://www.ofbiz.info http://www.antwebsystems.com : Quality services for competitive rates.
