Error handling for input validations

hi,
Problem:I'm writing FM for the material plant details on inputs material and plant.
                   if material is not valied and i need to show error messages
                    if material is not in plant then it shows relevent Error messages
                   i need to handle all possiable error messages.
Requirement:I need standard FM to handle any type of error messages that will eraise,
                   that i need to show.
could anyone tel me any standard FM to handle any type Error messages.
Thanks in Advance.
sivakumar

Hi siva,
In the past I have used the following function modules to handle multiple error messages;
1.
CALL FUNCTION 'MESSAGES_INITIALIZE' "To initialise the storage table
    EXPORTING
      collect_and_send   = ' '
      reset              = 'X'
      line_from          = ' '
      line_to            = ' '
      i_store_duplicates = ' '
      check_on_commit    = 'X'
      i_reset_line       = ' '.
2.
CALL FUNCTION 'MESSAGE_STORE' " Use to store each message one by one as they occur
    EXPORTING
      arbgb                  = p_msid
      msgty                  = p_tipo
      msgv1                  = p_var1
      msgv2                  = p_var2
      msgv3                  = p_var3
      msgv4                  = p_var4
      txtnr                  = p_txtnr
    EXCEPTIONS
      message_type_not_valid = 1
      not_active             = 2
      OTHERS                 = 3.
3.
CALL FUNCTION 'MESSAGES_SHOW' " Use at the end to finally display the messages
    EXPORTING
      object             = text-004
      send_if_one        = 'X'
      i_use_grid         = 'X'
    EXCEPTIONS
      inconsistent_range = 1
      no_messages        = 2
      OTHERS             = 3.
I hope this will help you.
Regards,
Simon

Similar Messages

Option for error handling for DTP, ' no updata, no reporting" and "deactiva

Hello Gurus,
     option for error handling for DTP, ' no updata, no reporting" and "deactivated" , please give some explanation and instance for them?
Many Thanks,

On the Update tab page, specify how you want the system to respond to data records with errors:
                            a.      No update, no reporting (default)
If errors occur, the system terminates the update of the entire data package. The request is not released for reporting. However, the system continues to check the records.
                            b.      Update valid records, no reporting (request red)
This option allows you to update valid data. This data is only released for reporting after the administrator checks the incorrect records that have not been updated and manually releases the request by setting the overall status on the Status tab page in the monitor (QM action).
                            c.      Update valid records, reporting possible
Valid records can be reported immediately. Automatic follow-up actions, such as adjusting the aggregates, are also carried out.
http://help.sap.com/saphelp_smehp1/helpdata/en/42/fbd598481e1a61e10000000a422035/content.htm
Hope it helps.
rgds, Ghuru

Error handling for work item

Dear All,
     When I trigger my workflow from SWUE,the workflow containers must be populated with agent name.But it is populated only with 'US'.Please suggest.
     On the other hand, when I trigger my workflow from ME21N,the workflow goes into error.The error statement is "Exception occurred - Error handling for work item 000000954797".What is the problem?
    Please suggest the solution for which I will be grateful.
Thanks and regards,
S.Suresh

Dear ,
I use bus2012 as BOR and event as created.
When I create purchase order from ME21N,bus2012 is not triggering.Instead FREBUS2012 gets triggered which is a subtype of bus2012.
At SWETYPV,event linkage is activated only for BUS2012 and there is no entry at SWETYPV for FREBUS2012.
Though I configured the workflow with start events:BUS2012->created,why FREBUS2012 should trigger my workflow which is not seen in SWETYPV?How to override it?Please suggest.
There is no start conditions for my workflow.Whenever purchase order is created,this workflow should trigger.
So,the parameters passed between even to workflow are
&_EVT_OBJECT&    ->        &BUS2012&
&_EVT_CREATOR&   ->     & WFINITIATOR&
Thanks and regards,
S.Suresh

Error handling for a save button

hi. how do i get error handling say in a button, and then to give an error to the user, without crashing the whole application. can any one point me to any articles, tried searching , and not finding wxactly what i am looking for. thanks.
http://startrekcafe.stevesdomain.net http://groups.yahoo.com/groups/JawsOz

hi. maybe i did not make my self clear. okay, here's how this button works, you have a open dialog button, and a open dialog box, you click the file, and it loads in the data grid. now you click on the save button, and a message says file was saved, need
try / catch code, to catch this, if the file was not saved, or other errors, then a error friendly message, any code for this. read the article, but need a specific error handler for the save button, like i had for the open dialog file dialog box. any suggestions,
or links, to look at sample code. thanks.
http://startrekcafe.stevesdomain.net http://groups.yahoo.com/groups/JawsOz

