<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/cp/rao/cprao1126s000" xml:lang="en">
   <Header>
      <Title>Find Signals (cprao1126s000)</Title>
   </Header>
   <HelpTopic>
      <AimSection>
         <Paragraph>Use this session to search
        for a specific set of signals.</Paragraph>
      </AimSection>
      <GeneralSection>
         <ProcedureList>
            <ListItem>Select a planner ID
          and a <Link href="/baanerp/cp/glossary/glossary#000007" role="glossary">scenario</Link>.</ListItem>
            <ListItem>Specify the minimum
          and the maximum reference date of the signals to be included in the overview.</ListItem>
            <ListItem>Select the minimum
          and the maximum priority of the signals to be included in the overview.</ListItem>
         </ProcedureList>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <Paragraph>By leaving the <GUIRef href="/baanerp/cp/rao/cprao1126s000#plid" role="manual">Planner ID</GUIRef> field empty, you can look for signals that are not directed to a
          specific planner.</Paragraph>
         </Note>
      </GeneralSection>
      <RelatedTopics>
         <SectionTitle>Related topics</SectionTitle>
         <RelTopic>
            <Link href="/baanerp/cp/onlinemanual/000041" role="manual">Planning signals in Enterprise Planning</Link>
         </RelTopic>
      </RelatedTopics>
   </HelpTopic>
   <Fields>
      <FieldHelp ID="plid">
         <Header>
            <Title>Planner ID</Title>
         </Header>
         <FuncDesc>The employee number of the planner whose signals you want to
        look for. If you leave this field empty, LN looks for those signals that
        are not directed to a specific planner.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="plnc">
         <Header>
            <Title>Scenario</Title>
         </Header>
         <FuncDesc>The identification of an overall planning solution.</FuncDesc>
         <SimpleSection>
            <Paragraph>Each scenario represents one overall planning solution, and
		  involves particular settings for the planning of items and resources. You can
		  use scenarios to analyze and compare various planning options and to find the
		  best planning solution. For example, you can vary demand forecasts or sourcing
		  strategies.</Paragraph>
            <Paragraph>One of the scenarios is the actual scenario, which
		  corresponds with the actual planning situation. You can only transfer planned
		  orders and production plans from the actual scenario to the execution level of LN.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="refdate.f">
         <Header>
            <Title>Reference Date</Title>
         </Header>
         <FuncDesc>The reference date for the signal involved.</FuncDesc>
         <SimpleSection>
            <List>
               <ListIntro>The meaning of this date depends on the signal type.</ListIntro>
               <ListItem>If the signal is
            generated for a specific <Link href="/baanerp/cp/glossary/glossary#000050" role="glossary">planned order</Link>, that is, the <GUIRef href="/baanerp/cp/rao/cprao1125m000#cprao020.orno" role="manual">Order</GUIRef> field
            contains an order number, the reference date usually indicates the end date of
            this order line.</ListItem>
               <ListItem>If the signal is
            generated for an item with an <Link href="/baanerp/cp/glossary/glossary#000019" role="glossary" Update="No">item master plan</Link>, that is, the <GUIRef href="/baanerp/cp/rao/cprao1125m000#cprao020.orno" role="manual">Order</GUIRef> field is
            empty, the reference date usually indicates the start date of the plan period
            in the item master plan to which the signal refers.</ListItem>
            </List>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="refdate.t">
         <Header>
            <Title>Reference Date</Title>
         </Header>
         <FuncDesc>The reference date for the signal involved.</FuncDesc>
         <SimpleSection>
            <List>
               <ListIntro>The meaning of this date depends on the signal type.</ListIntro>
               <ListItem>If the signal has
            been generated for a specific <Link href="/baanerp/cp/glossary/glossary#000050" role="glossary">planned order</Link>, that is,
            there is an order number in the <GUIRef href="/baanerp/cp/rao/cprao1125m000#cprao020.orno" role="manual">Order</GUIRef> field,
            the reference date usually indicates the end date of this order line.</ListItem>
               <ListItem>If the signal has
            been generated on the basis of <Link href="/baanerp/cp/glossary/glossary#000019" role="glossary">master-plan</Link> data, that is,
            the <GUIRef href="/baanerp/cp/rao/cprao1125m000#cprao020.orno" role="manual">Order</GUIRef> field
            contains the phrase MasterPln, the reference date usually indicates the start
            date of the plan period to which the signal refers.</ListItem>
            </List>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="prio.f">
         <Header>
            <Title>Priority</Title>
         </Header>
         <FuncDesc>In this field you can specify the lowest value in the range of
        priorities that you want to use as a selection criterion for the signals
        overview.</FuncDesc>
         <SimpleSection>
            <Paragraph>The signal's
          priority is expressed as a number between 1 (highest priority) and 100 (lowest
          priority).</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="prio.t">
         <Header>
            <Title>Priority</Title>
         </Header>
         <FuncDesc>In this field you can specify the highest value in the range of
        priorities that you want to use as a selection criterion for the signals
        overview.</FuncDesc>
         <SimpleSection>
            <Paragraph>The signal's
          priority is expressed as a number between 1 (highest priority) and 100 (lowest
          priority).</Paragraph>
         </SimpleSection>
      </FieldHelp>
   </Fields>
</Session>