Call Adapter Error

Hello everybody,
I have a synchronous scenario ABAP Proxy->XI->RFC, the reason why we used XI it's beacuse by company politics any systems integration needs to go by SAP XI, and the reason why we used RFC in the receiver system it's because by company politics too we can't generate proxies in that system, so we decided to go by RFC, now the interface is working really fine, the abap proxy in the sender system is called by a Z program, so this program gives a report of every record, and the problem that I'm facing is that I need to give back to the sender systems errors like this:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!--  Call Adapter
  -->
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
  <SAP:Category>XIAdapterFramework</SAP:Category>
  <SAP:Code area="MESSAGE">GENERAL</SAP:Code>
  <SAP:P1 />
  <SAP:P2 />
  <SAP:P3 />
  <SAP:P4 />
  <SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: could not convert request from XML to RFC:com.sap.mw.jco.JCO$ConversionException: (122) JCO_ERROR_CONVERSION: Date '9999-12-32' has a wrong format at field VALIDA: Unparseable date: "9999-12-32"</SAP:AdditionalText>
  <SAP:ApplicationFaultMessage namespace="" />
  <SAP:Stack />
  <SAP:Retry>M</SAP:Retry>
  </SAP:Error>
this error it's beacuse of the day 32 of the month december, we know that, but this error is only treated as exception CX_AI_SYSTEM_FAULT in the Proxy, and I need to pass the SAPAdditionalText of the error above to the sender system, is there a way to give back to the proxy this text so it will be more explicit in the error and not just a SYSTEM_FAULT???????, thanks in advance.
Regards,
Julio Cesar

Hello VJ,
Thanks for your answer, about the solution your are kindly giving me, it's not really clear to me in this point:
" When ever you get such exceptions, you need to catch them
in your RFC and fill your own exception object and throw it."
the exception I'm getting is a default by SAP, not one I could raise, maybe I'm not understanding right your proposal could you explain me more this part, do you mean that if I declare an exception in my RFC even if I'm not doing the RAISE is going to catch the exception I'm getting?, thanks a lot for your answer.
Regards,
Julio Cesar

