About Error Handling.

Hi,
        Can any body give the brief idea of error handling.And what the option containing in the error handling tabs like
1. NO Update , No Reporting.
2. Update Valid Records only ,Reporting not possible(Request red).
3. Update Valid Records only ,Reporting possible(Request green).
          Is these options works above the error tolerance limit or below the error tolerance limit.
      like        Error Tolerance Limit   =   1000.
How can i Test it practically in Navigation.Plz send the detailed information about this.
Thanks in Advance,
D.Malla Reddy.

Hi,
     1 Valid Records Update, No Reporting (Request Red): When you select this option, you tell the system to isolate erroneous records in a data packet from the data load and to load the valid records into the data target. The data upload request remains in red status in the data target and is unavailable for reporting. With this option, the data administrator can check the error records and then manually turn the uploaded request to green, making the data available for reporting.
u2022     2 Valid Records Update, Reporting Possible (Request Green): When you select this option, you tell ETL to make the valid data available immediately for reporting in the data target.
u2022     No Update, No Reporting: When you select this option, you tell the system to suspend data processing to the data targets if it encounters an erroneous record, preventing further data from loading into the data target. The system keeps scanning the remaining data packages for erroneous records.
Another important aspect of error handling is the process to deal with the erroneous records. In SAP NetWeaver BI 7.0, the error handling process identifies the erroneous record from the original data upload request and isolates it by storing the records in a separate container called the error stack. After you correct or modify the erroneous records, you can then load them to the original intended data target by using a special DTP called the error DTP. This helps to ensure data consistency.
you can check the data packets data at monitor
Thanks
Ramesh.
Edited by: Ramesh Raju on Feb 11, 2010 2:24 PM

Similar Messages

Please brief Describes about error handling with example

dear
please describe about error handling and exception handling

Darryl Burke wrote:
This is the third thread you have started here, without bothering to reply to responses on the two earlier threads. Not the best way to continue to get help on a forum, that.Not to mention the fact that it's a horribly broad and vague question that is better answered by a combination of books, tutorials, and google searches.

Question about error-handling in PL/SQL

Hi friends,
I would like to know if there is a way for error handling for insert and update statements in PL/SQL???
Like when for example an insert fails!
thanxx
Schoeib

You should get a book about such fundamentals!
This is not an online course...
begin
insert into emp values(...);
exception
when no_data_found then
when others then
end;

General QUestion about error handling

Hello,
I am writing my own VI's to communicate with my hardware. Each one of the VI's incorporate numerous error checking routines to detect if the desired operation completed correctly. If error(s) are detected with a VI, the "Bundle by Name" VI is used to update the Natiinal Instruments error cluster with the appropriate info each time a error occurs.
What I am finding is that the VI error cluster contains the last error found, instead of the first error found. Please be aware that I am assuming (we know what that stands for) is that the National Instruments error cluster is accumulative, so if I add four errors to the cluster, then the error cluster contains at least four errors.
So how do I find the first error that was entered into the error cluster. I have found a vi called "Find First Error:, but I am confused (as usual) on how to get what I want. So I am asking for "divine guidance" or a kick in behind from the Labview wizards on how to correctly handle errors.
Regards,
Kaspar
Regards,
Kaspar

The cluster is a standard cluster and is not accumulative.
Usually, the way to handle this is to check the error in terminal and if it is has an error to pass the error instead of executing the code. That way, when you have an error, the rest of the code does not execute. Here's an example:
If you want to merge the error numbers, search the forums for Mike Porter's error stacker.
Try to take over the world!

About error handling in session

suppose if we foung error at particular place how we have to correct it

hi,
for handling error records in session, you follow this navigation..
1) goto SM35----> for processing the SESSION.
2) here you select the SESSION.( which was created in bdc program)
3) after selecting the SESSION, you choose LOG tab option.
4) select the session and choose ANALYSE SESSION, here you found two options ALL and INCORRECT which are radiobutton options from this you select INCORECT radiobutton option for displaying the ERROR records and the reasons for the errors.
5) if possible correct the error records manually and process the session.
regards,
Ashok Reddy

About errors handling

suppose if we have 10000 records during session after 5000 records it found error
how we can recover that error and where we have to recover

Refer to this sample report
REPORT ztest_report
NO STANDARD PAGE HEADING
                        LINE-SIZE 255
                        MESSAGE-ID ZRASH.
