"SOAP:Fault" in scenario with ABAP proxy client

Hello,
I realized the scenario CRM40_Basis620(ABAP proxy client)->XI->File.
XI:
The sender communication channel is a XI adapter (Parameters: HTTP 1.0, XI 3.0, Integration Server, Security profile unchecked, Security level - HTTP).
CRM:
The proxy generation is ok.
SLDCHECK is ok.
All RFC destinations are ok.
APPINT_200_620 for CRM was installed and configured well (I think so, but...).
When I ran the ABAP proxy client on CRM, sxmb_moni(CRM) returned the text for the XML Message (Display-CallIntegrationServer-Payloads-TraceDocument):
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <SAP:TraceHeader xmlns:SAP="http://sap.com/exchange/MessageFormat">
<Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />
<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 = EST</Trace>
<Trace level="1" type="T">client = 300</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = BABKIN_RA</Trace>
<Trace level="1" type="Timestamp">2007-08-06T13:55:12Z</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />
- 
<Trace level="1" type="T">Message-GUID = DC4424A659314CF18F500002A541D0E7</Trace>
<Trace level="1" type="T">PLNAME = SENDER</Trace>
<Trace level="1" type="T">QOS = EO</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC" />
- 
<Trace level="1" type="T">Get definition of external pipeline = SENDER</Trace>
<Trace level="1" type="T">Get definition of internal pipeline = SAP_SENDER</Trace>
<Trace level="1" type="T">Generated prefixed queue name = XBTS0004</Trace>
<Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Going to persist message + call qRFC now...</Trace>
<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
<Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC</Trace>
<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- 
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Starting async processing with pipeline SENDER</Trace>
<Trace level="1" type="T">system-ID = EST</Trace>
<Trace level="1" type="T">client = 300</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = BABKIN_RA</Trace>
<Trace level="1" type="Timestamp">2007-08-06T13:55:12Z</Trace>
<Trace level="1" type="T">----
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC">
<Trace level="1" type="T">Get definition of pipeline PID= SENDER</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
- <Trace level="1" type="B" name="PLSRV_CALL_INTEGRATION_SERVER">
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- 
- <Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_XMB-ENTER_PLSRV">
<Trace level="1" type="T">URL for integration server read from global configuration</Trace>
<Trace level="1" type="T">URL= http://SRMDEV.oao.sng:8011/sap/xi/engine?type=entry</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-SET_TECHNICAL_ROUTING_PROPERTY" />
- <Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_XMB-CALL_XMS_HTTP">
<Trace level="1" type="System_Error">HTTP-client: error response= <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"> <SOAP:Header> </SOAP:Header> <SOAP:Body> <SOAP:Fault xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"><faultcode>SOAP:Client</faultcode><faultstring>Error during conversion of XI message</faultstring><faultactor>http://sap.com/xi/XI/Message/30</faultactor><detail><SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1"><SAP:Category>XIServer</SAP:Category><SAP:Code area="SECURITY">INBOUND_SECURE_LEVEL</SAP:Code><SAP:P1>DC4424A659314CF18F500002A541D0E7</SAP:P1><SAP:P2/><SAP:P3>HTTP</SAP:P3><SAP:P4/><SAP:AdditionalText/><SAP:ApplicationFaultMessage namespace=""/><SAP:Stack>Message DC4424A659314CF18F500002A541D0E7 was sent with ''. Channel configuration, however, requires 'HTTP' </SAP:Stack></SAP:Error></detail></SOAP:Fault> </SOAP:Body> </SOAP:Envelope></Trace>
</Trace>
<Trace level="1" type="System_Error">Exit XMB because of system error!</Trace>
<Trace level="1" type="System_Error">System-Error: HTTP.HTTP_STATUS_CODE_NEQ_OK</Trace>
<Trace level="1" type="System_Error">HTTP status code 500 : Error during conversion of XI message</Trace>
<Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />
</SAP:TraceHeader>
I think the main problem is the parameter "HTTP Security level" for the channel, but not sure.
Does anybody know where to find a solution?
Regards,
Roman

