JP2019503015A - System and method for event management in an enterprise resource planning system - Google Patents

Abstract

The systems and methods described herein monitor transactions that occur in large and complex enterprise software systems for simple or complex events that meet certain specified rules. When an event that succeeds in meeting the criteria set in each rule occurs, a prior notification is sent to the designated user. Thereby, early detection of a suspicious transaction and real-time quick response are possible.

Description

CROSS-REFERENCE TO RELATED APPLICATIONS This application is incorporated in its entirety herein by reference, claims priority to, filed January 25, 2016 U.S. Provisional Application No. 62 / 286,809.

  The present disclosure relates generally to systems and methods for managing enterprise information on distributed computer systems, and more particularly to identifying specific rules that meet certain defined rules in one or more ERP (enterprise resource planning) systems. The present invention relates to a system and method for monitoring the occurrence of various events and providing appropriate notifications.

  ERP systems often include software solutions that integrate information and processes within and across various areas of an organization. In this way, the information of the entire company can be viewed, and the entire company can be determined and executed. ERP systems are associated with large amounts of data. In an ERP system, information from users, customers, administrators, and other stakeholders is continuously generated, collected, and processed. It can be overwhelming to keep track of all of the various elements in an organization and their associated data. User and system problems can be audited by querying information from the database and viewing the query report in the digital dashboard or by displaying the query results, or to detect deviations from standard performance Is analyzed by running However, these processes can lead to delayed analysis of incidents and lost training opportunities, and if the incidents are a threat to the infrastructure or system, these delays can be a significant financial and HR damage.

  Disclosed herein are systems and methods that address the shortcomings of the art, which improve productivity, reduce threat detection and processing delays, and real-time workload changes. A number of additional benefits, such as dynamically scaling the system to deal with, pre-alert based on response time declining trends, providing real-time training, and gaining a competitive advantage Can be provided. The systems and methods described herein provide for notification of events that occur in an ERP system and meet certain user-defined rules.

  Certain embodiments include a method for detecting an event in an enterprise resource planning system. The method includes receiving, by a server, a plurality of criteria defining a rule stored as a first plurality of records in an event management database from an authorized device of an enterprise resource planning system, the method comprising: Criteria selected by the user through the graphical user interface of the rule configuration graphical user interface that presents transactions, batches, and access as rule type options, and names, operators, and values as multiple criteria And receiving by the server a plurality of information relating to a first plurality of events occurring at a plurality of user devices in the enterprise resource planning system. Further, the method includes identifying the second plurality of events by comparing the plurality of information associated with the first plurality of events and all of the plurality of criteria associated with the rule. Filtering a plurality of events by a server, wherein one or more of the plurality of pieces of information related to the second plurality of events satisfy all of the plurality of criteria related to the rule; Retrieving a second plurality of records defining a notification profile associated with the rule from the event management database in response to identifying the event, wherein the notification profile is one or more related to the notification format. And including one or more designated recipient devices. Finally, the method includes generating, by the server, one or more of a plurality of pieces of information related to the second plurality of events based on the notification profile to generate one or more notifications; Transmitting one or more notifications to one or more designated recipient devices and presenting a first notification of the one or more notifications via a graphical user interface comprising: A notification includes date and time, rules, and event details for each event of the second plurality of events, and selecting the event details presents an event details graphical user interface.

  Certain embodiments include a system for detecting events in an enterprise resource planning system. The system includes an event management database and a processor communicatively coupled to the event management database. The processor is operable to receive a plurality of criteria defining rules stored as a first plurality of records in an event management database from an authorized device of the enterprise resource planning system, wherein the plurality of criteria are , Transaction, batch, and access are each selected by the user through the graphical user interface of the rule configuration graphical user interface that presents each as a rule type option and presents the name, operator, and value as multiple criteria An operation and an operation of receiving a plurality of information related to a first plurality of events occurring at a plurality of user devices in the enterprise resource planning system may be configured. The processor includes a first plurality of events to identify a second plurality of events by comparing the plurality of information associated with the first plurality of events and all of the plurality of criteria associated with the rule. And a second plurality of events identified by one or more of the plurality of pieces of information related to the second plurality of events satisfying all of the plurality of criteria related to the rule In response to performing an operation to retrieve a second plurality of records defining a notification profile associated with the rule from the event management database, wherein the notification profile includes one or more preferences and one for the notification format. The above-described operation including the designated recipient device may be further configured. Finally, the processor formats one or more of the plurality of information associated with the second plurality of events based on the notification profile to generate one or more notifications and one or more An operation of sending a notification to one or more designated recipient devices and presenting a first notification of the one or more notifications via a graphical user interface, wherein the first notification is a first notification The event details graphical user interface may be configured to perform an action that includes date and time, rules, and event details for each of the plurality of events, and selecting the event details.

  Numerous other aspects, features and advantages of the present disclosure will become apparent from the following detailed description when taken in conjunction with the drawings. The system can include fewer components, more components, or different components depending on the desired analytical goal. It is also to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory and are provided to provide further explanation of the claimed invention.

  The present disclosure can be better understood with reference to the following drawings. The components in the drawings are not necessarily drawn to scale. Instead, emphasis is placed on explaining the principles of the present disclosure. In the drawings, reference numerals indicate corresponding parts throughout the different views.

