Are you perhaps seeing this behavior?
Product:SolidWorks Enterprise PDM 2012 CAD Editor
Technically Reviewed Date:4/17/2013
Question: Why does the “Exclude from bill of material” and other BOM or other configuration specific supporessed components not apply when selecting the (@) configuration in a Computed bill of materials (BOM) in the Enterprise PDM BOM view?
Answer: The as built (@) configuration is not what we consider a SolidWorks configuration; it is specific to Enterprise PDM and in the context of a Computed BOM will mainly read and display all the file references but without taking into account any additional SolidWorks configuration settings such as suppressed or excluded references. The “Exclude from bill of material” setting in a part or assembly is stored only for a valid SolidWorks configuration and during the check in operation in Enterprise PDM it will store the configuration information of where it is excluded; this information will be stored for all the SolidWorks configurations but not also the special as built (@) configuration. As a result of this behaviour when we view a bill of material and select the as built (@) configuration it will not take into consideration any configuration specific settings.
EPDM 2015 behaves as described above. To me it makes sense. The '@' tab isn't a configuration, so configuration specific settings have no meaning.
I don't think so, Jim. I'm seeing it with all configurations, and it's only happening with virtual parts. 'Regular' parts that are excluded do not show up in the computed BOM, but virtual parts which are excluded do show up - in every case.
It would be great if someone could try a test with their own setup by creating a test assembly with some regular parts and some virtual parts, then try excluding them from BOM to see what happens in the computed BOM. I suspect this is just an artifact of the way EPDM works (which would be a bummer), but I'd like to be sure if it's specific to our system or not.
EPDM 2015 appears to operated correctly. Virtual parts respect the 'Exclude from BOM' setting as long as you are viewing the computed BOM for a configuration.
It appears they may have addressed this annoying bug in 2015. For the time being I'm stuck with manually deleting all the inappropriate references to excluded virtual parts from my BOMs.