# US 10,311,390 B2 · Database document generation based on event-based database action recognition > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 10,311,390 B2 - Document ID: US10311390B2 - Status: Granted - Kind: B2 - Application number: 15/201,034 - Filed: 2016-07-01 - Published: 2018-01-04 - Granted: 2019-06-04 - Earliest claimed: 2016-07-01 - Assignees: Sap SE - Applicants: Sap SE - Inventors: Stefan Walz; Joachim Liebler; Birgit Oettinger; Martin Vogt; Frank Emminghaus - Web page: https://patentgrep.com/patent/US10311390B2 ## CPC - G06Q 10/06313: {Resource planning in a project environment} - H04L 67/1097: for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS] - 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 - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## Abstract A commit event to a database table of a first set of database tables, of a distributed database system, can be detected. The first set of database tables can have a set of first table characteristic and the commit event can have a set of commit event characteristics. The commit event can be correlated to a database table of a second set of database tables based on the set of commit event characteristics. The commit event can be assigned a state based on the correlation of the commit event to a database table of the second set of database tables. First and second documents associated with the commit event can be generated. The second document can be based on the state of the commit event and can include adjustment information associated with the commit event and the first document. ## Claims ### Claim 1 A method comprising: detecting, at one or more data processors, a commit event to a database table of a first set of database tables, of a distributed database system, the first set of database tables having a set of first table characteristics and the commit event having a set of commit event characteristics, wherein detection of the commit event to the database table occurs at a physical layer of an architecture of the distributed database system; correlating, by the one or more data processors, the commit event to a database table of a second set of database tables based on the set of commit event characteristics, wherein correlating the commit event to the database table of the second set of database tables occurs at a logical layer of the architecture of the distributed database system; assigning, by the one or more data processors, a state, from a set of predefined states, to the commit event based on the correlation of the commit event to a database table of the second set of database tables; generating, by the one or more data processors within the commit event, a first document associated with the commit event and saving the first document to the second set of database tables, wherein generating the first document, within the commit event, occurs at a view layer of the architecture of the distributed database system; and, generating, by the one or more data processors within the commit event, a second document associated with the commit event, the second document based on the state of the commit event and including adjustment information associated with the commit event and the first document, wherein generating the second document, within the commit event, occurs at the view layer of the architecture of the distributed database system, wherein generating the first document and generating the second document are performed in response to the detection of the commit event and at a time of detection of the commit event. ### Claim 2 (depends on 1) The method of claim 1, wherein the commit event comprises an indication of the expensing of a cost object. ### Claim 3 (depends on 1) The method of claim 1, wherein the database tables of the second set of database tables are assigned to a profit and loss category. ### Claim 4 (depends on 3) The method of claim 3, wherein the first document includes expense information associated with the commit event. ### Claim 5 (depends on 4) The method of claim 4, wherein the second document includes revenue information associated with the commit event. ### Claim 6 (depends on 2) The method of claim 2, wherein the states of the set of predefined states include a future revenue state, a realized revenue state and a non-revenue-based cost state. ### Claim 7 (depends on 6) The method of claim 6, wherein the second document includes an indication of future revenue correlating to commit events having a first commit characteristic, an indication of realized revenue correlating to commit events having a second commit characteristic and/or an indication of expenses correlating to commit events having a third commit characteristic. ### Claim 8 (depends on 1) The method of claim 1, further comprising: aggregating, to form an aggregated set of first documents, a plurality of first documents generated in response to the occurrence of a plurality of commit events that occurred since a period end activity; and, aggregating, to form an aggregated set of second documents, a plurality of second documents generated in response to the occurrence of a plurality of commit events that occurred since a period end activity. ### Claim 9 (depends on 8) The method of claim 8, further comprising: receiving a request, from a user device associated with the distributed database system, for a report containing information stored in the aggregated set of first documents and the aggregated set of second document; and, generating, by the one or more data processors, a report including at least a portion of the information stored in the aggregated set of first documents and the aggregated set of second documents. ### Claim 10 A system comprising: one or more data processors; at least one memory storing computer-readable instructions, which, when executed by the one or more data processors, cause the one or more data processors to perform operations comprising at least: detecting, at one or more data processors, a commit event to a database table of a first set of database tables, of a distributed database system, the first set of database tables having a set of first table characteristics and the commit event having a set of commit event characteristics, wherein detection of the commit event to the database table occurs at a physical layer of an architecture of the distributed database system; correlating, by the one or more data processors, the commit event to a database table of a second set of database tables based on the set of commit event characteristics, wherein correlating the commit event to the database table of the second set of database tables occurs at a logical layer of the architecture of the distributed database system; assigning, by the one or more data processors, a state, from a set of predefined states, to the commit event based on the correlation of the commit event to a database table of the second set of database tables; generating, by the one or more data processors within the commit event, a first document associated with the commit event and saving the first document to the second set of database tables, wherein generating the first document, within the commit event, occurs at a view layer of the architecture of the distributed database system; and, generating, by the one or more data processors within the commit event, a second document associated with the commit event, the second document based on the state of the commit event and including adjustment information associated with the commit event and the first document, wherein generating the second document, within the commit event, occurs at the view layer of the architecture of the distributed database system, wherein generating the first document and generating the second document are performed in response to the detection of the commit event and at a time of detection of the commit event. ### Claim 11 (depends on 10) The system of claim 10, wherein the commit event comprises an indication of the expensing of a cost object. ### Claim 12 (depends on 10) The system of claim 10, wherein the database tables of the second set of database tables are assigned to a profit and loss category. ### Claim 13 (depends on 12) The system of claim 12, wherein the first document includes expense information associated with the commit event. ### Claim 14 (depends on 13) The system of claim 13, wherein the second document includes revenue information associated with the commit event. ### Claim 15 (depends on 11) The system of claim 11, wherein the states of the set of predefined states include a future revenue state, a realized revenue state and a non-revenue-based cost state. ### Claim 16 (depends on 15) The system of claim 15, wherein the second document includes an indication of future revenue correlating to commit events having a first commit characteristic, an indication of realized revenue correlating to commit events having a second commit characteristic and/or an indication of expenses correlating to commit events having a third commit characteristic. ### Claim 17 (depends on 10) The system of claim 10, further comprising: aggregating, to form an aggregated set of first documents, a plurality of first documents generated in response to the occurrence of a plurality of commit events that occurred since a period end activity; and, aggregating, to form an aggregated set of second documents, a plurality of second documents generated in response to the occurrence of a plurality of commit events that occurred since a period end activity. ### Claim 18 (depends on 17) The system of claim 17, further comprising: receiving a request, from a user device associated with the distributed database system, for a report containing information stored in the aggregated set of first documents and the aggregated set of second document; and, generating, by the one or more data processors, a report including at least a portion of the information stored in the aggregated set of first documents and the aggregated set of second documents.