*                 Internal Table Declarations                          *
*--Internal Table for Data Uploading.
DATA : BEGIN OF IT_FFCUST OCCURS 0,
         KUNNR(10),
         BUKRS(4),
         KTOKD(4),
         ANRED(15),
         NAME1(35),
         SORTL(10),
         STRAS(35),
         ORT01(35),
         PSTLZ(10),
         LAND1(3),
         SPRAS(2),
         AKONT(10),
       END OF IT_FFCUST.
*--Internal Table to Store Error Records.
DATA : BEGIN OF IT_ERRCUST OCCURS 0,
         KUNNR(10),
         EMSG(255),
       END OF IT_ERRCUST.
*--Internal Table to Store Successful Records.
DATA : BEGIN OF IT_SUCCUST OCCURS 0,
         KUNNR(10),
         SMSG(255),
       END OF IT_SUCCUST.
*--Internal Table for Storing the BDC data.
DATA : IT_CUSTBDC LIKE BDCDATA OCCURS 0 WITH HEADER LINE.
*--Internal Table for storing the messages.
DATA : IT_CUSTMSG LIKE BDCMSGCOLL OCCURS 0 WITH HEADER LINE.
DATA : V_FLAG1(1) VALUE ' ',
"Flag used for opening session.
       V_TLINES LIKE SY-TABIX,
       "For storing total records processed.
       V_ELINES LIKE SY-TABIX,
       "For storing the no of error records.
       V_SLINES LIKE SY-TABIX.
       "For storing the no of success records.
*          Selection screen                                            *
SELECTION-SCREEN BEGIN OF BLOCK B1.
PARAMETERS : V_FNAME LIKE RLGRAP-FILENAME,
             V_SESNAM LIKE RLGRAP-FILENAME.
SELECTION-SCREEN END OF BLOCK B1.
*          Start-of-selection                                          *
START-OF-SELECTION.
*-- Form to upload flatfile data into the internal table.
PERFORM FORM_UPLOADFF.
*        TOP-OF-PAGE                                                   *
TOP-OF-PAGE.
WRITE:/ 'Details of the error and success records for the transaction'
ULINE.
SKIP.
*          End of Selection                                            *
END-OF-SELECTION.
*-- Form to Generate a BDC from the Uploaded Internal table
PERFORM FORM_BDCGENERATE.
*--To write the totals and the session name.
PERFORM FORM_WRITEOP.
*&      Form form_uploadff
*     Form to upload flatfile data into the internal table.
FORM FORM_UPLOADFF .
*--Variable to change the type of the parameter file name.
DATA : LV_FILE TYPE STRING.
LV_FILE = V_FNAME.
*--Function to upload the flat file to the internal table.
CALL FUNCTION 'GUI_UPLOAD'
    EXPORTING
      FILENAME                      = LV_FILE
*     FILETYPE                      = 'ASC'
      HAS_FIELD_SEPARATOR           = 'X'
*     HEADER_LENGTH                 = 0
*     READ_BY_LINE                  = 'X'
*     DAT_MODE                      = ' '
*   IMPORTING
*     FILELENGTH                    =
*     HEADER                        =
    TABLES
      DATA_TAB                      = IT_FFCUST
    EXCEPTIONS
      FILE_OPEN_ERROR               = 1
      FILE_READ_ERROR               = 2
      NO_BATCH                      = 3
      GUI_REFUSE_FILETRANSFER       = 4
      INVALID_TYPE                  = 5
      NO_AUTHORITY                  = 6
      UNKNOWN_ERROR                 = 7
      BAD_DATA_FORMAT               = 8
      HEADER_NOT_ALLOWED            = 9
      SEPARATOR_NOT_ALLOWED         = 10
      HEADER_TOO_LONG               = 11
      UNKNOWN_DP_ERROR              = 12
      ACCESS_DENIED                 = 13
      DP_OUT_OF_MEMORY              = 14
      DISK_FULL                     = 15
      DP_TIMEOUT                    = 16
      OTHERS                        = 17
IF SY-SUBRC = 0.
*--Deleting the headings from the internal table.
    DELETE IT_FFCUST INDEX 1.
*--Getting the total number of records uploaded.
    DESCRIBE TABLE IT_FFCUST LINES V_TLINES.
