Enterprise Notification System

• US 20080250115A1
• Filed: 04/22/2007
• Published: 10/09/2008
• Est. Priority Date: 04/04/2007
• Status: Abandoned Application

• Current Assignee: SEAL Infotech Private Limited
• Original Assignee: SEAL Infotech Private Limited
• Inventors: Iyer, Vaidy
• Application Number:
  US11/738,508
• Publication Number:
  US 20080250115A1
• Time in Patent Office: Days
• US Class Current: 709/207
• CPC Class Codes: G06Q 10/10 Office automation; Time management

Abstract

A system for notifying an end-user of the occurrence of an event is disclosed. The inventive concept comprises a front-end system that is accessible by the end-user, and a back-end system that is remotely accessible through the front-end system. The front-end system contains one or more mini-applications associated with various back-end applications. Each mini-application employs an information gathering procedure which is used to discover the occurrence of a remote event in an associated back-end application. When an event occurs, the mini-application notifies the end-user of its occurrence and, upon the end-user'"'"'s request, directs the end-user to a separate application accessible to the front-end system, which is used handle the event.

Claims

1. A computer implemented method of notifying the end-user of a front-end system of a remote event, the method comprising:

acquiring input from the end-user;

sending a request from a front-end system to a back-end system;

sending a response from the back-end system to the front-end system;

displaying a pop-up notification on the front-end system; and

handling the pop-up notification by calling another process on the front-end system from which the end-user may access the back-end system application.

2. The method as recited in claim 1 further comprising:

storing back-end authentication information on the front-end system; and

authenticating the front-end system with the back-end system.

3. The method as recited in claim 2 further comprising:

parsing the response; and

determining whether any data in the response is new.

4. The method as recited in claim 3 further comprising:

converting, by the back-end system, the received data from its original format to a format in which a function on the backend system may be executed; and

converting the resultant data to a format which may be utilized by the front-end system.

5. A method of notifying an end-user of a front-end system of an event occurring on a back-end system, the method comprising:

gathering input from the end-user of a front-end system;

setting connection settings and business rules based on the input acquired from the end-user;

sending a web service request from the front-end system to a back-end system;

sending a web service response from the back-end system to the front-end system; and

displaying a pop-up notification to the end-user using the web service response.

6. The method as recited in claim 5, wherein the back-end system is an SAP application.

7. The method as recited in claim 5 further comprising:

mapping the web service request to virtual interface parameters;

converting the virtual interface parameters to a function module format; and

calling the function module.

8. The method as recited in claim 5 further comprising:

acquiring input from the end-user in the pop-up notification; and

transmitting the input to the SAP application.

9. The method of claim 8, wherein the transmitting is performed without the end-user manually logging into the SAP application.

10. A system for notifying an end-user of a business event, the system comprising:

a front-end system directly accessible by an end-user, the front-end system running a mini-application; and

a back-end system remotely accessible by an end-user through the front-end system, the back-end system associated with the mini-application,

wherein the mini-application employs a notification procedure wherein the back-end system can notify the end-user of an event which has occurred,

wherein the mini application allows the end-user to respond to the event directly inside the mini-application.

11. The system as recited in claim 10, wherein the back-end system runs an SAP application.

12. The system as recited in claim 11 wherein the back-end system runs an SAP application comprising one of:

Customer Relationship Management, Enterprise Resource Planning, Supply Chain Management, Strategic Enterprise Management, Manufacturing Integration and Intelligence, Supplier Relationship Management, Business Intelligence, Exchange Infrastructure, Master Data Management, Product Lifecycle Management, Enterprise Portals, and electronic mail applications.

13. The system as recited in claim 10, wherein the mini-application implements a gathering operation to gather information from the back-end system, the gathering operation comprising sending a SOAP request from the front-end system to the back-end system and receiving a SOAP response from the back-end system,

wherein a request-handling procedure comprises parsing the SOAP request, associating the SOAP request'"'"'s parameters with virtual interface parameters, converting the parameters from web service to a function module format, calling a function module, gathering the information requested, and creating a SOAP response.

14. The system as recited in claim 10, wherein the notification procedure comprises displaying a pop-up message on the front-end system'"'"'s display.

15. The system as recited in claim 14, wherein an event-handling procedure performed on the mini-application comprises running a separate local process corresponding to the mini-application'"'"'s associated back-end application on the front-end system when the user clicks on or otherwise interacts with a the pop-up message.

16. The system as recited in claim 15, wherein the separate local process is an SAP application.

17. The system as recited in claim 14 wherein the notification procedure comprises an event-handling procedure which acquires input from the user and uses it to update the back-end application.

18. The system as recited in claim 10 wherein the mini-application comprises a Google gadget running under the Google desktop.

19. The system as recited in claim 10 wherein the mini-application comprises a Yahoo! widget.

20. The system as recited in claim 10 wherein the mini-application comprises a Microsoft Vista gadget.

21. The system as recited in claim 10 wherein the mini-application further comprises an options menu wherein the end-user may specify connection settings and business rules.

22. The system as recited in claim 10 wherein the mini-application further comprises an authentication procedure for validating a user'"'"'s identity.

23. The system as recited in claim 10 wherein,

the mini-application comprises a Google gadget running under the Google desktop;

the back-end system runs at least one SAP applications;

the mini-application performs an information gathering procedure that comprises sending a web service request from a front-end system to a back-end system and receiving a web service response from the back-end system;

the mini-application performs a request-handling procedure that comprises parsing the web service request, associating the web service request'"'"'s parameters with virtual interface parameters, converting the parameters from web service to a function module format, calling a function module, gathering the information requested, and creating a web service response;

the notification procedure comprises displaying a pop-up message on the front-end system'"'"'s display;

the mini-applications performs an event-handling procedure that comprises running a separate local process corresponding to the mini-application'"'"'s associated back-end application on the front-end system when the end-user clicks on or otherwise interacts with a the pop-up message.