<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/qm/ptc/qmptc0411m000" xml:lang="en">
   <Header>
      <Title>Print Quality Combinations (qmptc0411m000)</Title>
   </Header>
   <HelpTopic>
      <AimSection>
         <Paragraph>Use this session to print (a range of) <Link href="/baanerp/qm/glossary/glossary#000010" role="glossary">quality combinations</Link>.</Paragraph>
      </AimSection>
   </HelpTopic>
   <Fields>
      <FieldHelp ID="orgn">
         <Header>
            <Title>Origin</Title>
         </Header>
         <FuncDesc>An integrated module or package to which an (inspection) order
		is related.</FuncDesc>
         <SimpleSection>
            <Paragraph>Quality inspections
			 are executed within a module or package. This field is used to select one of
			 the implemented modules or packages of LN.</Paragraph>
            <Paragraph>See also: <Link href="/baanerp/qm/domains/ptc.orgn" role="domain">Origin of Inspection</Link>
            </Paragraph>
         </SimpleSection>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <Paragraph>In the <GUIRef href="/baanerp/qm/ptc/qmptc0100m000" role="session">Quality Management Parameters (qmptc0100m000)</GUIRef> session you can maintain the implemented
			 modules and packages.</Paragraph>
         </Note>
      </FieldHelp>
      <FieldHelp ID="item.f">
         <Header>
            <Title>From 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="item.t">
         <Header>
            <Title>To 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="sitm.f">
         <Header>
            <Title>From Sub-Item</Title>
         </Header>
         <FuncDesc>A means to further classify items.</FuncDesc>
         <SimpleSection>
            <List>
               <ListIntro>A sub-item can either be:</ListIntro>
               <ListItem>A component item used in a bill of material.</ListItem>
               <ListItem>A material used in a formula.</ListItem>
            </List>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="sitm.t">
         <Header>
            <Title>To Sub-Item</Title>
         </Header>
         <FuncDesc>A means to further classify items.</FuncDesc>
         <SimpleSection>
            <List>
               <ListIntro>A sub-item can either be:</ListIntro>
               <ListItem>A component item used in a bill of material.</ListItem>
               <ListItem>A material used in a formula.</ListItem>
            </List>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="qitg.f">
         <Header>
            <Title>Quality Group</Title>
         </Header>
         <FuncDesc>A group of items with similar quality characteristics. The data
		defined for the quality group are used as defaults for all items of that
		quality group.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="qitg.t">
         <Header>
            <Title>Quality Group</Title>
         </Header>
         <FuncDesc>A group of items with similar quality characteristics. The data
		defined for the quality group are used as defaults for all items of that
		quality group.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="pono.f">
         <Header>
            <Title>Line</Title>
         </Header>
         <FuncDesc>The component's <Link href="/baanerp/wh/glossary/glossary#BOMPositiNum_wh" role="glossary">BOM position number</Link>.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="pono.t">
         <Header>
            <Title>Line</Title>
         </Header>
         <FuncDesc>The component's <Link href="/baanerp/wh/glossary/glossary#BOMPositiNum_wh" role="glossary">BOM position number</Link>.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="bpid.f">
         <Header>
            <Title>Business Partner</Title>
         </Header>
         <FuncDesc>A party with whom you carry out business transactions, for
		example, a customer or a supplier. You can also define departments within your
		organization that act as customers or suppliers to your own department as
		business partners.</FuncDesc>
         <SimpleSection>
            <List>
               <ListIntro>The business partner definition includes:</ListIntro>
               <ListItem>The organization's name and main address.</ListItem>
               <ListItem>The language and currency used.</ListItem>
               <ListItem>Taxation and legal identification data.</ListItem>
            </List>
            <Paragraph>You address the business partner in the person of the
		  business partner's contact. The business-partner status determines if you can
		  carry out transactions. The transactions type (sales orders, invoices,
		  payments, shipments) is defined by the business partner's role.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="bpid.t">
         <Header>
            <Title>Business Partner</Title>
         </Header>
         <FuncDesc>A party with whom you carry out business transactions, for
		example, a customer or a supplier. You can also define departments within your
		organization that act as customers or suppliers to your own department as
		business partners.</FuncDesc>
         <SimpleSection>
            <List>
               <ListIntro>The business partner definition includes:</ListIntro>
               <ListItem>The organization's name and main address.</ListItem>
               <ListItem>The language and currency used.</ListItem>
               <ListItem>Taxation and legal identification data.</ListItem>
            </List>
            <Paragraph>You address the business partner in the person of the
		  business partner's contact. The business-partner status determines if you can
		  carry out transactions. The transactions type (sales orders, invoices,
		  payments, shipments) is defined by the business partner's role.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="opro.f">
         <Header>
            <Title>Routing</Title>
         </Header>
         <FuncDesc>The sequence of operations required to manufacture an item.</FuncDesc>
         <SimpleSection>
            <Paragraph>For each operation, the task, machine, and work center are
		  specified, as well as information about setup time and cycle time.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="opro.t">
         <Header>
            <Title>Routing</Title>
         </Header>
         <FuncDesc>The sequence of operations required to manufacture an item.</FuncDesc>
         <SimpleSection>
            <Paragraph>For each operation, the task, machine, and work center are
		  specified, as well as information about setup time and cycle time.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="opno.f">
         <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>
      </FieldHelp>
      <FieldHelp ID="opno.t">
         <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>
      </FieldHelp>
      <FieldHelp ID="tano.f">
         <Header>
            <Title>Task</Title>
         </Header>
         <FuncDesc>An activity to manufacture or repair an item. For example,
		sawing, drilling, or painting.</FuncDesc>
         <SimpleSection>
            <Paragraph>A task is carried out on a work center, and can be related to
		  a machine.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="tano.t">
         <Header>
            <Title>Task</Title>
         </Header>
         <FuncDesc>An activity to manufacture or repair an item. For example,
		sawing, drilling, or painting.</FuncDesc>
         <SimpleSection>
            <Paragraph>A task is carried out on a work center, and can be related to
		  a machine.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="swar.f">
         <Header>
            <Title>From 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="swar.t">
         <Header>
            <Title>From 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="twar.f">
         <Header>
            <Title>To 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="twar.t">
         <Header>
            <Title>To 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="quid.f">
         <Header>
            <Title>Quality ID</Title>
         </Header>
         <FuncDesc>The code to which data is linked that is necessary to check the
		quality requirements of an item. Since one quality ID can be used for a group
		of products that require the same quality standards and tests, a quality ID can
		considerably reduce time.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="quid.t">
         <Header>
            <Title>Quality ID</Title>
         </Header>
         <FuncDesc>The code to which data is linked that is necessary to check the
		quality requirements of an item. Since one quality ID can be used for a group
		of products that require the same quality standards and tests, a quality ID can
		considerably reduce time.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="txta.txt">
         <Header>
            <Title>Print Text</Title>
         </Header>
         <FuncDesc>If this check box is selected, the text that is linked
		  to the quality combinations (defined in the <GUIRef href="/baanerp/qm/ptc/qmptc0111m000" role="session">Quality Combinations (qmptc0111m000)</GUIRef> session) is printed in the report.</FuncDesc>
      </FieldHelp>
   </Fields>
</Session>