Error handling for RGB values

Hi
I am having problems doing error handling for RGB values. I have a Java applet with 3 JTextFields whose values are parsed as int variables and stored as ints. If a value is entered that is not a value between 0 and 255 is entered, the appropriate field/s should be set to an empty string.
The problem I am having is that I am using try/catch block to try to parse as an int but then it breaks out of execution completely.
I hope this makes sense and that someone can help.
Thanks!

this is because your code is probably inside one giant try catch block, what you need to do is have small ones in places where you do the parsing.
post code and i can show you how to modify it

Error Handling for Outbound IDOC - COSMAS (Cost Center Master)

Hi,
I need to trigger a mail to SAP inbox whenever a outbound idoc fails for any reason.
I know how to do it for inbound or outbound transaction data, but not sure how to do error handling for outbound master data.
Could one of you help me understand the same.
Thanks in Advance,
Vinoth

Hey Vinoth,
Do you want decide the recipient of the mail dynamically? am asking because if you give the USER NAME in the partner profile and when ever a IDOC fails a mail will automatically reach the user inbox automatically
let me know if i answered ur question.
Thanks,
Santhosh

Latest Error Handling for Dynamic Actions

Is there any documentation on the Latest Error Handling for Dynamic Actions?

BillC,
Interesting that I was looking around for the same thing after seeing a Foreign Key violation in my application.
I found this article by Patrick Wolf:
APEX 4.1 – Error Handling Improvements – Part 1
http://www.inside-oracle-apex.com/apex-4-1-error-handling-improvements-part-1/
I believe you need to be on 4.1 or later though.
Thanks,
Joe

How do we use Data rules/error table for source validation?

How do we use Data rules/error table for source validation?
We are using OWB repository 10.2.0.3.0 and OWB client 10.2.0.3.33. The Oracle version is 10 G (10.2.0.3.0). OWB is installed on Linux.
I reviewed the posting
Re: Using Data Rules
Thanks for this forum.
I want to apply data rules to source table/view and rule violated rows should go to defined error table. Here is an example.
Table ProjectA
Pro_ID Number(10)
Project_name Varchar(50)
Pro_date Date
As per above posting, I created the table in object editor, created the data rule
NAME_NOT_NULL (ie project name not null). I specified the shadow table name as ProjectA_ERR
In mapping editor, I have projectA as source. I did not find error table name and defined data rules in table properties. It is not showing up the ERR group in source table
How do we bring the defined data rules and error table into mapping?
Are there any additional steps/process?
Any idea ?
Thanks in advance.
RI

Hi,
Thanks for your reply/pointer. I reviewed the blog. It is interesting.
What is the version of OWB used in this blog?
After defining data rule/shadow table, I deployed the table via CC. It created a error table and created the all the source coulmns in alphabatical order. If I have the primary key as 1st coulmn (which does not start with 'A') in my source, it will apprear middle of of columns in error table.
How do we prevent/workaround this?
If I have source(view) in sch A, how do we create Error table in Sch B for source(view)?
Is it feasible?
I brought the error table details in mapping. Configured the data rules/error tables.
If I picked up 'MOVE TO ERROR' option, I am getting "VLD-2802 Missing delete matching criteria in table. the condition is needed because the operator contain at least one data rule with a MOVE TO ERROR action"
On condition Loading - I have 'All constraints' for matching criteria.
I changed to "no constraints' still I get the above error.
If I change to 'REPORT' option instead of 'MOVE TO ERROR' option, error goes off.
Any idea?
Thanks in advance.
RI

3.2 to 4.1 Upgrade - Error Handling for Unavailable Database Links

