Hello Amit and all, so how does it behave if you apply my patch and restart the scheduler? I could reproduce the bug without magentoerpconnect and my patch fixed it (well it detected the offending procurements and put them in error so you can fix them). If I understand right Kyle right, he said that if you change a product purchase UOM after some usage, then even if you sale in MTO with the same unit, you can have such an MRP UOM bug. In that case that would be worth a check: does he UOM exception shows up only if you have open procurements in both units? Then does my patch catch he offending procurement properly (I expect so). If yes, that would be just about updating the unit of the offending open procurement again (the old ones then). What do you think Kyle? Any better suggestion? On Wed, Jun 1, 2011 at 2:35 AM, Amit Parik (OpenERP)