We are still in pilot, have two companies in USA and NZ, and a lot of global parts, parts are mastered in NZ.
We are DMTing in their attributes in metric to NZ: mm, litre, kg etc. These are default units in NZ. They are also base units.
When we globalize them, the multicompany process creates the same metric attributes in USA, ie our US staff still see them in mm, ltr and kg. We have set Inches, Gallons, lb as the default units in USA, but have kept the metric as base units there, thinking that’s sensible, but without certainty as to what it all means!
Aside from doing a secondary DMT the units to the US parts created from NZ global parts, or using application studio to add conversion buttons etc, is there any way to have our US people simply see and work with these attributes in their preferred units?
Is this something to do with Dynamic attributes? That seems way more powerful and complex than what we need immediately, just want to make use of the conversion factors we have set up in UOM Class.
From what I can see there’s infrastructure there to support what we want (conversion factors), but we can’t see where these are actually utilized. I haven’t yet found documentation I can follow on unit conversion; a lot of the time searched on this return reults for changing bween UOM classes, I don’tr want this.
(PS, While searching here for help on this I came across “kilo-feet”. I might need a lie-down now )
thankls,
Chris
We set things up a bit differently in that our UOM and Class/Conversions are not global but specific to the company/country as we operate in the UK, Netherlands, and US. Our Parts are global, but the base UOMs are country appropriate. The DMT we used to start it all have the base UOMs edited that way.
Also, in the US, we reserve the Imperial UOMs for Inventory and Manufacturing, and the Metric is used (optionally) for Selling and Purchasing.
As for how it works - the UOM conversions work automatically because you can choose any UOM in the conversion matrix when you are on a line-item entry form - PO, Quote, Order, etc.- and the system will do the conversions for the most part. You select Meters for a Linear Feet IUM Part #, and the system will convert from Meters to feet if the UOMClass for that Part# includes that conversion.
This really doesn’t apply inside the configurator so be careful if you use that. And your MOM/BOMs drive all of the job-related transactions so the Part #'s base UOM should (IMO) match the Manufacturing and Inventory UOM you choose for parts - for clarity/simplicity - but the conversion will work in there for raw materials (I’m pretty sure).
I’ve not found a lot of documentation on the core UOM/Class/Conversion functionality either.
I did find a tutorial video in epicare learning “Understanding Units of Measure in Kinetic” which uses COUNT based examples (EA, Box, Pallet) for using different units for buying, selling and inventory- that helped a little. The attributes page however doesn’t seem to be very unit aware; it would be super nice if the Qty UOM controls there were able to do conversions on the qty as you changed UOM, wouldn’t it @hmwillett ? … are there REST calls to handle unit conversions?
Then on Part.UOM changing (datatable column changed trigger), store the in a transview column in base units. The ugly condition cascade is checking for example “{Part. NetWeightUOM}” == “LB”, the row updates apply conversion factors TO base units in Transview.
And on Part.UOM changed (datatable column changed trigger), convert the transview cached value back into Part.UOM units. The ugly condition cascade is checking for example “{Part. NetWeightUOM}” == “LB” same as in the previous OnChanging event. the row updates apply conversion factors FROM base units in Transview.
I had labeled the conditions with Shape Label, but it appears app studio loses these when you reload the layer.
This took best part of a day (!) to implement as Application Studio kept doing weird things, ended up scrapping layers a couple of times.
I also have a data rule to highlight the qty and UOM fields that are being converted when the convert checkbox is active, as you can see only GrossWeight and NetWeight currently dealt with.
)
… are there REST calls to handle unit conversions?
