ABAP Proxy call gets stuck in qRFC

When I execute my program to trigger an ABAP proxy, the program executes successfully, but then no message appears in the Integration Engine.
I have discovered that every time the program is executed, it ends up with an entry in the qRFC of the sending system. I can execute that manually, and the message appears in the Integration Engine.
Can somebody please tell me why this is happening?
Also, if I execute in client 110, the program works as described, but in client 100 and 120, I have a CX_AI_SYSTEM_FAULT exception raised.
Any ideas why this may be the case?
Kind Regards,
Tony.

Hi Anthony,
May i know what is the flag u got in sxmb_moni of ECC.
>>I have discovered that every time the program is executed, it ends up with an entry in the qRFC of the sending system. I can execute that manually, and the message appears in the Integration Engine.
i understood that the message is strucked in ques( i.e SMQ1 or SMQ2) always.
In order to resolve this, we need to register the ques and activate it.
some ques like XBQ1,XBQA,XBQS*,............etc.
we have QRFC Adminstration option in SMQ1,SMQ2 and SXMB_ADM.
please register and activate it ...
award the points, if it helpful to you
Regards
Mahesh.

Similar Messages

CX_BGRFC_INVALID_DESTINATION during outbound abap proxy call on 7.1

Hi guys,
I'm trying to set up a scenario with outbound abap proxy call using the new WS adapter and when I execute the report with the proxy call I'm getting the CX_BGRFC_INVALID_DESTINATION exception.
I've generated proxy w/o problems, I've set up everything in SOAMANAGER.
Have you experienced this issue?
Thanks for your help,
Olian

Hi guys,
so my connection to SLD works fine now and I'm still getting the error. Any other ideas?
Just in case: this is my proxy code. Is this correct for using with 7.1 and WS adapter?
REPORT Z_PI_PROXYTEST.
data sender_object type ref to ZCO_PROXYTEST_OUT.
data out type ZMT_PROXYTEST_OUT.
data lo_sys_exception TYPE REF TO cx_ai_system_fault.
data err_result type string.
out-ZMT_PROXYTEST_OUT-data = 'sample'.
try.
    create object sender_object
      EXPORTING
        logical_port_name = 'PROXYTEST'.
    call method sender_object->PROXYTEST_OUT
      EXPORTING
        output = out.
    commit work.
catch cx_ai_system_fault into lo_sys_exception.
    call method lo_sys_exception->IF_MESSAGE~GET_TEXT
      RECEIVING
        result = err_result.
    write err_result.
endtry.
write 'Data has been sent to PI'.
Thanks for your help, Olian

Calling where no reception - call gets stuck

sometimes i make a call when exist no reception. the call gets stuck and i can not end it.
in IOS6 i found a quick way to release it buy shifting back and forth to airplane mode.
in IOS7 it's no longer working and i have to restart my phone.
any ideas ?

Hi Anthony,
May i know what is the flag u got in sxmb_moni of ECC.
>>I have discovered that every time the program is executed, it ends up with an entry in the qRFC of the sending system. I can execute that manually, and the message appears in the Integration Engine.
i understood that the message is strucked in ques( i.e SMQ1 or SMQ2) always.
In order to resolve this, we need to register the ques and activate it.
some ques like XBQ1,XBQA,XBQS*,............etc.
we have QRFC Adminstration option in SMQ1,SMQ2 and SXMB_ADM.
please register and activate it ...
award the points, if it helpful to you
Regards
Mahesh.

User-exit/BADI during outbound ABAP proxy call

Hello,
I want to introduce certain check during outbound ABAP proxy calls to PI. This is a generic check, failure of which would stop the proxy call to proceed and raise an exception.
I would like to place this at the generic place which is called for all the outbound ABAP proxy calls, rather than coding this in each and every outbound proxy class as the check is generic.
Is there some user-exit/BADI where i can introduce this? Maybe within class CL_PROXY_OUTBOUND or somewhere else where i can introduce this check.
Any help in this regard would be appreciated.
Best Regards,
Gajendra.

