IDOC to abap proxy- Receiver Service Cannot be converted into ALE logical

Dear all,
I have idoc to abap proxy -
R3 to SRM scenario.
I am getting the error Receiver service cannot be converted to ale logical system.
I have check the receiver bs SRM_BS , adapter specific attributes ... im getting the logical system ( this is not the problem)
i am using receiver XI adapter
with XI 3.0 as protocol
and http destination with /sap/xi/engine?type = receiver
i can see the data in the moni of receiver SRM system but it shows a red flag
pls help

Hi kiran,
i have checked all the RFC destinations ... seems OK
problem is in SRM moni .. sender service and sender interface are not visible.
trace ::::
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
<Trace level="1" type="B" name="CL_XMS_HTTP_HANDLER-HANDLE_REQUEST" />
- 
<Trace level="1" type="T">XMB was called with URL /sap/xi/engine/?type=entry</Trace>
<Trace level="1" type="T">COMMIT is done by XMB !</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE" />
- 
<Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />
<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 = SR5</Trace>
<Trace level="1" type="T">client = 300</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = RFCADMIN_SR5</Trace>
<Trace level="1" type="Timestamp">2008-06-01T16:27:03Z CET</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 = DD2FF717DAE395F186DF001560A1C7CB</Trace>
<Trace level="1" type="T">PLNAME = RECEIVER</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 = RECEIVER</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Get definition of internal pipeline = SAP_RECEIVER</Trace>
<Trace level="1" type="T">Queue name : XBTR0003</Trace>
<Trace level="1" type="T">Generated prefixed queue name = XBTR0003</Trace>
<Trace level="1" type="T">Schedule message in qRFC environment</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</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="T">--start sender interface action determination</Trace>
<Trace level="1" type="T">select interface *</Trace>
<Trace level="1" type="T">select interface namespace</Trace>
<Trace level="1" type="T">no interface found</Trace>
<Trace level="1" type="T">--start receiver interface action determination</Trace>
<Trace level="1" type="T">Loop 0000000001</Trace>
<Trace level="1" type="T">select interface SupplierPortalTradingPartner_CreateOrChange_In*</Trace>
<Trace level="1" type="T">select interface namespace http://sap.com/xi/SRM/SupplierEnablement</Trace>
<Trace level="1" type="T">no interface found</Trace>
<Trace level="1" type="T">--no sender or receiver interface definition found</Trace>
<Trace level="1" type="T">Hence set action to DEL</Trace>
<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 RECEIVER</Trace>
<Trace level="1" type="T">system-ID = SR5</Trace>
<Trace level="1" type="T">client = 300</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = RFCADMIN_SR5</Trace>
<Trace level="1" type="Timestamp">2008-06-01T16:27:04Z CET</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 external pipeline RECEIVER</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Corresponding internal pipeline SAP_RECEIVER</Trace>
<Trace level="1" type="B" name="PLSRV_CALL_INBOUND_PROXY" />
- 
- <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="Inbound Framework" />
- 
- <asx:abap xmlns:asx="http://www.sap.com/abapxml" version="1.0">
- <asx:values>
<CX_ERROR href="#o3314" />
</asx:values>
- <asx:heap xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:abap="http://www.sap.com/abapxml/types/built-in" xmlns:cls="http://www.sap.com/abapxml/classes/global" xmlns:dic="http://www.sap.com/abapxml/types/dictionary">
- <cls:CX_SY_NO_HANDLER id="o3314">
- <CX_ROOT>
<TEXTID>1F09B73915F6B645E10000000A11447B</TEXTID>
<PREVIOUS href="#o3313" />
<KERNEL_ERRID>UNCAUGHT_EXCEPTION</KERNEL_ERRID>
- <INTERNAL_SOURCE_POS>
<PROGID>496</PROGID>
<CONTID>1564</CONTID>
</INTERNAL_SOURCE_POS>
</CX_ROOT>
<CX_NO_CHECK />
- <CX_SY_NO_HANDLER>
<CLASSNAME>CX_BBPX1_STD_MESSAGE_FAULT</CLASSNAME>
</CX_SY_NO_HANDLER>
</cls:CX_SY_NO_HANDLER>
- <cls:CX_BBPX1_STD_MESSAGE_FAULT id="o3313">
- <CX_ROOT>
<TEXTID>65B8FEB5F43CC949B7CD662AB888ED34</TEXTID>
<PREVIOUS />
<KERNEL_ERRID />
- <INTERNAL_SOURCE_POS>
<PROGID>496</PROGID>
<CONTID>1738</CONTID>
</INTERNAL_SOURCE_POS>
</CX_ROOT>
<CX_DYNAMIC_CHECK />
<CX_AI_APPLICATION_FAULT />
- <CX_BBPX1_STD_MESSAGE_FAULT>
<AUTOMATIC_RETRY />
<CONTROLLER />
<NO_RETRY />
- <STANDARD>
<CONTROLLER />
<FAULT_TEXT>An error occured within an XI interface: Exception occurredE:BBP_BUPA_SUPPLIER:089 -Unable to determine logical system of sender; check your data Programm: CX_BBP_BD_ERROR===============CP; Include: CX_BBP_BD_ERROR===============CM002; Line: 57</FAULT_TEXT>
<FAULT_URL />
<FAULT_DETAIL />
</STANDARD>
</CX_BBPX1_STD_MESSAGE_FAULT>
</cls:CX_BBPX1_STD_MESSAGE_FAULT>
</asx:heap>
</asx:abap>
</Trace>
<Trace level="1" type="T">System Error at Receiver... => ROLLBACK WORK</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="System_Error">Error exception return from pipeline processing!</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
</SAP:Trace>
fault message says the sender is not having logical sys...but my sender sys is showing logical system in adapter specific attributes
pls help
points will be awarded

