Comments
Product families does not cover it mostly because of the cost calculations for different outputs. You need also to specify somewhere the coefficents for quantities and cost rates as there may be situation where the quantity output of one of the produced part is large but the cost of the item is actually very small.There was a product named naviMeat, I worked with in Customer site, what had this feature (no associations with the company - I do not know do they even exist any more)
Actually, Arabic localisation has been requested many times by different partners and customers across the region, but until now, Microsoft has given zero tangible feedback.It’s clearly not in their priorities at the moment, even though Arabic is a strategic need.We all hope Microsoft will finally take this seriously, because the demand is real and urgent.
Adding another note here to raise this back up in the history. Without this capability, an organization that wants to shift from general parts handling to traceable parts handling has to essentially duplicate all of their released products, and change all Bills Of Material that utilize the products. This is an undue burden for products that are otherwise form-fit-and-function the same except for the addition (or removal) of traceability.
I will try to explain a working example of this requirement. Many years ago we were selling widgets and at the volume we were selling we stocked them as Eaches. After many years the popularity of the product increased and the volume of goods going in and out of the warehouse has increased. So now the vendor sells it to us in Boxes (1 Box = 10 Each). But we still have to count the goods on the shelf one at a time. It would be preferred to crate an entry somewhere that indicates a choice was made that as-of a point in time, the inventory unit changed. If inventory has to be removed from the system to make the change then OK. The confusion of "what does an Each represent?" as one widget or a box of widgets results in handling the wrong quantity.This would improve the ability of an organization to adjust to the changing needs of a product without having to create a duplicate released product. This would also allow fixing a mistake where the product was created with the wrong unit. I understand why this capability was removed when D365 was released, but we should revisit the impact this decision is having on organizations and the physical handling of goods in the warehouses.