Handling exceptions for barcode:

Hi,
How can I handle the exceptions for a barcode process? suppose I have a tiff document with 4 pages and 4 barcodes, and if one of them was failed in decoding, my whole process is running into exception. I want to handle that failed barcode alone and send a message to the output variable that the particualr barcode is failed.
I tried using events with default exception handling. I dont know how to configure it and catch the runtime exception. I tried searching in the internet to get some configuration samples for that. I checked the sample from Tour de livecycle. Even that didnt guide me how to configure those exceptions.
Chaitanya

Can someone help me out on this..
Thanks

Similar Messages

Can we handle exceptions for the expressions in select query?

Hi all,
Can we handle exceptions for the expressions in select query.
I created a view, there I am extracting a substring from a character data and expected that as a number.
For example consider the following query.
SQL> select to_number( substr('r01',2,2) ) from dual;
TO_NUMBER(SUBSTR('R01',2,2))
1
Here we got the value as "1".
Consider the following query.
SQL> select to_number( substr('rr1',2,2) ) from dual;
select to_number( substr('rr1',2,2) ) from dual
ORA-01722: invalid number
For this I got error. Because the substr returns "r1" which is expected to be as number. So it returns "Invalid number".
So, without using procedures or functions can we handle these type of exceptions?
I am using Oracle 10 G.
Thanks in advance.
Thank you,
Regards,
Gowtham Sen.

SQL> select decode(ltrim(rtrim(translate(substr('r21', 2, 2), '0123456789', ' ' ), ' '), ' '), null, (substr('r21', 2, 2)), null) from dual;
DE
21
SQL> ed a
SQL> select decode(ltrim(rtrim(translate(substr('rr1', 2, 2), '0123456789', ' ' ), ' '), ' '), null, (substr('rr1', 2, 2)), null) from dual;
D
-

Handling exceptions for a event handler method.

Hi Mates,
I have two custom container in which i am displaying an alv grid usind objects. when a double click event is performed in one of the alv the other alv should be displayed. I now have to handle exceptions of the class CX_SY_DYN_CALL_ILLEGAL_TYPE. This is raised for an invalid parameter type when calling a method dynamically. I cannot use the keyword "RAISING" in the definition of the event handler method. i checked with the syntax of the method definition in abap dictionary, there were no addition "RAISING" for an event handler method. please provide me with the solution (a sample code would do.)

Hello,
May be you should read about the TRY ... CATCH block which is used for handling exceptions.
Basic construct of your code should look like this:
TRY.
" Your Dynamic Method call
CATCH CX_SY_DYN_CALL_ILLEGAL_TYPE.
ENDTRY.
If you want to get the error message text:
DATA:
lcx_excp TYPE REF TO CX_SY_DYN_CALL_ILLEGAL_TYPE,
v_err_msg TYPE string.
TRY.
" Your Dynamic Method call
CATCH CX_SY_DYN_CALL_ILLEGAL_TYPE INTO lcx_excp.
v_err_msg = lcx_excp->get_text( ).
ENDTRY.

Java.sql exception for rs.nesxt() ( nested statements)