Dear Gajendra ,
i agree with sabrish, you must be having a z report on the application system that must be calling that outbound proxy...may be if the check is generic it may not be related to a proxy so you can code a FM and then call it before you call that proxy in the z report
Giving points is another way to say thanks

Abap proxy call : synchronous / background ?

Hi,
I use currently abap proxy call to send data from ECC to XI, and it works fine ! But... I would like to know two points :
1. Is it possible to execute SYNCHRONOUSLY this call abap proxy and not only in asynchronous...
2. Is it possible to execute in BACKGROUND this call abap proxy, because it seems it use a dialog process, even if the call is inside an abap program executed in background
I will appreciate your feedbacks on these both points ?
Regards.
Mickael

Hi,
Yes, we can do Sysnchronous call in Proxy.
and we can do the Background job schedule also in Proxy .
Reffer this help file
http://help.sap.com/saphelp_nw04/helpdata/en/86/58cd3b11571962e10000000a11402f/content.htm
Reffer this BLOG also
/people/sravya.talanki2/blog/2006/07/28/smarter-approach-for-coding-abap-proxies
Regards
Seshagiri
Edited by: N V Seshagiri on Feb 12, 2008 11:19 AM

System exception after a succesful synchronous ABAP Proxy call

Guys,
I have the following scenario:
1) From an R/3 box I initiate a synchronous ABAP proxy call
2) On XI everything works fine, the http request is sent out (using the http adapter), the response comes back succesfully and it is transfered back to the R/3 box - no error whatsoever
3) On the R/3 box however the EXECUTE_SYNCHRONOUS method throws a system exception BUT the returning (input) parameter holds the response message!
So in the end if I catch this exception (CX_AI_SYSTEM_FAULT) then I could be happy and just ignore the exception, but I don't feel comfortable leaving it this way. Why is the exception and how can I eliminate it?
Any help would be greatly appreciated.
Thanks a lot,
Viktor

Joel/Jörg,
Thank you for your response, indeed I ended up debugging it and found my error deep down:
Error code: ABAP_PROXY.PARSE_APPLICATION_DATA
Error text: Error handling Response Message; XSLT error: CX_XSLT_DESERIALIZATION_ERROR: XSLT program and source line: /1SAI/XS00000000000000000088: 0000000122; Tree Position: abap.values.1.1.1.6.1.5 ABAP Classname: CX_SY_CONVERSION_DATA_LOSS Data String: WINDSOR CT 06095-1712
The data field defined in SAP was too short for the field.
Thanks a lot,
Viktor

ABAP proxy call to eBay webservice

Hi,
I'm trying to configure an ABAP proxy call to the eBay SOAP web services using ECC6 (SP14).
Has anyone had any experience they can share on how to configure the security for the proxy endpoint in SOAMANAGER to use the ebay services?
Thanks
Tim

Hi,
Yes, we can do Sysnchronous call in Proxy.
and we can do the Background job schedule also in Proxy .
Reffer this help file
http://help.sap.com/saphelp_nw04/helpdata/en/86/58cd3b11571962e10000000a11402f/content.htm
Reffer this BLOG also
/people/sravya.talanki2/blog/2006/07/28/smarter-approach-for-coding-abap-proxies
Regards
Seshagiri
Edited by: N V Seshagiri on Feb 12, 2008 11:19 AM

FTP to ABAP Proxy Scenario - getting error CO_TXT_CHANNEL_PASSWORD_ERROR

We have transported PI and EP data from development server to respective production, every thing is running fine except the abap proxy scenarios i.e. PI reads file from ftp location and calls the abap proxy but we are getting following errors:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

<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="OUTBINDING">CO_TXT_CHANNEL_PASSWORD_ERROR</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unable to read user password from communication channel of type Error when accessing the secure store (access ID = FD768D4A8772DB50E1000000AC10041E) Error while reading from the secure store: ERROR_UNKNOWN: Cannot find entry in secure store (SECSTORE,023)</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Any solution?
Please note that I have searched and applied solutions given on SDN forums but didn't get any success. So I am looking for new suggestions.
Regards,
Jawed Ali

