<?xml version="1.0" encoding="utf-8"?>
<ManualTopic ID="/baanerp/ti/onlinemanual/000693" xml:lang="en">
   <Header>
      <Title>Generating Time Horizon - driven SILS Supply Messages</Title>
      <Keyword type="header" order="d1e2367581">
         <Level1>Generating</Level1>
         <Level2>time horizon - driven SILS supply messages</Level2>
      </Keyword>
      <Keyword type="header" order="d1e2367586">
         <Level1>Time Horizon - driven SILS Supply Messages</Level1>
         <Level2>generating</Level2>
      </Keyword>
   </Header>
   <GeneralSection>
      <Paragraph>Time horizon driven supply is one of the two methods to generate
		or update assembly part supply messages. The other method is to use triggers,
		defined in a <Link href="/baanerp/ti/glossary/glossary#000125" role="glossary">process-triggered workflow</Link>. For example, the completion
		of a previous LSO can be defined as a trigger to run the <Link href="/baanerp/ti/asc/tiasc8210m000" role="session">Replenish Shop Floor Warehouse (tiasc8210m000)</Link> session.</Paragraph>
      <List>
         <ListIntro>If you use time horizon driven supply, you have several
		  advantages. For example:</ListIntro>
         <ListItem>You can generate supply messages before the start of the first
		  LSO, because you are not dependent of previous trigger events.</ListItem>
         <ListItem>You can generate supply messages independent of variations in <Link href="/baanerp/ti/glossary/glossary#000000000000057" role="glossary">cycle time</Link>.</ListItem>
         <ListItem>You can generate supply messages independent of line structure
		  changes.</ListItem>
         <ListItem>You can skip the maintenance of triggers, which can become a
		  rather complex business.</ListItem>
      </List>
      <Paragraph>However, the disadvantage is that you only have planned assembly
		data as basis, and not actual data. If it is vital to act on start dates/times
		and job sequences that are (nearly) actual, in a situation where you cannot
		update the planned data, you must use triggers. Triggers, after all, are always
		based on the actual progress of the assembly order. It is also possible to use
		both methods, as is explained below.</Paragraph>
   </GeneralSection>
   <GeneralSection>
      <SectionTitle>Prerequisites</SectionTitle>
      <List>
         <ListIntro>To generate or update supply messages for an LSO, the
		  following conditions must be met:</ListIntro>
         <ListItem>The LSO falls in one of the time fences that are defined for
		  the assembly parts contained in the LSO.</ListItem>
         <ListItem>At least one of the check boxes <GUIRef href="/baanerp/ti/asc/tiasc8212m000#f.generate" role="manual">Generate Messages</GUIRef> or <GUIRef href="/baanerp/ti/asc/tiasc8212m000#f.regenerate" role="manual">Regenerate Messages</GUIRef> is selected. (If both check boxes
		  are cleared, supply messages are only unblocked, for LSOs that fall in the <GUIRef href="/baanerp/wh/wmd/whwmd4150s000#whwmd450.lutf" role="manual">Last Update Time Fence</GUIRef>.)</ListItem>
         <ListItem>The status of the LSO must be less than <GUIRef href="/baanerp/ti/domains/asc.lsst#completed" role="option">Completed</GUIRef>.</ListItem>
         <ListItem>The status of the assembly order that contains this LSO must be <GUIRef href="/baanerp/ti/domains/asc.asst#sequenced" role="option">Sequenced</GUIRef> or <GUIRef href="/baanerp/ti/domains/asc.asst#in.progress" role="option">In Progress</GUIRef>.</ListItem>
      </List>
   </GeneralSection>
   <GeneralSection>
      <SectionTitle>Functionality</SectionTitle>
      <Paragraph>If you run the current session, supply messages are generated or
		updated, according to the time fence the LSOs fall in, and the check boxes you
		select in this session. Each time fence is defined as a number of working days
		or hours before the planned start date/time of the LSO. Therefore, the time
		fences partly overlap each other.</Paragraph>
      <List>
         <ListIntro>The following time fences exist:</ListIntro>
         <ListItem>
            <GUIRef href="/baanerp/wh/wmd/whwmd4150s000#whwmd450.getf" role="manual">Generate Time Fence</GUIRef> If LSOs fall in this time fence, supply messages are
		  generated or updated for these LSOs.</ListItem>
         <ListItem>
            <GUIRef href="/baanerp/wh/wmd/whwmd4150s000#whwmd450.frtf" role="manual">Frozen Time Fence</GUIRef> This time fence indicates when the content of an LSO is frozen,
		  which means that no changes in materials or quantities are allowed, because the
		  warehouse or supplier cannot proces this kind of changes anymore. However,
		  changes in delivery sequence and delivery date/time are still
		  accepted.</ListItem>
         <ListItem>
            <GUIRef href="/baanerp/wh/wmd/whwmd4150s000#whwmd450.lutf" role="manual">Last Update Time Fence</GUIRef> Supply messages in this time fence cannot be updated
		  anymore and in any respect. The current session only unblocks the supply
		  messages for LSOs that fall in this time fence. Unblocking is explained in one
		  of the paragraphs below.</ListItem>
      </List>
      <Paragraph>The time fences are defined on the KIT that contains the
		assembly parts, in the <GUIRef href="/baanerp/wh/wmd/whwmd4150s000" role="session">Assembly Kit (whwmd4150s000)</GUIRef> session, which you can start by double-clicking a
		record in the <GUIRef href="/baanerp/wh/wmd/whwmd4550m000" role="session">Assembly Kit (whwmd4550m000)</GUIRef> session, in <Link href="/baanerp/wh/onlinemanual/wh" role="manual">Warehousing</Link>. The current session checks whether the selected LSOs fall in
		one of the time fences that are defined on the KIT of the required
		parts.</Paragraph>
   </GeneralSection>
   <GeneralSection>
      <SectionTitle>Post-requirements</SectionTitle>
      <Paragraph>After you generate or update supply messages, you must transfer
		them. To transfer the supply messages, run the <GUIRef href="/baanerp/ti/asc/tiasc8220m000" role="session">Transfer Assembly Part Supply Messages (tiasc8220m000)</GUIRef> session. When the messages are
		transferred, they are processed.</Paragraph>
      <List>
         <ListIntro>The way the supply messages are transferred and processed is
		  determined by the <GUIRef href="/baanerp/wh/wmd/whwmd2110s000#whwmd210.sfwh" role="manual">Supply from Warehouse</GUIRef> check box in the <GUIRef href="/baanerp/wh/wmd/whwmd2110s000" role="session">Warehouse - Item (whwmd2110s000)</GUIRef> session:</ListIntro>
         <ListItem>The check box is selected for internal supply. ERP Enterprise generates <Link href="/baanerp/ti/glossary/glossary#000077" role="glossary">warehouse transfers</Link> from the
		  source warehouse to the shop-floor warehouse.</ListItem>
         <ListItem>The check box is cleared for external supply. The <GUIRef href="/baanerp/td/pur" role="module">Purchase Control</GUIRef> module
		  uses this information to generate a <Link href="/baanerp/td/glossary/glossary#000034" role="glossary">sequenced shipping schedule</Link> to control supply from the supplier to the shop floor warehouse.</ListItem>
      </List>
   </GeneralSection>
   <GeneralSection>
      <SectionTitle>Blocking</SectionTitle>
      <Paragraph>Supply messages for internal supply are generated with the <GUIRef href="/baanerp/ti/asc/tiasc8520m000#tiasc820.bloc" role="manual">Blocked</GUIRef> status. The warehouse orders that result from
		these messages also have the Blocked status. Blocked warehouse orders are not
		processed, although they can be used for scheduling and reservation purposes.
		The warehouse orders are unblocked when you transfer unblocked update messages.
		Unblocked messages are generated, for LSOs that fall in the <GUIRef href="/baanerp/wh/wmd/whwmd4150s000#whwmd450.lutf" role="manual">Last Update Time Fence</GUIRef>, when you run the current
		session. Note that when you run the current session, you always generate last
		updates of supply messages, for LSOs in the selection range, that fall in the <GUIRef href="/baanerp/wh/wmd/whwmd4150s000#whwmd450.lutf" role="manual">Last Update Time Fence</GUIRef>, even if the <GUIRef href="/baanerp/ti/asc/tiasc8212m000#f.generate" role="manual">Generate Messages</GUIRef> check box and the <GUIRef href="/baanerp/ti/asc/tiasc8212m000#f.regenerate" role="manual">Regenerate Messages</GUIRef> check box are cleared. The last
		update can also be performed by the <GUIRef href="/baanerp/ti/asc/tiasc8210m000" role="session">Replenish Shop Floor Warehouse (tiasc8210m000)</GUIRef> session. The status of the supply
		messages is displayed in the <GUIRef href="/baanerp/ti/asc/tiasc8520m000" role="session">Assembly Part Supply Transfer (SILS) (tiasc8520m000)</GUIRef> session.</Paragraph>
   </GeneralSection>
   <GeneralSection>
      <SectionTitle>Relation between triggers and time fences</SectionTitle>
      <List>
         <ListIntro>It is possible to use both triggers and time fences. If you
		  use both methods, the relation between these methods is as follows:</ListIntro>
         <ListItem>The session that is first executed, generates the supply
		  messages. So, if the trigger is defined before the execution of the current
		  session, the <GUIRef href="/baanerp/ti/asc/tiasc8210m000" role="session">Replenish Shop Floor Warehouse (tiasc8210m000)</GUIRef> session
		  generates the messages. The trigger does not take into account the <GUIRef href="/baanerp/wh/wmd/whwmd4150s000#whwmd450.getf" role="manual">Generate Time Fence</GUIRef>, and therefore can be defined
		  before or in this time fence. If the current session is run in the Generate
		  Time Fence, and before the trigger, the current session generates the supply
		  messages.</ListItem>
         <ListItem>The supply messages can be updated by both sessions, and both
		  sessions take into account the <GUIRef href="/baanerp/wh/wmd/whwmd4150s000#whwmd450.frtf" role="manual">Frozen Time Fence</GUIRef>. So, there is no difference in this
		  respect. Only the update of the messages by the current session requires that
		  the selected LSOs are not yet in the <GUIRef href="/baanerp/wh/wmd/whwmd4150s000#whwmd450.lutf" role="manual">Last Update Time Fence</GUIRef>.</ListItem>
         <ListItem>Which session performs the last update, and of what character
		  the update is, depends on the sequence in which the sessions are executed, the
		  way the last update is defined, and the relation to the <GUIRef href="/baanerp/wh/wmd/whwmd4150s000#whwmd450.lutf" role="manual">Last Update Time Fence</GUIRef>. Because it is too complicated
		  to summarize the different situations, it is better to keep in mind the
		  following rules, which determine what happens: <List>
               <ListItem>The current session updates before the <GUIRef href="/baanerp/wh/wmd/whwmd4150s000#whwmd450.lutf" role="manual">Last Update Time Fence</GUIRef> and only unblocks in this time
				fence.</ListItem>
               <ListItem>The <GUIRef href="/baanerp/ti/asc/tiasc8210m000" role="session">Replenish Shop Floor Warehouse (tiasc8210m000)</GUIRef> session updates both before and in the <GUIRef href="/baanerp/wh/wmd/whwmd4150s000#whwmd450.lutf" role="manual">Last Update Time Fence</GUIRef>. If the update is the last
				update, the session also unblocks.</ListItem>
               <ListItem>Whether an update by the <GUIRef href="/baanerp/ti/asc/tiasc8210m000" role="session">Replenish Shop Floor Warehouse (tiasc8210m000)</GUIRef> session is the last update, is defined
				by a comparison of line stations, and not by the relation to the last run of
				the current session or the <GUIRef href="/baanerp/wh/wmd/whwmd4150s000#whwmd450.lutf" role="manual">Last Update Time Fence</GUIRef>. Refer to one of the notes
				below for further explanation.</ListItem>
               <ListItem>Messages can be updated, regardless if they are <GUIRef href="/baanerp/ti/asc/tiasc8520m000#tiasc820.bloc" role="manual">Blocked</GUIRef> or not.</ListItem>
               <ListItem>Messages can only be unblocked once.</ListItem>
            </List>
         </ListItem>
      </List>
   </GeneralSection>
   <Note>
      <SectionTitle>Note</SectionTitle>
      <List>
         <ListItem>The previous explanation supposes that the <GUIRef href="/baanerp/wh/wmd/whwmd4150s000#whwmd450.getf" role="manual">Generate Time Fence</GUIRef> is defined before the <GUIRef href="/baanerp/wh/wmd/whwmd4150s000#whwmd450.frtf" role="manual">Frozen Time Fence</GUIRef>, and the <GUIRef href="/baanerp/wh/wmd/whwmd4150s000#whwmd450.frtf" role="manual">Frozen Time Fence</GUIRef> before the <GUIRef href="/baanerp/wh/wmd/whwmd4150s000#whwmd450.lutf" role="manual">Last Update Time Fence</GUIRef>. In other words: the <GUIRef href="/baanerp/wh/wmd/whwmd4150s000#whwmd450.getf" role="manual">Generate Time Fence</GUIRef> includes the <GUIRef href="/baanerp/wh/wmd/whwmd4150s000#whwmd450.frtf" role="manual">Frozen Time Fence</GUIRef> and the <GUIRef href="/baanerp/wh/wmd/whwmd4150s000#whwmd450.frtf" role="manual">Frozen Time Fence</GUIRef> includes the <GUIRef href="/baanerp/wh/wmd/whwmd4150s000#whwmd450.lutf" role="manual">Last Update Time Fence</GUIRef>.</ListItem>
         <ListItem>The <GUIRef href="/baanerp/ti/asc/tiasc8210m000" role="session">Replenish Shop Floor Warehouse (tiasc8210m000)</GUIRef> session
		  can generate, update and unblock supply messages. If it updates messages, it
		  takes into account the <GUIRef href="/baanerp/wh/wmd/whwmd4150s000#whwmd450.frtf" role="manual">Frozen Time Fence</GUIRef>, but not the <GUIRef href="/baanerp/wh/wmd/whwmd4150s000#whwmd450.lutf" role="manual">Last Update Time Fence</GUIRef>. The last update, which also
		  unblocks the messages, is performed when the line station in the <GUIRef href="/baanerp/ti/asc/tiasc8210m000#ptwf.lstn.from" role="manual">Line Station Trigger From</GUIRef> field in that session is
		  the same as the <GUIRef href="/baanerp/wh/wmd/whwmd2110s000#whwmd210.trst" role="manual">Trigger-from Station</GUIRef> that is defined in the <GUIRef href="/baanerp/wh/wmd/whwmd2110s000" role="session">Warehouse - Item (whwmd2110s000)</GUIRef> session, for the assembly parts in the selected
		  LSOs.</ListItem>
         <ListItem>The session only generates messages for non-floor stock items.
		  You define whether an item is <Link href="/baanerp/ti/glossary/glossary#FloorStock_ti" role="glossary">floor stock</Link> in the <GUIRef href="/baanerp/wh/wmd/whwmd4100s000" role="session">Item - Warehousing (whwmd4100s000)</GUIRef> session.</ListItem>
         <ListItem>Do not confuse the <GUIRef href="/baanerp/wh/wmd/whwmd4150s000#whwmd450.frtf" role="manual">Frozen Time Fence</GUIRef> with the Freeze Time Fence that is
		  defined in Line Assembly Configuration (LAC). The Freeze Time Fence in LAC has
		  respect to the application of changes in the assembly line structure to the
		  assembly orders.</ListItem>
         <ListItem>The current session can only be used to generate and update
		  SILS supply messages. The <GUIRef href="/baanerp/ti/asc/tiasc8210m000" role="session">Replenish Shop Floor Warehouse (tiasc8210m000)</GUIRef> session can also generate Batch supply
		  messages. Once they are generated, Batch messages can not be updated, and they
		  can also not be blocked.</ListItem>
      </List>
   </Note>
</ManualTopic>