Business use case:
-in the eBOM (can be inherit and build from CAD assembly), the engineering deparment will design each single parts and assemblies.
-in the mBOM, manufacturing engineers will delete sub parts of purchased assemblies , cause in the mBOM (and by extension in the ERP), we do not need the sub parts details ... as we never buy or built these single sub parts ...
example for a ball-bearing : all is design in eBOM (ball + casing = bearing.asm) but in mBOM, only bearing
This use case cause the equivalence reports to show differences between eBom and mBOM:
we can not identify "real" difference : ie if engineering department remove or add a new manufactured component
from non significative differences .. a purchased assembly sub component removed by manufacturing department
MPMLink should permit to "disable" some usage link in the mBOM, and all downstream applications should take care of this:
- equivalence reports
- BOM filter ConfigSpec
- Creo View Visu (this use case make the purchased assembly not visible in CreoView (dynamic view in PSB or in MPM Process Plan explorer) Make or buy to be taking in account in order to display correctly structure in CreoView when leaf level isn't managed as article (see SUMA impact ?)
- ESI to send the mBOM without purchased sub levels to ERP