Jawed ,
Please test the HTTP destination of your receiver comm channel.
Which is the RFC connection to your R3 system.
Transaction SM59 and check the logon parameter for the connection you are using.
Regards,

Abap proxy call failed

Hi,
I am trying to call (synchronous mode) from XI 3.0 an ABAP proxy located on a R3 enterprise 4.7 ext 2.00 server.
Unfortunately, when I send the request message with the XI Adapter to the local integration engine using message protocol 2.0,
an error occured on the R3 system:
PROTOCOL.LOOP_IN_MESSAGE_ROUTING
<SAP:ErrorHeader xmlns:SAP="http://sap.com/exchange/MessageFormat">
               <SAP:Context></SAP:Context>
               <SAP:Code p1="is.00.hermes" p2="IS" p3="XI" p4="">PROTOCOL.LOOP_IN_MESSAGE_ROUTING</SAP:Code>
               <SAP:Text language="EN"></SAP:Text>
            </SAP:ErrorHeader>
            <SAP:HopList xmlns:SAP="http://sap.com/exchange/MessageFormat" Version="1.0">
               <SAP:Hop SystemName="is.00.hermes" Type="CENTRAL" TimeStamp="2005-08-04T18:11:25Z" WasRead="0">
                  <SAP:MessageInbound>
                     <SAP:Type></SAP:Type>
                     <SAP:AdapterRefId>3.0</SAP:AdapterRefId>
                     <SAP:MessageId>2B1B2E10-0513-11DA-A979-0013216B8075</SAP:MessageId>
                  </SAP:MessageInbound>
                  <SAP:MessageOutbound>
                     <SAP:Type>IENGINE</SAP:Type>
                     <SAP:AdapterRefId>3.0</SAP:AdapterRefId>
                     <SAP:MessageId>2B1B2E10-0513-11DA-A979-0013216B8075</SAP:MessageId>
                  </SAP:MessageOutbound>
               </SAP:Hop>
               <SAP:Hop SystemName="is.00.hermes" Type="CENTRAL" TimeStamp="2005-08-04T18:11:25Z" WasRead="0">
                  <SAP:MessageInbound>
                     <SAP:Type>IENGINE</SAP:Type>
                     <SAP:AdapterRefId>3.0</SAP:AdapterRefId>
                     <SAP:MessageId>2B1B2E10-0513-11DA-A979-0013216B8075</SAP:MessageId>
                  </SAP:MessageInbound>
                  <SAP:MessageOutbound>
                     <SAP:Type></SAP:Type>
                     <SAP:MessageId>2B1B2E10-0513-11DA-A979-0013216B8075</SAP:MessageId>
                  </SAP:MessageOutbound>
               </SAP:Hop>
               <SAP:Hop SystemName="UPG" Type="RECEIVER" TimeStamp="2005-08-04T18:11:25Z" WasRead="0">
                  <SAP:MessageInbound>
                     <SAP:Type>IENGINE</SAP:Type>
                     <SAP:AdapterRefId>2.0</SAP:AdapterRefId>
                     <SAP:MessageId>2B1B2E10-0513-11DA-A979-0013216B8075</SAP:MessageId>
                  </SAP:MessageInbound>
                  <SAP:MessageOutbound>
                     <SAP:Type>PROXY</SAP:Type>
                     <SAP:MessageId>2B1B2E10-0513-11DA-A979-0013216B8075</SAP:MessageId>
                  </SAP:MessageOutbound>
               </SAP:Hop>
            </SAP:HopList>
            <SAP:MessageHeader xmlns:SAP="http://sap.com/exchange/MessageFormat" version="1.0" SOAP:mustUnderstand="1">
               <SAP:From>
                  <SAP:Name>WebServer</SAP:Name>
                  <SAP:Interface namespace="http://adixen.fr/test">DataUserQuery_out</SAP:Interface>
               </SAP:From>
               <SAP:To>
                  <SAP:Name>UPG</SAP:Name>
                  <SAP:Interface namespace="http://adixen.fr/test">DataUserQuery_in</SAP:Interface>
               </SAP:To>
               <SAP:MessageId>2B1B2E10-0513-11DA-A979-0013216B8075</SAP:MessageId>
               <SAP:QualityOfService>BestEffort</SAP:QualityOfService>
               <SAP:TimeSent>2005-08-04T18:11:24Z</SAP:TimeSent>
               <SAP:Direction>Response</SAP:Direction>
               <SAP:Document></SAP:Document>
            </SAP:MessageHeader>
            <SAP:InternalAttributesHeader xmlns:SAP="http://sap.com/exchange/MessageFormat">
               <SAP:AdapterInbound>PROXY</SAP:AdapterInbound>
               <SAP:AdapterOutbound>IENGINE</SAP:AdapterOutbound>
            </SAP:InternalAttributesHeader>
         </SOAP:Header>
         <SOAP:Body xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
            <SAP:Manifest xmlns:SAP="http://sap.com/exchange/MessageFormat" xmlns:xlink="http://www.w3.org/1999/xlink" version="1.0">
               <SAP:Payload xlink:href="cid:[email protected]">
                  <SAP:Document>TraceDocument</SAP:Document>
               </SAP:Payload>
            </SAP:Manifest>
         </SOAP:Body>
      </SOAP:Envelope>--SAP_41F726EA34ED2F498C6BA328BAB08C43_ENDcontent-type:text/plaincontent-length:2912content-id:[email protected]
      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
         <SAP:TraceHeader xmlns:SAP="http://sap.com/exchange/MessageFormat">
            <Trace level="1" type="B">CL_XMS_TROUBLESHOOT-ENTER_PLSRV</Trace>
            <Trace level="1" type="E">CL_XMS_TROUBLESHOOT-ENTER_PLSRV</Trace>
            <Trace level="1" type="T">**************************************************** </Trace>
            <Trace level="1" type="T">*                                                  * </Trace>
            <Trace level="1" type="T">*                                                  * </Trace>
            <Trace level="1" type="T">XMB entry processing </Trace>
            <Trace level="1" type="T">system-ID = UPG</Trace>
            <Trace level="1" type="T">client = 100</Trace>
            <Trace level="1" type="T">language = E</Trace>
            <Trace level="1" type="T">user = YLEBLEVEC</Trace>
            <Trace level="1" type="Timestamp">2005-08-04T18:11:25Z </Trace>
            <Trace level="1" type="T">*                                                  * </Trace>
            <Trace level="1" type="T">*                                                  * </Trace>
            <Trace level="1" type="T">**************************************************** </Trace>
            <Trace level="1" type="B">CL_XMS_MAIN-CALL_UC_EXECUTE</Trace>
            <Trace level="1" type="T">Message-GUID = 2B1B2E10051311DAA9790013216B8075</Trace>
            <Trace level="1" type="T">PLNAME = SENDER</Trace>
            <Trace level="1" type="T">QOS = BE</Trace>
            <Trace level="1" type="B">CL_XMS_MAIN-CALL_PIPELINE_SYNC</Trace>
            <Trace level="1" type="T">Get definition of pipeline PID= SENDER</Trace>
            <Trace level="1" type="B">CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST</Trace>
            <Trace level="1" type="E">CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST</Trace>
            <Trace level="1" type="B">PLSRV_CALL_INTEGRATION_SERVER</Trace>
            <Trace level="1" type="B">CL_XMS_MAIN-CALL_PLSRV</Trace>
            <Trace level="1" type="B">CL_XMS_MAIN-CALL_PLSRV_LOCAL</Trace>
            <Trace level="1" type="B">CL_XMS_PLSRV_CALL_XMB-ENTER_PLSRV</Trace>
            <Trace level="1" type="T">URL for integration server read from global configuration </Trace>
            <Trace level="1" type="T">URL= dest://INTEGRATION_SERVEUR</Trace>
            <Trace level="1" type="B">CL_XMS_MAIN-SET_TECHNICAL_ROUTING_PROPERTY</Trace>
            <Trace level="1" type="E">CL_XMS_MAIN-SET_TECHNICAL_ROUTING_PROPERTY</Trace>
            <Trace level="1" type="B">CL_XMS_PLSRV_CALL_XMB-CALL_XMS_HTTP</Trace>
            <Trace level="1" type="E">CL_XMS_PLSRV_CALL_XMB-CALL_XMS_HTTP</Trace>
            <Trace level="1" type="E">CL_XMS_PLSRV_CALL_XMB-ENTER_PLSRV</Trace>
            <Trace level="1" type="E">PLSRV_CALL_INTEGRATION_SERVER</Trace>
            <Trace level="1" type="E">CL_XMS_MAIN-CALL_PIPELINE_SYNC</Trace>
            <Trace level="1" type="B">CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST</Trace>
            <Trace level="1" type="E">CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST</Trace>
            <Trace level="1" type="E">CL_XMS_MAIN-CALL_UC_EXECUTE</Trace>
            <Trace level="1" type="E">CL_XMS_MAIN-ENTER_XMS</Trace>
            <Trace level="1" type="E">CL_XMS_HTTP_HANDLER-HANDLE_REQUEST</Trace>
         </SAP:TraceHeader>SAP_41F726EA34ED2F498C6BA328BAB08C43_END
