Client proxy message strucked in ECC queues

Hi All,
I am working on Proxy interface. My interface is like below
ECC 6----
>PI (7.1) -
>File
I had done the entire configuration in ECC and PI for proxy activation. While testing the interface in ECC system messages processed successfully, but the message strucked in queues (SMQ2) in ECC system. If run the queue manually the message processed successfully to the PI.
Can you please tell any more configurations required?
Regards,
Ramesh

Hi,
The queue used for Proxy call is not registerd in ECC system. You need to register the queue to process successfully.
you will get the name of Queue from SMQ2 t-code and register it with t-code SMQR.
Thanks
Swarup
Edited by: Swarup Sawant on Aug 24, 2009 8:03 AM

Similar Messages

  • Client Proxy - Message waiting in queue

    Hi all,
    I have a client proxy in R3 that sends information to XI. I see in XSMB_MONI a green flag, but in the field "status queue" appears a yellow triangle with the message "Message waiting in queue".
    In Runtime Workbench I don't see any message.
    Any help? I have to activate the queue?
    Regards,

    Hi,
    Have u registered the queue in R3? If not....
    1.Go to SXMB_ADM(R/3)
    2. Go to Manage Queues and then
    3. Register All Queues.
    <a href="/people/sap.user72/blog/2005/11/29/xi-how-to-re-process-failed-xi-messages-automatically Failed Messages</a>
    Regards
    San

  • Screen output without connection to user, Message struck at inbound queue

    Chaps,
    I executed inbound proxy form PI 7.0, the message was struck in the inbound queue of ECC 6.0,
    with status text "Screen output without connection to user" then when I apply execute LUW then it is converted to
    "ThiSend:bad tm type /connection closed (no data)".
    when i test the same message from 'SPROXY' t.code, inbound proxy class was working fine.
    I came to know that when we call an ABAP program in side a proxy then it will throw same error what I got by checking the below url
    Message struck at inbound que in server proxy
    But in my proxy. I am just putting the data into z table and on some condition I am calling some other BAPI call.
    Here my doubt is calling the SUBMIT for other ABAP program is same as calling the BAPI call?
    because in the above thread clearly saying that don't use the other ABAP program in proxies. is the same case for calling the BAPI call into the proxy?
    In proxy, the logic is I am just simply reading the data from IS(integration server, PI7.0 SP 18) to ECC 6.0(SP14) if the row is not there the data is reading into table. If row is already there then it is stuck up in SMQ2 (inbound queue) of the ECC
    am I missing any basic things? please guide.

    But in my proxy. I am just putting the data into z table and on some condition I am calling some other BAPI call.
    Here my doubt is calling the SUBMIT for other ABAP program is same as calling the BAPI call?
    I too believe ..
    because in the above thread clearly saying that don't use the other ABAP program in proxies. is the same case for calling the BAPI call into the proxy?
    It is saying not suggestable...!!!! BAPI calls work perfectly !1
    In proxy, the logic is I am just simply reading the data from IS(integration server, PI7.0 SP 18) to ECC 6.0(SP14) if the row is not there the data is reading into table. If row is already there then it is stuck up in SMQ2 (inbound queue) of the ECC
    am I missing any basic things? please guide.
    Seems so,
    Lets try below things..
    1. Plz check the user is having auth to run the executable program in ECC.
    2. It seems that you are not using the proxy structures in a correct way..and check the calling program also..!!
    Edited by: Santosh Rawat on Jul 30, 2009 1:12 PM

  • ABAP Proxy - Message prioritizing in ECC

    Dear Experts,
    Can you provide me any document to prioritize the proxy messages in Application Engine (ECC - SMQ2). I've already gone through the document for Integration Server but I need the one more specific for the Application Engine and more details like configuring specific queue sets for individual interfaces. Please help.
    Thanks,

    Hi,
    The queue used for Proxy call is not registerd in ECC system. You need to register the queue to process successfully.
    you will get the name of Queue from SMQ2 t-code and register it with t-code SMQR.
    Thanks
    Swarup
    Edited by: Swarup Sawant on Aug 24, 2009 8:03 AM

  • Client proxy message not reaching to XI system

    Hi
    I have done one scenario from CRM to FILE. When i am executing the client proxy through my zprogram its executing without any errors. I have checked in SXMB_MONI of CRD system i can see the messages but they are not with successful flag or not with error flag. But in XI system (SXMB_MONI) i didnt find any messages. Could you please tell me what's the problem is?
    Regards
    Sowmya

    Sowmya,
    As you are not getting any message in SXMB_MONI, there can be following possibilities:
    1. There can be some problem in proxy configuration on your CRM system. Please check with your BASIS team that steps give in this blog are properly followed:
    How do you activate ABAP Proxies? 
    2. Make sure that in
    SXMB_ADM     --->integration engine config -
    >change specific attributes....
    The RUNTIME parameter is defined LOGGING and TRACE_LEVEL and the value is 1.
    3. Make sure the queues are registered in Tx: SMQR.
    Further, I do not think that COMMIT statement or anything like that is missing as in that case you should have got a message in SXMB_MONI with a green flag stating that "Commit statement is missing".

  • ABAP Client proxy message not reaching AAE

    Hi Experts,
    I am facing a strange issue in one of my proxy interfaces. ABAP client Proxy is used to post message to AAE in SAP PI 7.3. The messages are being generated and pushed out of ECC successfully. I can see them in the SXMB_MONI t-code with checkered flag. These messages are reaching the Integartion Engine instaed of the Adapter Engine.
    I have configured the following:
    1. Sender / Receiver ID  in SXMSIF:
    2. Configured the corresponding Runtime parameter in SXMB_ADM
    I have few other such ABAp client proxy i/f's which work fine and their message are being sent to the Adapter engine. Howveere, only this one interface is posing a problem. What can be the issue?
    Please advice.
    Thanks in advance.
    Elizabeth.

    Hi Elizabeth,
    It will be great if you could please let me know all the user profile configured in userID of Logon&Security tab of SM59 for connecting ECC system to post the message via AAE.
    I have used
    SAP_XI_APPL_SERV_USER
    SAP_XI_DEVELOPER_J2EE and
    SAP_XI_IS_SERV_USER
    profiles in my UserID for Basic authentication.
    Currently I am doing the same scenario what you have done with integrated configuration.The message is getting failed in ECC with 403 Forbidden error.
    Please help me.
    Thanks
    Ray...

  • Need to raise an Alert for huge Volume of messages struck in the queue

    Dear All,
    I have a query which is mentioned below.
    The Partners send huge number of volume of messages at a time to PI Server and due to this reason,the messages are getting struck up in the inbound/outbound queue.Everytime the user manually check for the struck up messages and reprocess it.
    Example: One Partner sends  50,000 number of ORDERS at a time.
    Now an alert needs to be raised for those messages which  got struck up ( i.e. messages on hold and "not failed") in the queue.
    Please share your inputs /suggestion.
    Warm Regards
    B.Dheepa

    Hi,
    Else you can implement the Logic in this blog
    XI :  How to Re-Process failed XI Messages Automatically
    You can Schedule the Strandard Reports to release  automatically the Strucked messages in Queues
    Regards
    Seshagiri

  • ABAP Client proxy - IF_WSPROTOCOL_ASYNC_MESSAGING

    I have a question regarding the value for the attribue ASYNC_MESSAGING. In every client proxy, this attribute is defaulted to IF_WSPROTOCOL_ASYNC_MESSAGING. (inherits the value from IF_WSPROTOCOL).
    Does that mean that the client ABAP proxy uses EOIO ? If so, how do you change it to EO?
    If the change of QoS from EOIO to EO is not possible, would creating custom queues and using the SERIALIZATION CONTEXT to specify the custom queue help me alleviate issues with stuck EOIO queues on the sender/receiver sides while using proxy? Since the QoS is determined by the sender, I would assume that if there is way to set it on the Sender client proxy, that would prevent the queues from stopping processing if a message fails. In my case, I am not too concerned about preserving the sequence of the messages.
    Any input will be appreciated.
    Thanks
    Sridhar

    Hello Sridhar,
    I'm not sure if I understand your question right, but I think following applies : ABAPProxy client (SAP sends data to SAP PI) behaves as EO by default. And if one needs to have messages to be delivered to the destination system in order, you need to "tell" this to SAP PI, when you send the data from ABAPProxy client. Thats the case you need include coding as mentioned here: http://help.sap.com/saphelp_nw04/helpdata/en/65/40c9a4a1fa476288ac61b5fcc6bbde/frameset.htm.
    Please note, that for WAS 620 ABAPProxy client another routine applies. For more information see the link: http://help.sap.com/saphelp_xi20sr1/helpdata/en/02/265c3cf311070ae10000000a114084/frameset.htm
    Regards
    Tomas

  • Error in Synchronous client proxy

    Hi Gurus,
    I have created a scenario in which I am using client proxy at source side (ECC ) and soap at target side.
    Its a synchronous scenario for which I have written an abap report.This interface sends a company name and uses a webservice to fetch the stock value of that company.
    I am a beginner in abap, so I am unable to to know the reason why is it showing the following error when I am executing the code.
    Method "EXECUTE_SYNCHRONOUS" is unknown or PROTECTED or PRIVATE.
    This error is coming at line :
    CALL METHOD Proxy->execute_synchronous
    Following is the code :
    REPORT  ZSYNC_PROXY_STOCKQUOTE NO STANDARD PAGE HEADING.
    DATA Proxy TYPE REF TO ZCO_SI_SOURCE.
    CREATE OBJECT Proxy.
    DATA: t_company_name TYPE zsource_request_mt,
           t_stock_value TYPE zsource_response_mt.
    SELECTION-SCREEN: BEGIN OF BLOCK B1.
    PARAMETER: p_id TYPE String.
    SELECTION-SCREEN: END OF BLOCK B1.
      START-of-selection.
      TRY.
        t_company_name-Source_Request_MT-Company_name = p_id.
        CALL METHOD Proxy->execute_synchronous
        Exporting
          output = t_company_name
       IMPORTING
         input = t_stock_value.
       WRITE: t_stock_value-Source_Response_MT-stock_value.
       CATCH cx_ai_system_fault.
         DATA fault TYPE REF TO cx_ai_system_fault.
         CREATE OBJECT FAULT.
        WRITE:/ fault->errortext.
        ENDTRY.
        END-OF-SELECTION.

    Hi,
    You have wrongly assigned the method. It should not be pointing to Execute method.
    it should be something like below
    TRY.
               CREATE OBJECT proxy.
               CATCH cx_ai_system_fault.
      ENDTRY.
    TRY.
        CALL METHOD Proxy->  " GIVE THE OUTBOUND SERVICE INTERFACE NAME HERE"
        Exporting
          output = t_company_name
       IMPORTING
         input = t_stock_value.

  • ABAP Client Proxy from ECC 6.0 to XI message irregular recieving

    Hi Gurus
    Any one has come across issue whereby the ECC 6 system trigger ABAP Client proxy to SAP PI 7.0. The first time the PI is able to recieve it in the SXI_MONITOR. But subsequent trigger from the ECC 6.0 system the SAP ABAP program to trigger the Client Proxy, the PI seem to lost connectivity and did not recieve any message. This is pretty strange and hopefully someone in SDN and enlighten me.
    Thanks
    Regards
    On behalf of malcolm

    Hi Santosh
    I went to SMQR and register the queue, but it still did not reflect the locked queue when i trigger the ECC 6 to SAP PI 7.0. The green flag - schedule still appear in the SXMB_MONI queue. But i am quite puzzle as why the ABAP client proxy after sending message the first time and second time, the third time it stuck? And also it is not practical to everytime go to the SMQ1 or SMQ2 to unlock the queue. I don't think it a good solution for solving my problem, it is just a temporary solution.

  • Message struck at inbound que in server proxy

    Sub :Message struck in SMQ2 with status text"ThiSend:bad tm type" .
    HI,
    I executed inbound proxy form PI 7.0, the message was struck in the inbound queue of ECC 6.0,
    with status text "ThiSend:bad tm type /connection closed (no data)".
    when i test the same message from 'SPROXY' t.code, inbound proxy class was working fine.
    I came to know the message scheduled due to function
    module sxms_async_exec
    and raising an exception as ThiSend:bad tm type/
    connection closed (no data)
    please provide the details like when this function
    module throw an exception as connection closed(no data).
    inside inbound proxy,
    could you please suggest us, what should be avoided inside the proxy
    method.
    warm regards
    mahesh.

    Hi Chaitanya,
                       previouly, i have the same problem.
                       At that time, we are using 'submit' command inside proxy method i.e i ABAP program.
                         because of that, the message was struck in the inbound que.
                       'submit' is not suggestable inside proxy method.
                       so, pls check your ABAP Program.
    warm regards
    mahesh.

  • Proxy messages are stucked in SMQ2.Can I pass these msgs in separate queue?

    Hi Guys,
    File >PI>ABAP proxy. (ECC)
    Once i pick and process the file, the resultant message is updating the table in ECC through ABAP proxy. These messages are high priority and they should not stuck in the queues in ECC.
    The problem is some of the messages of this interface are getting stucked in queues (SMQ2) by colliding with other low priority messages which are failed due to some data issues.
    Is there any way I can separate these high priority messages into separate custom queue and process them?
    Do I need to this in ECC or PI?
    Thanks
    Deepthi

    Hi,
         As Debashis has already said, use message prioritization in PI to handle your requirement.
    For SAP NetWeaver PI 7.0, navigate to SAP NetWeaver 7.0  SAP NetWeaver 7.0 Library  SAP NetWeaver Library  SAP NetWeaver by Key Capability  Process Integration by Key Capability  SAP NetWeaver Exchange Infrastructure  Runtime  Integration Engine  Prioritized Message Processing.
    For SAP NetWeaver PI 7.1 (including EHP 1), navigate to SAP NetWeaver  SAP NetWeaver PI/Mobile/IdM 7.1  SAP NetWeaver Process Integration 7.1 Including Enhancement Package 1  SAP NetWeaver Process Integration Library  Function-Oriented View  Process Integration  Integration Engine  Prioritized Message Processing.
    For more details about message prioritization within the Advanced Adapter Engine, please refer to SAP Help Portal http://help.sap.com, and navigate to SAP NetWeaver  SAP NetWeaver PI/Mobile/IdM 7.1  SAP NetWeaver Process Integration 7.1 Including Enhancement Package 1  SAP NetWeaver Process Integration Library  Function-Oriented View  Process Integration  Process Integration Monitoring  Component Monitoring  Prioritizing the Processing of Messages.

  • File to Proxy scenario message failed in ECC with staus SYSFAIL

    Hi All,
    We are working on File to proxy scenario,  PI  able to send message successfully to ECC, but  In ECC , message got  stuck in queues with the status 'SYSFAIL',
    when I read the error message it is showing Address Invalid.
    when I run the LUW, it is giving 'Function module does not exist or EXCEPTION 'raised message.
    I'm using PI 7.1 EHP1 , ECC 6.0, can anyone suggest the trouble shooting guidelines for this issue?
    Thanks,
    Venu.

    when I run the LUW, it is giving 'Function module does not exist or EXCEPTION 'raised message.
    in your code, there seems to be an invalid statement.
    check the proxy code.

  • Messages strucking in Receiver ECC

    Hi,
           I have a scenario i.e. non-SAP to PI to SAP ECC. In that, in PI we are getting Successful flags on every monitoring, but data is not inserting in ECC tables, due to Queues strucked in ECC (smq2) and we can see those messages with status scheduled in SXMB_MONI tcode in ECC system. Means messages are strucked in Queue. Some times In production environment it is giving very critical issue. Here I have a doubt. Between PI and ECC only one Queue is available or multiple?  If one message struked in Queue remaining all the messages also be strucking. If only one queue is avail between PI and ECC, Is there any other way to increase number of Queues to overcome this problem.
    Thanks & Regards,
    Srihari.

    Hi Srihari ,
    Every R/3 system will have the concept of queue.
    If the messages are passed successfully from PI and are stuck up in ECC means there might be some data issue with the first failed message in queue. you can save that message using save LUW and then thus releasing rest of messages from queue.
    even if you increase number of queues on ECC , queue stuck still can be a issue. Only way is to remove problamatic message from queue and clear the queue. lateron you can investigate on error message .
    Regards,
    Sheetal

  • Async ABAP Client Proxy Queuing

    Hi all,
    We've successfully set up an asynchronous ABAP client proxy on a WAS 6.20 instance to connect to our XI 3.0 box.  Our concern is if XI is down the messages won't get queued up for delivery.  As I understand it, failed messages won't get queued up for delivery if a delivery error occurs.  Is this correct?  If queuing is not possible with a standard WAS 6.20 installation, what options do we have to make queuing possible?
    Many thanks,
    --jtb

    I believe queuing should be supported on a WAS 6.20 system so long as you have installed APPINT 200_620 (XI 2.0 add-on), SL 6.  You need level 6 in order to communicate with XI 3.0 (or at least that's how I understand it).  This above mentioned add-on is a basically the ABAP side of a 2.0 integration server.  In our scenario we set the role of the business with the 2.0 add-on as an application server.

Maybe you are looking for