Ideas, ideas! I am implementing ERPNext in my business, and I think that the UOM table is fantastic. I like the fact that ERPNext supports PER ITEM conversion factors, however I consider that a great addition would be a generic, default table. This way, ERPNext could use the generic conversion factor as priority #1, and where a PER ITEM conversion exists, as is currently the case, use the PER ITEM conversion factor as priority #1. This would allow any conversion factor for a BOM, stock entry, or when entering a purchase receipt.
For example, two units of measure are defined in ERPNext.
- “Foot” referring to the English Foot measurement
- “Metre” referring to the SI unit.
The conversion table would thus store that a “Foot”, defined in terms of “Metre” is equivalent to 0.3048 Metre
Electrical wire is purchased from supplier, usually, by “Metre”. But the warehouse or field operator requires amount in “Foot” in Material Request (due to cultural and idiosincratyc behavioral habits that die hard, or is impractical to request change). When the purchase order is printed, the measurement is shown in “Metre”, and stated that amount originally was expressed in “Foot”.
The problem is that having a PER ITEM definition forces you to find the conversion factor each time, where some factors would be ideally pre-loaded into the system, with the SI and worldwide standards pre-loaded by ERPNext and the capability to define or customize the units.
The table should also house a URL to the source where the “standard” measure was referred to, for validation purposes.
Any development going on for this? Any ideas as to where to begin setting this up in ERPNext?
On Github, issue #5032