Similar Messages

  • XI - Call Adapter Error - HTTP client. Code 402 reason ICM_HTTP_TIMEOUT

    I am using HTTP adapter to post XML PO to vendor's site. We are having this problem with one of our vendor when PO's has more than 15 line items. XI server is getting error-"Call Adapter Error - HTTP client. Code 402 reason ICM_HTTP_TIMEOUT". Actually PO is posted good for the first time on vendor's site but XI is getting above error message and it keeps posting it again. Is there anyway to stop it otherthan manually stopping the XI message? Is there anyway to increase the wait time of the XI server to get the message.
    Thanks in advance.
    Mrudula Patel

    I'm getting the same issue "500 TIMEOUT error" in runtime work bench-->IE--->Test Message. When i manually trigger the file.
    The issue is basically from 01-01-2015 02:00 pm to 02-01-2015 01:am , File is picked from source ftp folder and places in archive but xml messages are not reflecting in SXMB_MONI.
    Today suddenly after 01:00 am messages are successfully processing.
    Please help on this issue. Many Thanks.

  • Call adapter error --- BPM to RFC

    Hi,
         I'm calling a simple RFC from a bpm, and the rfc in turn calls a proxy.At the step where i pass the data from bpm to the RFC i get the following error at the call adapter step:
    <SAP:Category>XIAdapterFramework</SAP:Category>
      <SAP:Code area="MESSAGE">GENERAL</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: Problem inserting a7f68d50-f88a-11db-ad02-001560a7b7a4(INBOUND) into the database: java.sql.SQLException: ORA-01461: can bind a LONG value only for insert into a LONG column</SAP:AdditionalText>
    this seems to be some database error, but i'm not insertinga ny data into any table.
    Can anyone tell me about this.

    Hi-
    Check the Data types you have mentioned for attributes.

  • Call Adapter Error - 401 Unauthorized

    Hi,
    We are using Multi Mapping where it splits 1 message into n messages. The n messages split by this scenario in trun calls another scenario configured in the same PI server using SOAP Adapter.
    The called scenario is SOAP --> Siebel using iWay Adapter.
    When the number of messages split are huge in order of thousands, the server is going for a toss and the called scenaio is failing at Call Adapter Step in IE with HTTP Error 401 Unauthorized. Few of the messages manage to pass successfully.
    Anticipating your valuable inputs.
    Thanks.
    Regards,
    Sudharshan N A

    Hi Sudharshan,
    There can be different reasons for getting HTTP 401: Unauthorized error. As you said, few of the messages are being passed to the called application, I would request you to check the scalability of the Seibel Server.
      Also if you are using a connections from a connection pool, then it may be that the pool itself is getting exhausted, though mostly we get Socket exception/Connection Exception/IO Errors in these cases.
      The other reasons can be that the user you are using to connect Seibel dont have enough permissions. But it is ruled out as you said some messages have been processed.
    If the Seibel server is SSL enabled, and your PI doesn't have any certificate configured, then also you may get such errors.
    Regards,
    Sugata

  • Call adapter: Error exception retnr from pipeline processing

    Hi!
    I am facing with the following error in sxmb_moni by retrieving the message from business system A.
    Errror in part Call adapter
    System_Error: Error exception retnr from pipeline processing
    Can some one help me tp solve this problem?
    Thank you very much!
    regards
    Holger

    Hi,
    Mark RFC destination AI_RUNTIME_JCOSERVER as UNICODE
    check this  Error exception return from pipeline processing
    Re: Queue problem ?
    Thanks!
    Edited by: Sudhir Tiwari on Dec 2, 2008 1:37 PM
    Edited by: Sudhir Tiwari on Dec 2, 2008 1:37 PM

  • Two "Call Adapter" step in SXMB_MONI

    Hello Experts,
    I have developed Sync interface WebService - PI - BAPI.
    However when message is failing due to error in mapping at response side, there are 2 "Call Adapter" steps in sxmb_moni got that message.
    First Call Adapter step is not in error status, however 2nd Call Adapter is in Error status (System Error- Restart not possible).
    Could you please explain me why there are 2 "Call Adapter" steps? Actually there has to be only one step.
    Best Regards,
    Manisha

    First Call Adapter step, there is no error
    but in 2nd call adapter error is
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Adapter
      -->
    - <SAP:Error SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
      <SAP:Category>Application</SAP:Category>
      <SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>
      <SAP:P1>com/sap/xi/tf/_MM_Z_BAPI_VL10_DLVY_CREATE_resp_2_~</SAP:P1>
      <SAP:P2>com.sap.aii.mappingtool.tf7.IllegalInstanceExcepti</SAP:P2>
      <SAP:P3>on: Cannot create target element /ns1:Order/OrderD</SAP:P3>
      <SAP:P4>etail/ListOfItemDetail/ItemDetail. Values missing~</SAP:P4>
      <SAP:AdditionalText />
      <SAP:Stack>Runtime exception occurred during application mapping com/sap/xi/tf/_MM_Z_BAPI_VL10_DLVY_CREATE_resp_2_; com.sap.aii.mappingtool.tf7.IllegalInstanceException: Cannot create target element /ns1:Order/OrderDetail/ListOfItemDetail/ItemDetail. Values missing</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    both call adapter steps are under "Central client" step. why 2 call adapter in one?

  • In the pipeline service, when does call adapter mean

    In the pipeline service, when the call adapter step execute, will it call the XI adapter or the outbound adapter

    Hi,
    It calls the outbound adapter.
    So if your receiver SAP system using proxy/RFC adapter is down, you get a Call Adapter error in SXMB_MONI.
    Regards,
    Puloma.

  • File-IDoc scnario : Error in call adapter

    Hi Experts,
    I have developed File to IDoc scenario. And getting the following error in "Call Adapter" pipeline step. I have mapped the control record values in IDoc like Sender Partner, no, port and same for receiver.
    Have created:
    In XI: RFC destination to connect to ECC (sm59)
            Port for the above RFC sestination (idx1)
    In ECC: New logical system for source file system (BD54)
                Partner Profile for Source (we20)
    Also in Receiver_IDoc_CC, checked options for 1. Apply control record values from payload 2. Take Sender and Receiver from Payload
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Adapter
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <SAP:Category>XIAdapter</SAP:Category>
      <SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_RUNTIME</SAP:Code>
      <SAP:P1>Transaction IDX1: Port SAPEAQ_100, client , RFC destination contain errors</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Error: Transaction IDX1: Port SAPEAQ_100, client , RFC destination contain errors</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    Please tell me if i am doing any mistake.
    Br,
    Nilz

    Hi,
    Adding to Björn
    Check the Port ( Tcode - idx1 ) Port SAPEAQ_100  & Select the Business System where you declared IDOC adapter -go to - Service  and check whether you have mentioned the right Logic System,System ID & Client.
    Cheers
    Agasthuri Doss

  • Error in Call Adapter (IDOC- XI- FILE)

    Hello,
    i have got the following error message in the integration engine monitoring in the "call adapter" part:
       td {font-family : Arial, Tahoma, Helvetica, sans-serif; font-size : 14px;} A:link A:visited A:active HTTP response contains status code 503 with the description Service Unavailable XML element Envelope missing in SOAP message header (SAP XI Extension)
    What is the AFW application?????

    Hi Christian,
    Have a look at the following thread, it might be useful
    XI Server Malfunction:Error in Receiver Adapter
    Regards
    Suraj

  • Error in Call Adapter step

    Hello,
    We have RFC --> HTTPS scenario.
    The RFC Destination of type G is created in XI and the connection test is working fine.
    When I run this scenario, sometimes I get following error:
    com.sap.aii.af.ra.ms.api.DeliveryException: XIAdapter:ATTRIBUTE_CLIENT:.
    Error in sxmb_moni in Call Adapter Step:
      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Adapter
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:Category>XIAdapter</SAP:Category>
      <SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_CLIENT</SAP:Code>
      <SAP:P1>400</SAP:P1>
      <SAP:P2>ICM_HTTP_CONNECTION_FAILED</SAP:P2>
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>HTTP client code 400 reason ICM_HTTP_CONNECTION_FAILED</SAP:Stack>
      <SAP:Retry>N</SAP:Retry>
      </SAP:Error>
    However sometimes it works fine.
    Please help to resolve this.
    Thanks in advance,
    Hetal

    Hello Hetal,
    Can you please elaborate more on the scenario. if it is a RFC -> PI -> SOAP scenario please check if you are using the correct target URL in your Receiver Comm. Channel. Also check if the backend service could be unstable due to network load.
    Thanks.
    Kiran

  • Error in Call Adapter

    Hello,
    We have RFC --> HTTPS scenario.
    The RFC Destination of type G is created in XI and the connection test is working fine.
    When I run this scenario, sometimes I get following error:
    com.sap.aii.af.ra.ms.api.DeliveryException: XIAdapter:ATTRIBUTE_CLIENT:.
    Error in sxmb_moni in Call Adapter Step:
    SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:Category>XIAdapter</SAP:Category>
      <SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_CLIENT</SAP:Code>
      <SAP:P1>110</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>HTTP client code 110 reason</SAP:Stack>
      <SAP:Retry>N</SAP:Retry>
      </SAP:Error>
    However sometimes it works fine.
    Please help to resolve this.
    Thanks in advance,
    Beena.

    Thanks Swarup.
    The HTTPS connection is used from XI to third party. XI is not receiving HTTPS request.
    Still do I need to enable HTTPS on web dispatcher?
    The runtime workbench has following error:
    Received XI System Error. ErrorCode: ATTRIBUTE_CLIENT ErrorText:   ErrorStack: HTTP client code 110 reason
    Transmitting the message using connection http://<dispatcher host>:<http port>/sap/xi/engine?type=entry failed, due to: com.sap.aii.af.ra.ms.api.DeliveryException: XIAdapter:ATTRIBUTE_CLIENT:.
    Thanks,
    Beena.

  • Error in SXMB_MONI in SOAP Header -- Call Adapter

    Hi ALL,
    Got a problem with monitoring activity.
    In SXMB_MONI, iam getting errors with Call Adapter section in SOAP HEADER section of the message.
    The Error part shows the following error:
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Adapter
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:Category>XIAdapterFramework</SAP:Category>
      <SAP:Code area="MESSAGE">GENERAL</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: Problem inserting 4657f861-f853-60e8-e100-00000a80314d(INBOUND) into the database: java.sql.SQLException: ORA-25153: Temporary Tablespace is Empty</SAP:AdditionalText>
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack />
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    Can anybody give me a clear picture of the exact error and what could be the diagnosis for this particular problem.
    cheers,
    Santosh

    Hi Santhosh
    1.Check your authorization settings in XI and R/3. Whether the user has sufficient rights to execute the Function Module etc. This is the most common reason for this error.
    2.If the XI system was brought online even before the R/3 system then re-activate the communication channels from the Integration directory.
    Cheers..
    Vasu
    <u><i><b>** Reward Points if found useful **</b></i></u>

  • Error in Call Adapter stage

    Hi
    I am trying to post to the ECC system using XI Adapter. I get this error at the Call Adapter stage
    URL http://host:port/sap/xi/engine call was terminated because the corresponding service is not available.
    Here the host is the server name of the ECC QAS and port is the ABAP port in SMICM
    How do I solve this error?
    Regards

    Shabarish,
    I guess I got the problem though I don't know how to solve it !
    Well, when I type this link in the IE, http://host:port/sap/xi/engine?type=entry, where host is the ECC QAS and port is the HTTP port maintained in SMICM, I get the same error that I get in the SXMB_MONI of the PIQ.
    Service cannot be reached
    What has happened?
    URL http://host:port/sap/xi/engine call was terminated because the corresponding service is not available.
    Note
    The termination occurred in system ERQ with error code 403 and for the reason Forbidden.
    The selected virtual host was 0 .
    What can I do?
    Please select a valid URL.
    If you do not yet have a user ID, contact your system administrator.
    I think this error has got nothing to do with the service users in PI and it has something to do with the ECC QAS server.
    Regards

  • Error in call adapter in SXM_MONI

    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Adapter
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <SAP:Category>XIAdapter</SAP:Category>
      <SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_RUNTIME</SAP:Code>
      <SAP:P1>MSGGUID 7F8BECB520324BBE088BED6BB02D6CE8: Tag found instead of tag IDOC BEGIN=</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:Stack>Error: MSGGUID 7F8BECB520324BBE088BED6BB02D6CE8: Tag found instead of tag IDOC BEGIN=</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    i am getting this problem in my error analysis.please suggest what could be the issue.
    thanks

    Hi,
    Check the following things:
    1.Try importing the Metadata of the IDOC again in IDX 2
    2.You might be trying to post multiple IDOC and you need to changed the occurance to  0..unbounded for  IDOC  as mentioned in the  Blog /people/michal.krawczyk2/blog/2005/12/04/xi-idoc-bundling--the-trick-with-the-occurance-change
    Regard,
    Srinivas

  • CLIENT_CREATE_FAILED error in the Call Adapter pipeline

    Hi, all.
      i think i've almost done the configuration of XI 3.0(CI + 2 DIs).
      SXI_CACHE, SLDCHECK, import of IR, ID objects ...etc. are O.K.
      But when i really run some scenarios of,
      File Adapter --> XI --> ABAP Proxy or
      ABAP Proxy --> XI --> Java Proxy, messages always got error in the "Call Adapter" pipeline of IS with the following message.
      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Adapter
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <SAP:Category>XIServer</SAP:Category>
      <SAP:Code area="INTERNAL">CLIENT_CREATE_FAILED</SAP:Code>
      <SAP:P1>1</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Cannot register HTTP Client(Exception 1)</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
      Any advice appreciated.
      Best Regards.

    Thanks, guys. Let me update my situation.
    i checked and rechecked dest:// ABAP Proxy : Error in Call Adapter step!
    For the error message of #3, i already attached message in my previous email.
    And following is the error message of #2. Please HELP!!!
    - Help
    !http://BSDEA03.darwin.denka.co.jp:50000/sap/public/icman/img/theme.jpg|alt=SAP|width=122 height=61 border=0 |src=http://BSDEA03.darwin.denka.co.jp:50000/sap/public/icman/img/theme.jpg!
    500 Internal Server Error
    Internal Server Error(-1)
    Error:
    -1
    Version:
    6040
    Component:
    ICM
    Date/Time:
    Tue Jul 26 15:40:19 2005
    Module:
    icxxthrio.c
    Line:
    538
    Server:
    BSDEA03_PDX_00
    Detail:
    internal error occured
    © 2001-2003, SAP AG
    </FONT></td></tr></table></SAP:AdditionalText>
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Error when receiving by HTTP (error code: 405, error text: ICM_HTTP_INTERNAL_ERROR)</SAP:Stack>
      <SAP:Retry>A</SAP:Retry>
      </SAP:Error>
    Any advice appreciated.
    Best Regards.

Maybe you are looking for