Hi Roman
There is no need for an XI adapter for client proxy.... we only use that for server proxies.
Vaibhav

Similar Messages

Send message with abap proxy client

I'm trying to send message to XI, but no message in sxmb_moni.
I have created logical port with LPCONFIG.
ABAP code
REPORT Z_HTTP_SEND.
DATA:
* Reference variables for proxy and exception class
lo_clientProxy     TYPE REF TO ZPCO_MI_COMPANY_OB,
lo_sys_exception   TYPE REF TO cx_ai_system_fault,
* Structures to set and get message content
   ls_request         TYPE ZPMT_COMPANY_ID,
   ls_response        TYPE ZPMT_COMPANY_DETAILS.
*Complete the structure ls_request for the request message.
*DATA: zmt_id type ZPMT_COMPANY_ID,
*zdt_id type ZPDT_COMPANY_ID,
*z_id_tab type ZPCOMPANY_ID_TAB,
*z_id type ZPCOMPANY_ID.
*z_id-COMPANY_ID = '3000'.
*append z_id to z_id_tab.
* zdt_id-RECORD = z_id_tab.
*zmt_id-MT_COMPANY_ID = zdt_id.
DATA tab TYPE ZPCOMPANY_ID_TAB WITH HEADER LINE.
tab-COMPANY_ID = '3000'.
APPEND tab.
ls_request-MT_COMPANY_ID-RECORD = tab[].
TRY.
* create proxy client
*CREATE OBJECT lo_clientProxy( u2018LOGICAL_PORT_NAMEu2019 ).
    CREATE OBJECT lo_clientProxy.
* do synchronous client proxy call
    CALL METHOD lo_clientProxy->execute_synchronous
             EXPORTING output = ls_request
             IMPORTING input   = ls_response.
    CATCH cx_ai_system_fault INTO lo_sys_exception.
*   Error handling
ENDTRY.
Any ideas? Thanks very much,

Hi,
Proxies communicate with the XI server by means of native SOAP calls over HTTP .RFC does not, so you have to convert from SOAP to RFC calls and vice versa. So XML conversion is required.
ABAP Proxies uses Webservice and Http Protocols. And if you use RFC it is mainly meant for Sync. call. But Proxies is used for both Sync and Async.
If you use ABAP Proxy , you can reduce the overhead calling the function again and again.
How do you activate ABAP Proxies? - Activate Proxy
ABAP Server Proxies - ABAP Server Proxy
ABAP Proxies in XI(Client Proxy) - ABAP Client Proxy
Re: JDBC Sender select/update problem
If u generate proxy for outbound interface then its client proxy and for inbound interface its server proxy.
In client proxy u can call the method to send messages but u can't modify it but in server proxy its possible to write a user code within the method to execute proxy.
CLIENT PROXY:
A WSDL description from a UDDI server (or an Internet page) is usually used to make a service executable in the Internet and to describe the interface of this service. You require a client proxy and not a server proxy to call this service by using the Web service infrastructure.
SERVER PROXY:
You can only generate ABAP server proxies from a WSDL description if they originate in the Integration Repository.You can also generate server proxies for Java and client proxies for ABAP from message interfaces.
s refer these doc about ABAP proxy ..
How do you activate ABAP Proxies? - Activate Proxy
ABAP Server Proxies - ABAP Server Proxy
ABAP Proxies in XI(Client Proxy) - ABAP Client Proxy
Re: JDBC Sender select/update problem
ABAP Server Proxies
How do you activate ABAP Proxies?
ABAP Proxies in XI(Client Proxy)
File to R/3 via ABAP Proxy
http://help.sap.com/saphelp_nw2004s/helpdata/en/48/d5a1fe5f317a4e8e35801ed2c88246/frameset.htm
http://help.sap.com/saphelp_nw04s/helpdata/en/ba/f21a403233dd5fe10000000a155106/frameset.htm
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/41e08c90-0201-0010-9197-d8774336ea78
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f0ae9874-109c-2910-f48a-e91f0cdd1c81
Smarter Approach for coding ABAP Proxies
regards,
Surya

