Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Project Report: "Package Unit" Quantity Used In "Amount to Order" Calculation. #341

Open
slylandro opened this issue Sep 12, 2013 · 2 comments

Comments

@slylandro
Copy link

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.

@Drachenkaetzchen Drachenkaetzchen added this to the 1.0 milestone Oct 16, 2015
@Drachenkaetzchen Drachenkaetzchen modified the milestones: 1.1, 1.0 Mar 14, 2016
@Drachenkaetzchen Drachenkaetzchen modified the milestones: 1.3, 1.2 Jan 17, 2017
@Drachenkaetzchen Drachenkaetzchen modified the milestone: 1.3 Sep 3, 2017
@baradhili baradhili added this to the future milestone Jan 16, 2020
berndoJ added a commit to berndoJ/PartKeepr that referenced this issue May 24, 2020
Implements the feature described in issue partkeepr#341 / partkeepr#404 (related / duplicates)

This simply adds a check to the report calculation which takes the packagingUnit into account.

If the part count (so the missing parts which have to be ordered) is not larger than the packagingUnit of the part distributor, that distributor is omitted (by the continue keyword).
@berndoJ
Copy link

berndoJ commented May 24, 2020

Should be fixed / implemented in pull request 1122.

@christianlupus
Copy link
Collaborator

I will keep this a feature request as is is in fact two parts: For one it is a duplicate of #404.

The other parted is satted here

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.

This is some independant wish that I keep here for reference.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants