<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/qm/ptc/qmptc1120m000" xml:lang="en">
   <Header>
      <Title>Standard Orders - by Origin (qmptc1120m000)</Title>
   </Header>
   <HelpTopic>
      <AimSection>
         <Paragraph>Use this session to display orders by
		  origin.</Paragraph>
      </AimSection>
      <GeneralSection>
         <Paragraph>In the details
		  session, you can maintain orders by origin.</Paragraph>
         <List>
            <ListItem>The values you enter
			 in the <GUIRef href="/baanerp/qm/ptc/qmptc1120m000#qmptc120.reco" role="manual">QM Only Recommends</GUIRef> field and the <GUIRef href="/baanerp/qm/ptc/qmptc1120m000#qmptc120.blmt" role="manual">Blocking Method</GUIRef> field will be linked to the origin order.</ListItem>
            <ListItem>The recommended
			 quantities displayed in the <GUIRef href="/baanerp/qm/ptc/qmptc1120m000#qmptc120.raqa" role="manual">Recommended</GUIRef> ( <GUIRef href="/baanerp/qm/ptc/qmptc1120m000#qmptcs2520.1" role="groupbox">Accepted Quantities</GUIRef>) field and the <GUIRef href="/baanerp/qm/ptc/qmptc1120m000#qmptc120.rrqa" role="manual">Recommended</GUIRef> ( <GUIRef href="/baanerp/qm/ptc/qmptc1120m000#qmptcs2520.2" role="groupbox">Rejected Quantities</GUIRef>) field will be stored after the
			 inspection order has been processed.</ListItem>
            <ListItem>If an inspection order
			 is closed, the actual quantities will be stored.</ListItem>
         </List>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <Paragraph>Use the <Link href="/baanerp/qm/ptc/qmptc1100m000" role="session">Inspection Orders (qmptc1100m000)</Link> session
			 to maintain the inspection order(s) for a specific order.</Paragraph>
         </Note>
      </GeneralSection>
      <RelatedTopics>
         <SectionTitle>Related topics</SectionTitle>
         <RelTopic>
            <Link href="/baanerp/qm/onlinemanual/000007" role="manual">Standard inspections</Link>
         </RelTopic>
      </RelatedTopics>
   </HelpTopic>
   <Fields>
      <FieldHelp ID="qmptc120.orgn">
         <Header>
            <Title>Origin</Title>
         </Header>
         <FuncDesc>An integrated module or package to which an (inspection) order
		is related.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="qmptc120.orno">
         <Header>
            <Title>Origin Order</Title>
         </Header>
         <FuncDesc>The order number of the <Link href="/baanerp/qm/glossary/glossary#000008" role="glossary">origin</Link> of the
		  inspection.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="qmptc120.rsta">
         <Header>
            <Title>Inspection Status</Title>
         </Header>
         <FuncDesc>The inspection status indicates the current status of the
		  inspection order. The status changes during several sessions.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="qmptc120.seqn">
         <Header>
            <Title>Sequence</Title>
         </Header>
         <FuncDesc>The sequence number of the inspection order on the basis of
		which characteristics are tested on different samples.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="qmptc120.pono">
         <Header>
            <Title>Position</Title>
         </Header>
         <FuncDesc>The position number on the order to which the inspection order
		  is linked. This can be the position number of the sales order line, the
		  position number of the purchase order line, or the position number in the
		  BOM.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="qmptc120.opno">
         <Header>
            <Title>Operation</Title>
         </Header>
         <FuncDesc>One of a series of steps in a routing that are carried out
		successively to produce an item.</FuncDesc>
         <SimpleSection>
            <List>
               <ListIntro>The following data is collected during a routing operation:</ListIntro>
               <ListItem>The task. For example, sawing.</ListItem>
               <ListItem>The machine used to carry out the task (optional). For
			 example, sawing machine.</ListItem>
               <ListItem>The place where the task is carried out (work center). For
			 example, woodwork.</ListItem>
               <ListItem>The number of employees required to carry out the task.</ListItem>
            </List>
            <Paragraph>This data is used to compute order lead times, to plan
		  production orders and to calculate cost prices.</Paragraph>
         </SimpleSection>
         <SimpleSection>
            <Paragraph>A quality inspection
			 must take place, during or after this operation.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="qmptc120.apno">
         <Header>
            <Title>Inspection</Title>
         </Header>
         <FuncDesc>Displays a list of the inspection order lines generated for a
		  particular inspection order. These lines will correspond to characteristics
		  maintained for each of the test groups that are linked to the Quality
		  ID.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="qmptc120.apsq">
         <Header>
            <Title>Inspection</Title>
         </Header>
         <FuncDesc>Displays the sequence of the inspection that is carried
		  out.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="qmptc120.huid">
         <Header>
            <Title>Handling Unit</Title>
         </Header>
         <FuncDesc>It is a structure of packaging materials, or a part of such
		  structure, used to pack items.</FuncDesc>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <List>
               <ListIntro>A handling unit includes the following
				attributes:</ListIntro>
               <ListItem>Identification code.</ListItem>
               <ListItem>Packaging item (optional).</ListItem>
               <ListItem>Quantity of packaging items (optional).</ListItem>
            </List>
         </Note>
         <Important>
            <SectionTitle>Important!</SectionTitle>
            <Paragraph>If you link an item to a handling unit, the item is packed
			 by means of the handling unit. The packaging item refers to the type of
			 container or other packing material of which the handling unit
			 consists.</Paragraph>
            <Paragraph>For example, by defining a packaging item such as wooden
			 crate for a handling unit, you specify that the handling unit is a wooden
			 crate.</Paragraph>
         </Important>
      </FieldHelp>
      <FieldHelp ID="qmptc120.oqua">
         <Header>
            <Title>Order Quantity</Title>
         </Header>
         <FuncDesc>Displays the quantity that has been ordered.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="qmptc120.cuoq">
         <Header>
            <Title>Order Unit</Title>
         </Header>
         <FuncDesc>The <Link href="/baanerp/tc/glossary/glossary#Units_tc" role="glossary">unit</Link> in which the ordered quantity is expressed.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="qmptc120.cwar">
         <Header>
            <Title>Warehouse</Title>
         </Header>
         <FuncDesc>A place for storing goods. For each warehouse, you can enter
		address data and data relating to its type.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tcmcs003.dsca">
         <Header>
            <Title>Warehouse</Title>
         </Header>
         <FuncDesc>Displays the warehouse ID which acts as an
		  identifier.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="qmptc120.loca">
         <Header>
            <Title>Location</Title>
         </Header>
         <FuncDesc>The location in the test area where the test takes place.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="qmptc120.clot">
         <Header>
            <Title>Lot</Title>
         </Header>
         <FuncDesc>A number of items produced and stored together that are
		identified by a (lot) code. Lots identify goods.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="qmptc120.date">
         <Header>
            <Title>Date</Title>
         </Header>
         <FuncDesc>A date that is assigned to items when they are stored. You can
		use inventory dates to retrieve items based on FIFO (First In First Out) or
		LIFO (Last In First Out), without carrying out extensive lot control.</FuncDesc>
         <SimpleSection>
            <Paragraph>The meaning of the inventory date is connected to the
		  outbound priority of LIFO, FIFO, or the product expiry date of the item.</Paragraph>
            <Paragraph>With outbound priority LIFO or FIFO, the default for the
		  inventory date is the system date; however, you can overwrite this so that the
		  inventory date does not have to be equal to the storage date. If the item has a
		  particular shelf life, the inventory date is the product expiry date defined
		  for the item.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="qmptc120.item">
         <Header>
            <Title>Item</Title>
         </Header>
         <FuncDesc>In LN,
		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.
			 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="tcibd001.dsca">
         <Header>
            <Title>Description</Title>
         </Header>
         <FuncDesc>Displays the description of the item.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tcibd001.cuni">
         <Header>
            <Title>Inventory Unit</Title>
         </Header>
         <FuncDesc>The unit of measure in which the inventory of an item is
		recorded, such as piece, kilogram, box of 12, or meter.</FuncDesc>
         <SimpleSection>
            <Paragraph>The inventory unit is also used as the base unit in measure
		  conversions, especially for conversions that concern the order unit and the
		  price unit on a purchase order or a sales order. These conversions always use
		  the inventory unit as the base unit. An inventory unit therefore applies to all
		  item types, also to item types that cannot be kept in stock.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="qmptc120.rdqa">
         <Header>
            <Title>Quantity Destroyed</Title>
         </Header>
         <FuncDesc>The total quantity destroyed during a destructive test,
		  expressed in the order unit. The quantity destroyed is equal to the <Link href="/baanerp/tc/glossary/glossary#SampleSize_tc" role="glossary">sample size</Link> of the
		  inspection orders that are tested by means of destructive tests.</FuncDesc>
         <SimpleSection>
            <Paragraph>The quantity
			 destroyed does not have any impact on the accepted or rejected quantities. LN only calculates the
			 quantity that is destroyed according to the test.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="qmptc120.reco">
         <Header>
            <Title>QM Only Recommends</Title>
         </Header>
         <FuncDesc>This field is used to indicate what can be done with the
		  inspection results.</FuncDesc>
         <AllowedValues>
            <SectionTitle>Allowed values</SectionTitle>
            <List>
               <ListIntro/>
               <ListItem>If this check box is selected, the
				  inspection results are a recommendation for the user; the user can overwrite
				  these results.</ListItem>
               <ListItem>If this check box is cleared, the
				  inspection results are mandatory; the user cannot overwrite these results. In
				  this case you cannot use <Link href="/baanerp/tc/glossary/glossary#DestruTest_tc" role="glossary">destructive tests</Link>.</ListItem>
            </List>
         </AllowedValues>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <Paragraph>This field overrules
			 the value of the <GUIRef href="/baanerp/qm/ptc/qmptc1120m000#qmptc120.reco" role="manual">QM Only Recommends</GUIRef> field in the <GUIRef href="/baanerp/qm/ptc/qmptc0100m000" role="session">Quality Management Parameters (qmptc0100m000)</GUIRef> session.</Paragraph>
         </Note>
      </FieldHelp>
      <FieldHelp ID="qmptc120.blmt">
         <Header>
            <Title>Blocking Method</Title>
         </Header>
         <FuncDesc>Refers to the way in which production, purchase, or sales, is
		  stopped or controlled in order to carry out inspections.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="qmptc120.cdis">
         <Header>
            <Title>Reason for Rejection</Title>
         </Header>
         <FuncDesc>The reason why an order is rejected.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tcmcs005.dsca">
         <Header>
            <Title>Reason for Rejection</Title>
         </Header>
         <FuncDesc>Enter the reason or click the browse arrow to display the
		  Reasons (tcmcs0105m000) session. Select the reason from this list.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="qmptc120.cdat">
         <Header>
            <Title>Completion Date</Title>
         </Header>
         <FuncDesc>The date on which all inspection order lines are
		  completed.</FuncDesc>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <Paragraph>The completion date
			 is updated automatically in the <GUIRef href="/baanerp/qm/ptc/qmptc1202m000" role="session">Complete and Process Inspection Orders (qmptc1202m000)</GUIRef> session, and cannot be
			 entered manually.</Paragraph>
         </Note>
      </FieldHelp>
      <FieldHelp ID="qmptc120.pdat">
         <Header>
            <Title>Processing Date</Title>
         </Header>
         <FuncDesc>The date on which the inspection order lines are
		  processed.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="qmptc120.raqa">
         <Header>
            <Title>Recommended</Title>
         </Header>
         <FuncDesc>The quantity to be accepted, as recommended by the <GUIRef href="/baanerp/qm" role="package">Quality</GUIRef>,
		  expressed in the inventory unit. The total of all sample quantities which
		  passed the tests successfully.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="qmptc120.aaqa">
         <Header>
            <Title>Actual</Title>
         </Header>
         <FuncDesc>The actual quantity that is accepted, expressed in the order
		  unit. The actual quantity can be adjusted until the inspection order is closed.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="qmptc120.rrqa">
         <Header>
            <Title>Recommended</Title>
         </Header>
         <FuncDesc>The recommended quantity by LN.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="qmptc120.arqa">
         <Header>
            <Title>Actual</Title>
         </Header>
         <FuncDesc>The actual quantity that is rejected, expressed in the order
		  unit. The actual quantity can be adjusted until the inspection order is
		  closed.</FuncDesc>
      </FieldHelp>
   </Fields>
   <FormCommands>
      <CommandHelp ID="qmptc1400m000">
         <Header>
            <Title>Print Inspection Orders</Title>
         </Header>
         <FuncDesc>Displays the option to print the inspection orders.</FuncDesc>
      </CommandHelp>
      <CommandHelp ID="compl.insp.orders">
         <Header>
            <Title>Complete and Process Inspection Orders...</Title>
         </Header>
         <FuncDesc>Displays an option that allows you to complete inspection
		  orders.</FuncDesc>
      </CommandHelp>
      <CommandHelp ID="process.selected.order">
         <Header>
            <Title>Process Inspection Order</Title>
         </Header>
         <FuncDesc>Displays an option that allows you to process inspection
		  orders.</FuncDesc>
      </CommandHelp>
      <CommandHelp ID="close.insp.orders">
         <Header>
            <Title>Inspection Orders...</Title>
         </Header>
         <FuncDesc>Displays an option that allows you to check and close
		  inspection orders.</FuncDesc>
      </CommandHelp>
      <CommandHelp ID="delete.insp.orders">
         <Header>
            <Title>Inspection Orders...</Title>
         </Header>
         <FuncDesc>Displays an option that allows you to delete inspection
		  orders.</FuncDesc>
      </CommandHelp>
      <CommandHelp ID="delete.test.data">
         <Header>
            <Title>Test Data...</Title>
         </Header>
         <FuncDesc>Displays an option to delete the inspection test.</FuncDesc>
      </CommandHelp>
      <CommandHelp ID="update.insp.history">
         <Header>
            <Title>Inspection History...</Title>
         </Header>
         <FuncDesc>Displays an option that allows you to update the
		  order.</FuncDesc>
      </CommandHelp>
      <CommandHelp ID="inspection.orders">
         <Header>
            <Title>Inspection Orders</Title>
         </Header>
         <FuncDesc>Displays the generated inspection orders for each origin. These
		  orders correspond to the number of test groups linked to the Quality ID used in
		  the Quality Combination.</FuncDesc>
      </CommandHelp>
      <CommandHelp ID="view.origin.orders">
         <Header>
            <Title>Origin Orders</Title>
         </Header>
         <FuncDesc>The order number of the <Link href="/baanerp/qm/glossary/glossary#000008" role="glossary">origin</Link> of the inspection.</FuncDesc>
      </CommandHelp>
   </FormCommands>
</Session>