<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/wh/inh/whinh2550m000" xml:lang="en">
   <Header>
      <Title>Warehousing Orders History (whinh2550m000)</Title>
   </Header>
   <HelpTopic>
      <AimSection>
         <Paragraph> Use this session to view the history of <Link href="/baanerp/wh/glossary/glossary#000388" role="glossary">warehousing orders</Link>.</Paragraph>
      </AimSection>
      <GeneralSection>
         <Paragraph>Warehousing orders have a header that
		  contains general order information and one or more order lines. The order lines
		  contain information about the specific item and quantity. Each
		  warehousing-order line consists of one or more advice lines. These lines
		  indicate which specific locations, lots, serialized items, or effectivity units
		  are assigned to the order line.</Paragraph>
         <Paragraph>When warehousing orders are manually
		  modified, LN generates
		  history to register the different versions of the warehousing order. This is
		  valid for the orders as well as for the order lines.</Paragraph>
      </GeneralSection>
      <RelatedTopics>
         <SectionTitle> Related topics</SectionTitle>
         <RelTopic>
            <Link href="/baanerp/wh/onlinemanual/000015" role="manual">Warehousing order history</Link>
         </RelTopic>
      </RelatedTopics>
   </HelpTopic>
   <Fields>
      <FieldHelp ID="whinh250.oorg">
         <Header>
            <Title>Order</Title>
         </Header>
         <FuncDesc>The origin of the warehousing order.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="whinh250.orno">
         <Header>
            <Title>Order</Title>
         </Header>
         <FuncDesc>An order for handling goods in the warehouse.</FuncDesc>
         <SimpleSection>
            <List>
               <ListIntro>A warehouse order can be of the following
			 inventory-transaction types:</ListIntro>
               <ListItem> 
                  <GUIRef href="/baanerp/wh/domains/inh.ittp#receipt" role="option">Receipt</GUIRef>
               </ListItem>
               <ListItem> 
                  <GUIRef href="/baanerp/wh/domains/inh.ittp#issue" role="option">Issue</GUIRef>
               </ListItem>
               <ListItem> 
                  <GUIRef href="/baanerp/wh/domains/inh.ittp#transfer" role="option">Transfer</GUIRef>
               </ListItem>
               <ListItem>
                  <GUIRef href="/baanerp/wh/domains/inh.ittp#wip.transfer" role="option">WIP Transfer</GUIRef>
               </ListItem>
            </List>
            <Paragraph>Each order has an origin and contains all the information
		  required for warehouse handling. Depending on the item (lot or non-lot) and
		  warehouse (with or without locations), lots and/or locations can be assigned.
		  The order follows a predefined warehousing procedure.</Paragraph>
         </SimpleSection>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <Paragraph>In <GUIRef href="/baanerp/ti" role="package">Manufacturing</GUIRef> a warehousing order is often called a
		  warehouse order.</Paragraph>
         </Note>
      </FieldHelp>
      <FieldHelp ID="whinh250.oset">
         <Header>
            <Title>Order</Title>
         </Header>
         <FuncDesc>The order set groups order lines of the same order together
		according to the following attributes:</FuncDesc>
         <SimpleSection>
            <List>
               <ListItem>Ship-from partner</ListItem>
               <ListItem>Ship-to partner</ListItem>
               <ListItem>Ship-from address</ListItem>
               <ListItem>Ship-to address</ListItem>
               <ListItem>Carrier</ListItem>
               <ListItem>Shipping date</ListItem>
               <ListItem>Original company</ListItem>
            </List>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="whinh250.trdt">
         <Header>
            <Title>Transaction Date</Title>
         </Header>
         <FuncDesc>The date on which the order is changed and/or written to the
		history file. For each change, LN inserts a new line and a new transaction date. This applies to any
		type of order.</FuncDesc>
         <SimpleSection>
            <List>
               <ListIntro>Among other things, the transaction date is important for:</ListIntro>
               <ListItem>Scheduling</ListItem>
               <ListItem>Statistics</ListItem>
               <ListItem>Determining due dates and currency exchange rates</ListItem>
            </List>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="whinh250.grid">
         <Header>
            <Title>Order Group</Title>
         </Header>
         <FuncDesc>The group of orders to which the warehousing order belongs.</FuncDesc>
         <SimpleSection>
            <Paragraph>You can use order groups to carry out the
			 outbound process for each group of related warehousing orders, to save time.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="whinh250.otyp">
         <Header>
            <Title>Warehousing Order Type</Title>
         </Header>
         <FuncDesc>A code that identifies the type of a warehousing order. The
		default warehousing procedure that you link to a warehousing order type
		determines how the warehousing orders to which the order type is allocated are
		processed in the warehouse, although you can modify the default procedure for
		individual warehousing orders or order lines.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="whinh250.ittp">
         <Header>
            <Title>Transaction Type</Title>
         </Header>
         <FuncDesc>A classification that is used to indicate the type of inventory
		movement.</FuncDesc>
         <SimpleSection>
            <List>
               <ListIntro>The following inventory transaction types are available:</ListIntro>
               <ListItemHead>
                  <GUIRef href="/baanerp/wh/domains/inh.ittp#issue" role="option">Issue</GUIRef>
               </ListItemHead>
               <ListItem>From warehouse to other entity than warehouse.</ListItem>
               <ListItemHead>
                  <GUIRef href="/baanerp/wh/domains/inh.ittp#receipt" role="option">Receipt</GUIRef>
               </ListItemHead>
               <ListItem>From other entity than warehouse to warehouse.</ListItem>
               <ListItemHead>
                  <GUIRef href="/baanerp/wh/domains/inh.ittp#transfer" role="option">Transfer</GUIRef>
               </ListItemHead>
               <ListItem>From one warehouse to another.</ListItem>
               <ListItemHead>
                  <GUIRef href="/baanerp/wh/domains/inh.ittp#wip.transfer" role="option">WIP Transfer</GUIRef>
               </ListItemHead>
               <ListItem>From one costing work center to another.</ListItem>
            </List>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="whinh250.hist">
         <Header>
            <Title>History Status</Title>
         </Header>
         <FuncDesc>The history status of the order</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="whinh250.logn">
         <Header>
            <Title>User</Title>
         </Header>
         <FuncDesc>The logon code or name of the person who last modified the
		  warehouse order.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="whinh250.odat">
         <Header>
            <Title>Order Date</Title>
         </Header>
         <FuncDesc>The order date.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="whinh250.wdep">
         <Header>
            <Title>Office</Title>
         </Header>
         <FuncDesc>The warehouse department responsible for processing the order.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="whinh250.clan">
         <Header>
            <Title>Language</Title>
         </Header>
         <FuncDesc>The language code of the site responsible for the order.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="whinh250.cons">
         <Header>
            <Title>Consignment</Title>
         </Header>
         <FuncDesc> If this check box is selected, the order is for <Link href="/baanerp/wh/glossary/glossary#000315" role="glossary">consignment inventory</Link>.</FuncDesc>
         <SimpleSection>
            <Paragraph>If the order is a receipt, the goods
			 received are taken into consignment inventory and no payment is made for the
			 received goods.</Paragraph>
            <Paragraph>If the order is an issue, the goods are
			 issued from the consignment warehouse of the business partner.</Paragraph>
            <Paragraph>If the order is a transfer, the goods are
			 transferred from the company's warehouse to the business partner's consignment
			 warehouse. No invoice is created.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="txta.yn">
         <Header>
            <Title>Header Text</Title>
         </Header>
         <FuncDesc> If this check box is selected, LN prints a header text.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="whinh250.invc">
         <Header>
            <Title>Invoicing</Title>
         </Header>
         <FuncDesc> If this check box is selected, the order must be
		  invoiced at the moment of shipping, because an invoice relation is defined.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="txtb.yn">
         <Header>
            <Title>Footer Text</Title>
         </Header>
         <FuncDesc> If this check box is selected, LN prints a footer text.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="whinh250.bflh">
         <Header>
            <Title>Backflush Order</Title>
         </Header>
         <FuncDesc> If this check box is selected, this warehousing order
		  is a <Link href="/baanerp/ti/glossary/glossary#Backflushing_ti" role="glossary">backflushing</Link> order.</FuncDesc>
         <Note>
            <SectionTitle> Note</SectionTitle>
            <Paragraph>If the <GUIRef href="/baanerp/wh/inh/whinh0100m000#whinh000.sbfo" role="manual">Suppress Backflushing Orders</GUIRef> check box in the <GUIRef href="/baanerp/wh/inh/whinh0100m000" role="session">Inventory Handling Parameters (whinh0100m000)</GUIRef> session is selected, backflushing orders
			 are suppressed. Therefore, you cannot view these orders in the current session.</Paragraph>
         </Note>
      </FieldHelp>
      <FieldHelp ID="whinh250.rtrn">
         <Header>
            <Title>Return Order</Title>
         </Header>
         <FuncDesc> If this check box is selected, the order is a return
		  order.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="whinh250.rrgd">
         <Header>
            <Title>Return Rejected Goods</Title>
         </Header>
         <FuncDesc> If this check box is selected, the warehousing order is
		  used to return rejected items to the business partner.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="blck.yn">
         <Header>
            <Title>Blocked</Title>
         </Header>
         <FuncDesc> If this check box is selected, the order is blocked.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="whinh250.sfty">
         <Header>
            <Title>Code</Title>
         </Header>
         <FuncDesc>The ship-from type is used, together with the ship-from code,
		to identify the exact source of a warehousing order.</FuncDesc>
         <SimpleSection>
            <List>
               <ListIntro>The ship-from type can have the following values:</ListIntro>
               <ListItem> 
                  <GUIRef href="/baanerp/tc/domains/typs#partner" role="option">Business Partner</GUIRef>
               </ListItem>
               <ListItem> 
                  <GUIRef href="/baanerp/tc/domains/typs#warehouse" role="option">Warehouse</GUIRef>
               </ListItem>
               <ListItem> 
                  <GUIRef href="/baanerp/tc/domains/typs#work.center" role="option">Work Center</GUIRef>
               </ListItem>
               <ListItem> 
                  <GUIRef href="/baanerp/tc/domains/typs#project" role="option">Project</GUIRef>
               </ListItem>
            </List>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="type.from.cwar">
         <Header>
            <Title>Code</Title>
         </Header>
         <FuncDesc>The type of warehouse from which the goods are shipped.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="whinh250.sfco">
         <Header>
            <Title>Code</Title>
         </Header>
         <FuncDesc>A code used, together with the ship-from type, to identify the
		exact source of a warehousing order.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="whinh250.sfad">
         <Header>
            <Title>Address</Title>
         </Header>
         <FuncDesc>The address from where the goods are shipped. This is the
		  address of the source type indicated in the <GUIRef href="/baanerp/wh/inh/whinh2100m000#whinh200.sfty" role="manual">Ship-from Code</GUIRef> field.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="whinh250.sflo">
         <Header>
            <Title>Location</Title>
         </Header>
         <FuncDesc>The ship-from location.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="whinh250.sfit">
         <Header>
            <Title>Ship-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="whinh250.sfrv">
         <Header>
            <Title>Revision</Title>
         </Header>
         <FuncDesc>The revision code of the item.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="whinh250.pddt">
         <Header>
            <Title>Planned Delivery Date</Title>
         </Header>
         <FuncDesc>The date for which delivery of a shipment is planned.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="whinh250.stty">
         <Header>
            <Title>Code</Title>
         </Header>
         <FuncDesc>The ship-to type is used, together with the ship-to code, to
		identify where goods are shipped to.</FuncDesc>
         <SimpleSection>
            <List>
               <ListIntro>The ship-to type can have the following values:</ListIntro>
               <ListItem> 
                  <GUIRef href="/baanerp/tc/domains/typs#partner" role="option">Business Partner</GUIRef>
               </ListItem>
               <ListItem> 
                  <GUIRef href="/baanerp/tc/domains/typs#warehouse" role="option">Warehouse</GUIRef>
               </ListItem>
               <ListItem> 
                  <GUIRef href="/baanerp/tc/domains/typs#work.center" role="option">Work Center</GUIRef>
               </ListItem>
               <ListItem> 
                  <GUIRef href="/baanerp/tc/domains/typs#project" role="option">Project</GUIRef>
               </ListItem>
            </List>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="type.to.cwar">
         <Header>
            <Title>Code</Title>
         </Header>
         <FuncDesc>The type of warehouse to which the goods are shipped.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="whinh250.stco">
         <Header>
            <Title>Code</Title>
         </Header>
         <FuncDesc>A code used, together with the ship-to type, to identify where
		goods are shipped to.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="whinh250.stad">
         <Header>
            <Title>Address</Title>
         </Header>
         <FuncDesc>The address to which the goods must be shipped.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="whinh250.stlo">
         <Header>
            <Title>Location</Title>
         </Header>
         <FuncDesc>The ship-to location.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="whinh250.stit">
         <Header>
            <Title>Ship-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="whinh250.strv">
         <Header>
            <Title>Revision</Title>
         </Header>
         <FuncDesc>The revision code of the item.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="whinh250.prdt">
         <Header>
            <Title>Planned Receipt Date</Title>
         </Header>
         <FuncDesc>The date for which delivery of a shipment is planned.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="whinh250.scon">
         <Header>
            <Title>Shipping Constraint</Title>
         </Header>
         <FuncDesc> 
            <Link href="/baanerp/wh/inh/whinh2100m000#whinh200.scon" role="formfield">Shipping Constraint</Link>
         </FuncDesc>
      </FieldHelp>
      <FieldHelp ID="whinh250.iscn">
         <Header>
            <Title>Ignore Shipping Constraint</Title>
         </Header>
         <FuncDesc> 
            <Link href="/baanerp/wh/inh/whinh2100m000#whinh200.iscn" role="formfield">Ignore Shipping Constraint</Link>
         </FuncDesc>
      </FieldHelp>
      <FieldHelp ID="whinh250.mint">
         <Header>
            <Title>Minimum Quantity Tolerance</Title>
         </Header>
         <FuncDesc>If the warehousing order is of the <Link href="/baanerp/wh/glossary/glossary#000373" role="glossary">Receipt</Link> transaction type,
		  this field shows the greatest negative deviation from the ordered quantity that
		  is tolerated, expressed in a percentage. The <GUIRef href="/baanerp/wh/inh/whinh2110m000#whinh210.hstq" role="manual">Quantity</GUIRef> field in
		  the <GUIRef href="/baanerp/wh/inh/whinh2110m000" role="session">Inbound Order Lines (whinh2110m000)</GUIRef> session indicates which action LN carries out if the
		  tolerance is not met.</FuncDesc>
         <SimpleSection>
            <Paragraph>If the warehousing order is of transaction
			 type <Link href="/baanerp/wh/glossary/glossary#000339" role="glossary">issue</Link>, this field shows the
			 minimum percentage of the ordered quantity that must be shipped. The highest
			 percentage that you can specify is 100%. If the minimum quantity is 0%, you do
			 not have shipping constraints; so, you can ship any percentage of the ordered
			 quantity.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="whinh250.maxt">
         <Header>
            <Title>Maximum Quantity Tolerance</Title>
         </Header>
         <FuncDesc>If the warehousing order is of the <Link href="/baanerp/wh/glossary/glossary#000373" role="glossary">Receipt</Link> transaction type,
		  this field shows the greatest positive deviation of the ordered quantity that
		  is tolerated, expressed in a percentage. The <GUIRef href="/baanerp/wh/inh/whinh2110m000#whinh210.hstq" role="manual">Quantity</GUIRef> field in
		  the <GUIRef href="/baanerp/wh/inh/whinh2110m000" role="session">Inbound Order Lines (whinh2110m000)</GUIRef> session indicates which action LN carries out if the
		  tolerance is not met.</FuncDesc>
         <SimpleSection>
            <Paragraph>If the warehousing order is of the <Link href="/baanerp/wh/glossary/glossary#000339" role="glossary">Issue</Link> transaction type, this field shows the greatest positive deviation from the
			 ordered quantity that is tolerated to be shipped, expressed in a percentage.
			 The <GUIRef href="/baanerp/wh/inh/whinh2120m000#whinh220.hstq" role="manual">Hard Stop on Quantity</GUIRef> field in the <GUIRef href="/baanerp/wh/inh/whinh2120m000" role="session">Outbound Order Lines (whinh2120m000)</GUIRef> session indicates which action LN carries out if the
			 tolerance is not met.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="whinh250.mind">
         <Header>
            <Title>Minimum Time Tolerance</Title>
         </Header>
         <FuncDesc>The number of days that the supplier is allowed to deliver too
		  early.</FuncDesc>
         <SimpleSection>
            <Paragraph>Deliveries before this limit, are
			 signalled, blocked, or ignored.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="whinh250.maxd">
         <Header>
            <Title>Maximum Time Tolerance</Title>
         </Header>
         <FuncDesc>The number of days that the supplier is allowed to deliver too
		  late.</FuncDesc>
         <SimpleSection>
            <Paragraph>Deliveries after this limit, are signalled,
			 blocked, or ignored.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="whinh250.carr">
         <Header>
            <Title>Carrier</Title>
         </Header>
         <FuncDesc>An organization that provides transport services. You can link
		a default carrier to both ship-to and ship-from business partners. In addition,
		you can print sales and purchase orders on a packing list, sorted by carrier.</FuncDesc>
         <SimpleSection>
            <Paragraph>For ordering and invoicing, you must define a carrier as a
		  business partner.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="whinh250.crte">
         <Header>
            <Title>Route</Title>
         </Header>
         <FuncDesc>Line of travel from your warehouses to the ship-to or ship-from
		business partner's warehouse and vice versa. Use routes to group business
		partners that are located in the same area or along one convenient route.</FuncDesc>
         <SimpleSection>
            <Paragraph>You can arrange addresses by routes to print picking lists
		  and shipping notes sorted by route.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="whinh250.cdec">
         <Header>
            <Title>Delivery Terms</Title>
         </Header>
         <FuncDesc>The terms or agreements concerning the delivery of goods.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="whinh250.refe">
         <Header>
            <Title>Reference</Title>
         </Header>
         <FuncDesc>A reference text that provides information about the order.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="whinh250.info">
         <Header>
            <Title>Information</Title>
         </Header>
         <FuncDesc>An information text that provides information about the order.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="whinh250.akit">
         <Header>
            <Title>Assembly Kit</Title>
         </Header>
         <FuncDesc>An order-dependent set of items that must be supplied together
		to the shop-floor warehouse.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="whinh200.lccl" OtherIDs="lccl.dsca">
         <Header>
            <Title>Landed Cost Classification</Title>
         </Header>
         <FuncDesc>Attribute that allows users to link a logistic transaction to a
		specific <Link href="/baanerp/tc/glossary/glossary#000481" role="glossary">landed costs set</Link>, overruling the landed costs settings
		of that transaction. If required, users can specify a landed costs
		classification and use this classification on the transaction.</FuncDesc>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <List>
               <ListIntro>This optional field is only available if these
					 conditions are met:</ListIntro>
               <ListItem>
                  <Link href="/baanerp/tc/glossary/glossary#000477" role="glossary">Landed costs</Link> functionality is used.</ListItem>
               <ListItem>The order is a <Link href="/baanerp/td/glossary/glossary#PurchaOrders_td" role="glossary">purchase order</Link> or a <Link href="/baanerp/ti/glossary/glossary#000077" role="glossary">warehouse transfer</Link>.</ListItem>
            </List>
         </Note>
         <RelatedTopics>
            <SectionTitle>Related topics</SectionTitle>
            <RelTopic>
               <Link href="/baanerp/tc/onlinemanual/000530" role="manual">Landed costs – overview</Link>
            </RelTopic>
         </RelatedTopics>
      </FieldHelp>
      <FieldHelp ID="main.item.sales">
         <Header>
            <Title>Main Item</Title>
         </Header>
         <FuncDesc>The main item of the sales order. When the sales order is
		  released to <GUIRef href="/baanerp/wh" role="package">Warehousing</GUIRef>, the value is retrieved from the <GUIRef href="/baanerp/td/sls/tdsls4561m000" role="session">Sales Order Main Items (tdsls4561m000)</GUIRef> session.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="main.item.so.dsca">
         <Header>
            <Title>Description</Title>
         </Header>
         <FuncDesc>The description of the main item.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="whinh250.sfcp">
         <Header>
            <Title>Company</Title>
         </Header>
         <FuncDesc>The company from which the goods are shipped.</FuncDesc>
         <SimpleSection>
            <Paragraph>The ship-from company is the logistic
			 company to which the warehouse in the <GUIRef href="/baanerp/wh/inh/whinh2550m000#whinh250.sfco" role="manual">Code</GUIRef> field belongs.</Paragraph>
         </SimpleSection>
         <SimpleSection>
            <SectionTitle> Note</SectionTitle>
            <List>
               <ListIntro>Only take this field into account if the warehousing
				order concerns a multicompany warehouse transfer. A warehousing order is a
				multicompany warehouse transfer if:</ListIntro>
               <ListItem>The inventory-transaction type is <GUIRef href="/baanerp/wh/domains/inh.ittp#transfer" role="option">Transfer</GUIRef>.</ListItem>
               <ListItem>The value in the <GUIRef href="/baanerp/wh/inh/whinh2550m000#whinh250.sfty" role="manual">Code</GUIRef> field in the <GUIRef href="/baanerp/wh/inh/whinh2550m000#inh200.shpf" role="groupbox">Ship-From</GUIRef> group box
				and the <GUIRef href="/baanerp/wh/inh/whinh2550m000#whinh250.stty" role="manual">Code</GUIRef> field in the <GUIRef href="/baanerp/wh/inh/whinh2550m000#whgen.sttc" role="groupbox">Ship-To</GUIRef> group box is <GUIRef href="/baanerp/tc/domains/typs#warehouse" role="option">Warehouse</GUIRef>.</ListItem>
               <ListItem>The warehouses specified in the <GUIRef href="/baanerp/wh/inh/whinh2550m000#whinh250.sfco" role="manual">Code</GUIRef> field in the <GUIRef href="/baanerp/wh/inh/whinh2550m000#inh200.shpf" role="groupbox">Ship-From</GUIRef> group box
				and the <GUIRef href="/baanerp/wh/inh/whinh2550m000#whinh250.stco" role="manual">Code</GUIRef> field in the <GUIRef href="/baanerp/wh/inh/whinh2550m000#whgen.sttc" role="groupbox">Ship-To</GUIRef> group box
				belong to different <Link href="/baanerp/tc/glossary/glossary#LogistCompan_tc" role="glossary">logistic companies</Link>.</ListItem>
            </List>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="whinh250.stcp">
         <Header>
            <Title>Company</Title>
         </Header>
         <FuncDesc>The company to which the goods are shipped.</FuncDesc>
         <SimpleSection>
            <Paragraph>The ship-to company is the <Link href="/baanerp/tc/glossary/glossary#LogistCompan_tc" role="glossary">logistic company</Link> to
			 which the warehouse in the <GUIRef href="/baanerp/wh/inh/whinh2550m000#whinh250.stco" role="manual">Code</GUIRef> field belongs.</Paragraph>
         </SimpleSection>
         <SimpleSection>
            <SectionTitle> Note</SectionTitle>
         </SimpleSection>
         <SimpleSection>
            <List>
               <ListIntro>Only take this field into account if the warehousing
				order concerns a multicompany warehouse transfer. A warehousing order is a
				multicompany warehouse transfer if:</ListIntro>
               <ListItem>The inventory-transaction type is <GUIRef href="/baanerp/wh/domains/inh.ittp#transfer" role="option">Transfer</GUIRef>.</ListItem>
               <ListItem>The value in the <GUIRef href="/baanerp/wh/inh/whinh2550m000#whinh250.sfty" role="manual">Code</GUIRef> field in the <GUIRef href="/baanerp/wh/inh/whinh2550m000#inh200.shpf" role="groupbox">Ship-From</GUIRef> group box
				and the <GUIRef href="/baanerp/wh/inh/whinh2550m000#whinh250.stty" role="manual">Code</GUIRef> field in the <GUIRef href="/baanerp/wh/inh/whinh2550m000#whgen.sttc" role="groupbox">Ship-To</GUIRef> group box is <GUIRef href="/baanerp/tc/domains/typs#warehouse" role="option">Warehouse</GUIRef>.</ListItem>
               <ListItem>The warehouses specified in the <GUIRef href="/baanerp/wh/inh/whinh2550m000#whinh250.sfco" role="manual">Code</GUIRef> field in the <GUIRef href="/baanerp/wh/inh/whinh2550m000#inh200.shpf" role="groupbox">Ship-From</GUIRef> group box
				and the <GUIRef href="/baanerp/wh/inh/whinh2550m000#whinh250.stco" role="manual">Code</GUIRef> field in the <GUIRef href="/baanerp/wh/inh/whinh2550m000#whgen.sttc" role="groupbox">Ship-To</GUIRef> group box
				belong to different <Link href="/baanerp/tc/glossary/glossary#LogistCompan_tc" role="glossary">logistic companies</Link>.</ListItem>
            </List>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="tcstl210.fd01"
                 OtherIDs="tcstl210.fd02 tcstl210.fd03 tcstl210.fd04 tcstl210.fd05 tcstl210.fd06 tcstl210.fd07 tcstl210.fd08 tcstl210.fd09 tcstl210.fd10">
         <Header>
            <Title>Additional Information</Title>
         </Header>
         <FuncDesc>User-defined fields that can be linked to LN tables.</FuncDesc>
         <SimpleSection>
            <Paragraph>The contents of additional fields can be transferred between LN tables. Additional
		  information fields are meaningless to LN as no functional logic is linked to the contents
		  of these fields.</Paragraph>
         </SimpleSection>
         <RelatedTopics>
            <SectionTitle> Related topics</SectionTitle>
            <RelTopic>
               <Link href="/baanerp/wh/onlinemanual/000560" role="manual">Additional information fields</Link>
            </RelTopic>
            <RelTopic>
               <Link href="/baanerp/wh/onlinemanual/000565" role="manual">Additional information fields - <GUIRef href="/baanerp/wh" role="package">Warehousing</GUIRef>
               </Link>
            </RelTopic>
         </RelatedTopics>
      </FieldHelp>
   </Fields>
   <FormCommands>
      <CommandHelp ID="view.last.transactions">
         <Header>
            <Title>View Last Transactions</Title>
         </Header>
         <FuncDesc>Shows only the last transaction.</FuncDesc>
      </CommandHelp>
      <CommandHelp ID="inbound.order.lines">
         <Header>
            <Title>Inbound Order Lines</Title>
         </Header>
         <FuncDesc>Starts the <GUIRef href="/baanerp/wh/inh/whinh2560m000" role="session">Inbound Order Line History (whinh2560m000)</GUIRef> session in which you can view the <Link href="/baanerp/wh/glossary/glossary#000396" role="glossary">inbound-order lines</Link> history.</FuncDesc>
      </CommandHelp>
      <CommandHelp ID="outbound.order.lines">
         <Header>
            <Title>Outbound Order Lines</Title>
         </Header>
         <FuncDesc>Starts the <GUIRef href="/baanerp/wh/inh/whinh2570m000" role="session">Outbound Order Line History (whinh2570m000)</GUIRef> session in which you can view the <Link href="/baanerp/wh/glossary/glossary#000407" role="glossary">outbound-order lines</Link> history.</FuncDesc>
      </CommandHelp>
   </FormCommands>
</Session>