Is Asynchronous ABAP proxy client possible without XI ?

Hi there,
Does anyone of you know if it is possible to create an asynchronous ABAP proxy client, without XI, thus directly in a SAP ERP 60 ABAP ?
Karim

Hi Anton,
thanks for your answer, it confirmed what I was thinking (asynchronous not possible in that case).
Now this leads me to a second question:
I would like to implement the scenario "acknowledge only and receive full answer later".
As you indicate: "...additionally to your webservice client you have to provide a webservice, which the receiver calls once it completes your request..."
In order to do this, I must practice as follows:
The service I call is using the WS-Addressing specifications.
Therefore, the information regarding the webservice that will be called when the request is completed should be sent as a special SOAP WS-addressing parameter, that should be indicated in the header of the SOAP Message, here is an example:
(001) <S:Envelope xmlns:S="http://www.w3.org/2003/05/soap-envelope"
                xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing">
(002)   <S:Header>
(003)    <wsa:MessageID>
(004)      uuid:6B29FC40-CA47-1067-B31D-00DD010662DA
(005)    </wsa:MessageID>
(006)    <wsa:ReplyTo>
(007)      <wsa:Address>http://business456.example/client1</wsa:Address>
(008)    </wsa:ReplyTo>
(009)    <wsa:To>http://fabrikam123.example/Purchasing</wsa:To>
(010)    <wsa:Action>http://fabrikam123.example/SubmitPO</wsa:Action>
(011)   </S:Header>
(012)   <S:Body>
(013)     ...
(014)   </S:Body>
(015) </S:Envelope>
You can see that the WS-A specific part is in the header of the SOAP Message, not in the body, so not covered by the WSDL.
Question: Is it possible to include this in the header of the SOAP Message generated by the ABAP proxy client ???

Fault message in asynchronous ABAP Proxy

Hi,
I have a question about fault messages in asynchronous ABAP proxy server.
The configured scenario is SOAP XI ABAP Proxy. Between XI and the ABAP Proxy I have configured an inbound asynchronous interface with a fault message, and then I have generated all the classes and implemented some code for exception handling in the ABAP Proxy side successfully.
When I tested negative cases, the exception raises and it is visible in the SXMB_MONI transaction in the R/3 side, but this exception is not displayed in the SXMB_MONI of XI it just displays a successful delivery to the ABAP Proxy message.
According the XI documentation it says <i>In the asynchronous case, you can see a fault message in the monitoring of the Exchange Infrastructure.</i> But this is not working.
Am I missing something?

Hi,
This parameters are form group RUNTIME.
Please check it:
http://help.sap.com/saphelp_nw04/helpdata/en/d6/49543b1e49bc1fe10000000a114084/content.htm
Regards,
Wojciech

Missing asyn abap proxy client message in ECC

Hi,
I have a asyn scenario which an abap program will send data from ECC to PI using abap proxy client. My problem is i notice some of the message was no send to PI. Checked in PI SXMB_MONI no message was found. Any idea where the message was stuck? I check on smq1 in ECC also found nothing in the queue.
Thanks.

Hi ,
KIndly check with the abap program if its thrwing any dump . If every thing is fine with ABAP program then might be its issue of RFC destination . check with transaction SPROXY are u able to connect and your sender interface is reflecting there if yes then double click on your interface open the proxy andthen click on GOto and click on connection test if nay issue is in connection then it will display the error here .might be some rfc DESTINATION is missing or authnetication error .
Regards,
Saurabh

ABAP proxy client sending to XI by using the WEB Service

Hi
I have scenario where ABAP Proxy need to send the data by calling a web service middleware as SAP XI/PI,
Can anyone please provide the details of the scenarion that ABAP Proxy calls the webservice to send the data and receive it back the response, (Synchronous communication)
Thanks
PR

