Reuse of business logic of reports as data sources

• US 7,899,841 B2
• Filed: 08/07/2007
• Issued: 03/01/2011
• Est. Priority Date: 08/07/2007
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP AG (SAP SE)
• Inventors: Otter, Wolfgang, Schneider, Faiko, Raasch, Ingo, Braun, Michelle
• Primary Examiner(s): CHANNAVAJJALA, SRIRAMA T
• Application Number:
  US11/835,278
• Publication Number:
  US 20090043735A1
• Time in Patent Office: 1,302 Days
• Field of Search: 707/1, 707/3, 707 5- 6, 707/100, 707/102, 707/103.Z, 707/200, 707/600, 707/694, 707/702, 707/703, 707/756, 707/791, 707/802, 707804-805, 707/810, 707/759, 707/769, 707/796
• US Class Current: 707/769
• CPC Class Codes: G06F 16/24524 Access plan code generation and invalidation; Reuse of access plans

Abstract

An InfoSet API calls a query, the call defining selections for data retrieval. These selections are passed by the query to a report, which obtains data responsive to the selections via a data source. The obtained data is persisted in a global memory which allows such data to be accessed in multiple sessions. The persisted data is retrieved from the global memory by the query which in turns provides such data in response to the InfoSet API call. Techniques for automatically creating aspects of Infosets are also described as well as other related techniques, apparatus, systems, and articles.

Claims

1. An article comprising a tangible machine-readable storing medium embodying instructions that when performed by one or more machines result in operations comprising:

calling, using a call by a first user interface using an application programming interface, a query, the call defining selections for data retrieval;

passing, by a first business logic component of the query, the selections to a report, the report comprising a previously generated report or report transaction, the passing of the selections by the query to the report being representative of a dark call of the report, the dark call comprising selections from a query rather than selections being specified on a second user interface that can directly call the report without calling an intermediate query between the second user interface and the report;

obtaining, by a second business logic component of the report and from a data source, data in response to receipt of the selections from the query;

persisting the obtained data in a global memory, the global memory persisting the data to enable access of the data by queries in multiple sessions;

retrieving, by the first business logic component of the query and from the global memory, the persisted data; and

responding, by the query, to the call with the persisted data retrieved from the global memory;

displaying the responded retrieved data at the first user interface,

wherein the second business logic component remains unchanged when the first user interface is modified.

2. An article as in claim 1, wherein:

the report is an advanced business application programming (ABAP) report; and

the modification occurs to make the user interface compatible with a new operating system.

3. An article as in claim 1, wherein:

the call bypasses a selection handling component in the query;

the query comprises a first selection handling component, the first business logic component, and a first presentation component; and

the report comprises a second selection handling component, the second business logic component, and a second presentation component.

4. An article as in claim 1, wherein the article embodies further instructions that when performed by one or more machines result in operations comprising:

presenting, to a user and in response to the call, the retrieved persisted data.

5. An article as in claim 1, wherein the article embodies further instructions that when performed by one or more machines result in operations comprising:

defining a structure in a data dictionary that characterizes the data is to be presented by the report;

defining an InfoSet that encapsulates the report based on the structure;

automatically defining, based on the defined InfoSet, the query such that the query contains all fields of the InfoSet,

wherein the calling of the query processes only the first business logic of the query while the application programming interface provides the selections rather than the selections being provided by a user interface associated with the query, and

wherein the report is a pre-defined report.

6. An article as in claim 5, wherein the application programming interface for the InfoSet uses a data dictionary to characterize how the data is to be presented in the report.

7. An article as in claim 1, wherein the application programming interface provides metadata of the report and execution of business logic.

8. A method for implementation by one or more data processors comprising:

calling, using a call by an application programming interface using at least one data processor, a query, the call defining selections for data retrieval;

passing, by a first data retrieval component of the query using at least one data processor, the selections to a report, the report comprising a previously generated report or report transaction;

obtaining, by a second data retrieval component of the report and from a data source and using at least one data processor, data in response to receipt of the selections from the query;

persisting the obtained data in a global memory, the global memory persisting the data to enable access of the data by queries in multiple sessions;

retrieving, by the first data retrieval component of the query and from the global memory and using at least one data processor, the persisted data; and

responding, by the query using at least one data processor, to the API call with the persisted data retrieved from the global memory,

wherein the second data retrieval component remains unchanged irrespective of a modification of a user interface displaying the retrieved data, the modification of the user interface occurring when an operating system associated with the user interface is changed.

9. A method as in claim 8, wherein the report is an ABAP report.

10. A method as in claim 8, wherein the call bypasses a selection handling component in the query.

11. A method as in claim 8, further comprising:

presenting, by at least one data processor, data responsive to the call to a user.

12. A method as in claim 8, wherein the application programm interface is for an InfoSet.

13. A method as in claim 8, wherein the InfoSet application programming interface uses a data dictionary to characterize how the data is to be presented in the report.

14. A method as in claim 8, wherein the application programming interface provides metadata of the report and execution of business logic.

15. A method for implementation by one or more data processors comprising:

initiating, by at least one data processor, execution of a report, the output of the report being pre-defined and based on provided selections, data responsive to the provided selections being displayed using a first user interface, the report comprising a second selection handling component, the second business logic component, and a second presentation component;

computing, by at least one data processor, automated list viewer (ALV). metadata during execution of the report;

deleting, by at least one data processor, ALV metadata to suppress presentation of an associated result list;

generating, by at least one data processor, a structure for an InfoSet based on remaining non-deleted ALV metadata;

generating, by at least one data processor, suggestions for the InfoSet based on the generated structure and an analysis of a selection screen of the report;

generating, by at least one data processor, the InfoSet based on the generated structure and the generated suggestions; and

generating, by at least one data processor, a query displaying all fields of the InfoSet, the query comprising a first selection handling component, the first business logic component, and a first presentation component,

wherein the provided selections are passed by the query to the report via a dark call such that the provided selections are directly provided to the report by the query rather than the provided selections being specified on a user interface that directly passes the provided selections to the report without passing the provided selections via an intermediate query between the second user interface and the report, and

wherein the second business logic component remains unchanged when the first user interface is modified to be compatible with a new operating system.

16. A method for encapsulating an a pre-defined report by an InfoSet, the method being implemented by one or more data processors and comprising:

defining, by at least one data processor, a structure in a data dictionary that characterizes data presented by the pre-defined report, the report comprising a second selection handling component, the second business logic component, and a second presentation component;

defining, by at least one data processor, the InfoSet that encapsulates the pre-defined report based on the structure;

defining, by at least one data processor, a query that contains all fields of the InfoSet, the query comprising a first selection handling component, the first business logic component, and a first presentation component; and

calling, by at least one data processor, the query via an application programming interface (API) of the InfoSet so that only data retrieval is processed,

wherein the second data retrieval component remains unchanged irrespective of a modification of a user interface displaying the retrieved data, the modification of the user interface occurring when an operating system associated with the user interface is changed.

17. A method as in claim 16, wherein the data presented by the pre-defined report is presented via an Automated List Viewer (ALV);

wherein the InfoSet is defined such that;

selections of the InfoSet are collected in a selection table;

a special call mode for the ALV is set in memory;

the selected table is transferred to the pre-defined report;

the ALV stores result data in the memory and does not visualize the result data; and

data is retrieved from the memory and stored in an internal table of the defined structure after the report is called.