 |
|
Topic: Cost model
|
| By: Del | Posted on: Nov 22 2021 at 07:03:05 AM | | Does this system use standard costings or some other basis? | |
| By: Support | Posted on: Nov 22 2021 at 01:16:40 PM | | I think you also asked this by email. Minimrp calculates assembly costs and inventory valuation using the items' default (manually inputted) item price. Or last purchase price if that option is enabled. | |
| By: Guest | Posted on: Dec 1 2021 at 12:23:08 AM | Please be aware that what support has mentioned above has bugs in it that minimrp don't seem interested in rectifying any time soon.
Specifically if you have items using the overkit value the generated assembly build costs in the assemblies tab and the inventory valuation report will both be completely wrong. In this case you must create a dummy work order to build 100 of an assembly open it up and get the build cost of that work order from the bottom right corner and divide it by 100 to get the accurate cost of one assembly, to then get the cost value of the amount of those assemblies that you have in your inventory go look at how many you have in stock and multiply the newly acquired single assembly cost you have worked out by the amount you have in stock, unfortunately that's the only way unless minimrp decide to fix it and the inventory valuation function serves no real usable purpose.
| |
| By: Support | Posted on: Dec 1 2021 at 04:24:41 AM | Del. I hope you were satisfied with the answer I gave a week or so ago.
@Guest. You're hijacking this thread to open up a discussion that already has a thread. That other thread is not locked.
But to answer the question anyway.
The OverKit feature is for small value components that frequently get wasted or lost during the manufacturing process.
It CAN NOT work for high value components. Surely your manufacturing process is not losing, breaking or otherwise wasting high value components?
For high value components it can never work. Which ever way we do this for you it will be wrong. You are overkitting an expenive component that is affecting your build costs because the Overkit feature ALWAYS rounds up to a whole component. That means if you build just ONE assembly then the overkit will still overkit that extra component.
This is the worst case scenario and the one we must show as the build cost.
You're suggesting that we divide the cost of that component by 100 to give you a more accurate build cost for one assembly. We could do that and YOU would be happy. But what stops somebody else wanting the cost of overkitted components to be divided by 10, 50 or 1000.
It can never be correct. It's not broken. Just do not use it for high value components that you probably never loss anyway.
But please, if you have an axe to grind, why not email us.
 | |
| By: Support | Posted on: Dec 1 2021 at 04:25:27 AM |  | |
Reply - add a comment to this topic.
You may enter letters, numbers and standard punctuation only. HTML and other scripts/tags will be rejected.
|
|
|
