We manufacture products that contain many subassemblies.  If I create a work order (manually) for the parent part and then use WO-K-D to create work orders for all subassemblies I end up with a minimum of 60 work orders for that particular product and, depending on the options, there can be over 100 work orders.  It doesn't seem feasible to me to to create individual work orders every time we manufacture one of these products.  It would be more than a full time job just to release/issue/enter finished production on 100's and 100's of work orders every day.
 
We'd like to use the work orders to maintain an accurate inventory.  Our production schedule and purchasing schedule is done outside of DBA (meaning we don't let DBA dictate what we should make or purchase).
 
Since we already know fairly accurately what we are going to be producing each month I was thinking I could create one work order for each parent part each month (quantity would be what our forecast dictates) and then just issue materials and enter finished production on a weekly basis.  If the original work order quantity is larger than what we actually produced that month I could just close the work order and start the process all over again.  Does that make sense?  Will that work or am I missing something?  Thanks.

Can you use phantom subassemblies, type B parts?  This gives you the structure in the BOM to show subassemblies and a logical assembly order.  No work order needs to be generated for the subassemblies, because a work order for the parent includes all the phantom subassemblies.

You can nest phantoms within phantoms so the allocation is ultimately for the bottom level items.

Change the Type A to B and then run BM-G to rollup and update all the BOMs to know the subassemblies are type B.
 
As for why it is only one level, Work Orders always look at only one level of BOM.  The Phantom assembly is a mechanism to get around that.