PI/Seeburger Split997 not recognizing EDIFACT EANCOM D01 map

[Former Member]

Hello Experts,

I'm trying to split an EDIFACT EANCOM D01B ORDRSP message having multiple UNH segments and my Seeburger split997 adapter is not recognizing the map I've deployed in SDM.

I've used the XML message from the SAP Marketplace for EANCOM D01B version because the standard Seeburger EDI adapter does not contain the D01B version by default.

I've generated a map in BIC and deployed the .sda file in PI 7.0 but when I try to process the ORDRSP file I get the following error:

2012-09-13 12:10:31
Success
Send text file "\\\INSAP\GUD-GT-O_08092012_TFL1a.txt", size 3555, character encoding ISO-8859-1 with QoS EO
2012-09-13 12:10:31
Success
SEEBURGER/CLASSIFIER: Successfully read message and configuration data. The analysing and classifing starts now
2012-09-13 12:10:31
Success
SEEBURGER/CLASSIFIER: exiting SeeClassifier successfully
2012-09-13 12:10:31
Success
SEEBURGER BICXIADAPTER.MODULE Message entered Module (CallBicXIRaBean) and will be passed to the adapter now.
2012-09-13 12:10:32
Success
SEEBURGER BICXIADAPTER +++ starting conversion with mapping: See_Edifact +++
2012-09-13 12:10:32
Success
SEEBURGER BICXIADAPTER +++ CONVERSION SUCCESSFUL +++
2012-09-13 12:10:32
Success
SEEBURGER BICXIADAPTER.MODULE BIC Module (CallBicXIRaBean) is exiting succesfully.
2012-09-13 12:10:32
Warning
SEEBURGER/MSGSPLITTER: There is no attachment to split. So there is nothing to do.
2012-09-13 12:10:32
Success
Application attempting to send an XI message asynchronously using connection File_http://sap.com/xi/XI/System.
2012-09-13 12:10:32
Success
SEEBURGER/MSGSPLITTER: Finished splitting!

The Splitter adapter works fine for ANSIX12 & even EDIFACT D96A messages but is not able to recognize the EANCOM D01B version.

I've also maintained the Message-Splitter config in Seeburger Workbench using the maps mentioned below but no luck.

Question:

1) How can I find out which  See_Edifact map the BIC adapter is using to process the inbound file.
2) Am I missing any steps in deploying a new custom map in PI for processing? I've tried the mapping name as  See_E2X_ORDRSP_EAN_D01B, map_E2X_ORDRSP_EAN_D01B and even as map_E2X_ORDRSP_EANCOM_D01B.

Any inputs is appreciated.

Regards,
PSR

[Former Member]

Issue resolved.

The probelm was with the map version. I used the EANCOM D01B verson which is a subset of the UN D01B version and the EDI ORDRSP file had UN version first so I had to use the UN D01B map instead of the EANCOM  D01B.

UNH+1+ORDRSP:D:01B:UN:EAN010

UN!! is first then comes the EAN. Thanks to Seeburger support!

Regards,

PSR

[Former Member]

Hi.

Have you test your  Mapping on BIC with Ansi Mapping?

Also check your message splitter on Seeburger Workbench.

Regards

Lucho.