Skip to Content
avatar image
Former Member

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

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • avatar image
    Former Member
    Apr 14, 2010 at 03:05 PM

    If the message has no payload, you do not need to search in the Seeburger receiver configuration for errors, because: what should it convert ?

    How do you produce the message for this receiver channel ? Is it a graphical mapping, java mapping ? What is the source payload (SXMB_MONI) ?

    CSY

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Apr 14, 2010 at 03:36 PM

    >

    > 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.

    >

    > The Seeburger modules used in my receiver adapter:

    >

    > 1. localejbs/CallBicXIRaBean -- BIC

    > 2. localejbs/Seeburger/Zip -- ZIP

    >

    Dimitri,

    The reason that you are getting this error is because you are missing the exit module bean. add this module after the zip module

    Processing sequence

    3. localejbs/ModuleProcessorExitBean Local Enterprise Bean Exit

    Module configuration

    exit JNDIName deployedAdapters/SeeXIAS2/Shareable/SeeXIAS2

    There is an exit entry missing which actually is used to pass the bic data to PI box.

    Regards,

    Pavan

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      @ Christian:

      The data is pushed from a SAP backend system, via an ABAP consumer proxy, to the SAP PI system.

      There we use an ABAP mapping to convert the data to an XML structure which was generated from the Seeburger BIC mapping designer tool.

      @ Pavan:

      We do use an exit module. I just didn't mention it because it's standard when you create a communication channel.

      Import remark 1: we process more than 15000 messages and only a few of them (sometimes 40, sometimes 50) are going into error.

      Import remark 2: if I take the XML from SXMB_MONI (just before the call adapter) and put it manually into my Seeburger mapping in the BIC tool, it goes fine. The EDI file is produced.

      Kind regards,

      Dimitri