SOAP Fault Response

Hi,
When we execute a service using XAI Dynamic submission we get a Fault response for an invalid request or any framework error and a actual response for the correct input.
Is it possible to send a Fault Response for the error scenarios from a custom developed service ? Is it possible to send a Fault response for the error scenarios and actual schema response for the successful scenarios from a single service ? Thanks in advance

Similar Messages

BEA-382500: ALSB Service Callout action received SOAP Fault response

Hi Friends...
 
 
 
During the implementation of TUTORIAL: 2 Loan Example of AquaLogic Service Bus 2.1,
I am getting fault response when testing the Proxy Service. Please help me in the following....
 
 
 
BEA-382500: ALSB Service Callout action received SOAP Fault response
 
 
 
error: failed to load java type corresponding to t=LoanStruct@java:normal.client
 
at
 
 
 
 
com.bea.staxb.runtime.internal.FailFastErrorHandler.add(FailFastErrorHandler.java:45)
at com.bea.staxb.runtime.internal.MarshalStreamUtils.addError(MarshalStreamUtils.java:274)
at com.bea.staxb.runtime.internal.MarshalStreamUtils.addError(MarshalStreamUtils.java:249)
at com.bea.staxb.runtime.internal.UnmarshalResult.addError(UnmarshalResult.java:140)
at com.bea.staxb.runtime.internal.UnmarshalResult.addError(UnmarshalResult.java:124)
at com.bea.staxb.runtime.internal.UnmarshalResult.getPojoBindingType(UnmarshalResult.java:327)
at com.bea.staxb.runtime.internal.UnmarshalResult.getPojoTypeFromXsiType(UnmarshalResult.java:310)
at com.bea.staxb.runtime.internal.RuntimeBindingType.determineActualRuntimeType(RuntimeBindingType.java:256)
at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalType(UnmarshalResult.java:210)
at com.bea.staxb.runtime.internal.SoapUnmarshallerImpl.unmarshalType(SoapUnmarshallerImpl.java:93)
at weblogic.wsee.bind.runtime.internal.EncodedDeserializerContext.unmarshalType(EncodedDeserializerContext.java:66)
at weblogic.wsee.bind.runtime.internal.BaseDeserializerContext.internalDeserializeType(BaseDeserializerContext.java:170)
at weblogic.wsee.bind.runtime.internal.BaseDeserializerContext.deserializeType(BaseDeserializerContext.java:87)
at weblogic.wsee.codec.soap11.SoapDecoder.decodePart(SoapDecoder.java:401)
at weblogic.wsee.codec.soap11.SoapDecoder.decodeParams(SoapDecoder.java:236)
at weblogic.wsee.codec.soap11.SoapDecoder.decodeParts(SoapDecoder.java:163)
at weblogic.wsee.codec.soap11.SoapDecoder.decode(SoapDecoder.java:116)
at weblogic.wsee.codec.soap11.SoapCodec.decode(SoapCodec.java:136)
at weblogic.wsee.ws.dispatch.server.CodecHandler.decode(CodecHandler.java:138)
at weblogic.wsee.ws.dispatch.server.CodecHandler.handleRequest(CodecHandler.java:39)
at weblogic.wsee.handler.HandlerIterator.handleRequest(HandlerIterator.java:127)
at weblogic.wsee.ws.dispatch.server.ServerDispatcher.dispatch(ServerDispatcher.java:85)
at weblogic.wsee.ws.WsSkel.invoke(WsSkel.java:80)
at weblogic.wsee.server.servlet.SoapProcessor.handlePost(SoapProcessor.java:66)
at weblogic.wsee.server.servlet.SoapProcessor.process(SoapProcessor.java:44)
at weblogic.wsee.server.servlet.BaseWSServlet$AuthorizedInvoke.run(BaseWSServlet.java:165)
at weblogic.wsee.server.servlet.BaseWSServlet.service(BaseWSServlet.java:84)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:225)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:127)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3214)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:1983)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:1890)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1344)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
 
Message was edited by:
alwaysvaghu
Message was edited by:
alwaysvaghu

I've been getting this problem as well. However, the thing that confuses me is that if I use the command-line client (as described in the tutorial), everything seems to work fine. However, if I use the test console, it fails to work (giving the fault described in an ancestor of this post).
I've tried added a 'Rename' operation, but I just get the java1 namespace as well.
If the problem was just the namespace issue as stated, wouldn't the command-line client have a similar problem?

Getting "OSB Service Callout action received SOAP Fault response" on trying to invoke a service using service callout

I'm trying to invoke a search service using service callout . However on trying to test it , I'm getting this response
<con:fault xmlns:con="http://www.bea.com/wli/sb/context">
<con:errorCode>BEA-382500</con:errorCode>
<con:reason>
OSB Service Callout action received SOAP Fault response
</con:reason>
<con:details>
<con1:ReceivedFaultDetail xmlns:con1="http://www.bea.com/wli/sb/stages/transform/config">
<con1:faultcode xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">soapenv:Client</con1:faultcode>
<con1:faultstring>Cannot find dispatch method for {}</con1:faultstring>
<con1:http-response-code>500</con1:http-response-code>
</con1:ReceivedFaultDetail>
Please help in resolving this error.
Thanks,
Rohit

you are calling wrong the Service.
¿what kind of service do you have? RPC? Document?
ir your target service its document, I recommend this:
1. Test target service with OSB
2. copy XML request and XML response from the test.
3. use XML request format that you got at Step 2 in your source service and using it at your "Service Callout".

Handling Soap Fault Response.

Hi All,
I have a Proxy to SOAP scenario.
While testing from SoapUI --
I am getting response for the valid input and for the invalid input the response is below.
In the scenario through SAP PI , the valid input given from the HTTP client is getting a valid response and the scenario is running fine.
But while checking the negative test, giving the invalid input, it is ending in a System error in PI.
We have to handle this and send the error back to the source system.
FAULT RESPONSE IN SoapUI :
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
 <soap:Body>
 <soap:Fault>
 <faultcode>soap:Client</faultcode>
 <faultstring>System.Web.Services.Protocols.SoapException: Server was unable to read request. ---> System.InvalidOperationException: There is an error in XML document (6, 45). ---> System.InvalidOperationException: Instance validation error: 'AD' is not a valid value for Currency.
 at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReader1.Read1_Currency(String s)
 at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReader1.Read2_ConversionRate()
 at Microsoft.Xml.Serialization.GeneratedAssembly.ArrayOfObjectSerializer.Deserialize(XmlSerializationReader reader)
 at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle, XmlDeserializationEvents events)
 --- End of inner exception stack trace ---
 at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle, XmlDeserializationEvents events)
 at System.Web.Services.Protocols.SoapServerProtocol.ReadParameters()
 --- End of inner exception stack trace ---
 at System.Web.Services.Protocols.SoapServerProtocol.ReadParameters()
 at System.Web.Services.Protocols.WebServiceHandler.CoreProcessRequest()</faultstring>
 <detail/>
 </soap:Fault>
 </soap:Body>
