Proxy scenario issue

Folks,
This is a simple scenario:
soap > PI > Proxy  (Sync)
now here is the deal, when pi receives the response from SAP, in the inbound message we are able to see only 1 row in the response.
now when a stand alone test is done @ sap , both from SPROXY and from the se37 we see many other rows as well.
Can some1 guide me on what steps/ line i need to be thinking in?
is this some cache related issue?

Hi Jovani,
Please check sxmb_moni in sap or ecc (not in pi) and see the message. Open the message and ask him to send that payload to his program. Also check whether they both are same or not. Please use this blog as reference:
/people/krishna.moorthyp/blog/2005/12/23/monitoring-for-processed-xml-messages-in-abap-proxy
He can put in debug mode and then can test end to end. So that when you send the data from xi it will stop at his debug point and from there can debug step by step till you see the response sending to xi.
Also debug the proxy using this stefans blog:
/people/stefan.grube/blog/2006/07/28/xi-debug-your-inbound-abap-proxy-implementation
Regards,
---Satish

Similar Messages

  • SOAP- Proxy scenario, issue with WS adapter

    Hi guys,
    i've set up a soap->abap proxy scenario (on 7.1) and want to use the new WS adapter. unfortunately I'm facing some issues. The proxy has been generated properly and I also set it up in soamanager. I tested it from XML Spy and it works fine. So there shouldn't be any problem with it.
    But when I try to run the scenario, I get following error:
    WS_ADAPTER_SYS_ERROR
    <sap:ExceptionChain xmlns:sap="http://www.sap.com/webas/710/soap/runtime/abap/fault/system/SystemFault"><sap:ChainedException><Exception_Name>CX_SOAP_FAILURE</Exception_Name><Exception_Text>SRT: Processing error in Internet Communication Framework: ("ICF Error when receiving the response: ICM_HTTP_CONNECTION_FAILED")</Exception_Text></sap:ChainedException><sap:ChainedException><Exception_Name>CX_SOAP_CORE</Exception_Name><Exception_Text>SRT: Processing error in Internet Communication Framework: ("ICF Error when receiving the response: ICM_HTTP_CONNECTION_FAILED")</Exception_Text></sap:ChainedException></sap:ExceptionChain>
    System error while calling Web service adapter: <sap:ExceptionChain xmlns:sap="http://www.sap.com/webas/710/soap/runtime/abap/fault/system/SystemFault"><sap:ChainedException><Exception_Name>CX_SOAP_FAILURE</Exception_Name><Exception_Text>SRT: Processing error in Internet Communication Framework: ("ICF Error when processing Web service
    I checked the /sap/xi/engine service on both - PI & ECC and it is activated.
    Any hint, what could be wrong?
    Thanks a lot,
    Olian

    Hi,
             "ICM_HTTP_CONNECTION_FAILED" this error is relaed to ICM. Does your Type H connection "INTEGRATION_SERVER_HMI" works fine.And check integration engine configuration in SXMB_ADM.
    And here is a similar thread.
    Re: HTTP to Enterprise Services.
    Regards,
    Reyaz

  • Issue in Iodc- abap proxy scenario

    Hi all
    I have a idoc to abap proxy scenario. The issue is ,
    when we send the idoc to client A of target system, it works ifne.
    But when we send the saem mesage to Client B, we find a error message in sxmb_moni of Target system. the mesage is Application_fault.
    Is it because of any error in XI configuration or somethin else.

    hi all
    thanks for all your responses.
    I forgot to mention that based on a particualr field value in the idoc , it will be routed to eihter Client 100 or 200 .
    I gave the conditions in Receiver Determination.
    Same Server Proxy  is used in both the target business sytems.
    I have done all the Configuration Steps ,( Created two separate business systems also )
    Also I have checked wiht all the system settings to be made in the target system B.
    When i trigger the idoc to Client 100, it goes to XI and then reaches  Client 100 of System B
    without any problem. I get the desired result from proxy code.
    When i send the saem idoc to Client 200, it reaches the target system and routed to client 200. But getting this error message in
    the Call Inbound PRoxy step. (from sxmb_moni)
    <SAP:Category>Application</SAP:Category>
      <SAP:Code area="ABAP">APPLICATION_ERROR</SAP:Code>
    Since it reaches the target system correctly, i guess there is nothing wrong in the XI configuration side.
    But if its Application fault, how come the same data is processed successfully in one client whereas it thorws error in another.

  • File to Proxy Scenario : Error in communication channel monitoring

    Hi,
    I have developed File to Proxy Scenario on PI 7.1 system and it is not working. I see the below error in communication channel monitoring.
    u201CError: com.sap.engine.interfaces.messaging.api.exception.ConfigException: Some of the IS access information is not available. SLDAccess property may be set to true, but SLD is not available.u201D
    File will be picked from the FTP server.
    I have created File system in SLD of type "Third Party", Can this be the issue?
    Please guide me on this.
    Thanks,
    Chandravadan

    Hi!
    Check if the tcode SLDCHECK is ok!
    Check note #764176.
    Also, refer to link below and execute each steps from the links there MANUALLY.
    Wizard-Based Configuration:
    http://help.sap.com/saphelp_nwpi71/helpdata/EN/45/2e4c1b16bb4aa8e10000000a11466f/frameset.htm
    Regards,
    Caio Cagnani

  • SOAP - Proxy Scenario

    In my SOAP to Proxy scenario I have a proxy that will return "true" or "false" depending on the logic in my method.  When I execute the proxy it returns the false value for cases that are false in SAP.  The scenario does not return the "true" value when the logic is true in SAP.  If I go into SAP and run the method, both the true and the false logic paths work and the method returns the correct value.  If I hard code the variable in the method to "test" and execute the XI scenario it will return the word "test" for both cases, true and false.  I have the same scenario in my XIQ system and it works fine. 
    So, what I have done...
    I have flushed the cache, that did not work.
    I have rebooted my XI system that has the problem.
    I have compared my XI broken system with the one that is working and there are no differences.
    Does anyone know how I can see what is truely being sent back to the SOAP side?  Is there a way to debug the ABAP code from the XI / SOAP side?
    Any help would be greatly appreciated.
    Thanks
    Skip Ford

    Hi Ford
    When you try with SAP its working right. Did you see that response in XI. If not then no need to touch XI.
    Take the payload and try to debug the proxy. You will come to know if it really returns the true value or there is a data issue itself and no problem with XI and SAP.
    Check in XI mapping as well. if the value from source is moving to target or not. If you make any changes or found problem do regenerate and activate proxy.
    Thanks
    Gaurav

  • SOAP to Proxy scenario communication error

    Hi Friends,
         Now i am developing SOAP to Proxy scenario,  i am testing WSDL file using SOAP UI software and i am getting an error in SOAP UI tool.
    <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
    <html>
    <head>
    <title>Error Report</title>
    <style>
    td {font-family : Arial, Tahoma, Helvetica, sans-serif; font-size : 14px;}
    A:link {color : #0059AA;}
    A:visited {color : #999999;}
    A:active {color : #999999;}
    </style>
    </head>
    <body marginwidth="0" marginheight="0" leftmargin="0" topmargin="0" rightmargin="0">
    <table width="100%" cellspacing="0" cellpadding="0" border="0" align="left" height="75">
    <tr bgcolor="#FFFFFF">
    <td align="left" colspan="2" height="48"><font face="Arial, Verdana, Helvetica" size="4" color="#666666"><b>  403   Forbidden</b></font></td>
    </tr>
    <tr bgcolor="#3F73A3">
    <td height="23" width="84"><img width=1 height=1 border=0 alt=""></td>
    <td height="23"><img width=1 height=1 border=0 alt=""></td>
    <td align="right" height="23"><font face="Arial, Verdana, Helvetica" size="2" color="#FFFFFF"><b>SAP NetWeaver Application Server </b></font></td>
    </tr>
    <tr bgcolor="#9DCDFD">
    <td height="4" colspan="3"><img width=1 height=1 border=0 alt=""></td>
    </tr>
      </table>
    <br><br><br><br><br><br>
    <p><font face="Arial, Verdana, Helvetica" size="3" color="#000000"><b>  Error: You are not authorized to view the requested resource.</b></font></p>
    <p><font face="Arial, Verdana, Helvetica" size="2" color="#000000"><b>  <a href="https://wiki.sdn.sap.com/wiki/x/wIN3Cw">SAP Technology Troubleshooting Guide</a></b></font></p>
    <p><font face="Arial, Verdana, Helvetica" size="2" color="#000000"><table>
    <tr>
    <td valign="top"><b> Details:</b></td>
    <td valign="top"><PRE>No details available.</PRE></td>
    </tr>
    </table></font></p>
    </body>
    </html>
    I have tried with the same WSDL earlier  it was working fine, now its not working and throwing the above error.
    Kindly suggest me to overcome from this issue.
    Regards,
    Senthil.

    Hi Senthil,
    Try with the authentication preemtive. Also, check your URL because that error seems that you are accessing to wrong PI section or your user has not the enough credentials, try with PIAPPLUSER or with the same roles that this user.
    Regards.

  • INTERNAL - AMF_ERROR in XML -- ABAP proxy scenario

    Hi Experts,
    Can any one help me to solve this following issue please, it is happening while I am executing the scenario between XML File to ABAP Proxy scenario.
    <?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">AMF_ERROR</SAP:Code>
      <SAP:P1>1</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:Stack>Error when processing message number 1 in package No object type found for the message. Check that the corresponding process is activated An exception has occurred.</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>.
    This XML message has got 5 Lines Header and more than 100 Lin Items, this kind of Header and Lin item message 3 to 4 in one XML, I am using multi mapping. Message mapping shows working fine, OM also shows working fine. BPM is splitting messages to send messages to ABAP Proxy on SNC 7.0. After I have done all with SDN experts support, still I am having the above issue. can any one experties might help to resolve this?
    I will appreciate your support.
    Thanks & Regards
    San

    Can you please explain the solution.
    Regards,
    Rashi

  • ABAP Application Error in Proxy scenario

    Hi All,
    I have a Proxy to Proxy scenario. I can see that few message are successful, whereas few are failing in ECC side. The messages are not stuck in Queue. It is giving a "ABAP" _APPLICATION ERROR. Has anyone faced this error before?
    Regards,
    Lavanya R

    Hi,
    Issue with Application end, Ask to developer to deebug the codu using the failed xml message.
    Regards
    srinivas

  • File to proxy scenario

    Dear one,
    I need a solution for my problem facing this moment.
    Here is the File to proxy scenario  explained.
    I created three new fields in XI IR to map three more  fields from File to CRM .On this line,I created three fields in IR and passed the updated file(containing three new filelds) and interfaced.Before that I had regenarated and activated CRM level proxy too.
    The file was red by XI and moved to CRM also.
    Now my problem is that I can see the three new fields in SXMB_MONI when I got into detail of that . But when I debug the CRM proxy the value for these three fields are not displaying over there .
    These three values are displayed in XML message but not in proxy ,why it is so?.
    Please help me out to resolve the issue.
    Swasthi,
    Karthik

    Hi Manjusha,
    Here is the reply:
    Is the issue with the fields , or the values in the fields ?
    Ans:Issue is with the values ,not with the fields .
    Is it that your proxy structure doesn't have the fields ?
    Ans:Proxy structure have the fields but not value.
    Can you check sxmb_moni in the CRM system if these fields with value appears.
    Ans:I checked in the CRM system
    <TOTL_INFO>
    <DT_INVOICE>
    <MT_Invoice>
    <ECOMM_VAT_BASIS_AMT>12</ECOMM_VAT_BASIS_AMT>
      <ECOMM_VAT_AMT>13</ECOMM_VAT_AMT>
      <ECOMM_CURR_CODE>GBP</ECOMM_CURR_CODE>
      </TOTL_INFO>
      </DT_INVOICE>
      </MT_Invoice>
    Both field and values are coming perfectly in XML message..
    You can see that above in last three fields (Field- ECOMM_VAT_BASIS_AMT , Value-12 and etc.).
    Only  values are not coming in proxy structure(table) ....fields are coming with no values
    Pls let us know yr views.

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

  • File to ABAP Server Proxy Scenario

    Hi 2 all,
    I am running File to Server(ABAP) Proxy scenario...
    I have checked the ABAP Server Proxy at application server only and it is working fine....But when i am running the whole scenario my server proxy is not getting executed..( i.e my file is being picked up but proxy is not getting called ..:(( )
    Can i expect some valuable inputs regarding this issue..?
    Regards,

    to debug the problem....
    first check SXMB_MONI of R3 system... where proxy has been created.
    1 .check whether your proxy has been called ... it will be evident you get any message in moni for you interface or namespace..
    2. check you proxy message has not got stucked in queue... sometimes message get stucked in queue and hence proxy are not called.. release the messaeg using smq2.
    ELSE
    1 .go to SXMB_MONI...of XI..
    2. select 'Call Adapter'  in right hand of monitor.
    3. check the 'trace' under Call Adapter.
    4. if you go at end of trace or somewhat near to end.. there should trace like...this ...
    Trace level="1" type="T">Receiver party normalized =</Trace>
      <Trace level="1" type="T">Receiver party external =</Trace>
    - <Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_XMB-CALL_XMS_HTTP">
      <Trace level="2" type="T">Addressing mode: destination</Trace>
      <Trace level="3" type="T">Destination = D67CLNT103_HTTP</Trace>
      <Trace level="3" type="T">Attributes of destination: D67CLNT103_HTTP</Trace>
      <Trace level="3" type="T">Type = H</Trace>
      <Trace level="3" type="T">Pipeline = ENTRY</Trace>
      <Trace level="3" type="T">Action = EXECUTE</Trace>
      <Trace level="3" type="T">Host = XXXXXXX</Trace>
      <Trace level="3" type="T">Port = XXXX7</Trace>
      <Trace level="3" type="T">Client = 103</Trace>
      <Trace level="3" type="T">User = XIAPPLUSER</Trace>
      <Trace level="3" type="T">Language = E</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="T">SSL not active</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="3" type="T">Creating HTTP-client</Trace>
      <Trace level="3" type="T">HTTP-client: creation finished</Trace>
      <Trace level="3" type="T">Serializing message object...</Trace>
      <Trace level="3" type="T">HTTP-client: sending http-request...</Trace>
      <Trace level="3" type="T">HTTP-client: request sent</Trace>
      <Trace level="3" type="T">HTTP-client: Receiving http-response...</Trace>
      <Trace level="3" type="T">HTTP-client: response received</Trace>
      <Trace level="3" type="T">HTTP-client: checking status code...</Trace>
      <Trace level="3" type="T">HTTP-client: status code = 200</Trace>
      <Trace level="3" type="T">Deserializing message object...</Trace>
      <Trace level="3" type="T">HTTP-client: closing...</Trace>
      </Trace>
    check whether connection establishment between XI and R3 is successful or not...
    if you are getting same message as above ,,that means ur RFC is working fine...
    problem is on r3 side.. for this go to r3 and check moni...

  • Help Required - File to Proxy (Performance Issue)

    Hi All,
         One of my file to proxy scenario is taking 3 to 4 days to execute.
    Basically XI picks up a file of 2-3 lakh records and pushing it to SAP via ABAP proxy. On the ABAP side, a BDC call is made to process the data. But the whole scenario takes 3 to 4 days for execution. 
    The scenario is an Asynch scenario and BPM is not used as its a very straight forward scenario.. Also the file can't be splitted as say each 10,000 records bcoz all of these records are interrelated and has to go to SAP end in a single shot.
    Is there anything which can be done on either XI or ABAP side to optimize the scenario?.
    Thanks,
    Joe.

    Joe,
    Can you give more details?
    Is this an Asynch call or a synch call?
    Are you using a BPM, etc, maybe there is something wrong in the way you have designed your interface.
    Proxies are supposed to provide the best perfromance and the fact that it is taking such a long time is really strange, and so maybe if you can give us details on your interface , some reason for this issue can be found out.
    Meanwhile also look into this guide,
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/70ada5ef-0201-0010-1f8b-c935e444b0ad
    Regards
    Bhavesh

  • SET_PAYLOAD_FAILED error in SOAP to Proxy scenario

    Hi PI Experts,
    We have an inbound syncronus interface (Non sap system to SAP) using the SOAP to Proxy scenario.
    When we test the interface using any soap tool like soapui it is working fine but when the interface is triggered end to end from source system then the below error is getting dispalyed on source system.
    500 Internal Server Error
    In XI below is the error message -
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Inbound Message
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:Category>XIProxy</SAP:Category>
      <SAP:Code area="ABAP">SET_PAYLOAD_FAILED</SAP:Code>
      <SAP:P1>IN</SAP:P1>
      <SAP:P2>REQUEST</SAP:P2>
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Internal error when completing the message object (setting the payload, direction: IN message: REQUEST)</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    Can any please let me know what is the issue here?
    Appreciate your help.
    Regards,
    Jitender

    We had a similar issue with a Synchronous Interface
    The interface worked perfectly when sending the request directly to the integration server, but when sending it using SOAP the issue appeared.
    It was very tricky to solve it because we had similar interfaces that worked without any issues.
    SOLUTION: Create a new Service interface with a new name different from the one failing. And make sure The Message Types are in the same namespace as the service interface.
    Why?:
    The issue turned out to be in the sender agreement, and name-spacing issues.
    Our Outbound Service Interface belonged to one SWCV and ns, We will call it "ns1:SI_A_OUT".
    In PI 7.3, and I believe 7.11 also, the you no longer assign a default interface in the to the SOAP communication channel sender agreement pair.
    Therefore the SOAP adapter determines the soap method from the payload. If The internal message type in the soap message belong to different namespace, the the java method  getMessage() does not find the correct XML node, therefore does not find the payload.
    <"ns1:SI_A_OUT">
    ...<ns2:MT_element>
    getMessage( ns1:MT_element)
    We are not sure if the issue is the implementation of the SOAP protocol or in the WSDL generation. But this issues seem to create orphan object during runtime, and even if you re-implement the complete interface, the sender agreement seems to be corrupt.
    Therefore the only was we could solve this, was to move our MT to the same namespace as the service interface and rename the interface "ns1:SI_A2_OUT"
    Hope this helps someone.
    Juan Francisco Zurita Duque
    NNIT A/S

  • Proxy acknowledgement issue

    Hi all,
    I have a Proxy-PI-Proxy scenario with acknowledgements(application acks) that I'm still testing.
    There's an interesting issue; in the PI and receiver systems, acknowledgement status gets updated
    after the receiver processes the message but in the sender system(SXMB_MONI), the message just sent gets stuck with "still waiting acknowledgment" status and is not updated.
    Any ideas?
    Thanks in advance.
    Regards,
    Gökhan

    hi Madhu,
    my blog that you mention does not have anything to do with proxy acknowledgments
    why did you bring it here?
    hi S. Gökhan Topçu,
    did you create ack as shown here:
    http://help.sap.com/saphelp_nwpi71/helpdata/en/f4/8620c6b58c422c960c53f3ed71b432/content.htm
    Regards,
    michal

  • File to Server Proxy Scenario

    Hi,
    I am working on ABAP (server)Proxy scenario. My servers are SAP PI 7.1 EHP1 and SAP ECC 6.0 running on HP-UX. I have gone through the Configuration steps for Proxy scenarios document. In that I found I need to create LCRSAPRFC and SAPSLDAPI RFC connections in ECC system and maintain the Program ID which is maintained in the J2ee Engine of ECC server.
    But my issue is - ECC system is running on only ABAP Engine.
    1. Can I configure Proxies with ECC systems which are running on only ABAP engines?
    2. I have ignored LCRSAPRFC and SAPSLDAPI steps and completed other configurations. I am able to see SWCV and Message Interfaces created in PI in ECC (SPROXY Transaction). Does this mean that I can ignore these 2 RFCs and go ahead with Proxy configurations?
    Thank you.

    >>I have ignored LCRSAPRFC and SAPSLDAPI steps and completed other configurations. I am able to see SWCV and Message Interfaces created in PI in ECC (SPROXY Transaction). Does this mean that I can ignore these 2 RFCs and go ahead with Proxy configurations?
    Why we need SM59 destinations SAPSLDAPI and LCRSAPRFC (on ECC) :
    LCRSAPRFC reads the exchange profile,
    SAPSLDAPI is used by the ABAP API.   Maintain the destinations as type T destinations to the registered server program with the program ID SAPSLDAPI. The program ID corresponds to the SLD data bridge.
    When using the destinations, the back-end system uses the parameters maintained in transaction SLDAPICUST.
    thanks
    BJagdishwar

Maybe you are looking for

  • No Printer Resolution Options for hp LaserJet Enterprise 600 M601

    Running under Mac OS 10.6.8, we've run into a problem printing separations to our new hp LaserJet Enterprise 600 m601 printer from Illustrator CS4, CS5 and CS6. In the printer dialog box, once under the "Output" section, with the mode set to either "

  • Critical stock as positive qty in LL01

    Hi Experts, could any of You pls help me to identify a reason for critical stock? There is positive qty in my certain storage type shown in LL01, even though the mterial qty is handled with TR - TI - material staging process based on requisition, usi

  • Laptop connects to wireless network via a WRT54G but it can't access internet

    I've got a WRT54G cabled to my desktop, I set up a WEP-secured wireless network for my laptop, and the laptop connects to the wireless network and receives a strong signal, but it can't get Internet access. I know the problem is not with the router b

  • Program to create Bank Statement

    Hi There is a program to create Bank statement, so that it can be used for Electronic Bank statement processiong FEBA... I am not able to recollect that program. Can any help me in this regard. Points assured Kalyan

  • Pro: SOAP to RFC, WSDL generation

    Hi Frnd, I  am getting problem in the WSDL Generation from the ID, When i generated it first time i was getting the following in the    Soap:address <soap:address location="http://vessxip01:8001/XISOAPAdapter/MessageServlet?channel=:BS_PWS:CC_PWS_Wei