IN-LANE EXCEPTION HANDLING

• US 20110126151A1
• Filed: 11/24/2009
• Published: 05/26/2011
• Est. Priority Date: 11/24/2009
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Colvard, Jeffrey Thomas, Ramaiah, Taruna, Bean, Erik, Cohen, Brian
• Granted Patent: US 9,274,871 B2
• Time in Patent Office: Days
• US Class Current: 715/810
• CPC Class Codes: G06F 11/0769 Readable error formats, e.g. cross-platform generic formats, human understandable formats
• CPC Class Codes: G06F 11/0787 Storage of error reports, e.g. persistent data storage, storage using memory protection
• CPC Class Codes: G06F 11/36 Preventing errors by testing or debugging software
• CPC Class Codes: G06F 16/284 Relational databases
• CPC Class Codes: G06F 3/04842 Selection of displayed objects or displayed text elements G06F3/0482 takes precedence
• CPC Class Codes: G06F 3/04847 Interaction techniques to control parameter settings, e.g. interaction with sliders or dials
• CPC Class Codes: G06F 40/18 of spreadsheets form-filling G06F40/174

Abstract

This disclosure describes, generally, methods and systems for implementing in-lane exception handling. The method includes displaying, on a user terminal display device, a first user interface (UI) configured to display application data in organized rows and columns, receiving, by a data management system, updates and/or edits to the application data, and calculating, by the data management system, the updated and/or edited application data. The method further includes analyzing, by the data management system, the updates and/or edits to determine one or more of associated errors, warnings, and exceptions, and displaying, within the first UI, a graphical representation for each of the errors, warnings, and exceptions in the row and/or column of the application data where the error, warning, or exception has occurred.

Claims

1. A method of implementing in-lane exception handling, the method comprising:

displaying, on a user terminal display device, a first user interface (UI) configured to display application data in organized rows and columns;

receiving, by a data management system, updates and/or edits to the application data;

calculating, by the data management system, the updated and/or edited application data;

analyzing, by the data management system, the updates and/or edits to determine one or more of associated errors, warnings, and exceptions; and

displaying, within the first UI, a graphical representation for each of the errors, warnings, and exceptions in the row and/or column of the application data where the error, warning, or exception has occurred.

2. A method of implementing in-lane exception handling as in claim 1, further comprising receiving a selection of at least one or the rows and/or columns including an error, warning, or exception.

3. A method of implementing in-lane exception handling as in claim 2, further comprising in response to the selection, displaying a second UI including an entries listing of each of the errors, warnings, or exceptions contained in each or the rows and/or columns of the first UI.

4. A method of implementing in-lane exception handling as in claim 3, wherein upon displaying of the second UI, a cursor is automatically placed over the error, warning, or exception associated with the selected row and/or column.

5. A method of implementing in-lane exception handling as in claim 3, further comprising providing expansion icons for each of the entries.

6. A method of implementing in-lane exception handling as in claim 5, further comprising:

receiving a selection of at least one of the expansion icons; and

in response to receiving the selection of at least one of the expansion icons, displaying information about the error, warning, or exception.

7. A method of implementing in-lane exception handling as in claim 6, wherein the information comprises one or more of the following:

details of the error, warning, or exception, causes of the error, warning, or exception, and actions to remedy the error, warning, or exception.

8. A method of implementing in-lane exception handling as in claim 1, further comprising receiving a change or edit to the application data.

9. A method of implementing in-lane exception handling as in claim 8, further comprising receiving a selection of a refresh/update interface icon.

10. A method of implementing in-lane exception handling as in claim 9, further comprising in response to receiving the selection, removing the graphical representation for remedied rows and/or columns.

11. A method of implementing in-lane exception handling as in claim 10, wherein the removal or displaying of the graphical representations is dynamically performed in real-time.

12. A method of implementing in-lane exception handling as in claim 1, wherein the errors, warnings, and exceptions comprise one or more of the following:

missing data, incomplete data, inaccurate data, and improper currency conversion.

13. A method of implementing in-lane exception handling as in claim 1, wherein the UI further includes a column for displaying a severity indication of the errors, warnings, and exceptions.

14. A system for implementing in-lane exception handling, the system comprising:

a user terminal including a display device configured to display a first user interface (UI) displaying application data in organized rows and columns; and

a data management system configured to receive updates and/or edits to the application data, calculate the updated and/or edited application data, analyze the updates and/or edits to determine one or more of associated errors, warnings, and exceptions, and

wherein the first UI is further configured to display a graphical representation for each of the errors, warnings, and exceptions in the row and/or column of the application data where the error, warning, or exception has occurred.

15. A system for implementing in-lane exception handling as in claim 14, wherein the data management system is further configured to receive a change or edit to the application data.

16. A system for implementing in-lane exception handling as in claim 15, wherein the data management system is further configured to receive a selection of a refresh/update interface icon, in response to receiving the selection, and remove the graphical representation for remedied rows and/or columns.

17. A machine-readable medium for implementing in-lane exception handling, having sets of instructions which, when executed by a machine, cause the machine to:

display, on a user terminal display device, a first user interface (UI) configured to display application data in organized rows and columns;

receive updates and/or edits to the application data;

calculate the updated and/or edited application data;

analyze the updates and/or edits to determine one or more of associated errors, warnings, and exceptions; and

display a graphical representation for each of the errors, warnings, and exceptions in the row and/or column of the application data where the error, warning, or exception has occurred.

18. A machine-readable medium for implementing in-lane exception handling as in claim 17, wherein the sets of instructions, when further executed by the machine, cause the machine to receive a selection of at least one of the rows and/or columns including an error, warning, or exception.

19. A machine-readable medium for implementing in-lane exception handling as in claim 18, wherein the sets of instructions, when further executed by the machine, cause the machine to, in response to the selection, display a second UI including entries listing of each of the errors, warnings, or exceptions contained in each of the rows and/or columns of the first UI.

20. A machine-readable medium for implementing in-lane exception handling as in claim 19, wherein the errors, warnings, and exceptions comprise one or more of the following:

missing data, incomplete data, inaccurate data, and improper currency conversion.