frappe / erpnext

Free and Open Source Enterprise Resource Planning (ERP)
https://erpnext.com
GNU General Public License v3.0
20.19k stars 7.06k forks source link

[Feature Request] Repacking - Incoming value automatically be same as Outgoing Value #7441

Open addymuliady opened 7 years ago

addymuliady commented 7 years ago

With reference to the following thread: https://discuss.erpnext.com/t/repacking-valuation-difference/18908

I am not sure how the rest feels about this but I think it would be good of the valuation rate of repacked items ties to the Outgoing value.

Like the "Update Rate & Availibiity", could there be a button "Make Incoming Value Same". At a click, it will calculate the Base Rate of Incoming Items to the following:

Base Rate of Incoming Items = Total Outgoing Value / Quantity of Incoming Items

bcornwellmott commented 7 years ago

I think this is best left as a customization to your system. Repacks can have multiple pieces in and out, all with different rates. It seems that there is a fairly limited case for making them all the same.

addymuliady commented 7 years ago

True, it depends on individual user cases.

This is useful for users who are using BOM and in manufacturing sector. An example, users who buy in KG but use grams in their raw materials. The complexity kicks in when repacking several items in one entry as you have mentioned.

dalers commented 7 years ago

I would say supporting separate "buy-as" and "use-as" is absolutely essential for the majority of real manufacturing, not just kitting or packaging. Supporting different "use-as" units for the same Item in different BOMs may be convenient in some cases, but I don't think a hard requirement.

The only example I can think of where different use-as units would be required is where BOMs with very large-quantity item use are in the same db as BOMs with very small-quantity item use (maybe very large-scale production BOMs and very small-scale test or QA BOMs), and the dynamic range from using the same use-as units in both BOMs would introduce unacceptable calculation or rounding errors.

Dale

On Jan 13, 2017, at 3:31 AM, addymuliady notifications@github.com wrote:

True, it depends on individual user cases.

This is useful for users who are using BOM and in manufacturing sector. An example, users who buy in KG but use grams in their raw materials. The complexity kicks in when repacking several items in one entry as you have mentioned.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.