<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/ti/sfc/tisfc1125m000" xml:lang="en">
   <Header>
      <Title>Select Data for Planning Board (tisfc1125m000)</Title>
   </Header>
   <HelpTopic>
      <AimSection>
         <Paragraph>Use this session to select the production
		  orders that must be displayed in the graphical planning board (SFC Gantt
		  chart). You can simply select a range of production orders, but you can also
		  use several criteria to select production orders, for example, production
		  orders by PCS project, production start date, machine, or work center.</Paragraph>
      </AimSection>
      <GeneralSection>
         <ProcedureList>
            <ListIntro>Carry out the following steps:</ListIntro>
            <ListItem>Select the data that you want to view in the graphical
			 planning board.</ListItem>
            <ListItem>Click <GUIRef href="/baanerp/ti/sfc/tisfc1125m000#continue.process" role="command">Continue</GUIRef>. The graphical planning board is
			 started.</ListItem>
         </ProcedureList>
         <Paragraph>In the planning board, you can choose how to view the
		  production orders. For more information, refer to <Link href="/baanerp/ti/sfc/tisfc1126m000" role="session">SFC Gantt Chart (tisfc1126m000)</Link>.</Paragraph>
      </GeneralSection>
      <RelatedTopics>
         <SectionTitle>Related topics</SectionTitle>
         <RelTopic>
            <Link href="/baanerp/basictasks/000064" role="manual">To use a graphical planning board</Link>
         </RelTopic>
      </RelatedTopics>
   </HelpTopic>
   <Fields>
      <FieldHelp ID="pdno.f" OtherIDs="pdno.t">
         <Header>
            <Title>Production Order</Title>
         </Header>
         <FuncDesc>An order to produce a specified quantity of an item on a
		specified delivery date.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="cprj.f" OtherIDs="cprj.t">
         <Header>
            <Title>Project (PCS)</Title>
         </Header>
         <FuncDesc>A collection of manufacturing and purchasing actions that are
		performed especially for a particular customer order. A project is initiated by
		a customer order for items having a <GUIRef href="/baanerp/tc/domains/opol#on.order" role="option">To Order</GUIRef> order policy. The purpose of a project is to plan and coordinate the production
		of these items.</FuncDesc>
         <SimpleSection>
            <List>
               <ListIntro>For a standard-to-order production, the project is only
			 used to link the item with the customer order. Otherwise, a project can
			 include:</ListIntro>
               <ListItem>Customized item data (BOMs and routings)</ListItem>
               <ListItem>Project planning (activity planning)</ListItem>
            </List>
            <Paragraph>A budget is a special type of project. A budget is used to
		  plan and estimate, not to carry out production.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="prdt.f" OtherIDs="prdt.t">
         <Header>
            <Title>Production Start Date and Time</Title>
         </Header>
         <FuncDesc>The date that the production order is started.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="dldt.f" OtherIDs="dldt.t">
         <Header>
            <Title>Planned Delivery Date</Title>
         </Header>
         <FuncDesc>The date that the production order items are finished according
		  to the planning.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="osta.f" OtherIDs="osta.t">
         <Header>
            <Title>Order Status</Title>
         </Header>
         <FuncDesc>The status assigned to a production order, which indicates how
		far a production order has been processed. For example, <GUIRef href="/baanerp/tc/domains/osta#planned" role="option">Planned</GUIRef>, <GUIRef href="/baanerp/tc/domains/osta#printed" role="option">Documents Printed</GUIRef>, or <GUIRef href="/baanerp/tc/domains/osta#in.prod" role="option">Released</GUIRef>.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="cwoc.f" OtherIDs="cwoc.t">
         <Header>
            <Title>Work Center</Title>
         </Header>
         <FuncDesc>A specific production area consisting of one or more people
		and/or machines with identical capabilities, that can be considered as one unit
		for purposes of the capacity requirement planning and detailed scheduling.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="mcno.f" OtherIDs="mcno.t">
         <Header>
            <Title>Machine</Title>
         </Header>
         <FuncDesc>In ERP Enterprise,
		a mechanical object on which operations can be carried out to produce items.</FuncDesc>
         <SimpleSection>
            <Paragraph>Machines are linked to operation rates. The operation rate
		  and the labor rate together form the basis for the actual costing of production
		  orders.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="rsdt.f" OtherIDs="rsdt.t">
         <Header>
            <Title>Remainder Start Date</Title>
         </Header>
         <FuncDesc>The date on which the rest of the production is planned to
		  start.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="item.f" OtherIDs="item.t">
         <Header>
            <Title>Item</Title>
         </Header>
         <FuncDesc>In ERP Enterprise,
		the raw materials, subassemblies, finished products, and tools that can be
		purchased, stored, manufactured, sold, and so on.</FuncDesc>
         <SimpleSection>
            <Paragraph>An item can also represent a set of items handled as one kit,
		  or exist in multiple product variants.</Paragraph>
            <List>
               <ListIntro>You can also define nonphysical items, which are not held
			 in inventory but can be used to post costs or to invoice services to customers.
			 The following are examples of nonphysical items:</ListIntro>
               <ListItem>Cost items (for example, electricity)</ListItem>
               <ListItem>Service items</ListItem>
               <ListItem>Subcontracting services</ListItem>
               <ListItem>List items (menus/options)</ListItem>
            </List>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="skip.zero.opers">
         <Header>
            <Title>Skip operations having Remaining Production Time = 0</Title>
         </Header>
         <FuncDesc>If this check box is selected, finished operations are
		  not displayed in the planning board.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="skip.completed">
         <Header>
            <Title>Skip operations with status Completed</Title>
         </Header>
         <FuncDesc>If this check box is selected, operations with the <GUIRef href="/baanerp/ti/domains/sfc.opst#completed" role="option">Completed</GUIRef> status are not displayed in the planning
		  board.</FuncDesc>
      </FieldHelp>
      <FieldHelp>
         <Header>
            <Title>Read Only</Title>
         </Header>
         <FuncDesc>If this check box is selected, you will not be able to
		  move operations around with the mouse in the planning board to change the
		  operations' planning data. However, you <Emphasis>will</Emphasis> be able to
		  double-click the operation blocks in the planning board, so that the
		  appropriate session is started in which you can change planning
		  data.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="grid.size">
         <Header>
            <Title>Grid Size</Title>
         </Header>
         <FuncDesc>If you are replanning operations in the graphical planning
		  board, you can define the step size (in minutes) to drag and drop an operation.
		  For example, if the <GUIRef href="/baanerp/ti/sfc/tisfc1125m000#grid.size" role="manual">Grid Size</GUIRef> field is 30 minutes, you can move an operation with steps of 30
		  minutes. The start time of your operation can then be 12.30, 13.00, 13.30,
		  etcetera.</FuncDesc>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <Paragraph>If your grid size is 1 or 2 minutes, and you increase it,
			 for example, to 15 or 30 minutes, the sensivity of the planning board is
			 decreased. A larger step size prevents you from accidently moving an operation
			 by only touching the operation with the mouse.</Paragraph>
         </Note>
      </FieldHelp>
      <FieldHelp ID="activity.dsca">
         <Header>
            <Title>Activity Description</Title>
         </Header>
         <FuncDesc>The description on the activity bars can be:</FuncDesc>
         <AllowedValues>
            <SectionTitle>Allowed values</SectionTitle>
            <List>
               <ListItem>
                  <GUIRef href="/baanerp/ti/domains/sfc.actd#pdno.opno" role="option">Order and Operation</GUIRef>
               </ListItem>
               <ListItem>
                  <GUIRef href="/baanerp/ti/domains/sfc.actd#main.item" role="option">Main Item</GUIRef>
               </ListItem>
               <ListItem>
                  <GUIRef href="/baanerp/ti/domains/sfc.actd#oper.item" role="option">Operated Item</GUIRef>
               </ListItem>
            </List>
         </AllowedValues>
      </FieldHelp>
   </Fields>
   <FormCommands>
      <CommandHelp ID="continue.process">
         <Header>
            <Title>Continue</Title>
         </Header>
         <FuncDesc>Click to start the graphical planning board.</FuncDesc>
      </CommandHelp>
   </FormCommands>
</Session>