# US 2014/0195476 A1 · Generating notification from database update > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2014/0195476 A1 - Document ID: US20140195476A1 - Status: Published application - Kind: A1 - Application number: 13/738,686 - Filed: 2013-01-10 - Published: 2014-07-10 - Earliest claimed: 2013-01-10 - Assignees: Sap SE - Inventors: Olaf Sxhmidt - Web page: https://patentgrep.com/patent/US20140195476A1 ## CPC - G06Q 30/0633: {Managing shopping lists, e.g. compiling or processing purchase lists (shipping orders G06Q10/083; order filling G06Q10/087)} - G06F 16/23: Updating - G06Q 30/0601: Electronic shopping [e-shopping] - G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## Abstract A computer-implemented method for generating a notification from an in-memory database update includes: detecting an in-memory database event that inserts, deletes or modifies a first record in an in-memory database; executing a first database trigger that corresponds to the detected in-memory database event; identifying a first business event definition that is mapped to the executed first database trigger; and generating a first notification that corresponds to the identified first business event definition, the first notification generated for a first subscriber to the identified first business event definition. ## Claims ### Claim 1 A computer-implemented method for generating a notification from an in-memory database update, the method comprising: detecting an in-memory database event that inserts, deletes or modifies a first record in an in-memory database; executing a first database trigger that corresponds to the detected in-memory database event; identifying a first business event definition that is mapped to the executed first database trigger; and generating a first notification that corresponds to the identified first business event definition, the first notification generated for a first subscriber to the identified first business event definition. ### Claim 2 (depends on 1) The computer-implemented method of claim 1, wherein the first database trigger is executed using a trigger engine operating in a server hosting the in-memory database, wherein the first business event definition is identified by an event publisher operating in an application server associated with the server, and wherein the notification is generated by a notification publisher operating in a gateway system hosted by the application server. ### Claim 3 (depends on 1) The computer-implemented method of claim 1, wherein: an application is operated by executing custom code in an application container hosted by an application server; the first subscriber to the first identified business event includes at least the application; the application generates an alert to a gateway system hosted by the application server, the alert generated using an API of the gateway system; a subscription manager in the gateway system identifies a second subscriber to the generated alert; and a notification publisher hosted by the gateway system generates a second notification that corresponds to the generated alert, the second notification generated for the identified second subscriber. ### Claim 4 (depends on 1) The computer-implemented method of claim 1, wherein the executed first database trigger further inserts, deletes or modifies a second record in the in-memory database, and wherein the insertion, deletion or modification of the second record further causes a second database trigger to be executed. ### Claim 5 (depends on 4) The computer-implemented method of claim 4, wherein the first subscriber to the identified business event definition is not a subscriber to a second business event definition that is mapped to the executed second database trigger. ### Claim 6 (depends on 1) The computer-implemented method of claim 1, further comprising specifying, before the first database trigger is executed, whether the first database trigger is executed (i) once for each affected record in the in-memory database, or (ii) once for each execution of an operation that affects one or more records in the in-memory database. ### Claim 7 (depends on 1) The computer-implemented method of claim 1, further comprising presenting a subscription control adjacent a user interface feature regarding at least the first record in the in-memory database, wherein activation of the subscription control establishes subscription to the first business event definition. ### Claim 8 A computer program product embodied in a non-transitory computer-readable storage medium and comprising instructions that when executed by a processor perform a method for generating a notification from an in-memory database update, the method comprising: detecting an in-memory database event that inserts, deletes or modifies a first record in an in-memory database; executing a first database trigger that corresponds to the detected in-memory database event; identifying a first business event definition that is mapped to the executed first database trigger; and generating a first notification that corresponds to the identified first business event definition, the first notification generated for a first subscriber to the identified first business event definition. ### Claim 9 (depends on 8) The computer program product of claim 8, wherein the first database trigger is executed using a trigger engine operating in a server hosting the in-memory database, wherein the first business event definition is identified by an event publisher operating in an application server associated with the server, and wherein the notification is generated by a notification publisher operating in a gateway system hosted by the application server. ### Claim 10 (depends on 8) The computer program product of claim 8, wherein: an application is operated by executing custom code in an application container hosted by an application server; the first subscriber to the first identified business event includes at least the application; the application generates an alert to a gateway system hosted by the application server, the alert generated using an API of the gateway system; a subscription manager in the gateway system identifies a second subscriber to the generated alert; and a notification publisher hosted by the gateway system generates a second notification that corresponds to the generated alert, the second notification generated for the identified second subscriber. ### Claim 11 (depends on 8) The computer program product of claim 8, wherein the executed first database trigger further inserts, deletes or modifies a second record in the in-memory database, and wherein the insertion, deletion or modification of the second record further causes a second database trigger to be executed. ### Claim 12 (depends on 11) The computer program product of claim 11, wherein the first subscriber to the identified business event definition is not a subscriber to a second business event definition that is mapped to the executed second database trigger. ### Claim 13 (depends on 8) The computer program product of claim 8, the method further comprising specifying, before the first database trigger is executed, whether the first database trigger is executed (i) once for each affected record in the in-memory database, or (ii) once for each execution of an operation that affects one or more records in the in-memory database. ### Claim 14 (depends on 8) The computer program product of claim 8, the method further comprising presenting a subscription control adjacent a user interface feature regarding at least the first record in the in-memory database, wherein activation of the subscription control establishes subscription to the first business event definition. ### Claim 15 A system comprising: one or more processors; and a computer program product embodied in a non-transitory computer-readable storage medium and comprising instructions that when executed by a processor perform a method for generating a notification from an in-memory database update, the method comprising: detecting an in-memory database event that inserts, deletes or modifies a first record in an in-memory database; executing a first database trigger that corresponds to the detected in-memory database event; identifying a first business event definition that is mapped to the executed first database trigger; and generating a first notification that corresponds to the identified first business event definition, the first notification generated for a first subscriber to the identified first business event definition. ### Claim 16 (depends on 15) The system of claim 15, wherein the first database trigger is executed using a trigger engine operating in a server hosting the in-memory database, wherein the first business event definition is identified by an event publisher operating in an application server associated with the server, and wherein the notification is generated by a notification publisher operating in a gateway system hosted by the application server. ### Claim 17 (depends on 15) The system of claim 15, wherein: an application is operated by executing custom code in an application container hosted by an application server; the first subscriber to the first identified business event includes at least the application; the application generates an alert to a gateway system hosted by the application server, the alert generated using an API of the gateway system; a subscription manager in the gateway system identifies a second subscriber to the generated alert; and a notification publisher hosted by the gateway system generates a second notification that corresponds to the generated alert, the second notification generated for the identified second subscriber. ### Claim 18 (depends on 15) The system of claim 15, wherein the executed first database trigger further inserts, deletes or modifies a second record in the in-memory database, and wherein the insertion, deletion or modification of the second record further causes a second database trigger to be executed. ### Claim 19 (depends on 18) The system of claim 18, wherein the first subscriber to the identified business event definition is not a subscriber to a second business event definition that is mapped to the executed second database trigger. ### Claim 20 (depends on 15) The system of claim 15, the method further comprising presenting a subscription control adjacent a user interface feature regarding at least the first record in the in-memory database, wherein activation of the subscription control establishes subscription to the first business event definition.