System and method for social service event processing and management

• US 20070220140A1
• Filed: 06/30/2006
• Published: 09/20/2007
• Est. Priority Date: 03/14/2006
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP AG (SAP SE)
• Inventors: Weidenschlager, Armin
• Granted Patent: US 8,489,729 B2
• Time in Patent Office: Days
• US Class Current: 709/224
• CPC Class Codes: H04L 41/0681 Configuration of triggering conditions
• CPC Class Codes: H04L 41/22 comprising specially adapted graphical user interfaces [GUI]

Abstract

An event processing mechanism is provided as a system interface between software applications that contain events that need to be processed, a BRF program that executes event rules, and workflow processes that capture the processing of the events. A social service eventing program enables centralized and streamlined event processing by receiving event information from software applications, assigning appropriate event rules based on the received information and applicable business or regulatory rules, prioritizing event rules, setting and communicating applicable event rules to parameterized rules to be executed by a BRF program.

Claims

1. An event processing computer system comprising a social service eventing program providing a program interface between a plurality of software applications containing events to be raised and processed, a BRF program, and a workflow process.

2. The system of claim 1, wherein the social service eventing program:

receives event data from the plurality of software applications;

sends confirmation of the receipt of the event data to the plurality of software applications;

performs rule determination to assign event subscriptions to the events raised by the plurality of software applications;

sets the assigned event subscriptions to parameterized BRF rules;

initiates the BRF program for execution of the parameterized BRF rules;

sends the BRF program the parameterized BRF rules; and

initiates workflow processes for processing of the events raised by the plurality of software applications.

3. The system of claim 2, wherein the plurality of software applications return to their existing work processes after receiving confirmation from the social service eventing program.

4. The system of claim 1, wherein the events contain information, including event type, event subscriptions, and event instance data.

5. The system of claim 4, wherein the event type contains event type hierarchy.

6. The system of claim 4, wherein the event instance data contains event attributes and event context.

7. The system of claim 2, wherein the event data received by the social service eventing program contains the event type, the event attributes, and the event context.

8. The system of claim 2, wherein the event subscriptions are rules embodied in logical conditions, of which if true, initiate actions to be processed.

9. The system of claim 2, wherein the social service eventing program performs rule determination by reading the event subscriptions available to the events based on the event data received from the plurality of software applications, deciding processing priority of the event subscriptions, and filtering event subscriptions based on the processing priority.

10. The system of claim 9, wherein the social service eventing program decides the processing priority of the event subscriptions by comparing the event subscriptions available to the events and the received event data and determining a set of event subscriptions for immediate processing and a set of event subscriptions for delayed processing.

11. The system of claim 9, wherein the social service eventing program performs rule determination based on authorization granted to a system administrator using the computer system.

12. The system of claim 11, wherein the authorization granted to the system administrator is based on an individual level.

13. The system of claim 11, wherein the authorization granted to the system administrator is based on an organizational unit level.

14. The system of claim 8, wherein the social service eventing program performs rule determination by verifying whether the events raised by the plurality of software applications belong to particular case categories.

15. The system of claim 2, wherein the parameterized BRF rule contains the case category, the processing priority, and the authorization granted to the system administrator.

16. The system of claim 1, wherein the BRF program maintains an error log that records errors occurred during the execution of the BRF rules.

17. The system of claim 1, wherein the social service eventing program checks the error log and processes errors depending on whether the errors occurred after the events were raised, and whether the errors were permanent or temporary.

18. An event processing method comprising the steps of:

receiving event data by a social service eventing program;

initiating a first workflow process to process immediate event subscriptions by the social service eventing program;

initiating a BRF program by the social service eventing program;

determining the immediate event subscriptions to be applied to the event by the social service eventing program;

setting the immediate event subscriptions to be applied to the event to parameterized BRF rules by the social service eventing program;

executing the parameterized BRF rules by the BRF program;

initiating a second workflow process to process delayed event subscriptions by the social service eventing program;

initiating the BRF program by the social service eventing program;

determining the delayed event subscriptions to be applied to the event by the social service eventing program;

setting the delayed event subscriptions to be applied to the event to parameterized BRF rules by the social service eventing program;

executing the parameterized BRF rules by the BRF program.

19. The method of claim 18, wherein the event contains information, including event type, event subscriptions, and event instance data.

20. The method of claim 19, wherein the event type contains event type hierarchy.

21. The method of claim 19, wherein the event instance data contains event attributes and event context.

22. The method of claim 18, wherein the event data received by the social service eventing program contains the event type, the event attributes, and the event context.

