<?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 Lower level details information in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/Lower-level-details-information/m-p/172972#M42335</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I have a model which shows shortages on Production lines.I am able to calculate the shortages and it works wonderfully for the&lt;BR /&gt;purchased parts. So basically if a MO is short of a Purchased part..&lt;BR /&gt;its shows the relevant information about PO which helps. I am getting&lt;BR /&gt;stuck at the Manufactured parts level.&lt;BR /&gt;If a MO part is short of Manufactured part..I want qlikview to be able&lt;BR /&gt;to do a recursive call to the MO file and find the MO details&lt;BR /&gt;regarding this component which is short.&lt;/P&gt;&lt;P&gt;The Momast is the manufacturing order master file containing order number,&lt;BR /&gt;top level item number which is FITEM, planner and the scheduled start date.&lt;BR /&gt;This file relates to MOdata which is the mnf component file.&lt;BR /&gt;It contains all the components (CITEM) required to make the top level MO item.&lt;BR /&gt;Which I have related again to MOMAST to get the order details for these components.&lt;BR /&gt;Hence giving info for two levels down. What I want to achieve is for this to blow down to the bottom.&lt;BR /&gt;ITEMBL file helps us giving the on hand quantity MOHTQ.&lt;BR /&gt;POITEM is the purchase order file giving relevant info about the purchase parts identified by LTCOD 'P' or 'M'.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;For example, if I choose FItem(Top Level Part) 5002227, it shows components which are short-in red, one component being 200813(lower level). - This is perfect. But if we clear all and select 200813 as the Top Level Part, we see that component 200813 has further component shortages(going to an even lower level).&lt;/STRONG&gt; &lt;STRONG&gt;I want to be able to show these without having to clear Top Level Part and selecting 200813.&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;I've attached a sample of the .qvw&lt;/P&gt;&lt;P&gt;Any help would be greatly appreciated!&lt;/P&gt;&lt;P&gt;Xena&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 09 Mar 2010 15:25:21 GMT</pubDate>
    <dc:creator />
    <dc:date>2010-03-09T15:25:21Z</dc:date>
    <item>
      <title>Lower level details information</title>
      <link>https://community.qlik.com/t5/QlikView/Lower-level-details-information/m-p/172972#M42335</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I have a model which shows shortages on Production lines.I am able to calculate the shortages and it works wonderfully for the&lt;BR /&gt;purchased parts. So basically if a MO is short of a Purchased part..&lt;BR /&gt;its shows the relevant information about PO which helps. I am getting&lt;BR /&gt;stuck at the Manufactured parts level.&lt;BR /&gt;If a MO part is short of Manufactured part..I want qlikview to be able&lt;BR /&gt;to do a recursive call to the MO file and find the MO details&lt;BR /&gt;regarding this component which is short.&lt;/P&gt;&lt;P&gt;The Momast is the manufacturing order master file containing order number,&lt;BR /&gt;top level item number which is FITEM, planner and the scheduled start date.&lt;BR /&gt;This file relates to MOdata which is the mnf component file.&lt;BR /&gt;It contains all the components (CITEM) required to make the top level MO item.&lt;BR /&gt;Which I have related again to MOMAST to get the order details for these components.&lt;BR /&gt;Hence giving info for two levels down. What I want to achieve is for this to blow down to the bottom.&lt;BR /&gt;ITEMBL file helps us giving the on hand quantity MOHTQ.&lt;BR /&gt;POITEM is the purchase order file giving relevant info about the purchase parts identified by LTCOD 'P' or 'M'.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;For example, if I choose FItem(Top Level Part) 5002227, it shows components which are short-in red, one component being 200813(lower level). - This is perfect. But if we clear all and select 200813 as the Top Level Part, we see that component 200813 has further component shortages(going to an even lower level).&lt;/STRONG&gt; &lt;STRONG&gt;I want to be able to show these without having to clear Top Level Part and selecting 200813.&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;I've attached a sample of the .qvw&lt;/P&gt;&lt;P&gt;Any help would be greatly appreciated!&lt;/P&gt;&lt;P&gt;Xena&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 09 Mar 2010 15:25:21 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Lower-level-details-information/m-p/172972#M42335</guid>
      <dc:creator />
      <dc:date>2010-03-09T15:25:21Z</dc:date>
    </item>
  </channel>
</rss>

