Setting up intermediate codes for process driven BoMs that allow intermediates to be tracked but do not prompt a allocation upon WO generation.

Hello All,

So I'm trying to setup a BoM for a process driven product formula which would look similar to this:

Phase 1 Instructions  (Component type: Text, Type: Active)
Input 1      Weight  (Component: Normal, Type: Physical)
Input 2     Weight  (Component: Normal, Type: Physical)
Input 3     Weight  (Component: Normal, Type: Physical)
Output 1 (Product Intermediate)  Weight  (Component: Normal, Type: Physical)
Output 2 Weight (Waste)  (Component: Normal, Type: Physical)

Phase 2 Instructions  (Component type: Text, Type: Active)
Output 1 (Product Intermediate)  Weight  (Component: Normal, Type: Physical)
Input 1      Weight  (Component: Normal, Type: Physical)
Input 2     Weight  (Component: Normal, Type: Physical)
Input 3     Weight  (Component: Normal, Type: Physical)
Output 3 (Final Product)  Weight  (Component: Normal, Type: Physical)
Output 4 Weight (Waste)  (Component: Normal, Type: Physical)

Currently the intermediate "Outputs" are causing a the WO to request allocations of each though these are not inventory items but a creation of the phase they came out of. In this scenario Output 1 is used as a input component of Phase 2's bom items.

I notice that the text component type has an subtype of "Active" vs "Physical" which doesn't prompt a allocation pull when generating a WO.

Is there a way to setup the Output codes in a way that they have a anticipated weight so that they scale with the WO but are a "active" type so that they do not prompt a WO allocation?

*Component type: Byproduct is not an option in this scenario because we do use that component type in some cases.

Thanks in advance for any help/advice!