SOAP Receiver/Sender in IDOC- XI- SOAP receivers?

hi,
i have idoc-> xi-> soap receiver.
1. How can i get a response back from soap receiver?
2. in the above scenario is SOAP the receiver or agian the sender?
3. not sure how i can get a response back from the soap receiver?
any tips would be helpful.
thanks,
tirumal

Hi,
It should be

Under Target URL, enter the complete address (URL) of the Web service provider that you want to send the message to.
http://help.sap.com/saphelp_nw04/helpdata/en/29/5bd93f130f9215e10000000a155106/content.htm
What are you specifying?
Can you give the entry in Target URL...
Regards
Suraj
Message was edited by: S.R.Suraj

Similar Messages

SOAP receiver adapter - payload inside the soap envelop

Hi,
We have to send a SOAP message to 3rd party from PI 7.1. Using SOAP receiver adapter - we are trying to achieve this. 3rd party software is unable to accept payload as an attachment of the main envelop - they want it enside the main envelop.
I tried with "Keep attachment" option - but PI still keping the payload as an attachment. I think this option is for handling "extra" attachment.
Is there any way we can keep the payload inside the envelop?
In run-time WB, at the moment envelop looks like
<SOAP:Envelope xmlns:SOAP="http://schemas....
<SOAP:Body>
<sap:Payload xlink:type="simple" xlink:href="cid:payload-d6518670ca1311debbd9ca347000800b...">
</SOAP:Body>
</SOAP:Envelope>
And the payload d6518670ca1311debbd9ca347000800b... ( again viewed from RWB) - contains the data.
<?xml version="1.0" encoding="UTF-8" ?>
<ns2:Order> ....
</ns2:Order>
Can we insert this payload directly inside the SOAP:Envelope body instead of a link there?
Regards,
Sudhin

Hi!
It seems to me that this 3rd party is expecting only XML not SOAP.
If this is the case, you should use the HTTP Receiver adapter instead of SOAP.
Some systems 'say' they can speak SOAP but they can only speak XML. Not to blame, it's a mistake many make these days.
The only way you use SOAP Receiver adapter with this 3rd party, is that if someone from the 3rd party hands you a WSDL file.
Ricardo Sancio Lóra
Brazil

Soap Receiver adapter , Target URL and Soap Action

HI all,
WIll anyone tell me regarding Soap action, casue , they have given a URL which i have put in Target URL, but i am not able to understand what is SOap action what need to be put in this
Thankign you
Sridhar

i Sridhar,
In XI SOAP adapter we need two things:
SOAP URL: which is endpoint to the webserver.
SOAP action: describes particular method name we wanted to excute on that web applicaiton hosted on the webserver.
WSDL file has normally multiple operations(methods) , so we execute particular method by giving particular action name.
Action is not mandatory parameter i guess, this is in case , when wsdl is exposing only one method(action).
:Normally you can find SOAP Action element under element <SOAP:operation name = "XXX">
Hope this clears.
Cheers,
Div

SOAP RECEIVER: Possible to change the soap header request

