Analytical task invocation

• US 7,694,307 B2
• Filed: 09/18/2003
• Issued: 04/06/2010
• Est. Priority Date: 05/15/2003
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP AG (SAP SE)
• Inventors: Kulkarni, Girish V., Dill, Marcus, Weidner, Jens, Gilg, Sven, Mahabal, Harish Hoskere, V, Manikandan, Roy, Dipankar, Kraiss, Achim, Bhan, Vikas
• Primary Examiner(s): An; Meng-Ai
• Assistant Examiner(s): To; Jennifer N
• Application Number:
  US10/665,249
• Publication Number:
  US 20040230978A1
• Time in Patent Office: 2,392 Days
• Field of Search: 718100-106, 707/2, 707 5- 6, 707/10, 707/101, 707/102, 707/1, 709201-202
• US Class Current: 718/106
• CPC Class Codes: G06Q 30/02 Marketing; Price estimation or determination; Fundraising
• CPC Class Codes: G06Q 99/00 Subject matter not provided for in other groups of this subclass

Abstract

One implementation provides a computer system for invoking execution of analytical tasks in sequence. In this implementation, the computer system is programmed to receive a request to execute an analytical task from a front-end software application, and determine that a first additional analytical task needs to be executed before the requested analytical task. The computer system is then programmed to invoke execution of the first additional analytical task on a first analytical engine. Using information generated from the execution of the first additional analytical task, the computer system is then programmed to invoke execution of the requested analytical task on a second analytical engine.

Claims

1. A computer-implemented method for generating analytical information requested by a front-end software application system, the method comprising:

receiving from a front-end software application system, an electronic request to execute a preconfigured analytical task;

determining, from task definition configuration data that define the preconfigured analytical task, that a predecessor analytical task needs to be executed as part of the preconfigured analytical task;

invoking execution of the predecessor analytical task on a first analytical engine, the first analytical engine being identified by the task definition configuration data, and receiving from the first analytical engine a value for an output field of the predecessor analytical task;

determining, from the task definition configuration data, that a second analytical task needs to be executed as part of the preconfigured analytical task, wherein the second analytical task is a prediction task, the execution of the second analytical task requiring, as an input field, the output field of the predecessor analytical task;

invoking execution of the second analytical task on a second analytical engine, wherein the second analytical engine is a prediction engine, the second analytical engine being identified by the task definition configuration data, sending to the second analytical engine the value for the output field of the predecessor analytical task received from the first analytical engine, and receiving from the second analytical engine a value for an output field of the second analytical task; and

using the value for the output field of the second analytical task to generate an electronic response with analytical information, and sending the electronic response to the front-end software application system.

2. The computer-implemented method of claim 1, wherein the electronic response back to the front-end software application system includes information relating to the execution of the predecessor analytical task and the second analytical task.

3. The computer-implemented method of claim 1, wherein the predecessor analytical task is a key performance indicator (KPI) lookup task, and wherein the first analytical engine is a KPI engine.

4. The computer-implemented method of claim 1, wherein the method further comprises using information contained within the electronic request to select the first analytical engine to be used in executing the predecessor analytical task, and to select the second analytical engine to be used in executing the second analytical task.

5. The computer-implemented method of claim 1, wherein the first analytical engine is located externally from the second analytical engine.

6. The computer-implemented method of claim 1, wherein the method comprises:

determining, from the task definition configuration data, that a second predecessor analytical task needs to be executed before the predecessor analytical task;

invoking execution of the second predecessor analytical task on a third analytical engine, the third analytical engine being identified by the task definition configuration data; and

sending information generated from the execution of the second predecessor analytical task to the first analytical engine for use in the execution of the predecessor analytical task on the first analytical engine.

7. A computer-readable storage medium having computer-executable instructions that when executed by a processor cause a method to be performed, the method comprising:

receiving from a front-end software application system, an electronic request to execute a preconfigured analytical task;

determining, from task definition configuration data that define the preconfigured analytical task, that a predecessor analytical task needs to be executed as part of the preconfigured analytical task;

invoking execution of the predecessor analytical task on a first analytical engine, the first analytical engine being identified by the task definition configuration data, and receiving from the first analytical engine a value for an output field of the predecessor analytical task;

determining, from the task definition configuration data, that a second analytical task needs to be executed as part of the preconfigured analytical task, wherein the second analytical task is a prediction task, the execution of the second analytical task requiring, as an input field, the output field of the predecessor analytical task;

invoking execution of the second analytical task on a second analytical engine, wherein the second analytical engine is a prediction engine, the second analytical engine being identified by the task definition configuration data, sending to the second analytical engine the value for the output field of the predecessor analytical task received from the first analytical engine, and receiving from the second analytical engine a value for an output field of the second analytical task; and

using the value for the output field of the second analytical task to generate an electronic response with analytical information, and sending the electronic response to the front-end software application system.

8. The computer-readable storage medium of claim 7, wherein the electronic response back to the front-end software application system includes information relating to the execution of the predecessor analytical task and the second analytical task.

9. The computer-readable storage medium of claim 7, wherein the predecessor analytical task is a key performance indicator (KPI) lookup task, and wherein the first analytical engine is a KPI engine.

10. The computer-readable storage medium of claim 7, wherein the method further comprises using information contained within the electronic request to select the first analytical engine to be used in executing the predecessor analytical task, and to select the second analytical engine to be used in executing the second analytical task.

11. The computer-readable storage medium of claim 7, wherein the first analytical engine is located externally from the second analytical engine.