23. The method claim 18, wherein the immediate event subscriptions are rules embodied in logical conditions that are to be executed immediately, of which if true, initiate actions to be processed.

24. The method of claim 18, wherein the social service eventing program determines the immediate event subscriptions by reading the event subscriptions available to the event based on the event data received, comparing the event subscriptions with the event data received, and deciding processing priority to be immediate.

25. The method of claim 18, wherein the social service eventing program determines the immediate event subscriptions based on authorization granted to a system user of the program.

26. The method of claim 25, wherein the authorization granted to a system user is based on an individual level.

27. The method of claim 25, wherein the authorization granted to a system user is based on an organizational unit level.

28. The method claim 18, wherein the delayed event subscriptions are rules embodied in logical conditions that are to be executed after the execution of the immediate event subscriptions, of which if true, initiate actions to be processed.

29. The method of claim 18, wherein the social service eventing program determines the delayed event subscriptions by reading the event subscriptions available to the event based on the event data received, comparing the event subscriptions and the event data received, and deciding the processing priority to be delayed.

30. The method of claim 18, wherein the social service eventing program determines the delayed event subscriptions based on authorization granted to the system user of the program.

31. The method of claim 30, wherein the authorization granted to a system user is based on an individual level.

32. The method of claim 30, wherein the authorization granted to a system user is based on an organizational unit level.

33. The method of claim 18, wherein the social service eventing program determines whether the event belongs to a particular case category.

34. The method of claim 18, wherein the parameterized BRF rule contains the case category, the processing priority, and the authorization granted to the system administrator.

35. The method of claim 18, further comprising the step of maintaining an error log that records errors occurred during the execution of the BRF rules by the BRF program.

36. The method of claim 18, further comprising the steps of the social service eventing program:

checking the error log; and

processing an error depending on whether the error occurred after the software application raised the event, and whether the error was permanent or temporary.

37. A computer readable medium having program instructions stored thereon that, when executed, performs the steps of:

raising an event to be processed;

sending event data to a social service eventing program;

confirming the receipt of the event data;

initiating a first workflow process to process immediate event subscriptions;

initiating a BRF program;

determining the immediate event subscriptions to be applied to the event;

setting the immediate event subscriptions to be applied to the event to parameterized BRF rules;

executing the parameterized BRF rules;

initiating a second workflow process to process delayed event subscriptions;

initiating the BRF program;

determining the delayed event subscriptions to be applied to the event;

setting the delayed event subscriptions to be applied to the event to parameterized BRF rules;

executing the parameterized BRF rules.

38. The medium of claim 37, wherein the event-contains information, including event type, event subscriptions, and event instance data.

39. The medium of claim 38, wherein the event type contains event type hierarchy.

40. The medium of claim 38, wherein the event instance data contains event attributes and event context.

41. The medium of claim 37, wherein the event data sent to the social service eventing program contains the event type, the event attributes, and the event context.

42. The medium claim 37, wherein the immediate event subscriptions are rules embodied in logical conditions that are to be executed immediately, of which if true, initiate actions to be processed.

43. The medium of claim 37, wherein the social service eventing program determines the immediate event subscriptions by reading the event subscriptions available to the event based on the event data received, and comparing the event subscriptions and the event data received, and deciding processing priority to be immediate.

44. The medium of claim 37, wherein the social service eventing program determines the immediate event subscriptions based on authorization granted to a system user of the program.

45. The medium of claim 44, wherein the authorization granted to the system user is based on an individual level.

46. The medium of claim 44, wherein the authorization granted to the system user is based on an organizational unit level.

47. The medium of claim 37, wherein the social service eventing program determines the delayed event subscriptions by reading the event subscriptions available to the event based on the event data received, comparing the event subscriptions and the event data received, and deciding the processing priority to be delayed.

48. The medium of claim 37, wherein the social service eventing program determines the delayed event subscriptions based on authorization granted to the system user of the program.

49. The medium of claim 48, wherein the authorization granted to the system user is based on an individual level.

50. The medium of claim 48, wherein the authorization granted to the system user is based on an organizational unit level.

51. The medium of claim 37, wherein the social service eventing program determines whether the event belongs to a particular case category.

52. The medium of claim 37, wherein the parameterized BRF rule contains the case category, the processing priority, and the authorization granted to the system administrator.

53. The medium of claim 37, further performs the step of maintaining an error log that records errors occurred during the execution of the BRF rules.

54. The medium of claim 37, further performs the steps of the social service eventing program:

checking the error log; and

processing an error depending on whether the error occurred after the software application raised the event, and whether the error was permanent or temporary.