Hi,
I'm having a 3.2 -> 4.1 upgrade issue related to error handling for failed database links.
I have a conditional Exists button on a page that has a SQL query to linked tables. However, for the 10 minutes every day where the target of the database link is getting a cold backup, the query fails. In the old 3.2 apex I simply got an error inside the region where the button is located but otherwise the page was still visible:
"Invalid exists/not exists condition: ORA-02068: following severe error from MYDBLINK ORA-01034: ORACLE not available ORA-27101: shared memory realm does not exist"
However, in apex 4.1.0.00.32 I get the following unhandled error, and clicking "OK" takes me to the edit page when logged in as developer.
i.e., the page can't be run at all while the database links are failing in this one region.
Error Error processing condition.
ORA-12518: TNS:listener could not hand off client connection
Technical Info (only visible for developers):
is_internal_error: true
apex_error_code: APEX.CONDITION.UNHANDLED_ERROR
ora_sqlcode: -12518
ora_sqlerrm: ORA-12518: TNS:listener could not hand off client connection
component.type: APEX_APPLICATION_PAGE_REGIONS
component.id: 4
component.name: Current Alerts
error_backtrace:
ORA-06512: at "SYS.WWV_DBMS_SQL", line 1041
ORA-06512: at "APEX_040100.WWV_FLOW_DYNAMIC_EXEC", line 687
ORA-06512: at "APEX_040100.WWV_FLOW_CONDITIONS", line 272
General users see this:
Error Error processing condition.
ORA-01034: ORACLE not available ORA-02063: preceding line from MYDBLINK
clicking "OK" takes user to another page, not sure how apex decides which, but not a concern at the moment.
I've done a search and read the page http://www.inside-oracle-apex.com/apex-4-1-error-handling-improvements-part-1/ but the new apex error handling isn't clear to me, and I don't know if the apex_error_handling_example provided on that page would be applicable to this situation.

Thanks Patrick.
The PL/SQL Function Body returning boolean condition with:
begin
    for l_check in (
      SELECT 1
       FROM myview@MYDBLINK
      WHERE ... ) loop
        return true;
    end loop;
    return false;
exception when others then
    sys.htp.p('Invalid exists/not exists condition: ' || sys.htf.escape_sc(sqlerrm));
    return false;
end; Resulted in a similar issue:
Error Error processing condition.
ORA-04052: error occurred when looking up remote object MYLINKUSER.myview@MYDBLINK
ORA-00604: error occurred at recursive SQL level 3
ORA-01033: ORACLE initialization or shutdown in progress
ORA-02063: preceding line from MYDBLINK
Technical Info (only visible for developers)
is_internal_error: true
apex_error_code: APEX.CONDITION.UNHANDLED_ERROR
ora_sqlcode: -4052
ora_sqlerrm: ORA-04052: error occurred when looking up remote object MYLINKUSER.myview@MYDBLINK
ORA-00604: error occurred at recursive SQL level 3
ORA-01033: ORACLE initialization or shutdown in progress
ORA-02063: preceding line from MYDBLINK
component.type: APEX_APPLICATION_PAGE_REGIONS
component.id: 4
component.name: Current Alerts
error_backtrace:
ORA-06512: at "SYS.WWV_DBMS_SQL", line 904
ORA-06512: at "APEX_040100.WWV_FLOW_DYNAMIC_EXEC", line 588
ORA-06512: at "APEX_040100.WWV_FLOW_CONDITIONS", line 148However, I created a view with the same query:
CREATE OR REPLACE VIEW v_localview (ALERT_1)
AS
SELECT 1
FROM myview@MYDBLINK ...then change the condition to look at the local view:
begin
    for l_check in (
      select alert_1 from v_localview ) loop
        return true;
    end loop;
    return false;
exception when others then
    sys.htp.p('Invalid exists/not exists condition: ' || sys.htf.escape_sc(sqlerrm));
    return false;
end;As a view is simply a query I'm surprised this should make any difference but it now looks similar to the 3.2 error, inside the region, when the linked database gets its morning cold backup, and this is fine:
Invalid exists/not exists condition: ORA-12518: TNS:listener could not hand off client connection

Error handling for importing a file