I guess the error occurs before the call of my proxy. Can anyone help?
Thanks,
Yann

Hi,
>>>However to be able to process XML messages on 'UPG' I need to activate the service '/default-host/sap/xi/engine'. This service start my local integration engine, correct?
I thought you tried to send messsages from the same WAS local can be set on every client - the same as R3 - right
further reference (XI configuration guide):
<b>Connecting Business Systems with an Integration Engine to the Central Integration Server</b> <-- you have to do all of those steps on your R/3 (SLD, SICF, SXMB_ADM etc.)
>>>>Last question do I need to have 2 different clients on UPG, the one for my local integration engine and the other one for my ABAP proxies? Can they be on the same client?
yes you can send proxies (from r3) to XI from the same client as your R3 system (application system)
no need for a second client on R3 side:)
sorry if I confused you with my response
Regards,
michal
Message was edited by: Michal Krawczyk

Idoc syntx error me21 , abap proxy call transaction

Hi Experts,
I am struck with the below problem, could you please shed some light on the issue, appreciate your help and rewarded.
scenario:
XI sends NEW PO message to abap proxy, in abap proxy we populate bdc_tab
and call ME21 as below
CALL TRANSACTION 'ME21' using bdc_tab mode 'N' update 'S' messages into messtab.
problem:
EKSEKS01 idoc is getting created with syntax error status code :26 in ECC5.0
only 5 sigments are generated in the idocs. the three segments ( E1PISHO, E1PISIO,E1PISSO not generated).
after transaction executed it returns subrc 1001, msgid--> ME, MSGNO --> 218.
Thanks In Advance.
Ranjit.

