Costing components are not used in a WO neither in the tracking. But the provisional WO cost and the actual WO cost will be increased with the cost of this component. Isn't it what you try to achieve here?

Thanks, that's correct and as I expected Costing components to work. So good to know I'm on the right track. The issue is that these components need to show up on the WO, in order to export them to xml and then import them into a third party shopfloor system, which for some reason needs to be aware that these items are on the WO.

GB410 said:

The issue is that these components need to show up on the WO,

Unfortunatly this is not standard. Maybe you can change the current export to look for the costing component set on the current BoM code used in the WO.

Thanks Julien, we'll do some development for this; probably to get the item directly from the BOM, as you suggested.

You may want to consider using a text component type and have it print on the BOM.  The text would tell you the information related to the component without impacting the costing.

Thanks for your reply Frank. I've initially considered Text items as well, but the issue is they do want these to impact the costing.

I would do both.  I would use text to "communicate" on paper and use a costing component to achieve the desired cost impact.  This is a little more work from a configuration perspective, but you avoid a customization.  Good luck.

Good one! I'll give that a try.