Similar Messages

File2idoc receiver service cannot be converted into ale/logical system

hi
i m working with file to idoc the file adapter is working fine bit\ut wen i checked in
sx_monitor i found the red flag and it shows the error
receiver service cannot be converted in to ale/logicalsystem

Go to the Business System / Service you have maintained for your File.
Double Click ,Business System --> Adapetr Specific Identifiers.
Here, maintain the Logical System name of the Sender System. This logical system name should be the value for which the partner profile
has been created in your SAP system in we20.
The same should also be maintained for your Receievr Business System.
Regards
Bhavesh

Error: Receiver Service Cannot be converted into an ALE logical system

While doing scenario FILE to SAP R/3 by using BPM we get following error message:
<IDOC_Adapter> Attribute_INV_REC_SERV
SAP system is not able to receive the output.

Hi,
Goto Integration directory.
Click on your integration Process ( imported BPM).
Then check the Service in the menu bar of the Integration process.
You will have adapter specific paramters.
Give the logical system name of PI for the integration process.
This name will be used as the logical system when sending IDOC.
Hope this helps.
Regards,
Viany.

Receiver service ??? cannot be converted into an ALE logical system

Hi,
I am hoping for some help with an Idoc issue in XI version 3.0. The scenario is like this:
Flat file->File adapter->XI->Idoc adapter->R/3
I have configured a scenario in one system like this that works fine. But in the current system I am getting the error message "Receiver service ??? cannot be converted into an ALE logical system" from the Idoc adapter.
As it is XI 3.0, I have set the Agency and Scheme in the destination communication channel to <Service>, ALE#LS and in the destination party, I have created a alternative identifier <Service>, ALE#LS, SYSCLNT200.
I have configured an ALE logical system name in the SLD.
I have cleared the SLD cache in the integration builder.
The ALE logical system name was not in the SLD when the message first appeared, but I thought clearing the cache would fix that. I have not tried deleting the service and re creating it. That is my next step....if all else fails.
Not sure what else I haven't tried.
Can anyone offer any advice?

