Actual and Forecast load

[BariAbdul]

We have a requirement that Forecast will only be loaded when actual of that month is present in the cube otherwise forecast data shouldn't be loaded. I am sure i have went through similar post but couldn't find it when i needed.Any help will be highly appreciated.Thanks

[Alan Kirk]

We have a requirement that Forecast will only be loaded when actual of that month is present in the cube otherwise forecast data shouldn't be loaded. I am sure i have went through similar post but couldn't find it when i needed.Any help will be highly appreciated.Thanks

More information needed. For example:
- What is the source of the forecast? Another cube, an external system, what? If there is an option to exclude the Actuals period data from the source, so much the better since you won't need to iterate through a whole bunch of rows that you don't want to load. If, for example, the source is a cube view then you could iterate through all of the months to check whether there is Actuals data (by looking at high level consolidations), and include only the months where there is such data in the subset that you use to define the view for your data source. If it's from a SQL query you could use parameters to dynamically modify the query to pull only the records that fall into the Actuals period.
- If that's not an option, is the forecast data ordered by time? If so you could determine the cut-off month, and as soon as you reach the following month quit the process that's doing the loading.

[BariAbdul]

Thanks,Alan.The Actual are coming from EDW and loaded in to the cube by Finance guys monthly.

[tomok]

it depends on what your definition of when actual of that month is present in the cube. If it simply means there is data in the Actual version, i.e., not zero, then it could be a simple as running a CellGetN function against a consolidated node at the top of the house in the prolog of the forecast load process and doing a ProcessQuit if the function returns 0. If it means something else like Actual is fully loaded and correct how would an automated process know something like that? in this case you may need to put a flag in a control cube that says Actuals are loaded and correct. Your forecast load process can CellGetS against this control cube and terminate, or continue, based on this flag.