ABAP exceptions!

Hi!
    Pls tell me a sample code in core abap exception handling
   ie using raise etc...
   one more thing 
    we can use this try endtry catch endcatch etc without using oops concept in abap.
  will it works
  looking for your reply.

Hi,
Exceptions are situations that occur while an ABAP program is being executed, in which normal continuation of the program does not make any sense.
Exceptions can be raised either implicitly in the ABAP runtime environment or explicitly in the ABAP program.
For example, division by zero leads to an exception in the ABAP runtime environment. It is possible to determine this situation through a query in the ABAP program and to trigger an exception there.
See the demo program DEMO_HANDLE_EXCEPTIONS in se38.
*--EXAMPLE FOR RUNTIME ERROR--
*DATA : VALUE1 TYPE I.
*VALUE1 = 1 / 0. "----
>>>>>> IT MAKES RUN TIME ERROR.
*WRITE : VALUE1.
*--EXAMPLE FOR HOW TO CATCH THE ARITHMETIC ERROR AT THE RUN TIME USING SUBRC--
*DATA : VALUE1 TYPE I.
*CATCH SYSTEM-EXCEPTIONS ARITHMETIC_ERRORS = 1.
*VALUE1 = 1 / 0.
*WRITE : VALUE1.
*ENDCATCH.
*IF SY-SUBRC = 1.
*WRITE : ' IT MAKES ERROR'.
*ELSE.
*WRITE : VALUE1.
*ENDIF.
in abap program we handle exceptions based on value returned by the system variable SY-SUBRC.
if SY-SUBRC = 0.
means execution completed sucessfull.
if SY-SUBRC = 1........n.
means execution compleated not sucessfully.
if sy-sbrc = 0.
write:/ 'execution sucessfull.
**here write logic as per u r requirement
else sy-subrc = '1'
message
elseif sy-subrc eq '2'
message
elseif sy-subrc eq '3'
message
elseif sy-subrc eq '4'
message
endif
Messages are defined in SE91..
These messages are of 5 types..
<b>A Termination Message</b>
The message appears in a dialog box, and the program terminates. When the user has confirmed the message, control returns to the next-highest area menu.
<b>E Error Message</b>
Depending on the program context, an error dialog appears or the program terminates.
<b>I (Information)</b>
The message appears in a dialog box. Once the user has confirmed the message, the program continues immediately after the MESSAGE statement.
<b>S (Status Message)</b>
The program continues normally after the MESSAGE statement, and the message is displayed in the status bar of the next screen.
<b>W (Warning)</b>
Depending on the program context, an error dialog appears or the program terminates.
<b>X (Exit)</b>
No message is displayed, and the program terminates with a short dump. Program terminations with a short dump normally only occur when a runtime error occurs. Message type X allows you to force a program termination. The short dump contains the message ID.
Pls read the following links:
http://help.sap.com/saphelp_nw04/helpdata/en/fb/35c62bc12711d4b2e80050dadfb92b/content.htm
Regards,
Padmam.

