Project Report: "Package Unit" Quantity Used In "Amount to Order" Calculation. #341
Description
It appears if there's two entries for a part in the part's Distributor section with a quantity of 1 at price X and quantity 10 at price <X, the Project Report picks the quantity 10 entry since the Price Per Item is less due to the quantity price break? This is fine, but if this lower priced part is used, the Project Report should multiply the "Amount to Order" (Stock minus Project's Qty?) times the "Package Unit" quantity, and this result placed in the "Amount to Order" column. It appears Project Report function simply takes the lowest Price Per Item and multiplies this by Stock minus Project's Qty. and thus doesn't take into account the Package Unit, which I feel it should. If one doesn't want this capability, then one doesn't include multiple part quantities in the part's distributor list. In any case, it shouldn't use the lowest per unit price and not use the Package Unit.
Looking at this closer, it would be ideal if the Project Report could take into account the quantity price breaks by taking the Amount to Order, the Package Price and the Price Per Item to calculate the most economical package size to order and make that Project Report's Amount to Order. In other words, if 6 resistors are more expensive than a package of 10, then order 10.
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.