On Sep 19, 2006, at 2:10 AM, Jacopo Cappellato wrote:
David,
really thanks for your help.
This is very similar to what Daniel suggested to do and, even if I
really needed this but on the purchase order/receiving side of the
story, I ended up following your suggestions: I have created a
marketing package (that I order from supplier) and I automatically
decompose when it is received in inventory.
To summarize this interesting conversation, just to be sure to
understand the meaning of all these fields:
Product.unitsIncluded
Product.quantityIncluded
Product.quantityUomId
are just 'descriptive' fields: I mean that their content is
intended to better describe the nature of the product but this
information has no impact in the system (prices and inventory).
Yes, I believe that is still correct. There could be automation uses
for these, but I think to date there is not.
On the other hand, the "amount" (that is stored in the
OrderItem.amountSelected field) is used as a multiplier for the
unit price: if a product (with require amount = Y) has a unit price
of 2$ (ProductPrice) and you select an amount of 100 then the new
unit price (in the cart/order) is 200; the "amount" will not affect
in any way the quantity issued from inventory that is always the
OrderItem.quantity field.
Is this correct?
I think this is correct, but unfortunately it is also a bug... The
amount really should be multiplied by the quantity in order to get
the total to deduct from inventory and so on.
Jacopo
PS: This makes me think that the amount multiplier has some
potential and could be used also to express small unit prices
(amount = 0.0001)... but the problem is that the new unitPrice is
stored in the OrderItem.unitPrice field that has limited
precision... maybe we should store there the original unit price
and just get the order item total as: OrderItem.quantity *
OrderItem.amountSelected * OrderItem.unitPrice
Isn't it done this way already, ie calculating the order item
subtotal this way?
-David
David E Jones wrote:
So, what you're saying is that you want to stock in quantities of
1 but sell only quantities of 50?
You could have a product (product "A") that represents a single
unit and put that in inventory but don't make it available for
sale, and then have another product (product "B") that is
available for sale that represents 50 of the stocked product and
use a marketing package or manufactured product to handle the
quantity.
In this way you don't need any price attached to product A, and
instead just have your $59.99 associated with product B. That way
even if it is a small price that would make the price of product A
too small to reasonably handle, it will still work fine.
-David
