It's really disappointing to hear from you that the BOM comparison is not configurable in FLC. Don't take it otherwise.
There are bunch of key users in our organization (especially operations group) who uses BOM comparison on a daily basis to identify what really changed on the latest released BOM. As most of the BOMs end up with different sequence numbers for the same children across the BOMs, sequence number also shows as a difference causing those users to spend more time on filtering out sequence number changes from BOM comparison report, which is really time consuming and frustrating to them. I feel like I am sticking my neck out at them when I see them at work and I say hi to them because they ask me the same question, "What happened to BOM comparison issue?, Is it fixed?"
I am still wondering is this issue fixed in modern UI? If not, Is there any chance of adding this requirement to your FLC road map to get it addressed soon?
BTW majority of PLM tools, esp. Teamcenter, have a capability to configure what needs to be compared on BOMs upon comparison.
@dfrey.ac
Thanks,
Madhav
