Erp Forum: The Sage Forum Site

[michael_aussie]

Hi,

We use multi-level Bill Of Materials. The sublevels are phantoms.
When you raise a Works Order in Sage for a BOM, the components in the phantoms are allocated to the WO.
However, if the phantom sublevels have routes with operations, they are not allocated to the WO.
Only the operations the the master BOM are allocated to the WO.

For practical reasons, we cannot put all the operations in the master BOM.
For practical reasons, we cannot raise WOs for the phantoms.
To get around this we currently don't use routes. All of our operations are stock-codes and are included in the BOMs.
Does anyone else have multilevel BOMs with operations?? How do you handle this issue???

To use Preactor we need to set up routes and operations in the WOs.

Any suggestions???

Regards,
Michael.

[michael_aussie]

With no replies..... does this mean that no one uses operations in sub-assemblies??

[michael_aussie]

Well some water has gone under the bridge .. and now I am a route guru!!!

Well not really, but I do now have a good understanding.

Any questions, feel free to ask me.

I still haven't learnt "issue to stage" - any suggestions???

[or-8]

We do use phantom sub-levels in our BOMS but I am not involved with Works orders too much.

Although the routing operations are not on the WO for the upper level item the cost is rolled up when doing a Costed Bill of Material for the upper level.

If the WO was used as a 'route card' things wouldn't get manufactured at the sub-level -
Do you have too many levels/BOMs to consider making subs non-phantoms and having MRP raise the WO for them?

[michael_aussie]

Our BOMs are multi-level (sometimes up to 6 or 7).
Many BOMs are generated as a one off combination pulling together subassemblies.
We have created some "standard" routes. When we raise a WO for a BOM we call up and closest relevant route. We then modify as required.