Hi Atish and Nishant,
Thanks much for the immediate response.
1.Would like to know what is the mandatory data to be passed for PO creation in BDC table.
2. Is there any user exit or where the idoc creation happens during me21 execution.
I have verified the po in we02 , as before mentioned the three sigments are not getting created and i am not sure the reason.
Note: We didnot have any output configured in ECC 5.0 for this idoc to be created.
I am really not able to locate in debug mode FOR ME21, where this ekseks01 idoc getting created and triggered.
Appreciate your help.
Thanks in Advance.
Ranjit.

How to check for Web Srvice Timeout in ABAP Proxy call

I am calling a web service in my ABAP program using ABAP proxy. The code is as under:
TRY.
      y_v_request-mt_request-yaskkey   = y_l_matnr.
      y_v_request-mt_request-maktx      = y_l_maktx.
      y_v_request-mt_request-ymtart     = y_l_mtart.
      CALL METHOD y_v_prxy->execute_synchronous
        EXPORTING
          output = y_v_request
        IMPORTING
          input = y_v_response.
    CATCH cx_ai_system_fault INTO y_v_fault.
      y_v_message = y_v_fault->errortext.
ENDTRY.
y_l_ycod = y_v_response-mt_response-answer.
1. Is there is any way to know that the called web service has timed out ?
2. Is it possible to check for the time spent in the call if it is more then say 500 sec then it should be considered as timeout?
Any help will be appreciated.
Thanks in advance

