# US 2025/0086044 A1 · Systems and methods for multi-system fault determination > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2025/0086044 A1 - Document ID: US20250086044A1 - Status: Published application - Kind: A1 - Application number: 18/464,133 - Filed: 2023-09-08 - Published: 2025-03-13 - Earliest claimed: 2023-09-08 - Assignees: Sap SE - Applicants: Sap SE - Inventors: Manish Gupta - Web page: https://patentgrep.com/patent/US20250086044A1 ## CPC - G06F 11/0709: {in a distributed system consisting of a plurality of standalone computer nodes, e.g. clusters, client-server systems} - G06F 11/0787: {Storage of error reports, e.g. persistent data storage, storage using memory protection} - G06F 11/0751: {Error or fault detection not based on redundancy (power supply failures G06F1/30; network fault management H04L41/06)} - G06F 11/0769: {Readable error formats, e.g. cross-platform generic formats, human understandable formats} - G06F 11/0775: {Content or structure details of the error report, e.g. specific table structure, specific error fields} - G06F 11/079: {Root cause analysis, i.e. error or fault diagnosis (in a hardware test environment G06F11/22; in a software test environment G06F11/36)} - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## Abstract Embodiments of the present disclosure include techniques for determining faults across multiple software applications. In one embodiment, a configuration table is loaded with information specifying relationships between software applications. Fault events from the software applications are received and stored in a fault log database. A query is received pertaining to a fault in one of the applications, and the information in the configuration table is used to determine details about faults in other software applications related to the fault specified in the query. The other software systems are accessed to retrieve fault information, and a fault relationship table is populated providing more insight into relationships between faults across the applications. ## Claims ### Claim 1 A method of determining faults comprising: storing information specifying relationships between a plurality of software applications; receiving fault events from a plurality of software servers executing the plurality of software applications, the fault events comprising data specifying faults; storing the fault events; receiving a query, the query specifying information pertaining to a first fault in a first software application of the plurality of software applications; retrieving the information specifying relationships between the plurality of software applications; retrieving one or more first fault events from the stored fault events, based on the information pertaining to the first fault; retrieving, from second software applications of the plurality of software applications directly or indirectly interacting with the first software application, as determined from the first fault events and information specifying relationships between the plurality of software applications, information describing the first fault; and storing the information describing the first fault in a table. ### Claim 2 (depends on 1) The method of claim 1, wherein information specifying relationships between a plurality of software applications comprises one or more of: an identifier associated with the first software application, a server identifier associated with the first software application, an identifier associated with a second software application dependent on the first software application, a server identifier associated with the second software application, and one or more first fault search relevant fields; and a plurality of: an identifier associated with a parent software application, including at least the second software application, a server identifier associated with the parent software application, an identifier associated with a dependent software application dependent on the parent software application, a server identifier associated with the parent software application, and one or more second fault search relevant fields. ### Claim 3 (depends on 1) The method of claim 1, wherein the data specifying faults comprises: an identifier of the software application generating the fault event and one or more text fields in the fault events describing the fault events. ### Claim 4 (depends on 1) The method of claim 1, wherein the query specifying information pertaining to the first fault comprises an identifier associated with the first software application, an object identifier associated with an object in the first software application experiencing an error condition, and an identifier associated with a first server running the first software application. ### Claim 5 (depends on 1) The method of claim 1, wherein the information describing the first fault comprises an object identifier, an object type, a server identifier, a node identifier, a parent node identifier, a node level, and a fault log identifier. ### Claim 6 (depends on 1) The method of claim 1, wherein the plurality of software applications form a hierarchy. ### Claim 7 (depends on 6) The method of claim 6, wherein the first software application interfaces with one or more second software applications forming a second hierarchical layer, and the one or more second software applications interface with a plurality of third software applications across the hierarchy, and wherein the information specifying relationships between the plurality of software applications specifies a position of each software application in the hierarchy. ### Claim 8 (depends on 6) The method of claim 6, the method further comprising iteratively connecting to the second and third software applications to retrieve fault event information. ### Claim 9 (depends on 1) The method of claim 1, further comprising generating, based on the information describing the first fault in the table, a hierarchical model of interrelated fault events across the plurality of software applications and presenting the hierarchical model to a user. ### Claim 10 A computer system comprising: at least one processor; at least one non-transitory computer readable medium storing computer executable instructions that, when executed by the at least one processor, cause the computer system to perform a method of determining faults comprising: storing information specifying relationships between a plurality of software applications; receiving fault events from a plurality of software servers executing the plurality of software applications, the fault events comprising data specifying faults; storing the fault events; receiving a query, the query specifying information pertaining to a first fault in a first software application of the plurality of software applications; retrieving the information specifying relationships between the plurality of software applications; retrieving one or more first fault events from the stored fault events, based on the information pertaining to the first fault; retrieving, from second software applications of the plurality of software applications directly or indirectly interacting with the first software application, as determined from the first fault events and information specifying relationships between the plurality of software applications, information describing the first fault; and storing the information describing the first fault in a table. ### Claim 11 (depends on 10) The computer system of claim 10, wherein the plurality of software applications form a hierarchy. ### Claim 12 (depends on 10) The computer system of claim 10, wherein information specifying relationships between a plurality of software applications comprises one or more of: an identifier associated with the first software application, a server identifier associated with the first software application, an identifier associated with a second software application dependent on the first software application, a server identifier associated with the second software application, and one or more first fault search relevant fields; and a plurality of: an identifier associated with a parent software application, including at least the second software application, a server identifier associated with the parent software application, an identifier associated with a dependent software application dependent on the parent software application, a server identifier associated with the parent software application, and one or more second fault search relevant fields. ### Claim 13 (depends on 10) The computer system of claim 10, wherein the data specifying faults comprises: an identifier of the software application generating the fault event and one or more text fields in the fault events describing the fault events. ### Claim 14 (depends on 10) The computer system of claim 10, wherein the query specifying information pertaining to the first fault comprises an identifier associated with the first software application, an object identifier associated with an object in the first software application experiencing an error condition, and an identifier associated with a first server running the first software application. ### Claim 15 (depends on 10) The computer system of claim 10, wherein the information describing the first fault comprises an object identifier, an object type, a server identifier, a node identifier, a parent node identifier, a node level, and a fault log identifier. ### Claim 16 A non-transitory computer-readable medium storing computer-executable instructions that, when executed by at least one processor, perform a method of determining faults, the method comprising: storing information specifying relationships between a plurality of software applications; receiving fault events from a plurality of software servers executing the plurality of software applications, the fault events comprising data specifying faults; storing the fault events; receiving a query, the query specifying information pertaining to a first fault in a first software application of the plurality of software applications; retrieving the information specifying relationships between the plurality of software applications; retrieving one or more first fault events from the stored fault events, based on the information pertaining to the first fault; retrieving, from second software applications of the plurality of software applications directly or indirectly interacting with the first software application, as determined from the first fault events and information specifying relationships between the plurality of software applications, information describing the first fault; and storing the information describing the first fault in a table. ### Claim 17 (depends on 16) The non-transitory computer-readable medium of claim 16, wherein the plurality of software applications form a hierarchy. ### Claim 18 (depends on 16) The non-transitory computer-readable medium of claim 16, wherein information specifying relationships between a plurality of software applications comprises one or more of: an identifier associated with the first software application, a server identifier associated with the first software application, an identifier associated with a second software application dependent on the first software application, a server identifier associated with the second software application, and one or more first fault search relevant fields; and a plurality of: an identifier associated with a parent software application, including at least the second software application, a server identifier associated with the parent software application, an identifier associated with a dependent software application dependent on the parent software application, a server identifier associated with the parent software application, and one or more second fault search relevant fields. ### Claim 19 (depends on 16) The non-transitory computer-readable medium of claim 16, wherein the data specifying faults comprises: an identifier of the software application generating the fault event and one or more text fields in the fault events describing the fault events. ### Claim 20 (depends on 16) The non-transitory computer-readable medium of claim 16, wherein the query specifying information pertaining to the first fault comprises an identifier associated with the first software application, an object identifier associated with an object in the first software application experiencing an error condition, and an identifier associated with a first server running the first software application.