</soap:Envelope>
*System error message in SAP PI* :
<?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>XIAdapterFramework</SAP:Category><SAP:Code area="MESSAGE">GENERAL</SAP:Code><SAP:P1/><SAP:P2/><SAP:P3/><SAP:P4/><SAP:AdditionalText>com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: System.Web.Services.Protocols.SoapException: Server was unable to read request. ---> System.InvalidOperationException: There is an error in XML document (1, 328). ---> System.InvalidOperationException: Instance validation error: 'US' is not a valid value for Currency.
 at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReader1.Read1_Currency(String s)
 at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReader1.Read2_ConversionRate()
 at Microsoft.Xml.Serialization.GeneratedAssembly.ArrayOfObjectSerializer.Deserialize(XmlSerializationReader reader)
 at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle, XmlDeserializationEvents events)
 --- End of inner exception stack trace ---
 at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle, XmlDeserializationEvents events)
 at System.Web.Services.Protocols.SoapServerProtocol.ReadParameters()
 --- End of inner exception stack trace ---
 at System.Web.Services.Protocols.SoapServerProtocol.ReadParameters()
 at System.Web.Services.Protocols.WebServiceHandler.CoreProcessRequest()</SAP:AdditionalText><SAP:Stack/><SAP:Retry>M</SAP:Retry></SAP:Error>
I want to capture the text in Fault string in the Fault response and send it back to the Source system.
I have referred many blogs but i am unable to do it.
Will java mapping work as this is a response from the Target Webservice and NOT an errorin PI.

Hello.
If your scenario is ECC -> Proxy -> PI -> SOAP -> WS -> SOAP -> PI -> Proxy -> ECC.
In ESR create a Fault Message Type, and added to your Service Interface (Outboun/Inbound), use a XSLT mapping to take anyway format response, rebuid your proxy ABAP and see your "message fault" on exception tab.
this works for me.
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:xs="http://www.w3.org/2001/XMLSchema">
 <xsl:output method="xml" version="1.0" encoding="UTF-8" indent="yes"/>
 <xsl:template match="/">
 <ns0:FMT_ResponseAuth>
 <standard>
 <faultText>
 <xsl:value-of select="//detail"/>
 </faultText>
 </standard>
 </ns0:FMT_ResponseAuth>
 </xsl:template>
I hope this help you.
Edited by: KrlosRios on Nov 2, 2011 5:59 PM

Handling of SOAP Faults in SOAP Clients consuming PI Web services

Hi there,
the following is in regards to SOAP fault error handling in a SOAP client that consumes a Web Service published by PI.
I have been reading a number of threads and blogs in regards to this topic and I am still left with some open questions which I hope to get some final answersclarifications through this thread.
In particular the blogs
Handling Web Service SOAP Fault Responses in SAP NetWeaver XI - Handling Web Service SOAP Fault Responses in SAP NetWeaver XI
XI: Propagation of meaningful error information to SOAP Client - XI: Propagation of meaningful error information to SOAP Client
have caused by attention.
Both of these threads are realating to the Fault Message type one can use to return errors back to a SOAP Client (.Net, Java, etc.).
In our scenario we published a number of Web Services through PI that provide functionality to integrate with an R3 back-end system using inbound ABAP Proxies.
The services are standardised and will be consumed by a number of .NetJava applications and systems. The reason for the use of ABAP proxies is the customer specific application logic that is executed in the backend system. The Web services are synchronous and don't use ccBPM in the middle. Transformations are performed in PI combined with various lookups to set default values before the message is passed into the ABAP Framework of the R3 back-end system. The lookups are done against the R3 back-end system using the PI RFC Lookup feature.
The inbound proxies currently return application errors as part of the response message back to the SOAP client. For more critical errors we introduced the use of Fault message types as the method to return the information back to the SOAP Client. This is all working satisfactory.
The questions I have are as follows.
1. When an error occurs at the IE level (e.g. mapping error), ABAP Proxy framework level (e.g. conversion from XML to ABAP format) or Adapter Framework level (Adapter releated error) a different SOAP fault message structure is returned to the SOAP Client than the one used for the application errors. The SOAP fault message structure used in this case is the standard SOAP fault used by PI to return system errors back to the caller. For those SOAP fault messages there is no payload generated that could be mapped to the SOAP fault structure used for the application errors. This would be preferrable as there would be only one Fault message structure used for both inbound ABAP proxy generated fault messages and PI generated fault messages.
Also the error messages generated by PI can be quite cryptic and difficult to interpret at the client end and could be filtered ranslated during message mapping if the payload of the PI generated SOAP fault message could be accessed in a message mapping.
Point 3 of the above thread 2759 indicates that this would be possible but doesn't outline how. Could somebody please clarify this for me as I don't believe that this is really possible ???.
My idea instead was to use the PI SOAP fault message structure to also return application errors. Therefore I would create a Fault message type that matches the PI SOAP fault structure. This would enable the SOAP Client to handle only one SOAP Fault error structure. Would that be something to look into instead ?????.
2. We have been looking at using the integrated WEB AS SOAP adapter instead of using the AF Sender SOAP adapter. While playing with this we encountered differences in the content returned through the SOAP fault generated by PI. A sample is below. Shouldn't the content of these SOAP faults be the same if the error that caused it is the same. Also the SOAP fault returned by the IE SOAP adapter is much more useful in this particular case. Both errors below are the same, a conversion error from XML to ABAP took place in the inbound ABAP proxy framework of the back-end system.
SOAP fault returned when using SOAP Sender adapter of AF
<!see the documentation>
<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
 <SOAP:Body>
 <SOAP:Fault>
 <faultcode>SOAP:Server</faultcode>
 <faultstring>Server Error</faultstring>
 <detail>
 <s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
 <context>XIAdapter</context>
 <code>ADAPTER.JAVA_EXCEPTION</code>
 <text>com.sap.aii.af.ra.ms.api.DeliveryException: XIProxy:PARSE_APPLICATION_DATA:
 at com.sap.aii.adapter.xi.ms.XIEventHandler.onTransmit(XIEventHandler.java:455)
 at com.sap.aii.af.ra.ms.impl.core.queue.consumer.CallConsumer.onMessage(CallConsumer.java:134)
 at com.sap.aii.af.ra.ms.impl.core.queue.Queue.run(Queue.java:916)
 at com.sap.aii.af.ra.ms.runtime.MSWorkWrapper.run(MSWorkWrapper.java:56)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)</text>
 </s:SystemError>
 </detail>
 </SOAP:Fault>
 </SOAP:Body>
