cancel
Showing results for 
Search instead for 
Did you mean: 

Seeburger - BIC configured as Module

Sudheer_Nagalla
Explorer
0 Kudos

Has any one sucessfully used the BIC as module and convereted the EDI document to XML-EDI format and viceversa. I have configured the BIC as a module and i am running in to all sort of Isssues. Tried to use the Classifier Module to Classify the Message and all it could return was

<classifier><type>AnsiX12</type>

<classifierMappingID>null</classifierMappingID>

<encoding>US-ASCII</encoding>

<additionalIdentifier></additionalIdentifier>

</classifier>

Because the Mapping Id was Null and with the Information that classifier passed to the Bic Module it resolved the mapping name to See_AnsiX12 and i got the Functional Acknowledment in XML-EDI format.

I got fed up and took out the classifier Module and Provided the mappingName as Parmeter for the BIC module and specified the MAP to be used as bic mappingName See_E2X_ANSIX12_850V4010. Now when i try to Process the the 850 EDI File i get an error: ISA Segment Filed I15 is empty even though it has the value "/"

trying to see if any one went through the headchae of Seeburger EDI Adapter and got it working.

<b>Adapter Error:</b>

Sender Adapter v1830 for Party 'Business_Partner_1', Service 'EDI':

Configured at 19:15:57 2005-08-01

Last message processing started 19:19:07 2005-08-01, Error: Module Exception 'com.sap.aii.af.mp.module.ModuleException: Adapter call failed. Reason: --- Conversion of synchronous request from module chain ended with errors ---[Error:ID=2088;LEVEL=3] FieldData checkInputSyntax(): Mandatory, incoming field is empty. Segment:'ISA', Field:'I15'

DESCRIPTION: FieldData Error in Segment [not specified] incoming mandatory Field [not specified] is empty. Check class files.

' found, cause: javax.resource.ResourceException: --- Conversion of synchronous request from module chain ended with errors ---[Error:ID=2088;LEVEL=3] FieldData checkInputSyntax(): Mandatory, incoming field is empty. Segment:'ISA', Field:'I15'

DESCRIPTION: FieldData Error in Segment [not specified] incoming mandatory Field [not specified] is empty. Check class files.

last retry interval started 19:19:21 2005-08-01

length 10,000 secs

<b>Actual Input Document:</b>

ISA00 00 ZZCA7045542000 14007944580RTE 0503240823U004000063519450P/

GSPOCA7045542000007944580RTE2005032408236351945X4010

ST8506351945

BEG00SA450013584120050324*AC

CURBYUSD*1.000

N1SO922431

REFZZ3000*PAORG-

REFZZ903*PAGRU-

PERCNMc JunkinTE5409215020

PERCNNAFTA Purchasing OrgFX5409215030

N1BTCONTACT THE PST AT 704-554-377892903

N2*NO BILL-TO ADDRESS AVAILABLE

REFZZ3000*PAORG-

REFZZ903*PAGRU-

PERCNMc JunkinTE5409215020

PERCNNAFTA Purchasing OrgFX5409215030

N1VN920001008751

REFZZE*SPRAS-

N1STNarrows, VA924022

N2*Celanese Acetate, LLC

N3*3520 Virginia Ave.

N4NarrowsVA24124US

REFZZE*SPRAS-

REFZZVA*REGIO-

PO10001025EA3.62PEPI0VN55159103IN*30300754

PIDF***Pins,RETAINER #66267536008 FOR 3/4 DRIVE

REFWO000050248591

MSG*PINS, RETAINER #66267536008 FOR 3/4 DRIVE SOCKETS-LARGE, ,

SCH25EA**06720050408

N1STNarrows, VA924022

N2*Celanese Acetate, LLC

N3*CC SHOP

N3*3520 Virginia Ave.

N4NarrowsVA24124US

REFZZE*SPRAS-

PERCNtmckinne4381

PO10002050EA3.62PEPI0VN55142194IN*30300755

PIDF***Pins,RETAINER F/3/4 IN DRIVE SOCKET SMAL

REFWO000050248591

MSG*PINS, RETAINER F/3/4 IN DRIVE SOCKET SMALL #66267936007, ,

SCH50EA**06720050408

N1STNarrows, VA924022

N2*Celanese Acetate, LLC

N3*CC SHOP

N3*3520 Virginia Ave.

N4NarrowsVA24124US

REFZZE*SPRAS-

PERCNtmckinne4381

CTT*2

SE486351945

GE16351945

IEA1006351945

Message was edited by: Sudheer Nagalla

Message was edited by: Sudheer Nagalla

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hello,

I have forwarded your problem, do you have an OSS note open for this problem, already?

At a first glance I think it is missing a deimiter at the end of the ISA segment, but thats just a rough guess. I can tell you tomorow.

Greetings

Bernd

Former Member
0 Kudos

Hello,

I'm getting the same message. I'm trying to convert ANSI 856 to XML. Can you tell me what I need to do to fix it.

thank you,

Pam