EANCOM message : Separate channel per message sub-version

[#1]

Hello Experts,

I have the following scenario:

Flow 1 : ORDERS message  :  Dummy interface ( Sender AS2 channel ) -----> Dummy interface ( Receiver EDISeparator )

Flow 2 :                                  SI_Orders_96AEAN008  ( Sender EDISeparator adapter ) ------------>   IDOC ( Receiver IDOC )

Flow 3 :

SI_Orders_96AEAN009  ( Sender EDISeparator adapter ) ------------>   IDOC ( Receiver IDOC )

If you see, I need to configure 2 separate receiver communication channels based on message subversion to receiver 2 different messages; one CC for receiving EAN008 type of messages and one CC for receiving EAN009 type of messages. But the sender EDISeperator of type EANCOM does not have option to select the sub-version. Can you please tell how to configure 2 separate receiver channels per message sub-version.

Thanks

Saurabh

[saurabhkumbhare]

Hello Sudharshan,

Can you please elaborate more on "Have a single sender interface (with the XSD of subversion having superset of fields) and communication channel for both EAN sub versions." please.

I believe you have the solution for me but I could not get it properly.

1 small example, and I should be able to pick it up.

Thanks

Saurabh

[Former Member]

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