I’m more familiar with IFS Cloud, but my guess is that this might be related to an inherited configuration rule or a default option defined in the part structure.
Sometimes, when a configuration is created, IFS automatically populates values based on earlier revisions, default characteristics, or valid combinations stored in the configuration rules.
You could check if there’s a default value or dependency set up for that item in the part configuration logic or in the revision history.