Thanks Sam Raju for the reply.
On your questions:
1. I checked IDX1 - port for the receiving R/3 is defined as SAPIR1_300 (port: SAPIR1 and Client: 300) and it is mapped to RFC destination of IR1300.
2. Checked RFC destination IR1300 - it is setup as R/3 connection and checked test connection and remote login and both are working fine
3. Checked IDX5 - did find one message (status is successful) corresponding to the file I am sending into R/3 and this entry is an Outbound entry.
Question: Should there be two entries here in IDX5 - one for inbound and the other for outbound?
May be I am doing something wrong here in setting up the interface mapping and endpoints. Anyway when I check the IDOCOutbound in the Soap Header, I see the following:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:IDocOutbound xmlns:SAP="http://sap.com/exchange/MessageFormat/">
<SAP:TABNAM>EDI_DC40</SAP:TABNAM>
<SAP:MANDT>100</SAP:MANDT>
<SAP:DOCNUM>0000000000008002</SAP:DOCNUM>
<SAP:DIRECT>2</SAP:DIRECT>
<SAP:IDOCTYP>FLIGHT_SAVEREPLICA01</SAP:IDOCTYP>
<SAP:MESTYP>FLIGHT_SAVEREPLICA</SAP:MESTYP>
<SAP:SNDPOR>SAPBXI</SAP:SNDPOR>
<SAP:SNDPRN>PRISM</SAP:SNDPRN>
<SAP:SNDPRT>LS</SAP:SNDPRT>
<SAP:RCVPOR>SAPIR1</SAP:RCVPOR>
<SAP:RCVPRN>IR1CLNT300</SAP:RCVPRN>
<SAP:RCVPRT>LS</SAP:RCVPRT>
</SAP:IDocOutbound>
Do you see anything wrong or missing here. SNDPOR is XI port, SNDPRN is the source partner (file) and RCV... information is all the receiving R/3.
I am suspecting that something is missing either here or in the endpoint setup.
Also, in the TechnicalRouting I have this:
- <SAP:address version="20">
<SAP:systemKey>IR1CLNT300</SAP:systemKey>
<SAP:endpointType>IDOC</SAP:endpointType>
<SAP:url>IDOC://SAPIR1?RFCDEST=IR1300&DOCREL=&VERSION=3&SAPREL=46C</SAP:url>
</SAP:address>
Any issues you see here in url?
Also, when I look on the XI server, I do not see these files deposited anywhere- so they are going somewhere (as the status in IDX5 is successful)!
Do I need to activate any queues or triggers anywhere.
Can you please offer advice and help us out.
Thanks again.
Srini
[email protected]

HTMLError in sxmb_moni, Idoc to ABAP Proxy Scenario

Hi Friends
I am trying to send data from R3 to SCMTM system(SAP System), via Idoc to ABAP Proxy Scenario ,I am getting the following under HTMLError in sxmb_moni
<?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="INTERNAL">CLIENT_RECEIVE_FAILED</SAP:Code>
<SAP:P1>400</SAP:P1>
<SAP:P2>ICM_HTTP_CONNECTION_FAILED</SAP:P2>
<SAP:P3>(See attachment HTMLError for details)</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Error while receiving by HTTP (error code: 400, error text: ICM_HTTP_CONNECTION_FAILED) (See attachment HTMLError for details)</SAP:Stack>
<SAP:Retry>A</SAP:Retry>
</SAP:Error>
Any ideas will be helpful.

Hi,
I faced similar problem. it was due to configuration problem in SXMB_ADM. corss check specific server confiration in SXMB_ADM.
/people/krishna.moorthyp/blog/2006/07/23/http-errors-in-xi
Regards,
Reyaz

Mail Sender to Abap Proxy Receiver with Attachements