ENDIF.
ENDFORM.                    " form_uploadff
*&      Form Form_bdcgenerate
*     Form to Generate a BDC from the Uploaded Internal table
FORM FORM_BDCGENERATE .
*--Generating the BDC table for the fields of the internal table.
LOOP AT IT_FFCUST.
    PERFORM POPULATEBDC USING :
                                'X' 'SAPMF02D' '0105',
                                ' ' 'BDC_OKCODE' '/00' ,
                                ' ' 'RF02D-KUNNR' IT_FFCUST-KUNNR,
                                ' ' 'RF02D-BUKRS' IT_FFCUST-BUKRS,
                                ' ' 'RF02D-KTOKD' IT_FFCUST-KTOKD,
                                'X' 'SAPMF02D' '0110' ,
                                ' ' 'BDC_OKCODE' '/00',
                                ' ' 'KNA1-ANRED' IT_FFCUST-ANRED,
                                ' ' 'KNA1-NAME1' IT_FFCUST-NAME1,
                                ' ' 'KNA1-SORTL' IT_FFCUST-SORTL,
                                ' ' 'KNA1-STRAS' IT_FFCUST-STRAS,
                                ' ' 'KNA1-ORT01' IT_FFCUST-ORT01,
                                ' ' 'KNA1-PSTLZ' IT_FFCUST-PSTLZ,
                                ' ' 'KNA1-LAND1' IT_FFCUST-LAND1,
                                ' ' 'KNA1-SPRAS' IT_FFCUST-SPRAS,
                                'X' 'SAPMFO2D' '0120',
                                ' ' 'BDC_OKCODE' '/00',
                                'X' 'SAPMF02D' '0125',
                                ' ' 'BDC_OKCODE' '/00',
                                'X' 'SAPMF02D' '0130',
                                ' ' 'BDC_OKCODE' '=ENTR',
                                'X' 'SAPMF02D' '0340',
                                ' ' 'BDC_OKCODE' '=ENTR',
                                'X' 'SAPMF02D' '0360',
                                ' ' 'BDC_OKCODE' '=ENTR',
                                'X' 'SAPMF02D' '0210',
                                ' ' 'KNB1-AKONT' IT_FFCUST-AKONT,
                                ' ' 'BDC_OKCODE' '/00',
                                'X' 'SAPMF02D' '0215',
                                ' ' 'BDC_OKCODE' '/00',
                                'X' 'SAPMF02D' '0220',
                                ' ' 'BDC_OKCODE' '/00',
                                'X' 'SAPMF02D' '0230',
                                ' ' 'BDC_OKCODE' '=UPDA'.
*--Calling the transaction 'fd01'.
    CALL TRANSACTION 'FD01' USING IT_CUSTBDC MODE 'N' UPDATE 'S'
    MESSAGES INTO IT_CUSTMSG.
    IF SY-SUBRC <> 0.
*--Populating the error records internal table.
      IT_ERRCUST-KUNNR = IT_FFCUST-KUNNR.
      APPEND IT_ERRCUST.
      CLEAR IT_ERRCUST.
*--Opening a session if there is an error record.
      IF V_FLAG1 = ' '.
        PERFORM FORM_OPENSESSION.
        V_FLAG1 = 'X'.
      ENDIF.
*--Inserting the error records into already open session.
      IF V_FLAG1 = 'X'.
        PERFORM FORM_INSERT.
      ENDIF.
*--Populating the Success records internal table.
    ELSE.
      IT_SUCCUST-KUNNR = IT_FFCUST-KUNNR.
      APPEND IT_SUCCUST.
      CLEAR IT_SUCCUST.
    ENDIF.
*--Displaying the messages.
    IF NOT IT_CUSTMSG[] IS INITIAL.
      PERFORM FORM_FORMATMSG.
    ENDIF.
*--Clearing the message and bdc tables.
    CLEAR : IT_CUSTBDC[],IT_CUSTMSG[].
ENDLOOP.
*--Getting the total no of error records.
DESCRIBE TABLE IT_ERRCUST LINES V_ELINES.
*--Getting the total no of successful records.
DESCRIBE TABLE IT_SUCCUST LINES V_SLINES.
*--Closing the session only if it is open.
IF V_FLAG1 = 'X'.
    PERFORM FORM_CLOSESESS.
ENDIF.
ENDFORM.                    " Form_bdcgenerate
*&      Form populatebdc
*       FOrm to Populate the BDC table.
FORM POPULATEBDC USING    VALUE(P_0178)
                           VALUE(P_0179)
                           VALUE(P_0180).
IF P_0178 = 'X'.
    IT_CUSTBDC-PROGRAM = P_0179.
    IT_CUSTBDC-DYNPRO = P_0180.
    IT_CUSTBDC-DYNBEGIN = 'X'.
ELSE.
    IT_CUSTBDC-FNAM = P_0179.
    IT_CUSTBDC-FVAL = P_0180.
