Page 1 of 1
ViewExtractSkipConsolidatedStringSet (Cube, ViewName, Flag)
Posted: Tue May 03, 2016 9:16 pm
by mnaithan
Hi
Actually I have one doubt regarding ViewExtractSkipConsolidatedStringSet (Cube, ViewName, Flag), ViewExtractSkipZeroesSet and ViewExtractSkipRuleValuesSet, I am under the impression that these functions can only be used in case we have Cube View as datasource, but recently I was going throught one process having text file as datasource and these functions are used on target cube view ,is it correct...?, I search on IBM documentation as well which says :
This function sets an option to include/exclude zero values in a view and any associated view extracts
So its talking about the extract so I am little bit confused here, appreciate any help
Thanks and regards
Micky
Re: ViewExtractSkipConsolidatedStringSet (Cube, ViewName, Flag)
Posted: Tue May 03, 2016 9:39 pm
by Wim Gielis
Hello Micky,
Irrespective of the data source of a TI process, you can use these functions when creating a view extract.
View extracts can be used as a data source or to zero out a cube view (1 slice of the cube).
So it's perfectly possible that a TI process has a text file as its data source, and the Prolog can do a zero out first -
whereby these functions are used to skip certain cells.
Re: ViewExtractSkipConsolidatedStringSet (Cube, ViewName, Flag)
Posted: Tue May 03, 2016 9:49 pm
by mnaithan
Thanks for reply Wim
Regards
Micky
Re: ViewExtractSkipConsolidatedStringSet (Cube, ViewName, Flag)
Posted: Wed May 04, 2016 1:35 pm
by tomok
Wim is correct but using these settings is pretty much a waste of time when creating a target view in a TI process. There is no need to tell the view to skip zeros when zeroing out a cube because by definition, the function only targets non-zero cells. Also, no need to tell it to skip rule calculated values OR consolidated values during a zero out because the function automatically skips them already. When creating a view for zeroing out you can just leave the defaults for all those those settings except maybe the skipping strings one. I've never used that setting.
Re: ViewExtractSkipConsolidatedStringSet (Cube, ViewName, Flag)
Posted: Thu May 05, 2016 7:37 pm
by mnaithan
Thanks for the reply Tomok, that brings another question that suppose if skip consolidation is off on Target View VIEWEXTRACTSKIPCONSOLIDATEDSTRINGSET (CUBE, VIEWNAME, 0), then I don't think ViewZeroOut going to zero out the consolidated cells ( and value in consolidate cell is entered via rule at C level or from another cube)...?, then in this case these functions holds no significance , kindly correct me if wrong
Regards
Micky
Re: ViewExtractSkipConsolidatedStringSet (Cube, ViewName, Flag)
Posted: Thu May 05, 2016 7:42 pm
by tomok
mnaithan wrote:Thanks for the reply Tomok, that brings another question that suppose if skip consolidation is off on Target View VIEWEXTRACTSKIPCONSOLIDATEDSTRINGSET (CUBE, VIEWNAME, 0), then I don't think ViewZeroOut going to zero out the consolidated cells ( and value in consolidate cell is entered via rule at C level or from another cube)...?, then in this case these functions holds no significance , kindly correct me if wrong
Well, just as the name implies, consolidated cells are the result of the "consolidation" of all the cells that roll up to that point in the hierarchy. When you enter something in a consolidated cell, TM1 breaks the amount back to the individual cells underneath the consolidation. So, you don't need to zero out the consolidation, you need to zero out all the leaf cells that make up the consolidation (and of course any lower level consolidations if the hierarchy has several levels).
It's just like a SUM formula in Excel. If you delete the SUM formula it doesn't delete all the values that were being added up does it? No, and neither does TM1. The only time TM1 will delete all the values underneath a consolidation is when you use the Data Spread right-click functionality in one of the clients to Clear values.
Re: ViewExtractSkipConsolidatedStringSet (Cube, ViewName, Flag)
Posted: Fri May 06, 2016 6:46 am
by lotsaram
What Tomok said, except to add that strings don't consolidate. String data is the exception to this rule as a text value stored on a C element is independent and has no relationship to any text stored against its children or descendants.
This is the reason that the ViewExtractSkipConsolidatedStringSet function was (recently) added. In order to be able to choose when processing string data, whether to include or exclude strings entered against consolidated elements.
Re: ViewExtractSkipConsolidatedStringSet (Cube, ViewName, Flag)
Posted: Fri May 06, 2016 6:55 am
by Wim Gielis
Very true.
In fact I prefer to use the 4 ViewExtract functions in any view, even though 3 out of 4 (and probably 4 out of 4) are not very useful in ZeroOut views.
It's just more consistent and allows for easier copy/paste or reusing code.
You only need to see that they are all on skip flag = 1 for a regular zero out.