Hi All,
Scenario: I need to create a ticket in Solman from a mail. I intend to do the scenario as Mail sender to Abap Proxy receiver asynchronous.
I have configured my sender mail adapter and am able to get the mails in XI. The attachements also appear in Inbound payload as MailAttachement-1, MailAttachement-2 etc. I have checked use mail packege and keep attachements in sender adapter.
Transport Protocol: IMAP4
Message Protocol: XIPAYLOAD
Queries:
1. My Inbound Data Type is the mail Package -- ximail30_xsd. Here in sxmb_moni I can see the mail attributes like from, to and the mail body in content. But How can I read the attachements in my message mapping.
2. How can I pass these attachements to Abap Proxy ( I do not need to alter attachments only pass to proxy ). These attachements have to be attached to the Solman ticket in SOLMAN server.
Appreciate your kind response to my above queries.
Thanks.
Regards,
Siddhesh S.Tawate
PS: I have tried using PayloadSwapBean in adapter module but still the content at source remains same.

Hi,
Please find below the part of code that might help you. I have given code only responsible for attachements part of the ticket.
loop at lt_attach into l_attachment.
        count = count + 1.
        if count = 1.
          first_line = 1.
        endif.
        l_type = l_attachment->GET_CONTENT_TYPE( ).
        split l_type at '"' into l_type
                                 file_name
                                 l_name.
        l_name = file_name.
        split file_name at '.' into file_name
                                    file_type.
        l_xstring = l_attachment->GET_BINARY_DATA( ).
        strlen = xstrlen( l_xstring ).
        Compute int = ( strlen div 255 ).
        Compute rem = ( strlen mod 255 ).
        if rem <> 0.
          int = int + 1.
        endif.
        count1 = int.
        if count = 1.
          last_line = count1.
        else.
          if int = 1.
            first_line = last_line.
          else.
            last_line = first_line + count1.
          endif.
        endif.
        wa_APPX_HEADERS-APPXNO = count.
        wa_APPX_HEADERS-DESCR = l_name.
        wa_APPX_HEADERS-FILETYP = file_type.
        wa_APPX_HEADERS-FILENAM = l_name.
        wa_APPX_HEADERS-FILEFM_UL = 'BIN'.
        wa_APPX_HEADERS-FIRSTL = first_line.
        wa_APPX_HEADERS-LASTL = last_line.
        wa_APPX_HEADERS-FILELEN = strlen.
        wa_APPX_HEADERS-LAST_USR = sy-uname.
        GET TIME STAMP FIELD wa_appx_headers-TIMESTAMP.
        append wa_APPX_HEADERS to it_APPX_HEADERS.
        while count1 <> 0.
          count1 = count1 - 1.
          if count1 <> 0.
            wa_APPX_LINES_bin-LINE = l_xstring+0(255).
            shift l_xstring left by 255 places in BYTE MODE.
          ELSE.
            wa_APPX_LINES_bin-LINE = l_xstring.
          endif.
          append wa_APPX_LINES_bin to it_APPX_LINES_bin.
          clear: wa_APPX_LINES_bin, wa_APPX_LINES.
        endwhile.
        first_line = last_line + 1.
        clear: strlen, count1, file_name, file_type, l_type, int, rem, l_xstring, l_attachment.
      endloop.
CALL FUNCTION 'BAPI_NOTIFICATION_CREATE'
        EXPORTING
          NOTIF_EXT                = wa_NOTIF_EXT
        NOTIF_CRM                = wa_NOTIF_CRM
IBASE_DATA               =
     IMPORTING
       NUMBER                   = Refnum
       NUMB                     = Numb
       REFNUM                   = Ticket_No
       SYSID                    = SYSID
        TABLES
          NOTIF_PARTNERS           = it_NOTIF_PARTNERS
        NOTIF_NOTES              = it_NOTIF_N_EXT
          NOTIF_SAP_DATA           = it_NOTIF_SAP_DATA
        NOTIF_TEXT_HEADERS       = it_NOTIF_TEXT_HEADERS
        NOTIF_TEXT_LINES         = it_NOTIF_TEXT_LINES
        APPX_HEADERS             = it_APPX_HEADERS
        APPX_LINES               = it_APPX_LINES
        APPX_LINES_BIN           = it_APPX_LINES_BIN
         RETURN                   = RETURN