Similar Messages

  • I need information about Web dynpro ABAP Exception : ICF Service Node

    I need information about Web dynpro ABAP Exception :
    ICF Service Node "/sap/bc/webdynpro/sap/abcd/undefined" does not exist.
    Here abcd is application name.
    ICF Service Node exists and activated but kindly let me know from where "undefined" is coming .
    Please let me know your comments /views about  this.

    Hi,
    I think ur webdynpro service is not active after upgradation.
    You have manually activate it.
    Go go Tcode SICF,Execute the Initial screen,
    and in this new screen give service  as your application name and click on filter.
    You will get your service below which will be ur application name .
    right-Click on the deactivate and activate it or just activate it,.
    This shd work

  • The following ABAP Exception occurred: USER_NOT_FOUND

    Hi,
    A few of my users are receiving the following error :
    The following ABAP Exception occurred: USER_NOT_FOUND
    This only occurs when accessing webdynpro iviews. BSP iviews such as LSO (Learning Solution), SAP transaction iviews etc all work fine.
    The SU01 ECC accounts are all valid and have the neccessary roles. Communications (IT0105) have also been assigned and have valid dates.
    Both users have worked fine with no problems for several years and all of a sudden they have this error.
    We use a Novell LDAP for authentication which is shared by muliple applications and the UME is using dataSourceConfiguration_novell_not_readonly_db.xml
    I have tried deleting and recreating the accounts but this makes no difference. If I create new accounts with a different username they work fine with no problems. But this is not a suitbale work around, plus I would like to find out why this is happening.
    Any advice appreciated
    Thanks
    Craig

    Hi Craig,
    Can you please tell in detail what was wrong with the structural authorisations.
    We are also facing the same issue.
    Thanks
    Amit

  • The following ABAP Exception occurred: LINKLISTKEY_INVALID

    The following ABAP Exception occurred: LINKLISTKEY_INVALID:
    com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException
         at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:98)
         at com.sap.xss.ser.xssconfview.fc.FcLinks.onInit(FcLinks.java:256)
         at com.sap.xss.ser.xssconfview.fc.wdp.InternalFcLinks.onInit(InternalFcLinks.java:238)
         at com.sap.xss.ser.xssconfview.fc.FcLinksInterface.onInit(FcLinksInterface.java:115)
         at com.sap.xss.ser.xssconfview.fc.wdp.InternalFcLinksInterface.onInit(InternalFcLinksInterface.java:193)
         at com.sap.xss.ser.xssconfview.fc.wdp.InternalFcLinksInterface$External.onInit(InternalFcLinksInterface.java:257)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:922)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:891)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.attachComponentToUsage(FPMComponent.java:1084)
         at com.sap.xss.ser.xssconfview.vc.VcLinks.onInit(VcLinks.java:198)
         at com.sap.xss.ser.xssconfview.vc.wdp.InternalVcLinks.onInit(InternalVcLinks.java:222)
         at com.sap.xss.ser.xssconfview.vc.VcLinksInterface.onInit(VcLinksInterface.java:162)
         at com.sap.xss.ser.xssconfview.vc.wdp.InternalVcLinksInterface.onInit(InternalVcLinksInterface.java:144)
         at com.sap.xss.ser.xssconfview.vc.wdp.InternalVcLinksInterface$External.onInit(InternalVcLinksInterface.java:220)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:564)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent.doEventLoop(FPMComponent.java:438)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent.access$600(FPMComponent.java:78)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.raiseSaveEvent(FPMComponent.java:953)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.raiseSaveEvent(FPMComponent.java:1116)
         at com.sap.xss.per.vc.reviewnavi.VcPersInfoReviewNavi.next(VcPersInfoReviewNavi.java:227)
         at com.sap.xss.per.vc.reviewnavi.wdp.InternalVcPersInfoReviewNavi.next(InternalVcPersInfoReviewNavi.java:175)
         at com.sap.xss.per.vc.reviewnavi.ReviewNaviView.onActionNext(ReviewNaviView.java:153)
         at com.sap.xss.per.vc.reviewnavi.wdp.InternalReviewNaviView.wdInvokeEventHandler(InternalReviewNaviView.java:173)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
         at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseModel.java:420)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:132)
         at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:321)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:733)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:668)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
         at com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:73)
         at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionInternal(AbstractApplicationProxy.java:860)
         at com.sap.tc.webdynpro.portal.pb.impl.localwd.LocalApplicationProxy.sendDataAndProcessAction(LocalApplicationProxy.java:77)
         at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1299)
         at com.sap.portal.pb.PageBuilder.SendDataAndProcessAction(PageBuilder.java:326)
         at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:868)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processPhaseListener(WindowPhaseModel.java:755)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doPortalDispatch(WindowPhaseModel.java:717)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:136)
         at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:321)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(AccessController.java:219)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    Caused by: com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFC_Fault_Exception: Fault name: LINKLISTKEY_INVALID, fault text: LINKLISTKEY_INVALID
         at java.lang.Class.newInstanceImpl(Native Method)
         at java.lang.Class.newInstance(Class.java:1303)
         at com.sap.aii.proxy.framework.core.JcoMarshaler.unmarshalException(JcoMarshaler.java:429)
         at com.sap.aii.proxy.framework.core.JcoProxy.send(JcoProxy.java:78)
         at com.sap.aii.proxy.framework.core.AbstractProxy$JcoProxyHelper.send(AbstractProxy.java:173)
         at com.sap.aii.proxy.framework.core.AbstractProxy.send$(AbstractProxy.java:141)
         at com.sap.xss.ser.xssconfview.model.CSLinksModel.hrxss_Ser_Getconfscrlinks(CSLinksModel.java:152)
         at com.sap.xss.ser.xssconfview.model.Hrxss_Ser_Getconfscrlinks_Input.doExecute(Hrxss_Ser_Getconfscrlinks_Input.java:137)
         at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:92)
         ... 67 more
    Can nay one suggest anything on this?

    To solve this problem, make sure the LINKLISTKEY  property defined in the Web Dynpro Application properties exists in table T7XSSSERLNK.
    1. To view the link list key in the Web Dynpro app, in NWDS expand the Applications tree and then double click on your application. Click on the "Application Properties" tab, then look at the value for the "sap.xss.linkListKey".
    2. Ensure that value exists in the backend under transactions SPRO --> Personnel Management --> ESS --> General Settings --> Homepage for Self-Services -->Services --> Define Links on Confirmation Page
    Regards,
    Tom

  • ABAP exception monitoring with Nagios

    Hi all,
    is it possible to monitoring ABAP exception generated by an ABAP proxy receiver with Nagios? If yes, how?
    Thanks

    problem solved... external tables are the solution

  • The following ABAP Exception occurred: SERVICEKEY_INVALID error message

    Hello Gurus,
    I am setting up custom LWE and I completed doing that. Now, when I am running the LWE from the portal, I am getting the error "The following ABAP Exception occurred: SERVICEKEY_INVALID" while accessing 'Address', 'Benefits enrollment' 'personal data' etc.
    I do not know how to solve this error. Could anybody please suggest how to solve this problem?
    Thanks and appreciate much for your help with this!!
    Maria Kutty Somori....

    Please read the configuration in note 968360
    This is normally caused because of a missing or misleading
    configuration for the Homepage Framework.
    Please ensure the correct customistion is done for the  in the confirmation link ie V_T7XSSSERLNK
    check the resource table V_T7XSSSERRES in Homepage Customizing to solve
    this issue.

  • DOTNET RFC-Server: Throwing ABAP-exceptions

    Dear all,
    how do I throw ABAP-exceptions in a generated RFC-server?
    When I have an RFC-function module like the attached one in an SAP system and generate a server for this function module, how can I throw the ABAP-exception WRONG_UUID (for example in the C# code attached)?
    I haven't found an rfc-server example dealing with ABAP-exceptions.
    Best regards,
       Willy
    FUNCTION ZZZ.
    ""Local interface:
    *"  IMPORTING
    *"     VALUE(UUID) TYPE  SYSUUID_C DEFAULT SPACE
    *"  EXCEPTIONS
    *"      WRONG_UUID
        // Implementation of remote function module ZZZ
        protected override void Zzz (
               string Uuid)
          // TODO: add your server code here

    Hi Willy
    If I am not mistaken, it should be ...
    RfcAbapException ns = new RfcAbapException("WRONG_UUID", " Wrong user Id");
    throw ns;
    Not a C# guru but it should be something like that.

  • How to use an ABAP exception as a web service fault

    Hi experts,
    I have created a web service out of an ABAP function module, using the SAP standard wizard for web services. The ABAP function has some exceptions defined. Now the question is: How can I "translate" these ABAP function exceptions to web service faults?
    In the WSDL file I can see that the web service defines the faults, but they are not part of the web service operation (in the WSDL file). So when I load the definition into JDeveloper, the faults are not recognized.
    Any ideas what I am missing here?
    Thanks in advance!
    Kind regards, Matthias

    Exceptions from SAP function module are not translated as web service fault message, this is a standard behaviour due among other to the fact that exceptions are not "in line" with the definition a web service fault message.
    Usually when you want to use a standard SAP function module and expose it as web service, you need to "wrap-it" into a new Z function module.
    In that new function module you must capture the exceptions and convert them into a web service fault message structure (usually containing error type, text and number)
    Karim

  • Handling ABAP Exceptions in a Block

    Hi,
    If a background task calls an ABAP Class Method and that method throws a defined exception of type CX_BO_ERROR, I would expect to see a possible outcome for that exception that would allow me to handle the exception for the specific task. If I activate that outcome then an exception handling path will be displayed on the graphical representation which is taken if the exception is then raised by the method. If the outcome is disabled then the workitem goes to error.
    If I want to catch these exceptions (for multiple tasks) in an enclosing block in order to handle them in a single, standard way, how do I achieve that? It does not seem possible to simply define the exception type in the enclosing block and then activate it in order to then be able to automatically catch any exceptions of a particular type that have their outcomes disabled in their individual tasks. It would appear that I have to activate the outcomes for each task and then raise it during with a Process Control item on the exception handling path of the task. This seems to defeat the object of having exception handling at the Block level. Is my understanding correct or am I doing something wrong?
    Also, is it possible to capture the class exception object from the method call and store it in the Task Container (in order to get text & longtext details)?

    Thankyou for both of your responses.
    I understand that an individual ABAP Object or BOR method (call during an Activity) can raise an exception which can be handled as a separate outcome of that activity. However, if there are multiple Activity steps in the workfow that can all throw similar exceptions and I want to react to all of those exceptions in a uniform way, it seems excessive to have to handle each exception individually for each Activity in order to do the same thing (e.g. I may just want to send a standard email to someone or trigger another workflow event).
    I may have misunderstood things but I thought that the purpose of the Block step was to be used as a kind of TRY..CATCH mechanism that will allow exceptions to thrown to the Block by enclosed Activities without the need for enabling outcomes at the Activity level. I thought it would be possible for the exception type to be defined in the Block properties so that all exceptions of that type could be handled at a higher level by a single Block outcome (regardless of which enclosed Activity threw it). If this is the case then I do not see the point in having to define individual outcomes for each activity within the Block.
    That said, I cannot seem to get it to work without enabling the outcome for each activity and using a Process Control step to raise the exception to the Block (which seems to defeat the object because I have, in fact, just handled the exception!). The reason for my original posting is to verify whether or not what I am trying to do is possible and to find out what I doing wrong with regards to Block configuration.
    Kind Regards
    Simon.

  • - java handling ABAP Exception

    Hi folks,
    I am developing a webdynpro java programm that communicate with R/3 through a RFC.
    In an especif condition the ABAP program raises an "NO_DATA_FOUND" exception.
    Unfortunatelly  I can't catch this exception raised by ABAP.
    Do you may help me?
    Best wishes,
    Nelson Duarte

    Hi Nelson,
    You will get the error "NO_DATA_FOUND" in the back end when there are no records and you will get "INVALID_DATA"  when you pass an invalid input.
    BAPIRET2 structure return the error/warning/success messages if there are in the in the backend. If they are returning any messages for the above errors then you can print those messages by accessing the BAPIRET2 structure.
    You can print different error/warning/success using the return structure (if they are returning any)with the following code.
    IWDMessageManager msgmgr = wdComponentAPI.getMessageManager();
         String msgtype = new String();          
         try{
    //          If the RFc is returning any error messages the display those messages
         if(wdContext.currentReturn_outElement().getMessage()!=null){
              for(int i=0; i<wdContext.node<Return_out()>.size();i++)
                   msgtype = wdContext.nodeReturn_out().getElementAt(i).getAttributeValue("Type").toString();
                   if(msgtype.equals("W"))
                        msgmgr.reportWarning(wdContext.currentReturn_outElement().getMessage());
                   else if(msgtype.equals("E"))
                        msgmgr.reportException(wdContext.currentReturn_outElement().getMessage(),true);
                   else
                        msgmgr.reportSuccess(wdContext.currentReturn_outElement().getMessage());
         }catch(Exception e){
    Or
    int size = wdContext.node<Return_out()>.size();
    if(size ==0){
      //here you can print your own message
    Thanks n Regards,
    Jhansi Miryala

  • ABAP Exception Handling Document Link

    Anyone have a link for the document:
    "A Programmers Guide to the New Exception Handling Concept in ABAP"
    Thanks!

    Hello Kenneth
    Perhaps the following article may also be useful to you.
    <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/c1be1003-0701-0010-3795-f87160de6483">NetWeaver Developers Guide 2004s: Using ABAP</a>
    Regards
      Uwe

  • JCO ABAP Exception

    Hi Experts,
    Portal version: 7.02
    When I am trying to run a application, I am getting the following error,
    com.sap.mw.jco.JCO$AbapException: (126) NOT_FOUND: NOT_FOUND
    at com.sap.mw.jco.JCO$Client.execute(JCO.java:3712)
    at com.sap.mw.jco.JCO$Repository.execute(JCO.java:21910)
    at com.sap.mw.jco.JCO$Repository.queryFunctionInterface(JCO.java:22312)
    at com.sap.mw.jco.JCO$Repository.queryFunctionInterface(JCO.java:21935)
    at com.sap.mw.jco.JCO$Repository.getFunctionInterface(JCO.java:22039)
    at com.sap.tc.webdynpro.modelimpl.dynamicrfc.RFCMetadataRepository.getJcoMetadataForFunction(RFCMetadataRepository.java:77)
    at com.sap.tc.webdynpro.modelimpl.dynamicrfc.AiiModelClass.descriptor(AiiModelClass.java:220)
    at com.pg.invmodel.models.inv_unicode.Zisp_Inv_Get_Details_Input.<init>(Zisp_Inv_Get_Details_Input.java:51)
    at com.pg.invoicedetailapp.controllers.datauncust.DataUNCust.wdDoInit(DataUNCust.java:109)
    at com.pg.invoicedetailapp.controllers.datauncust.wdp.InternalDataUNCust.wdDoInit(InternalDataUNCust.java:327)
    at com.sap.tc.webdynpro.progmodel.generation.DelegatingCustomController.doInit(DelegatingCustomController.java:73)
    at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
    at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
    at com.sap.tc.webdynpro.progmodel.controller.Component.getCustomControllerInternal(Component.java:450)
    at com.sap.tc.webdynpro.progmodel.controller.Component.getMappableContext(Component.java:388)
    at com.sap.tc.webdynpro.progmodel.controller.Component.getMappableContext(Component.java:417)
    at com.sap.tc.webdynpro.progmodel.context.MappingInfo.getDataNode(MappingInfo.java:83)
    at com.sap.tc.webdynpro.progmodel.context.MappingInfo.initMapping(MappingInfo.java:125)
    at com.sap.tc.webdynpro.progmodel.context.MappingInfo.init(MappingInfo.java:121)
    at com.sap.tc.webdynpro.progmodel.context.MappedNodeInfo.doInit(MappedNodeInfo.java:215)
    at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:671)
    at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:674)
    at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:40)
    at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:199)
    at com.sap.tc.webdynpro.progmodel.controller.Component.getCustomControllerInternal(Component.java:450)
    at com.sap.tc.webdynpro.progmodel.controller.Component.getMappableContext(Component.java:388)
    at com.sap.tc.webdynpro.progmodel.controller.Component.getMappableContext(Component.java:417)
    at com.sap.tc.webdynpro.progmodel.context.MappingInfo.getDataNode(MappingInfo.java:83)
    at com.sap.tc.webdynpro.progmodel.context.MappingInfo.initMapping(MappingInfo.java:125)
    at com.sap.tc.webdynpro.progmodel.context.MappingInfo.init(MappingInfo.java:121)
    at com.sap.tc.webdynpro.progmodel.context.MappedNodeInfo.doInit(MappedNodeInfo.java:215)
    at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:671)
    at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:674)
    at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:40)
    at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:199)
    at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:709)
    at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:579)
    at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:155)
    at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.doOpen(WebDynproWindow.java:295)
    at com.sap.tc.webdynpro.clientserver.window.ApplicationWindow.show(ApplicationWindow.java:182)
    at com.sap.tc.webdynpro.clientserver.window.ApplicationWindow.open(ApplicationWindow.java:177)
    at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:364)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:783)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:303)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:741)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:694)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
    at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:185)
    at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
    at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1060)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
    at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
    at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
    at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
    at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
    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:104)
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
    Here I checked ,
    1. JCOs- no issue with jcos, all are working fine.
    2. There is no modification done in that particular FM Zisp_Inv_Get_Details ( Confirmed with ABAP team)
    3. This was working previous, i mean 1 week back but  now its dumping.
    4. I also refereed Error while Accessing RFC in java webdynpro and  some other scn links, but no luck yet.
    Kindly help me to find the root-cause   for this issue.
    Thanks & regards
    Rabin D

    HI Experts,
    When i tried the application in quality portal, the error is different, the error is as below
    com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: CPIC-CALL: CMRCV on convId: 86354998
    LOCATION CPIC (TCP/IP) on local host with Unicode
    ERROR connection to partner '155.111.253.124:3300' broken
    TIME Tue May 27 06:46:18 2014
    RELEASE 720
    COMPONENT NI (network interface)
    VERSION 40
    RC -6
    MODULE nixxi.cpp
    LINE 5086
    DETAIL NiIRead: P=155.111.253.124:3300; L=???
    SYSTEM CALL recv
    ERRNO 232
    ERRNO TEXT Connection reset by peer
    COUNTER 35
    at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.java:516)
    at com.sap.mw.jco.MiddlewareJRfc$Client.execute(MiddlewareJRfc.java:1498)
    at com.sap.mw.jco.JCO$Client.execute(JCO.java:4185)
    at com.sap.mw.jco.JCO$Client.execute(JCO.java:3697)
    at com.sap.mw.jco.JCO$Repository.execute(JCO.java:21910)
    at com.sap.mw.jco.JCO$Repository.queryFunctionInterface(JCO.java:22249)
    at com.sap.mw.jco.JCO$Repository.queryFunctionInterface(JCO.java:21935)
    at com.sap.mw.jco.JCO$Repository.getFunctionInterface(JCO.java:22039)
    at com.sap.tc.webdynpro.modelimpl.dynamicrfc.RFCMetadataRepository.getJcoMetadataForFunction(RFCMetadataRepository.java:77)
    at com.sap.tc.webdynpro.modelimpl.dynamicrfc.AiiModelClass.descriptor(AiiModelClass.java:220)
    at com.pg.invmodel.models.inv_unicode.Zisp_Inv_Get_Details_Input.<init>(Zisp_Inv_Get_Details_Input.java:51)
    at com.pg.invoicedetailapp.controllers.datauncust.DataUNCust.wdDoInit(DataUNCust.java:109)
    at com.pg.invoicedetailapp.controllers.datauncust.wdp.InternalDataUNCust.wdDoInit(InternalDataUNCust.java:327)
    at com.sap.tc.webdynpro.progmodel.generation.DelegatingCustomController.doInit(DelegatingCustomController.java:73)
    at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
    at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
    at com.sap.tc.webdynpro.progmodel.controller.Component.getCustomControllerInternal(Component.java:450)
    at com.sap.tc.webdynpro.progmodel.controller.Component.getMappableContext(Component.java:388)
    at com.sap.tc.webdynpro.progmodel.controller.Component.getMappableContext(Component.java:417)
    at com.sap.tc.webdynpro.progmodel.context.MappingInfo.getDataNode(MappingInfo.java:83)
    at com.sap.tc.webdynpro.progmodel.context.MappingInfo.initMapping(MappingInfo.java:125)
    at com.sap.tc.webdynpro.progmodel.context.MappingInfo.init(MappingInfo.java:121)
    at com.sap.tc.webdynpro.progmodel.context.MappedNodeInfo.doInit(MappedNodeInfo.java:215)
    at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:671)
    at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:674)
    at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:40)
    at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:199)
    at com.sap.tc.webdynpro.progmodel.controller.Component.getCustomControllerInternal(Component.java:450)
    at com.sap.tc.webdynpro.progmodel.controller.Component.getMappableContext(Component.java:388)
    at com.sap.tc.webdynpro.progmodel.controller.Component.getMappableContext(Component.java:417)
    at com.sap.tc.webdynpro.progmodel.context.MappingInfo.getDataNode(MappingInfo.java:83)
    at com.sap.tc.webdynpro.progmodel.context.MappingInfo.initMapping(MappingInfo.java:125)
    at com.sap.tc.webdynpro.progmodel.context.MappingInfo.init(MappingInfo.java:121)
    at com.sap.tc.webdynpro.progmodel.context.MappedNodeInfo.doInit(MappedNodeInfo.java:215)
    at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:671)
    at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:674)
    at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:40)
    at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:199)
    at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:709)
    at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:579)
    at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:155)
    at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.doOpen(WebDynproWindow.java:295)
    at com.sap.tc.webdynpro.clientserver.window.ApplicationWindow.show(ApplicationWindow.java:182)
    at com.sap.tc.webdynpro.clientserver.window.ApplicationWindow.open(ApplicationWindow.java:177)
    at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:364)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:783)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:303)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:741)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:694)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
    at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:185)
    at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
    at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:46)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1060)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
    at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
    at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
    at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
    at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
    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:104)
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
    Thanks & Regards
    Rabin D

  • Consuming a web service in ABAP exception and error

    Hi experts,
    I have succesfully implemented this example web service http://www.webservicex.net/airport.asmx?WSDL from http://www.webservicex.net/airport.asmx and everything works perfect so I know it is possible.
    But my requirement is to implement the following web service: http://ws1.webservices.nl/business/soap_doclit?wsdl it is a document/literal soap web service and WS-I Basic Profile 1.0 compliant. When I try to create a proxy object I get the following errors:
    - Exception occurred in library handler
    - Incorrect value: Unknown Namespace http://schemas.xmlsoap.org/wsdl
    I already found that library handler exception might have something to do with http bindings, I found note 1403271 but as my system is running on release 702 level 0008 this note is obsolete.
    Now 2nd error, incorrect value I don't really understand.. I also think the web service is SOAP 1.1 and not 1.2 because that should also give problems according to this topic: Proxy object to consume web service - can anyone verify to be sure? I'm not that familiar with WSDL files but does anyone know what I can test and what I can remove from the web service?
    The web service documentation is found here: https://webview.webservices.nl/documentation/files/interfaces/soap/soap-txt.html#SOAP_Interface.Differences_between_SOAP_interfaces
    There are also other versions such as RPC/Encoded and one without a header but ALL versions give the exact same error.
    Thx!

    check the beginning of your WSDL file
    just after the first line <xml> you should have
    <wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:wsa="http://www.w3.org/2005/08/addressing"
    followed by the namespaces related to your web service if required.
    SAP does all the job (generate the web service client) but any very little error in the file (or element not recognized) leads to this message "exception occurred in library handler" and it is not easy to know exactly what is the error...

  • ABAP proxy exception to SOAP fault and vice versa not getting mapped

    Hi there,
    I have these scenario's: ABAP proxy to SOAP (AXIS framework) and the other way around, synchronous, using AAE.
    When declaring the Synchronous Service interfaces we also defined error message types in order to pass system and application exceptions back to the service consumers.
    The behavior we are observing is as follows;
    When an exception is generated on the ABAP proxy, the error message type is correct generated and filled with the corresponding values in the ABAP proxy runtime. However, when the response arrives at the service consumer, it only contains a SOAP fault filled with some kind of generic PI mapping exception information.
    1. Why is the original ABAP proxy exception not mapped/passed into the SOAP response?
    2. What can we do in order to change that situation?
    3. Does it has to do with the use of the AAE - Advanced Adapter Engine or the AXIS framework?
    PS: We have performed a test of the Operation Mapping - OM using the ABAP exception as input and it did work correctly, so the error structure seems to be Ok.
    Many thanks for your replies.
    Edited by: Roberto Viana on Jul 26, 2010 8:30 PM

    Problem was caused by some differences in namespaces between source and target.

  • Handling Java Web Service Exception in ABAP

    Hi
    I have created a web service in Java using NWDS.
    Which has a businessMethod which throws a Exception based on certain business logic.
    I have consumed this  Web Service Method using .NET Client.
    i am able to catch the Exception and get the Exceltion Message.
    But when i try to consume the same web service Method in ABAP,
    i am not getting the Exception Message .
    The Method call works fine.
    What am i missing here ?
    regards
    Rajendra

    Hi,
    Upon further investigation and comparison of the custom exception object (generated during consumer proxy creation for a CUSTOM web service) with a standard exception object(generated during consumer proxy creation for a STANDARD web service) I found that the sub-elements of the exception structure errorPart are not available in the custom exception object (and one of these sub-elements is the message text).
    Call Stack,ExceptionName and MessageText Elements are missing in the errorPart node of Exception
    Node. as seen in the ABAP Exception structure generated.
    Queries:
    1.       Are there any standards which need to be followed when coding exceptions in the Java web service for consumption in ABAP such that all sub-elements of the exception object are also created in ABAP during the proxy creation?
    2.       Can we get the Java code for a standard web service available in SAP Netweaver? Asking the same as the exception object created for the standard web service RoomABAPWS contains the sub-elements. Getting the Java code of the same will be very helpful in resolving the issue.
    Regards
    Rajendra

Maybe you are looking for