Hi PR
My understanding of your requirement is like
Proxy <-> XI <-> SOAP.
Steps.
1. Create Client proxy to send data to XI
2. Import the WSDL provided by receiver system in XI
3. Do IR steps
4. ID - SA is not required
5. Configure Receiver SOAP adapter using the URL and Soap Action from the WSDL you received.
Thanks
Gaurav

Catching and rethrowing a SOAP Fault from an OSB 11g Proxy service

Hello,
We have a chain of proxy services (that last one of which calls a business service) in our 11.1.1.6 OSB project. At one of the lower levels, we successfully throw a fault like this:
<soapenv:Body xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Fault xmlns:soap="http://www.w3.org/2003/05/soap-envelope">
    <soap:faultcode>SOAP-ENV:Client</soap:faultcode>
    <soap:faultstring>Non-Existent User</soap:faultstring>
    <soap:faultActor>Client who consumed this Web Service operation</soap:faultActor>
    <soap:detail>
      <sc:UserNonExistentFault xmlns:sc="http://xmlns.sc.com/Services/V1">
        <sc:CustomerNumber>12345</sc:CustomerNumber>
      </sc:UserNonExistentFault>
    </soap:detail>
</soap:Fault>
</soapenv:Body>
In the proxy service which calls this proxy service, I tried to catch this fault in an Error Handler so that I could confirm that it's available for me to re-throw back up the chain. Curiously, the proxy service which calls that proxy service cannot see that fault. But rather it sees what appears to be an OSB-overridden fault:
<con:fault xmlns:con="http://www.bea.com/wli/sb/context">
<con:errorCode>BEA-380000</con:errorCode>
<con:reason>com.bea.wli.sb.pipeline.PipelineException</con:reason>
<con:details>
    <err:ErrorResponseDetail xmlns:err="http://www.bea.com/wli/sb/errors">
      <err:response-metadata xsi:type="sb:SBResponseMetaDataXML" xmlns:sb="http://www.bea.com/wli/sb/transports/sb" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
        <tran:headers xsi:type="sb:SBResponseHeadersXML" xmlns:tran="http://www.bea.com/wli/sb/transports"/>
        <tran:response-code xmlns:tran="http://www.bea.com/wli/sb/transports">1</tran:response-code>
        <tran:encoding xmlns:tran="http://www.bea.com/wli/sb/transports">utf-8</tran:encoding>
      </err:response-metadata>
    </err:ErrorResponseDetail>
</con:details>
<con:location>
    <con:node>PipelinePairNode</con:node>
    <con:pipeline>PipelinePairNode_request</con:pipeline>
    <con:stage>GetCustomerByNumber</con:stage>
    <con:path>request-pipeline</con:path>
</con:location>
</con:fault>
I have tried printing out the values of $body, $fault, $outbound and $inbound from the calling proxy service's Error Handler just to see if our <sc:UserNonExistentFault> is nested anywhere therein. Unfortunately, it is nowhere to be found.
How can we force OSB to NOT override our faults with OSB-framework faults and, instead, just throw our custom fault all the way up the chain and back to the consumer?
Thank you,
Michael

I think I figured this out.
In proxyService-2, build the <soap:Fault> and assign it to the body, then Reply with Failure (as you mentioned above).
When proxyService-1 receives this, it will still be in the $body variable. But the $fault variable is now populated with a BEA-38000 error. It seems that as long as the $fault variable has data in it, then the OSB system will throw that instead of my fault (ignoring the <soap:Fault> I put into the body).
So what I did was to Delete the $fault variable in the error handler of proxyService-1, then Reply with Failure (again).
It would seem as if the inner workings of OSB has some logic like:
if $fault is not null, throw the BEA-####### fault. Otherwise, return the contents of the $body.
By removing the fault, I effectively got to that "else/otherwise" condition.
Of course, the Reply with Failure is still needed to ensure that an HTTP 500 error is passed with the fault (per the SOAP specification).
Cheers!
Michael

Abap proxy client and https webservice

