Parallel display of multiple query results

• US 9,501,537 B2
• Filed: 11/28/2012
• Issued: 11/22/2016
• Est. Priority Date: 11/28/2012
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP SE
• Inventors: Walter, Wolfgang, von Duhn, Joerg
• Primary Examiner(s): To, Baoquoc N
• Application Number:
  US13/687,814
• Publication Number:
  US 20140149391A1
• Time in Patent Office: 1,455 Days
• Field of Search: 707/705, 707/706, 707/707
• US Class Current: 1/1
• CPC Class Codes: G06F 16/248 Presentation of query results
• CPC Class Codes: H04W 52/027 by controlling a display operation or backlight unit
• CPC Class Codes: Y02D 30/70 in wireless communication networks

Abstract

A computer program product tangibly embodied on a computer-readable medium includes executable code that, when executed, causes at least one computer system hosting a computer application to provide a memory to store results of multiple queries processed by the computer application and a feeder component in a front end display logic layer of the computer application. The feeder component is configured to read the results of the multiple queries stored in the memory asynchronously and to supply the results of the multiple queries in parallel to respective query result display entities in a user interface of the computer application.

Claims

1. A system comprising:

at least one processor configured to execute queries for a computer application having a back end business logic layer separate from a front end display logic layer, each of the queries being a query received by the computer application and being directed from the back end business logic layer of the computer application to business information warehouses or databases;

a user interface including a plurality of query display elements, each query display element configured to display data results of a respective query;

a memory configured to individually store, query-by-query, data results of multiple queries directed from the back end business logic layer of the computer application to the business information warehouses or databases; and

a parallel feeder component installed in the front end display logic layer of the computer application,

wherein the parallel feeder component is configured with logic to retrieve, query-by-query, the individually stored data results of the multiple queries from the shared memory asynchronously or in parallel, and to supply the retrieved individually stored data results of the multiple queries concurrently in parallel to a corresponding multiplicity of query display elements in the user interface for display, and wherein the parallel feeder component is implemented as a custom feeder class in contrast to a standard feeder basis class that always reads data serially or sequentially and can populate multiple display entities only serially or sequentially.

2. The system of claim 1, wherein the parallel feeder component is configured to supply data to a particular query display element in the user interface of the computer application as soon as data for that particular query display element becomes available in the memory.

3. The system of claim 1, wherein the custom feeder class logic is configured to be independent of all specific functionalities of the computer application.

4. A method, comprising:

providing a shared memory to individually store data results of multiple queries for a computer application, each of the multiple queries being a query received by the computer application directed to business information warehouses or databases, the computer application having a front end display logic layer with functionality supporting a user interface and a separate back end layer with functionality supporting query functions; and

providing a parallel feeder component in the front end display logic layer that is configured with logic to retrieve, query-by-query, the individually stored data results of the multiple queries from the shared memory asynchronously or in parallel, and to supply the retrieved individually stored data results of the multiple queries in parallel to a corresponding multiplicity of query display components in the user interface for display, the parallel feeder component being implemented as a custom feeder class in contrast to a standard feeder basis class that always reads data serially or sequentially and can populate multiple display entities only serially or sequentially.

5. The method of claim 4 further comprising providing a service to access the memory storing the data results of multiple queries from the front end display logic layer.

6. The method of claim 4, wherein providing a parallel feeder component in the front end display logic layer includes configuring the parallel feeder component to supply data to a particular query result display entity in the user interface of the computer application as soon as data for that particular query result display entity becomes available in the memory.

7. The method of claim 4, wherein at least one computer system hosting the computer application is an Advanced Business Application Programming (ABAP) system, and wherein implementing the parallel feeder component as a custom feeder class includes implementing the custom feeder class as an ABAP Object Oriented class.

8. The method of claim 4, wherein implementing the parallel feeder component as a custom feeder class includes configuring the custom feeder class to inherit one or more functions from a standard Advanced Business Application Programming (ABAP) feeder basis class.

9. The method of claim 4, wherein providing a parallel feeder component in the front end display logic layer includes configuring the parallel feeder component with logic to read data asynchronously.

10. The method of claim 4, wherein providing a parallel feeder component in the front end display logic layer includes coupling the custom feeder class to a ping mechanism to help determine latency or delay in a connection to the memory.

11. The method of claim 4, wherein providing a parallel feeder component in the front end display logic layer includes implementing the parallel feeder component as a single class with individual instantiation for each query result display entity in the user interface of the computer application.

12. A non-transitory computer-readable storage medium including executable code that, when executed, is configured to cause at least one computer system to host a computer application having a back end business logic layer separate from a front end display logic layer in the computer application and to provide:

a memory to store, query-by-query, individual results of multiple queries directed to business information warehouses or databases by the back end business logic layer of the computer application, each of the multiple queries being a query received by the computer application; and

a parallel feeder component in a front end display logic layer of the computer application, the parallel feeder component being configured with logic to read the individual results of the multiple queries stored in the memory asynchronously or in parallel, and to supply the read individual results of the multiple queries in parallel to a corresponding multiplicity of query result display entities in a user interface of the computer application, wherein the parallel feeder component is implemented as a custom feeder class in contrast to a standard feeder basis class that always reads data serially or sequentially and can populate multiple display entities only serially or sequentially.

13. The non-transitory computer-readable storage medium of claim 12, wherein both the back end business logic layer and the front end display logic layer have access via a service to the memory storing the individual results of multiple queries.

14. The non-transitory computer-readable storage medium of claim 12, wherein the parallel feeder component is configured to asynchronously read, query-by-query, the individual results of the multiple queries stored in the memory, and to supply data to a particular query result display entity in the user interface of the computer application as soon as data for that particular query result display entity becomes available in the memory.

15. The non-transitory computer-readable storage medium of claim 12, wherein the at least one computer system hosting the computer application is an Advanced Business Application Programming (ABAP) system, and wherein the custom feeder class is an ABAP Object Oriented class.

16. The non-transitory computer-readable storage medium of claim 15, wherein the custom feeder class inherits one or more functions from a standard Advanced Business Application Programming (ABAP) feeder basis class.

17. The non-transitory computer-readable storage medium of claim 16, wherein the standard ABAP feeder basis class reads data sequentially and the custom feeder class in contrast implements logic to read data asynchronously.

18. The non-transitory computer-readable storage medium of claim 12, wherein the custom feeder class is coupled to a ping mechanism to help determine latency or delay in a connection to the memory.

19. The non-transitory computer-readable storage medium of claim 12, wherein the custom feeder class is implemented as a single class with individual instantiation for each query result display entity in the user interface of the computer application.

20. The non-transitory computer-readable storage medium of claim 12, wherein the custom feeder class logic is configured to be independent of all specific functionalities of the computer application.