Sage 100

To my manufacturing gurus (@DebThomas @BethBowers ) - what is the reasoning behind not being able to explode sub-assemblies in WO when you have MRP installed and activated? Does MRP ""suggest"" scheduling separate WO's for sub-assemblies? TIA!

No idea WHY but the WOEP from ACS let's you explode them.

Thanks @BethBowers - good to know!

no fair. Beth always gets to answer first...time differences - poo! ;) i believe Sage changed the logic in MRP when they were messing with BOM explosions. MRP should ""normally"" be able to handle them. Sadly our MRP lacks flexibility. But as Beth indicated WO Automation resolves the situation.

Thanks to you too @DebThomas - I was going to suggest adding Manufacturing Automation (FKA WOEP?) to them anyway.

It will always be WOEP to me.... I really have to give ACS kudos - their MA add-on just keeps getting better and better.

Yes, WOEP is now part of WO Automation - a more comprehensive solution

These discussions make me sad. When I see what SAP does as part of minor releases compared to what Sage hasn't fixed in years... In the newest release (in beta now) they added a whole slew of features that close gaps with Sage 100 and other systems and keeps their advantage in other areas. For the manufacturing guru's... In Production (equivalent of BoM and WO) they added resources to production which basically will have made B1 finally truly capable of manufacturing out of the box. These resources have capacity planning and can be added to BOMs (which MRP will blow through). In the same release they are adding by-product support, true valuation by lot or serial, batch BoM updates, and basic routing. Sage will continue to lose market share unless they stop relying on ACS and Job OPS to do all the light lifting.