SOAP FTP SOAP Sync Scenario

Hi,
I am working on scenario where PI receiver XML message through SOAP Adapter and then transform into tab separated text and send it to FTP location, now requirement is to send back synchronours respose back same XML message with adding one more tag as Status In Process.
I am fine till sending text File to FTP location but how to send Sync XML response back with additional Status tag.
There r few solution use BPM Sync Async bridge, can we do it without using BPM. Even if i am using BPM, even after sending File i need Send Sync step to send back message to close Sync Asyn Bridge in BPM it means i need Sender Agreement with Sender communication channel to send corresponding response message to BPM. is their any alternate way to the same.
With Regards
Sunil

now requirement is to send back synchronours respose back same XML message with adding
one more tag as Status In Process.
not sure if you can add a tag to a already defined structure.....
What you can do in this case is
1) If you are using a wsdl of some other application then ask them to modify the response message to accomodate the Status tag ( if it is not present already).....then you can populate this in a mapping..
Can you tell me when the Status in Progress should be populated?
Is there any response coming from FTP which you will use as an indicator to say Status in progress?
OR is it when you send the FIle you need to correspondingly popluate Status in Progress tag and send to SOAP sender (irrespective of what happens in the FTP end)?
Regards,
Abhishek.

Similar Messages

SOAP to RFC - Sync Scenario. How to find where the response is going to?

Hello All
I have a SOAP to RFC sync scenario.
In SXMB_MONI, i see that both the initial message and the response message are successfully processed.
But, the SOAP sender is not receiving the response message.
How can i trouble shoot this scenario? How can i findout what is going wrong?
Most importantly, How can i find out the web address of the SOAP sender? I do not see it anywhere.
Thanks

Hi Chandra,
Please check this blog.
/people/shabarish.vijayakumar/blog/2008/01/08/troubleshooting--rfc-and-soap-scenarios-updated-on-20042009
You can by pass your message through a TCPIP gateway , this will help you to see the message contnet and the SOAP header information.
TCPIPGW application is availabel in one of the SAP notes for Monitoring SOAP adapter. and 2 SAP SDN PI blogs are also there on how to use this application...
Regards
Sunil.

Soap to proxy : sync scenario

Hi
Have a new PI 7.1 system , wanted to do a soap to proxy sync scenario
Do i need to create business system for proxies or if I just create 2 business services: one for sender and other for reciever ,it would suffice?
Is there any advantage / dsiadvantage if I use Business service instead of Business systems?
In SLD if I just create a product /swcv : it should be good if I want to use Business service mechanism instead of Business syste, ? or is creating Technical system and Business system mandatory even if I have to configure scnearios using Business service
Thnx

Business Systems require technical systems/software components and products, from an organisational perspective in PI it might be a good idea to define these things for an external entity (Business System). As far as Im aware business Services do not have that same requirment.
I tend to limit business service usage to one off or simple interaction B2B, as soon as you have more than one adapter interacting with the same external entity a business system with all of "their" adapters will help keep things clear to other people configuring integration scenario's. Whilst smart naming standard will get you around this most of the time, it makes more sense to put them together under the one system.
Hope this helps.

SOAP to RFC sync scenario

Hello members:
we have a business scenario: SOAP to RFC sync
an external system (ABC) sends documentrequest thru XI SOAP adapter and makes an RFC call to a BAPI and gets back the resposne to the ABC system.we are handling 4 mappings. 1. request msg to a common msg 2. common msg to BAPI request3.bapi response to common msg 4. common msg to response msg(which is same as the req msg)
i have the request msg and common msg as external definitions. I did the following steps and wanted to
know if i am right.
1. there are no data type & msg type needed for this
2. 4 msg interfaces
i) document o/b sysnc
ii) document i/b sync
iii)common o/b sync
iiii) common i/b sync
3) 4 mappings
i) document to common
ii) common to bapi req
iii) bapi resp to common
iiii) common to req/response
4) 3 intf mappings
source intf**********               target intf
i)document o/b               common o/b uses mapping #1
ii)request :common i/b         bapi i/b uses mapping #2
   resposne:bapi i/b           common i/b uses mapping #3
