Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

Seeburger BIC problem

Hello experts,

I'm facing a nasty Seeburger BIC problem in my receiver adapter when converting from XML to EDI.

The error is:

- SEEBURGER BICXIADAPTER.MODULE Message could not be forwarded from the Module (CallBicXIRa) to the JCA adapter.

Adapter Framework caught exception: BICMODULE:Adapter call failed. Reason:

- Delivering the message to the application using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Error in BICMODULE-module:Adapter call failed. Reason: .

As you can see, the reason is not mentioned.

When I look into the message monitoring, I see the message does not have a payload. On the SOAP ducument is provided with this content:

authorization:Basic UElJU1VTRVI6SUQzaW5zdGFsbA== accept-encoding:gzip

sap-xi-messageid:4BA11A89186666D8E1000000C0A8A310 content-

length:2916349 host:id3-ma-dwh1.mrco.be:51300 user-agent:SAP NetWeaver Application Server (1.0;711) content-

type:multipart/related;boundary=SAP_001E0BFD21001DEF8CBF15AFFC885B07_END;type="text/xml";start="" soapaction:"http://sap.com/xi/XI/Message/30"ApplicationMessageasynchronous4ba11a89-1866-66d8-e100-0000c0a8a3102010-

03-17T19:07:56ZID2CLNT001SteriaVANBC_UTILMDToSteriaVANMDSnapShot_In_AExactlyOnceInformationOffID2CLNT001XI4ba11a89-1866-66d8-e100-0000c0a8a3103.0is.13.id3-ma-dwh1XI4ba11a89-1866-66d8-e100-0000c0a8a3103.0af.id3.id3-ma-dwh1XIRA4ba11a89-1866-66d8-e100-0000c0a8a310MainDocumentApplication

The Seeburger modules used in my receiver adapter:

1. localejbs/CallBicXIRaBean -- BIC

2. localejbs/Seeburger/Zip -- ZIP

The Module Configuration:

BIC - destEncoding - ISO8859_1

BIC - destSourceMsg - MainDocument

BIC - destTargetMsg - MainDocument

BIC - mappingName - X2E_....

BIC - srcEncoding - ISO8859_1

ZIP - mode - zip

ZIP - sourceDest - MainDocument

ZIP - targetDest - MainDocument

ZIP - zipFormat - gzip

Messages fail at random. ABAP mapping and data are ok.

I think there is a problem with capacity or memory or something.

Anyone any idea?

Thanks a lot!

Dimitri

Former Member
Not what you were looking for? View more on this topic or Ask a question