Reading between the lines; would it be reasonable to suggest we should consider creating a new entity to represent "inventory item packaging" that would have reference to the inventory item and its own set of facility, container, location, etc. attributes?
Assuming yes, I would guess we would have to determine if this "packaging" entity is going to represnt metadata about the packaging or an actual instance of the packaging. The location information would suggest the latter, but the nature of the non-serialized inventory item would require a slightly more complicated relationship then a nice one-to-one (50 ns items -> 50 ii packagings). For us there is no rush on this; we have not prioritized this business requirement against others -- so just building a potential direction to go forward with down the road. - Bob David E Jones-4 wrote: > > For the container data model the term does not refer to product > packaging, but rather something that a number of items can be put in. > The idea is to associate the items with the container and not with a > facility, and then to look up the location of the item you would see > that it is in a container and look up the location of the container. > -- View this message in context: http://www.nabble.com/Splitting-product-packaging-and-physical-product-tp24874481p24893655.html Sent from the OFBiz - User mailing list archive at Nabble.com.