ENDIF.
APPEND IT_CUSTBDC.
CLEAR IT_CUSTBDC.
ENDFORM.                    " populatebdc
*&      Form FORM_OPENSESSION
*       Form to Open a session.
FORM FORM_OPENSESSION .
*--Variable to convert the given session name into reqd type.
DATA : LV_SESNAM(12).
LV_SESNAM = V_SESNAM.
*--Opening a session.
CALL FUNCTION 'BDC_OPEN_GROUP'
   EXPORTING
     CLIENT                    = SY-MANDT
     GROUP                     = LV_SESNAM
     HOLDDATE                  = '20040805'
     KEEP                      = 'X'
     USER                      = SY-UNAME
     PROG                      = SY-CPROG
* IMPORTING
*    QID                       =
   EXCEPTIONS
     CLIENT_INVALID            = 1
     DESTINATION_INVALID       = 2
     GROUP_INVALID             = 3
     GROUP_IS_LOCKED           = 4
     HOLDDATE_INVALID          = 5
     INTERNAL_ERROR            = 6
     QUEUE_ERROR               = 7
     RUNNING                   = 8
     SYSTEM_LOCK_ERROR         = 9
     USER_INVALID              = 10
     OTHERS                    = 11
IF SY-SUBRC <> 0.
    WRITE :/ 'Session not open'.
ENDIF.
ENDFORM.                    " FORM_OPENSESSION
*&      Form FORM_INSERT
*       fORM TO INSERT ERROR RECOED INTO A SESSION.
FORM FORM_INSERT .
*--Inserting the record into session.
CALL FUNCTION 'BDC_INSERT'
    EXPORTING
      TCODE                  = 'FD01'
*     POST_LOCAL             = NOVBLOCAL
*     PRINTING               = NOPRINT
*     SIMUBATCH              = ' '
*     CTUPARAMS              = ' '
    TABLES
      DYNPROTAB              = IT_CUSTBDC
    EXCEPTIONS
      INTERNAL_ERROR         = 1
      NOT_OPEN               = 2
      QUEUE_ERROR            = 3
      TCODE_INVALID          = 4
      PRINTING_INVALID       = 5
      POSTING_INVALID        = 6
      OTHERS                 = 7
IF SY-SUBRC <> 0.
    WRITE :/ 'Unable to insert the record'.
ENDIF.
ENDFORM.                    " FORM_INSERT
*&      Form FORM_CLOSESESS
*       Form to Close the Open Session.
FORM FORM_CLOSESESS .
CALL FUNCTION 'BDC_CLOSE_GROUP'
    EXCEPTIONS
      NOT_OPEN    = 1
      QUEUE_ERROR = 2
      OTHERS      = 3.
IF SY-SUBRC <> 0.
ENDIF.
ENDFORM.                    " FORM_CLOSESESS
*&      Form FORM_FORMATMSG
*       Form to format messages.
FORM FORM_FORMATMSG .
*--Var to store the formatted msg.
DATA : LV_MSG(255).
CALL FUNCTION 'FORMAT_MESSAGE'
    EXPORTING
      ID        = SY-MSGID
      LANG      = SY-LANGU
      NO        = SY-MSGNO
      V1        = SY-MSGV1
      V2        = SY-MSGV2
      V3        = SY-MSGV3
      V4        = SY-MSGV4
    IMPORTING
      MSG       = LV_MSG
    EXCEPTIONS
      NOT_FOUND = 1
      OTHERS    = 2.
IF SY-SUBRC = 0.
    WRITE :/ LV_MSG.
ENDIF.
ULINE.
ENDFORM.                    " FORM_FORMATMSG
*&      Form form_writeop
*       To write the totals and the session name.
FORM FORM_WRITEOP .
WRITE :/ 'Total Records Uploaded :',V_TLINES,
           / 'No of Error Records :',V_ELINES,
           / 'No of Success Records :',V_SLINES,
           / 'Name of the Session :',V_SESNAM.
ULINE.
ENDFORM.                    " form_writeop

Transaction and Error handling in Mediator 11g