iii) common i/b             document i/b uses mapping # 4
pls provide your inputs if my approach is rite? do i need to have 4 msg intefaces?has any made mappings where 4 mappings are involved ( without BPM)
Thanks in advance

Hi,
I think you will have only 2 interfaces.
1. Sync Outbound interface (SOAP Structure)
    Two message types Req and Res
2. Sync Inbound interface (RFC Structure)
    Two message types Req and Res
Then two message mapping
1. SOAP Request to RFC Request
2. RFC Response to SOAP Response
and finally one Interface mapping.
Thanks,
Prakash

IDOC to Soap Webservice (Async/Sync scenario)

is any can provide somesteps please

Refer this thread
Synchronous IDoc -> SOAP scenario
Regards
Aashish Sinha
PS : reward points if helpful

Dynamic receiver Determination for Sync Scenario??

Hello Experts,
I have a SOAP -> Xi -> R3 sync scenario i,e, R3 to send back response to SOAP client.
Also I need the Dynamic receiver determination.
When I try to create the Interface Mapping, I get the error:
"Interface modi are different. "
Source interface MI_My_sync_iface is synchronous.
Target interface ReceiverDetermination | http://sap.com/xi/XI/System is asynchronous
I coud find few threads on forum related to this but i think there is no clear solution provided.
I do not wanna use BPM.
Please suggest.
Thanks in Advance!
Appropriate point will be awarded.

> So when I try to define a interface Mapping using a Sync interface as Source and Async interface as target, XI does not allow me to do so.
You are getting this error because in Interface mapping when you use sync source then it generates request and response tab so if at target side if you put anync interface then definetly it will go into error. You have to make both the interfaces as sync.
BTW, after getting the message in R3, how are processing the message? Are you using sync proxy??
You can solve the problem by creating one additional message interface of type inbound-asyn. Use this additional Message interfce in your Interface Determination. And create additional Receiver Agreement to deliver the message to it's destination.
Note: When you careate additional Interface Determination then you have to chose the response message interface (Sync message interface which returns the response from R3) as a source.
Regards,
Sarvesh

Hi, In a IDOC --- XI(BPM)--- SOAP Sync Scenario failrure.

Hi, In an IDOC ->XI(BPM)->SOAP Sync Scenario I observed recently messages are failing in SXMB_MONI with an error as:
com.sap.aii.af.ra.ms.api.DeliveryException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: System.Web.Services.Protocols.SoapException: Server did not recognize the value of HTTP Header SOAPAction: http://172.16.209.162/esdryrun/ContractData_Push. at System.Web.Services.Protocols.Soap11ServerProtocolHelper.RouteRequest() at System.Web.Services.Protocols.SoapServerProtocol.Initialize() at System.Web.Services.Protocols.ServerProtocol.SetContext(Type type, HttpContext context, HttpRequest request, HttpResponse response) at System.Web.Services.Protocols.ServerProtocolFactory.Create(Type type, HttpContext context, HttpRequest request, HttpResponse response, Boolean& abortProcessing)
friends, could u plz help on this.
Thanks,
satya.

Hello,
This indicates a configuration issue with this SOAP receiver adapter. Please check the on line help for the configuration of the SOAP adapter (the link is below). Please set the indicator in the "SOAP Action" field.
Configuring the Receiver SOAP Adapter
http://help.sap.com/saphelp_nw70/helpdata/EN/29/5bd93f130f9215e10000000a155106/frameset.htm
(Below is the extract from the link)
SOAP Action
Specify the SOAP action. The action specifies the value for the
SOAPAction in Web service messages; set the indicator.
Regards,
Sarah

(SOAP sender) --- XI ---- R/3 (RFC receiver) this sync scenario