Hi, I have a problem with an abap proxy client.
This proxy works perfectyl when I call the test webservice (via HTTP protocol) but it does not work if I try to call the productive webservice (via HTTPS protocol). Of course I have configured LPCONFIG in order to let the proxy point to the correct web site.
I'm pretty sure that problkem is caused by different protocols HTTP vs HTTPS.
I thought the problem could be the web site certificate, so I added it into the PSE (transaction STRUST) but nothing happnes.
Your help is really appreciated.
Edited by: robcom69 on Feb 22, 2010 3:34 PM
Edited by: robcom69 on Feb 22, 2010 3:35 PM
Edited by: robcom69 on Feb 22, 2010 3:49 PM

I have loaded the certificate in the TRUST transaction.
Anyway, in our system we do not have the SAPCRIPTOLIB libraries and I do not underastand if they are necessary or not.
I mean, I need these libraries only if I expose an HTTPS server from SAP or even if SAP is the client and it need to access an external https webservice ?
Please help.

Can we edit SOAP Header for an Outbound ABAP Proxy message?

Hi,
Can we add some information such as dynamic configuration to the SOAP header for the outbound ABAP Proxy from ABAP report in SAP Application System?
Regards,
Praveen Gujjeti.

Hi Praveen, have you found soulution for this? Can you share it with me?
From here http://help.sap.com/saphelp_nw70/helpdata/EN/d6/49543b1e49bc1fe10000000a114084/content.htm
The help described that:
Set logging in the message header. This means that this message is logged even if logging is deactivated explicitly in the configuration. The logging information is part of the message header:
¡ <SAP:Logging>1</SAP:Logging>
Activates logging explicitly.
¡ <SAP:Logging>0</SAP:Logging>
Deactivates logging explicitly.
So it means that we can edit SOAP header for outbound ABAP proxy. But i haven't find the correct method to do that.

File to Web service (SOAP) to File scenario with out BPM in PI 7.1

Hi All,
I have scenario File to Web service (SOAP) to File scenario with out BPM.i am getting the below error:
1) Error MP: unexpected exception caught com.sap.aii.af.service.cpa.impl.exception.CPAObjectKeyException: Value of key must not be null: ObjectId
2) Error ROB: error during processing: com.sap.aii.af.lib.mp.processor.ModuleProcessorException: Processing Error
PI server is 7.1 with SP:8
I have configured the scenario like this
1) 2 File channels - Sender & Receiver ,1 RFC channel - Receiver. We need to note that, the additional Module parameters need to be added only for sender File channel
2) Created Sender Agreement
3)Created Receiver Determination
4)Created Interface Determination
5)Created Receiver Agreement
Regards,
Ramesh

Hi,
Thanks for your reply!!
My Scenario is File to SOAP to File.
Configred modules in Sender channal below:
Prcessing sequence:
Number       Module Name                                        Module Key
1..........       AF_Modules/RequestResponseBean.......1
2..........       CallSapAdapter..........................................2
3..........       AF_Modules/ResponseOnewayBean.......3
Module Configuration:
Module Key                                       Parameter Name                                       ParameterValue
1                                                        passThrough                                            true
3                                                        receiverChannel                                       receiverChannel name
3                                                        receiverService                                        receiverService name
please tell any more confiration requered.
Regards,
Ramesh

Problem: ABAP Proxy Client Sending to XI - Message lost

Hi all,
I got a problem, concerning ABAP Proxy Client.
I have done the following:
1. Created an outbound interface in XI 3.0, sp14
2. Created Proxy for this in ABAP using sproxy
3. Created ABAP pgm to call this proxy
4. Maintained SM59 http destination to XI
(RFC Dest:INTEGRATIONSERVER TYPE H)
5. Sender r/3 system is WAS 640
6. I also did sxmb_adm in Sender System to have Integration Engine URL pointing to XI System.
7. I registered/ activated queues in SXMB_ADM.
8. SICF service is active for defalt/xi/engine in both Sender and target systems.
I allready have ABAP Proxy Server running...
My Proxy Client seems to run.., running my report (based on the ABAP Proxy Client Weblog from SDN)I get a sy-subrc 0 and no error, bot I can't see no message in XI. Neither in SXMB_MONI, nor in RWB checking Message-Monitoring
Can someone please tell me what is going wrong and where I could check for my messages?
Thanks in advance, Daniel

