<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/wh/inh/whinh4551s000" xml:lang="en">
   <Header>
      <Title>Shipment Line History (whinh4551s000)</Title>
   </Header>
   <HelpTopic>
      <AimSection>
         <Paragraph>Use this session to view the history of <Link href="/baanerp/wh/glossary/glossary#000053" role="glossary">shipment lines</Link>.</Paragraph>
      </AimSection>
   </HelpTopic>
   <Fields>
      <FieldHelp ID="whinh451.shpm">
         <Header>
            <Title>Shipment Line</Title>
         </Header>
         <FuncDesc>All goods that are transported to a specific address on a
		specific date and time by using a specific route. An identifiable part of a
		load.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="whinh451.pono">
         <Header>
            <Title>Shipment Line</Title>
         </Header>
         <FuncDesc>The shipment line's position number.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="whinh451.item">
         <Header>
            <Title>Item</Title>
         </Header>
         <FuncDesc>In ERP Enterprise,
		the raw materials, subassemblies, finished products, and tools that can be
		purchased, stored, manufactured, sold, and so on.</FuncDesc>
         <SimpleSection>
            <Paragraph>An item can also represent a set of items handled as one kit,
		  or exist in multiple product variants.</Paragraph>
            <List>
               <ListIntro>You can also define nonphysical items, which are not held
			 in inventory but can be used to post costs or to invoice services to customers.
			 The following are examples of nonphysical items:</ListIntro>
               <ListItem>Cost items (for example, electricity)</ListItem>
               <ListItem>Service items</ListItem>
               <ListItem>Subcontracting services</ListItem>
               <ListItem>List items (menus/options)</ListItem>
            </List>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="whinh210.bgxc">
         <Header>
            <Title>Budget Exception</Title>
         </Header>
         <FuncDesc>If this check box is selected, the budget check process for the line has not
			 been completed successfully. A budget exception is generated in ERP Enterprise. The field is always
			 disabled. For more information, refer to <Link href="/baanerp/wh/onlinemanual/000650" role="manual">Budget control in Warehousing</Link>.</FuncDesc>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <List>
               <ListItem>The check box is displayed only if the <GUIRef href="/baanerp/tf/bgc" role="module">Budget Control</GUIRef> is
				  implemented. To enable <GUIRef href="/baanerp/tf/bgc" role="module">Budget Control</GUIRef>, you must select the <GUIRef href="/baanerp/tc/com/tccom0100s000#tccom000.bgci" role="manual">Budget Control</GUIRef> check box in the <GUIRef href="/baanerp/tc/com/tccom0100s000" role="session">Implemented Software Components (tccom0100s000)</GUIRef> session.</ListItem>
               <ListItem>The check box is not displayed if the <GUIRef href="/baanerp/tf/bgc/tfbgc0110m000#tfbgc010.rcca" role="manual">Check Available Budget</GUIRef> check box is not selected in
				  the <GUIRef href="/baanerp/tf/bgc/tfbgc0110m000#bgc.issues" role="groupbox">Issues</GUIRef> tab in the <GUIRef href="/baanerp/tf/bgc/tfbgc0110m000" role="session">Budget Control Policy (tfbgc0110m000)</GUIRef> session.</ListItem>
               <ListItem>
                  <Paragraph>For manual warehousing orders, you must select the <GUIRef href="/baanerp/wh/inh/whinh0110m000#whinh010.gpil" role="manual">Generate Planned Inbound Order Lines</GUIRef> for <GUIRef href="/baanerp/wh/domains/inr.sel.tran#receipt" role="option">Receipt Transactions</GUIRef> parameter check box in the <GUIRef href="/baanerp/wh/inh/whinh0110m000" role="session">Warehousing Order Types (whinh0110m000)</GUIRef> session.</Paragraph>
               </ListItem>
               <ListItem>
                  <List>
                     <ListIntro>The field is applicable only for these order
						origins:</ListIntro>
                     <ListItem>Production Manual (return orders)</ListItem>
                     <ListItem>Service Manual (return orders)</ListItem>
                  </List>
                  <Paragraph>The <GUIRef href="/baanerp/wh/domains/inh.oorg#transfer.man" role="option">Transfer (Manual)</GUIRef> orders are allowed but the budget check process is not
					 carried out.</Paragraph>
               </ListItem>
            </List>
         </Note>
         <SimpleSection>
            <Paragraph>When a manual inbound order line is created (which is a
				return order), the corresponding data in the <GUIRef href="/baanerp/tc/bgc/tcbgc1100m000" role="session">Budget Account Distribution (tcbgc1100m000)</GUIRef> session also needs to be created
				manually.</Paragraph>
            <Paragraph>When a manual inbound order line is copied, the
				corresponding data in the <GUIRef href="/baanerp/tc/bgc/tcbgc1100m000" role="session">Budget Account Distribution (tcbgc1100m000)</GUIRef> session also needs to be
				copied.</Paragraph>
            <Paragraph>When an inbound line is deleted, the corresponding data in
				the <GUIRef href="/baanerp/tc/bgc/tcbgc1100m000" role="session">Budget Account Distribution (tcbgc1100m000)</GUIRef> session also needs to be
				deleted.</Paragraph>
         </SimpleSection>
         <RelatedTopics>
            <SectionTitle>Related topics</SectionTitle>
            <RelTopic>
               <Link href="/baanerp/wh/onlinemanual/000650" role="manual">Budget control in Warehousing</Link>
            </RelTopic>
         </RelatedTopics>
      </FieldHelp>
      <FieldHelp ID="whinh451.clot">
         <Header>
            <Title>Lot</Title>
         </Header>
         <FuncDesc>The shipped item's lot code.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="whinh451.effn">
         <Header>
            <Title>Effectivity Unit</Title>
         </Header>
         <FuncDesc>A reference number, for example a sales order line or a project
		deliverable line, that is used to model deviations for a unit effective item.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="whinh451.serl">
         <Header>
            <Title>Serial Number</Title>
         </Header>
         <FuncDesc>The unique identification of a single physical item. ERP Enterprise uses a mask to
		generate the serial number. The serial number can consist of multiple data
		segments that represent, for example, a date, model and color information,
		sequence number, and so on.</FuncDesc>
         <SimpleSection>
            <Paragraph>Serial numbers can be generated for items and for tools.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="whinh451.idat">
         <Header>
            <Title>Inventory 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="whinh451.cuni">
         <Header>
            <Title>Quantity Staged</Title>
         </Header>
         <FuncDesc>The unit in which quantities are expressed.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="whinh451.qpic">
         <Header>
            <Title>Picked</Title>
         </Header>
         <FuncDesc>The quantity of items picked for the shipment line.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="whinh451.cwun">
         <Header>
            <Title>Gross Weight</Title>
         </Header>
         <FuncDesc>The unit in which the weights are expressed.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="whinh451.qshp">
         <Header>
            <Title>Shipped</Title>
         </Header>
         <FuncDesc>The actual quantity of items that is shipped after the shipment
		  is confirmed.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="whinh451.ntwt">
         <Header>
            <Title>Net Weight</Title>
         </Header>
         <FuncDesc>The shipment's net weight.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="whinh451.qnsh">
         <Header>
            <Title>Not Shipped</Title>
         </Header>
         <FuncDesc>The quantity of picked items that is not shipped.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="whinh451.worg">
         <Header>
            <Title>Order</Title>
         </Header>
         <FuncDesc>The origin of the order.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="whinh451.worn">
         <Header>
            <Title>Order</Title>
         </Header>
         <FuncDesc>The code of the warehousing order. If the order is generated by
		another package, this number will correspond to the original order number.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="whinh451.wset">
         <Header>
            <Title>/</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="whinh451.wpon">
         <Header>
            <Title>Line</Title>
         </Header>
         <FuncDesc>The warehousing order line number. If the order is generated by
		a package other than <GUIRef href="/baanerp/wh" role="package">Warehousing</GUIRef>, this number is the same as the original order line number.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="whinh451.wseq">
         <Header>
            <Title>Line</Title>
         </Header>
         <FuncDesc>The sequence number of the warehousing order line.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="whinh451.boml">
         <Header>
            <Title>BOM Line</Title>
         </Header>
         <FuncDesc>A reference number identifying a specific combination of
		manufactured and component items in a bill of material. The position number is
		subdivided by sequence numbers that are used to refer to usage of a component
		between particular dates.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="whinh451.cwar">
         <Header>
            <Title>Warehouse</Title>
         </Header>
         <FuncDesc>The warehouse code.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="whinh451.pbol">
         <Header>
            <Title>Print Bills of Lading</Title>
         </Header>
         <FuncDesc>If this check box is selected, the shipment line must
		  be printed on the bill of lading.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="whinh451.loca">
         <Header>
            <Title>Staging Location</Title>
         </Header>
         <FuncDesc>The staging location where the goods are stored before shipping
		  takes place.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="whinh451.bolp">
         <Header>
            <Title>Cluster Line</Title>
         </Header>
         <FuncDesc>The position number of the bill of lading on which one or more
		  position numbers of the shipment are clustered. This number refers to an
		  existing position number of the shipment.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="whinh451.adjs">
         <Header>
            <Title>Automatic Adjustment of Quantity Not Shipped</Title>
         </Header>
         <FuncDesc>If this check box is selected, ERP Enterprise creates and processes an automatic
		  adjustment for any quantity not shipped (that is, where the value of <GUIRef href="/baanerp/wh/inh/whinh4551s000#whinh451.qshp" role="manual">Shipped</GUIRef> is
		  less than the value of <GUIRef href="/baanerp/wh/inh/whinh4551s000#whinh451.qpic" role="manual">Picked</GUIRef>.
		  The quantity not shipped is also removed from the inventory.</FuncDesc>
         <SimpleSection>
            <Paragraph>If this check box is cleared, and there is a quantity
			 not shipped, then the quantity is left on the staging location. You can then
			 transfer that quantity to another location to create another adjustment order
			 or to return it to bulk or pick locations.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="whinh451.iadt">
         <Header>
            <Title>Inventory Adjustment Date</Title>
         </Header>
         <FuncDesc>The date on which the inventory is updated and financial
		  transactions took place.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="whinh451.recd">
         <Header>
            <Title>Reason</Title>
         </Header>
         <FuncDesc>The reason code for the adjustment.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="whinh451.qrcp">
         <Header>
            <Title>Confirmed Received Quantity</Title>
         </Header>
         <FuncDesc>The quantity received and confirmed by the customer.</FuncDesc>
         <SimpleSection>
            <Paragraph>This is used to show
			 discrepancies between the shipped quantity and the received quantity.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="whinh451.grwt">
         <Header>
            <Title>Gross Weight</Title>
         </Header>
         <FuncDesc>The gross weight of the shipment line.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="whinh451.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, ERP Enterprise 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="whinh451.hist">
         <Header>
            <Title>History Status</Title>
         </Header>
         <FuncDesc>The history status of the shipment line.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="whinh451.logn">
         <Header>
            <Title>User</Title>
         </Header>
         <FuncDesc>The login code or name of the person who last modified the
		  shipment line.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="whinh451.huid">
         <Header>
            <Title>Handling Unit</Title>
         </Header>
         <FuncDesc>A uniquely identifiable physical unit that consists of
		packaging and contents. A handling unit can contain <Link href="/baanerp/tc/glossary/glossary#000001" role="glossary">items</Link> registered in <GUIRef href="/baanerp/wh" role="package">Warehousing</GUIRef> and
		other handling units. A handling unit has a structure of packaging materials
		used to pack items, or is a part of such a structure.</FuncDesc>
         <SimpleSection>
            <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>
            <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. 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>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="whinh451.sppk">
         <Header>
            <Title>Specific Packaging</Title>
         </Header>
         <FuncDesc>ERP Enterprise selects the check box when the handling unit generated on the shipment line is
		  based on an alternative packaging definition or is based on the shipment line
		  specific handling unit template. By default, the check box is clear.</FuncDesc>
         <RelatedTopics>
            <SectionTitle>Related topics</SectionTitle>
            <RelTopic>
               <Link href="/baanerp/wh/onlinemanual/000520" role="manual">Global Update of Handling Units</Link>
            </RelTopic>
         </RelatedTopics>
      </FieldHelp>
      <FieldHelp ID="tcstl215.fd01"
                 OtherIDs="tcstl215.fd02 tcstl215.fd03 tcstl215.fd04 tcstl215.fd05 tcstl215.fd06 tcstl215.fd07 tcstl215.fd08 tcstl215.fd09 tcstl215.fd10 tcstl215.fd11 tcstl215.fd12 tcstl215.fd13 tcstl215.fd14 tcstl215.fd15 tcstl215.fd16 tcstl215.fd17 tcstl215.fd18 tcstl215.fd19 tcstl215.fd20 tcstl215.fd21 tcstl215.fd22 tcstl215.fd23 tcstl215.fd24 tcstl215.fd02 tcstl215.fd03 tcstl215.fd04 tcstl215.fd05 tcstl215.fd06 tcstl215.fd07 tcstl215.fd08 tcstl215.fd09 tcstl215.fd10 tcstl215.fd11 tcstl215.fd12 tcstl215.fd13 tcstl215.fd14 tcstl215.fd15 tcstl215.fd16 tcstl215.fd17 tcstl215.fd18 tcstl215.fd19 tcstl215.fd20 tcstl215.fd21 tcstl215.fd22 tcstl215.fd23 tcstl215.fd24 tcstl215.fd25 tcstl215.fd26">
         <Header>
            <Title>Additional Field</Title>
         </Header>
         <FuncDesc>User-defined fields that can be linked to ERP Enterprise tables.</FuncDesc>
         <SimpleSection>
            <Paragraph>The contents of additional fields can be transferred between ERP Enterprise tables. Additional
		  information fields are meaningless to ERP Enterprise 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>
</Session>