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 · Accepted solution]

Hello Former Member,

Thank you very much for thinking it accross

For my current requirement, i compared the differences between EANCOM-ORDERS-96A-EAN008 and EANCOM-ORDERS-93A-EAN007, i saw many difference with differences also in the occurences of tags at various places.

The solution you have was very well thought of ( thanks for it ), but unfortunately I cannot use it since it "might" lead to difficult maintainance and there is no guarantee if another version is added for some other customer..In such case, I would then have to create a common XSD bundling 3 messages. And if the occurences for a particular tag is different in all these 3 versions, then that will make my life more miserable in grpahical mapping

Dont you agree SAP should have provided the option to select the EANCOM sub-version in the sender EDISeparator adaptor of type EANCOM..That should solve my problem. Else, i dont see any logical sense between the sender EDISeparator adaptor of type EANCOM & sender EDISeparator adaptor of type EDIFACT

Thanks

Saurabh

[Former Member · Accepted solution]

Hi Saurabh,

Ideally yes. Subversion would be handy in terms of EANCOM messages.

But, I was under the impression that the major version was the same. But if its different as in your case Orders 93 A and 96A then it would be difficult to handle the structures.

quick question- if the main version is different as in your case, could you not just classify based on orders 93A or 96A in the sender channel.

Regards,

Sudharshan N A

[saurabhkumbhare]

Hi Sudarshan,

Yes, I agree. For 96A and 93A, I should classify based on main version.

And for one of the cases that I have, 96A-EAN008 and 96A-EAN009, i see that there is no difference in both the versions, so for this case I can use the approach you mentioned above in the first place.

Thanks you very much for bringing me to understanding terms. Thanks for your help.

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

[saurabhkumbhare]

Hi Piyush,

My requirement is :

Interface 1 : EDISeparator Sender Interface ( 96A-EAN008 ) ---> Mapping 1 ---> ZCNOSE_ORDERS.ORDER05

Interface 2 : EDISeparator Sender Interface ( 96A-EAN010 ) ---> Mapping 2 ---> ZCNOSE_ORDERS.ORDER05

There are around 21 GLN's sending messages of type 96A-EAN008 and 60 GLN's sending messages of type 96A-EAN010.

As suggested by you in thread is that we have to use '|' as GLN separator. However since I have many GLN's, the option does not work for my scenario unless I create multiple communication channels with sets of GLN's in each communication channel.

Will you agree that if the sender EDI separator adaptor had an option to choose the messag sub-version of the EANCOM message ( EAN008 / EAN010 ), then it would have been simple for me to create 1 Communicaiton channel such that all the messages of Interface 1 would use Mapping 1 and all the messages of Interface 2 would use Mapping 2 irrespective of any sender GLN.

Thanks

Saurabh

[Former Member]

Hi Saurabh,

If you cannot achieve the segregation by standard EDI Sender channel, I could think of below option.

Have a single sender interface (with the XSD of subversion having superset of fields) and communication channel for both EAN sub versions.

The EAN Subversion will be part of your xml payload in UNH segment. Use that as a condition to determine the mapping.

Not sure how far it is feasible.

Thanks.

Regards,

Sudharshan N A

[saurabhkumbhare]

Hi Former Member / .

Do you have any suggestions for this problem.

Thanks

Saurabh

[piyush_gakhar]

Hi Saurabh,

What is your scenario? Would you like to receive two different sub version from same partner or from different partner? Generally the agreement between two partners is to use a specific version and sub version.

In case above is true, you just need to differentiate based on different sender ids in EDI Separator sender channels.

Regards,

Piyush