<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/wh/inh/whinh2205m000" xml:lang="en">
   <Header>
      <Title>Generate Orders (OCB) (whinh2205m000)</Title>
   </Header>
   <HelpTopic>
      <AimSection>
         <Paragraph>Use this session to generate orders to
		  replenish the specified combination of warehouse and item. To generate
		  replenishment orders, LN checks the supply requests present in the <GUIRef href="/baanerp/wh/inp/whinp3100m000" role="session">Supply Requests for Order Controlled/Batch (whinp3100m000)</GUIRef> session.</Paragraph>
         <List>
            <ListIntro>LN can generate supply orders of the following types:</ListIntro>
            <ListItem>Purchase orders and purchase schedules for purchased items,
			 if the <GUIRef href="/baanerp/wh/wmd/whwmd2510m000#whwmd210.sfwh" role="manual">Supply from Warehouse</GUIRef> check box is cleared in the <GUIRef href="/baanerp/wh/wmd/whwmd2510m000" role="session">Warehouse - Item (whwmd2510m000)</GUIRef> session.</ListItem>
            <ListItem>Production orders for manufactured items, if the <GUIRef href="/baanerp/wh/wmd/whwmd2510m000#whwmd210.sfwh" role="manual">Supply from Warehouse</GUIRef> check box is cleared in the <GUIRef href="/baanerp/wh/wmd/whwmd2510m000" role="session">Warehouse - Item (whwmd2510m000)</GUIRef> session.</ListItem>
            <ListItem>Warehouse transfers, if the <GUIRef href="/baanerp/wh/wmd/whwmd2510m000#whwmd210.sfwh" role="manual">Supply from Warehouse</GUIRef> check box is selected in the <GUIRef href="/baanerp/wh/wmd/whwmd2510m000" role="session">Warehouse - Item (whwmd2510m000)</GUIRef> session and the value in the <Link href="/baanerp/tc/trm/tctrm1130m000#tctrm130.ttaw" role="formfield">Transfer Type</Link> field in the <GUIRef href="/baanerp/tc/trm/tctrm1130m000" role="session">Order Terms and Conditions (tctrm1130m000)</GUIRef> session is <GUIRef href="/baanerp/tc/domains/ttaw#wh.transfer" role="option">Warehouse Transfer</GUIRef>.</ListItem>
            <ListItem>Sales order or sales schedule transfers, if the <GUIRef href="/baanerp/wh/wmd/whwmd2510m000#whwmd210.sfwh" role="manual">Supply from Warehouse</GUIRef> check box is selected in the <GUIRef href="/baanerp/wh/wmd/whwmd2510m000" role="session">Warehouse - Item (whwmd2510m000)</GUIRef> session and the value in the <Link href="/baanerp/tc/trm/tctrm1130m000#tctrm130.ttaw" role="formfield">Transfer Type</Link> field in the <GUIRef href="/baanerp/tc/trm/tctrm1130m000" role="session">Order Terms and Conditions (tctrm1130m000)</GUIRef> session is <GUIRef href="/baanerp/tc/domains/ttaw#sls.order.trf" role="option">Sales Order Transfer</GUIRef> or <GUIRef href="/baanerp/tc/domains/ttaw#sls.sched.trf" role="option">Sales Schedule Transfer</GUIRef>.</ListItem>
            <ListItem/>
            <ListItem/>
         </List>
         <Paragraph>The generated order numbers and order statuses are displayed
		  in the <GUIRef href="/baanerp/wh/inp/whinp3100m000" role="session">Supply Requests for Order Controlled/Batch (whinp3100m000)</GUIRef> session.</Paragraph>
      </AimSection>
      <RelatedTopics>
         <SectionTitle>Related topics</SectionTitle>
         <RelTopic>
            <Link href="/baanerp/wh/onlinemanual/000313" role="manual">Order Controlled/Batch setup and order generation</Link>
         </RelTopic>
      </RelatedTopics>
   </HelpTopic>
   <Fields>
      <FieldHelp ID="cwar.f">
         <Header>
            <Title>Warehouse</Title>
         </Header>
         <FuncDesc>The warehouse for which to generate supply orders. The only <Link href="/baanerp/tc/glossary/glossary#Warehouse_tc" role="glossary">warehouse</Link> types allowed are <GUIRef href="/baanerp/tc/domains/typw#normal" role="option">Normal</GUIRef> and <GUIRef href="/baanerp/tc/domains/typw#wip" role="option">Shop Floor</GUIRef>.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="cwar.t">
         <Header>
            <Title>Warehouse</Title>
         </Header>
         <FuncDesc>The warehouse for which to generate supply orders. The only <Link href="/baanerp/tc/glossary/glossary#Warehouse_tc" role="glossary">warehouse</Link> types allowed are <GUIRef href="/baanerp/tc/domains/typw#normal" role="option">Normal</GUIRef> and <GUIRef href="/baanerp/tc/domains/typw#wip" role="option">Shop Floor</GUIRef>.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="effn.f">
         <Header>
            <Title>Effectivity Unit</Title>
         </Header>
         <FuncDesc>A reference number on a sales order line or a sales quotation
		line that is used to model deviations for a unit effective item.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="effn.t">
         <Header>
            <Title>Effectivity Unit</Title>
         </Header>
         <FuncDesc>A reference number on a sales order line or a sales quotation
		line that is used to model deviations for a unit effective item.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="rdat.f">
         <Header>
            <Title>Requirement Date</Title>
         </Header>
         <FuncDesc>The date the goods are required. For actual orders this date
		  equals the planned delivery date.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="rdat.t">
         <Header>
            <Title>Requirement Date</Title>
         </Header>
         <FuncDesc>The date the goods are required. For actual orders this date
		  equals the planned delivery date.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="kitm.f">
         <Header>
            <Title>Item Type</Title>
         </Header>
         <FuncDesc>The type of <Link href="/baanerp/tc/glossary/glossary#000001" role="glossary">item</Link> for which to generate
		  replenishment orders.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="kitm.t">
         <Header>
            <Title>Item Type</Title>
         </Header>
         <FuncDesc>The type of <Link href="/baanerp/tc/glossary/glossary#000001" role="glossary">item</Link> for which to generate
		  replenishment orders.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="abcc.f">
         <Header>
            <Title>ABC Code</Title>
         </Header>
         <FuncDesc>A code that shows each item's contribution to the total
		inventory turnover. A items are high-value items and C items constitute low
		value.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="abcc.t">
         <Header>
            <Title>ABC Code</Title>
         </Header>
         <FuncDesc>A code that shows each item's contribution to the total
		inventory turnover. A items are high-value items and C items constitute low
		value.</FuncDesc>
      </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="factor">
         <Header>
            <Title>Factor</Title>
         </Header>
         <FuncDesc>The <Link href="/baanerp/wh/glossary/glossary#000414" role="glossary">order horizon</Link> factor.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="constant">
         <Header>
            <Title>Constant</Title>
         </Header>
         <FuncDesc>The <Link href="/baanerp/wh/glossary/glossary#000414" role="glossary">order horizon</Link> constant.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="unit">
         <Header>
            <Title>Constant</Title>
         </Header>
         <FuncDesc>Days or hours for the <Link href="/baanerp/wh/glossary/glossary#000414" role="glossary">order horizon</Link> constant.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="comb.trans.order">
         <Header>
            <Title>Combine Warehousing Transfer Orders</Title>
         </Header>
         <FuncDesc>If this check box is selected, multiple items that have to be shipped on the
		  same date from the same source warehouse to same destination warehouse, are
		  combined in one transfer order.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="number.group.wh">
         <Header>
            <Title>Number Group</Title>
         </Header>
         <FuncDesc>A group of first free number series that you can assign to a
		specific use.</FuncDesc>
         <SimpleSection>
            <List>
               <ListIntro>For example, you can assign a number group to:</ListIntro>
               <ListItem>Business partner codes</ListItem>
               <ListItem>Purchase contracts</ListItem>
               <ListItem>Sales orders</ListItem>
               <ListItem>Production orders</ListItem>
               <ListItem>Service orders</ListItem>
               <ListItem>Warehousing orders</ListItem>
               <ListItem>Freight orders</ListItem>
            </List>
         </SimpleSection>
         <SimpleSection>
            <Paragraph>Within a number group you can define multiple series. Each
		  series is identified by the series code. The series numbers that LN generates consist of
		  the series code followed by the first free number in the series. Series codes
		  of the same number group have the same length.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="nrgr.wh.dsca">
         <Header>
            <Title>Number Group</Title>
         </Header>
         <FuncDesc>A group of first free number series that you can assign to a
		specific use.</FuncDesc>
         <SimpleSection>
            <List>
               <ListIntro>For example, you can assign a number group to:</ListIntro>
               <ListItem>Business partner codes</ListItem>
               <ListItem>Purchase contracts</ListItem>
               <ListItem>Sales orders</ListItem>
               <ListItem>Production orders</ListItem>
               <ListItem>Service orders</ListItem>
               <ListItem>Warehousing orders</ListItem>
               <ListItem>Freight orders</ListItem>
            </List>
         </SimpleSection>
         <SimpleSection>
            <Paragraph>Within a number group you can define multiple series. Each
		  series is identified by the series code. The series numbers that LN generates consist of
		  the series code followed by the first free number in the series. Series codes
		  of the same number group have the same length.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="order.no.series">
         <Header>
            <Title>Order Series</Title>
         </Header>
         <FuncDesc>A group of order numbers or document numbers starting with the
		same series code. The numbers consist of 9 characters.</FuncDesc>
         <SimpleSection>
            <Paragraph>Series identify orders with certain characteristics, for
		  example, all sales orders handled by the large accounts department start with
		  LA (LA0000001, LA0000002, LA0000003, and so on).</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="series.wh.dsca">
         <Header>
            <Title>Order Series</Title>
         </Header>
         <FuncDesc>A group of order numbers or document numbers starting with the
		same series code. The numbers consist of 9 characters.</FuncDesc>
         <SimpleSection>
            <Paragraph>Series identify orders with certain characteristics, for
		  example, all sales orders handled by the large accounts department start with
		  LA (LA0000001, LA0000002, LA0000003, and so on).</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="wh.order.type">
         <Header>
            <Title>Order Type</Title>
         </Header>
         <FuncDesc>A classification of sales and/or purchase orders with similar
		work flows.</FuncDesc>
         <SimpleSection>
            <Paragraph>Order types determine the character or function of an order
		  and, consequently, of the message. Order types prescribe the chronological
		  order of the sessions (order steps) in the order procedure. The main point is,
		  that you must carry out order steps successively to process a purchase or sales
		  order.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="order.type.dsca">
         <Header>
            <Title>Order Type</Title>
         </Header>
         <FuncDesc>A classification of sales and/or purchase orders with similar
		work flows.</FuncDesc>
         <SimpleSection>
            <Paragraph>Order types determine the character or function of an order
		  and, consequently, of the message. Order types prescribe the chronological
		  order of the sessions (order steps) in the order procedure. The main point is,
		  that you must carry out order steps successively to process a purchase or sales
		  order.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="number.group.sfc">
         <Header>
            <Title>Number Group</Title>
         </Header>
         <FuncDesc>A group of first free number series that you can assign to a
		specific use.</FuncDesc>
         <SimpleSection>
            <List>
               <ListIntro>For example, you can assign a number group to:</ListIntro>
               <ListItem>Business partner codes</ListItem>
               <ListItem>Purchase contracts</ListItem>
               <ListItem>Sales orders</ListItem>
               <ListItem>Production orders</ListItem>
               <ListItem>Service orders</ListItem>
               <ListItem>Warehousing orders</ListItem>
               <ListItem>Freight orders</ListItem>
            </List>
         </SimpleSection>
         <SimpleSection>
            <Paragraph>Within a number group you can define multiple series. Each
		  series is identified by the series code. The series numbers that LN generates consist of
		  the series code followed by the first free number in the series. Series codes
		  of the same number group have the same length.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="nrgr.sfc.dsca">
         <Header>
            <Title>Number Group</Title>
         </Header>
         <FuncDesc>A group of first free number series that you can assign to a
		specific use.</FuncDesc>
         <SimpleSection>
            <List>
               <ListIntro>For example, you can assign a number group to:</ListIntro>
               <ListItem>Business partner codes</ListItem>
               <ListItem>Purchase contracts</ListItem>
               <ListItem>Sales orders</ListItem>
               <ListItem>Production orders</ListItem>
               <ListItem>Service orders</ListItem>
               <ListItem>Warehousing orders</ListItem>
               <ListItem>Freight orders</ListItem>
            </List>
         </SimpleSection>
         <SimpleSection>
            <Paragraph>Within a number group you can define multiple series. Each
		  series is identified by the series code. The series numbers that LN generates consist of
		  the series code followed by the first free number in the series. Series codes
		  of the same number group have the same length.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="series.sfc">
         <Header>
            <Title>Order Series</Title>
         </Header>
         <FuncDesc>A group of order numbers or document numbers starting with the
		same series code. The numbers consist of 9 characters.</FuncDesc>
         <SimpleSection>
            <Paragraph>Series identify orders with certain characteristics, for
		  example, all sales orders handled by the large accounts department start with
		  LA (LA0000001, LA0000002, LA0000003, and so on).</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="series.sfc.dsca">
         <Header>
            <Title>Order Series</Title>
         </Header>
         <FuncDesc>A group of order numbers or document numbers starting with the
		same series code. The numbers consist of 9 characters.</FuncDesc>
         <SimpleSection>
            <Paragraph>Series identify orders with certain characteristics, for
		  example, all sales orders handled by the large accounts department start with
		  LA (LA0000001, LA0000002, LA0000003, and so on).</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="number.group.pur">
         <Header>
            <Title>Number Group</Title>
         </Header>
         <FuncDesc>A group of first free number series that you can assign to a
		specific use.</FuncDesc>
         <SimpleSection>
            <List>
               <ListIntro>For example, you can assign a number group to:</ListIntro>
               <ListItem>Business partner codes</ListItem>
               <ListItem>Purchase contracts</ListItem>
               <ListItem>Sales orders</ListItem>
               <ListItem>Production orders</ListItem>
               <ListItem>Service orders</ListItem>
               <ListItem>Warehousing orders</ListItem>
               <ListItem>Freight orders</ListItem>
            </List>
         </SimpleSection>
         <SimpleSection>
            <Paragraph>Within a number group you can define multiple series. Each
		  series is identified by the series code. The series numbers that LN generates consist of
		  the series code followed by the first free number in the series. Series codes
		  of the same number group have the same length.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="nrgr.pur.dsca">
         <Header>
            <Title>Number Group</Title>
         </Header>
         <FuncDesc>A group of first free number series that you can assign to a
		specific use.</FuncDesc>
         <SimpleSection>
            <List>
               <ListIntro>For example, you can assign a number group to:</ListIntro>
               <ListItem>Business partner codes</ListItem>
               <ListItem>Purchase contracts</ListItem>
               <ListItem>Sales orders</ListItem>
               <ListItem>Production orders</ListItem>
               <ListItem>Service orders</ListItem>
               <ListItem>Warehousing orders</ListItem>
               <ListItem>Freight orders</ListItem>
            </List>
         </SimpleSection>
         <SimpleSection>
            <Paragraph>Within a number group you can define multiple series. Each
		  series is identified by the series code. The series numbers that LN generates consist of
		  the series code followed by the first free number in the series. Series codes
		  of the same number group have the same length.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="series.pur">
         <Header>
            <Title>Order Series</Title>
         </Header>
         <FuncDesc>A group of order numbers or document numbers starting with the
		same series code. The numbers consist of 9 characters.</FuncDesc>
         <SimpleSection>
            <Paragraph>Series identify orders with certain characteristics, for
		  example, all sales orders handled by the large accounts department start with
		  LA (LA0000001, LA0000002, LA0000003, and so on).</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="series.pur.dsca">
         <Header>
            <Title>Order Series</Title>
         </Header>
         <FuncDesc>A group of order numbers or document numbers starting with the
		same series code. The numbers consist of 9 characters.</FuncDesc>
         <SimpleSection>
            <Paragraph>Series identify orders with certain characteristics, for
		  example, all sales orders handled by the large accounts department start with
		  LA (LA0000001, LA0000002, LA0000003, and so on).</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="order.type.pur">
         <Header>
            <Title>Order Type</Title>
         </Header>
         <FuncDesc>A classification of sales and/or purchase orders with similar
		work flows.</FuncDesc>
         <SimpleSection>
            <Paragraph>Order types determine the character or function of an order
		  and, consequently, of the message. Order types prescribe the chronological
		  order of the sessions (order steps) in the order procedure. The main point is,
		  that you must carry out order steps successively to process a purchase or sales
		  order.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="pur.type.dsca">
         <Header>
            <Title>Order Type</Title>
         </Header>
         <FuncDesc>A classification of sales and/or purchase orders with similar
		work flows.</FuncDesc>
         <SimpleSection>
            <Paragraph>Order types determine the character or function of an order
		  and, consequently, of the message. Order types prescribe the chronological
		  order of the sessions (order steps) in the order procedure. The main point is,
		  that you must carry out order steps successively to process a purchase or sales
		  order.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="number.group.sls">
         <Header>
            <Title>Number Group</Title>
         </Header>
         <FuncDesc>A group of first free number series that you can assign to a
		specific use.</FuncDesc>
         <SimpleSection>
            <List>
               <ListIntro>For example, you can assign a number group to:</ListIntro>
               <ListItem>Business partner codes</ListItem>
               <ListItem>Purchase contracts</ListItem>
               <ListItem>Sales orders</ListItem>
               <ListItem>Production orders</ListItem>
               <ListItem>Service orders</ListItem>
               <ListItem>Warehousing orders</ListItem>
               <ListItem>Freight orders</ListItem>
            </List>
         </SimpleSection>
         <SimpleSection>
            <Paragraph>Within a number group you can define multiple series. Each
		  series is identified by the series code. The series numbers that LN generates consist of
		  the series code followed by the first free number in the series. Series codes
		  of the same number group have the same length.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="nrgr.sls.dsca">
         <Header>
            <Title>Number Group</Title>
         </Header>
         <FuncDesc>A group of first free number series that you can assign to a
		specific use.</FuncDesc>
         <SimpleSection>
            <List>
               <ListIntro>For example, you can assign a number group to:</ListIntro>
               <ListItem>Business partner codes</ListItem>
               <ListItem>Purchase contracts</ListItem>
               <ListItem>Sales orders</ListItem>
               <ListItem>Production orders</ListItem>
               <ListItem>Service orders</ListItem>
               <ListItem>Warehousing orders</ListItem>
               <ListItem>Freight orders</ListItem>
            </List>
         </SimpleSection>
         <SimpleSection>
            <Paragraph>Within a number group you can define multiple series. Each
		  series is identified by the series code. The series numbers that LN generates consist of
		  the series code followed by the first free number in the series. Series codes
		  of the same number group have the same length.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="series.sls">
         <Header>
            <Title>Order Series</Title>
         </Header>
         <FuncDesc>A group of order numbers or document numbers starting with the
		same series code. The numbers consist of 9 characters.</FuncDesc>
         <SimpleSection>
            <Paragraph>Series identify orders with certain characteristics, for
		  example, all sales orders handled by the large accounts department start with
		  LA (LA0000001, LA0000002, LA0000003, and so on).</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="series.sls.dsca">
         <Header>
            <Title>Order Series</Title>
         </Header>
         <FuncDesc>A group of order numbers or document numbers starting with the
		same series code. The numbers consist of 9 characters.</FuncDesc>
         <SimpleSection>
            <Paragraph>Series identify orders with certain characteristics, for
		  example, all sales orders handled by the large accounts department start with
		  LA (LA0000001, LA0000002, LA0000003, and so on).</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="order.type.sls">
         <Header>
            <Title>Order Type</Title>
         </Header>
         <FuncDesc>A classification of sales and/or purchase orders with similar
		work flows.</FuncDesc>
         <SimpleSection>
            <Paragraph>Order types determine the character or function of an order
		  and, consequently, of the message. Order types prescribe the chronological
		  order of the sessions (order steps) in the order procedure. The main point is,
		  that you must carry out order steps successively to process a purchase or sales
		  order.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="sls.type.dsca">
         <Header>
            <Title>Order Type</Title>
         </Header>
         <FuncDesc>A classification of sales and/or purchase orders with similar
		work flows.</FuncDesc>
         <SimpleSection>
            <Paragraph>Order types determine the character or function of an order
		  and, consequently, of the message. Order types prescribe the chronological
		  order of the sessions (order steps) in the order procedure. The main point is,
		  that you must carry out order steps successively to process a purchase or sales
		  order.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="number.group.sche">
         <Header>
            <Title>Number Group</Title>
         </Header>
         <FuncDesc>A group of first free number series that you can assign to a
		specific use.</FuncDesc>
         <SimpleSection>
            <List>
               <ListIntro>For example, you can assign a number group to:</ListIntro>
               <ListItem>Business partner codes</ListItem>
               <ListItem>Purchase contracts</ListItem>
               <ListItem>Sales orders</ListItem>
               <ListItem>Production orders</ListItem>
               <ListItem>Service orders</ListItem>
               <ListItem>Warehousing orders</ListItem>
               <ListItem>Freight orders</ListItem>
            </List>
         </SimpleSection>
         <SimpleSection>
            <Paragraph>Within a number group you can define multiple series. Each
		  series is identified by the series code. The series numbers that LN generates consist of
		  the series code followed by the first free number in the series. Series codes
		  of the same number group have the same length.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="nrgr.sched.dsca">
         <Header>
            <Title>Number Group</Title>
         </Header>
         <FuncDesc>A group of first free number series that you can assign to a
		specific use.</FuncDesc>
         <SimpleSection>
            <List>
               <ListIntro>For example, you can assign a number group to:</ListIntro>
               <ListItem>Business partner codes</ListItem>
               <ListItem>Purchase contracts</ListItem>
               <ListItem>Sales orders</ListItem>
               <ListItem>Production orders</ListItem>
               <ListItem>Service orders</ListItem>
               <ListItem>Warehousing orders</ListItem>
               <ListItem>Freight orders</ListItem>
            </List>
         </SimpleSection>
         <SimpleSection>
            <Paragraph>Within a number group you can define multiple series. Each
		  series is identified by the series code. The series numbers that LN generates consist of
		  the series code followed by the first free number in the series. Series codes
		  of the same number group have the same length.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="series.schedules">
         <Header>
            <Title>Order Series</Title>
         </Header>
         <FuncDesc>A group of order numbers or document numbers starting with the
		same series code. The numbers consist of 9 characters.</FuncDesc>
         <SimpleSection>
            <Paragraph>Series identify orders with certain characteristics, for
		  example, all sales orders handled by the large accounts department start with
		  LA (LA0000001, LA0000002, LA0000003, and so on).</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="series.sched.dsca">
         <Header>
            <Title>Order Series</Title>
         </Header>
         <FuncDesc>A group of order numbers or document numbers starting with the
		same series code. The numbers consist of 9 characters.</FuncDesc>
         <SimpleSection>
            <Paragraph>Series identify orders with certain characteristics, for
		  example, all sales orders handled by the large accounts department start with
		  LA (LA0000001, LA0000002, LA0000003, and so on).</Paragraph>
         </SimpleSection>
      </FieldHelp>
   </Fields>
   <FormCommands>
      <CommandHelp ID="exec.cont.process">
         <Header>
            <Title>Generate</Title>
         </Header>
         <FuncDesc>Start generating supply orders.</FuncDesc>
      </CommandHelp>
   </FormCommands>
</Session>