<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Actual vs Target(Budget ) -- Different Granularity in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/Actual-vs-Target-Budget-Different-Granularity/m-p/761464#M270828</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks ,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This really should work&amp;nbsp; for the case 1.&amp;nbsp; additional question ,&amp;nbsp; Is it a kind of common technique in qlik or BI world ?&amp;nbsp; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 18 Dec 2014 18:00:20 GMT</pubDate>
    <dc:creator />
    <dc:date>2014-12-18T18:00:20Z</dc:date>
    <item>
      <title>Actual vs Target(Budget ) -- Different Granularity</title>
      <link>https://community.qlik.com/t5/QlikView/Actual-vs-Target-Budget-Different-Granularity/m-p/761461#M270825</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I see many topic of related mixed-Granularity ( especially &lt;A href="https://community.qlik.com/qlik-blogpost/2819"&gt;Fact Table with Mixed Granularity&lt;/A&gt; )&amp;nbsp; .&amp;nbsp;&amp;nbsp; &lt;/P&gt;&lt;P&gt;they are all helpful but not 100% match with my situation. So would like have some advice from here.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here I have two specific situation, I would like to highlight .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;&lt;SPAN style="text-decoration: underline;"&gt;&lt;STRONG&gt;Different Granuality of Target&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN style="text-decoration: underline;"&gt;&lt;STRONG&gt;Consolidated Target&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #575757; text-decoration: underline;"&gt;&lt;STRONG&gt;1st&amp;nbsp;&amp;nbsp; Different ( more than one ) Granuality of Target&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My actual data&amp;nbsp; is like&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Region&lt;/P&gt;&lt;P&gt;&amp;nbsp; │&lt;/P&gt;&lt;P&gt;&amp;nbsp; └→ Business Unit &lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; │&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; └───Area&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We have two different level of Target data&amp;nbsp; one is&amp;nbsp;&amp;nbsp; Region, the other is Region-Area &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Target 1.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Region only&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;SPAN style="font-size: 10pt; line-height: 1.5em;"&gt;Target 2.&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt; line-height: 1.5em;"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Region&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;　　　　&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; │&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 　　　　└→ Area&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;actual&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt; line-height: 1.5em;"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Business Unit&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; │&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; └→ Area&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The user requirement is that , on a same chart&amp;nbsp; ( example is pivot )&lt;/P&gt;&lt;P&gt;&lt;STRONG style="font-size: 10pt; line-height: 1.5em;"&gt;case 1&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;when user select Region + Area ,&amp;nbsp; they need to compare&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Area Sum of Actual&amp;nbsp; vs&amp;nbsp; Region-Area Target&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;case 2&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;when user select only Region (btw region is "always select one value " )&amp;nbsp; , they need to compare&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt; line-height: 1.5em;"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Regional Sum of Actual&amp;nbsp; vs&amp;nbsp; Region Target&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I tried to put both those target into same fact table as actual data and distinguish by type ( actual , target_region, target_region_area )In attached example , &lt;STRONG&gt;case 1&lt;/STRONG&gt; works fine as&amp;nbsp; when user select both Region and Area , qlikview filter and get only one target.&lt;/P&gt;&lt;P&gt;&lt;IMG class="jive-image image-2" src="https://community.qlik.com/legacyfs/online/73838_pastedImage_158.png" style="max-width: 1200px; max-height: 900px;" /&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But &lt;STRONG&gt;case 2&lt;/STRONG&gt; when user select only "region" ,we can see target for both target_region and target_region_area&amp;nbsp; .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG class="image-1 jive-image" src="https://community.qlik.com/legacyfs/online/73819_pastedImage_155.png" style="max-width: 1200px; max-height: 900px;" /&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;as one of the solution, I can&amp;nbsp; use if condition&amp;nbsp; based on what is selected like below , but it is not preferable .&amp;nbsp;&amp;nbsp; &lt;/P&gt;&lt;P&gt;Can any one advise how I should handle this situation ?&amp;nbsp; I don't even know if the "concentrated fact" is right decision or not , any suggestion is greatly appreciated.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Target Fomula&lt;/P&gt;&lt;P&gt;&amp;nbsp; --&amp;gt;&amp;nbsp; if(GetSelectedCount(Area)&amp;gt;0,sum({&amp;lt;Type={'Target_Region_Area'}&amp;gt;}amount) , sum({&amp;lt;Type={'Target_Region'}&amp;gt;}amount))&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="text-decoration: underline;"&gt;&lt;STRONG&gt;2nd&amp;nbsp; Consoliated Target&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We have regional target and Global target.&amp;nbsp;&amp;nbsp; If we stick to "concentrated fact" and keep all level ( region, Business Unit , Area ) in a fact table.Certain fact data will be stored more than one time.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ie )&amp;nbsp; USA is included in both "Global" and "North America"&amp;nbsp; , so all USA data appears both under "Global" and "North America" .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In example , I put&amp;nbsp; all level into a fact table which is easy to handle ,but concern is data size.&amp;nbsp; example is oversimple and do not have&amp;nbsp; many data ,but actual data can be more than Billion "actual" rows which may cause any issue like performance.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;can anyone please advise how I should handle this from data model point of view ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Ko&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 18 Dec 2014 16:23:54 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Actual-vs-Target-Budget-Different-Granularity/m-p/761461#M270825</guid>
      <dc:creator />
      <dc:date>2014-12-18T16:23:54Z</dc:date>
    </item>
    <item>
      <title>Re: Actual vs Target(Budget ) -- Different Granularity</title>
      <link>https://community.qlik.com/t5/QlikView/Actual-vs-Target-Budget-Different-Granularity/m-p/761462#M270826</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;forgot attachments.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 18 Dec 2014 16:29:07 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Actual-vs-Target-Budget-Different-Granularity/m-p/761462#M270826</guid>
      <dc:creator />
      <dc:date>2014-12-18T16:29:07Z</dc:date>
    </item>
    <item>
      <title>Re: Actual vs Target(Budget ) -- Different Granularity</title>
      <link>https://community.qlik.com/t5/QlikView/Actual-vs-Target-Budget-Different-Granularity/m-p/761463#M270827</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Koichi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It looks like you have an overall region target that is greater than the individual breakdown, presumably a floating overall target. One idea could be to make you region target more of a region topup target, instead of the overall number. Which would allow you to use the combination of the 2 for your overall region target but still be able to breakdown to the specific region ones.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I've just adjusted your target for North America in the excel, you have the option of doing this change in your source data (preferable) or if required can be done in QV by grouping up the area specific target into the region and netting the result.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;(not had a chance t look at no.2 yet sorry)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope that helps&lt;/P&gt;&lt;P&gt;Joe&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 18 Dec 2014 17:24:30 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Actual-vs-Target-Budget-Different-Granularity/m-p/761463#M270827</guid>
      <dc:creator />
      <dc:date>2014-12-18T17:24:30Z</dc:date>
    </item>
    <item>
      <title>Re: Actual vs Target(Budget ) -- Different Granularity</title>
      <link>https://community.qlik.com/t5/QlikView/Actual-vs-Target-Budget-Different-Granularity/m-p/761464#M270828</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks ,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This really should work&amp;nbsp; for the case 1.&amp;nbsp; additional question ,&amp;nbsp; Is it a kind of common technique in qlik or BI world ?&amp;nbsp; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 18 Dec 2014 18:00:20 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Actual-vs-Target-Budget-Different-Granularity/m-p/761464#M270828</guid>
      <dc:creator />
      <dc:date>2014-12-18T18:00:20Z</dc:date>
    </item>
  </channel>
</rss>

