Building on the idea I suggested, the ProductAssoc entity could then be
used to prevent anything other than defective products associated with
either the raw material or finished good from being declared. Can we
agree that logic should be implemented in the service as well?
On 03/08/2014 10:29 AM, Christian Carlow wrote:
Thanks Jacopo,
Since we've established the inventory declaration form should only be
used for stocking in defective products, is there a way to prevent
non-defective products from being declared with the form? Is there an
easy way to determine if a product represents a defective one? If
not, then would using the ProductAssoc entity to relate the defect
(defective-tortilla) to the intended good (good-tortilla) with an
assoTypeId="PRODUCT_DEFECTIVE" be sufficient for modeling the data to
used for applying product declaration limitation rules to the
by-product declaration form?
On 03/08/2014 12:22 AM, Jacopo Cappellato wrote:
On Mar 8, 2014, at 2:38 AM, Christian Carlow
<[email protected]> wrote:
In Jacopo's pizza scenario, the tortilla technically represents a
finished good (though different than the PRun good). But I think
you are saying that the form should only be used for stocking-in
degradated by-products such as processed-dough.
I think we are all on the same line now: in my example, the tortilla
by-product could be returned as a special productId as "defective
tortilla - do not sell to customers".
Jacopo
