@Marco Belladelli Happy to help. I’ll get a few test cases added and create a PR.

For context, in our specific case we’re using @Any as an alternative to a JOINED inheritance mapping strategy. This allowed us to query strictly on the parent table without a UNION across all children but still retain child table-specific foreign key/non-null constraints that we lose with a SINGLE_TABLE strategy. The @Id field is used as the @JoinColumn on the parent entity's @Any reference to the child, which is where we get our mapping exceptions as of 6.2.0.