Hi Experts,
Webservice(SOAP sender) < - > XI <--> R/3 (RFC receiver) this sync scenario tested with Infopath successfully.
I have given partner number,student object id are the two input fields(request) and i am getting student number as response. This scenario is working when i use MS infopath.
I have generated WSDL file embedded with below URL
http://xxxx.yyytec.passh.ed:7271/XISOAPAdapter/MessageServlet?channel=:Webservice_Sender_BS:GET_NUMBERS_Sender_CC&version=3.0;amp;Sender.Service=Webservice_Sender_BS;amp;Interface=urn%Apache
Sender business system: Webservice_Sender_BS
Sender CC: GET_NUMBERS_Sender_CC
Msg Interface: STU_GET_NUMBERS_Synch_MI
now we want to test from third party website, what are the things to be provided to the website developer to test the scenario.
the way i generated URL, is it correct?
if i provide above URL and generated WSDL in XI , is it enough for web developer to enter the input fields to RFC(r/3) via XI as webservice request and getting back response from RFC(r/3) to webservice via XI.
can you please advice if any body worked on this kind of scenario.
Thanks
Dhanush.

For the developer you have to provide WSDL file so that they know the input/output fields and write the code.
URL is correct.
Other informatino they required is Username and password of you PI system.
Gaurav Jain
Points if answer is helpful

RFC(WSDL) to SOAP sync scenario

Dear all,
My requirement is there is an RFC from ABAP that has to be exposed as WSDL and send it to some 3rd part sys take response and send it to RFC(abap).
How can this be achieved in 7.1/7.3,is there any difference .
I did not on work much on Soap scenario's.
Pls suggest.
Thanks