Hi Subbu,
you can catch CX_AI_SYSTEM_FAULT.
DATA:   lo_sys_exception TYPE REF TO cx_ai_system_fault,
l_error_text type string.
CALL METHOD ...
CATCH cx_ai_system_fault INTO lo_sys_exception.
l_error_text = lo_sys_exception->errortext.
You can configure XI timeout parameter (for shure in SMICM / Parameter and, if i remeber right, as profile parameter in XI administration).
Regards,
Udo
Message was edited by: Udo Martens

Sender Abap Proxy no get in PI

Hi expert,
I have an sender abap proxy scenario which working fine in development server and even staging server but when transported to production server, the data seem can't go into PI server. I have check all the setting and sure the setting was set correctly. When i check on the system log in sm21 abap ERP, it show an error.
Operating system call gethostbyname failed (error no. 0 )
Any idea on how to solve this? Thanks.

Hi,
plz check transactions sldcheck and sldapicust. Everything ok?
What about SXMB_ADM? System maintained as Application System? Destination given to PI Runtime?
Can you ckeck that destination at SM59?
Plz have a look to destinations SLD_NUC and SLD_UC. Do they work?
Regards,
Udo

Messages getting stuck in QRFC Queue

Hi,
Today I noticed that a message had gotten stuck with the status "Sheduled for Outbound Processing" (scenario IDOC->XI->File), XI 3.0 SP11.
This in turn had the effect that the whole QRFC queue got stuck, and all following messages got stuck with status "Sheduled".
I had to remove the first message from the queue manually so that XI could start to purge the other messages from the queue.
What could be the reason for the first messages getting stuck with this status ("Sheduled for Outbound Processing")?
The message was very small, just a couple of lines. One thing that comes into mind, is that XI received 4 IDOCS for the same interface, within one second. These 4 messages were assigned to different queues, but one of them got stuck. Could there be problems with XI when several messages arrive on the same interface within a very short time?
Is it possible to use Alerts to detect this kind of problem in the future? As I have understood, Alerts only handle XI "errors", but according to XI, this message did not have an "error status", it just had the status "Sheduled for Outbound processing"..
Thanks for any help,
Hans

Hi,
If the message got struck in Queue, you try to activate the queues in smq2 to reprocess the data instead of deleting it. This is the final solution. But you should able to see a dump in ST22 for this problem.
thanks,
sasi

Web Service to ABAP Proxy, Calling RFC from ABAP Proxy

can any body send me the notes or Step by step process of Webserice of calling RFC using ABAP proxy, I am new to XI. send me detail process of this perticular scenarios

Hope this helps
/people/siva.maranani/blog/2005/05/23/communication-between-sap-system-webservice-using-proxies
also refer to
/people/shabarish.vijayakumar/blog/2006/03/23/rfc--xi--webservice--a-complete-walkthrough-part-1
/people/shabarish.vijayakumar/blog/2006/03/28/rfc--xi--webservice--a-complete-walkthrough-part-2
Rgds,
Kumar
Message was edited by:
Kumar

Async call gets stuck with pending status

Hi,
I am working on Tasklayer where need to invoke Async. call, the .bpel file has Invoke activity and below that it has pick activity with branches one for OnMessage and another is also OnMessage but, this is for fault. Now, when it invokes the Async. what i see in the instance is that the OnMessage activity gets stuck in Pending status, it doesn't proceed further. Kindly let me know if any one has faced similar issue.
Thanks & Regards,
Sanjay

Hi Sanjay,
you are saying that u r calling an asyc process.
So as an async process do not send the response back to parent through same port, you have to send the fault back to parent by invoking it(parent).
Here you can send the fault by using existing callback port otherwise you can define separate port for fault can send through that(you have to do it in WSDL).
So here for the first case no need to have the pick as u r getting both success and fault through same port. If you are going for separate one you have to have pick(one for success and other for faulted one)
So as Steven said you have to have a catch and invoke to send the fault back to parent.
Regards
PavanKumar.M

ABAP Proxy call gets stuck in qRFC

Similar Messages

Maybe you are looking for