Hi Saurabh,
Key for this approach is to do the comparison between EAN 0008 and EAN 0010 structures.
You can do the comparison in B2B Cockpit -> Compare Messages.
If the differences seem to be just few additional segments or fields in EAN 0010. Then you can create the XSD for EAN 0010 and create an Interface for that.
You can create 2 mappings as per the requirement. You will ignore the additional segments in EAN 008 mapping.
Sender Channel will pick both the sub versions using the Interface.
At runtime, the EAN subversion will be available in one of the UNH segments, query that and have a condition to choose the appropriate mapping.
Regards,
Sudharshan N A