<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/wh/inp/whinp1500m000" xml:lang="en">
   <Header>
      <Title>Planned Inventory Transactions (whinp1500m000)</Title>
   </Header>
   <HelpTopic>
      <AimSection>
         <Paragraph> Use this session to view the <Link href="/baanerp/wh/glossary/glossary#000012" role="glossary">planned inventory transactions</Link> by item.</Paragraph>
      </AimSection>
      <GeneralSection>
         <Paragraph>After each entry, the originating module
		  creates a planned inventory transaction. The planned inventory transaction is
		  removed when a warehouse order is generated.</Paragraph>
      </GeneralSection>
      <RelatedTopics>
         <SectionTitle> Related topics</SectionTitle>
         <RelTopic>
            <Link href="/baanerp/wh/onlinemanual/000035" role="manual">Planned inventory transactions</Link>
         </RelTopic>
      </RelatedTopics>
   </HelpTopic>
   <Fields>
      <FieldGroup>
         <Title> General Data</Title>
         <FieldHelp ID="spcn.yn">
            <Header>
               <Title>Specification</Title>
            </Header>
            <FuncDesc> If this check box is selected, <Link href="/baanerp/tc/glossary/glossary#000455" role="glossary" Update="No">specifications</Link> are present for the items included in the
			 current planned inventory transactions. Specification information is available
			 in the fields of the <GUIRef href="/baanerp/wh/inp/whinp1500m000#gen.demand.peg" role="groupbox">Demand Peg</GUIRef> group box of the details
			 session.</FuncDesc>
            <RelatedTopics>
               <SectionTitle> Related topics</SectionTitle>
               <RelTopic>
                  <Link href="/baanerp/cp/onlinemanual/000460" role="manual">Demand pegging overview</Link>
               </RelTopic>
            </RelatedTopics>
         </FieldHelp>
         <FieldGroup>
            <Title> Order</Title>
            <FieldHelp ID="whinp100.koor">
               <Header>
                  <Title>Originating Type of Order</Title>
               </Header>
               <FuncDesc>The <Link href="/baanerp/td/glossary/glossary#OrderType_td" role="glossary">order type</Link> of the order from which the planned inventory transaction is
				generated.</FuncDesc>
               <Note>
                  <SectionTitle> Note</SectionTitle>
                  <Paragraph>The originating type of order for
				  planned inventory transactions generated from unapproved purchase orders is <GUIRef href="/baanerp/tc/domains/koor#act.pur.adv" role="option">Purchase Order Advice</GUIRef>. After the purchase order is approved in the <GUIRef href="/baanerp/td/pur" role="module">Purchase Control</GUIRef> module
				  of the <GUIRef href="/baanerp/procurement" role="package">Procurement</GUIRef> package, the originating type of order of the planned inventory transaction
				  changes to <GUIRef href="/baanerp/tc/domains/koor#act.pur" role="option">Purchase Order</GUIRef>. For further information about order procedures in <GUIRef href="/baanerp/td/pur" role="module">Purchase Control</GUIRef>, see <Link href="/baanerp/td/onlinemanual/000040" role="manual">Purchase order procedure</Link>.</Paragraph>
               </Note>
            </FieldHelp>
            <FieldHelp ID="whinp100.orno">
               <Header>
                  <Title>Order</Title>
               </Header>
               <FuncDesc>This number indicates which order or contract causes the
				inventory transaction to take place.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="whinp100.pono">
               <Header>
                  <Title>Order Line</Title>
               </Header>
               <FuncDesc>The position number of the order or contract line that
				causes the planned inventory transaction to take place.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="whinp100.ponb">
               <Header>
                  <Title>Order Line</Title>
               </Header>
               <FuncDesc>The order line <Link href="/baanerp/tc/glossary/glossary#SequenNumber_tc" role="glossary">sequence number</Link>.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="whinp100.boml">
               <Header>
                  <Title>BOM Line</Title>
               </Header>
               <FuncDesc>The line number within the bill of material.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="whinp100.dlin">
               <Header>
                  <Title>Distribution Line</Title>
               </Header>
               <FuncDesc>The <Link href="/baanerp/tc/glossary/glossary#SequenNumber_tc" role="glossary">sequence number</Link> of the distribution line in the order
				line peg distributions.</FuncDesc>
               <Note>
                  <SectionTitle>Note</SectionTitle>
                  <Paragraph>This field is enabled only if the <GUIRef href="/baanerp/tc/com/tccom0100s000#tccom000.ppeg" role="manual">Project Pegging</GUIRef> functionality is
				  implemented.</Paragraph>
               </Note>
            </FieldHelp>
            <FieldHelp ID="whinp100.date">
               <Header>
                  <Title>Transaction Date</Title>
               </Header>
               <FuncDesc>The date on which the inventory transaction will take
				place.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="whinp100.kotr">
               <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="whinp100.corn">
               <Header>
                  <Title>Customer Order Number</Title>
               </Header>
               <FuncDesc>The number of the <Link href="/baanerp/tc/glossary/glossary#SoldtoBusine_tc" role="glossary"
                        Update="No">sold-to business partner's</Link> purchase order.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="chance.perc">
               <Header>
                  <Title>Probability Percentage</Title>
               </Header>
               <FuncDesc>The success percentage indicates the probability that the
				deliveries listed in the quotation will be realized by a purchase order.</FuncDesc>
            </FieldHelp>
         </FieldGroup>
         <FieldGroup>
            <Title> Item</Title>
            <FieldHelp ID="whinp100.cwar">
               <Header>
                  <Title>Warehouse</Title>
               </Header>
               <FuncDesc>A place for storing goods. For each warehouse, you can enter
		address data and data relating to its type.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="whinp100.typw">
               <Header>
                  <Title>Warehouse Type</Title>
               </Header>
               <FuncDesc>The type of warehouse indicates the purposes for which you
				can use the warehouse. The warehouse type also determines the data and settings
				that you can define for the warehouse.</FuncDesc>
               <SimpleSection>
                  <Paragraph> 
                     <Link href="/baanerp/tc/domains/typw" role="domain">Type of warehouse</Link>
                  </Paragraph>
               </SimpleSection>
               <RelatedTopics>
                  <SectionTitle> Related topics</SectionTitle>
                  <RelTopic>
                     <Link href="/baanerp/wh/onlinemanual/wmd00201" role="manual">Using warehouses</Link>
                  </RelTopic>
                  <RelTopic>
                     <Link href="/baanerp/wh/onlinemanual/000459" role="manual">Financial warehouses</Link>
                  </RelTopic>
               </RelatedTopics>
            </FieldHelp>
            <FieldHelp ID="whinp100.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="whinp100.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="whinp100.qana">
               <Header>
                  <Title>Planned Quantity</Title>
               </Header>
               <FuncDesc>The quantity by which the inventory will be adjusted.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="whinp100.qinp">
               <Header>
                  <Title>In Process Quantity</Title>
               </Header>
               <FuncDesc>The quantity that is shipped but not yet
				received.</FuncDesc>
               <Note>
                  <SectionTitle> Note</SectionTitle>
                  <Paragraph>The field is applicable only for
				  transfers.</Paragraph>
               </Note>
            </FieldHelp>
            <FieldHelp ID="whinp100.cuni">
               <Header>
                  <Title>Unit</Title>
               </Header>
               <FuncDesc>The unit in which the quantity is expressed.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="whinp100.expl">
               <Header>
                  <Title>Exclude from Planning</Title>
               </Header>
               <FuncDesc>If quantity 1 is filled in this field, the planned
				inventory transaction is not taken into account for Material Requirement
				Planning and <Link href="/baanerp/cp/glossary/glossary#000030" role="glossary">available-to-promise</Link>.</FuncDesc>
               <SimpleSection>
                  <Paragraph>Planned inventory transactions are
				  excluded from Material Requirement Planning and <Link href="/baanerp/cp/glossary/glossary#000030" role="glossary">available-to-promise</Link> if all of the following conditions
				  apply:</Paragraph>
                  <List>
                     <ListItem>The item is a <Link href="/baanerp/wh/onlinemanual/000382#382_low_volume" role="manual" Update="No">low volume</Link> serialized item.</ListItem>
                     <ListItem> 
                        <List>
                           <ListIntro>The status of the serialized item is either of the
						  following:</ListIntro>
                           <ListItem> 
                              <GUIRef href="/baanerp/tc/domains/ibd.ssts#defective" role="option">Defective</GUIRef>
                           </ListItem>
                           <ListItem> 
                              <GUIRef href="/baanerp/tc/domains/ibd.ssts#working.cond" role="option">Working Condition</GUIRef>
                           </ListItem>
                           <ListItem> 
                              <GUIRef href="/baanerp/tc/domains/ibd.ssts#to.be.recycled" role="option">To be Recycled</GUIRef>
                           </ListItem>
                           <ListItem> 
                              <GUIRef href="/baanerp/tc/domains/ibd.ssts#removed" role="option">Removed</GUIRef>
                           </ListItem>
                        </List>
                     </ListItem>
                     <ListItem> 
                        <List>
                           <ListIntro>The origin is:</ListIntro>
                           <ListItem> 
                              <GUIRef href="/baanerp/wh/domains/inh.oorg#sales.man" role="option">Sales (Manual)</GUIRef>
                           </ListItem>
                           <ListItem> 
                              <GUIRef href="/baanerp/wh/domains/inh.oorg#transfer.man" role="option">Transfer (Manual)</GUIRef>
                           </ListItem>
                           <ListItem> 
                              <GUIRef href="/baanerp/ts" role="package">Service</GUIRef>
                           </ListItem>
                        </List>
                     </ListItem>
                  </List>
               </SimpleSection>
               <Note>
                  <SectionTitle> Note</SectionTitle>
                  <Paragraph>Planned inventory transactions that are
				  excluded from planning are not taken into account for the following types of
				  runs:</Paragraph>
                  <List>
                     <ListItem>SIC</ListItem>
                     <ListItem>TPOP</ListItem>
                     <ListItem>KANBAN</ListItem>
                  </List>
               </Note>
               <RelatedTopics>
                  <SectionTitle> Related topics</SectionTitle>
                  <RelTopic>
                     <Link href="/baanerp/wh/onlinemanual/000310" role="manual">To generate order advice (SIC)</Link>
                  </RelTopic>
                  <RelTopic>
                     <Link href="/baanerp/wh/onlinemanual/000311" role="manual">Kanban setup, label layout, and order generation</Link>
                  </RelTopic>
                  <RelTopic>
                     <Link href="/baanerp/wh/onlinemanual/000316" role="manual">Time-phased order point (TPOP)</Link>
                  </RelTopic>
               </RelatedTopics>
            </FieldHelp>
            <FieldHelp ID="stoc.balance">
               <Header>
                  <Title>Expected Inventory</Title>
               </Header>
               <FuncDesc>For each transaction date, ERP Enterprise displays the
				inventory expected as a result of planned inventory transactions. If there are
				multiple transaction lines for the same date, it shows the expected inventory
				at the end of the day for that date.</FuncDesc>
               <SimpleSection>
                  <Paragraph>You can display expected inventory by
				  item, which means that expected inventory for all warehouses is shown, or by
				  item and warehouse, which shows expected inventory for an item in a particular
				  warehouse. For this purpose, in the <GUIRef href="" role="manual">View</GUIRef> menu, select the
				  relevant sort option.</Paragraph>
               </SimpleSection>
            </FieldHelp>
            <FieldGroup>
               <Title>Project</Title>
               <FieldHelp ID="f.program">
                  <Header>
                     <Title>Program</Title>
                  </Header>
                  <FuncDesc>The code of the program to which the <Link href="/baanerp/tp/glossary/glossary#000063" role="glossary">project</Link> is
				  linked.</FuncDesc>
               </FieldHelp>
               <FieldHelp ID="whinp100.cprj">
                  <Header>
                     <Title>Project</Title>
                  </Header>
                  <FuncDesc>The <Link href="/baanerp/tp/glossary/glossary#000063" role="glossary">project</Link> code.</FuncDesc>
               </FieldHelp>
               <FieldHelp ID="whinp100.cspa">
                  <Header>
                     <Title>Element</Title>
                  </Header>
                  <FuncDesc>The <Link href="/baanerp/tp/glossary/glossary#Element_tp" role="glossary">element</Link> linked to the project.</FuncDesc>
               </FieldHelp>
               <FieldHelp ID="whinp100.cact">
                  <Header>
                     <Title>Activity</Title>
                  </Header>
                  <FuncDesc>The <Link href="/baanerp/tp/glossary/glossary#000005" role="glossary">activity</Link> linked to the project.</FuncDesc>
               </FieldHelp>
               <FieldHelp ID="whinp100.cstl">
                  <Header>
                     <Title>Extension</Title>
                  </Header>
                  <FuncDesc>The <Link href="/baanerp/tp/glossary/glossary#000017" role="glossary">extension</Link> code.</FuncDesc>
               </FieldHelp>
               <FieldHelp ID="whinp100.ccco">
                  <Header>
                     <Title>Cost Component</Title>
                  </Header>
                  <FuncDesc>The <Link href="/baanerp/tp/glossary/glossary#000360" role="glossary">cost component</Link>.</FuncDesc>
               </FieldHelp>
               <FieldHelp ID="whinp100.pptl">
                  <Header>
                     <Title>Peg Distribution</Title>
                  </Header>
                  <FuncDesc>If this check box is selected, peg distribution data exists for the
				  selected order.</FuncDesc>
               </FieldHelp>
            </FieldGroup>
         </FieldGroup>
      </FieldGroup>
      <FieldGroup>
         <Title> Planning Data</Title>
         <FieldGroup>
            <Title> Planning Data</Title>
            <FieldHelp ID="whinp100.plpl">
               <Header>
                  <Title>Planned by APS</Title>
               </Header>
               <FuncDesc>Integration with APS is currently not
				implemented.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="whinp100.blck">
               <Header>
                  <Title>Blocked</Title>
               </Header>
               <FuncDesc> If this check box is selected, the order is
				blocked.</FuncDesc>
               <RelatedTopics>
                  <SectionTitle> Related topics</SectionTitle>
                  <RelTopic>
                     <Link href="/baanerp/wh/onlinemanual/000000000000041" role="manual">To block and unblock</Link>
                  </RelTopic>
               </RelatedTopics>
            </FieldHelp>
            <FieldHelp ID="whinp100.cacc">
               <Header>
                  <Title>Confirmation Accepted</Title>
               </Header>
               <FuncDesc> If this check box is selected, the quantity confirmed
				by the supplier is accepted. In the <GUIRef href="/baanerp/td/pur/tdpur4101m000" role="session">Purchase Order Lines (tdpur4101m000)</GUIRef> session or the <GUIRef href="/baanerp/td/pur/tdpur4101m300" role="session">Purchase Order Line Quantities and Dates (tdpur4101m300)</GUIRef> session, the <GUIRef href="/baanerp/td/pur/tdpur4101m300#tdpur419.cfap" role="manual">Confirmation Accepted</GUIRef> check box is selected. If the
				accepted confirmed quantity is lo <Link href="/baanerp/wh/onlinemanual/000488#hard_peg_supply_orders" role="manual">To hard peg supply orders</Link> wer than the ordered
				quantity, the <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef> package generates a warning notifying the user of the
				discrepancy.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="whinp100.subc">
               <Header>
                  <Title>Contains Customer Furnished Material</Title>
               </Header>
               <FuncDesc> If this check box is selected, the planned inventory
				transaction is either:</FuncDesc>
               <SimpleSection>
                  <List>
                     <ListItem>An issue for a <Link href="/baanerp/ti/glossary/glossary#000044" role="glossary">subcontracting</Link> sales order or a materials issue for a
					 subcontracting <GUIRef href="/baanerp/ti/sfc" role="module">Shop Floor Control</GUIRef> order</ListItem>
                     <ListItem>A receipt for a subcontracting <GUIRef href="/baanerp/ti/sfc" role="module">Shop Floor Control</GUIRef> order</ListItem>
                  </List>
                  <Paragraph> If this check box is cleared, the planned inventory transaction is a receipt or an issue
				  not involved in subcontracting.</Paragraph>
               </SimpleSection>
            </FieldHelp>
            <FieldHelp ID="whinp100.inrl">
               <Header>
                  <Title>Affiliated Company</Title>
               </Header>
               <FuncDesc> If this check box is selected, the business partner is
				an <Link href="/baanerp/tc/glossary/glossary#AffiliCompan_tc" role="glossary">affiliated company</Link>.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="whinp100.iscn">
               <Header>
                  <Title>Affiliated Company Number</Title>
               </Header>
               <FuncDesc>The company number of the <Link href="/baanerp/tc/glossary/glossary#AffiliCompan_tc" role="glossary">affiliated company</Link> represented by the business partner.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="whinp100.chan">
               <Header>
                  <Title>Channel</Title>
               </Header>
               <FuncDesc>A sales or distribution channel used to assign goods to
		customer groups.</FuncDesc>
               <SimpleSection>
                  <Paragraph>You can link channels to sold-to business partners and to
		  items. Channels can be used in connection with available-to-promise (ATP).</Paragraph>
                  <Paragraph>You can assign a certain ATP volume to a channel. This volume
		  limits the ATP for that channel to a maximum.</Paragraph>
               </SimpleSection>
            </FieldHelp>
            <FieldHelp ID="whinp100.prio">
               <Header>
                  <Title>Order Priority</Title>
               </Header>
               <FuncDesc>The order priority that is considered by ERP Enterprise when generating <Link href="/baanerp/wh/glossary/glossary#000424" role="glossary">time-phased order point</Link> orders, <Link href="/baanerp/wh/glossary/glossary#000408" role="glossary">order controlled/Single</Link> orders, and transfer orders for <Link href="/baanerp/wh/glossary/glossary#000458" role="glossary">direct material supply (DMS)</Link>.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="whinp100.bpid">
               <Header>
                  <Title>Ship-from/Ship-to Business Partner</Title>
               </Header>
               <FuncDesc>The business partner linked to the transaction.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="whinp100.bfst">
               <Header>
                  <Title>Buy-from/Sold-to Business Partner</Title>
               </Header>
               <FuncDesc>The business partner linked to the transaction.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="whinp100.scon">
               <Header>
                  <Title>Shipping Constraint</Title>
               </Header>
               <FuncDesc>The terms and conditions related to the shipment of goods.</FuncDesc>
               <AllowedValues>
                  <SectionTitle> Allowed values</SectionTitle>
                  <Paragraph> 
                     <Link href="/baanerp/td/domains/scon" role="domain" Update="No">Shipping Constraint</Link>
                  </Paragraph>
               </AllowedValues>
            </FieldHelp>
            <FieldHelp ID="whinp100.oprs">
               <Header>
                  <Title>Order Promising Status</Title>
               </Header>
               <FuncDesc>If the planned inventory transaction is created from a
				sales order, this field shows the sales order line's status that is determined
				by the <GUIRef href="" role="manual">SCS Order Promising</GUIRef> server.</FuncDesc>
               <SimpleSection>
                  <Paragraph>If a sales order is created, the
				  default order promising status is <GUIRef href="/baanerp/td/domains/sls.oprs#not.accepted" role="option">Not Accepted</GUIRef>. However, when an <Link href="/baanerp/cp/glossary/glossary#000030" role="glossary">available-to-promise</Link> check
				  is performed and <GUIRef href="" role="manual">Order Promising</GUIRef> is implemented, <GUIRef href="" role="manual">Order Promising</GUIRef> processes the sales order delivery line following its rule
				  engine. If the <GUIRef href="/baanerp/td/sls/tdsls4101m000#tdsls401.susi" role="manual">Supplying Site</GUIRef> field is filled, the order promising status changes to <GUIRef href="/baanerp/td/domains/sls.oprs#accepted" role="option">Accepted</GUIRef>.</Paragraph>
               </SimpleSection>
               <DefaultValue>
                  <SectionTitle> Default value</SectionTitle>
                  <Paragraph>If the <GUIRef href="/baanerp/tc/ibd/tcibd2100s000#tcibd200.plpl" role="manual">Planned by SCM Planner</GUIRef> check box in the <GUIRef href="/baanerp/tc/ibd/tcibd2100s000" role="session">Item - Ordering (tcibd2100s000)</GUIRef> session is selected for the item, the order promising
				  status is by default set to <GUIRef href="/baanerp/td/domains/sls.oprs#not.accepted" role="option">Not Accepted</GUIRef> when a sales order line is created in the <GUIRef href="/baanerp/td/sls/tdsls4101m000" role="session">Sales Order Lines (tdsls4101m000)</GUIRef> session.</Paragraph>
               </DefaultValue>
               <SimpleSection>
                  <List>
                     <ListIntro>The default order promising status is <GUIRef href="/baanerp/td/domains/sls.oprs#not.applicable" role="option">Not Applicable</GUIRef> if:</ListIntro>
                     <ListItem>The <GUIRef href="/baanerp/tc/ibd/tcibd2100s000#tcibd200.plpl" role="manual">Planned by SCM Planner</GUIRef> check box in the <GUIRef href="/baanerp/tc/ibd/tcibd2100s000" role="session">Item - Ordering (tcibd2100s000)</GUIRef> session is cleared for the item.</ListItem>
                     <ListItem>The <GUIRef href="/baanerp/tc/ibd/tcibd2100s000#tcibd200.plpl" role="manual">Planned by SCM Planner</GUIRef> check box in the <GUIRef href="/baanerp/tc/ibd/tcibd2100s000" role="session">Item - Ordering (tcibd2100s000)</GUIRef> session is selected for the item and the <GUIRef href="/baanerp/td/sls/tdsls4101m000#tdsls401.dltp" role="manual">Delivery Type</GUIRef> field is set to <GUIRef href="/baanerp/td/domains/sls.dltp#direct.delivery" role="option">Direct Delivery</GUIRef> in the <GUIRef href="/baanerp/td/sls/tdsls4101m000" role="session">Sales Order Lines (tdsls4101m000)</GUIRef> session.</ListItem>
                     <ListItem>The <GUIRef href="/baanerp/tc/ibd/tcibd2100s000#tcibd200.plpl" role="manual">Planned by SCM Planner</GUIRef> check box in the <GUIRef href="/baanerp/tc/ibd/tcibd2100s000" role="session">Item - Ordering (tcibd2100s000)</GUIRef> session is selected for the item and the <GUIRef href="/baanerp/td/sls/tdsls4101m000#tdsls401.isss" role="manual">Inventory Handling</GUIRef> field in the <GUIRef href="/baanerp/td/sls/tdsls4101m000" role="session">Sales Order Lines (tdsls4101m000)</GUIRef> session has the value <GUIRef href="/baanerp/tc/domains/isss#issue.comp" role="option">Issue Components</GUIRef>.</ListItem>
                     <ListItem>The sales order or sales order line is created through
					 EDI.</ListItem>
                     <ListItem>The order quantity is zero.</ListItem>
                  </List>
                  <Paragraph>When an available-to-promise (ATP)
				  request is sent to the <GUIRef href="" role="manual">SCS Order Promising</GUIRef> server, the <GUIRef href="" role="manual">SCS Order Promising</GUIRef> server carries out an ATP check and sends
				  back the appropriate data to the <GUIRef href="/baanerp/td/sls" role="module">Sales Control</GUIRef> module. When the <GUIRef href="" role="manual">SCS Order Promising</GUIRef> server accepts the sales order line, the order
				  promising status is changed to <GUIRef href="/baanerp/td/domains/sls.oprs#accepted" role="option">Accepted</GUIRef>. When the <GUIRef href="" role="manual">SCS Order Promising</GUIRef> server declines the sales order line, the
				  order promising status is not changed, but remains <GUIRef href="/baanerp/td/domains/sls.oprs#not.accepted" role="option">Not Accepted</GUIRef>.</Paragraph>
                  <List>
                     <ListIntro>In the <Link href="/baanerp/td/sls/tdsls4899m000" role="session">ATP Handling (tdsls4899m000)</Link> session, the <GUIRef href="" role="manual">SCS</GUIRef> user must manually
					 carry out the ATP check for sales order lines with the order promising status <GUIRef href="/baanerp/td/domains/sls.oprs#manual" role="option">Manual</GUIRef>,
					 and for sales order lines for which the following conditions apply:</ListIntro>
                     <ListItem>The <GUIRef href="/baanerp/cp/rpd/cprpd0100m000#cprpd000.atpq" role="manual">CTP Check for Sales</GUIRef> check box in the <GUIRef href="/baanerp/cp/rpd/cprpd0100m000" role="session">Planning Parameters (cprpd0100m000)</GUIRef> session is cleared.</ListItem>
                     <ListItem>The order promising status is <GUIRef href="/baanerp/td/domains/sls.oprs#not.accepted" role="option">Not Accepted</GUIRef>. However, if a sales order line, for which the ATP check must
					 be carried out manually by an <GUIRef href="" role="manual">SCS</GUIRef> user, is released to
					 warehousing, the order promising status is changed to <GUIRef href="/baanerp/td/domains/sls.oprs#accepted" role="option">Accepted</GUIRef> without an ATP
					 check being carried out by an <GUIRef href="" role="manual">SCS</GUIRef> user.</ListItem>
                  </List>
               </SimpleSection>
               <SimpleSection>
                  <List>
                     <ListIntro>An ATP check for the sales order line is carried out
					 automatically by the <GUIRef href="" role="manual">Order Acceptance Engine</GUIRef> of the <GUIRef href="" role="manual">SCS Order Promising</GUIRef> server if the following conditions apply:</ListIntro>
                     <ListItem>The <GUIRef href="/baanerp/cp/rpd/cprpd0100m000#cprpd000.atpq" role="manual">CTP Check for Sales</GUIRef> check box in the <GUIRef href="/baanerp/cp/rpd/cprpd0100m000" role="session">Planning Parameters (cprpd0100m000)</GUIRef> session is selected.</ListItem>
                     <ListItem>The order promising status is <GUIRef href="/baanerp/td/domains/sls.oprs#not.accepted" role="option">Not Accepted</GUIRef>.</ListItem>
                  </List>
               </SimpleSection>
            </FieldHelp>
            <FieldHelp ID="whinp100.pric">
               <Header>
                  <Title>Price</Title>
               </Header>
               <FuncDesc>The
				price of the order or contract line that causes the planned inventory
				transaction to take place.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="whinp100.ccur">
               <Header>
                  <Title>Price Currency</Title>
               </Header>
               <FuncDesc>The currency in which the item price is
				expressed.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="whinp100.qorg">
               <Header>
                  <Title>Original Ordered Quantity</Title>
               </Header>
               <FuncDesc>The original planned receipt quantity that the supplier is
				committed to, or the original planned delivery quantity that the own company is
				committed to.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="whinp100.ordt">
               <Header>
                  <Title>Original Date</Title>
               </Header>
               <FuncDesc>The original planned receipt date that the supplier is
				committed to, or the original planned delivery date that the own company is
				committed to.</FuncDesc>
            </FieldHelp>
         </FieldGroup>
         <FieldGroup>
            <Title> Ownership</Title>
            <FieldHelp ID="whinp100.owns">
               <Header>
                  <Title>Ownership Behaviour</Title>
               </Header>
               <FuncDesc> 
                  <Link href="/baanerp/tc/domains/owns" role="domain">Ownership Behavior</Link>
               </FuncDesc>
               <SimpleSection>
                  <Paragraph>Note that if the inventory is owned, the
				  ownership behaviour
				  value is <GUIRef href="" role="manual">Not Applicable</GUIRef>.</Paragraph>
               </SimpleSection>
            </FieldHelp>
            <FieldHelp ID="whinp100.ownr">
               <Header>
                  <Title>Owner</Title>
               </Header>
               <FuncDesc>The <Link href="/baanerp/tc/glossary/glossary#BusinePartne_tc" role="glossary">business partner</Link> who owns the items. If this field is
				not filled, your own organization owns the inventory. If the owner is not the
				same as the <Link href="/baanerp/tc/glossary/glossary#BuyfroBusine_tc" role="glossary">buy-from business partner</Link>, the owner is the <Link href="/baanerp/tc/glossary/glossary#000074" role="glossary">internal business partner</Link> of another <Link href="/baanerp/tc/glossary/glossary#000011" role="glossary">enterprise unit</Link> such as a division in another country, of your organization. If the
				buy-from business partner is the owner, the items are held in not-owned
				consignment.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="confirmed">
               <Header>
                  <Title>Confirmed</Title>
               </Header>
               <FuncDesc> If this check box is selected,, a purchase order with a
				confirmed delivery date is present for the current planned receipt
				transaction.</FuncDesc>
            </FieldHelp>
         </FieldGroup>
      </FieldGroup>
      <FieldGroup>
         <Title> Specification</Title>
         <FieldGroup>
            <Title> Demand Peg</Title>
            <FieldHelp ID="tcibd420.albp" OtherIDs="albp.nama">
               <Header>
                  <Title>Business Partner</Title>
               </Header>
               <FuncDesc>The <Link href="/baanerp/tc/glossary/glossary#SoldtoBusine_tc" role="glossary">sold-to business partner</Link> to which the inventory was <Link href="/baanerp/cp/glossary/glossary#000450" role="glossary">allocated</Link> or the supply object was <Link href="/baanerp/cp/glossary/glossary#000451" role="glossary">hard pegged</Link>.</FuncDesc>
               <SimpleSection>
                  <Paragraph> ERP Enterprise uses this
				  characteristic to match supply and demand.</Paragraph>
               </SimpleSection>
               <RelatedTopics>
                  <SectionTitle> Related topics</SectionTitle>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000460" role="manual">Demand pegging overview</Link>
                  </RelTopic>
               </RelatedTopics>
            </FieldHelp>
            <FieldHelp ID="tcibd420.albt">
               <Header>
                  <Title>Business Object</Title>
               </Header>
               <FuncDesc>The type of order to which the inventory was allocated or
				the supply object was hard pegged, such as, <GUIRef href="/baanerp/tc/domains/albt#sales" role="option">Sales Order</GUIRef>,
				or <GUIRef href="/baanerp/tc/domains/albt#service" role="option">Service Order</GUIRef>.</FuncDesc>
               <Note>
                  <SectionTitle> Note</SectionTitle>
                  <List>
                     <ListIntro>The following fields are always used in combination;
					 together, they identify the relevant order or order line:</ListIntro>
                     <ListItem> 
                        <GUIRef href="/baanerp/wh/inp/whinp2100m000#tcibd420.albt" role="manual">Business Object</GUIRef>
                     </ListItem>
                     <ListItem> 
                        <GUIRef href="/baanerp/wh/inp/whinp2100m000#tcibd420.albo" role="manual">Business Object</GUIRef>
                     </ListItem>
                     <ListItem> 
                        <GUIRef href="/baanerp/wh/inp/whinp2100m000#tcibd420.abor" role="manual">Business Object Reference</GUIRef>
                     </ListItem>
                  </List>
               </Note>
               <AllowedValues>
                  <SectionTitle> Allowed values</SectionTitle>
                  <Paragraph> 
                     <Link href="/baanerp/tc/domains/albt" role="domain">Allocated to Business Object Type</Link>
                  </Paragraph>
               </AllowedValues>
               <RelatedTopics>
                  <SectionTitle> Related topics</SectionTitle>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000460" role="manual">Demand pegging overview</Link>
                  </RelTopic>
               </RelatedTopics>
            </FieldHelp>
            <FieldHelp ID="tcibd420.albo" OtherIDs="tcibd420.abor">
               <Header>
                  <Title>Business Object</Title>
               </Header>
               <FuncDesc>The <Link href="/baanerp/fm/glossary/glossary#000008" role="glossary">order</Link>,
				or order line, to which the inventory was <Link href="/baanerp/cp/glossary/glossary#000450" role="glossary">allocated</Link> or the supply object was <Link href="/baanerp/cp/glossary/glossary#000451" role="glossary">hard pegged</Link>.</FuncDesc>
               <SimpleSection>
                  <Paragraph> ERP Enterprise uses this
				  characteristic to match supply and demand.</Paragraph>
               </SimpleSection>
               <Note>
                  <SectionTitle> Note</SectionTitle>
                  <List>
                     <ListIntro>The following fields are always used in combination;
					 together, they identify the relevant order or order line:</ListIntro>
                     <ListItem> 
                        <GUIRef href="/baanerp/wh/inp/whinp2100m000#tcibd420.albt" role="manual">Business Object</GUIRef>
                     </ListItem>
                     <ListItem> 
                        <GUIRef href="/baanerp/wh/inp/whinp2100m000#tcibd420.albo" role="manual">Business Object</GUIRef>
                     </ListItem>
                     <ListItem> 
                        <GUIRef href="/baanerp/wh/inp/whinp2100m000#tcibd420.abor" role="manual">Business Object Reference</GUIRef>
                     </ListItem>
                  </List>
               </Note>
               <RelatedTopics>
                  <SectionTitle> Related topics</SectionTitle>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000460" role="manual">Demand pegging overview</Link>
                  </RelTopic>
               </RelatedTopics>
            </FieldHelp>
            <FieldHelp ID="tcibd420.alrf">
               <Header>
                  <Title>Reference</Title>
               </Header>
               <FuncDesc>A reference code to which the inventory was <Link href="/baanerp/cp/glossary/glossary#000450" role="glossary">allocated</Link> or the supply object was <Link href="/baanerp/cp/glossary/glossary#000451" role="glossary">hard pegged</Link>.</FuncDesc>
               <SimpleSection>
                  <Paragraph> ERP Enterprise uses this
				  characteristic to match supply and demand.</Paragraph>
               </SimpleSection>
               <SimpleSection>
                  <List>
                     <ListIntro> ERP Enterprise can use this field in two ways:</ListIntro>
                     <ListItem>If the <GUIRef href="/baanerp/wh/inp/whinp2100m000#tcibd420.albp" role="manual">Business Partner</GUIRef> field is filled, ERP Enterprise uses the <GUIRef href="/baanerp/wh/inp/whinp2100m000#tcibd420.alrf" role="manual">Reference</GUIRef> field to record a reference code defined by
					 a customer.</ListItem>
                     <ListItem>If the <GUIRef href="/baanerp/wh/inp/whinp2100m000#tcibd420.albp" role="manual">Business Partner</GUIRef> field is empty, ERP Enterprise uses the <GUIRef href="/baanerp/wh/inp/whinp2100m000#tcibd420.alrf" role="manual">Reference</GUIRef> field to record an internal
					 reference.</ListItem>
                  </List>
               </SimpleSection>
               <SimpleSection>
                  <Paragraph>You can use a reference code to keep a
				  collection of parts linked together, even if they follow different routings,
				  for example, if some of the parts are transported to a <Link href="/baanerp/td/glossary/glossary#Subcontracto_td" role="glossary">subcontractor</Link> to be returned later.</Paragraph>
               </SimpleSection>
               <RelatedTopics>
                  <SectionTitle> Related topics</SectionTitle>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000460" role="manual">Demand pegging overview</Link>
                  </RelTopic>
               </RelatedTopics>
            </FieldHelp>
         </FieldGroup>
         <FieldHelp ID="tcibd420.cpva">
            <Header>
               <Title>Derived from Product Variant</Title>
            </Header>
            <FuncDesc>A unique configuration of a configurable item. The variant
		results from the configuration process and includes information such as feature
		options, components, and operations.</FuncDesc>
            <ExampleSection>
               <SectionTitle>Example</SectionTitle>
               <Paragraph>Configurable item: electric drill</Paragraph>
               <List>
                  <ListIntro>Options:</ListIntro>
                  <ListItem>3 power sources (batteries, 12 V or 220 V)</ListItem>
                  <ListItem>2 colors (blue, gray).</ListItem>
               </List>
               <Paragraph>A total of 6 product variants can be produced with these
		  options.</Paragraph>
            </ExampleSection>
            <RelatedTopics>
               <SectionTitle> Related topics</SectionTitle>
               <RelTopic>
                  <Link href="/baanerp/wh/onlinemanual/000580" role="manual">Product variants in <GUIRef href="/baanerp/wh" role="package">Warehousing</GUIRef>
                  </Link>
               </RelTopic>
            </RelatedTopics>
         </FieldHelp>
         <FieldHelp ID="cpva.dsca">
            <Header>
               <Title>Product Variant</Title>
            </Header>
            <FuncDesc> The description or name of the code.</FuncDesc>
            <RelatedTopics>
               <SectionTitle> Related topics</SectionTitle>
               <RelTopic>
                  <Link href="/baanerp/wh/onlinemanual/000580" role="manual">Product variants in <GUIRef href="/baanerp/wh" role="package">Warehousing</GUIRef>
                  </Link>
               </RelTopic>
            </RelatedTopics>
         </FieldHelp>
      </FieldGroup>
      <FieldHelp ID="tcibd420.olid">
         <Header>
            <Title>Option List ID</Title>
         </Header>
         <FuncDesc>The identification of the options and features for a configured
		item. The ID is used in the item specification to match supply and
		demand.</FuncDesc>
         <SimpleSection>
            <Paragraph>The ASN specifications include the <Link href="/baanerp/tc/glossary/glossary#000442" role="glossary">option list ID</Link>. The ASN specifications are populated from the <GUIRef href="/baanerp/wh/inh/whinh2110m000" role="session">Inbound Order Lines (whinh2110m000)</GUIRef> session. In turn, the specifications on the inbound
			 order line are populated from the purchase schedule line.</Paragraph>
            <Paragraph>For configurable purchased items in <GUIRef href="/baanerp/wh" role="package">Warehousing</GUIRef>, only the
			 option list ID is part of the specifications. This means that inventory is
			 maintained per option list ID and is the total of inventory of all product
			 variants with the same option list ID.</Paragraph>
         </SimpleSection>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <List>
               <ListItem>
                  <Paragraph>The field is displayed only if the <GUIRef href="/baanerp/tc/com/tccom0100s000#tccom000.asci" role="manual">Assembly Control (ASC)</GUIRef> check box is selected in the <GUIRef href="/baanerp/tc/com/tccom0100s000" role="session">Implemented Software Components (tccom0100s000)</GUIRef> session.</Paragraph>
               </ListItem>
               <ListItem>
                  <Paragraph>The field is populated only for configurable purchased
				  items and manufactured assembly (FAS) items.</Paragraph>
               </ListItem>
            </List>
         </Note>
         <RelatedTopics>
            <SectionTitle>Related topics</SectionTitle>
            <RelTopic>
               <Link href="/baanerp/wh/onlinemanual/000640" role="manual">Configurable purchased items in Warehousing</Link>
            </RelTopic>
            <RelTopic>
               <Link href="/baanerp/wh/onlinemanual/000641" role="manual">Changing the configuration of the purchased configurable item</Link>
            </RelTopic>
         </RelatedTopics>
      </FieldHelp>
   </Fields>
   <FormCommands>
      <CommandHelp ID="configuration.button">
         <Header>
            <Title>Option List</Title>
         </Header>
         <FuncDesc>Displays the options and features that are linked to the option
		  list ID. For more information, refer to.</FuncDesc>
         <SimpleSection>
            <List>
               <ListItem>
                  <Link href="/baanerp/wh/onlinemanual/000640" role="manual">Configurable purchased items in Warehousing</Link>
               </ListItem>
               <ListItem>
                  <Link href="/baanerp/wh/onlinemanual/000641" role="manual">Changing the configuration of the purchased configurable item</Link>
               </ListItem>
            </List>
         </SimpleSection>
      </CommandHelp>
      <CommandHelp ID="whinp1400m000">
         <Header>
            <Title>Print Planned Inventory Transactions by Item</Title>
         </Header>
         <FuncDesc>Starts the <GUIRef href="/baanerp/wh/inp/whinp1400m000" role="session">Print Planned Inventory Transactions by Item (whinp1400m000)</GUIRef> session.</FuncDesc>
      </CommandHelp>
      <CommandHelp ID="option.show.chart">
         <Header>
            <Title>View Chart</Title>
         </Header>
         <FuncDesc>Starts the <GUIRef href="/baanerp/wh/inp/whinp1700m000" role="session">Planned Inventory Transactions - Chart (whinp1700m000)</GUIRef> session.</FuncDesc>
      </CommandHelp>
      <CommandHelp ID="whinp1200m000">
         <Header>
            <Title>Rebuild Planned Inventory Transactions</Title>
         </Header>
         <FuncDesc>Starts the <GUIRef href="/baanerp/wh/inp/whinp1200m000" role="session">Rebuild Planned Inventory Transactions (whinp1200m000)</GUIRef> session.</FuncDesc>
      </CommandHelp>
      <CommandHelp ID="open.pegging.relations">
         <Header>
            <Title>Pegging Relations</Title>
         </Header>
         <FuncDesc>(to be implemented)</FuncDesc>
      </CommandHelp>
      <CommandHelp ID="peg.distribution">
         <Header>
            <Title>Peg Distribution</Title>
         </Header>
         <FuncDesc>Starts the <GUIRef href="/baanerp/wh/inp/whinp1501m000" role="session">Order - Planned Inventory Transactions (whinp1501m000)</GUIRef> session with the peg
		  details.</FuncDesc>
      </CommandHelp>
      <CommandHelp ID="view.peg.lines">
         <Header>
            <Title>Peg Details</Title>
         </Header>
         <FuncDesc>Toggles the view between order line level and the peg
		  distribution level within the planned inventory transactions.</FuncDesc>
      </CommandHelp>
   </FormCommands>
</Session>