PARSING ADAPTER.SOAP_EXCEPTION
Hi,
I am Integrating Sap(RFC) with Webservice(Soap) using XI.
I uploaded the FM and Wsdl file.
For Wsdl I created Message Interface having Inbound Asychronous.
I have done mapping,Interface mapping and Activated.
For ID Part I am Using Two Business System , 1 for Sender and 1 for Receiver.
I created Sender Communication channel and Receiver communication Channel,
SenderAgreement,Receiver Determination,Interface Determination,Receiver Agreement.
Then Activated.
I Executed the Scenario It is throwing Error in RWB as
PARSING>>>>>>>ADAPTER.SOAP_EXCEPTION .
Wat it means.
I am Going The Scenario for Webservice Receiver for the First Time.
Points will be awarded for the answer.
Hi
Look into this Blog
/people/shabarish.vijayakumar/blog/2006/03/23/rfc--xi--webservice--a-complete-walkthrough-part-1
Also these threads might help u
SOAP Adapter Exception
SOAP Adapter Exception
SOAP adapter exception
SOAP receiver exception problem
Issue with SOAP Adapter calling a Web Service
error in connecting to sender soap adapter
http://help.sap.com/saphelp_nw2004s/helpdata/en/29/5bd93f130f9215e10000000a155106/content.htm
**********Reward points if usefullll***********
Similar Messages
-
Hi All,
We have a scenario of FTP-->PI---> Webservice. While triggering the data in the FTP, it is failing in the PI with the below error
SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server was unable to read request. ---> There is an error in XML document (1, 447). ---> Input string was not in a correct format.
Can you please help?Hi Raja- It seems to be a data quality issue.
Check for the value @ 1447 position in the xml message that you are trying to send to web service..
may be a date filed/decimal value which is not in expected format. -
XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault
Hi Experts,
I am trying to create a scenario SOAP to SOAP through AAE. There is no mapping involved.
Sender is a 3rd Party application and receiver is SAP BusinessObjects [BI].
Following error is coming when posting the message from SOAPUI or through integration engine.
Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: String index out of range: 0
I have done following workaround.
1) I tried the message flow through AAE, but same error in the channel
2) I checked creating a one to one mapping with soap fault message. Still the same error.
3) "XMBWS.NoSOAPIgnoreStatusCode = true" in module tab -> Module configuration
When I tried this mentioned option, the message is passing through the channel but the passing blank empty payload.
I have checked following links.
http://forums.sdn.sap.com/thread.jspa?threadID=156305
http://forums.sdn.sap.com/thread.jspa?threadID=2111959
http://forums.sdn.sap.com/thread.jspa?threadID=1675917&tstart=0
Any pointers on this subject will be very much helpful
Thanks
Ray..Hello,
Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: String index out of range: 0
When I tried this mentioned option, the message is passing through the channel but the passing blank empty payload.
Probably because the return is blank. If this is expected, can you just use Java Mapping to parse the blank response?
Hope this helps,
Mark -
XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: No such operation
Hi,
I am doing a SOAP - PI - SOAP scenario.
When I tested my scenario, I am getting this error in wsnavigator:
Web service returned error. Fault code: "(http://schemas.xmlsoap.org/soap/envelope/)Server" Fault String: "Server Error".
When I checked in SXMB_MONI, I get this error in the response message:
<SAP:AdditionalText>com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: No such operation</SAP:AdditionalText>
I searched thru the forums but I am not finding this similar issue.
"no such operation" issues posted here usually have an operation name after.
I would appreciate your help.
Thanks,
maeHI
WSDL is having some problem
When you imported this wsdl how many messages does it show. Check weather it is having SETCOMPANYFIELDVALUE request and response. you can check the messages carried in a wsdl using the messages tab in external definition.
Thanks -
C4C Integration issue XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault
Hi All,
Scenario: ECC to C4C
I am getting below error while pushing message to C4C using SOAP channel with Http Protocol.
SOAP channel has been configured with SSL Authentication.
Regards,
ManiHi Manikandan,
Use TCPGW tool to see the response from C4C, it is very useful for trouble shooting this kind of errors.
Troubleshooting SOAP, HTTP and Mail Adapter Scenarios with TCPGateway
Regards,
Praveen. -
ADAPTER.SOAP_EXCEPTION Error while posting data on webservice.
Hi.
I have IDOC-> SOAP -> IDOC Synchronous Scenario.
I have uploaded WSDL of the webservice for mapping.
Data is not posting on Webservice.
it is giving me Following error.
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="PARSING">ADAPTER.SOAP_EXCEPTION</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>soap fault: Server was unable to process request. ---> Object reference not set to an instance of an object.</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
When i checked Call Adapter Outboundbinding..
<SAP:OutboundBindingAttributes>
- <SAP:AdapterTypeData xmlns:SAP="http://sap.com/xi/XI/Message/30">
- <SAP:Attribute>
<SAP:Name>verifyWsuTimestampMessageAge_SecurityProfileWSSEVerifyEncryptionBodyThenSignatureBodyResponse</SAP:Name>
<SAP:Value />
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>applyEncryptionKeyStore</SAP:Name>
<SAP:Value />
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>applyEncryptionKeyStoreAlias_SecurityProfileWSSEApplyEncryptionBody</SAP:Name>
<SAP:Value />
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>WSSEProfileApply</SAP:Name>
<SAP:Value>SecurityProfileWSSEApplySignatureBody</SAP:Value>
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>applyEncryptionEncryptionSignatureAlias</SAP:Name>
<SAP:Value />
</SAP:Attribute>
I found this entry..
Is there any problem in outbound binding.
Kindly guide me for same.
Regards,
SiyaThanks Stefan.
Yes, sender agreement is there and it is also there in CPA Cache.
CPAObject: (Binding) keys: ObjectId=02cb8f5717cc35e582f072b26138a0f8 values: Direction=I
ActionNamespace=http://test.com/xi/POC ToParty= FromParty= HeaderMappingConfig=null MappedActionNamespace=null MappingClassName=null ActionName=os_test AdapterNamespace=http://sap.com/xi/XI/System MappedActionName=null ToService= AdapterSWCV=b38bcd00e47111d7afacde420a1145a5 FromService=temp AdapterType=SOAP MappingId=null Attributes=<?xml version="1.0" encoding ...
http://sapxis:50000/XIAxisAdapter/MessageServlet page also shows the status OK for required components and Warning for optional components.
Am I missing something?
Thanks,
Beena. -
Hi,
i got the following error when calling webservice. i've experienced webservice in using XI, but i do not know this situation. please help me!!
receiver soap adapter i've set as below;
connection parameter : http://60.7.103.210:8011/RuleInvokerEJBwar/RuleInvokerWS
soap action : executeRulesFI01
===========================================================
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Call Adapter
-->
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="PARSING">ADAPTER.SOAP_EXCEPTION</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>soap fault: Unable to find a matching Operation for this remote invocation <ns1:ruleInvokerVOFI01s xmlns:ns1="http://www.cc.com/RuleInvokerWS/javaclass"> <ns2:RuleInvokerVOFI01 xmlns:ns2="java:com.sds.approval.biz.invoker.ejb.vo"> <ns2:approvalService xmlns:ns2="java:com.sds.approval.biz.invoker.ejb.vo"> </ns2:approvalService> <ns2:budgetExceedYn xmlns:ns2="java:com.sds.approval.biz.invoker.ejb.vo">N</ns2:budgetExceedYn> <ns2:categoryCode xmlns:ns2="java:com.sds.approval.biz.invoker.ejb.vo">E3</ns2:categoryCode> <ns2:categoryDetailCode xmlns:ns2="java:com.sds.approval.biz.invoker.ejb.vo">01</ns2:categoryDetailCode> <ns2:deptAttrCode xmlns:ns2="java:com.sds.approval.biz.invoker.ejb.vo"> </ns2:deptAttrCode> <ns2:deptPjtAttrCode xmlns:ns2="java:com.sds.approval.biz.invoker.ejb.vo">02</ns2:deptPjtAttrCode> <ns2:deptPjtCode xmlns:ns2="java:com.sds.approval.biz.invoker.ejb.vo"> </ns2:deptPjtCode> <ns2:pjtAttrCode xmlns:ns2="java:com.sds.approval.biz.invoker.ejb.vo"> </ns2:pjtAttrCode> <ns2:pmEmpNo xmlns:ns2="java:com.sds.approval.biz.invoker.ejb.vo">00000000</ns2:pmEmpNo> <ns2:reporterEmpNo xmlns:ns2="java:com.sds.approval.biz.invoker.ejb.vo">51</ns2:reporterEmpNo> <ns2:reporterJikgubCode xmlns:ns2="java:com.sds.approval.biz.invoker.ejb.vo">A</ns2:reporterJikgubCode> </ns2:RuleInvokerVOFI01> </ns1:ruleInvokerVOFI01s>. Please check your operation name.</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
wsdl information..
=========================================================
<?xml version="1.0" encoding="UTF-8" ?>
- <definitions xmlns:tns="http://www.cc.com/RuleInvokerWS/javaclass" xmlns:wsr="http://www.openuri.org/2002/10/soap/reliability/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:soap12enc="http://www.w3.org/2003/05/soap-encoding" xmlns:conv="http://www.openuri.org/2002/04/wsdl/conversation/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns="http://schemas.xmlsoap.org/wsdl/" targetNamespace="http://www.cc.com/RuleInvokerWS/javaclass">
- <types xmlns:tns="http://www.cc.com/RuleInvokerWS/javaclass" xmlns:wsr="http://www.openuri.org/2002/10/soap/reliability/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:soap12enc="http://www.w3.org/2003/05/soap-encoding" xmlns:conv="http://www.openuri.org/2002/04/wsdl/conversation/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns="http://schemas.xmlsoap.org/wsdl/">
- <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:stns="java:com.sds.approval.biz.invoker.ejb.vo" elementFormDefault="qualified" attributeFormDefault="qualified" targetNamespace="java:com.sds.approval.biz.invoker.ejb.vo">
- <xsd:complexType name="ArrayOfRuleInvokerVOCO01">
- <xsd:sequence>
<xsd:element type="stns:RuleInvokerVOCO01" name="RuleInvokerVOCO01" minOccurs="0" nillable="true" maxOccurs="unbounded" />
</xsd:sequence>
</xsd:complexType>
- <xsd:complexType name="ArrayOfRuleInvokerVOFI01">
- <xsd:sequence>
<xsd:element type="stns:RuleInvokerVOFI01" name="RuleInvokerVOFI01" minOccurs="0" nillable="true" maxOccurs="unbounded" />
</xsd:sequence>
</xsd:complexType>
- <xsd:complexType name="ArrayOfRuleInvokerVOFI02">
- <xsd:sequence>
<xsd:element type="stns:RuleInvokerVOFI02" name="RuleInvokerVOFI02" minOccurs="0" nillable="true" maxOccurs="unbounded" />
</xsd:sequence>
</xsd:complexType>
- <xsd:complexType name="ArrayOfRuleInvokerVOITO01">
- <xsd:sequence>
<xsd:element type="stns:RuleInvokerVOITO01" name="RuleInvokerVOITO01" minOccurs="0" nillable="true" maxOccurs="unbounded" />
</xsd:sequence>
</xsd:complexType>
- <xsd:complexType name="ArrayOfRuleInvokerVOMM01">
- <xsd:sequence>
<xsd:element type="stns:RuleInvokerVOMM01" name="RuleInvokerVOMM01" minOccurs="0" nillable="true" maxOccurs="unbounded" />
</xsd:sequence>
</xsd:complexType>
- <xsd:complexType name="ArrayOfRuleInvokerVOMM02">
- <xsd:sequence>
<xsd:element type="stns:RuleInvokerVOMM02" name="RuleInvokerVOMM02" minOccurs="0" nillable="true" maxOccurs="unbounded" />
</xsd:sequence>
</xsd:complexType>
- <xsd:complexType name="ArrayOfRuleInvokerVOPS01">
- <xsd:sequence>
<xsd:element type="stns:RuleInvokerVOPS01" name="RuleInvokerVOPS01" minOccurs="0" nillable="true" maxOccurs="unbounded" />
</xsd:sequence>
</xsd:complexType>
- <xsd:complexType name="ArrayOfRuleInvokerVOPS02">
- <xsd:sequence>
<xsd:element type="stns:RuleInvokerVOPS02" name="RuleInvokerVOPS02" minOccurs="0" nillable="true" maxOccurs="unbounded" />
</xsd:sequence>
</xsd:complexType>
- <xsd:complexType name="ArrayOfRuleInvokerVOSD01">
- <xsd:sequence>
<xsd:element type="stns:RuleInvokerVOSD01" name="RuleInvokerVOSD01" minOccurs="0" nillable="true" maxOccurs="unbounded" />
</xsd:sequence>
</xsd:complexType>
- <xsd:complexType name="RuleInvokerVOCO01">
+ <xsd:sequence>
<xsd:element type="xsd:string" name="amt" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="approvalService" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="assignAccountYn" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="budgetExceedYn" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="budgetUseCode" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="categoryCode" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="deptAttrCode" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="deptPjtAttrCode" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="deptPjtCode" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="execPreBsneStepAttrCode" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="pmEmpNo" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="reporterEmpNo" minOccurs="1" nillable="true" maxOccurs="1" />
</xsd:sequence>
</xsd:complexType>
- <xsd:complexType name="RuleInvokerVOFI01">
- <xsd:sequence>
<xsd:element type="xsd:string" name="approvalService" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="budgetExceedYn" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="categoryCode" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="categoryDetailCode" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="deptAttrCode" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="deptPjtAttrCode" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="deptPjtCode" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="pjtAttrCode" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="pmEmpNo" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="reporterEmpNo" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="reporterJikgubCode" minOccurs="1" nillable="true" maxOccurs="1" />
</xsd:sequence>
</xsd:complexType>
- <xsd:complexType name="RuleInvokerVOFI02">
- <xsd:sequence>
<xsd:element type="xsd:string" name="amt" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="approvalService" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="categoryCode" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="costItemCode" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="deptPjtAttrCode" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="deptPjtCode" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="execPreBsneStepAttrCode" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="forwardYn" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="monthAttrCode" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="pmEmpNo" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="reporterEmpNo" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="standardDeptYn" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="unusualDeptYn" minOccurs="1" nillable="true" maxOccurs="1" />
</xsd:sequence>
</xsd:complexType>
- <xsd:complexType name="RuleInvokerVOITO01">
- <xsd:sequence>
<xsd:element type="xsd:string" name="approvalService" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="categoryCode" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="categoryDetailCode" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="clientDeptCode" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="deptPjtCode" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="reporterEmpNo" minOccurs="1" nillable="true" maxOccurs="1" />
</xsd:sequence>
</xsd:complexType>
- <xsd:complexType name="RuleInvokerVOMM01">
- <xsd:sequence>
<xsd:element type="xsd:string" name="amt" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="approvalService" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="assoOrgYn" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="categoryCode" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="deptPjtAttrCode" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="deptPjtCode" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="inoutYn" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="purchaseDeptCode" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="reporterEmpNo" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="requestEmpNo" minOccurs="1" nillable="true" maxOccurs="1" />
</xsd:sequence>
</xsd:complexType>
- <xsd:complexType name="RuleInvokerVOMM02">
- <xsd:sequence>
<xsd:element type="xsd:string" name="amt" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="approvalService" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="categoryCode" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="deptPjtCode" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="purchaseDeptCode" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="reposterEmpNo" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="requestCode" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="requestEmpNo" minOccurs="1" nillable="true" maxOccurs="1" />
</xsd:sequence>
</xsd:complexType>
- <xsd:complexType name="RuleInvokerVOPS01">
- <xsd:sequence>
<xsd:element type="xsd:string" name="approvalService" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="architManInvestYn" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="architcentBelongDeptCode" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="bsnePrsntEmpNo" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="categoryCode" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="ctrlExceedAmt" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="deptPjtCode" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="execBndPrftRate" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="execPmEmpNo" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="matrExceedAmt" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="notCtrlExceedAmt" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="orderBndPrftRate" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="orderDeptCode" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="orderModProgressYn" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="pdctManInvestYn" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="pdctinndivBelongDeptCode" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="pmEmpNo" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="postPmEmpNo" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="saleDeptCode" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="serviceLineCode" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="vrbYn" minOccurs="1" nillable="true" maxOccurs="1" />
</xsd:sequence>
</xsd:complexType>
- <xsd:complexType name="RuleInvokerVOPS02">
- <xsd:sequence>
<xsd:element type="xsd:string" name="approvalService" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="budget" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="budgetExceedYn" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="costDeptAttrYn" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="costDeptCode" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="deptPjtCode" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="execDeptCode" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="ipjtAttrCode" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="mgrPlanLinkYn" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="owrspDeptCode" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="pmEmpNo" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="vaCodeYn" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="vfCodeYn" minOccurs="1" nillable="true" maxOccurs="1" />
</xsd:sequence>
</xsd:complexType>
- <xsd:complexType name="RuleInvokerVOSD01">
- <xsd:sequence>
<xsd:element type="xsd:string" name="afterActivityEmpNo" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="approvalService" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="architManInvestYn" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="architcentBelongDeptCode" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="bsneAttrCode" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="bsneDeptCode" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="bsnePrsntEmpNo" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="categoryCode" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="clientInoutAttrCode" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="deptPjtCode" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="gukpanExportAttrCode" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="manRequestAttrCode" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="newSjtYn" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="pdctManInvestYn" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="pdctinndivBelongDeptCode" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="proposalPmEmpNo" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="reporterEmpNo" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="saleDeptCode" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="serviceLineCode" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="vrbYn" minOccurs="1" nillable="true" maxOccurs="1" />
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
- <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:stns="java:com.sds.approval.biz.dao" elementFormDefault="qualified" attributeFormDefault="qualified" targetNamespace="java:com.sds.approval.biz.dao">
- <xsd:complexType name="ApprovalUserInfo">
- <xsd:sequence>
<xsd:element type="xsd:string" name="apprEmpDeptCode" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="apprEmpDeptName" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="apprEmpEmailAddr" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="apprEmpHname" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="apprEmpJikchakCode" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="apprEmpJikchakName" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="apprEmpJikwiCode" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="apprEmpJikwiName" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="apprEmpNo" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="apprEmpResNo" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="apprItemTypeCode" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="apprItemTypeName" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="apprOrgEmpNo" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="apprRepYn" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="xsd:int" name="apprSeq" minOccurs="1" maxOccurs="1" />
<xsd:element type="xsd:string" name="apprService" minOccurs="1" nillable="true" maxOccurs="1" />
</xsd:sequence>
</xsd:complexType>
- <xsd:complexType name="ArrayOfApprovalUserInfo">
- <xsd:sequence>
<xsd:element type="stns:ApprovalUserInfo" name="ApprovalUserInfo" minOccurs="0" nillable="true" maxOccurs="unbounded" />
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
</types>
- <message name="executeRulesCO01">
<part xmlns:partns="java:com.sds.approval.biz.invoker.ejb.vo" type="partns:ArrayOfRuleInvokerVOCO01" name="ruleInvokerVOCO01s" />
</message>
- <message name="executeRulesCO01Response">
<part xmlns:partns="java:com.sds.approval.biz.dao" type="partns:ArrayOfApprovalUserInfo" name="result" />
</message>
- <message name="executeRulesFI01">
<part xmlns:partns="java:com.sds.approval.biz.invoker.ejb.vo" type="partns:ArrayOfRuleInvokerVOFI01" name="ruleInvokerVOFI01s" />
</message>
- <message name="executeRulesFI01Response">
<part xmlns:partns="java:com.sds.approval.biz.dao" type="partns:ArrayOfApprovalUserInfo" name="result" />
</message>
- <message name="executeRulesFI02">
<part xmlns:partns="java:com.sds.approval.biz.invoker.ejb.vo" type="partns:ArrayOfRuleInvokerVOFI02" name="ruleInvokerVOFI02s" />
</message>
- <message name="executeRulesFI02Response">
<part xmlns:partns="java:com.sds.approval.biz.dao" type="partns:ArrayOfApprovalUserInfo" name="result" />
</message>
- <message name="executeRulesITO01">
<part xmlns:partns="java:com.sds.approval.biz.invoker.ejb.vo" type="partns:ArrayOfRuleInvokerVOITO01" name="ruleInvokerVOITO01s" />
</message>
- <message name="executeRulesITO01Response">
<part xmlns:partns="java:com.sds.approval.biz.dao" type="partns:ArrayOfApprovalUserInfo" name="result" />
</message>
- <message name="executeRulesMM01">
<part xmlns:partns="java:com.sds.approval.biz.invoker.ejb.vo" type="partns:ArrayOfRuleInvokerVOMM01" name="ruleInvokerVOMM01s" />
</message>
- <message name="executeRulesMM01Response">
<part xmlns:partns="java:com.sds.approval.biz.dao" type="partns:ArrayOfApprovalUserInfo" name="result" />
</message>
- <message name="executeRulesMM02">
<part xmlns:partns="java:com.sds.approval.biz.invoker.ejb.vo" type="partns:ArrayOfRuleInvokerVOMM02" name="ruleInvokerVOMM02s" />
</message>
- <message name="executeRulesMM02Response">
<part xmlns:partns="java:com.sds.approval.biz.dao" type="partns:ArrayOfApprovalUserInfo" name="result" />
</message>
- <message name="executeRulesPS01">
<part xmlns:partns="java:com.sds.approval.biz.invoker.ejb.vo" type="partns:ArrayOfRuleInvokerVOPS01" name="ruleInvokerVOPS01s" />
</message>
- <message name="executeRulesPS01Response">
<part xmlns:partns="java:com.sds.approval.biz.dao" type="partns:ArrayOfApprovalUserInfo" name="result" />
</message>
- <message name="executeRulesPS02">
<part xmlns:partns="java:com.sds.approval.biz.invoker.ejb.vo" type="partns:ArrayOfRuleInvokerVOPS02" name="ruleInvokerVOPS02s" />
</message>
- <message name="executeRulesPS02Response">
<part xmlns:partns="java:com.sds.approval.biz.dao" type="partns:ArrayOfApprovalUserInfo" name="result" />
</message>
- <message name="executeRulesSD01">
<part xmlns:partns="java:com.sds.approval.biz.invoker.ejb.vo" type="partns:ArrayOfRuleInvokerVOSD01" name="ruleInvokerVOSD01s" />
</message>
- <message name="executeRulesSD01Response">
<part xmlns:partns="java:com.sds.approval.biz.dao" type="partns:ArrayOfApprovalUserInfo" name="result" />
</message>
- <portType name="RuleInvokerWSPort">
- <operation name="executeRulesCO01">
<input message="tns:executeRulesCO01" />
<output message="tns:executeRulesCO01Response" />
</operation>
- <operation name="executeRulesFI01">
<input message="tns:executeRulesFI01" />
<output message="tns:executeRulesFI01Response" />
</operation>
- <operation name="executeRulesFI02">
<input message="tns:executeRulesFI02" />
<output message="tns:executeRulesFI02Response" />
</operation>
- <operation name="executeRulesITO01">
<input message="tns:executeRulesITO01" />
<output message="tns:executeRulesITO01Response" />
</operation>
- <operation name="executeRulesMM01">
<input message="tns:executeRulesMM01" />
<output message="tns:executeRulesMM01Response" />
</operation>
- <operation name="executeRulesMM02">
<input message="tns:executeRulesMM02" />
<output message="tns:executeRulesMM02Response" />
</operation>
- <operation name="executeRulesPS01">
<input message="tns:executeRulesPS01" />
<output message="tns:executeRulesPS01Response" />
</operation>
- <operation name="executeRulesPS02">
<input message="tns:executeRulesPS02" />
<output message="tns:executeRulesPS02Response" />
</operation>
- <operation name="executeRulesSD01">
<input message="tns:executeRulesSD01" />
<output message="tns:executeRulesSD01Response" />
</operation>
</portType>
- <binding type="tns:RuleInvokerWSPort" name="RuleInvokerWSPort">
<soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http" />
- <operation name="executeRulesCO01">
<soap:operation style="rpc" soapAction="" />
- <input>
<soap:body namespace="http://www.cc.com/RuleInvokerWS/javaclass" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="encoded" />
</input>
- <output>
<soap:body namespace="http://www.cc.com/RuleInvokerWS/javaclass" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="encoded" />
</output>
</operation>
- <operation name="executeRulesFI01">
<soap:operation style="rpc" soapAction="" />
- <input>
<soap:body namespace="http://www.cc.com/RuleInvokerWS/javaclass" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="encoded" />
</input>
- <output>
<soap:body namespace="http://www.cc.com/RuleInvokerWS/javaclass" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="encoded" />
</output>
</operation>
- <operation name="executeRulesFI02">
<soap:operation style="rpc" soapAction="" />
- <input>
<soap:body namespace="http://www.cc.com/RuleInvokerWS/javaclass" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="encoded" />
</input>
- <output>
<soap:body namespace="http://www.cc.com/RuleInvokerWS/javaclass" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="encoded" />
</output>
</operation>
- <operation name="executeRulesITO01">
<soap:operation style="rpc" soapAction="" />
- <input>
<soap:body namespace="http://www.cc.com/RuleInvokerWS/javaclass" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="encoded" />
</input>
- <output>
<soap:body namespace="http://www.cc.com/RuleInvokerWS/javaclass" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="encoded" />
</output>
</operation>
- <operation name="executeRulesMM01">
<soap:operation style="rpc" soapAction="" />
- <input>
<soap:body namespace="http://www.cc.com/RuleInvokerWS/javaclass" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="encoded" />
</input>
- <output>
<soap:body namespace="http://www.cc.com/RuleInvokerWS/javaclass" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="encoded" />
</output>
</operation>
- <operation name="executeRulesMM02">
<soap:operation style="rpc" soapAction="" />
- <input>
<soap:body namespace="http://www.cc.com/RuleInvokerWS/javaclass" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="encoded" />
</input>
- <output>
<soap:body namespace="http://www.cc.com/RuleInvokerWS/javaclass" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="encoded" />
</output>
</operation>
- <operation name="executeRulesPS01">
<soap:operation style="rpc" soapAction="" />
- <input>
<soap:body namespace="http://www.cc.com/RuleInvokerWS/javaclass" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="encoded" />
</input>
- <output>
<soap:body namespace="http://www.cc.com/RuleInvokerWS/javaclass" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="encoded" />
</output>
</operation>
- <operation name="executeRulesPS02">
<soap:operation style="rpc" soapAction="" />
- <input>
<soap:body namespace="http://www.cc.com/RuleInvokerWS/javaclass" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="encoded" />
</input>
- <output>
<soap:body namespace="http://www.cc.com/RuleInvokerWS/javaclass" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="encoded" />
</output>
</operation>
- <operation name="executeRulesSD01">
<soap:operation style="rpc" soapAction="" />
- <input>
<soap:body namespace="http://www.cc.com/RuleInvokerWS/javaclass" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="encoded" />
</input>
- <output>
<soap:body namespace="http://www.cc.com/RuleInvokerWS/javaclass" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="encoded" />
</output>
</operation>
</binding>
- <service name="RuleInvokerWS">
- <port name="RuleInvokerWSPort" binding="tns:RuleInvokerWSPort">
<soap:address location="http://60.7.103.210:8011/RuleInvokerEJBwar/RuleInvokerWS" />
</port>
</service>
</definitions>Hi Ogawa,
First of all check the URL in your receiver SOAP adapter. The error comes from the web service server. It says that the request message is wrong.
U have to fill field SOAPAction in the receiver soap adapter
U may find the related information here
http://help.sap.com/saphelp_nw2004s/helpdata/en/29/5bd93f130f9215e10000000a155106/content.htm
Please check this
/people/shabarish.vijayakumar/blog/2006/03/23/rfc--xi--webservice--a-complete-walkthrough-part-1
There are multiple soap actions listed there.
Regards,
Prateek -
ADAPTER.SOAP_EXCEPTION:Maximum request length exceeded.
Hi frnds,
Plz look for the error i am getting when sending large record...
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="PARSING">ADAPTER.SOAP_EXCEPTION</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>soap fault: System.Web.Services.Protocols.SoapException: There was an exception running the extensions specified in the config file. ---> System.Web.HttpException: Maximum request length exceeded. at System.Web.HttpRequest.GetEntireRawContent() at System.Web.HttpRequest.get_InputStream() at System.Web.Services.Protocols.SoapServerProtocol.Initialize() --- End of inner exception stack trace --- 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)</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
What could be the possible solution .
Thanks,
AdhirHi Ahdir,
First of all check the URL in your receiver SOAP adapter. The error comes from the web service server. It says that the request message is wrong.
U have to fill field SOAPAction in the receiver soap adapter
U may find the related information here
http://help.sap.com/saphelp_nw2004s/helpdata/en/29/5bd93f130f9215e10000000a155106/content.htm
Please check this
/people/shabarish.vijayakumar/blog/2006/03/23/rfc--xi--webservice--a-complete-walkthrough-part-1
There are multiple soap actions listed there.
Regards,
Divya -
Receiver soap : Error ADAPTER.SOAP_EXCEPTION
Hi all,
My Scenario is IDOC -> XI -> WEBSERVICE using BPM & SOAP adaptor.
when i send idoc from R/3 it is going Xi
From Xi to web service using WSDL Request message .it is not reach to web service(connection is ok but wsdl request massage is not going properly) .
sxmb-moni :error is
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Inbound Message
-->
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="PARSING">ADAPTER.SOAP_EXCEPTION</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>soap fault: com.sap.webservice.SchemeTopupDeliveryService</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
<SAP:AdditionalText>soap fault: com.sap.webservice.SchemeTopupDeliveryService</SAP:AdditionalText> : this service is not related to my service (It is showing wrong service name)
Pleas tell me where error is happenedthis service is not related to my service (It is showing wrong service name)
This is the reason, you somehow call the wrong web service. But are you talking about BI or XI here?
Best regards
Dirk -
ADAPTER.SOAP_EXCEPTION : soap fault: No such operation
Hi Experts,
I have done File to Webservice scenario. When I am trying to execute the scenario I am getting the following error.
<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="PARSING">ADAPTER.SOAP_EXCEPTION</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>soap fault: No such operation 'InventoryRequest'</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
My receiver SOAP adapter is showing inactive in communication channel monitoring. But I check one of the forum people are saying it is showing like that only until we execute the scenario. Is it correct.
I have checked the webservice for "InventoryRequest" soapAction but in my webservice all soapActions are just empty.As follows
<operation name="InventoryStatus">
<wsdlsoap:operation soapAction="" />
<input name="InventoryRequest">
Is it problem with weservice or my configuration. Please suggest me
Regards
SowmyaHi
In configurator if I check the "Do Not Use Soap Envelope" I am gettin "Internal Error 500"
If i dont check that check box I am getting the following error
soap fault: No such operation 'InventoryRequest'
But I didn't specify anything in soapAction.
Could you please tell me how to resolve this issue
I have chec the url from browser it is wroking..
Thanks & Regards
Sowmya -
Email Parsing Adapter
An interesting idea - what about an email parsing adapter? It would be too cool to have an email agent that was configurable by email account (pop, smtp, etc.) and typical account settings, that could skim emails for name value pairs or something similar. Not sure how it would be configured, but the idea being that you could accept changes to services based on emails into a specific email box (comments, updates of tasks, etc.)eGain seems pretty robust (though we aren't using it and I don't know much about it, so that's not an official endorsement), but I don't know that I'm talking about a full-scale enterprise application integration, but rather something simple - a basic, configurable, email parsing agent with a couple of options so that it can support diffent types of email environments.
-
Adapter.soap_exception (parsing error) in sxi_monitor
Hello everyone.
I am getting the next error in the TC sxi_monitor when Im sending an Idoc:
soap fault: Server did not recognize the value of HTTP Header SOAPAction: http://wsceresdes/WSCeres/AsientoInsert/Servicio.asmx
I have changed the *.asmx file (external definition) that this interface uses, because they add one node in the xml receiver, and then I mapped it.
This idoc goes from Sap to non sap system.
I cheked the mapping result and there isnt any error, its all working fine.
What am I missing? Where is the problem?
Edited by: Claudio Carrer on Oct 8, 2008 8:32 PMYou have a SOAP receiver channel and you have put a parameter SOAPAction which is not valid.
Figure out, which SOAPAction you really need and put that value. You find the SOAP action in the WSDL in an attribute with same name.
Regards
Stefan -
SOAP_EXCEPTION - Value cannot be null. Parameter name: s
Hi All,
I'm getting the following error whicle executing my soap scenaraio.
"Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server was unable to process request. ---> Value cannot be null. Parameter name: s"
Its IDOC to SOAP scenario.
can some one tell me what might be missing. its not anything to with the data, as we tried extracting the output message from moni and using in the application and it works. we also tried sending a blank idoc and the error is same. so, conclusion is the parameter is not any data in the message but something to do with the soap message setting.
any help will be greatly appreciated.Hi suraj,
i tried opening the url in ie and manually uploading the payload. its all works perfect. error comes only when sent via XI.
the paramets are:
Receiver SOAP
Transport protocol: HTTP
Message protocol: SOAP 1.1
Connection parameters
Target URL: http://**..*.*/XIDynExchange.asmx
no check box checked
Security prameters
not checked
Conversion parameter
no checkbox checked
soap action: http://***.org/SendXMLMsgSA
No advance setting done
what might have gone wrong?
Regards,
Rashmi -
Error in SOAP Adapter Response
I am getting the following Error in SOAP Response
... but when i tried the with ALTOVA XML SPY its working fine..
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Inbound Message
-->
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="PARSING">ADAPTER.SOAP_EXCEPTION</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>soap fault: Registration Method error</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>hi,
check the XML that you send to the WS
if the server returned this soap fault it might mean that XML was not correct .
also take a look at the default.trc log file from visual administrator-> server -> services -> log viewer -> locations -> com -> aii -> bc -> soap
regards
kummari
Edited by: kummari on Jul 29, 2008 5:40 AM -
SOAP Header in SOAP Receiver adapter
Hi All,
I am doing a Proxy to Webservice scenario where webservice requires the SOAP request as below.
<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP-ENV:Header>
<mh:CustomHeader xmlns:mh="http://schemas.test.com/customHeader">
<mh:MessageData>
<mh:MessageId>12345</mh:MessageId>
<mh:Timestamp>2004-06-09T14:41:44Z</mh:Timestamp>
</mh:MessageData>
</mh:CustomHeader>
<wsse:Security xmlns:wsse="http://schemas.xmlsoap.org/ws/2002/04/secext">
<wsse:UsernameToken>
<wsse:Username>test</wsse:Username>
<wsse:Password>test123</wsse:Password>
</wsse:UsernameToken>
</wsse:Security>
</SOAP-ENV:Header>
<SOAP-ENV:Body>
</SOAP-ENV:Body>
Need your help to understand how can we achieve this using Standard SOAP adapter to customize the Header part as it requires to include "<mh:CustomHeader " & "UsernameToken".
Or Do i need to go for adapter module development to create this SOAP request.
Please provide your suggestion to achieve this scenario.
Thanks & regards
Ashwin
Edited by: ashwin dhakne on May 17, 2010 5:32 PMHi all,
Created a below target payload in a message mapping with SOAP Header & Body part as per the requirement.
In SOAP receiver communication channel, checked the option " Do Not Use SOAP Envelope".
But while executing an sceanrio, i am facing an error in SOAP receiver channel as Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Internal Server Error
And if i don't check the option " Do Not Use SOAP Envelope" it gives an error as
Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Unable to obtain service binding,error=Payload Envelope is not a known message for TestWebserviceService.
Please provide your suggestions to handle this issue.
<?xml version="1.0" encoding="UTF-8" ?>
<ns1:Envelope xmlns:ns1="http://schemas.test.com/CustomrHeader">
<ns1:Header>
<ns1:CustomrHeader>
<ns1:MessageData>
<ns1:MessageId>Constant</ns1:MessageId>
<ns1:Timestamp>Constant</ns1:Timestamp>
</ns1:MessageData>
<ns1:Security>
<ns1:UsernameToken>
<ns1:Username>Constant</ns1:Username>
<ns1:Password>Constant</ns1:Password>
</ns1:UsernameToken>
</ns1:Security>
</ns1:CustomrHeader>
</ns1:Header>
<ns1:Body>
<ns1:Details>
<ns1:Information>
<ns1:Title>Test</ns1:JobTitle>
</ns1:Information>
<ns1:Contacts>
<ns1:Street>Test Drive</ns1:Street />
</ns1:Contacts>
</ns1:Details>
</ns1:Body>
</ns1:Envelope>
Thanks
Ashwin
Edited by: ashwin dhakne on May 18, 2010 5:47 PM
Edited by: ashwin dhakne on May 18, 2010 5:48 PM
Edited by: ashwin dhakne on May 18, 2010 5:48 PM
Maybe you are looking for
-
I am trying to restore my iphone to my itune and it is asking for a password and I dont know it?
I just got my replacement phone and I need to restore my information but it will not allow me to since it is asking for a password I dont remember?
-
How can i install airport express A 1264 on os x 10.9.2
How can i install Airport Express A 1264 on os x 10.9.2
-
Hi! I want to set a filter ''is in top'' to use dynamicly defined columns in filter. Something like as a user changes specific column with column selector, also the filter ''column'' is in top changes. Or doing this through some variable... Any ideas
-
Re-Installing Photoshop Elements 11
Greetings. I recently installed PE11. However, I have to reset my computer back to original factory settings (for an unrelated matter), which will uninstall all of my software. I need to know if I will be able to reinstall my PE11 or will I receiv
-
Installing Lightroom on new iMac
I have purchased Lightroom 4 which I installed on my laptop. I recently got a new iMac 27" and want to use the same serial number to install it on my iMac (I read that you can use the serial number on more than one computer). As the iMac don't take c