Hi
Is it possible to change what is included in the soap header like namespaces (.. xmlns:ns="http://what.com"
Specifically I need to have the "http://Strange.org/thisis.xsd" (see below) included in the header and the <ns:pi-create> included in SOAP-ENV
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:ns="http://Strange.org/thisis.xsd">
<SOAP-ENV:Body>
<ns:pi-create>
<request>
<request-data>...
</request-data>
</request>
</ns:pi-create>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
Hope somebody can help
Cheers

Hi Bowie,
1.You can change the Namespace. condition is no obj's under the namesapce then only it's possible otherwise u can't.
2.create a new namesapce what ever u want and copy all the obj's under that namesapce.finally delete the previous one.
XMLAnonymizerBean
Use
You use this module to anonymize XML elements and attributes by removing namespaces or namespace prefixes from the XML document of the main payload.
You can define a particular namespace prefix for each namespace. You can also change the encoding attribute of the XML declaration.
Integration
You can use the module in adapters that can be extended in the module processor.
Activities
Entries in the Processing Sequence
● Insert the module before the adapter module.
If the adapter comprises multiple modules, for information about the position of the module, see: Extending the Module Chain in the Module Processor
● Enter the module name AF_Modules/XMLAnonymizerBean.
● Select the Module Type Local Enterprise Bean.
● The system proposes a module key.
Entries in the Module Configuration
● anonymizer.acceptNamespaces
Enter a list of namespaces and their prefixes that are to be kept in the XML document as follows: namespace1 n1 namespace2 n2 u2026
To enter a namespace without a prefix, enter '' (two single quotation marks).
Any namespaces you do not specify are removed from the XML document.
● anonymizer.quote
Specify the character to be used to enclose the attribute values.
The default value is '. The parameter is optional.
● anonymizer.encoding
To use a code page other than UTF-8, enter it. The parameter is optional.
For example, enter ISO-8859-1.
Example
The anonymizer.acceptNamespaces parameter has the following value:
urn:sap-com:document:sap:rfc:functions rfc urn:sap-com:document:sap:soap:functions:mc-style rfc
● Payload before using the XMLAnonymizerBean:
<Z_PAYMITEM_GET_LIST
xmlns="urn:sap-com:document:sap:rfc:functions"
xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<I_ACCOUNTIDENT xmlns="">
 <ACCOUNT_NUMBER>0080000094</ACCOUNT_NUMBER>
 <BANK_COUNTRY>DE</BANK_COUNTRY>
 <BANK_COUNTRY_ISO>DE</BANK_COUNTRY_ISO>
</I_ACCOUNTIDENT>
</Z_PAYMITEM_GET_LIST>
● Payload after using the XMLAnonymizerBean:
<?xml version='1.0' encoding='utf-8'?>
<rfc:Z_PAYMITEM_GET_LIST
xmlns:rfc='urn:sap-com:document:sap:rfc:functions'>
<I_ACCOUNTIDENT>
 <ACCOUNT_NUMBER>0080000094</ACCOUNT_NUMBER>
 <BANK_COUNTRY>DE</BANK_COUNTRY>
 <BANK_COUNTRY_ISO>DE</BANK_COUNTRY_ISO>
</I_ACCOUNTIDENT>
</rfc:Z_PAYMITEM_GET_LIST>
with rgds,
MFH

SOAP receiver inactive problem

Hi Gurus,
I am using a SOAP receiver channel, I actived this SOAP CC in ID , but when I go to RWB and goto Communication Channel monitor, found the SOAP receiver channel status is "Channel started but inactive" with a yellow triangle.
Our XI version is PI7.0 SP11.

Hi,
send the first message with it and check again
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

SOAP Receiver adapter target url and method details

Hi Friends,
I am working on file to SOAP interface.
I know using SOAP receiver adapter , we need to have target URL and action.
Here, how client need to give target url and action as they are not aware of these things..please suggest.
Also if we are generating inbound service interface,how they have to handle this from their end.
Thanks
Kishore

Get the WSDL file from ur Third party client and u can use the WSDL file as an External definition in PI and WSDL file also has WSDL URL which u can use in SOAP receiver adapter.
For INbound SOAP case-
Generate the WSDL file in XI and give that WSDL file to ur third party client which will send the data using the WSDL URL mentioned in the file.
refer below blog for understanding in detail:-
How to use SOAP adapter:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/40611dd6-e66e-2910-f383-e80fb44f9cd4
chirag

SOAP receiver adapter for ASCII-7 characterset???

Hi,
Our scenario is Abap Proxy -> XI -> Web Services (SOAP Adapter). Receiver webservice will accept only the characterset of ASCII-7. But Abap Proxy will send only unicode characterset (default).
Any workaround for receiver SOAP adapter to accept ASCII-7 characterset?
Regards,
Prasad U

Hi -
You can set a specific encoding in the soap receiver channel module configuration. From the SOAP Adapter FAQ (Note 856597):
 o Q: What character encoding is supported by the SOAP receiver
 adapter?
 A: The SOAP receiver adapter can use any character encoding
 supported by the local JDK. The request message from the SOAP
 receiver is normally encoded in UTF-8. If you want to change this
 encoding, for instance to iso-8859-1, you can set parameter
 XMBWS.XMLEncoding to iso-8859-1 in the module configuration for
 the SOAP adapter module. This setting is for the outgoing SOAP
 message and has no effect on the incoming SOAP message. For the
 incoming SOAP message, any code page supported by the local JDK
 is accepted.
Check the <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/d23cbe11-0d01-0010-5287-873a22024f79">How to Use the XI 3.0 SOAP Adapter</a> document for an example.
Regards,
Jin

IDOC -XI-SOAP one sender different receivers based on condition

Hi All,
I have an IDOC to SOAP scenario.
For each record based on the input flag XI has to send the any one of the request ...like either create or update or delete request. All these message types are a part of single WSDL.
How can i do it?
Thanks in Advance
Jyothsna

hi There are two ways you can do this:
1. Without BPM - Since you have to create all the target messages adn you want either the 1st and second, or the first and third: create two multi-mapping with one and two, and one and three. In the receiver determination check the condtion based on which you decide the second or the third message has to be created and route it to the correct mapping accordingly.
2. with BPM, create all the target mapping. In the BPM check the condtion in the switch and do a send accordingly.
You can do this either on Receievr Determination or on Interface Determination.
Add multiple Receievrs/ Interfaces and then add the conditons on which the target should be choosen
to use Xpath for your receiver det. ref these blogs;
a combination of logics should help you in this case ...
/people/shabarish.vijayakumar/blog/2006/06/07/customise-your-xpath-expressions-in-receiver-determination
/people/shabarish.vijayakumar/blog/2005/08/03/xpath-to-show-the-path-multiple-receivers
pls reward points if solution found helpfull
regards
chandra.k

Message mapping: SOAP Receiver to IDOC Sender

hi,
i have an idoc sent to SOAP receiver. SOAP Response will have only the "Status code" and the "Reason of failure".
IDOC Sender will have the PO Number and the Vendor Name to which we are sending.
The SOAP Response will not have the PO Number and the Vendor Name.
How can i have the Reason of failure, PO Number and Vendor in one message type?
Thanks in advance,
Tirumal

Praveen -
Thanks for the response and appreciate your observation.
Very tight deadlines with the client and have to finish lot of tasks in short time so putting hands in everything.
There are lot of vendors who run their proprietary web services. So cannot change their stuff.
How would i map the SOAP request to the SOAP Response since some information is in one message type and other half of information available in other message type.
I created a SOAP Response Type with the "Reason Code" information.
I created another message type with all the information that i want.
How would i map the SOAP Request to the SOAP Response msg type and the other message type.
Let me know.
Thanks in advance,
Tirumal

SOAP sender and IDOC receiver

hi
Could u please help me, how to do this interface.
I am transferring the PO from legacy system(webServices Request) to SAP system when ever PO_IDOC is created in SAP I need to send PO number and Acknowledge back to the legacy system.This is synchronous communication from SOAP to IDOC.

you can use the ORDRSP ORDERS05 Idoc for PO response.
So your scenario will be
SOAP Req -> IDoc -> IDoc resp -> SOAP Resp
but if you can have a standard RFC or maybe an ABAP proxy you can make the scenario sync from SAP end.

SOAP Receiver- Error While Sending Message: 500 Internal Server Error

Hello,
Our scenario: IDoc to SOAP
I have added a third party system in the SLD and have used the same in my ID configuration.
An idoc will be triggered from R/3, which will received in PI, PI will transform the IDoc into SOAP message for the third party system.
I have tested the scenario in ID from Interface Determination and its successful.
But when i try to try to test it from RWB, using Test Message in Adapter Engine, I get an error,
"Error while sending message:500 Internal server error"
If we test it using a testing software like SOAP UI, it works fine but from PI we get the error mentioned above.
Regards,
Abhishek

Hello,
Since the IDOC adapter resides on the ABAP stack, you can use this URL instead (it will be sent to the integration engine as Venkata suggested)
http://host:port/sap/xi/engine?type=entry
Also check your firewall settings from PI to the third-party system.
Hope this helps,
Mark
Edited by: Mark Dihiansan on Feb 7, 2012 11:48 AM

IDoc to SOAP Receiver Fault Message Handling?

Hi,
I am working on IDoc to SOAP Scenario (IDoc -> PI -> SOAP). It is in async mode without BPM. This works fine as long as there is no error on the SOAP receiver side. How to handle the falut message raised by the SOAP receiver and send it back the SAP ECC.
Do I need to use ALEAUD IDoc for this? If Yes, how to configure this to handle fault message? Is there any other way of doing it?
Could you please give steps to handle the fault message?
Thank you.
Regards,
Cdr.

Have a look into the below threads -
How to capture SOAPFault in an Async/Sync Scenario without BPM
Acknowledgement Handling in IDoc to SOAP Scenario in PI 7.3

Unable to convert sender service for IDoc to SOAP Scenario

Hi,
I tried to find the solution my way and by using the search function but without any success. I have the folowing scenario:
SYS(my sap system) => IDoc => PI (Process Integration) => SOAP => XML
When i send the IDoc to the PI System and open SXI_Moni the folowing error is shown:
"Unable to convert the sender service receiver_service to an ALE logical system"
I read about Adapter Specific Identifies so i go to ID->Service without partner->Business System->MyBusinessSystem(SYS) then in Menü on Services and checked Adapter Specific Identifies. They are like maintained in SLD.
Next is a Cache refresh i tried a full one but no impact
Then i tried a header mapping in receiver agreement. I mapped there the receiver party to the definied receiver party and the receiver_service to the service.
I have no idea
Thanks for help, be sure that helpful answers will be awarded
regards
Matthias
P.S. What causes this error ? For my opinion ALE has already done all neccesary things (The Idoc is in PI System and the data is available in mesaage payload) so why didn't the pi map it and send it via Soap?

Hi Matthias
>>I dont know if its helpful but in SLD are only the system of our landscape so i have no entry for the external Party.
Party information is generally not required to be maintained in SLD
>>Adapter Specific Identifies
What is the value you have given for sender Business system->adapter specific identifier. Is it the same as the partner profile name in sender SAPECC. if not try making them same.
Regards
Suraj

Receiving IDOC through SOAP

Hello everyone,
Being new to XI, i'm still trying to process this brave new world. I've read and developed some simple scenarios using webservices. The last one i did was in a company A that needed to send ORDERS05 Idocs to company B. The latest provided a wsdl file used to create an external definition of the order document being sent. mapping is direct between all fields.
Now, Company B needs me to setup things here, and receive the IDOC sent from company A (message monitoring states that all messages from there are sent with success, but still missing the part i just described).
What is the best way to achieve this? can anyone point me to a document i could read on the subject (IDOC->IDOC with SOAP).
Thank you in advance

I'll try and explain the best i can:
In company B, i have two SWC:
COMPANYA - Represents the company that sent the IDOC ORDERS05 via webservice.
PI_COMPANYB - Represents the company where i stand fisically, where the IDOC must arrive and be integrated into SAP R3.
Here in company B i have created:
- edORDERS05 - An external definition, on a namespace dependent of COMPANYA, importing a xsd file ORDERS05.
- miOrdersDocuments - A message interface, of type edORDERS05.
In Integration Directory i have:
- COMPA - Party representing Company A
- COMPAPI - Business Service of COMPA with channel SOAP_Receiver_OrderRequest.
- SOAP_Receiver_OrderRequest - channel of communication to receive the webservice arriving from Company A, with URL like this:
http://65.222.222.222:50000/XISOAPAdapter/MessageServlet?channel=COMPB:COMPBPI:SOAP_Sender_OrdersRequests&version=3.0&Sender.Party=http%3A%2F%2Fsap.com%2Fxi%2FXI%3AXIParty%3ACOMPB&Sender.Service=COMPBPI&Interface=http%3A%2F%2FcompanyA.com%2FOrdersRequests%5EmiSalesDocumentsReq
The URL was snipped from "Location" tag in wsdl webservice previously created in Company B, using the "Tools->Define Webservice" from Integration Repository.
Right now the idoc is being sent successfully from SAP R3 to XI Engine in Company A, and then sent to Company B where the message should be arriving (logs in proxy at the company say so), but when arriving at XI Engine of company B, nothing appears on sxmb_moni transaction.
Hope i explained everything as asked.

BPM - IDoc to SOAP problem (Unable to convert sender service)

Hi,
I have a BPM scenario where I'm sending an Idoc from r/3 to XI to SOAP. As part of my scenario I'm sending an acknowledgment (ALEAUD) back to R/3.
I'm getting Unable to convert sender service IP_BPEL_INBOUND_ORDER to an ALE logical system on the Ack back.
So I usually know what to do when I get this, I do the SLD settings on the r/3 service and I'm OK. But in this case, it's asking for those ALE settings on the Integration Process?
I tried adding a logical system on it but now I'm getting the error that this is already used by the r/3 service. So I'm not to sure what to do next???
Rgds,
Yves

Ok do one thing, in you mapping take one field at target side (may be u can create one or use which is not been used yet) just map the standard function called Sender to this field in target.
Now in Intergration Directory when you do the header mapping by using F4 do not map the business systems this time, just press the button "Etended Path" (m not sure abt the exact name of this button) not use the X-Path here and select that target field which you mapped with Sender function in mapping.
How To Handle Acknowledgments for IDoc
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/903a0abc-e56e-2910-51a8-9dc616df56eb
I hope this will solve your problem.
Regards,
Sarvesh

SOAP Receiver/Sender in IDOC- XI- SOAP receivers?

Similar Messages

Maybe you are looking for