Please observe how first and last line of attachement is calculated. That is what created problem for me initially.
Hope this helps.
Regards,
Siddhesh S.Tawate

ABAP Proxy Receiver Asynchronous EOIO

Hi,
Is it possible to Guaranteeing the Sequence of Asynchronous Messages for ABAP Proxy Receiver(EOIO)?
If yes, how can I configure?
Thanks,
Kiara.

Hi Stefan,
Thank you.
One quick question.
In case if I use JMS>PI>RFC(Async) then also no need of maintaining EOIO for RFC Receiver Async?
On JMS sender we are maintaining EOIO.
Reason for this request is currently we are using JMS>PI>RFC Async. We are using EOIO on JMS sender, but some times sequence of messages is missing.
Can you please let us know the cause of this issue.
Thanks,
Kiara.

On DNG Converter 8.3.0.141 Fuji X-T1 files (RAF) cannot be convertes into DNG. What can I do?

On DNG Converter 8.3.0.141 Fuji X-T1 files (RAF) cannot be convertes into DNG. What can I do?

Use DNG Converter 8.4: http://www.adobe.com/downloads/updates

Abap Proxy = Web Service - Connection timeout

Hi Experts,
I request your help on some issue we encounter actually on our Web services interfaces.
We have sceanario in which from SAP, we are sending a message to PI via Abap proxy.
PI then, send the message to the external system via a Web Service (we have configured the URL and authentification values).
When we want to test the scenario we have an issue.
- We see in SXMB_MONI message has status sent succesfully
- When we check the external system, we see that no message is received (no trace of message from PI).
- Then we check on PI runtime workbench, we see in the receiver communication channel error saying "Connextion Timeout"
(in detail: SOAP: call failed: java.net.ConnectException: Connection timed out")
We would like to investigate the issue.
Have you already encountered this kind of issues ? And how we could investigate the root cause here ?
And thanks for ur help,
S.N

This might be due to following reasons.
Please check whether firewall exist between Pi and external system. If so check with network team weather port or connectivity is established between PI server and external system. This should be the main reason. Also check the target URL and see whether you can able to consume the webservice directly from Soapui without PI. If your workstation is within PI's landscape and you see the same timed out error, then the network connectivity is the issue. Ask them to enable the port.

Choice Between IDOC and ABAP Proxy

Hello All,
We are building a Bi Directional Interface for Business partners between a third Party ERP, XI and SAP CRM.
We are looking for some advise on the best way to go forward between the two options below:
a) Do an ABAP Proxy Call on Fn Module CRMXIF_PARTNER_SAVE from XI
b) Create and IDOC in CRM
( Message Type CRMXIF_PARTNER_SAVE_M )
Not being an XI consultant, my understanding is as follows
Option A : Gives me the flexibility to format my response in the manner we like. But this is a synchronous call. Also this is a generated RFC. So changes in the XIF layer of CRM could be an issue.
Option B : Response can be achieved only through the ALE Audit Functionality, which has a predefined message structure. For Eg: If I wanted to send the response in the same format as the incoming message with an added segment for the error, this is not possible. Ofcourse, I get all the functionalities of monitoring and Handling IDOCs in this option.
Any thoughts on the advantages and disadvantages of each option would be greatly appreciated.
Thanks
Anoop

Anoop,
I probably should have mentioned in the BLOG, that IDOC is good if its a standard IDOC, so that you don't have under go the pain doing the modifications for the custom one.
In your case, PROXY might make more sense as you are saying that you have to do some custom processing as well. So, you can call the BAPI / Function for the standard processing and then do the custom processing in your Proxy code. And more over, if you have want to have a Synch interface, then you cannot use IDOC.
So, the options in this case boil down to PROXY / RFC.
PROXY will definitely have the advantage as its going to bypass the adapter engine and directly interact with the Integration server. And moreover, even if you already have a RFC, you can always call that inside your PROXY. However, the only flip side here compared to IDOC, is that you will have to create all your IR objects manually.
Hope this helps you in making your decision.
regards,
Ravi
Note : Please mark the helpful answers.