Hi Experts/Gurus/All,
We have following scenario in Mediators :-
For Inbound Interfaces :-
M1-->M2-->M3
M1 calls M2 and M2 calls M3
There are 3 mediators, Mediator#1(M1),Mediator#2(M2) and Mediator#3(M3)
M1 performs a FIle Read and do a ABO-->OAGIS conversion
M2 performs routing
M3 performs a OAGIS -->ABO(JDE E1) conversion.
Now,we are in middle to decide the Fault Handling Mechanism for this case.
M1 is Asynchronous , M2 is Synchronous and M3 is also Synchronous.
Question is :
1. M1 will start a new Transaction,Do M1 will propogate the same transaction to M2 which,as being Synch,propogates the same transaction to M3 ?
2. How will the commit and Roll back will be taken care of?
3. What if M1 errors out?
4. Whatif M2 errors out?
5. What if M3 errors out?
In question 3,4 and 5:
What will happen will the Full Transaction ? If M3 erros out,would the Entire Transaction Propogated by M1 will be roll back?
Also ,How about Error handling in this case:
Do I need to create seperate fault-policy.xml and fault-binding.xml for M1,M2 and M3 ?
Another Scenario is of OUTBOUND interfaces :-
M1-->M2-->M3
M1 calls M2 and M2 calls M3
However , M1,M2 and M3 are all Asynchronous.
In this scenarios how would I handle following :-
1. If M2 Errors out,I need the entire Interface which comprises of M1-->M2-->M3 to roll back?
2. If M3 Errors out,I need the entire Interface which comprises of M1-->M2-->M3 to roll back?
3. Seperate Transactions means I have to create seperate fault-policy.xml and fault-mapping.xml to handle errors?

Hi,
You could create a package, and use the OdiSqlUnload to export the data into a flat file (csv) from snp_check_tab, then amend it. Then create an interface to load the data from the flat file to your tables, either via external tables or SQL Loader.
Question is, why are you amending data going from source to target? there surely has to be something wrong with the Architecture (especially if you are getting errors in production). If you amend data, so that it is different in source as it is in target, then when it comes to regression testing, this will never match.
The errors should go be fixed at source, and either you, or the business should have access to do so.
Cheers
Bos

Best error handling for visa calls?

We are using some handlers we've devloped for power supply handling (over GPIB). The power supplies are SCPI and use SCPI/GPIB commands. The handlers use the NI visa api's Read() and Write() functions to send the commands. They work fine, for the most part, and we've been using them for a number of years.
However, we're hearing reports that there may have been a few times that commands were not executed on the power supply and our handler did not report back any error.
So, I'm trying to update these handlers to add a little error checking to make them more robust and hopefully we'll catch this error if it happens again.
For error handling, I've come up with 3 solutions and tried all 3. I find some benefits and drawbacks with each and hoped I could get your opinions about error handling as I'm not overly familiar with some of the methods.
Method 1:
Set the Event Status Enable register to catch all events (or all that I care about).
Read status byte (STB?) after each command and check the event bit and then event status bit if event bit set.
Drawback1: I have one power supply that does not implement this correctly and a second type that appears to not be working correctly either.
Drawback2: Errors are generic. I'll know if I got, for example, a DDE (Device Dependant Error), but I won't know more detail than that.
Method 2:
After each command sent, read the error queue with the System:Error? query.
Drawback: It seems I get a lot of messages back in this method that aren't real errors. It's very "noisy" and I have no way to distinguish real errors from "noise" messages like "query interrupted" and such.
Method 3:
Check the return code of the Visa Read() and Write() commands. At first I didn't think this was very robust, but after seeing the list of errors here, I'm beginning to think that these might be more robust and detailed than Method 1. However, I'm not sure.
So is method 3 as robust as it looks, or is there a combination/comprimise I can make, or another method I did not mention which is best to trap errors from Visa Reads/Writes to these GPIB power supplies? Keep in mind that the handlers work for a number of different power supplies and its likely that some things may be implemented differently between supplies....so its best to stick with somethind standard that will work on all power supplies.

Hi KingTermite,
I hope you will got answer of the question and may be implemeted something .It was really a nice discussion .I am also facing the same issue where I am communicating with different instrument using GPIB communication and RS 232 too.
Can you share and discuss about the implementation of your initiative.
Best Regards
Regards:
Vaibhav Kanchan
Sr. Engineer
NI Certified LabVIEW Developer(CLD)
NI Certified TestStand Developer(CTD}

Error Handling in Oracpe form 9.4.0

Hi,
Have you got good documentaion about error handling in Oracle form 9.0.4? If yes, Could you let me know?
Many thanks
Michael

