<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/td/sls/tdsls3517m000" xml:lang="en">
   <Header>
      <Title>Sequence Shipping Information (tdsls3517m000)</Title>
   </Header>
   <HelpTopic>
      <AimSection>
         <Paragraph>Use this session to view the sales
		  schedule's sequence shipping information. LN only files the
		  sequence shipping information if the sales schedule is referenced and is of the <GUIRef href="/baanerp/td/domains/sls.reltype#seqschedule" role="option">Sequence Shipping Schedule</GUIRef> type. Each sales schedule line results in one
		  sequence shipping detail line.</Paragraph>
      </AimSection>
      <GeneralSection>
         <Paragraph>The sequence shipping information informs you about the
		  sequence in which your ship-to business partner needs the items on the assembly
		  line.</Paragraph>
         <Paragraph>If the sales schedule is referenced and is of the <GUIRef href="/baanerp/td/domains/sls.reltype#seqschedule" role="option">Sequence Shipping Schedule</GUIRef> type, LN files the last revision of the related sequence shipping details
		  in the <GUIRef href="/baanerp/wh/inh/whinh4520m000" role="session">Shipping Sequence (whinh4520m000)</GUIRef> session. For more information on sequence
		  shipping details, refer to <Link href="/baanerp/td/onlinemanual/000364" role="manual">Sales schedules and Warehouse Management</Link>.</Paragraph>
         <Paragraph>In the current session, you can also view the sequence
		  shipping detail revisions.</Paragraph>
         <Paragraph>You can print sequence shipping information in the <GUIRef href="/baanerp/td/sls/tdsls3417m000" role="session">Print Sequence Shipping Information (tdsls3417m000)</GUIRef> session.</Paragraph>
      </GeneralSection>
      <RelatedTopics>
         <SectionTitle>Related topics</SectionTitle>
         <RelTopic>
            <Link href="/baanerp/td/onlinemanual/000366" role="manual">Referenced sales schedules</Link>
         </RelTopic>
      </RelatedTopics>
   </HelpTopic>
   <Fields>
      <FieldHelp ID="tdsls317.schn">
         <Header>
            <Title>Schedule</Title>
         </Header>
         <FuncDesc>A timetable of planned supply of materials. Sales schedules
		support long-term sales with frequent deliveries. All requirements for the same
		item, sold-to business partner, ship-to business partner, and delivery
		parameter are stored in the same sales schedule.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tdsls317.sctp">
         <Header>
            <Title>Schedule Type</Title>
         </Header>
         <FuncDesc>The sales schedule type, which specifies the sales schedule's
		  purpose.</FuncDesc>
         <SimpleSection>
            <Paragraph>This field can only read <GUIRef href="/baanerp/td/domains/sls.reltype#seqschedule" role="option">Sequence Shipping Schedule</GUIRef>.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="tdsls317.spon">
         <Header>
            <Title>Schedule Position</Title>
         </Header>
         <FuncDesc>The number of the sales schedule line to which the sequence
		  shipping information is related.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tdsls317.revn">
         <Header>
            <Title>Revision</Title>
         </Header>
         <FuncDesc>A number that uniquely identifies the revision of the sales
		schedule. The sales schedule revision number indicates the sales schedule
		updates that are sent by your business partner.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tdsls317.rseq">
         <Header>
            <Title>Revision Information for Sequence</Title>
         </Header>
         <FuncDesc>The revision for the sequence shipping detail.</FuncDesc>
         <SimpleSection>
            <Paragraph>Each update to a sequence shipping schedule line results in
			 a new sequence shipping detail.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="tdsls317.ddta">
         <Header>
            <Title>Delivery Date</Title>
         </Header>
         <FuncDesc>The date on which the items must be shipped for the sales
		  schedule line.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tdsls317.qoor">
         <Header>
            <Title>Quantity</Title>
         </Header>
         <FuncDesc>The quantity required on the sales schedule line.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tdsls317.cuqs">
         <Header>
            <Title>Quantity</Title>
         </Header>
         <FuncDesc>The unit in which an item is sold.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tdsls317.rdat">
         <Header>
            <Title>Receipt Date</Title>
         </Header>
         <FuncDesc>The date on which the business partner must receive the items.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tdsls317.dock">
         <Header>
            <Title>Dock Location</Title>
         </Header>
         <FuncDesc>The <Link href="/baanerp/ti/glossary/glossary#LineStatio_ti" role="glossary">line station</Link> to which the items must be delivered.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tdsls317.jseq">
         <Header>
            <Title>Job Sequence</Title>
         </Header>
         <FuncDesc>The sequence number of the job for which the items are
		  required.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tdsls317.akit">
         <Header>
            <Title>Assembly Kit</Title>
         </Header>
         <FuncDesc>The <Link href="/baanerp/wh/glossary/glossary#000300" role="glossary">assembly kit</Link> to which the required items belong.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tdsls317.refe">
         <Header>
            <Title>Reference</Title>
         </Header>
         <FuncDesc>A number that, if determined by <GUIRef href="/baanerp/ti/asc" role="module">Assembly Control</GUIRef>, refers
		to a unique combination of line station, assembly kit, and parent serial
		number.</FuncDesc>
         <SimpleSection>
            <Paragraph>A number that, if determined by <GUIRef href="/baanerp/td/pur" role="module">Purchase Control</GUIRef>, refers
		  to a unique purchase schedule call-off that is generated from <GUIRef href="/baanerp/wh" role="package">Warehousing</GUIRef>.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="tdsls317.vino">
         <Header>
            <Title>Vehicle</Title>
         </Header>
         <FuncDesc>The number of the item (vehicle) on the assembly line for which
		  the item is required. If, for example, the item is an assembly part of a car,
		  the number in the current field is the number of the car.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tdsls317.stat">
         <Header>
            <Title>Release Status</Title>
         </Header>
         <FuncDesc>The status of the sales schedule line to which the shipping
		  sequence information is linked.</FuncDesc>
         <AllowedValues>
            <SectionTitle>Allowed values</SectionTitle>
            <Paragraph>
               <Link href="/baanerp/td/domains/sls.stat" role="domain">Sales Schedule Status</Link>
            </Paragraph>
         </AllowedValues>
      </FieldHelp>
      <FieldHelp ID="tdsls317.hold">
         <Header>
            <Title>Put on Hold</Title>
         </Header>
         <FuncDesc>If this check box is selected, the sales schedule line
		  is put on hold. You cannot continue the sales schedule process for this sales
		  schedule line.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tdsls317.item">
         <Header>
            <Title>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="tdsls317.ofbp">
         <Header>
            <Title>Sold-to Business Partner</Title>
         </Header>
         <FuncDesc>Usually a customer's purchase department, the business partner
		who orders goods or services from your organization, that owns the
		configurations you maintain, or for whom you perform a project.</FuncDesc>
         <SimpleSection>
            <List>
               <ListIntro>Details of the agreement with the sold-to business partner
			 can include the following:</ListIntro>
               <ListItem>Default price and discount agreements</ListItem>
               <ListItem>Sales order defaults</ListItem>
               <ListItem>Delivery terms</ListItem>
               <ListItem>The related ship-to and invoice-to business partner</ListItem>
            </List>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="tdsls317.stbp">
         <Header>
            <Title>Ship-to Business Partner</Title>
         </Header>
         <FuncDesc>The business partner to which you ship the ordered goods. This
		usually represents a customer's distribution center or warehouse. The
		definition includes the default warehouse from which you send the goods, the
		carrier who carries out the transport, and the related sold-to business
		partner.</FuncDesc>
      </FieldHelp>
   </Fields>
</Session>