Agreed and I realize my words were a bit harsh but I sort of expected it to work out of the box. Just cerate a new WO with two items with BoMs that share common components. A component of type LABOR in each BoM is a very good start. You will see the scripts present data that is not correct.
I will gladly share all my revised scripts as they have addressed this issue and allow for granularity at the WO item level. Before I do though, I need to know the EXPECTED operation of the scripts. I do not want to throw users into the ditch due to revised context functionality.
The good news is Costing works as expected but we still have the issue that WO items with Labour and/or Overhead costs get lost and throw the inventory value off. I have also addressed this issue in my scripts. See here:
http://www.weberp.org/forum/showthread.php?tid=8253
This is another piece that really threw me off the rails...