Hi, I have only been doing java for 1 semester, and have got terribly stuck on my final assg. I have to import a txt file, and catch any exceptions. I know I am not using the correct method to read the file, but am not sure what the alternatives are. I am getting a compile time..illegal character msg for my Mydata.txt file. Here is my code.
PS I do have a CatalogueItem class and a bit more to the main class, I have not attached it as I do not want this to be too long.
/The program reads 10 sets of catalogue data from the Mydata.txt file
//it prompts the user to use one of the 5 menu options displayed on the screen
//depending on which option is selected the program displays the data
//back on the screen.
import java.awt.*;
import java.lang.*;
import java .io.*;
import java.util.StringTokenizer;
import java.text.NumberFormat;
import java.util.Locale;
//set up a class to call on the constructors from the catalogueitem class
public class Myassg5
     private static final int MAX = 10; //sets the length to 10(for most exp products)
     private static CatalogueItem[] prodlist; //sets array for product list
     NumberFormat cash = NumberFormat.getCurrencyInstance(new Locale("en","AU"));
     public static void main(String[] args) throws IOException
     CatalogueItem prodlist = new CatalogueItem[10];//sets the length to 10
     {//create Buffered FileStream and initialise to zero
     //use bufferedReader to read in data my Mydata.txt file.
     BufferedReader inFile = null;
     BufferedReader inFile = new BufferedReader(new FileReader(C:\Mydata.txt);
     //print a msg stating the file is loading
     System.out.println("Loading file data from Mydata.txt...10 item(s) OK");
     //initialise the array elments to zero
     for( int a = 0; a < prodlist.length; a++)
     prodlist[a] = 0;
     //if incorrect command lines were passed in display
     //usage msg and quit program
     if(prodlist.length != 1)
          System.out.println("Usage: java assg <Mydata.txt>");
          System.exit(0);
     try
          inFile = new BufferedReader(new FileReader(args[0]));
     //display the error and quit if the file is not found
     catch(FileNotFoundException e)
          System.err.println("File not found--program will terminate");
          System.exit(1);
     //display error msg and quit if there is a problem
     //when opening the file
     catch(IOException e)
          System.err.println("Error opening file--program will terminate")
          System.exit(1);
     //repeat this error handling process as often as neccessary
     boolean go = true;
     while (go)
     //get a line of data from the file
     boolean valid = false;
     CatalogueItem prodlist =-1;
     while(!valid)
     //read the line of text from the file
     String temp = null;
     try
          temp = inFile.readLine();
     //display error msg and quit if there is a problem
     //reading from the file
     catch (IOException e)
          System.err.println("error reading from the file--program will terminate");
     System.exit(1);
     //if the string is null the EOF has been reached
     if(temp ==null)
          valid = true;
          go = false;
     //close the file stream
     try
          inFile.close();
     //display error if there was a problem closing the file
     catch (IOException e)
          System.err.println("error closing data file")


I think the problem is the "\M" in "C:\Mydata.txt". It is trying to make that into an escape character. Use "C:\\Mydata.txt" or "C:/Mydata.txt" instead.
The logic here is odd. You open a BufferedReader for Mydata.txt, then you trash it without closing it and create another BufferedReader for whatever command line argument the user passes in. Which reader do you want to keep?

Error Handling for Background/Update Tasks (Transfer Order creation) - How?

Hi,
I have a standard process for creating a Transfer Order and 2 user-exits that I have implemented.
The user exits are used to transfer information during Transfer Order creation.
However, the user-exits also check data in table TVARV and other. As such, error handling needs to be implemented, since the T.O. might or might not go through, depending on data validation and related.
However, the user-exits are implemented during creation, which is an update task that runs in the background. This makes it impossible to output any information or error messages.
What else can be done in regards to outputting a message, since the user will need to see some sort of message that the process failed, that the T.O. didnu2019t confirm? Can an SAP inbox message be created and how?
Please help.
Thank You,
John

Hi,
Please check the following link for all the function modules and user exits on TOs.
http://help.sap.com/saphelp_erp2005/helpdata/EN/c6/f83a294afa11d182b90000e829fbfe/content.htm
Reward points if it was helpful.
Regards
Abhishek
Edited by: Abhishek Raj on May 29, 2008 10:20 AM

Error handler for event based messaging framework

I've been very interested in using the event based messaging framework (described here http://forums.ni.com/t5/LabVIEW/Community-Nugget-2009-03-13-An-Event-based-messageing-framework/td-p...) for my next large application.
My main concern is the fact that it seems like typos would be very difficult to debug since you need to ignore unknown commands to make this system work.
To solve this problem I've been considering the idea of having a single message error handler VI which will store all valid commands and check all sent commands to see if they are valid. Each VI would send out a register message on startup with their name and all messages they can send and receive. The message error handler would store these and then check all future messages to be sure it is a valid message, throwing an error if it is not.
My basic problem is this: for this to work the message error handler VI would have to be started before any messages are sent so that it can capture all the register events. If this is a VI that will be continuously running the entire application how can I ensure it starts first since I cannot wait for it to complete? (I.e. the usual method of running an error out wire or using a sequence structure will not work since everything will then wait for it to complete which will not happen until the program is ready to shut down)
I'm assuming the answer might be to use an asynchronous call but I'm not very familiar with this method.
Any help is appreciated. Thanks.

Could you just use the error handler as a subVI inside a case structure that is only called when you have new message to be checked? I'm not sure I understood the exact functionality you are looking for, so sorry if this does not apply.
Zach P.
Product Support Engineer | LabVIEW R&D | National Instruments

Error Handling for DSO

Hi all,
Is it not possible to give error handling options for DSO in Delta loads?
I have created a delta infopackage to load data from Order Line Item (2LIS_11_VAITM) into a DSO.
But the error handling gives only option 'No Update ,No reporting'.
I want to give the option 'Valid Records update, reporting possible (request green)' option.
Please let me know whether any setting needs to be done to make this option available.
Thanks in advance.
Meera

Check this help - self explanatory - trying checking F1 thats very informative and self explantory most of the times
Switched off
If an error occurs, the error is reported as a package error in the DTP monitor. The error is not assigned to the data record. The cross-reference tables for determining the data record numbers are not built; this results in faster processing.
The incorrect records are not written to the error stack since the request is terminated and has to be updated again in its entirety.
No update, no reporting (default)
If errors occur, the system terminates the update of the entire data package. The request is not released for reporting. The incorrect record is highlighted so that the error can be assigned to the data record.
The incorrect records are not written to the error stack since the request is terminated and has to be updated again in its entirety.
Update valid records, no reporting (request red)
This option allows you to update valid data. This data is only released for reporting after the administrator checks the incorrect records that are not updated and manually releases the request (by a QM action, that is, setting the overall status on the Status tab page in the monitor).
The incorrect records are written to a separate error stack in which the records are edited and can be updated manually using an error DTP.
Update valid records, reporting possible
Valid records can be reported immediately. Automatic follow-up actions, such as adjusting the aggregates, are also carried out.
The incorrect records are written to a separate error stack in which the records are edited and can be updated manually using an error DTP.

Error handling for distributed cache synchronization

Hello,
Can somebody explain to me how the error handling works for the distributed cache synchronization ?
Say I have four nodes of a weblogic cluster and 4 different sessions on each one of those nodes.
On Node A an update happens on object B. This update is going to be propogated to all the other nodes B, C, D. But for some reason the connection between node A and node B is lost.
In the following xml
<cache-synchronization-manager>
<clustering-service>...</clustering-service>
<should-remove-connection-on-error>true</should-remove-connection-on-error>
If I set this to true does this mean that the Toplink will stop sending updates from node A to node B ? I presume all of this is transparent. In order to handle any errors I do not have to write any code to capture this kind of error .
Is that correct ?
Aswin.

This "should-remove-connection-on-error" option mainly applies to RMI or RMI_IIOP cache synchronization. If you use JMS for cache synchronization, then connectivity and error handling is provided by the JMS service.
For RMI, when this is set to true (which is the default) if a communication exception occurs in sending the cache synchronization to a server, that server will be removed and no longer synchronized with. The assumption is that the server has gone down, and when it comes back up it will rejoin the cluster and reconnect to this server and resume synchronization. Since it will have an empty cache when it starts back up, it will not have missed anything.
You do not have to perform any error handling, however if you wish to handle cache synchronization errors you can use a TopLink Session ExceptionHandler. Any cache synchronization errors will be sent to the session's exception handler and allow it to handle the error or be notified of the error. Any errors will also be logged to the TopLink session's log.

Error handling for master data with direct update

Hi guys,
For master data with flexible update, error handling can be defined in InfoPackege, and if the load is performed via PSA there are several options - clear so far. But what about direct update...
But my specific question is: If an erroneous record (e.g invalid characters) occur in a master data load using direct update, this will set the request to red. But what does this mean in terms of what happens to the other records of the request (which are correct) are they written to the master data tables, so that they can be present once the masterdata is activated, or are nothing written to masterdata tables if a single record is erroneous???
Many thanks,
/ Christian

Hi Christian -
Difference between flexible upload & Direct upload is that direct upload does not have Update Rules, direct upload will have PSA as usual & you can do testing in PSA.
second part when you load master data - if error occurs all the records for that request no will be status error so activation will not have any impact on it i.e. no new records from failed load will be available.
hope it helps
regards
Vikash

Error handling for input validations

Similar Messages

Maybe you are looking for