The OneStream Community is temporarily frozen until June 29th due to the ongoing maintenance. Please read the blog post here to learn more.
Forum Discussion
Solved
Hybrid Source Scenarios - Additional Documentation / Details
One of the new features in the 6.6 release is the introduction of Hybrid Source Scenarios. I've watched the 6.6 release and read through the abbreviated examples in the admin guide. Both have good h...
Hello - I am going to ask that more documentation around the Options are added to the documentation. Below is more detail on the Options:
- ExecuteCopyDuringCalc - this is a True/False setting and by default it is set to True. This would only be used with the 2 Copy binding types and not the Share binding type. Having this setting as True indicates that the copy will execute during the Data Unit Calculation Sequence (DUCS). Or in other words, anytime you calculate a Data Unit the copy will execute. Making this setting False, you would need to use a Data Management Job to execute the Hybrid Source Data Copy. On a DM Step, there is a new setting called "Execute Scenario Hybrid Source Data Copy". You would make this True and then the Calculation defined on this step would use the settings from the Hybrid Source Data properties to run the Copy. This would NOT run during the DUCS and be a "point in time" calculation. Use cases for this may be versioning or seeding where constant copying of the same numbers would be unnecessary overhead on every calculation.
- CopyAsDurableData - this is a True/False setting and by default it is set to False. This would only be used with the 2 Copy binding types and not the Share binding type. By default, copied data is stored as calculated. Set this to true to flag this data as durable. Calculated data is cleared by OS at the beginning of the DUCS (if the scenario setting is set to True) and will re-calculate. Durable data is NOT cleared by OS at the beginning of the DUCS and must be cleared via a rule. These 2 settings go hand in hand. Likely, if you have ExecuteCopyDuringCalc as True, CopyAsDurableData would be False. And vice versa.
- RemoveZeros - this will remove zeros for the copied data. This is only if all periods of the intersection being copied are 0.
- SourceTimePeriodForYearlyResult - this is used when the Input Frequency of the target scenario is Yearly and the source scenario is an Input Frequency that is more granular. It is used for performance reasons to only share or copy one time period to the target scenario which limits the Data Unit size and will improve calculation and/or query performance.
- SourceViewForYearlyResult - use in conjunction with the setting above, this can either be Period/YTD. For the time period being copied/shared you can choose whether you want to copy/share the Periodic or YTD value.
- ExecuteCopyDuringCalc - this is a True/False setting and by default it is set to True. This would only be used with the 2 Copy binding types and not the Share binding type. Having this setting as True indicates that the copy will execute during the Data Unit Calculation Sequence (DUCS). Or in other words, anytime you calculate a Data Unit the copy will execute. Making this setting False, you would need to use a Data Management Job to execute the Hybrid Source Data Copy. On a DM Step, there is a new setting called "Execute Scenario Hybrid Source Data Copy". You would make this True and then the Calculation defined on this step would use the settings from the Hybrid Source Data properties to run the Copy. This would NOT run during the DUCS and be a "point in time" calculation. Use cases for this may be versioning or seeding where constant copying of the same numbers would be unnecessary overhead on every calculation.
EricOsmanski
OneStream Employee
OneStream EmployeeHello - I am going to ask that more documentation around the Options are added to the documentation. Below is more detail on the Options:
- ExecuteCopyDuringCalc - this is a True/False setting and by default it is set to True. This would only be used with the 2 Copy binding types and not the Share binding type. Having this setting as True indicates that the copy will execute during the Data Unit Calculation Sequence (DUCS). Or in other words, anytime you calculate a Data Unit the copy will execute. Making this setting False, you would need to use a Data Management Job to execute the Hybrid Source Data Copy. On a DM Step, there is a new setting called "Execute Scenario Hybrid Source Data Copy". You would make this True and then the Calculation defined on this step would use the settings from the Hybrid Source Data properties to run the Copy. This would NOT run during the DUCS and be a "point in time" calculation. Use cases for this may be versioning or seeding where constant copying of the same numbers would be unnecessary overhead on every calculation.
- CopyAsDurableData - this is a True/False setting and by default it is set to False. This would only be used with the 2 Copy binding types and not the Share binding type. By default, copied data is stored as calculated. Set this to true to flag this data as durable. Calculated data is cleared by OS at the beginning of the DUCS (if the scenario setting is set to True) and will re-calculate. Durable data is NOT cleared by OS at the beginning of the DUCS and must be cleared via a rule. These 2 settings go hand in hand. Likely, if you have ExecuteCopyDuringCalc as True, CopyAsDurableData would be False. And vice versa.
- RemoveZeros - this will remove zeros for the copied data. This is only if all periods of the intersection being copied are 0.
- SourceTimePeriodForYearlyResult - this is used when the Input Frequency of the target scenario is Yearly and the source scenario is an Input Frequency that is more granular. It is used for performance reasons to only share or copy one time period to the target scenario which limits the Data Unit size and will improve calculation and/or query performance.
- SourceViewForYearlyResult - use in conjunction with the setting above, this can either be Period/YTD. For the time period being copied/shared you can choose whether you want to copy/share the Periodic or YTD value.
Hey Eric - thanks for the above, and additional questions:
I was experimenting with Hybrid Copies, and I'd like to only pull over some data from upper level Entities from some Actual months into a Forecast.
In regard to the Entity dimension, it only seemed to pull over data when I had Base Entities as part of my calculation filter. When I tried to pull upper levels alone it would not bring over the data (this is certainly consistent with the setting name of 'Copy Input Data...').
Also I tried to limit the T# Time Periods with a Member Filter (only some for a Year) and it seemed like this was ignored.
- Are there any ways to do the non-Base Entity and Time limitations with Hybrid copies?
- Do the Member Filters only apply to the non-Data Unit dimensions?
Thank you!
- EricOsmanski
That is correct - the member filters on Hybrid Source data are only Account-level dimensions. Data Unit dimensions are invalid. DU dimensions would be supplied when a calc/trans/cons is ran.
(thank you very much Eric!)