I have never implemented version management but my understanding is: managing version is to have a simple way to identify a product / stock based on its unique production process. If same version can be produced in multiple ways, it would defeat the purpose of managing version. Then, you might just need to implement traceability (using lot management for instance) w/o BoM / routing version mgt. 

Maybe you are trying to use version for product alternate such as a T-shirt can be in various sizes. But version management in Sage EM is not designed to handle variant of the same product but evolution of the process through the time.

Even that Julien. Imagine you have Phone version 1 and Phone version 2, both versions active, and you may have two alternatives of production for version 1 and for version 2, if this is a requirement, apparently you can't...

When you move from Version 1 to Version 2, we will assume you stop producing Version 1 (that will become obsolete soon) and you sell Version 2 as the normal one. However if you set Version 1 as derogation, you can continue to sell Version 1 (to get rid of the  stock for instance) or even to produce it as well. 

Somehow I understand what you describe, but even having that behaviour, I mean if I just produce one version at a time, I may have different alternatives of production, for one version only, and as per our testing, you cannot.

So even if technically you have a single BoM code, you have 2 differents BOM depending on the validity period. And using derogation, you can produce both at the same time.

OK... Not for what I want, but understand, thanks for your precious help, as always!

Hi how did you resolve this. We have a similar issue. We are trying to create a different BOM that uses an alternative BOM code but we get the message that "Creation not possible"