</SOAP:Envelope>
SOAP fault using integrated SOAP adapter of PI IE
<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
 <SOAP:Body>
 <SOAP:Fault>
 <faultcode>SOAP:Server</faultcode>
 <faultstring>System Error</faultstring>
 <detail>
 <s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
 <context/>
 <code>ABAP.PARSE_APPLICATION_DATA</code>
 <text>Error during XML => ABAP conversion (Request Message; error ID: CX_ST_DESERIALIZATION_ERROR; (/1SAI/TXSBE20FF604BAFEF8D990A XML Bytepos.: 564 XML Path: ns1:CreatePORequest(1)POHEADER(2)COMP_CODE(1) Error Text: Data loss occurred when converting ############################## Kernel ErrorId: CONVT_DATA_LOSS))</text>
 </s:SystemError>
 </detail>
 </SOAP:Fault>
 </SOAP:Body>
</SOAP:Envelope>
I have been reading threads for hours without being able to find one that answers questions 1 or provides a blog that outlines the approach one should take for error handling in SOAP clients that consume PI Web Services (and covers both PISystem generated faults and faults raised in Proxies).
There may already be a blog or thread and I just missed it.
Any comments are welcome.
Thanks. Dieter

Hi Dieter,
As Bhavesh already mentioned fault messages are used for application errors. The same is described in SAP XI help:
http://help.sap.com/saphelp_nw04/helpdata/en/dd/b7623c6369f454e10000000a114084/frameset.htm
In case of system error (e.g. field length too long in proxy call or error in XI/PI mapping) there seems to be no standard way of handling it and propagating the response to the consumer of webservice.
Each system error is not recognized by SOAP adapter and SOAP adapter exception is raised.
The only bizzare solution that I can see is developing an adapter module and transport wrong message to standard fault message before delivering it to adapter engine:
http://help.sap.com/saphelp_nw04/helpdata/en/a4/f13341771b4c0de10000000a1550b0/frameset.htm
Kind regards,
Wojciech
btw nice thread

PI 7.1 Adapter Module Development - Identify SOAP Fault Message

Hi Experts,
here's a PI 7.1 Adapter Module Development issue I hope you can help me to resolve. It's about identifying SOAP fault messages.

Scenario at a glance:
Adapter Modules placed in the modules chain at request and response time in a synchronous Scenario:
- Request: SOAP Axis to RFC 
- Response and Fault Response: RFC to SOAP Axis

The issue is how to identify SOAP fault message in SOAP Axis Adapter Module in the response message:
The client gets SOAP fault messages like the follwong one:
 <SOAP:Body>
 <SOAP:Fault>
 <faultcode>SOAP:Server</faultcode>
 <faultstring>Server Error</faultstring>
 <detail>
 <ns1:exception xmlns:ns1="http://typen.geschaeftsstelle.pab.barmer.de">
 <ns1:errortext>bla bla bla ...</ns1:errortext>
 </ns1:exception>
 </detail>
 </SOAP:Fault>
 </SOAP:Body>


But when trying to access the tags faultcode and/or faultstring in the adapter module via xPath expressions I do not get them. Obviously the SOAP Fault tags are built AFTER the adapter module has been passed. So my question is:
How can I clearly/uniquely detect a SOAP fault response message (and distinguish it from a "normal" response message) in my SOAP Axis Adapter Module?

I tried it the following way:


// Check Message Payload for SOAP Fault Message via xPath expressions
...
// SOAP Fault Code
zv_xPression = zc_constXPattern.replaceFirst("&", "faultcode");
zv_soapFaultCode = XPathAPI.eval(zv_doc, (String) zv_xPression).toString();
// SOAP Fault String
zv_xPression = zc_constXPattern.replaceFirst("&", "faultstring");
zv_soapFaultString = XPathAPI.eval(zv_doc, (String) zv_xPression).toString();
// check for SOAP Fault Message
if (zv_soapFaultCode.equals("") && zv_soapFaultString.equals("")) {
 // Create Audit Log entry - NOT a SOAP Fault Message
 zv_msgText = zc_constModuleName + " 0190: xPath - OK! This message is NOT a SOAP Fault Message";
 zv_audit.addAuditLogEntry(zv_msgKey, AuditLogStatus.SUCCESS, zv_msgText);
 zv_faultCheck = false;
}
else {
 ...
 // Create Audit Log entry - SOAP Fault Message
 zv_msgText = zc_constModuleName 
 + " 0200: xPath - this message is a SOAP Fault Message. " 
 + " - Faultcode is: " + zv_soapFaultCode 
 + " - Faultstring is: " + zv_soapFaultString; 
 zv_audit.addAuditLogEntry(zv_msgKey, AuditLogStatus.ERROR, zv_msgText);
 ...
}
...

But zv_soapFaultCode and zv_soapFaultString are always empty (with other payload tags this coding works fine).

Any ideas? 
Thanx very much in advance!
Regards,
Volker

Hi Alex!
Like already mentioned I solved my problem by identifying the SOAP exception with the messageClass attribute of the PI message header. Acess code:
try {
String zv_msgClass = zv_piMsg.getMessageClass().toString();
} catch (Exception e) {
zv_msgText = zc_constModuleName
+ " E0110: Message processing terminated."
+ " Reason: Error while getting MessageClass "
+ zv_dataSource
+ e;
// create trace and audit log entry (severity ERROR) for exception
zv_location.errorT(ZV_SIGNATURE, zv_msgText);
zv_audit.addAuditLogEntry(zv_msgKey, AuditLogStatus.ERROR, zv_msgText);
ModuleException me = new ModuleException(e);
zv_location.throwing(ZV_SIGNATURE, me);
e.printStackTrace();
throw me;
} // end of try-catch-block
But I do not think this will solve your problem. I am almost sure, that something in your Axis configuration is wrong/missing. If a handler cannot be instatiated then it really may be missing. Have a look at defaultTrace.trc. Maybe you will find more suitable information about the root cause of your problem. Also have a look at NWA under software components and/or application modules if you can find/see your modules.
But there is a general issue when trying to catch PI fault messages. If e.g. the requestor tries to login with wrong userid/pasword, then you will have no chance to catch this kind of error - at least as far as I know. Because in this very early stage of PI message processing no module is called.
One last question: Did you develop your own Adapter or just an adapter module? In the first case: Is your adapter started and healthy? Have a look at RWB -> communication channel monitoring.
Regards,
Volker

Soap Fault mapping issue

Hi,
I have a synchronous scenario of (request) Proxy --> XI --> SOAP and (response) SOAP --> XI --> Proxy. I am having an issue returning the application soap faults back to the sender system. When I enter invalid data while testing this webservice call with a soap client directly without XI I get a soap fault response:
<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.generalException</faultcode>
 <faultstring>Login failed</faultstring>
 <detail>
 <LoginFault xmlns="NAMESPACE">
 <exceptionCode>710</exceptionCode>
 <exceptionMessage>Login failed</exceptionMessage>
 </LoginFault>
 <ns1:exceptionName xmlns:ns1="http://xml.apache.org/axis/">NAMESPACE</ns1:exceptionName>
 </detail>
 </soapenv:Fault>
 </soapenv:Body>
</soapenv:Envelope>
When testing this through XI, the response message after the Soap call is returning the following soap fault in XI payload:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

<LoginFault xmlns="NAMESPACE">
<exceptionCode>710</exceptionCode>
<exceptionMessage>Login failed</exceptionMessage>
</LoginFault>
Notice just the detail body exists in the payload instead of the soap evelope and body, which I read is stripped off within XI in the case of application errors. I have setup a fault message mapping to tie the wsdl login fault with the standard fault message type and included this in the service interfaces and operations mapping. When the soap fault happens within XI I am getting the following mapping error:
NO_MAPPINGPROGRAM_FOUND: Mapping program is not available in runtime cache:
I am expecting the fault mapping to be executed in this case but doesn't seem to be found. Any ideas why this mapping error is occuring and not being directed to my fault message mapping? Is the mapping expecting the soap envelope and body to be included in the payload?
Any suggestions would be appreciated.
Thanks,
Nate

Here are the errors I am seeing within the sxmb_moni transaction:
Call adapter exception:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="MAPPING">NO_MAPPINGPROGRAM_FOUND</SAP:Code>
<SAP:P1>Object ID 35F8008AA0A830FC93FC221572A15ABD Software Component DC6FB8300EDE11DC8E05DB6DA3E77028</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Mapping program is not available in runtime cache: Object ID 35F8008AA0A830FC93FC221572A15ABD Software Component DC6FB8300EDE11DC8E05DB6DA3E77028</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Response Message Error:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>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="NAMESPACE REMOVED">LoginFault</SAP:ApplicationFaultMessage>
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
and response message payload:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <LoginFault xmlns="NAMESPACE REMOVED">
<exceptionCode>710</exceptionCode>
<exceptionMessage>Login failed</exceptionMessage>
</LoginFault>

Mapping SOAP Fault Message on PI

Hi there,
I'm trying to map a SOAP Fault Response From a Legacy system on PI, but i have some doubts on how to create the Data Type and the fault message Type,
Basically the response will look like this:
<SOAP-ENV:Body>
 <SOAP-ENV:Fault>
 <faultcode>SOAP-ENV:Client</faultcode>
 <faultstring>Data failed validation</faultstring>
 <detail>
 <fault xsi:type="ns1:Fault">
 <ns1:code>1002</ns1:code>
 <ns1:errorMessage>Data failed validation</ns1:errorMessage>
 <ns1:detailMessage>Invalid (does not exist) Zone Identity...</ns1:detailMessage>
 </fault>
 </detail>
</SOAP-ENV:Fault>
</SOAP-ENV:Body>
so basically i defined a data type detail ( named detail aswell in pi ), with a fault element and code errorMessage and detailMessage xsd:String attributes ( i dont know what to do with that ns1 xsi type )
but when i want to creat the whole message PI only allows me to have 1 outter element like this:
<FaultMessage>
 <faultcode>
 <faultstring>
 <detail>
so pretty much i want to have a data type with 4 independent elements cause i know the SOAP-ENV tags wont get to the mapping, im almost sure i'm missing something very dumb here but i dont see it ,
Thanks in advance for all the help you guys can provide,
Regards,
Roberto.

Thanks for the documention it was really helpful,
now i have another problem, i alredy created the data type for the detail tag to match the soap response, but when creating de Fault Message Type on the Data Type Used area, PI inserts me some standard data that is mandatory and does not correspond with the structure im going to receive, it only allows me to import the detail data type as Additional data :S.
Regards,
Roberto.

How to catch a SOAP fault

Hi All,
I have a ISU to web service, PROXY to SOAP sync interface. I am getting following as response.
How can I get this into Fault message mapping?
I have followed these blogs:
Fault Message Types - A Demo (Part 1)
Handling Web Service SOAP Fault Responses in SAP NetWeaver XI
<?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>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Validation constraint violation: data type mismatch in element 'extraOverhead'</SAP:AdditionalText>
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Thanks,
Aravind

Hi,
Can you please elaborate exactly what you are trying to achieve.....are you trying to display this error message to the user of client proxy...If so, You can catch the exceptions in client proxy using the two standard exception classes.
CATCH cx_ai_system_fault .
CATCH cx_ai_application_fault .
and in the catch block you can receive the error message and display it. The code will look like this
DATA : sys_fault TYPE REF TO cx_ai_system_fault,
 text TYPE string.
CREATE OBJECT sys_fault.
CALL METHOD sys_fault->get_text
 RECEIVING
 result = text.
WRITE : /10 'System Fault ', 30 text.
Regards,
Priyanka

How to return SOAP Fault from MII?

Hello, there!
I'd like an MII 12 transaction to return a SOAP Fault response when it fails for some reason.
The closest thing I found to this is to terminate the transaction (using the "Terminate Transaction" action) with error.
But this will cause MII to return an HTML page containing the error message, which is not satisfactory at all. It even causes the client to fail, since it is expecting a SOAP response.
Does anyone have any clue about this?
Thanks in advance!

The client will get a 500 error, with the error data available in the HTML content. Using the 500 error as the notification that something went wrong is probably the easiest way at present.
You could also create a "simulated" SOAP call using the Runner servlet and HTTP post, along with input and output XML documents that use a SOAP envelope/structure. You could then add a SOAP fault to the returned XML from within your transaction logic. It's not easy, but it can be done. The transaction itself is easy, but creating the WSDL is a bit more work, since you need to override the SOAP URL in the WSDL to point to Runner instead of SOAPRunner, and to include the InputParameter parameter in the URL to tell MII to map the "posted" XML (SOAP Input message) to a specific transaction input parameter.

Populating SOAP Fault

Does anyone know of a method by which i can populate a SOAP XML ( mainly SOAP FAULT ) directly into a object so that i have access to all the data in the code and do not have to put XML parsing logic in it.
I am interacting to a webservice using the WSDL , when i build it using ant it gave me response and request objects and methods to access them, but nothing was given that can cater to a SOAP fault response.
I was wondering if there is any way by which i can directlt map my SOAP output to a object ( API Defined ) so i would not have to write any XML parsing logic in the code, which i am trying to avoide.

Couple of things you can check:
1. Are you able to access the CAVS endpoint ?.
2. From your composite are you pointing to CAVS endpoint instead of the real endpoint, this can be done by changing the endpoint in the AIAConfigurationProperties.xml file or from the AIAApplication -> Setup screen routeToCAVS = true.
3. If not done, please go through the CAVS enablement process using the guide - http://docs.oracle.com/cd/E21764_01/doc.1111/e17364/completeabcs.htm#BACDIIID
Also you can check AIAApplication->CAVS to know if the request has reached CAVS by checking the instance tab.
Hope this helps.

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.

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.

SOAP Fault or Response

Hi dear members,
I would like to know if there is any best practices on whether to use SOAP Fault or a response object for returning messages including business errors
in request-response operations.
Can someone refer to some documentation on this topic?

In general I prefer to use SOAP faults for exceptions as they force the caller to handle them. When returning errors in a response object the caller can just not check for the response status and continue, which may lead to new failures on subsequent calls. Also, when calling services from an environment as BPEL, using soap faults helps you to use built in error handling like the error hospital and transaction support which would be far more difficult to do when the service would return an error status as part of a normal response.

SOAP fault - How to log error in response message map

Hi,
I have a scenario ABAP Proxy <-> XI <-> SOAP.
Occassionally there is an issue with communication to the destination system and an HTTP 500 Error is returned. I assume this is due to a system related error and it is returned as a SOAP Fault as opposed to a SOAP response with payload.
How do I get this "HTTP-500" error into my message map to return to the calling system ?
I have looked at Fault Messages but need to know if these are relevant for the SOAP Adapter and how they can be utilised ?
Thanks for any help.
Kind regards
Colin.

SOAP fault message not in correcto format to allow an application error to be caught.

SOAP Fault Exception [Actor null]

Hi All,
Im trying to call a webservice from portal This web service is in ECC. When I try to call it, it throws the following error:
#1.5 #00E0ED0BA5EF005C000000C500001E350004532D85C22E36#1217354889571#com.sap.portal.SOAPLogger#sap.com/irj#com.sap.portal.SOAPLogger#TESTUSER#9868##n/a##4b8f60d05d9911dda9db00e0ed0ba5ef#SAPEngine_Application_Thread[impl:3]_4##0#0#Warning#1#/System/Server#Java###Call failed
[EXCEPTION]
{0}#1#SOAP Fault Exception [Actor null] : CX_ST_MATCH_ELEMENT:XSLT exception.System expected element 'ItItem'
<Host>undefined</Host>
<Component>APPL</Component>
<ChainedException>
<Exception_Name>CX_SOAP_CORE</Exception_Name>
<Exception_Text>CX_ST_MATCH_ELEMENT:XSLT exception.System expected element 'ItItem'</Exception_Text>
</ChainedException>
<ChainedException>
<Exception_Name>CX_SXMLP</Exception_Name>
<Exception_Text>XSLT exception</Exception_Text>
</ChainedException>
<ChainedException>
<Exception_Name>CX_ST_MATCH_ELEMENT</Exception_Name>
<Exception_Text>System expected element 'ItItem': Main Program:/1BCDWB/WSSC9FCD3336732797F332| Program:/1BCDWB/WSSC9FCD3336732797F332| Line: 11| Valid:X</Exception_Text>
</ChainedException>
#1.5 #00E0ED0BA5EF005C000000C700001E350004532D85C23109#1217354889572#System.err#sap.com/irj#System.err#BHARDWS#9868##n/a##4b8f60d05d9911dda9db00e0ed0ba5ef#SAPEngine_Application_Thread[impl:3]_4##0#0#Error##Plain###SOAP Fault Exception [Actor null] : CX_ST_MATCH_ELEMENT:XSLT exception.System expected element 'ItItem'
<Host>undefined</Host>
<Component>APPL</Component>
<ChainedException>
<Exception_Name>CX_SOAP_CORE</Exception_Name>
<Exception_Text>CX_ST_MATCH_ELEMENT:XSLT exception.System expected element 'ItItem'</Exception_Text>
</ChainedException>
<ChainedException>
<Exception_Name>CX_SXMLP</Exception_Name>
<Exception_Text>XSLT exception</Exception_Text>
</ChainedException>
<ChainedException>
<Exception_Name>CX_ST_MATCH_ELEMENT</Exception_Name>
<Exception_Text>System expected element 'ItItem': Main Program:/1BCDWB/WSSC9FCD3336732797F332| Program:/1BCDWB/WSSC9FCD3336732797F332| Line: 11| Valid:X</Exception_Text>
</ChainedException>
#1.5 #00E0ED0BA5EF005C000000C800001E350004532D85C231DF#1217354889572#System.err#sap.com/irj#System.err#BHARDWS#9868##n/a##4b8f60d05d9911dda9db00e0ed0ba5ef#SAPEngine_Application_Thread[impl:3]_4##0#0#Error##Plain###We are in Exception and got the message778: SOAP Fault Error (n.a) : CX_ST_MATCH_ELEMENT:XSLT exception.System expected element 'ItItem'#
Has anyone come across this? Please help by giving directions on how to fix this.
Thanks
SB

Hi Alex,
Please ignore the above bapi call, it is too complex since it is a custom BAPI that Im trying to call. For now, I am trying to call a very simple BAPI --> BAPI_CUSTOMER_GETDETAIL just to make sure that communication is happening.
Here is the WSDL:
<?xml version="1.0" encoding="utf-8" ?>
- <wsdl:definitions targetNamespace="urn:sap-com:document:sap:rfc:functions" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:tns="urn:sap-com:document:sap:rfc:functions">
- <wsdl:documentation>
<sidl:sidl xmlns:sidl="http://www.sap.com/2007/03/sidl" />
</wsdl:documentation>
- <wsdl:types>
- <xsd:schema attributeFormDefault="qualified" targetNamespace="urn:sap-com:document:sap:rfc:functions">
- <xsd:simpleType name="char1">
- <xsd:restriction base="xsd:string">
<xsd:maxLength value="1" />
</xsd:restriction>
</xsd:simpleType>
- <xsd:simpleType name="char10">
- <xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
- <xsd:simpleType name="char130">
- <xsd:restriction base="xsd:string">
<xsd:maxLength value="130" />
</xsd:restriction>
</xsd:simpleType>
- <xsd:simpleType name="char16">
- <xsd:restriction base="xsd:string">
<xsd:maxLength value="16" />
</xsd:restriction>
</xsd:simpleType>
- <xsd:simpleType name="char2">
- <xsd:restriction base="xsd:string">
<xsd:maxLength value="2" />
</xsd:restriction>
</xsd:simpleType>
- <xsd:simpleType name="char20">
- <xsd:restriction base="xsd:string">
<xsd:maxLength value="20" />
</xsd:restriction>
</xsd:simpleType>
- <xsd:simpleType name="char220">
- <xsd:restriction base="xsd:string">
<xsd:maxLength value="220" />
</xsd:restriction>
</xsd:simpleType>
- <xsd:simpleType name="char3">
- <xsd:restriction base="xsd:string">
<xsd:maxLength value="3" />
</xsd:restriction>
</xsd:simpleType>
- <xsd:simpleType name="char30">
- <xsd:restriction base="xsd:string">
<xsd:maxLength value="30" />
</xsd:restriction>
</xsd:simpleType>
- <xsd:simpleType name="char31">
- <xsd:restriction base="xsd:string">
<xsd:maxLength value="31" />
</xsd:restriction>
</xsd:simpleType>
- <xsd:simpleType name="char32">
- <xsd:restriction base="xsd:string">
<xsd:maxLength value="32" />
</xsd:restriction>
</xsd:simpleType>
- <xsd:simpleType name="char35">
- <xsd:restriction base="xsd:string">
<xsd:maxLength value="35" />
</xsd:restriction>
</xsd:simpleType>
- <xsd:simpleType name="char4">
- <xsd:restriction base="xsd:string">
<xsd:maxLength value="4" />
</xsd:restriction>
</xsd:simpleType>
- <xsd:simpleType name="char5">
- <xsd:restriction base="xsd:string">
<xsd:maxLength value="5" />
</xsd:restriction>
</xsd:simpleType>
- <xsd:simpleType name="char50">
- <xsd:restriction base="xsd:string">
<xsd:maxLength value="50" />
</xsd:restriction>
</xsd:simpleType>
- <xsd:simpleType name="cuky5">
- <xsd:restriction base="xsd:string">
<xsd:maxLength value="5" />
</xsd:restriction>
</xsd:simpleType>
- <xsd:simpleType name="date">
- <xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
<xsd:pattern value="\d\d\d\d-\d\d-\d\d" />
</xsd:restriction>
</xsd:simpleType>
- <xsd:simpleType name="lang">
- <xsd:restriction base="xsd:string">
<xsd:maxLength value="1" />
</xsd:restriction>
</xsd:simpleType>
- <xsd:simpleType name="numeric3">
- <xsd:restriction base="xsd:string">
<xsd:maxLength value="3" />
<xsd:pattern value="\d*" />
</xsd:restriction>
</xsd:simpleType>
- <xsd:simpleType name="numeric6">
- <xsd:restriction base="xsd:string">
<xsd:maxLength value="6" />
<xsd:pattern value="\d*" />
</xsd:restriction>
</xsd:simpleType>
- <xsd:complexType name="BAPIRET2">
- <xsd:sequence>
<xsd:element name="TYPE" type="tns:char1" />
<xsd:element name="ID" type="tns:char20" />
<xsd:element name="NUMBER" type="tns:numeric3" />
<xsd:element name="MESSAGE" type="tns:char220" />
<xsd:element name="LOG_NO" type="tns:char20" />
<xsd:element name="LOG_MSG_NO" type="tns:numeric6" />
<xsd:element name="MESSAGE_V1" type="tns:char50" />
<xsd:element name="MESSAGE_V2" type="tns:char50" />
<xsd:element name="MESSAGE_V3" type="tns:char50" />
<xsd:element name="MESSAGE_V4" type="tns:char50" />
<xsd:element name="PARAMETER" type="tns:char32" />
<xsd:element name="ROW" type="xsd:int" />
<xsd:element name="FIELD" type="tns:char30" />
<xsd:element name="SYSTEM" type="tns:char10" />
</xsd:sequence>
</xsd:complexType>
- <xsd:complexType name="BAPIKNA101">
- <xsd:sequence>
<xsd:element name="FORM_OF_AD" type="tns:char30" />
<xsd:element name="FIRST_NAME" type="tns:char35" />
<xsd:element name="NAME" type="tns:char35" />
<xsd:element name="NAME_3" type="tns:char35" />
<xsd:element name="NAME_4" type="tns:char35" />
<xsd:element name="DATE_BIRTH" type="tns:date" />
<xsd:element name="STREET" type="tns:char35" />
<xsd:element name="POSTL_CODE" type="tns:char10" />
<xsd:element name="CITY" type="tns:char35" />
<xsd:element name="REGION" type="tns:char3" />
<xsd:element name="COUNTRY" type="tns:char3" />
<xsd:element name="COUNTRNISO" type="tns:char3" />
<xsd:element name="COUNTRAISO" type="tns:char3" />
<xsd:element name="INTERNET" type="tns:char130" />
<xsd:element name="FAX_NUMBER" type="tns:char31" />
<xsd:element name="TELEPHONE" type="tns:char16" />
<xsd:element name="TELEPHONE2" type="tns:char16" />
<xsd:element name="LANGU" type="tns:lang" />
<xsd:element name="LANGU_ISO" type="tns:char2" />
<xsd:element name="CURRENCY" type="tns:cuky5" />
<xsd:element name="CURRENCY_ISO" type="tns:char3" />
<xsd:element name="COUNTRYISO" type="tns:char2" />
<xsd:element name="ONLY_CHANGE_COMADDRESS" type="tns:char1" />
</xsd:sequence>
</xsd:complexType>
- <xsd:complexType name="BAPIRETURN">
- <xsd:sequence>
<xsd:element name="TYPE" type="tns:char1" />
<xsd:element name="CODE" type="tns:char5" />
<xsd:element name="MESSAGE" type="tns:char220" />
<xsd:element name="LOG_NO" type="tns:char20" />
<xsd:element name="LOG_MSG_NO" type="tns:numeric6" />
<xsd:element name="MESSAGE_V1" type="tns:char50" />
<xsd:element name="MESSAGE_V2" type="tns:char50" />
<xsd:element name="MESSAGE_V3" type="tns:char50" />
<xsd:element name="MESSAGE_V4" type="tns:char50" />
</xsd:sequence>
</xsd:complexType>
- <xsd:element name="BAPI_TRANSACTION_COMMIT">
- <xsd:complexType>
- <xsd:sequence>
<xsd:element name="WAIT" type="tns:char1" minOccurs="0" />
</xsd:sequence>
</xsd:complexType>
</xsd:element>
- <xsd:element name="BAPI_TRANSACTION_COMMITResponse">
- <xsd:complexType>
- <xsd:sequence>
<xsd:element name="RETURN" type="tns:BAPIRET2" />
</xsd:sequence>
</xsd:complexType>
</xsd:element>
- <xsd:element name="BAPI_CUSTOMER_GETDETAIL">
- <xsd:complexType>
- <xsd:sequence>
<xsd:element name="CUSTOMERNO" type="tns:char10" />
<xsd:element name="PI_DISTR_CHAN" type="tns:char2" minOccurs="0" />
<xsd:element name="PI_DIVISION" type="tns:char2" minOccurs="0" />
<xsd:element name="PI_PASS_BUFFER" type="tns:char1" minOccurs="0" />
<xsd:element name="PI_SALESORG" type="tns:char4" />
</xsd:sequence>
</xsd:complexType>
</xsd:element>
- <xsd:element name="BAPI_CUSTOMER_GETDETAILResponse">
- <xsd:complexType>
- <xsd:sequence>
<xsd:element name="PE_ADDRESS" type="tns:BAPIKNA101" />
<xsd:element name="RETURN" type="tns:BAPIRETURN" />
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>
</wsdl:types>
- <wsdl:message name="BAPI_TRANSACTION_COMMIT">
<wsdl:part name="parameters" element="tns:BAPI_TRANSACTION_COMMIT" />
</wsdl:message>
- <wsdl:message name="BAPI_TRANSACTION_COMMITResponse">
<wsdl:part name="parameter" element="tns:BAPI_TRANSACTION_COMMITResponse" />
</wsdl:message>
- <wsdl:message name="BAPI_CUSTOMER_GETDETAIL">
<wsdl:part name="parameters" element="tns:BAPI_CUSTOMER_GETDETAIL" />
</wsdl:message>
- <wsdl:message name="BAPI_CUSTOMER_GETDETAILResponse">
<wsdl:part name="parameter" element="tns:BAPI_CUSTOMER_GETDETAILResponse" />
</wsdl:message>
- <wsdl:portType name="YCUST">
- <wsdl:operation name="BAPI_TRANSACTION_COMMIT">
<wsdl:input message="tns:BAPI_TRANSACTION_COMMIT" />
<wsdl:output message="tns:BAPI_TRANSACTION_COMMITResponse" />
</wsdl:operation>
- <wsdl:operation name="BAPI_CUSTOMER_GETDETAIL">
<wsdl:input message="tns:BAPI_CUSTOMER_GETDETAIL" />
<wsdl:output message="tns:BAPI_CUSTOMER_GETDETAILResponse" />
</wsdl:operation>
</wsdl:portType>
- <wsdl:binding name="YCUST" type="tns:YCUST">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document" />
- <wsdl:operation name="BAPI_TRANSACTION_COMMIT">
<soap:operation soapAction="" style="document" />
- <wsdl:input>
<soap:body use="literal" />
</wsdl:input>
- <wsdl:output>
<soap:body use="literal" />
</wsdl:output>
</wsdl:operation>
- <wsdl:operation name="BAPI_CUSTOMER_GETDETAIL">
<soap:operation soapAction="" style="document" />
- <wsdl:input>
<soap:body use="literal" />
</wsdl:input>
- <wsdl:output>
<soap:body use="literal" />
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
- <wsdl:service name="service">
- <wsdl:port name="YCUST" binding="tns:YCUST">
<soap:address location="http://myportal:8040/sap/bc/srt/rfc/sap/ycust/040/ycust/ycust" />
</wsdl:port>
</wsdl:service>
</wsdl:definitions>
As you will see below in my portal component, Im populating the four fields that it requires:
public class WS_ECC_Service extends PageProcessorComponent {
public DynPage getPage(){
 return new WS_ECC_ServiceDynPage();
public static class WS_ECC_ServiceDynPage extends JSPDynPage{
 protected IPortalComponentRequest request;
 protected IPortalComponentResponse response;
 protected IPortalComponentSession session;
 protected IPortalComponentContext context;
 protected IPortalComponentProfile profile;
 protected String userId;
 // protected IUser epUser;
 protected String sapSystem;
 protected String fileName;
 private DAO DAO = null;
 // private FileUploadUtility FIU = null;
 // private ReadExcelData RED = null;
 private final static int SUCCESS_STATE = 0;
 private final static int INITIAL_STATE = 1;
 private final static int ERROR_STATE = 2;
 private int state = INITIAL_STATE;
 public void doInitialization(){
 this.communicate();
 // fill your bean with data here...
 public void communicate()throws IllegalArgumentException{
 try{
 IPortalRuntimeResources runtimeResources = PortalRuntime.getRuntimeResources();
 IYBAPI_Service myService = (IYBAPI_Service)runtimeResources.getService(IYBAPI_Service.KEY);
 System.err.println("b4 passing object to service Anurag-"+IYBAPI_Service.KEY);
 com.ybapi.BAPI_CUSTOMER_GETDETAIL param = new com.ybapi.BAPI_CUSTOMER_GETDETAIL();
 com.ybapi.BAPI_CUSTOMER_GETDETAILResponse result1 = new com.ybapi.BAPI_CUSTOMER_GETDETAILResponse();
 com.ybapi.Char10 custno = new com.ybapi.Char10();
 custno.setValue("0000009702");
 param.setCUSTOMERNO(custno);
 com.ybapi.Char2 distr = new com.ybapi.Char2();
 distr.setValue("12");
 param.setPI_DISTR_CHAN(distr);
 param.setPI_DIVISION(distr);
 com.ybapi.Char1 buff = new com.ybapi.Char1();
 buff.setValue("w");
 param.setPI_PASS_BUFFER(buff);
 com.ybapi.Char4 sorg = new com.ybapi.Char4();
 sorg.setValue("0001");
 param.setPI_SALESORG(sorg);
 result1 = myService.BAPI_CUSTOMER_GETDETAIL(param);
 System.err.println("message message dear message : - " + result1.getPE_ADDRESS().getNAME());
 }catch (IllegalArgumentException ex){
 System.err.println("Getting details2 " + ex.getMessage());
 }catch (Exception e) {
 e.printStackTrace();
 System.err.println("We are in Exception and got the message778: " + e.getMessage());
 }//end try catch
 public void doProcessAfterInput() throws PageException {
 public void doProcessBeforeOutput() throws PageException {
 this.setJspName("uploadutility.jsp");
and this is what it is throwing the error, exactly the same that I got in my above post which I asked you to ignore.
#1.5 #00E0ED0BA5EF006E0000015A00001E350004533EB66A08B6#1217428720322#com.sap.portal.SOAPLogger#sap.com/irj#com.sap.portal.SOAPLogger#BHARDWS#17255##n/a##2aaa48605e4511ddbbf300e0ed0ba5ef#SAPEngine_Application_Thread[impl:3]_2##0#0#Warning#1#/System/Server#Java###Call failed
[EXCEPTION]
{0}#1#SOAP Fault Exception [Actor null] : CX_ST_MATCH_ELEMENT:XSLT exception.System expected element 'CUSTOMERNO'
<Host>undefined</Host>
<Component>APPL</Component>
<ChainedException>
<Exception_Name>CX_SOAP_CORE</Exception_Name>
<Exception_Text>CX_ST_MATCH_ELEMENT:XSLT exception.System expected element 'CUSTOMERNO'</Exception_Text>
</ChainedException>
<ChainedException>
<Exception_Name>CX_SXMLP</Exception_Name>
<Exception_Text>XSLT exception</Exception_Text>
</ChainedException>
<ChainedException>
<Exception_Name>CX_ST_MATCH_ELEMENT</Exception_Name>
<Exception_Text>System expected element 'CUSTOMERNO': Main Program:/1BCDWB/WSSB675FB6DBC9770445BC| Program:/1BCDWB/WSSB675FB6DBC9770445BC| Line: 19| Valid:X</Exception_Text>
</ChainedException>
#1.5 #00E0ED0BA5EF006E0000015C00001E350004533EB66A09BD#1217428720322#System.err#sap.com/irj#System.err#BHARDWS#17255##n/a##2aaa48605e4511ddbbf300e0ed0ba5ef#SAPEngine_Application_Thread[impl:3]_2##0#0#Error##Plain###$$$$$$$$$$$$$exex-SOAP Fault Error (n.a) : CX_ST_MATCH_ELEMENT:XSLT exception.System expected element 'CUSTOMERNO'#
#1.5 #00E0ED0BA5EF006E0000015D00001E350004533EB66A0B44#1217428720323#System.err#sap.com/irj#System.err#BHARDWS#17255##n/a##2aaa48605e4511ddbbf300e0ed0ba5ef#SAPEngine_Application_Thread[impl:3]_2##0#0#Error##Plain###SOAP Fault Exception [Actor null] : CX_ST_MATCH_ELEMENT:XSLT exception.System expected element 'CUSTOMERNO'
<Host>undefined</Host>
<Component>APPL</Component>
<ChainedException>
<Exception_Name>CX_SOAP_CORE</Exception_Name>
<Exception_Text>CX_ST_MATCH_ELEMENT:XSLT exception.System expected element 'CUSTOMERNO'</Exception_Text>
</ChainedException>
<ChainedException>
<Exception_Name>CX_SXMLP</Exception_Name>
<Exception_Text>XSLT exception</Exception_Text>
</ChainedException>
<ChainedException>
<Exception_Name>CX_ST_MATCH_ELEMENT</Exception_Name>
<Exception_Text>System expected element 'CUSTOMERNO': Main Program:/1BCDWB/WSSB675FB6DBC9770445BC| Program:/1BCDWB/WSSB675FB6DBC9770445BC| Line: 19| Valid:X</Exception_Text>
</ChainedException>
#1.5 #00E0ED0BA5EF006E0000015E00001E350004533EB66A0B93#1217428720323#System.err#sap.com/irj#System.err#TESTUSER#17255##n/a##2aaa48605e4511ddbbf300e0ed0ba5ef#SAPEngine_Application_Thread[impl:3]_2##0#0#Error##Plain###We are in Exception and got the message778: SOAP Fault Error (n.a) : CX_ST_MATCH_ELEMENT:XSLT exception.System expected element 'CUSTOMERNO'#

SOAP Fault Response

Similar Messages

Maybe you are looking for