Since RFC is exposed as WSDL you can import that WSDL int the ESR to include request and response messages. Also create outbound(RFC) interface with the request and response message types. Similary you need to get WSDL for the receiver system. Import the WSDL IN ESR to create request and response message. Create inbound interface (receiver) using the receiver wsdl req,resp messages. since RFC Is exposed as WSDL, I think you can create soap sender for RFC and soap receiver for the target system synchronous. You can refer SDN for SOAP sender and receiver scenarios.
Refer SDN and also refer this [link|http://www.riyaz.net/sap/xipi-a-guide-to-using-sap-xi-soap-adapter/113/]

Soap to RFC synchronous scenario

Dear experts,
i am doing a SOAP to RFC(BAPI_INTERNALORDER_GETDETAIL) sync scenario and the rfc returns a structure with the records as well as the BAPIRET2 records .
Do i need to use fault message types here ?
If yes what would be its purpose in this scenario ?
Ravi

Hi,
if you have BAPIRET2 then all the errors will be over there
so I guess there is no need to use a fault message
Regards,
Michal Krawczyk

Error capturing SOAP fault for Sync Messages

Hi
We have a Sync interface which makes a Proxy call from ECC to PI and then PI makes Soap Sync call to Web application. We are having issues when handling Exceptions. Sender is getting misleading errors in response, even though they are application errors the proxy sender is getting error like MappingObjectNotFound.
When debug the PI system, PI is truncating error info when it return the reponse.
Below is the scenario of Synchronous interface:
ECC(Proxy) -> PI(Soap Receiver Adapter) -> MasterDataApp-(Webserver)
Below is the actual response from Webserver (Extracted via TCPGW sniffer):
<?xml version="1.0" encoding="utf-8"?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Body>
<soapenv:Fault>
<faultcode>soapenv:Server.userException</faultcode>
<faultstring>*java.rmi.RemoteException: No Messages Found*</faultstring>
<detail>
<ns1:hostname xmlns:ns1="http://xml.apache.org/axis/">hostname.com</ns1:hostname>
</detail>
</soapenv:Fault>
</soapenv:Body>
</soapenv:Envelope>
But PI receives this response payload like this :
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
<ns1:hostname xmlns:ns1="http://xml.apache.org/axis/">hostname.com</ns1:hostname>
and then Sync Request mesasge fails with below error because of the unexpected response payload as shown above:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="MAPPING">NO_MAPPINGPROGRAM_FOUND</SAP:Code>
<SAP:P1>Object ID B0CC6B27847A368AA04F4171EF6460F4 Software Component 86524CE0304911DEAE48CC6C83461631</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Mapping program is not available in runtime cache: Object ID B0CC6B27847A368AA04F4171EF6460F4 Software Component 86524CE0304911DEAE48CC6C83461631</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Also in the response message see this error message:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Category>Application</SAP:Category>
<SAP:Code area="UNKNOWN">APPLICATION_ERROR</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>application fault</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="http://xml.apache.org/axis/">hostname</SAP:ApplicationFaultMessage>
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Please let me for any clues how to handle this error response.
Thanks,
laxman

Hi Laxman,
SOAP Adapter cannot handle fault responses. I understand your issue. You even want to send the errorneous response from the Webservice as a payload back to the sender. But because of application error from Webservice, you are getting an error in the response message (Mapping Not found). SOAP Adapter cannot handle application error (i.e you will not get the errorneous response in form of payload) . For details please read below:
The receiver adapter expects a SOAP message as response. For synchrnous calls, a successful response should be returned with HTTP 200. In this case, the content of the SOAP body will be returned to the caller as the response payload. When some error occurs, the SOAP message may contain the SOAP fault element. In this case, when the fault detail element is not empty, its content will be returned as the fault payload in an application error message. For others, a system error message will be returned to the caller.
HTTP/1.1 200 OK
Content-Type: text/xml; charset="utf-8"
<SOAP:Envelope
xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP:Body>
<m:GetLastTradePriceResponse xmlns:m="Some-URI">
<Price>34.5</Price>
</m:GetLastTradePriceResponse>
</SOAP:Body>
</SOAP:Envelope>
will result in an application response message with response payload
<m:GetLastTradePriceResponse xmlns:m="Some-URI">
<Price>34.5</Price>
</m:GetLastTradePriceResponse>
HTTP/1.1 500 Internal Server Error
Content-Type: text/xml; charset="utf-8"
<SOAP:Envelope
xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP:Body>
<SOAP:Fault>
<faultcode>SOAP:MustUnderstand</faultcode>
<faultstring>SOAP Must Understand Error</faultstring>
</SOAP:Fault>
</SOAP:Body>
</SOAP:Envelope>
will result in a system error message.
HTTP/1.1 500 Internal Server Error
Content-Type: text/xml; charset="utf-8"
<SOAP:Envelope
xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP:Body>
<SOAP:Fault>
<faultcode>SOAP:Server</faultcode>
<faultstring>Server Error</faultstring>
<detail>
<e:myfaultdetails xmlns:e="Some-URI">
<message>My application didn't work</message>
<errorcode>1001</errorcode>
</e:myfaultdetails>
</detail>
</SOAP:Fault>
</SOAP:Body>
</SOAP:Envelope>
will result in an application error message with fault payload
<e:myfaultdetails xmlns:e="Some-URI">
<message>My application didn't work</message>
<errorcode>1001</errorcode>
</e:myfaultdetails>
In order to send the erroneous response as a payload to the sender, you should develop flow in below manner:
ECC(Proxy) -> PI --> ECC(Proxy)
In PI make a SOAP lookup. The response of the SOAP lookup will contain the response given by the WebService (it can be a vaid response or an application error in WebService). Now map this response to the proxy...In this way you can handle the application error msgs from webservice..
I hope this helps you...
Regards,
Rakesh Sharma

Error while executing the SOAP-XI-JDBC(syn) scenario

Dear Forum,
We have done SOAP-XI-JDBC(synch) scenario with out BPM.
When we sent the request data from EP to Oracle database through XI, we got an error,Runtime in Message-Mapping transformation~.
com.sap.aii.utilxi.misc.api.BaseRuntimeException: Runtime in Message-Mapping transformation: Cannot produce target element /ns:Customer/customers. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd at com.sap.aii.mappingtool.tf3.AMappingProgram.start(AMappingProgram.java:291)
Exception message says that it is a mapping issue. But we got the responce data from database along with this message.In message monitoring we got the message processed successfully.
Now i am not able to understanding why it throughs an error Runtime in Message-Mapping transformatio~ first time ?
Pls revert me to fulfill this task successfully.
Points will be rewarded.
Regards,
Naresh

Dear Friends,
Sorry for the delay,and Thank you for your quick responce.
Yes I got that message under trace option in SXMB_MONI,
Pls find the following msg structures and if any error please let me know status...
Soap request structure:
<?xml version="1.0" encoding="ISO-8859-1"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://soap2dbns" targetNamespace="http://soap2dbns">
<xsd:element name="soap_reqmt" type="soap_reqdt" />
<xsd:complexType name="soap_reqdt">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
5b474a34c8a511dc8d8e001a4bf038d4
</xsd:appinfo>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="Request" maxOccurs="unbounded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
49b1ae20c81211dcce03001b78afb958
</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="ORDERID" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
49b1ae21c81211dcc20d001b78afb958
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="Operation" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
49b1ae22c81211dc858a001b78afb958
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
Data base request structure:
<?xml version="1.0" encoding="ISO-8859-1"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://soap2dbns" targetNamespace="http://soap2dbns">
<xsd:element name="db_reqmt" type="db_reqdt" />
<xsd:complexType name="db_reqdt">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
5b4e7620c8a511dcc4fe001a4bf038d4
</xsd:appinfo>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="STATEMENTNAME" maxOccurs="unbounded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
fa204eb0bceb11dcbb54001b78b0798a
</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="FETCHDATA">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
fa204eb1bceb11dc9750001b78b0798a
</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="TABLE" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
fa204eb3bceb11dccc94001b78b0798a
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="access">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
fa204eb4bceb11dc9b35001b78b0798a
</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="ORDERID" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
fa204eb5bceb11dca20a001b78b0798a
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="ITEM" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
d0279840c81011dc8e4e001b78afb958
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="QUANTITY" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
d0279841c81011dcb8f4001b78afb958
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="PRICE" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
d0279842c81011dc832f001b78afb958
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="key">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
89f43170c81611dcc8fa001b78afb958
</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="ORDERID">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
89f43171c81611dcb6e3001b78afb958
</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:simpleContent>
<xsd:extension base="xsd:string">
<xsd:attribute name="compareOperation" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
89f43172c81611dccba5001b78afb958
</xsd:appinfo>
</xsd:annotation>
</xsd:attribute>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="action" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
fa204eb2bceb11dca298001b78b0798a
</xsd:appinfo>
</xsd:annotation>
</xsd:attribute>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
Soap Responce Structure:
<?xml version="1.0" encoding="ISO-8859-1"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://soap2dbns" targetNamespace="http://soap2dbns">
<xsd:element name="soap_resmt" type="soap_resdt" />
<xsd:complexType name="soap_resdt">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
8d49d494c8a411dc81f5001a4bf038d4
</xsd:appinfo>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="response" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
491ccd30bd0611dcb29d001b78b0798a
</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="row" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
491ccd31bd0611dca3d7001b78b0798a
</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="ORDERID" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
491ccd32bd0611dcc7d1001b78b0798a
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="ITEM" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
491ccd33bd0611dca6ad001b78b0798a
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="QUANTITY" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
491ccd34bd0611dc95a8001b78b0798a
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="PRICE" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
491ccd35bd0611dcc034001b78b0798a
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
Database responce Structure:
<?xml version="1.0" encoding="ISO-8859-1"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://soap2dbns" targetNamespace="http://soap2dbns">
<xsd:element name="db_resmt" type="db_resdt" />
<xsd:complexType name="db_resdt">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
8d3b7cb1c8a411dcb1d6001a4bf038d4
</xsd:appinfo>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="STATEMENTNAME_response" maxOccurs="unbounded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
adca3410bcfd11dcaf4c001b78b0798a
</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="row" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
adca3411bcfd11dc92d6001b78b0798a
</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="ORDERID" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
adca3412bcfd11dc92e8001b78b0798a
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="ITEM" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
adca3413bcfd11dc9f7a001b78b0798a
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="QUANTITY" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
adca3414bcfd11dcc6c4001b78b0798a
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="PRICE" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
adca3415bcfd11dca54c001b78b0798a
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
Regards,
Naresh

Soap -- XI -- IDOC/RFC scenario

Hello,
I have a jsp page that working in tomcat server.
I want to send values from jsp page to xi to r/3. I think it will have
soap-- xi -- IDOC/RFC scenario
Pls send me pdf /doc to implemet it
Regards

Hi,
Please Refer the Following Links
/people/shabarish.vijayakumar/blog/2006/03/23/rfc--xi--webservice--a-complete-walkthrough-part-1
/people/shabarish.vijayakumar/blog/2006/03/28/rfc--xi--webservice--a-complete-walkthrough-part-2
/people/siva.maranani/blog/2005/09/03/invoke-webservices-using-sapxi - Invoke Webservices using SAPXI
/people/siva.maranani/blog/2005/03/01/testing-xi-exposed-web-services
/people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step
https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/2131 [original link is broken] [original link is broken] [original link is broken] [original link is broken]
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/336365d3-0401-0010-9884-a651295aeaa9
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/336365d3-0401-0010-9884-a651295aeaa9
Regards
Khanna

Response from PI in SOAP to SOAP Scenario

Hi,
My scenario is Soap to SOAP sending purchase orders. they want acknowledgement from PI whether PI received the message or not in the form of SOAP response.
sender system not expecting the response after the message processing in receiver system, they are expecting the response when PI receives message from them.
As any way they receive HTTP200 OK acknowledgement is it necessary that to send the SOAP response from PI by developing BPM?
Is it a good way of doing it?
Is any other way of doing it?
Your suggestions will be helpful to me.
Thank you.
Santhi.

Hi Santhi,
Please refer to SAP Note 856597 - SOAP Adapter FAQ Question number 2
2. Sender Asynchronous Calls
o Q: What are the correct sender options for asynchronous calls?
When the client sends a SOAP message and checks if the response is
an HTTP 200 response message with an empty soap envelope or an HTTP
202 response message with no content, the quality of service with
AtLeastOnce can be realized. In this case, the client must resend
the message until such a successful response is returned. When the
message successfully accepted by the adapter, an HTTP 200 response
with an empty SOAP envelope or an HTTP 202 response message with no
content is returned.
You don't have to do anything. When an async message is sent, PI will either reply with a 200 with an empty SOAP Envelope or an HTTP 202 with no content . That will serve as your acknowledgement.
Regards,
Mark

SOAP to SOAP BPM scenario

Hi Experts,
Could you please tell me, how to do SOAP to SOAP scenario using BPM?
SOAP -> XI -> BPM ( Inside BPM two more SOAP Adapter call) -> SOAP.
1. Pass the request thro' SOAP to BPM
2. Call first SOAP Adpter.
3. Response of the first SOAP will be the input for the next SOAP adapter
4. Call second SOAP adapter.
5. Return the SOAP response
Regards
Sara
Message was edited by:
        Sara D

Message Interface
1. MI_SEND_SOAP_OUT           - (Out,Asyn : MT_BPM_SOAPRequest)
2. MI_SEND_SOAP_IN          - (In, Asyn : MT_BPM_SOAPResponse)
3. MI_BPM_Req_ABS_OUT          - (Abs,Asyn : MT_BPM_Receiver_SOAPRequest)
4. MI_BPM_Req_ABS_IN          - (Abs,Asyn : MT_BPM_Receiver_SOAPResponse)
5. MI_WS1_Service_ABS          - (Abs, Synch : OutMessage : MT_BPM_WS1_Request InMessage:MT_BPM_WS1_Response)
6. MI_WS2_Service_ABS          - (Abs, Synch : OutMessage : MT_BPM_WS2_Request InMessage:MT_BPM_WS2_Response)
Message Mapping
1. MM_BPM_SOAPRequest_To_BPM_RecSOAPRequest ( Source: MT_BPM_SOAPRequest Target :MT_BPM_Receiver_SOAPRequest)
2. MM_BPM_RecSOAPRequest_To_BPM_WS1Request ( Source: MT_BPM_Receiver_SOAPRequest Target :MT_BPM_WS1_Request)
3. MM_BPM_WS1Response_To_BPM_WS2Request     ( Source: MT_BPM_WS1_Response Target :MT_BPM_WS2_Request)
4. MM_BPM_WS2Response_To_BPM_RecSOAPResponse( Source: MT_BPM_WS2_Response Target :MT_BPM_Receiver_SOAPResponse)
5. MM_BPM_RecSOAPResponse_To_BPM_SOAPResponse( Source: MT_BPM_Receiver_SOAPRespons Target :MT_BPM_SOAPResponse)
Could you please tell me, whether the above objects are correct for this scenario?
Regards
Sara
Regards
Sara
Message was edited by:
        Sara D
Message was edited by:
        Sara D

SOAP FTP SOAP Sync Scenario

Similar Messages

Maybe you are looking for