Seeburger no attachment to split

[anu_patyath]

Hello experts,

<Removed by Moderator>

We are integrating with partner on an EDI incoming document(E2X Mapping)

If i delete all of the CRLFs so that the entire message is on one line,  BIC is able to successfully map the EDI message to XML and generate EDI 997 as well.

But when i try to process the file with each segments in sepearate line it throws me the following error in the BIClog.

INFO This is the Error Segment: GE

INFO ID: 2099

INFO Text: InhouseDocReader doSyntaxCheck(): offset[239]: the found segment GE is not in the message description.

DESCRIPTION: InhouseDocReader Error: The Segment GE is missing in the message description. Check your file.

INFO Source Field:

INFO Source Segment : GE

INFO offset[258]: End of file reached, shutting down...

My file looks like below and there is a newline at the end. I tried deleting the new line but it showed the same error.

ISA*00*          *00*          *02*ZMCD          *ZZ*123456789      *130417*1111*U*00401*000000732*0*T*:~

GS*GF*ZMCD*123456789*20130417*111118*732*X*004010~

ST*990*000000732~

B1*CLLQ*2302181916*20130417*A~

SE*3*000000732~

GE*1*732~

IEA*1*000000732~

I tried the option of replacing the string but for no use and the file did not appear in a single line.

localejbs/Seeburger/ReplaceString                  Local Enterprise         key

key                                                                    searchString         "\n"

key                                                                     replaceString        ""

Kindly tell me what am i missing here.

I have gone through almost all links already.

Thanks to all

Anu Patyath

Message was edited by: Prateek Raj Srivastava

[anu_patyath]

Anybody have any idea on this?

[S0003485845]

Hello,

I have copied the content from thsi post nad made the following modification:

- included one "blank" in the ISA Segment as the sender code was only 14digits....included the CRLF at the end of the file....so that each line ends with the same character... afterwards the file looked like:

ISA*00*

*00*

*02*ZMCD

*ZZ*123456789

*130417*1111*U*00401*000000732*0*T*:~

GS*GF*ZMCD*123456789*20130417*111118*732*X*004010~

ST*990*000000732~

B1*CLLQ*2302181916*20130417*A~

SE*3*000000732~

GE*1*732~

IEA*1*000000732~

And could be translated without any issue....

Has your testfile been received like this from the partner or did you make any modifications before you tried to process it ....?

Kind Regards

Stefan