Idoc to ABAP Proxy with Acknowledgement Coming Back

We are running SAP standard SRM scenario where our ECC systems are posting Idocs to PI which maps and sends to SRM as an ABAP proxy. Can someone please explain to me the best way to have SRM send back an acknowledgement to the sending ECC system when the document has been posted so we can update the Idoc status? We are looking for standard SAP config firstly, then will consider custom development if absolutely necessary.
Thanks in advance!
Peter

Hi Peter,
you can configure the IDOC ack setting and you can getthe idocs for acknowledgement in ECC side.Configure the ALEAUD message type in ECC and configure one Coomunication channel for the ACk in ID.
if this is not clear just giive ur mail id i will send u one pdf or this
Regards

ABAP Proxy, WEB SERVICE and RFC

Hi
I have to pull the data from XI.
I have the PDFdocument of how to integrate XI with BI.
But i am not clear what is abap proxy and web service.
Could anyone let me know basic of what is abap proxy and webservice.
Is abap proxy and webservice are present in both the systems XI&BI ?
REgards
annie

Hi,
ABAP proxy is a connection between SAP XI & BI . For all the connections need to chk in SM59, and SICF .
proxies are a replacemet for adapters whereas webservices(WSDL) are replacements for data typesYou generate proxies from an interface description in WSDL (Web Service Description Language) by using ABAP proxy generation.
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/46d6c25d-0b01-0010-06a9-8e8218753c02
The SOAP adapter enables you to exchange SOAP messages between remote clients or Web service servers and the Integration Server. Also you can use the axis framework with SOAP adapter. Check this help:
http://help.sap.com/saphelp_nw04/helpdata/en/45/a4f8bbdfdc0d36e10000000a114a6b/content.htm
We can Communicate between SAP System & Webservice Using Proxies. Check this weblog for some information on this:
/people/siva.maranani/blog/2005/05/23/communication-between-sap-system-webservice-using-proxies
ABAP Proxy -> XI -> Webservice :
pls chk this links;
/people/shabarish.vijayakumar/blog/2006/03/23/rfc--xi--webservice--a-complete-walkthrough-part-1
http://www.webservicex.net/WS/WSDetails.aspx?CATID=4&WSID=59
/people/thomas.jung3/blog/2004/11/17/bsp-a-developers-journal-part-xiv--consuming-webservices-with-abap
https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/3022- [original link is broken] [original link is broken] [original link is broken] Activate Proxy
/people/siva.maranani/blog/2005/04/03/abap-server-proxies -ABAP Server Proxy
/people/ravikumar.allampallam/blog/2005/03/14/abap-proxies-in-xiclient-proxy - ABAP Client Proxy
/people/siva.maranani/blog/2005/09/03/invoke-webservices-using-sapxi
/people/ravikumar.allampallam/blog/2005/03/14/abap-proxies-in-xiclient-proxy
Hope this helps,
Regards
CSM Reddy

ABAP proxy web service authentication

Hi,
We are trying to develop an ABAP proxy for a web service call on ECC6 (SP14).
The web service (provided by another SAP system) uses basic authentication. The proxy has been created as has the logical endpoint/service (via SOAMANAGER). In the endpoint I have provided the credentials for authentication.
Manually testing the proxy via SE80 works fine.
When I try and call the proxy via a program it prompts for user id/password. If provided the call works.
DATA: ZPROXY   type REF TO ZMY_PROXY,
          INPUT       type ZMY_PROXY_REQUEST,
          OUTPUT    type ZMY_PROXY_RESPONSE.