Hi Daniel -
Looks like you've done the major tasks for this to work. A couple of things however...
For proxies, Type H is the correct RFC Dest type. However, don't know if it's a typo, but the 'Dest:INTEGRATIONSERVER' should have '//' like 'Dest://INTEGRATIONSERVER'.
Also, confirm that your are using the correct port in your destination. You should use the integration server's ICM port, not the J2EE server port. You can confirm this in SMICM, then Goto-->Services. You may already have this; I just didn't see it specified in your description.
Regards,
Jin

SOAP error in synchronous scenario for ABAP Proxy with Oracle D/B

Dear Experts,
I am working in Sender ABAP Proxy <====>SAP PI 7.31 JAVA only <====> Oracle Database. My proxy configuration are working successfully.
Apart from that, I have maintained a SOAP sender communication channel under the ECC business system with
Transport Protocol as HTTP
Message Protocol as XI 3.0
Adapter Engine as Central Engine
When I am testing from ECC at Tx SPROXY, I am receiving following error.
com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.aii.adapter.xi.routing.RoutingException: InterfaceDetermination did not yield any actual interface at com.sap.aii.adapter.soap.web.SOAPHandler.processSOAPtoXMB(SOAPHandler.java:746) at com.sap.aii.adapter.soap.web.MessageServlet.doPost(MessageServlet.java:505) at javax.servlet.http.HttpServlet.service(HttpServlet.java:754) at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) at
1. In XI3.0 protocol, I can not select BE but when selected HTTP 1.0 as Message protocol then I can find the BE.
2. No Response message is shown in ECC when testing the message.
3. How do Receiver JDBC adapter for Oracle Database is configured
4. What would be Message Protocol for Oracle Database i.e. XML SQL Format or Native SQL format for Select operation.
Please guide.. All your inputs will be appreciated......
Regards
Rebecca

Dear Indrajit,
Appreciate your inputs.. Yes I have configured all the ABAP proxy configurations and there no question of missing any thing as Tx SLDCHECK in ECC is working perfectly fine.
But still to go, some of the queries needs more input.
1.In ID, i have created a Sender SOAP communication channel with listed details.
Transport Protocol as HTTP
Message Protocol as XI 3.0
Adapter Engine as Central Engine
Is there any parameters which I may be missing from Module tab of Synchronous SOAP Cc ?
2. In the Cc monitoring, the JDBC receiver status shows "Database operation successfully completed" but I could not find any response data from database. The Message monitoring should have 2 messages for 1 trigger, but I could find only 1 message by SOAP only?
Sorry to bother experts...Please answer in sequence...
Regards
Rebecca

ABAP proxy client call PI with new client 120 in old business system

Hi all
We have a requirement to call PI from ABAP client proxy in synchronous mode via a CRM client 120.
CRM client 100 is already configured in the Business system talked above but now we need the same business system to be configured for client 120 as well.
My question is If we go to the SLD and
|-> Click on Business System
|-> Add new client 120
Will it work or we need to do some extra configuration for communication channel.
Also please let me know how to configure Integration Directory for sender agreement, Receiver Agreement and the communication channel.
Thanks in Advance.

Hi Naina ,
We have a requirement to call PI from ABAP client proxy in synchronous mode via a CRM client 120.
CRM client 100 is already configured in the Business system talked above but now we need the same business system to be configured for client 120 as well.
My question is If we go to the SLD and
|-> Click on Business System
|-> Add new client 120
> hope the technical entry of CRM is already in SLD . So you just need to make a business system entry . point the business sytem to the technical system entry with the right client here 120 .
Will it work or we need to do some extra configuration for communication channel.
> since sender is client proxy you don't need to do anything in case of receiver proxy you will be needing reciver communication channel of XI adapter type .
for proxy based communication your application system(other than PI/XI) should be able to make a proxy call to XI or receive a call from XI .for this purpose you need to make some settings at R/3( or CRM level)
For this check blog : /people/vijaya.kumari2/blog/2006/01/26/how-do-you-activate-abap-proxies
Abap proxies ( Client and Server proxies)
Other steps i.e Interface determination/receiver determination are as usual .
Regards ,

