B2B EDIFACT or EANCOM protocol in EDISeparator sender channel

[former_member592854]

Hi Experts,

Few partners are sending the EDI file in edifact format with ean008 as subversion and some are sending the EDI content in eancom format.we have imported both edifact and eancom content in b2bic.

EDIFACT with EAN008 as subversion:

We have created the mapping using EDIFACT structure(orders96A) and in sender EDISeparator CC ,EDIFACT message protocol is chosen.While testing,its giving error like.

Searching sender channel for Eancom message part message with Message type ORDERS, Message version number D, Message release number 96A, Interchange sender identification xxx, Interchange sender identification code qualifier 14, Interchange recipient identification xxx, Interchange recipient identification code qualifier 14, Message Subversion EAN008, Message Agency UN.

Why EDIseparator is expecting the EANCOM protocol channel.?But the partner is actually sending the EDIFACT file with EAN008 as subversion.

How to handle this case?

Regards,

Karthiga

[peter_karg]

Hi,
if the subversion is starting with EAN (UNH 0057) then PI will automatically process this message as EANCOM.
See also https://archive.sap.com/discussions/thread/3599098

Regards, Peter