<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/td/sls/tdsls4120s000" xml:lang="en">
   <Header>
      <Title>Sales Order (Line) Blocking (tdsls4120s000)</Title>
   </Header>
   <HelpTopic>
      <AimSection>
         <Paragraph>Use this session to view a blocked order or
		  order (component) line that you have selected from the list in the <GUIRef href="/baanerp/td/sls/tdsls4520m000" role="session">Blocked Sales Order (Lines) (tdsls4520m000)</GUIRef> session.</Paragraph>
      </AimSection>
      <GeneralSection>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <Paragraph>A freight order that is linked to the sales order line is
			 blocked automatically if the sales order line is blocked.</Paragraph>
         </Note>
      </GeneralSection>
      <RelatedTopics>
         <SectionTitle>Related topics</SectionTitle>
         <RelTopic>
            <Link href="/baanerp/td/onlinemanual/sls09410" role="manual">Order blocking</Link>
         </RelTopic>
         <RelTopic>
            <Link href="/baanerp/td/onlinemanual/000516" role="manual">Component handling - component lines</Link>
         </RelTopic>
      </RelatedTopics>
   </HelpTopic>
   <Fields>
      <FieldHelp ID="tdsls420.orno">
         <Header>
            <Title>Sales Order</Title>
         </Header>
         <FuncDesc>An agreement that is used to sell items or services to a
		business partner according to certain terms and conditions. A sales order
		consists of a header and one or more order lines.</FuncDesc>
         <SimpleSection>
            <Paragraph>The general order data such as business partner data, payment
		  terms, and delivery terms are stored in the header. The data about the actual
		  items to be supplied, such as price agreements and delivery dates, is entered
		  on the order lines.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="tdsls420.pono">
         <Header>
            <Title>Position</Title>
         </Header>
         <FuncDesc>The number used to identify the position of the order line on
		the sales or purchase order.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tdsls420.sqnb">
         <Header>
            <Title>Sequence Number</Title>
         </Header>
         <FuncDesc>The number used to identify in detail the position number of a
		sales order (delivery) line or a purchase order line (detail).</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tdsls420.csqn">
         <Header>
            <Title>Component Sequence</Title>
         </Header>
         <FuncDesc>The <Link href="/baanerp/cf/glossary/glossary#000060" role="glossary">sequence number</Link> of the sales order line <Link href="/baanerp/td/glossary/glossary#000392" role="glossary">component</Link>.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tdsls420.hrea">
         <Header>
            <Title>Hold Reason</Title>
         </Header>
         <FuncDesc/>
         <SimpleSection>
            <List>
               <ListIntro>A reason for blocking a sales order or a sales order line,
			 which can be:</ListIntro>
               <ListItem>The open order balance exceeds the customer's credit limit.</ListItem>
               <ListItem>The customer has overdue invoices.</ListItem>
               <ListItem>The customer's status is doubtful.</ListItem>
               <ListItem>The sales margin of one of the order lines is exceeded.</ListItem>
               <ListItem>The gross margin of the order is exceeded.</ListItem>
               <ListItem>The sales order is received through EDI.</ListItem>
               <ListItem>The sales order has an invalid zip code.</ListItem>
               <ListItem>The sales order is entered by an inexperienced operator.</ListItem>
               <ListItem>The sales order line contains a blocked item.</ListItem>
               <ListItem>A promotion is linked to the sales order (line).</ListItem>
               <ListItem>A user-defined general reason.</ListItem>
            </List>
            <Paragraph>An order can be held for more than one reason at any point in
		  the sales order procedure. For example, an order can be blocked due to credit
		  checking (the order balance exceeds the customers credit limit) at the same
		  time as being blocked due to margin control (the gross margin of the order is
		  exceeded).</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="tdsls420.opon">
         <Header>
            <Title>Originating Position</Title>
         </Header>
         <FuncDesc>The <Link href="/baanerp/td/glossary/glossary#000207" role="glossary">position number of the order line</Link> that caused the blocking of the sales order.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tdsls421.phsn">
         <Header>
            <Title>Phase (for Credit Rating)</Title>
         </Header>
         <FuncDesc>The phase during which LN performs credit
		  checking.</FuncDesc>
         <SimpleSection>
            <ProcedureList>
               <ListIntro>The following phases are available:</ListIntro>
               <ListItemHead>Phase 1</ListItemHead>
               <ListItem>During sales order entry.</ListItem>
               <ListItemHead>Phase 2</ListItemHead>
               <ListItem>When you release the sales order to <GUIRef href="/baanerp/wh" role="package">Warehousing</GUIRef>.</ListItem>
               <ListItemHead>Phase 3</ListItemHead>
               <ListItem>When you confirm the shipment in <GUIRef href="/baanerp/wh" role="package">Warehousing</GUIRef>.</ListItem>
            </ProcedureList>
         </SimpleSection>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <Paragraph>You can define the phases for credit checking in the <GUIRef href="/baanerp/tc/mcs/tcmcs0564m000" role="session">Credit Ratings (tcmcs0564m000)</GUIRef> session.</Paragraph>
         </Note>
      </FieldHelp>
      <FieldHelp ID="tdsls421.dtbl">
         <Header>
            <Title>Date/Time Blocked</Title>
         </Header>
         <FuncDesc>The date and time the sales order is automatically or manually
		  blocked in the <GUIRef href="/baanerp/td/sls/tdsls4100m000" role="session">Sales Orders (tdsls4100m000)</GUIRef> session or the <GUIRef href="/baanerp/td/sls/tdsls4101m000" role="session">Sales Order Lines (tdsls4101m000)</GUIRef> session.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tdsls420.erdt">
         <Header>
            <Title>Expected Release Date</Title>
         </Header>
         <FuncDesc>The date you expect the sales order to be unblocked.</FuncDesc>
         <SimpleSection>
            <Paragraph>The default expected release date is equal to the system
			 date. You can manually overwrite the date in the <GUIRef href="/baanerp/td/sls/tdsls4220m000" role="session">Select Blocked Sales Order (Lines) (tdsls4220m000)</GUIRef> session.</Paragraph>
         </SimpleSection>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <Paragraph>The sales order or order (component) line is always
			 manually released in the <GUIRef href="/baanerp/td/sls/tdsls4520m000" role="session">Blocked Sales Order (Lines) (tdsls4520m000)</GUIRef> session or <GUIRef href="/baanerp/td/sls/tdsls4120s000" role="session">Sales Order (Line) Blocking (tdsls4120s000)</GUIRef> session.</Paragraph>
         </Note>
      </FieldHelp>
      <FieldHelp ID="plan.del.date">
         <Header>
            <Title>Planned Delivery Date</Title>
         </Header>
         <FuncDesc>The planned date on which the items on the order/schedule line
		must be delivered. The planned delivery date cannot occur before the order
		date/schedule generation date.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tdsls420.lobl">
         <Header>
            <Title>User Who Blocked</Title>
         </Header>
         <FuncDesc>The employee who is responsible for blocking the sales order.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tdsls420.cran">
         <Header>
            <Title>Credit Analyst</Title>
         </Header>
         <FuncDesc>One of your employees in charge of controlling and monitoring
		the credit that you give to an invoice-to business partner.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tdsls420.pstc">
         <Header>
            <Title>ZIP Code</Title>
         </Header>
         <FuncDesc>The business partner's <Link href="/baanerp/tc/glossary/glossary#ZIPCode_tc" role="glossary">ZIP code</Link>.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tdsls420.bpid">
         <Header>
            <Title>Business Partner</Title>
         </Header>
         <FuncDesc>A party with whom you carry out business transactions, for
		example, a customer or a supplier. You can also define departments within your
		organization that act as customers or suppliers to your own department as
		business partners.</FuncDesc>
         <SimpleSection>
            <List>
               <ListIntro>The business partner definition includes:</ListIntro>
               <ListItem>The organization's name and main address.</ListItem>
               <ListItem>The language and currency used.</ListItem>
               <ListItem>Taxation and legal identification data.</ListItem>
            </List>
            <Paragraph>You address the business partner in the person of the
		  business partner's contact. The business-partner status determines if you can
		  carry out transactions. The transactions type (sales orders, invoices,
		  payments, shipments) is defined by the business partner's role.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="tdsls420.bprt">
         <Header>
            <Title>Business Partner Role</Title>
         </Header>
         <FuncDesc>The <Link href="/baanerp/tc/glossary/glossary#000015" role="glossary">business-partner role</Link> of the
		  business partner the sales order is blocked for.</FuncDesc>
      </FieldHelp>
   </Fields>
</Session>