1 is a block diagram illustrating a system that includes an event management engine in an ERP system, according to one embodiment. FIG. FIG. 6 is a flowchart illustrating an exemplary process for the flow of information through a module of an event management system for receiving an event and sending a notification. 2 is a flowchart illustrating an exemplary process for creating rules using an event management system, according to one embodiment. 6 is a flowchart illustrating an exemplary process for updating rules, according to one embodiment. 6 is an illustrative user interface for managing rules, according to an example embodiment. 7 is an illustrative user interface for deleting an existing rule, according to an exemplary embodiment. 7 is an illustrative user interface presented to a user to create a new rule, according to an exemplary embodiment. 7 is an illustrative user interface of a notification inbox, according to an exemplary embodiment. 6 is an illustrative user interface showing details of an event with a triggered notification, according to an exemplary embodiment. FIG. 6 is an illustrative class diagram showing a high-level diagram of various software modules / packages that collectively perform event management functions, according to an example embodiment. Figure 7 is a continuous flowchart illustrating an event management process according to an exemplary embodiment. Figure 7 is a continuous flowchart illustrating an event management process according to an exemplary embodiment.

  Reference will now be made to the exemplary embodiments illustrated in the drawings, and specific language will be used herein to describe the same. It should be understood, however, that it is not intended to limit the scope of the invention. Variations and further modifications of the features of the invention shown herein, as well as further applications of the principles of the invention shown herein, as would occur to one of ordinary skill in the relevant art to obtain this disclosure, Should be considered within the scope of the embodiments.

  As used herein, the following terms may have the following definitions:

  An “event” refers to the occurrence of a transaction that meets certain criteria. A simple event is a one-time occurrence that meets certain criteria. Examples of simple events include a user named Chris successfully logging in to the system, an employee trying to register a profit from his seat, an employee trying to log in to Best Buy on a computer, Alternatively, a security employee may receive a security error while a general clerk of a general ledger department is attempting to view data in the human resources department, but is not limited thereto.

  A composite event includes multiple occurrences of a simple event, and in certain embodiments, a complex event can include time-box and index functionality.

  “Time boxing” as used herein refers to the addition of a time reference to trigger a notification based on a complex event. Timebox settings allow the user to create rules for notifications after multiple occurrences of simple events. Examples include 5 or more transactions in the accounts payable system within 1 minute, response times greater than 2 seconds, 5 or more unsuccessful login attempts from Eastern Europe within 5 minutes, and personnel Two batch jobs in a set of queues may enter, but are not limited to, “requires recovery” status within the last hour.

  “Indexing” further expands the time box settings by allowing these time box events to be grouped by additional criteria. As an example, an individual user of the accounts payable system will generate the same error 5 times within 5 minutes in the invoice application, or a clerk in the human resources department will view the master records of more than 10 employees within 1 hour However, it is not limited to these.

  "Event management engine" refers to one or more software modules that process data using appropriate logic, execute rules, and perform data matching, and monitor all of the ERP system for simple or complex events Including, but not limited to, software that provides prior notice to designated or authorized parties.

  Certain embodiments include an initial discovery of events that are spread within the ERP system. The event management system consists of an event management engine that provides a rule composer module for defining rules and a notification module that sends alerts via browser, app, email, or text message.

  Certain embodiments include a method for detecting an event in an enterprise resource planning system. The method includes receiving, from the authorized device of the enterprise resource planning system, a plurality of criteria defining rules stored as a first plurality of records in an event management database by an event management engine; Receiving a plurality of information related to a first plurality of events occurring at a plurality of user devices in a planning system, a plurality of information related to the first plurality of events, and a plurality of criteria related to the rule Filtering the first plurality of events to identify the second plurality of events by comparing with all of the one of the plurality of information related to the second plurality of events This is in response to identifying a step that satisfies all of the criteria associated with the rule and a second plurality of events. Retrieving a second plurality of records defining a notification profile associated with the rule from the event management database, wherein the notification profile is one or more preferences for the notification format, one or more specified. A recipient device and a notification schedule, and formatting one or more of a plurality of information related to the second plurality of events to generate one or more notifications based on the notification profile And transmitting one or more notifications to the user interface of the one or more designated recipient devices via the electronic communication network according to the notification schedule. This notification may be a text message. This notification may be an electronic mail.

  Certain embodiments include a system for detecting events in an enterprise resource planning system. The system stores an event management database, one or more processors communicatively coupled to the event management database, and a computer program that is arranged to communicate with the one or more processors and includes a set of instructions. And non-transitory computer readable media. These instructions, when executed by one or more processors, store a plurality of criteria defining rules stored as a first plurality of records in an event management database from an authorized device of the enterprise resource planning system. For receiving a plurality of information related to a first plurality of events occurring at a plurality of user devices in an enterprise resource planning system, and for the first plurality of events Filtering the first plurality of events to identify the second plurality of events by comparing the plurality of information with all of the plurality of criteria associated with the rule, the second plurality of events comprising: An operation in which one or more of the plurality of information related to the event satisfy all of the plurality of criteria related to the rule; Retrieving a second plurality of records defining a notification profile associated with a rule from an event management database in response to identifying a number of events, wherein the notification profile includes one or more of the notification formats Format one or more of the plurality of information related to the second plurality of events based on preferences, one or more designated recipient devices, an action including a notification schedule, and a notification profile One or more operations of generating one or more notifications and transmitting one or more notifications to a user interface of one or more designated recipient devices via an electronic communication network according to a notification schedule. Let the processor execute it.

  The event management system allows companies to detect fraud, reduce risk, improve compliance, and improve human productivity by managing events in the ERP system in advance. Businesses cannot tolerate the consequences of data breaches, lost revenue, or simply inefficient processes. The event management system's proactive notification and on-demand reporting capabilities enable decision makers to identify and respond in real time to events that are determined to be critical to the success of a particular team, department, or organization. it can. The event management system can function as part of a comprehensive fraud detection program. This is because authorized users can create alerts for simple or complex events, monitor user access and errors, and be notified when simple or complex events occur, resulting in threats according to defined criteria. This is because it can be identified and separated. Authorized users can use the event management system's rule-based pattern recognition capabilities to quickly identify, track, and investigate potentially harmful events, minimizing both threats and response times Alerts to decision makers. The event management system can also be designed to alert the system administrator when an employee continuously issues a certain number of login errors within a specified time. The event management system may further be used to trigger additional infrastructure that is prepared to improve the user experience or alert the administrator about performance degradation.

  The event management system provides full flexibility in creating notifications about events that occur in the ERP system. Using the event management system, authorized users or teams can receive real-time alerts and dedicated displays for selected devices. Designated or authorized individuals / teams can create and customize simple or complex rules and alerts in the event management system according to their needs. These alerts and notifications can be customized in a report-like format for designated individuals within the company. The event management system can provide more specific alerts to specific designated or authorized individuals or teams, including appropriate ERP data that enables immediate response.

  The event management system can be configured to deliver real-time, on-demand and self-explanatory notifications. These notifications allow performance problems in the system or for individuals to be recognized and confirmed with real-time data, minimizing response time and potential data loss. The event management system can be configured to optimize workflows and batch jobs with alerts for failed or delayed computing. Another benefit of real-time notifications using an event management system is to maximize training opportunities based on customizable human interaction with the system, and therefore, on the verge of problem occurrence, problematic users Can be identified and corrective action can be taken. Significant trends that can impede process execution and efficiency, such as a large number of wrong orders from a particular client, can be addressed with minimal time loss and effort.

  The event management system is configured to apply rules to data between other organizational systems communicatively coupled to the ERP system, including but not limited to a supply chain management system or customer relationship management. Can do. In certain embodiments, the event management system can be deployed as part of enterprise application integration middleware. Designated or authorized individuals or teams can define and enforce relevant corporate rules and standards for identifying events or notifying users, which apply to data values across all information systems. obtain. The event management system can be applied to raw or cleansing data or enriched data from within the ERP system and across all information systems.

  FIG. 1 is a block diagram illustrating a system including an event management engine in an ERP system, according to one embodiment. The steps involved in the above method may be performed by one or more computing devices, such as the system described at 100, for example. Each of the various components of event management system 100 is implemented in any type of computer-based architecture including a suitable processor control device configured to receive, process, and / or transmit digital data configured as described above. May be. Examples of devices incorporating one or more suitable processor control devices include smartphones, desktop computers, laptop computers, servers, tablets, PDAs, and dedicated computers that perform enterprise data processing, rule matching, and notification algorithms, etc. Singing platform.

  In certain embodiments, computing device users 1, 2, and 3 shown as user station A101, user station B102, and user station C103 perform one or more transactions in the organization's ERP system; It interacts with the event management engine 105 via the network 104. One or more user stations may be authorized user stations and may be accessed by authorized users to create rules for event detection and management. The event management engine 105 may be implemented as software running on a server that includes a processing unit for executing associated algorithms or computer-executable program instructions. The event management engine 105 can be used to enable parallel and / or sequential execution of a single processor system including one processor or one or more portions of the techniques described herein. It may be implemented using a multiprocessor system that includes a processor. The processes and logic flows described herein are performed by one or more programmable processors that execute one or more computer programs to perform functions by manipulating input data and generating corresponding outputs. May be. The processing unit may include a processor with a computer readable medium such as a random access memory (RAM) (not shown) coupled to the processor. Examples of processors can include, among others, microprocessors, application specific integrated circuits (ASICs), and field programmable object arrays (FPOAs).

  In some embodiments, the event management engine 105 may be implemented as part of a server and user computing device. Examples of suitable implementations of event management engine 105 include receiving, processing, and / or transmitting servers, authorized user computing devices, smartphones, desktop computers, laptop computers, tablet computers, PDAs, and digital data. Other types of processor control devices may be mentioned. In one example, event management engine 105 performs certain operations that are necessary for proper operation of system architecture 100. A suitable event management engine 105 performs these operations as a result of the central processing unit executing software instructions contained within a computer readable medium (such as in memory). In one embodiment, system software instructions are read into memory associated with event management engine 105 from another memory location (such as from a storage device) or from another computing device via a communication interface. In this embodiment, software instructions contained in the memory instruct the event management engine 105 to perform the above process. Alternatively, hardwired circuitry may be used in place of or in combination with software instructions to implement the processes described herein. Thus, the implementations described herein are not limited to a specific combination of hardware circuitry and software.

  The event management engine 105 is communicatively coupled to the event management database 106. In one or more embodiments, the event management database 106 includes data from the ERP system, which includes accounting and finance, human resources, manufacturing, inventory management, sales and marketing, purchasing, warehousing, shipping, As well as data from other logistics groups.

  The event management database 106 may be configured as a combination of an external source and an internal database, and is implemented as a relational database that provides functions for fetching, indexing, and storing data. In these embodiments, the event management database 106 provides the previously described data and other stored data and files to one or more software modules in the event management system 100 for further analysis. Examples of data received from external sources include inventory management, sales, customer interaction, and financial records. The event management database 106 can organize MySQL, PostgreSQL, SQLLite, Microsoft SQL Server, Microsoft Access, Oracle, SAP, dBASE, FoxPro, IBM DB2, LibreOffice Base, FilePro, DataMer It may be implemented by a database management system (DBMS) such as a type of database. In these embodiments, the event management database 106 may be implemented using an application protocol to access and maintain a distributed directory information service or data feed, such as specifically Lightweight Directory Access Control (LDAP). Good. Data stored in database fields may be updated as needed by users with administrative access to the database, for example, to add new data to a library in the database so that the new data is supported Good. Those skilled in the art may further understand that the data stored in the database described herein may be stored or maintained in non-transitory memory, such as subroutines, functions, modules, objects, program products, or processes. It will be appreciated that access may be made, for example, according to such subroutines, functions, modules, objects, program products, or process objects and / or variables. Any of the fields, such as database records, tables, and libraries, may be multidimensional structures similar to arrays or matrices, and may include values or references to other fields, records, tables, or libraries. Any of the foregoing fields may include actual values or links, bindings, references, or pointers to other local or remote sources for such values. The external source may be a single database, multiple databases, or a virtual database, such as a server on the World Wide Web, containing data from multiple sources.

  The electronic communication network 104 may comprise a communication architecture that includes devices and software that facilitates communication between transmitters and receivers residing on one or more computing devices forming the system 100. It will also be apparent to those skilled in the art that the network components may be implemented in dedicated processing devices and / or cloud processing networks. Network 104 may be an intranet, local area network (LAN), cloud network, virtual private network (VPN), wireless area network (WAN), and the Internet, or any other that allows servers and user devices to interact with each other. The network may be configured as follows. Non-limiting examples of devices that make up a network include routers, switches, hubs, firewalls, proxy servers, and telecommunications trunks. Thus, the electronic communication network may be implemented in whole or in part by a wireless or wired communication network or a combination of both. Further, in accordance with various exemplary embodiments of the present invention, a wireless communication network may employ any of a variety of wireless communication technologies, such as Code Division Multiple Access (“CDMA”), Global System for Mobile, Implemented by Communications (“GSM®”) and either wireless local area networks such as WiFi, Worldwide Interoperability for Microwave Access (“WiMAX”), or Bluetooth® May be.

  Event management engine 105 may generate a user interface on a computing device that includes user devices 101, 102, and 103 and designated recipient devices 107 and 108. Such devices are communicatively coupled to and bi-directionally communicate with other devices, databases, and components of the event management system 100. Computing devices including user devices 101, 102, and 103 and designated recipient devices 107 and 108 are laptop computers or desktop computers, or smart phones, mobile phones, tablets, personal digital assistants (PDAs), smart phone clients. It may be a mobile computing device such as an equipped mobile computer or any other data accessible device. Designated recipient devices 107 and 108 are configured to receive notifications from the event management engine 105. The event management engine 105 utilizes a user interface to request, collect, and present information with one or more users. A user can interact with a user interface via an input / output (I / O) device, such as a touch screen, mouse, keyboard, and / or keypad that operates in conjunction with a display. In some embodiments, the data processing module of the event management engine 105 is required by one or more computing devices 101, 102, and 103 and a designated recipient device 107 and 108 or one or more software modules. It is further configured to automatically search for information. In these embodiments, this information is obtained from the event management database 106. In other embodiments, this information is obtained from the operation of one or more software modules in the ERP system. The event management engine 105 may include and / or may be communicatively coupled to a software module that includes one or more audit modules, a rule executor module, an alert and notification module, a document Including, but not limited to, management module and management module. In one or more embodiments, the event management engine 105 may interact with external services, applications, and databases through one or more application programming interfaces (APIs), RSS feeds, or some other structured format. . The API may be a representational state transfer application programming interface (REST API) that controls and manages one or more APIs. In these embodiments, the API may provide web services to one or more mobile applications installed on the computing device. Examples of web services include displaying data on a website, uploading large amounts of data that is later consumed by mobile apps, downloading data to perform custom analysis, and exporting data And so on.

  FIG. 2 is a flowchart illustrating an exemplary process 200 for the flow of information through a module of an event management system for sending notifications. In step 202, the ERP event may be sent to an audit module 204 that provides a record related to the event, such as event metadata, to the event management database. In a next step 206, the ERP event may be sent to an event engine 208 that selects an applicable event to enforce the rule. Next, at step 210, the event engine 208 may send the selected event to a custom rule executor 212 that evaluates the event against the criteria set in the rules provided by the authorized user. . Next, in step 214, a notification regarding an event that has successfully met the criteria and is sent to the notification manager 216 may be triggered by the custom rule executor 212. In a next step 218, the notification manager 216 may send a preferred format alert to the preferred recipient's preferred device. Notification manager 216 may be configured to send alerts in various formats, such as text, email, app notifications, web hyperlinks, to one or more devices, for example. Devices can include smartphones, tablets, and other computing and communication devices. Next, in step 220, the custom rule executor 212 may control the return to the event engine 208. In step 222, the event engine 208 may control the return to the audit module 204, which may then generate an audit server response 224.

  FIG. 3 is a flowchart illustrating an exemplary process 300 for creating rules using an event management system. In a first step 302, the user may log in using the user device and open the rule composer 304. In some embodiments, the rule composer 304 comprises a user interface that allows a user to configure rules and even view existing rules. If the user chooses to create a new rule in the next step 306, the user may be directed to the “Create New Rule” page 308. On the new rule creation page 308, the user is presented with various options for creating a rule. For example, in addition to rules for specific transactions, rules for batches of data or rules for individual users or user groups may be created. After the user selects one of the available options for the type of rule at step 310, the user may be directed to a rule criteria page. The user may further select one or more criteria and a reference operator and enter a reference value. Next, the user is directed to a notification management page. On the notification management page, the user adds additional constraints, such as timebox settings, adds a list of designated users to receive notifications, moves to the next step, or is otherwise directed to the end page It is possible. In this interface, the user can name the newly created rule and add a brief description for other users. The user is then directed to save the rule, such as at step 312, and review one or more features, such as at step 314. Newly created rules can also be presented as a set of rules available in the rule composer 304.

  FIG. 4 is a flowchart illustrating an exemplary process 400 for updating rules. In step 402, the user may open the rule composer 404. The rule composer 404 may include a graphical user interface that allows the user to view existing rules and select the rules to modify / update. The user may then choose to view the criteria associated with the rule at step 406. The user may then be directed to the rule criteria page. On the rule update page 408, the user may review or change one or more criteria as needed at step 410, select or change a reference operator, and enter or change a reference value. The user may then be directed to a grouping / user page. On the grouping and user page, the user may change or add additional constraints such as time box settings. Similarly, the user may change the list of designated recipients to receive notifications and / or add individuals to this and move on to the next step or otherwise be directed to an end page . In this interface, the user may change the name of the updated rule and add a brief description about the updated rule for other users. The user may then be directed to save the rule at step 412 and review one or more features of the updated rule at step 414. The updated rules may also be presented as a set of rules that are available in the rule composer 404.

  Some embodiments include a system for generating a user interface as shown in FIGS. 5A, 5B, 6, 7, and 8 on authorized user devices and designated recipient devices. . A computer program comprising: a set of instructions arranged to communicate with one or more processors, one or more processors communicatively coupled to an event management database, an event management database and an event management engine In conjunction with a non-transitory computer readable medium for storing. These instructions, when executed by one or more processors, are stored on the one or more processors from an authorized device of the enterprise resource planning system as a first plurality of records in an event management database, An operation of receiving a plurality of criteria for defining a rule may be executed. For example, when user login certificates are received from an authorized computing device in an ERP system via an electronic communication network, the event management engine compares these certificates with records in an event management database and Check the user login certificate as an authorized user. The event management engine may then generate a user interface on the computing device provided with the authorized user login credentials via the electronic communication network 104. The event management engine may present one of several user interfaces on the computing device, such as in a web browser or application interface, where authorized users are provided with event management of the enterprise resource planning system. Options may be presented for creating new rules in the database, accessing previously created rules, and / or managing rules.

  FIG. 5A is an illustrative user interface 500a for managing rules, according to an illustrative embodiment. In some embodiments, the generated graphical user interface may include various controls that operate various functions of the application. Such controls may include, for example, icons, text, buttons, input boxes, menus, drop-down lists, sliders, scroll bars, bars, and / or any other operable visual element. Functional control may also be implemented with one or more physical buttons, rather than as part of the user interface of the event management system itself. For example, a particular button, such as a “create new rule” button, may be used to perform a particular function and interact with the interface. The user may initiate the process of creating a new rule by clicking on a button 501 titled “Create a new rule”. Interface 500a may also provide the user with a list of rules that already exist. These rules include column headers such as rule name 502, subscribing user 508, time stamp indicating last modified date 514, last notified date 516, and enable option 518 that allows selection of whether to enable notification. It may be arranged in the form of a table having. For example, the illustrative interface includes two rules: a master user access rule 504 and an HR 11.1 training Ops rule 506. Each of the rules is associated with a particular user, and its identifying information (such as personal email information 510) may be displayed under the column header 508 titled “Subscribed User”. Certain embodiments include notifications sent as alerts in another software application, including content shown on a website. The descriptive user interface also indicates that the rule “HR 11.1 Cruising” is not valid (520). Finally, the trash can icon 522 in the interface may be used to delete a rule.

  When any of the trash can icons 522 is clicked, a confirmation user interface 500b shown in FIG. 5B may be presented to the user. The dialog element 524 may ask the user to cancel the rule deletion 526 or confirm the action by pressing the delete 528 as desired by the user. The user may then be returned to interface 500b. According to an exemplary embodiment, this illustrative user interface 500b of the rule composer module may also be presented to delete unwanted rules. In addition, the system may be configured such that only authorized users are provided with the option to delete existing rules.

  FIG. 6 is an illustrative user interface 600 presented to a user to create a new rule, according to an exemplary embodiment. For example, when user login certificates are received from an authorized computing device in the ERP system via the electronic communication network 104, the event management engine compares these certificates with records in the event management database; Confirm that this user login certificate belongs to an authorized user. The event management engine may then generate a user interface on the computing device provided with the login credentials of the authorized user via the electronic communication network. The event management engine may present a user interface on the computing device, such as in a web browser or application interface, where an authorized user is presented with an option to create a new rule.

  The illustrative user interface 600 is an example of a rule composer module. Embodiments of the user interface workflow include: In a section 602 titled “Rule Type & Name”, the user may be presented with options for creating various types of rules. The clickable button 610 titled “Transaction” is an example for creating a rule based on a transaction executed in the ERP system. The clickable button 612 titled “Batch” is another example for creating a rule that is executed in a batch in the ERP system. The clickable button 614 titled “Access” is yet another example for creating a rule based on user access of the ERP system. In the illustrative user interface 600, the user has selected a transaction rule type. The user may then give the name of the rule by entering text in the name field 616. In this example, the user names the rule “slow response”. The user may then move to section 604 titled “Reference”. The interface guides the user to the addition of grouping criteria 604. The user is presented with a row of criteria elements that are selected in turn from a drop-down selection box to define the criteria for the rule. These elements may include a reference name 618, a reference operator 620, and a reference value 622. When selecting a rule type, the contents of the drop-down selection box for criteria name 618 are populated and enabled. Upon selection of the reference name, the contents of the reference operator 620 drop-down selection box are populated and validated. When the operator selects, the input field of the reference value 622 becomes valid. Once complete criteria are defined, the add button 624 is enabled. Clicking on the add button 624 inserts the defined criteria into the criteria table below the selector. In this example, two criteria are set for the rule: response time 626 with an operator greater than 4.50 seconds and user ID 628 with an operator containing the string “patil”. Deletion buttons 630 and 632 for deleting the criteria 626 and 628 from the rule are enabled.

  Continuing with FIG. 6 as an illustrative user interface, the user selects the desired grouping of events in section 606, labeled “Grouping” in the exemplary embodiment. This interface is generated when the user selects the menu item 606 titled “Group”. The user is presented with options including time box event settings such as occurrence 634 and time interval 636 and other constraints such as grouping events 638 by criteria name. In this example, the user has defined a time interval constraint 636 with an enterable value of 180 seconds and three alert occurrences 634. In addition, the user groups these events by the user ID of element 638. The list of subscribed users for the rule is defined in section 608 by entering an email address in text field 640. In other embodiments, the subscribed user list may be an enterable field or selected from existing users presented as a drop-down menu. This list is populated here with personal email addresses, but in other embodiments, the list is populated with other personal identifiers such as usernames, phone numbers, or employee IDs. Also good. In this exemplary embodiment, the subscribed user is notified by a web application. To add an email notification on alert, the user selects the check box 642 of “Send email to subscribed user”. There may also be an option to communicate to the subscribed user by text message or mobile application. Finally, the user selects the “Save Rule” button 644, which submits this rule to the notification engine. Standard navigation controls for navigating between different interfaces are provided, for example as buttons, but are not so limited. Selecting “Save Rule” 644 redirects the user to the illustrative user interface 500a shown in FIG. 5A, where the newly created rule can be viewed. In certain embodiments, this interface is generated when the user selects a menu item titled “Exit”. The user is presented with an option to enter the rule name in the form of an enterable field or drop-down menu. The user is also given the option to enter a description in the enterable field. Standard navigation controls for navigating between different interfaces navigate the user to the previous screen as a button, for example, a button that directs the user to the process of exiting the rule composer module or canceling the attempt Provided as a button to, but not limited to.

  In one embodiment, when user login credentials are received from an authorized computing device in an ERP system via an electronic communication network, the event management engine compares these certificates with records in an event management database. Then, it may be confirmed that the user login certificate belongs to the designated recipient. The event management engine may then generate a user interface on the recipient computing device provided with the designated recipient certificate via the electronic communication network. The event management engine may present one of a number of user interfaces on the recipient's computing device, such as in a web browser or application interface, where the designated recipient receives enterprise resource planning. An option may be presented to review new or previously received notifications in the system's event management database. In another embodiment, a notification received from an event management engine on a designated recipient device may include a link to an interface through which the event management engine presents further details regarding the notification.

  FIG. 7 is an illustrative user interface 700 of a notification inbox on a designated recipient device, according to an exemplary embodiment. The user interface 700 presents details about the notification to the designated recipient when the recipient device logs into the system or is communicating with the system. For example, the executed rules may be identified by rules each having a count value, such as a clickable button 702. The user interface also allows the user to search by selecting a clickable button 702 or by entering text in a search box 704. The user can view various instances when a notification is triggered by presenting information in the form of a table as shown, with column headings such as date and time 706, rules 708, details 710, events 712, and trash can 714. You can search. Rules 708 may identify executed rules. Details 710 may present details of the rule criteria summary. Event 712 may provide a link to the user interface as shown in FIG. The recycle bin 714 may be selected to delete an event, and the column header has a delete button 716 that deletes all selected notifications. In the top row of the example provided, a notification regarding the “HR11.1 cruising” rule 712 is sent to the specified recipient at a specific time of date 706 on January 18, 2016. . This rule can be explained by a brief explanation of details 710 that “transaction name is equal to HR 11.1”. The user is presented with an option to view details of each event as shown in interface 800 by clicking or selecting button 712. Standard navigation controls are provided as buttons or links to control movement between different interfaces.

  FIG. 8 is an illustrative user interface 800 of notification event details on a specified recipient device, according to an example embodiment. Interface 800 presents details of ERP system events that meet the criteria of rule 802 of rule type 804. Matching criteria at the time of the event are listed in section 806 labeled “Criteria Details” and are shown as 810, 812, and 814. The triggering events are listed in tabular format in section 808 labeled “Event”, where the time point 816, user 818, transaction name 820, response time 822, and response code 824 are shown. The series of columns in the user interface 800 is specific to the rule type. The user can navigate to various notifications, such as those listed in the user interface 700, using controls 826 and 828 having labels of “previous notification” and “next notification”, respectively.

  FIG. 9 is an illustrative class diagram 900 illustrating a high-level diagram of various software modules / packages that collectively perform event management functions, according to an example embodiment. A diagram 900 shows object interactions arranged in a time series, and includes a buildConFIGjava 901, an EventEngine 902, a RuleProcessor 910, a RuleExector 912, a SimpleRuleExecutor906, a TimeBoxRuleExecutor914, and a TimeBoxRuleExecutor914. The two classes of RuleExecutor 912 and SimpleRuleExector 906 are hierarchically superior classes. EventEngine 902 is associated with RuleProcessor 910, which in turn is associated with RuleExecutor 912 and fed to RuleExecutor 912. The event is also handled by RuleExecutor 912, SimpleRuleExecutor 906, and TimeBoxRuleExecutor 914. In addition, a particular class, for example NotificationDaemon 916, is represented in the UML class diagram 900 as a rectangle 917 having three sections 918, 919, and 920. The first partition 918 indicates the class name “NotificationDaemon”, the second partition 919 indicates the class attributes (ie, structure), and the third partition 920 is the method (ie, behavior) performed by that class.

  10A and 10B form a continuous flow chart illustrating an event management process 1000 according to an exemplary embodiment. The process may begin at step 1002 and proceed to input the event buffer from the ERP system to the event management system at step 1004. The system may proceed to step 1006 where the event buffer may be available to the audit server module, and the audit server module inserts a record into the event database at step 1008. After successful insertion of the record, at step 1010, the event management engine may check the special event buffer. In this regard, if it is determined in step 1012 that a special event buffer exists, the input event buffer may be sent to the rule executor module in step 1014. The rule executor validates the event buffer against applicable defined rules in the new thread and redirects it to a path that generates an appropriate response from the audit server at step 1022 or step 1018. May be sent to evaluate whether a notification should be sent. If it is not necessary to send a notification, it is redirected to generate an appropriate response from the audit server at step 1022 and the process may end at step 1024. If a notification needs to be sent to the designated recipient, the system may proceed to the part of the process described in FIG. 10B. The input event buffer may be sent to the notification manager or notification management module at step 1026. In a next step 1028, the notification manager may send a notification in a preferred format to the preferred recipient's preferred device. Notification Manager configured to send alerts in various formats such as text, email, app notifications, and web hyperlinks to one or more devices such as smartphones, tablets, and other computing and communication devices May be. The notification manager may store data and metadata associated with the notification in the event database 1008 at step 1030. The computer software described herein may be executed on one computer or on several computers networked together.

  The foregoing method descriptions and process flow diagrams are provided merely as illustrative examples, and do not require or suggest that the steps of the various embodiments must be performed in the order presented. Absent. As will be appreciated by those skilled in the art, the steps in the foregoing embodiments may be performed in any order. Terms such as “then”, “next”, etc. do not limit the order of the steps, and these terms are merely used to guide the reader through the description of the method. Although a process flow diagram may describe the operations as a sequential process, many of the operations can be performed in parallel or concurrently. Further, the order of operations may be rearranged. A process may correspond to a method, function, procedure, subroutine, subprogram, etc. If the process corresponds to a function, its termination may correspond to the return of the function to the calling function or main function.

  Various illustrative logic blocks, modules, circuits, and algorithm steps described in connection with the embodiments disclosed herein are implemented as electronic hardware, computer software, or a combination of both. Also good. To clearly illustrate this compatibility between hardware and software, various illustrative components, blocks, modules, circuits, and steps are generally described above with respect to their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. Those skilled in the art can implement the described functions in a variety of ways for each particular application, but such implementation decisions should not be construed as departing from the scope of the invention.

  Embodiments implemented in computer software may be implemented in software, firmware, middleware, microcode, hardware description language, or any combination thereof. A code segment or machine-executable instruction may represent a procedure, function, subprogram, program, routine, subroutine, module, software package, class, or any combination of instructions, data structures, or program statements. A code segment may be coupled to another code segment or a hardware circuit by passing and / or receiving information, data, arguments, parameters, or memory contents. Information, arguments, parameters, data, etc. may be passed, forwarded, or transmitted by any suitable means such as memory sharing, message passing, token passing, network transmission, etc.

  The actual software code or specialized control hardware used to implement these systems and methods is not limiting of the invention. Accordingly, the operation and behavior of the system and method are described without reference to specific software code, and the software and control hardware can be designed to implement the system and method based on the description herein. It is understood.

  If implemented in software, the functions may be stored as one or more instructions or code on a non-transitory computer-readable storage medium or processor-readable storage medium. The steps of the method or algorithm disclosed herein may be implemented in a processor-executable software module that may reside on a computer-readable or processor-readable storage medium. Non-transitory computer readable media or processor readable media include both computer storage media and tangible storage media that facilitate the transfer of a computer program from one place to another. A non-transitory processor readable storage medium may be any available medium that can be accessed by a computer. By way of example, and not limitation, such non-transitory processor readable media can be RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage, or instructions or data structure. Any other tangible storage medium that can be used to store the desired program code in the form of and can be accessed by a computer or processor may be provided. As used herein, a disc and a disc are a compact disc (CD), a laser disc, an optical disc, and a digital versatile disc (DVD). Versatile discs, floppy discs, and Blu-ray discs, which normally play data magnetically, while discs are discs The data is optically reproduced using a laser. Combinations of the above should also be included within the scope of computer-readable media. Further, the operations of the method or algorithm may reside on a non-transitory processor readable medium and / or computer readable medium that may be incorporated into a computer program product as one or any combination or set of codes and / or instructions. Also good.

  If implemented in hardware, the functions may be implemented in circuits of a wireless signal processing circuit that may be suitable for use in a wireless receiver or mobile device. Such wireless signal processing circuitry may include circuitry for accomplishing the signal measurement and calculation steps described in the various embodiments.

  The hardware used to implement the various illustrative logic, logic blocks, modules, and circuits described in connection with aspects disclosed herein is a general purpose processor, digital signal processor (DSP). , Application specific integrated circuit (ASIC), field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or perform the functions described herein May be implemented or implemented using any combination of these designed. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, eg, a DSP and microprocessor combination, a plurality of microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration. Also good. Alternatively, some steps or methods may be performed by circuitry that is specific to a given function.

  Reference to an element in a claim in the singular, for example using the article “a”, “an”, or “the” limits the element to the singular. Should not be construed as doing. The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the invention. obtain. Accordingly, the present invention is not intended to be limited to the embodiments shown herein, but includes the following claims as well as the principles and novel features disclosed herein. The widest range consistent with should be given.