Michael,
Although, link I'm listing here is for Forms 4.5, the concepts of Error Handling still apply as Forms Error Handling has not changed significantly.
[Oracle Forms Developer and Forms Server Documentation|http://www.oracle.com/technology/documentation/forms.html]
Select the "A32506_2 PDF Forms 4.5 Advanced Techniques" option.
You can also try the [Oracle9iDS Forms Developer Reference Guide|http://www.oracle.com/technology/documentation/forms/902docs/9iRefGuide.zip] from the [Link to Oracle Forms 10g (10.1.2), Oracle Forms 10g (9.0.4), and Oracle9i Forms (9.0.2) Documentation|http://www.oracle.com/technology/documentation/9i_forms.html]. This is a .zip file which contains the "Forms 9i Reference Guide" pdf file.
Hope this helps.
Craig...

Error handling, logging and monitoring business process

I would like to know more about error handling, logging and monitoring in business process? Can someone give more information on this one?

Chandran
Please refer to following tutorials to understand each of these topics in detail:
Validations:
http://www.orafmwschool.com/validations/
Exception Handling:
http://www.orafmwschool.com/exception-handling/
Fault Management Tutorial:
http://www.orafmwschool.com/fault-management-tutorial/
Business Activity Monitoring Tutorial:
http://www.orafmwschool.com/bam-tutorial/
You'll have to refer to Oracle documentation to understand more finer details.
-Amjad.

Error Handler Settings

Can anybody give me more insights about Error Handler Settings in CRM Middleware. Transaction SMW00.
I need to execute a custom function module, if the BDOC errors out. Also need to send an email message with details.
Any help would be appreciated.
Thanks!

HI
Error Handling Configuration SMW00
Different assignments of error actions are possible:
> Standard Error Action (valid for all messages)
> Error Action for a Specific BDoc Type
> Error Action for a Specific Site Type
> Error Action for Aborted Messages
> These four logical levels are used in reverse order to determine the error actions to be carried out. If no
specific error action has been assigned to a message, the least specific action (this means the default
action) starts.
> You can choose the following actions for a message:
> Workflow event: the start event SERVICEERROROCCURRED of object type MIDMESSAGE has
been prepared (the end event is SERVICEERRORFINISHED). This event triggers a work item of
standard task TS75110000 (MIDMESSAGE.ShowMessage).
As the event is executed, you can view the message and decide on what to do with it (Deletion,
Resubmission, Resume Processing with the next service).
> E-mail function:
> Customer function: Calls a customer function module.
Hope it helps

Is including an error handler in every procedure OK?

Hello,
I have read a lot of articles about error handling on the internet but could not find advice on whether it is good/acceptable practice to put a handler in every procedure. My goal
when debugging is to break on every error, so that the relevant variables are still in scope, and I can view them and react to the error. Is there a VS setting for this, or do I need to achieve this via error handling?
In VB6 I think that there used to be a “Break on all errors” option.
Currently, many procedures in my code do not have error handlers. When an error is encountered in a procedure that does not have an error handler, I believe that control is passed back down the stack to the first procedure that has a Catch.
This makes it hard to debug, because the error variables that I need to review are out of scope.
Therefore, if one is not worried about performance considerations, is it reasonable/best practice to include an error handler in every procedure where there might conceivably be an error?
Also, how will the above approaches affect runtime behaviour?
Many thanks.
Keith
R K Howard

Hi Keith,
First, just to be clear, I am going to assume that by error handling we are talking about Try-Catch blocks in code. As Acamar said, if you write a block of code that has the potential to fail, and you have a plan for doing something when that failure
occurs, then definitely wrap the code block in a Try-Catch.
As for what happens in the debugger when an error occurs, it depends on the context of the error and the assembly in which it occurred. If you are still on the UI thread and the error occurred in your code or a base class library, then execution
will stop on the line of code that caused the error - with or without a Try-Catch. If however the error occurred in another thread, asynchronously, or within an assembly for which you do not have source code (or in unmanaged code), then the debugger
will break at the lowest spot in the stack where managed code with known source was executed, or nowhere (no source available) if there is no source code or you broke in unmanaged code. In these cases, adding a Try-Catch might let you break closer to
the exception because there is managed code executed to create the Try statement - but it still doesn't let you break
at the actual exception because there's still either no source code or the error is unmanaged.
So I guess the answer is two-part: don't be afraid to use Try-Catch anywhere that it makes sense, and wait for the improved debugging experience in the next version of Visual Studio (they're improving the ability to debug with secondary threads and async
code execution).
Reed Kimble - "When you do things right, people won't be sure you've done anything at all"

About ale error handling in workflow?

Hi,
can any one explian in detail ale error handling through workflow,its urgent for me.
Regards,
phani

Hi Srikanth,
follw the steps it will helpful u,
Pre-requisites.
It is assumed that the reader of this article has some knowledge in SAP workflow BOR objects and ALE Idoc process like process code, Partner Profile etc.
Description
Here, we will be discussing in details the Error handling of an Inbound Idoc through triggering an event, which in turn will be triggering a workflow attached to the workflow.
Steps:-
1.     Create custom BOR object with the events, Start and Stop event
2.     Create a workflow for the error handling, like generating a notification whenever an error occurred in the Inbound Idoc.
3.     Creation of Function Module and attachment with the Process Code
4.     Create the settings for the Inbound Process of the Idoc through the Process Code.
Creation of BOR objects. Go to the[http://www.****************/Tutorials/ALE/ErrorHandling/page3.htm] transaction SWO1.
Enter a name for the Object type and click CREATE button for creating the custom BOR object.
Enter the details required for creating the BOR objects...
Create the Key fields and events of the BOR object.
For creating the Key fields place the cursor on the Key fields and Click on the Create Button
Create events for triggering the workflow and stopping the workflow.
For creating the event place the cursor on the EVENTS and Click the create button like Key fields.
Create two events.
Enter the event name description etc and proceed further to create it.
Similarly create another event for ending the Workflow in the similar manner like that created earlier.
Now, Generate the BOR object through the generate button
Release the EVENTS and subsequently release the BOR object.
After the creation of BOR object
Create a workflow for the generation of notification whenever an error is reached in the Inbound Idoc.
Execute the transaction SWDD.
Click on the CREATE button for creating the workflow for error handling.
Choose the Step type to be inserted for the notification like here we are using Send Mail option for sending a mail to the user whenever any error occurred.
Activate the Workflow and test it whether it is working as per the requirement.
After the successful completion it is required to attach the workflow with the event.
Go to the Header section (Denoted by CAP).
Go to the Start Events TAB.
Enter the details of the event with which the workflow should be linked like the category, BOR object type and the event with which that should be linked.
Enter here the BOR object that has been created and give the name of event created for starting the workflow.
Click on the Binding Button for generating the binding between the event and the workflow.
Click on the Binding Button for generating the binding between the event and the workflow.
Generate the binding and click OK button to save the binding.
Click on Activate / deactivate button for activating the linkage.
After the successful linkage the following sign will appear on the workflow.....
This shows that the workflow has been linked to the event and it will be triggered whenever that particular event will be triggered.
After the creation and successful linkage of workflow with the event it is required it is required to generate a function module and attached it to the process code.
Go to SE37 transaction and copy a standard process code function module to a custom one. Do no delete any parameters from the function module as the SAP standard program itself is calling this.
In that function module do the required validation and whenever the validation fails set a standard parameter WORKFLOW_RESULT to 9999 from within the function module, otherwise normally proceed to set the status to 53.
After the creation of function module it is required to attach it to the process code and corresponding attached to the message type at the Partner Profile stage.
The process code is being created through the transaction WE42
Go to the change mode and click the New Entries button for creating new process code.
Enter the Process Code Name, description and choose the processing type as Processing by function module. Click on the extension button of Identification.
The details for the of the Process Code after clicking the identification button will be
Whenever idoc arrives into the Destination system then the standard SAP triggers the Process code attached to the Message type in the partner profile. The partner profile is being maintained in the transaction WE20.
Since, it is and inbound scenario so the message type and the corresponding process code will be maintained for the Inbound Parameters.
Click on Create Inbound Parameters button for creating new Inbound Message type and the corresponding message type.
Enter the process code for the corresponding message type.
Click SAVE button for saving the changes.
Whenever the IDOC arrives into the target system, it checks the partner profile and finds the corresponding process code. The process code is being linked with the function module through which the IDOC is required to be processed.
Regards,
Phani.

LV7.1 Strange behavior with Automatic Error Handling occuring when it shouldn't [LV 7.1 Pro on WinXP for Tablet PC's]

[LV 7.1 Pro on WinXP for Tablet PC's]
I recently let a rather large LV app of mine run in the development environment while I was out for a couple of days. Upon returning I found that the app had hung for ~22 hours waiting for an answer to an Automatic Error Handling (AEH) dialog proclaiming an Error 7 in New File without any indication of the VI hierarchy that called New File. I set about ensuring that AEH dialogs would not pop up and have not been able to discover how I could have possibly received one in the first place.
Subsequent investigation revealed:
Neither AEH option in Options>Block Diagrams were checked.
Network problems had occurred around the time that the app had hung. All file paths are network paths when running in the development environment, so the cause of the error was most likely valid, even if the AEH dialog appearance wasn't.
My app has only one instance where the New File primitive is used by me. That subVI and all others above it in the hierarchy DO NOT have the AEH property enabled. The error out cluster of New File in my subvi is wired.
My app has three instances where New File is called from a vi.lib vi (Open/Create/Replace File.vi, Open Config Data.vi, and Prompt Web Browser Path.vi), none of which have the AEH property enabled. Nor does any of their calling VI's. All three instances also have their error out cluster wired.
A utility to examine the AEH property of all VI's (with all top level and dynamic VI's loaded) in memory reported that only 1 of 308 vi's ( RGT Does File Exists.vi from the Report Generation Toolkit) had that property true. That vi has no subVI's other than the File/Directory Info primitive and no calling VI's in common with any of the vi's that call New File, except a top level VI.
As long as 'Enable automatic error handling dialogs' remains unselected in options>block diagram, I am unable to get an AEH dialog for either the New File or File/Directory Info primitives in a test VI with AEH property enabled and their error out clusters unwired no matter what invalid path I pass to the functions. As soon as the options>block diagram>Enable AEH dialogs' is selected, both primitives fire AEH dialogs with no error out wired and don't when wired. i.e. works as advertised.
In other words I can find no reason why I should have gotten the problem AEH dialog...
I cannot afford for this app to hang because of a network problem, other portions of the app that were running concurrently correctly handled the error and, had the AEH dialog not appeared, the app would have made corrections or shutdown in an orderly fashion.
Any ideas?

Very good.
Write Characters to File.vi>Open/Create/Replace File.vi>New File
New File throws the error. Open/Create/Replace strips the hierarchy from the source of the error. Write Characters passes it to the General Error Handler. I never looked above O/C/R file in the hierarchy except for enable automatic error handling property. The tip-off should have been to realize that O/C/R file was stripping the hierarchy from the error and look above that.
The real irony is that Write Characters was being used to log error cluster data to an error log file...
Save as... Copy without updating... the OEM 'Write Characters to File' is gone from this app.
Thanx (a bunch)

Error handling in process chain-doubts

Hi ,
I have some doubts in error handling of process chains.
1) I have aprocess load infopackeage and subsequent process is update fromPSA.
process load infopackage got failed , so i loaded the IP manually and repeated the next i.e process update from PSA .
How to correct the process chain from now?
2) I have aprocess load infopackeage and subsequent process is Delete request in infocube .process load infopackage got failed , so i loaded the IP manually and repeated the next process i.e Delete request in infocube. Chain continued by deleting the right request . How this is possible ?
Plz help me as this is urgent and daily i have to deal with this issues. If any documents on error handling is greatly appreciated.
My mail id is [email protected]
Regards,
Pavan