TRY.
     CREATE OBJECT ZPROXY.
     CATCH CX_AI_SYSTEM_FAULT.
ENDTRY.
TRY.
     CALL METHOD ZPROXY->LIST_USERS
       EXPORTING
         INPUT = INPUT
       IMPORTING
         OUTPUT = OUTPUT.
     CATCH CX_AI_SYSTEM_FAULT .
     CATCH CX_AI_APPLICATION_FAULT .
ENDTRY.
My expectation is that the proxy would derive the credentials from the logical endpoint.
Am I missing something?
Thanks in advance.

Hi Olivier,
Yes - the consumer system is ABAP Netweaver 7.0.
It has SP14. The webservice provider system is running at the same level.
The webservice provider was created using the wizard to convert an RFC enabled function module. I then used SOAMANAGER to created the provider endpoint. On the consumer side it was the same - wizard to create the proxy & then SOAMANAGER for the endpoint.
I checked the services on the provider system & the service indicated was activated already - which was expected as the web service call itself works fine.
/default_host/sap/bc/srt/rfc/sap/<webservice>/<client>/<method>/<binding>
Any other suggestions?
Thanks again,
Tim
Edited by: Tim Brown on Mar 10, 2009 10:58 PM

Sender Abap Proxy -- Receiver JDBC , catch communication channel exceptions

Hi All,
I have a sender abap proxy and a receiver jdbc asynchronous interface.
Now under some circumstances when I send some junk data for an update query(which satisfies metadata requirement but wrong primary key) it shows chequered flag in both XI and r/3.
But in communication channel it shows error.
Queries:
1. How do I handle this.
2. Since this is triggered from Abap wht will be subrc when method ends in this particular case.
3. Is there any possibility of program goin into dump?
Regards,
Prem

You can catch the exception in cx_ai_system_fault.
http://help.sap.com/saphelp_nw70/helpdata/en/75/a55c3cff8ca92be10000000a114084/content.htm
DATA:
lo_mes TYPE REF TO
     [Client proxy class],
l_sys_exc TYPE REF TO
        cx_ai_system_fault,
l_app_exc TYPE REF TO
        cx_ai_application_fault.
CREATE OBJECT lo_mes.
TRY.
CALL METHOD
lo_mes->EXECUTE_SYNCHRONOUS
    EXPORTING
      OUTPUT    = ls_request
    IMPORTING
      INPUT     = ls_response.
CATCH cx_ai_system_fault
            INTO l_sys_exc.
* handle system error
    EXIT.
CATCH cx_fault_1
            INTO l_app_exc.
* handle application error 1
CATCH cx_fault_n
            INTO l_app_exc.
* handle application error n
CATCH cx_ai_application_fault
            INTO l_app_exc.
* handle other
* application errors
ENDTRY.
Thanks,
Beena.

IDoc vs ABAP Proxy

Hi experts,
I have a couple of integration scenarios as such
SAP -> XI -> SOAP
We have a couple of options for the link between SAP -> XI.
1. ABAP Proxy
2. IDoc
These are usually asynchronous updates to the external system, triggered from SAP.
Which method is better in terms of performance, and maintainability point of view.
Currently, I chose the IDOC approach because if we were to go with the ABAP Proxy approach, the SAP system requires an XI ADD-ON, which implies additional risk.
Any advise is greatly appreciated.
Thanks.
Ron

Ron,
Take a look at this blog, it should answer your question of when to choose Idoc's and when to go for proxies,
<a href="/people/ravikumar.allampallam/blog/2005/08/14/choose-the-right-adapter-to-integrate-with-sap-systems">Choose the Right Adapter to integrate with SAP systems</a>
If your load is high, then SAP strictly recommends proxies. If load is not very high and you have standard Idoc's available for this, you might as well go for Idoc's.
Regards
Bhavesh

IDOC to abap proxy- Receiver Service Cannot be converted into ALE logical

Similar Messages

Maybe you are looking for