<?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: Insight in stocklevels in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/Insight-in-stocklevels/m-p/1546836#M745592</link>
    <description>&lt;P&gt;You could create reference dates: &lt;A href="https://community.qlik.com/t5/Qlik-Design-Blog/Creating-Reference-Dates-for-Intervals/ba-p/1463944" target="_blank"&gt;https://community.qlik.com/t5/Qlik-Design-Blog/Creating-Reference-Dates-for-Intervals/ba-p/1463944&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Or&amp;nbsp; you could create an AsOf table: &lt;A href="https://community.qlik.com/t5/Qlik-Design-Blog/The-As-Of-Table/ba-p/1466130" target="_blank"&gt;https://community.qlik.com/t5/Qlik-Design-Blog/The-As-Of-Table/ba-p/1466130&lt;/A&gt;&lt;/P&gt;&lt;P&gt;The first is probably easier to understand and work with. But if you have a large fact table it could increase the amount of data a lot. The As-Of table might perform better with a large fact table.&lt;/P&gt;</description>
    <pubDate>Wed, 20 Feb 2019 11:21:26 GMT</pubDate>
    <dc:creator>Gysbert_Wassenaar</dc:creator>
    <dc:date>2019-02-20T11:21:26Z</dc:date>
    <item>
      <title>Insight in stocklevels</title>
      <link>https://community.qlik.com/t5/QlikView/Insight-in-stocklevels/m-p/1546800#M745591</link>
      <description>&lt;P&gt;Hello experts,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I need to make a report in which we can see our current, and stock levels from the past. I did some research in our database en the best table to use is a table with stock mutations.&lt;/P&gt;&lt;P&gt;All stock is kept on a carrier. Carriers are unique values on which mutations are registered. In the example below you see two mutations on 1 carrier. The first mutation is the stock coming in, the second mutation is stock going out. In between it is possible that there is a correction en movement to a different storage location.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Qlik example.jpg" style="width: 999px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/6401iCCA4D8EFD540226D/image-size/large?v=v2&amp;amp;px=999" role="button" title="Qlik example.jpg" alt="Qlik example.jpg" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;In the example i have two dates. A date in and a date out. In between i want to make dates. On each date it also needs to make the quantity (e.g. on 12-10-2018 quantity = 6, on 25-10-2018 quantity = 0), and count the carrier because it is in stock (after date out the carrier is also out of stock). Via this way i think it is possible to report stocklevels for each customer, per Warehouse, per article.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;In the appendix you'll find the script.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Can someone help me with this?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 16 Nov 2024 21:22:42 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Insight-in-stocklevels/m-p/1546800#M745591</guid>
      <dc:creator>tomgrouwe</dc:creator>
      <dc:date>2024-11-16T21:22:42Z</dc:date>
    </item>
    <item>
      <title>Re: Insight in stocklevels</title>
      <link>https://community.qlik.com/t5/QlikView/Insight-in-stocklevels/m-p/1546836#M745592</link>
      <description>&lt;P&gt;You could create reference dates: &lt;A href="https://community.qlik.com/t5/Qlik-Design-Blog/Creating-Reference-Dates-for-Intervals/ba-p/1463944" target="_blank"&gt;https://community.qlik.com/t5/Qlik-Design-Blog/Creating-Reference-Dates-for-Intervals/ba-p/1463944&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Or&amp;nbsp; you could create an AsOf table: &lt;A href="https://community.qlik.com/t5/Qlik-Design-Blog/The-As-Of-Table/ba-p/1466130" target="_blank"&gt;https://community.qlik.com/t5/Qlik-Design-Blog/The-As-Of-Table/ba-p/1466130&lt;/A&gt;&lt;/P&gt;&lt;P&gt;The first is probably easier to understand and work with. But if you have a large fact table it could increase the amount of data a lot. The As-Of table might perform better with a large fact table.&lt;/P&gt;</description>
      <pubDate>Wed, 20 Feb 2019 11:21:26 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Insight-in-stocklevels/m-p/1546836#M745592</guid>
      <dc:creator>Gysbert_Wassenaar</dc:creator>
      <dc:date>2019-02-20T11:21:26Z</dc:date>
    </item>
  </channel>
</rss>