Hi Pavan,
Hope the following links will give u a clear idea about process chains and clear ur doubts.
Business Intelligence Old Forum (Read Only Archive)
http://help.sap.com/saphelp_nw2004s/helpdata/en/8f/c08b3baaa59649e10000000a11402f/frameset.htm
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/8da0cd90-0201-0010-2d9a-abab69f10045
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/19683495-0501-0010-4381-b31db6ece1e9
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/36693695-0501-0010-698a-a015c6aac9e1
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/9936e790-0201-0010-f185-89d0377639db
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/3507aa90-0201-0010-6891-d7df8c4722f7
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/263de690-0201-0010-bc9f-b65b3e7ba11c
/people/siegfried.szameitat/blog/2006/02/26/restarting-processchains
Errors in monitoring of process chains can be categorized into 4 different sections...
Master data - Full Update
Master data - Delta Update
Transaction data - Full Update
Transaction data - Delta Update.. in terms of loading of data which can be due to server shut down or system maintenance... errors due to incorrect entries in the OLTP system in which case you'll have to fix the errors in the PSA and manually load the data...
Otherwise it can have errors on Attribute change run being locked by some other job... Aggregate Roll up failing because of attribute change run being run at the same time... Problem with hierarchies and save hierarchies...
There can be problems with the data store activation if the ODS object contains any incorrect request sitting inside it... then, you need to delete the incorrect request and reload the data again...
In case of Transaction Delta failure, you'll have to request for a repeat either manually in the infopackage or using the repeat option if available on right clicking the load event...
For Master Data Delta failures, you need to do an Re-init by deleteing the previous initalization condition in the "initalization option for source systems" in the menu scheduler or reschedule the enitre chain... because, master data generally do not support repeat of last delta ...
U can even look into these links:
/people/siegfried.szameitat/blog/2006/02/26/restarting-processchains
For common data load errors check this link:
/people/siegfried.szameitat/blog/2005/07/28/data-load-errors--basic-checks
****Assign Points if Helpful****
Regards,
Ravikanth.

About Error Handling.

Similar Messages

Maybe you are looking for