Claims (20)

A method for detecting an event in an enterprise resource planning system, comprising:
Receiving, by a server, a plurality of criteria defining a rule stored as a first plurality of records in an event management database from an authorized device of the enterprise resource planning system, the plurality of criteria comprising: Selected by the user through a rule configuration graphical user interface that presents rule type options, including transaction, batch, and access, wherein the plurality of criteria includes a name, an operator, and a value; ,
Receiving, by the server, a plurality of information relating to a first plurality of events occurring at a plurality of user devices in the enterprise resource planning system, wherein each of the events includes an instance of a data transaction. When,
The first plurality of information to identify a second plurality of events by comparing the plurality of information associated with the first plurality of events and all of the plurality of criteria associated with the rule. Filtering events by the server, wherein one or more of the plurality of information associated with the second plurality of events satisfy all of the plurality of criteria associated with the rule;
Retrieving, by the server, a second plurality of records defining a notification profile associated with the rule from the event management database in response to identifying the second plurality of events, the notification A profile comprising one or more preferences for a notification format and one or more designated recipient devices;
Generating one or more notifications by formatting the one or more of the plurality of information associated with the second plurality of events based on the notification profile by the server;
The server sends the one or more notifications to the one or more designated recipient devices and presents a first of the one or more notifications via the graphical user interface. An event details graphical user interface, wherein the first notification includes a date and time, rules, and event details for each event of the second plurality of events, and selecting the event details A method comprising the steps of:   The method of claim 1, wherein the transaction type rules comprise rules for transactions executed in the enterprise resource planning system.   The method of claim 2, wherein the batch type rule comprises a rule that is executed on a batch in the enterprise resource planning system.   4. The method of claim 3, wherein the access type rules comprise rules for user access of the enterprise resource planning system.   The method of claim 1, wherein the event details graphical user interface displays rule names and rule types.   The method of claim 5, wherein the event details graphical user interface further comprises presenting the name, the operator, and the value of the criteria for the rule.   The method of claim 6, wherein the event details graphical user interface further presents each of the second plurality of events.   The method of claim 7, wherein the event details graphical user interface further presents a time point, user identifier, transaction name, response time, and response code for the event. A system for detecting an event in an enterprise resource planning system, the system comprising:
An event management database;
A processor communicatively coupled to the event management database, the processor comprising:
Receiving a plurality of criteria defining rules stored as a first plurality of records in an event management database from an authorized device of the enterprise resource planning system, wherein the plurality of criteria is a transaction Actions selected by the user via a rule configuration graphical user interface that presents options of rule types, including batch, and access, wherein the plurality of criteria includes a name, an operator, and a value;
An operation for receiving a plurality of information related to a first plurality of events occurring at a plurality of user devices in the enterprise resource planning system, wherein each of the events includes an instance of a data transaction;
The first plurality of information to identify a second plurality of events by comparing the plurality of information associated with the first plurality of events and all of the plurality of criteria associated with the rule. An operation of filtering events, wherein one or more of the plurality of information associated with the second plurality of events satisfy all of the plurality of criteria associated with the rule;
In response to identifying the second plurality of events, searching the event management database for a second plurality of records defining a notification profile associated with the rule, the notification profile comprising: An action comprising one or more preferences for the notification format and one or more designated recipient devices;
Formatting one or more of the plurality of information related to the second plurality of events based on the notification profile to generate one or more notifications;
Sending the one or more notifications to the one or more designated recipient devices and presenting a first notification of the one or more notifications via the graphical user interface; , The first notification includes a date and time for each event of the second plurality of events, the rules, and event details, and selecting the event details presents an event details graphical user interface A system that is configured to perform actions.   The system of claim 9, wherein the transaction type rules comprise rules relating to transactions executed in the enterprise resource planning system.   The system of claim 10, wherein the batch type rule comprises a rule that is executed on a batch in the enterprise resource planning system.   The system of claim 11, wherein the access type rules comprise rules for user access of the enterprise resource planning system.   The system of claim 9, wherein the event details graphical user interface displays rule names and rule types.   The system of claim 13, wherein the event details graphical user interface further comprises presenting the name, the operator, and the value of the criteria for the rule.   The system of claim 14, wherein the event details graphical user interface further presents each of the second plurality of events.   The system of claim 15, wherein the event details graphical user interface further presents a time point, user identifier, transaction name, response time, and response code for the event. A computer-readable storage medium storing instructions that, when executed by a computing system, cause the computing system to perform an operation of a method for detecting an event in an enterprise resource planning system, the operation comprising:
Receiving, by a server, a plurality of criteria defining rules stored from a permitted device of the enterprise resource planning system as a first plurality of records in an event management database, wherein the plurality of criteria is Selected by the user through a rule configuration graphical user interface that presents rule type options, including transaction, batch, and access, and the plurality of criteria includes an action including a name, an operator, and a value. ,
An operation of receiving, by the server, a plurality of information related to a first plurality of events occurring at a plurality of user devices in the enterprise resource planning system, wherein each of the events includes an instance of a data transaction When,
The first plurality of information to identify a second plurality of events by comparing the plurality of information associated with the first plurality of events and all of the plurality of criteria associated with the rule. An operation of filtering events by the server, wherein one or more of the plurality of information associated with the second plurality of events satisfy all of the plurality of criteria associated with the rule;
In response to identifying the second plurality of events, the server searches the event management database for a second plurality of records defining a notification profile associated with the rule, the notification An operation in which the profile includes one or more preferences for the notification format and one or more designated recipient devices;
Formatting the one or more of the plurality of information related to the second plurality of events to generate one or more notifications by the server based on the notification profile;
The server sends the one or more notifications to the one or more designated recipient devices and presents a first of the one or more notifications via the graphical user interface. An event details graphical user interface by selecting the event details, wherein the first notification includes a date and time, rules, and event details for each event of the second plurality of events A computer-readable storage medium comprising:   The computer readable storage medium of claim 17, wherein the transaction type rules comprise rules relating to transactions executed in the enterprise resource planning system.   The computer readable storage medium of claim 18, wherein the batch type rule comprises a rule that is executed on a batch in the enterprise resource planning system.   The computer readable storage medium of claim 19, wherein the access type rules comprise rules for user access of the enterprise resource planning system.