Create Standard Part fails for Multi-Level CTO Configuration

Hi everyone,

We are experiencing an issue with the Create Standard Part from Configuration functionality for a Multi-Level CTO structure and would like to know if others have encountered the same behavior and how that was solved. 

When creating a Standard Part from a completed/excisting configuration, the system appears to include all configured components in the structure, rather than only the components that belong to the evaluated configuration.

We observe the following behavior:

• If "Use Configuration Description as Part Description" is selected, only some components receive a value in New Part Description.
• When proceeding to the next step, the process fails with the error:
• If "Use Configuration Description as Part Description" is not selected, the system appears to generate descriptions for all configured components, including components that should not belong to the selected configuration.

Because of this, it looks as if components excluded by the configuration rules are still being included in the Create Standard Part process.

Questions

1. Has anyone experienced similar issues with Create Standard Part on Multi-Level CTO structures?
2. Are there any known limitations for Multi-Level CTO configurations when creating Standard Parts?
3. Is there a known workaround or fix?
4. Should Create Standard Part only process the components that belong to the resolved configuration, or is the current behavior expected?

Any insights, experiences, or recommendations would be greatly appreciated.

Thanks in advance!