Forecasting method, system and machine readable storage medium for the selection between asynchronous or synchronous forecasting based on event criteria

• US 9,760,844 B2
• Filed: 07/14/2014
• Issued: 09/12/2017
• Est. Priority Date: 10/04/2006
• Status: Active Grant

• Current Assignee: Salesforce.com, Inc.
• Original Assignee: Salesforce.com, Inc.
• Inventors: Doshi, Kedar, Fischer, Mark, Chou, Evan
• Primary Examiner(s): Gart, Matthew
• Assistant Examiner(s): Swartz, Stephen S
• Application Number:
  US14/331,095
• Publication Number:
  US 20140324540A1
• Time in Patent Office: 1,156 Days
• CPC Class Codes: G06Q 10/04 Forecasting or optimisation specially adapted for administrative or management purposes, e.g. linear programming or "cutting stock problem" market predictions or forecasting for commercial activities G06Q30/0202
• CPC Class Codes: G06Q 10/0639 Performance analysis of employees; Performance analysis of enterprise or organisation operations
• CPC Class Codes: G06Q 30/0202 Market predictions or forecasting for commercial activities

Abstract

In accordance with embodiments, there are provided mechanisms and methods for selecting a synchronous or asynchronous process to determine a forecast. These mechanisms and methods for such synchronous/asynchronous process selection can enable embodiments to determine forecasts for multiple users (e.g. with hierarchical relationships, etc.) over an arbitrary time interval. The ability of embodiments to provide forecasts that involve such a large amount of data in an effective way can enable forecasting that was otherwise infeasible due to resource limitations.

Claims

1. A method comprising:

identifying an event for processing in a database environment having at least one hardware processing component coupled with at least one hardware memory device, wherein the event comprises modifications to data or metadata that have a potential to affect a forecast and each of the events having potential to affect the forecast are classified into either a first portion or a second portion, wherein the first portion corresponds to events that involve data modifications and the second portion corresponds to metadata changes;

directing the identified event to processing, with the hardware processing component, wherein directing the event to processing includes automatically selecting one or more of the following;

processing the event synchronously with the at least one hardware processing component if the event is classified in the first portion;

or

queuing the event in a queue maintained in a physical memory device for processing asynchronously with the at least one hardware processing component if the event is classified in the second portion; and

managing processing the event within the database environment with the hardware processing component using the selected process, wherein the processing of the event including generating the forecast;

wherein the selection of synchronous processing or asynchronous processing for the event is based on application of specified criteria for selection of processing.

2. The method of claim 1, wherein the criteria for selection of processing includes selecting processing of the event synchronously for a data event that affects data for the forecast.

3. The method of claim 2, wherein the data event involves addition, removal, or modification of data that may potentially affect the forecast.

4. The method of claim 1, wherein the criteria for selection of processing includes selecting queuing the event for processing asynchronously for an event that affects a set-up function for the forecast or associated metadata.

5. The method of claim 4, wherein the metadata includes metadata to categorize or describe data for the forecast.

6. The method of claim 4, wherein an event affecting the metadata includes one or more of a forecast hierarchy change, a forecast period setting, and a forecast dimension setting.

7. The method of claim 1, further comprising setting the criteria for selection of processing based on a user configuration.

8. The method of claim 1, wherein generating the forecast includes identifying a forecast difference amount, and applying the forecast difference amount to a previous forecast amount.

9. The method of claim 8, further comprising maintain the forecast as a set of contributing previous forecasts, wherein generating the forecast includes recalculating one or more previous forecasts that are affected by the event.

10. The method of claim 1, wherein the synchronous processing or asynchronous processing is performed on data stored in a multi-tenant database system.

11. The method of claim 1, wherein the forecast includes one or more of:

a sales forecast;

a planning forecast;

a routing or transportation forecasts;

a material requirements forecasts;

a manufacturing forecast;

a spending forecast;

a budget forecast;

or

a scheduling forecast.

12. The method of claim 1, wherein generating the forecast includes taking into account a level of commitment for the event.

13. The method of claim 12, wherein generating the forecast includes excluding certain forecast amounts or estimates based on the level of commitment for the event.

14. The method of claim 12, wherein taking into account the level of commitment for the event includes comparing the level of commitment for the event with a user-configured level threshold.

15. A database system providing database service having at least one hardware processor coupled with at least one hardware data storage device, comprising:

the hardware data storage for user data; and

the hardware processor to process events; and

wherein the database service provided by the database system includes;

identifying an event for processing in a database environment, wherein the event comprises modifications to data or metadata that have a potential to affect a forecast and each of the events having potential to affect the forecast are classified into either a first portion or a second portion, wherein the first portion corresponds to events that involve data modifications and the second portion corresponds to metadata changes;

directing the identified event to processing, with the hardware processing component, wherein directing the event to processing includes automatically selecting one or more of the following;

processing the event synchronously with the hardware processor if the event is classified in the first portion;

or

queuing the event in a queue maintained in a physical memory device for processing asynchronously with the hardware processor if the event is classified in the first portion; and

managing processing the event within the database environment with the hardware processing component using the selected process, wherein the processing of the event including generating the forecast;

wherein the selection of synchronous processing or asynchronous processing for the event is based on application of specified criteria for selection of processing.

16. The system of claim 15, wherein the criteria for selection of processing includes selecting processing of the event synchronously for a data event that affects data for the forecast.

17. The system of claim 16, wherein the data event involves addition, removal, or modification of data that may potentially affect the forecast.

18. The system of claim 15, wherein the criteria for selection of processing includes selecting queuing the event for processing asynchronously for an event that affects a set-up function for the forecast or associated metadata.

19. The system of claim 15, wherein the metadata includes metadata to categorize or describe data for the forecast.

20. The system of claim 15, wherein an event affecting the metadata includes one or more of a forecast hierarchy change, a forecast period setting, or a forecast dimension setting.

21. The system of claim 15, wherein the criteria for selection of processing are configurable by a user.

22. A machine-readable storage medium having stored thereon data representing sequences of instructions that, when executed by a hardware processor, cause the hardware processor to perform operations comprising:

identifying an event for processing in a database environment having at least one hardware processor coupled with at least one hardware data storage device, wherein the event comprises modifications to data or metadata that have a potential to affect a forecast and each of the events having potential to affect the forecast are classified into either a first portion or a second portion, wherein the first portion corresponds to events that involve data modifications and the second portion corresponds to metadata changes;

directing the identified event to processing, with the hardware processing component, wherein directing the event to processing includes automatically selecting one or more of the following;

processing the event synchronously with the hardware processor if the event is classified in the first portion;

or

queuing the event in a queue maintained in a physical memory device for processing asynchronously with the hardware processor if the event is classified in the first portion; and

managing processing the event within the database environment with the hardware processing component using the selected process, wherein the processing of the event including updating the prediction;

wherein the selection of synchronous processing or asynchronous processing for the event is based on application of specified criteria for selection of processing.

23. The medium of claim 22, wherein the criteria for selection of processing includes selecting processing of the event synchronously for a data event that affects data for the prediction.

24. The medium of claim 22, wherein the criteria for selection of processing includes selecting queuing the event for processing asynchronously for an event that affects a set-up function for the prediction or associated metadata.

25. The medium of claim 22, further comprising instructions that, when executed by the processor, cause the processor to perform operations comprising:

setting the criteria for selection of processing based on a user configuration.