# US 10,503,816 B2 · Real-time view-based reporting metadata > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 10,503,816 B2 - Document ID: US10503816B2 - Status: Granted - Kind: B2 - Application number: 15/606,476 - Filed: 2017-05-26 - Published: 2018-11-29 - Granted: 2019-12-10 - Earliest claimed: 2017-05-26 - Assignees: Sap SE - Applicants: Sap SE - Inventors: Janel Lynn Brandon; Willy Tjandra; Raghavendra Konduru; Alvin Sheng Jye Lim - Web page: https://patentgrep.com/patent/US10503816B2 ## CPC - G06F 16/26: Visual data mining; Browsing structured data - G06F 16/9038: Presentation of query results - G06F 16/951: Indexing; Web crawling techniques - G06F 16/9538: Presentation of query results - G06F 40/143: Markup, e.g. Standard Generalized Markup Language [SGML] or Document Type Definition [DTD] - G06F 40/186: Templates - G06F 3/0488: using a touch-screen or digitiser, e.g. input of commands through traced gestures - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## Abstract In an example, a database is accessed to obtain a first metadata type, the database further including a second metadata type and a third metadata type, the third metadata type including instance-specific reporting metadata. The first metadata type is persisted in the memory, while the instance-specific reporting metadata is not persisted. In response to receiving a request from the graphical user interface to provide options for inclusion in a custom report template for the user, information from the first metadata type is sent to a graphical user interface, information regarding the instance-specific reporting metadata is generated by executing structured query language (SQL) queries stored in database views for the database. ## Claims ### Claim 1 A system comprising: a memory; an application executable by at least one hardware processor of the system to perform operations comprising: accessing a database to obtain reporting metadata, the reporting metadata including metadata of a first metadata type, metadata of a second metadata type, and metadata of a third metadata type, the first metadata type being of a type that is updated by the application less frequently than the second metadata type is updated by the application, the second metadata type being of a type that is updated less frequently by the application than the third metadata type is updated by the application, the third metadata type including instance-specific reporting metadata; based on a determination that a first portion of the reporting data is of the first metadata type, persisting the first portion in a memory; based on a determination that a third portion of the reporting data is of the third metadata type, not persisting the third portion of the reporting data; receiving a request from a graphical user interface to provide options for inclusion in a custom report template; and in response to the receiving: generating information regarding the instance-specific reporting metadata by executing structured query language (SQL) queries stored in database views for the database, the information regarding the instance-specific reporting metadata preventing inclusion of one or more selectable objects and fields in the custom report template. ### Claim 2 (depends on 1) The system of claim 1, wherein the application is further to perform operations comprising not persisting an instance-specific data model configuration. ### Claim 3 (depends on 1) The system of claim 1, wherein the application is further to perform operations comprising persisting an instance-specific data model configuration in the memory and to, upon receiving a request from the graphical user interface to provide options for inclusion in a custom report template, sending information regarding the instance-specific data model configuration to the graphical user interface. ### Claim 4 (depends on 3) The system of claim 3, wherein the application obtains the instance-specific data model configuration by parsing one or more Extensible Markup Language (XML) files. ### Claim 5 (depends on 1) The system of claim 1, wherein the application is further to perform operations comprising not persisting an instance-specific data model configuration and to, upon receiving a request from the graphical user interface to provide options for inclusion in the custom report template, obtaining the instance-specific data model configuration by parsing one or more XML files and send information regarding the instance-specific data model configuration to the graphical user interface. ### Claim 6 (depends on 1) The system of claim 1, wherein the first metadata type includes a database schema. ### Claim 7 (depends on 1) The system of claim 1, wherein the first metadata type is only updated when a major version change occurs in the database schema. ### Claim 8 A computerized method comprising: accessing a database to obtain reporting metadata, the reporting metadata including metadata of a first metadata type, metadata of a second metadata type, and metadata of a third metadata type, the first metadata type being of a type that is updated by the application less frequently than the second metadata type is updated by the application, the second metadata type being of a type that is updated less frequently by the application than the third metadata type is updated by the application, the third metadata type including instance-specific reporting metadata; based on a determination that a first portion of the reporting data is of the first metadata type, persisting the first portion in a memory; based on a determination that a third portion of the reporting data is of the third metadata type, not persisting the third portion of the reporting data; receiving a request from a graphical user interface to provide options for inclusion in a custom report template; and in response to the receiving: generating information regarding the instance-specific reporting metadata by executing structured query language (SQL) queries stored in database views for the database, the information regarding the instance-specific reporting metadata preventing inclusion of one or more selectable objects and fields in the custom report template. ### Claim 9 (depends on 8) The method of claim 8, further comprising not persisting an instance-specific data model configuration. ### Claim 10 (depends on 8) The method of claim 8, further comprising: persisting an instance-specific data model configuration from the database in the memory; and upon receiving a request from the graphical user interface to provide options for inclusion in a custom report template, sending information regarding the instance-specific data model configuration to the graphical user interface. ### Claim 11 (depends on 10) The method of claim 10, wherein the instance-specific data model configuration is obtained by parsing one or more Extensible Markup Language (XML) files. ### Claim 12 (depends on 8) The method of claim 8, further comprising not persisting an instance-specific data model configuration from the database and to, upon receiving a request from the graphical user interface to provide options for inclusion in the custom report template, obtain the instance-specific data model configuration by parsing one or more XML files and send information regarding the instance-specific data model configuration to the graphical user interface. ### Claim 13 (depends on 8) The method of claim 8, wherein the first metadata type includes a database schema. ### Claim 14 (depends on 8) The method of claim 8, wherein the first metadata type includes relationships between objects and fields in the database. ### Claim 15 A non-transitory machine-readable storage medium comprising instructions, which when implemented by one or more machines, cause the one or more machines to perform operations comprising: accessing a database to obtain reporting metadata, the reporting metadata including metadata of a first metadata type, metadata of a second metadata type, and metadata of a third metadata type, the first metadata type being of a type that is updated by the application less frequently than the second metadata type is updated by the application, the second metadata type being of a type that is updated less frequently by the application than the third metadata type is updated by the application, the third metadata type including instance-specific reporting metadata; based on a determination that a first portion of the reporting data is of the first metadata type, persisting the first portion in a memory; based on a determination that a third portion of the reporting data is of the third metadata type, not persisting the third portion of the reporting data; receiving a request from a graphical user interface to provide options for inclusion in a custom report template; and in response to the receiving: generating information regarding the instance-specific reporting metadata by executing structured query language (SQL) queries stored in database views for the database, the information regarding the instance-specific reporting metadata preventing inclusion of one or more selectable objects and fields in the custom report template. ### Claim 16 (depends on 15) The non-transitory machine-readable storage medium of claim 15, wherein the operations further comprise not persisting an instance-specific data model configuration. ### Claim 17 (depends on 15) The non-transitory machine-readable storage medium of claim 15, further comprising: persisting an instance-specific data model configuration from the database in the memory; and upon receiving a request from the graphical user interface to provide options for inclusion in a custom report template for the user, sending information regarding the instance-specific data model configuration to the graphical user interface. ### Claim 18 (depends on 17) The non-transitory machine-readable storage medium of claim 17, wherein the instance-specific data model configuration is obtained by parsing one or more Extensible Markup Language (XML) files. ### Claim 19 (depends on 15) The non-transitory machine-readable storage medium of claim 15, further comprising not persisting an instance-specific data model configuration from the database and to, upon receiving a request from the graphical user interface to provide options for inclusion in the custom report template, obtain the instance-specific data model configuration by parsing one or more XML files and send information regarding the instance-specific data model configuration to the graphical user interface. ### Claim 20 (depends on 15) The non-transitory machine-readable storage medium of claim 15, wherein the standard metadata includes a database schema.