how to send exception to soap(third party) through...

Hello Experts ,

I am having soap to rfc synchronous scenario . I have kept 2 fields mandatory in the rfc as well as in the data type .But when i am testing the scenario from Altova or Soap UI , even if i am sending blank data from those 2 fields we are getting response .Neither altova nor pi nor rfc giving any error or exception . Why is it so ? Then what is the use of keeping data type as well as rfc fields mandatory ?

If i have kept them mandatory then it should not allow blank data to go ahead .

Please help .

Regards ,

Nikhil Save

SAP Managed Tags:
SAP Process Integration

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Accepted Solutions (0)

Answers (2)

Hello Nikhil,

Can you also paste the screenshot of Mapping?

Regards,

Nitin

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hi Nitin ,

Regards ,

Nikhil Save

Hi Nikhil,

vishnu already had explained very well , he is correct..

i will explain as per ur screenshot, how we will get exception when target field is mandatory.

if source field(pre_mast_rec_num) itself is not coming in data then the target field(I_ALTKN) will get fail because that filed occurrence is 1..1

and let me tell u wat us null and wat is empty

1.if source field itself not presents in data then its displays "null"

2.if source field is coming with out any data then its shows "[]" mean that is empty

i hope u are testing as like second case that is the reason u are not getting any exception.

BR,

Maheswarareddy

Hi Maheswarareddy ,

Thanks for explaining . Now i understood how mandatory field works .

In that case i have used below link to raise custom exception from PI when there will be blank value . I am getting the exception but it is not giving me custom exception message which i have wriiten in the UDF same as below link. It is giving me some standard as below.

<context>XIAdapter</context>
<code>ADAPTER.JAVA_EXCEPTION</code>
<text><![CDATA[
com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Application:EXCEPTION_DURING_EXECUTE:

Kindly help

http://scn.sap.com/thread/3204486

Regards ,

nikhil Save

Nikhil,

wat type of exception you are expecting in mapping level?

do u mean if mandatory not gets value then it should show particular filed in error?

Hi Nikhil,

I guess the custom exception which you have written in the udf will be there in the trace level.

Can you check the same in the trace tab.

Regards

Hello Nikhil,

Can you share the detailed error from the Trace in Moni?

May be that will speak about the fields and what is the exact error? Or else please paste the data in Test tab and check if you are facing any error?

Regards,

Nitin

Hello All ,

Thanks ,

We want to create exception in PI if mandatory field is sent blank by third party . So we have written below UDF.

And when we are testing in test tab of message mapping , we are getting runtime exception with custom message as expected .

But When we are testing from altova , we are getting below exception which is not having custom message anywhere .

<?xml version="1.0"?>

<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">

<SOAP:Body>

<SOAP:Fault>

<faultcode>SOAP:Server</faultcode>

<faultstring>Server Error</faultstring>

<s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">

<context>XIAdapter</context>

<code>ADAPTER.JAVA_EXCEPTION</code>

<text><![CDATA[

com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Application:EXCEPTION_DURING_EXECUTE:

at com.sap.aii.adapter.soap.web.SOAPHandler.processSOAPtoXMB(SOAPHandler.java:663)

at com.sap.aii.adapter.soap.web.MessageServlet.doPost(MessageServlet.java:470)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)

at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:202)

at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:103)

at com.sap.engine.services.servlets_jsp.server.servlet.AuthenticationFilter.doFilter(AuthenticationFilter.java:126)

at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:79)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:432)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:210)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:441)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:430)

at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:38)