Error with ABAP proxy

Hi all,
I have an ABAP proxy - XI - Webservice scenario, in the XI side we are getting error saying input data not coming in. How to check weather proxy is triggering the actual payload or data?
There has been a change in the WSDL from the Webservices side, they have changed the data type, so we too updated the mapping in XI. So do we need to change anything in the ABAP program which triggers the proxy,
how do I check weather proxy is triggering data or not?
I want to see weather its problem with the ABAP trigger program.
Thanks,
Srinivas

Hi ramakrishna,
Does R/3 side SXMB_MONI give successful chequered flag when the message is processed?
Because for correctly processed message, the data is being updated in the table, but I can't see the chequered flag on the R/3 side.
But for the wrongly processed ones its showing PL_TIMEOUT error and showing red flag on R/3 side, this is what I see on the R/3 side:
<?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="1">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">PL_TIMEOUT</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Pipeline timeout condition satisfied</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>

ABAP Proxy Client?

Hi Experts,
i've gone thru a ABAP Client Proxy scenario which is mention below.
/people/ravikumar.allampallam/blog/2005/03/14/abap-proxies-in-xiclient-proxy
can anyone elaborate abt this scenario?
i want to know proxy will be generated on XI or on the sender system. if we are creating proxy on XI then how XI message format i.e., (SOAP XML message) is generated and Message interface which is created for Sender will b mapped?
Cheers
Faisal

Hi Faisal,
/people/ravikumar.allampallam/blog/2005/03/14/abap-proxies-in-xiclient-proxy
Proxy is created on application system .in this example they have taken two clients of XI system. client 100 is configured as XI integration server and client 105 is configuired as sap application system.client 105 is working as Sender system.Actually we can have only one XI integration server on any NW system but we can have various application systems.
For client proxy creation , we first create outbound mesage interfaces in IR and then we go to SPROXY transaction and chose our outbound message interface and create proxy from that interface.
u create a abap report and send message from there.
use these links:
ABAP Proxy Generation
http://help.sap.com/saphelp_nw04/helpdata/en/ba/f21a403233dd5fe10000000a155106/content.htm
ABAP Proxy Generation
http://help.sap.com/saphelp_nw04/helpdata/en/14/555f3c482a7331e10000000a114084/content.htm
Proxy Generation
http://help.sap.com/saphelp_nw04/helpdata/en/86/58cd3b11571962e10000000a11402f/content.htm
ABAP Proxy Runtime
http://help.sap.com/saphelp_nw04/helpdata/en/02/265c3cf311070ae10000000a114084/content.htm
To activate ABAP proxies
/people/vijaya.kumari2/blog/2006/01/26/how-do-you-activate-abap-proxies
Detailed step-by-step solution for ABAP proxies in XI
/people/ravikumar.allampallam/blog/2005/03/14/abap-proxies-in-xiclient-proxy
ABAP Server proxies
/people/siva.maranani/blog/2005/04/03/abap-server-proxies
Debugging of Inbound ABAP proxies
/people/stefan.grube/blog/2006/07/28/xi-debug-your-inbound-abap-proxy-implementation
File to R/3 via ABAP Proxy
/people/prateek.shah/blog/2005/06/14/file-to-r3-via-abap-proxy
Cheers
Rohit
please reward points if found useful....it would be appreciable...:)
Edited by: Rohit Goel on Jan 30, 2008 7:45 AM

"SOAP:Fault" in scenario with ABAP proxy client

Similar Messages

Maybe you are looking for