I have a problem with java.sql.I am getting an Invalid handle exception for nested result sets ...
example:-
//Conn is the common connection
Statement s1 = conn.createStatement();
rs1 = s1.executeQuery(query1);
while (rs.next){
Statement s2 = conn.createStatement();
rs2= s2.executeQuery(query2)
while (rs2.next){
The rs2 resultset works fine,but when it gets back into the outer while loop the exception is thrown.
I know that the problem is becuase the nested statements are usign the same connection.
I know of two ways to work around this
(1) use different connections
(2) remove nesting (save the result rs1,and then retrieve rs2)
But I wnated to know if anyone knows of any other way to work around this problem.
let me know.
Thanks.

Each connection has a single storage area for iteration, metadata, etc. Obviously you are aware that outer loop is unable to proceed because iteration data is of a different format from the inner sql query. It is not a good idea to do more than a single, or small set of queries on a single connection object. Would you consider a connection pool? They are not for the timid programmer, but they do take advantage of using connection objects much like pointers, with the ability to pop them into and out of a collection, ready to roll once the connection object is setup and ready for action much like a pointer that is properly assigned can be passed and always ready for action. The entire connection object (and metadata) is stored in the collection data structure. My advice is to keep it simple! It is easy to get too carried away with connection pools.

How to Handle Exceptions in Web Dynpro for ABAP?

Is there a simple method inside a try/catch/endcatch/endtry using the code wizard. If anyone has any documentation or suggestions I am learning and open to all.
Thank-You.

Hi Thomas,
is there also a way to globally handle all exceptions for a wd application or a wd component?
We would like to always show a popup window and write the exception (including stack trace) to the log file.
Thanks,
Christoph

Extend BizTalk ESB Exception Handling to manage exception for all organization wide application exception

Hello,
Can we Extend BizTalk ESB Exception Handling to manage exception for all organization wide application ( both biztalk and external) exception ?
Is it something a good option or there are better approach to do this.
Business requirement is Exception management should be single window for complete end-to end application ( source-Biztalk - destination)
Tarun
Tarun

Hi Tarun,
ESB Toolkit framework for exception handling is not complete OOTB. it is intended as a framework and set of patterns that can and should
be extended based on the customer’s needs.
One way of extending the capabilities is by using Standardized Exception Management or SEM in short.
SEM solution extends the capabilities of the Microsoft ESB Exception Management Framework and follows a design pattern that provides a flexible
approach to exception monitoring and enables error responses to originate from outside of the solution. While SEM is primarily targeted to Microsoft BizTalk Server applications, it can also be leveraged by other applications that are able to call a Windows
Communications Foundation (WCF) or web service.
Refer: Standardized Exception Management
Standardized Exception Management (SEM)
Rachit

Is Exception handler necessary for every stored subprogram

Hi All,
I knwo exception handler is very important. But is it necessary for every stored procedure or function?
For example,
procedure test(p_index_code IN varchar2(10)
p_changed_code OUT varchar2(15))
as
begin
IF p_index_code = 'A' then
p_changed_code := 'A'|| p_index_code;
elsif p_index_code = 'B' then
p_changed_code := 'B'|| p_index_code;
else
p_changed_code := p_index_code;
end if;
end;
This kind of simple procedures, do I have to add the 'exection when others than raise_application_error(-20001,'error in this SP')'?
I can't see obvious drawbacks without the exception handler in this CASE.
Best regards,
Leon
Edited by: user12064076 on Nov 11, 2010 7:12 PM

user12064076 wrote:
I knwo exception handler is very important. But is it necessary for every stored procedure or function?It is important to know WHY an exception handler is needed. There are couple of basic reasons why you want to use an exception handler.
The exception is not an error.
The exception raised is a technical error, but may not be a business or processing error. The typical example is the NO_DATA_FOUND exception. The business logic may say "+when there is no fixed discounts found, apply a 5% dis-count+". So not finding (dis-count) row data in such a case is not an exception. What does you exception handler do? It fixes the exception and there is not an exception anymore. In other words, the caller that called your code will never know that there was an exception.
Making the exception meaningful
An exception, like NO_DATA_FOUND, is not very meaningful. What is meaningful is NO_INVOICE_FOUND or NO_CUSTOMER_FOUND. Thus your exception handler can catch a generic exception and make it more meaningful by returning a custom application exception instead.
Action stations
Some exceptions will require you to clean up and fix what you can - kind of like action stations when a ship takes a hit. But as you cannot fix the exception, the exception must be passed to the caller so that it too can decide how to re-act to that exception. For example, you may have an open ref cursor or open UTL_FILE handle that needs to be closed when your code terminates. If not, your code will leak resources. So you need to trap exceptions that can occur, clean up, and then re-raise the exception (this is called a resource protection code block in other languages). You may have done a partial transaction - and the exception handler may need to roll back the changes your code made. The bottom line here is that you must re-raise the exception after you have done your "+action stations+" bit. You did not fix the exception. You did not make it more meaningful. In that case you must pass it back to the caller so that it can decide what it needs to do about that exception.
Using an exception for any other reason - that would likely be the wrong thing to do most of the time.

Good exception handling policy for Java web application

I'm looking for a good exception handling policy for Java web application. First I found this Java exception handling best practices - How To Do In Java which says that you should never catch the Trowable class nor use e.printStackTrace();
Then I found this Oracle page The Message-Driven Bean Class - The Java EE 6 Tutorial, which does just that. So now I'm confused. Is there a good page online for an exception handling policy for Java EE Web applications? I have a hard time finding one. I've read that you should not catch the Exception class. I've been catching it previously to make sure that some unknown exception doesn't slip through early in the loop and stops all other customers from executing later on in the loop. We have a loop which runs once a minute implemented using the Quartz framework. Is it OK if you just change the implementation to catch the RuntimeException class instead of the Exception class? We're using Java 7 and the Jetty Servlet Container.

I'm looking for a good exception handling policy for Java web application.
If you have not done so I suggest you start by reviewing the several trails in The Java Tutorials.
Those trails cover both HOW to use exceptions and WHEN to use them.
This trail discusses the 'controversy' you mention regarding 'Unchecked Exceptions'
http://docs.oracle.com/javase/tutorial/essential/exceptions/runtime.html
Unchecked Exceptions — The Controversy
Because the Java programming language does not require methods to catch or to specify unchecked exceptions (RuntimeException, Error, and their subclasses), programmers may be tempted to write code that throws only unchecked exceptions or to make all their exception subclasses inherit from RuntimeException. Both of these shortcuts allow programmers to write code without bothering with compiler errors and without bothering to specify or to catch any exceptions. Although this may seem convenient to the programmer, it sidesteps the intent of the catch or specify requirement and can cause problems for others using your classes.
Why did the designers decide to force a method to specify all uncaught checked exceptions that can be thrown within its scope? Any Exception that can be thrown by a method is part of the method's public programming interface. Those who call a method must know about the exceptions that a method can throw so that they can decide what to do about them. These exceptions are as much a part of that method's programming interface as its parameters and return value.
The next question might be: "If it's so good to document a method's API, including the exceptions it can throw, why not specify runtime exceptions too?" Runtime exceptions represent problems that are the result of a programming problem, and as such, the API client code cannot reasonably be expected to recover from them or to handle them in any way. Such problems include arithmetic exceptions, such as dividing by zero; pointer exceptions, such as trying to access an object through a null reference; and indexing exceptions, such as attempting to access an array element through an index that is too large or too small.
Generally don't catch an exception unless you plan to HANDLE the exception. Logging, by itself is NOT handliing.
First I found this Java exception handling best practices - How To Do In Java which says that you should never catch the Trowable class nor use e.printStackTrace();
That article, like many, has some good advice and some poor or even bad advice. You get what you pay for!
I've read that you should not catch the Exception class.
Ok - but all that does is indicate that a problem of some sort happened somewhere. Not very useful info. Java goes to a lot of trouble to provide specific exceptions for specific problems.
I've been catching it previously to make sure that some unknown exception doesn't slip through early in the loop and stops all other customers from executing later on in the loop.
If the exception is 'unknown' then maybe it NEEDS to 'stop all other customers from executing later on in the loop'.
That is EXACTLY why you don't want to do that. You need to identify which exceptions should NOT stop processing and which ones should.
Some 'unknown' exceptions can NOT be recovered and indicate a serious problem, perhaps with the JVM itself. You can NOT just blindly keep executing and ignore them without risking data corruption and/or the integrity of the entire system Java is running on.
Is it OK if you just change the implementation to catch the RuntimeException class instead of the Exception class? We're using Java 7 and the Jetty Servlet Container.
No - not if you want a well-behaved system.
Don't catch exceptions unless you HANDLE/resolve them. There are times when it makes sense to log the exception (which does NOT handle it) and then raise it again so that it gets handled properly later. Yes - I know that is contrary to the advice given in that article but, IMHO, that article is wrong about that point.
If you have ever had to maintain/fix/support someone else's Java code you should already understand how difficult it can be to find WHERE a problem occurs and WHAT the exact problem is when exceptions are not handled properly.

Exceptions for repeating Events aren't handled correctly on iPod!?

I have a few repeating all day events set up in my calendar in iCal. If I sync them to my iPod they are transfered correctly.
However, if I move one of them in iCal from say wednesday to tuesday as an exception for this event (for just one week), the event isn't moved on the ipod as well. Instead, after syncing, it shows up on tuesday *as well as* wednesday. In iCal everything is displayed correctly...but on the ipod it is doubled.
Does anyone know how to fix this?
Best regards,
Markus.

Scott,
thanks for your hint. unfortunately this didn't change anything at all.
I still got my repeating events correct on the mac but doubled on the ipod.
Any other ideas?
Best regards,
Markus.

Handle exception 'Program errors' for CL_GUI_ALV_GRID

Hi all,
I am displaying ALV in a dialogbox container, with first column for checkbox.
I have created a pushbutton named RELEASE in the toolbar. Pupose of the Release button is to further process the
rows selected by the user. But clicking on the Release button after checkboxes are selected throws error 'Program errors' which I guess is probably is an exception for method SET_TABLE_FOR_FIRST_DISPLAY of CL_GUI_ALV_GRID. If the button is clicked without touching any of the checkboxes everything works fine. Probably the reference to outtab is lost on clicking the button.
Appreciate any help.
Many thanks.
Vipin.

Hi vipin,
hard to say as you do not give any code detail. In a mixture of classic and oo ABAP a common reason for failure is the use of local (FORM routine) fields for controls and their contents: Entering a FORM routine, DATA is created on the stack, controls with grids may be created - they have their own lifetime, After leaving the Form routine, the stack is cleared. The control will not know this but as soon as a controls event tries to access data, it is a grip into emptiness.
Regards,
Clemens

How to handle exception CX_SY_REF_IS_INITIAL

hi experts,
im working on a test scenario for abap mapping in SAP XI im getting this error
An exception with the type CX_SY_REF_IS_INITIAL occurred, but was neither handled locally, nor declared in a RAISING clause Dereferencing of the NULL reference
i understand that i need to catch this exception in the abap coding but i'm not familiar with oops concepts
can any one please suggest me how to handle this exception for the following code...
method IF_MAPPING~EXECUTE.
break x1149.
* initialize iXML
TYPE-POOLS: ixml.
class cl_ixml definition load.
** Instances & Variable declaration =======================
* instance main factory
TYPES: BEGIN OF t_xml_line,
          data(256) TYPE x,
        END OF t_xml_line.
DATA: l_ixml TYPE REF TO if_ixml,
* instance input stream factory
   l_streamfactory TYPE REF TO if_ixml_stream_factory,
* instance input stream
l_istream TYPE REF TO if_ixml_istream,
* instance input document
l_document TYPE REF TO if_ixml_document,
* instance parse input document
l_parser TYPE REF TO if_ixml_parser,
* instance for elements within the nodes
node      TYPE REF TO if_ixml_node,
*instance of nodemap
nodemap   TYPE REF TO if_ixml_named_node_map,
* instance for iterator
iterator TYPE REF TO if_ixml_node_iterator,
name      TYPE string,
value     TYPE string,
* instance main factory
   o_ixml   TYPE REF TO if_ixml,
* instance output document
   o_document TYPE REF TO if_ixml_document,
* instance output stream
o_istream TYPE REF TO if_ixml_ostream,
* instance parse output document
o_parser TYPE REF TO if_ixml_parser,
* instance fot renderer
renderer type ref to if_ixml_renderer,
irc type i,
l_xml_size   TYPE i,
*ROOT ELEMENT
l_element_MT_DEMANDTEC_COST TYPE REF TO if_ixml_element,
*NEXT CHILD ELEMENT FROM THE ABOVE PARENT
l_element_DT_DEMANDTEC TYPE REF TO if_ixml_element,
*CHILDREN1 ELEMENT FOR DT_DEMANDTEC
l_element_DT_WHSE TYPE REF TO if_ixml_element,
*CHILDREN2 ELEMENT FOR DT_DEMANDTEC
l_element_DT_DC    TYPE REF TO if_ixml_element,
*CHILDREN3 ELEMENT FOR DT_DEMANDTEC
l_element_DT_PLANT    TYPE REF TO if_ixml_element,
*CHILDREN4 ELEMENT FOR DT_DEMANDTEC
l_element_DT_QTY    TYPE REF TO if_ixml_element.
*saving the xml document
DATA: l_xml_table       TYPE TABLE OF t_xml_line.
types: begin of t_source,
          whse(5),
          dc(4) ,
          plant(4),
          qty    type i,
         end of t_source.
types: tt_source TYPE STANDARD TABLE OF t_source.
data: wa_source type t_source.
data: it_source TYPE tt_source,
        ivalue type string.
* Procedures and business logic =======================================
*   Creating the main iXML factory
l_ixml = cl_ixml=>create( ).
*   Creating a stream factory
l_streamfactory = l_ixml->create_stream_factory( ).
* create input stream
l_istream = l_streamfactory->create_istream_xstring( source ).
* initialize input document
l_document = l_ixml->create_document( ).
* Create a Parser
l_parser = l_ixml->create_parser( stream_factory = l_streamfactory
                                      istream        = l_istream
                                      document       = l_document ).
* parse input document
l_parser->parse( ).
*   Validate a document
l_parser->set_validating( mode = if_ixml_parser=>co_validate ).
*   Parse the stream
IF l_parser->parse( ) NE 0.
    IF l_parser->num_errors( ) NE 0.
      DATA: parseerror TYPE REF TO if_ixml_parse_error,
            str        TYPE string,
            i          TYPE i,
            count      TYPE i,
            index      TYPE i.
      count = l_parser->num_errors( ).
      WRITE: count, ' parse errors have occured:'.
      index = 0.
      WHILE index < count.
        parseerror = l_parser->get_error( index = index ).
        i = parseerror->get_line( ).
        WRITE: 'line: ', i.
        i = parseerror->get_column( ).
        WRITE: 'column: ', i.
        str = parseerror->get_reason( ).
        WRITE: str.
        index = index + 1.
      ENDWHILE.
    ENDIF.
ENDIF.
*   Process the document
IF l_parser->is_dom_generating( ) EQ 'X'.
    refresh : it_source.
    node ?= l_document.
    CHECK NOT node IS INITIAL.
*   create a node iterator
    iterator = node->create_iterator( ).
*   get current node
    node = iterator->get_next( ).
*   loop over all nodes
    WHILE NOT node IS INITIAL.
      CASE node->get_type( ).
        WHEN if_ixml_node=>co_node_element.
*         element node
          name    = node->get_name( ).
          nodemap = node->get_attributes( ).
        WHEN if_ixml_node=>co_node_text.
*         text node
          value = node->get_value( ).
          if name eq 'DT_WHSE'.
            wa_source-whse = value.
          ELSEIF name eq 'DT_DC'.
            wa_source-DC = value.
          ELSEIF name eq 'DT_PLANT'.
            wa_source-PLANT = value.
          ELSEIF name eq 'DT_QTY'.
            wa_source-QTY = value.
            COLLECT wa_source INto it_source.
            CLEAR   wa_source.
          ENDIF.
      endcase.
      node = iterator->get_next( ).
    endwhile.
ENDIF.
loop at it_source into wa_source .
    at first.
*       Creating a ixml factory
      o_ixml = cl_ixml=>create( ).
*       Creating the dom object model
      o_document = l_ixml->create_document( ).
    endat.
*       Build and Fill root node MT_DEMANDTEC_COST
    AT FIRST.
      l_element_MT_DEMANDTEC_COST    =
O_document->create_simple_element(
                              name   = 'MT_DEMANDTEC_COST'
                              parent = o_document ).
    ENDAT.
*      Build and Fill Child node DT_DEMANDTEC for parent
*                                                  MT_DEMANDTEC_COST
    l_element_DT_DEMANDTEC    = O_document->create_simple_element(
                                 name   = 'DT_DEMANDTEC'
                                 parent = l_element_MT_DEMANDTEC_COST ).
*      Build and Fill Child node1 DT_WHSE for parent DT_DEMANDTEC
    ivalue              = wa_source-WHSE.
    l_element_DT_WHSE    = O_document->create_simple_element(
                                     name   = 'DT_WHSE'
                                     VALUE = ivalue
                                     parent = l_element_DT_DEMANDTEC ).
*      Build and Fill Child node2 DT_WHSE for parent DT_DEMANDTEC
    ivalue              = wa_source-DC.
    l_element_DT_DC   = O_document->create_simple_element(
                                         name   = 'DT_DC'
                                          VALUE = ivalue
                                parent = l_element_DT_DEMANDTEC ).
*      Build and Fill Child node3 DT_WHSE for parent DT_DEMANDTEC
    ivalue              = wa_source-PLANT.
    l_element_DT_PLANT   = O_document->create_simple_element(
                                             name   = 'DT_PLANT'
                                              VALUE = ivalue
                               parent = l_element_DT_DEMANDTEC ).
*      Build and Fill Child node4 DT_QTY for parent DT_DEMANDTEC
    ivalue              = wa_source-QTY.
    l_element_DT_QTY     = O_document->create_simple_element(
                                             name   = 'DT_QTY'
                                              VALUE = ivalue
                               parent = l_element_DT_DEMANDTEC ).
endloop.
* render document ======================================================
* create output stream
o_istream = l_streamfactory->create_ostream_xstring( result ).
*   Connect internal XML table to stream factory
o_istream = l_streamfactory->create_ostream_itable( table =
l_xml_table ).
renderer = o_ixml->create_renderer( ostream = o_istream
                                          document = o_document ).
irc = renderer->render( ).
* how do i catch the exception for type CX_SY_REF_IS_INITIAL ...?
endmethod.
full reward points for answers.
Thanks & Regards,
Uday Kumar.
Edited by: UDAY on May 6, 2008 9:32 PM

Hi Uday,
Its occurs because you're trying to access a objects with null reference. Or you forgot to create an instance or an error occurs during the instance creation. So You should put all your "Procedures and business logic" inside a Try/catch block. as follow.
" Define a class exception object to get error message......
DATA o_exception TYPE REF TO cx_sy_ref_is_initial.
"// Use the statment Try block to catch the error.
TRY.
*   Creating the main iXML factory
l_ixml = cl_ixml=>create( ).
*   Creating a stream factory
l_streamfactory = l_ixml->create_stream_factory( ).
* create input stream
l_istream = l_streamfactory->create_istream_xstring( source ).
* initialize input document
l_document = l_ixml->create_document( ).
* Create a Parser
l_parser = l_ixml->create_parser( stream_factory = l_streamfactory
                                      istream        = l_istream
                                      document       = l_document ).
* parse input document
l_parser->parse( ).
*   Validate a document
l_parser->set_validating( mode = if_ixml_parser=>co_validate ).
*   Parse the stream
IF l_parser->parse( ) NE 0.
    IF l_parser->num_errors( ) NE 0.
      DATA: parseerror TYPE REF TO if_ixml_parse_error,
            str        TYPE string,
            i          TYPE i,
            count      TYPE i,
            index      TYPE i.
      count = l_parser->num_errors( ).
      WRITE: count, ' parse errors have occured:'.
      index = 0.
      WHILE index < count.
        parseerror = l_parser->get_error( index = index ).
        i = parseerror->get_line( ).
        WRITE: 'line: ', i.
        i = parseerror->get_column( ).
        WRITE: 'column: ', i.
        str = parseerror->get_reason( ).
        WRITE: str.
        index = index + 1.
      ENDWHILE.
    ENDIF.
ENDIF.
*   Process the document
IF l_parser->is_dom_generating( ) EQ 'X'.
    refresh : it_source.
    node ?= l_document.
    CHECK NOT node IS INITIAL.
*   create a node iterator
    iterator = node->create_iterator( ).
*   get current node
    node = iterator->get_next( ).
*   loop over all nodes
    WHILE NOT node IS INITIAL.
      CASE node->get_type( ).
        WHEN if_ixml_node=>co_node_element.
*         element node
          name    = node->get_name( ).
          nodemap = node->get_attributes( ).
        WHEN if_ixml_node=>co_node_text.
*         text node
          value = node->get_value( ).
          if name eq 'DT_WHSE'.
            wa_source-whse = value.
          ELSEIF name eq 'DT_DC'.
            wa_source-DC = value.
          ELSEIF name eq 'DT_PLANT'.
            wa_source-PLANT = value.
          ELSEIF name eq 'DT_QTY'.
            wa_source-QTY = value.
            COLLECT wa_source INto it_source.
            CLEAR   wa_source.
          ENDIF.
      endcase.
      node = iterator->get_next( ).
    endwhile.
ENDIF.
loop at it_source into wa_source .
    at first.
*       Creating a ixml factory
      o_ixml = cl_ixml=>create( ).
*       Creating the dom object model
      o_document = l_ixml->create_document( ).
    endat.
*       Build and Fill root node MT_DEMANDTEC_COST
    AT FIRST.
      l_element_MT_DEMANDTEC_COST    =
O_document->create_simple_element(
                              name   = 'MT_DEMANDTEC_COST'
                              parent = o_document ).
    ENDAT.
*      Build and Fill Child node DT_DEMANDTEC for parent
*                                                  MT_DEMANDTEC_COST
    l_element_DT_DEMANDTEC    = O_document->create_simple_element(
                                 name   = 'DT_DEMANDTEC'
                                 parent = l_element_MT_DEMANDTEC_COST ).
*      Build and Fill Child node1 DT_WHSE for parent DT_DEMANDTEC
    ivalue              = wa_source-WHSE.
    l_element_DT_WHSE    = O_document->create_simple_element(
                                     name   = 'DT_WHSE'
                                     VALUE = ivalue
                                     parent = l_element_DT_DEMANDTEC ).
*      Build and Fill Child node2 DT_WHSE for parent DT_DEMANDTEC
    ivalue              = wa_source-DC.
    l_element_DT_DC   = O_document->create_simple_element(
                                         name   = 'DT_DC'
                                          VALUE = ivalue
                                parent = l_element_DT_DEMANDTEC ).
*      Build and Fill Child node3 DT_WHSE for parent DT_DEMANDTEC
    ivalue              = wa_source-PLANT.
    l_element_DT_PLANT   = O_document->create_simple_element(
                                             name   = 'DT_PLANT'
                                              VALUE = ivalue
                               parent = l_element_DT_DEMANDTEC ).
*      Build and Fill Child node4 DT_QTY for parent DT_DEMANDTEC
    ivalue              = wa_source-QTY.
    l_element_DT_QTY     = O_document->create_simple_element(
                                             name   = 'DT_QTY'
                                              VALUE = ivalue
                               parent = l_element_DT_DEMANDTEC ).
endloop.
* render document ======================================================
* create output stream
o_istream = l_streamfactory->create_ostream_xstring( result ).
*   Connect internal XML table to stream factory
o_istream = l_streamfactory->create_ostream_itable( table =
l_xml_table ).
renderer = o_ixml->create_renderer( ostream = o_istream
                                          document = o_document ).
irc = renderer->render( ).
"   The Statement CATCH define a block that catches the exceptions of the
"   exception class cx_sy_ref_is_initial
    CATCH cx_sy_ref_is_initial INTO o_exception.
" If you need to get the error message text do as follow
DATA errorMsg type string.
" Get the message text
errorMsg = o_exception->GET_TEXT( ).
" Display the error information
MESSAGE errorMsg TYPE 'I'.
ENDTRY.
The TRY block defines a guarded area whose class-based exceptions can be caught in the subsequent CATCH blocks. If no exception occurs in the TRY block and it reaches its end, the system continues the processing after ENDTRY. If a class-based exception occurs in the TRY block, the system searches for an exception handler in the same or an external TRY control structure.
Font: SAP Help
You can see a how to create and use an exception in this example [ ABAP Objects - Defining a Class-based exceptions|https://wiki.sdn.sap.com/wiki/x/19w] .
Best Regards.
Marcelo Ramos

Invalid Handle Exception-What is the reason?

I face with "Invalid Handle exception" (SQLException) while using the following code.
Could anybody tell me the possible reasons/Situation the error rise?
stmt = conn.createStatement();
ResultSet rs = stmt.executeQuery(SQLStmt);
     if(rs!=null){
ResultSetMetaData rsm = rs.getMetaData();
     int totalcols = rsm.getColumnCount();
     Vector temp;
     while (rs.next()) {
     Vector temp = new Vector();
     for (int i = 1; i <= totalcols; i++) {
          String value = rs.getString(i);
          if (value == null) {
          value = "";
     temp.addElement(value);
     }//for loop ends here
     valueVector.addElement(temp);
     rs.close();
     stmt.close();
Thank you all

Vector temp;
while (rs.next()) {
Vector temp = new Vector();Are you sure that this is the code you are running? The reason I ask is that I'm pretty sure that it won't compile, at least under JDK1.4. You should get a compile error something like "temp is already defined".
If thats not the problem you need to find out on which line the error actually occurs. You can get this from the exception by calling the printStackTrace() method.
Col

I have a production mobile Flex app that uses RemoteObject calls for all data access, and it's working well, except for a new remote call I just added that only fails when running with a release build. The same call works fine when running on the device

I have a production mobile Flex app that uses RemoteObject calls for all data access, and it's working well, except for a new remote call I just added that only fails when running with a release build. The same call works fine when running on the device (iPhone) using debug build. When running with a release build, the result handler is never called (nor is the fault handler called). Viewing the BlazeDS logs in debug mode, the call is received and send back with data. I've narrowed it down to what seems to be a data size issue.
I have targeted one specific data call that returns in the String value a string length of 44kb, which fails in the release build (result or fault handler never called), but the result handler is called as expected in debug build. When I do not populate the String value (in server side Java code) on the object (just set it empty string), the result handler is then called, and the object is returned (release build).
The custom object being returned in the call is a very a simple object, with getters/setters for simple types boolean, int, String, and one org.23c.dom.Document type. This same object type is used on other other RemoteObject calls (different data) and works fine (release and debug builds). I originally was returning as a Document, but, just to make sure this wasn't the problem, changed the value to be returned to a String, just to rule out XML/Dom issues in serialization.
I don't understand 1) why the release build vs. debug build behavior is different for a RemoteObject call, 2) why the calls work in debug build when sending over a somewhat large (but, not unreasonable) amount of data in a String object, but not in release build.
I have't tried to find out exactly where the failure point in size is, but, not sure that's even relevant, since 44kb isn't an unreasonable size to expect.
By turning on the Debug mode in BlazeDS, I can see the object and it's attributes being serialized and everything looks good there. The calls are received and processed appropriately in BlazeDS for both debug and release build testing.
Anyone have an idea on other things to try to debug/resolve this?
Platform testing is BlazeDS 4, Flashbuilder 4.7, Websphere 8 server, iPhone (iOS 7.1.2). Tried using multiple Flex SDK's 4.12 to the latest 4.13, with no change in behavior.
Thanks!

After a week's worth of debugging, I found the issue.
The Java type returned from the call was defined as ArrayList. Changing it to List resolved the problem.
I'm not sure why ArrayList isn't a valid return type, I've been looking at the Adobe docs, and still can't see why this isn't valid. And, why it works in Debug mode and not in Release build is even stranger. Maybe someone can shed some light on the logic here to me.

How to handle exceptions of rfc in web dydnpro

hi all,
i want to handle exceptions of Remote function module in webdynpro.how can we do that one.are there any variables in model class for those exceptions.
regards
Naidu

Hi,
Hope the following snippet answers ur query
IWDMessageManager manager = wdComponentAPI.getMessageManager();
               try{
                    wdContext.currentB_Quotation_Createfromdata_InpElement().modelObject().execute();
                    wdContext.nodeOutputQuotation().invalidate();
               } catch(WDDynamicRFCExecuteException ce) {
                    manager.reportException(ce.getMessage(), false);

Handling exception logging in a Java task scheduler program?

I need to design a Task Scheduler Where
1) User should be able to schedule multiple task at the same time.
2) There should be proper error handling on failure of any task and should not affect the other running tasks.
I found the related programme at http://www.roseindia.net/java/example/java/util/CertainAndRepeatTime.shtml
My concern is about handling of point 2 in program provided at above link. Say I schedule a recurring mail send process in above program which will be run first time on 12 september 2011 at 2 am, and will be repeated after every 2 hours Say a one process fais at 8 am. I want to log it in log file with task name and time details. Now if I look at above programme i.e CertainAndRepeatTime.java. This program will exit once it schedules all the tasks. Where and how should handle the logging?
Posted at http://stackoverflow.com/questions/7377204/handling-exception-logging-in-a-java-task-scheduler-program but folks suggesting Quartz scheduler . My Limitation is that i can't for quartz because my project allows me to use only standard java library. Is there any way we can handle logging in the same programme in case of exception.

Well, first of all I wouldn't trust any code from roseindia. So you might want to look for more reliable advice.
As for your logging, you can add it for example to the TimerTask itself. I don't recommend adding logging to that roseindia cr*p though.

Handling exceptions for barcode:

Similar Messages

Maybe you are looking for