<?xml version="1.0" encoding="utf-8"?>
<ManualTopic ID="/baanerp/td/onlinemanual/000063" xml:lang="en">
   <Header>
      <Title>Sales contracts</Title>
      <Keyword type="header" order="d1e1285460">
         <Level1>sales contract</Level1>
      </Keyword>
   </Header>
   <AimSection>
      <Paragraph>Sales contracts are used to register specific agreements with a
		sold-to business partner that concern the delivery of specific goods.</Paragraph>
      <List>
         <ListIntro>These agreements can be registered at the following
		  levels:</ListIntro>
         <ListItemHead>Sales contract lines</ListItemHead>
         <ListItem>In contract lines the agreements about the delivery of a
		  particular item or group of items for a specified period of time, are
		  registered. These agreements are focused on total quantities, prices, and
		  discounts. Apart from specifying an <Link href="/baanerp/td/glossary/glossary#EffectPeriod_td" role="glossary">effective period</Link>, you can
		  also indicate whether the minimum quantity to be sold is binding.</ListItem>
         <ListItemHead>Terms and conditions agreements</ListItemHead>
         <ListItem>In terms and conditions agreements, detailed terms and
		  conditions regarding orders, schedules, planning, logistics, invoicing,
		  allocation and hard pegging regarding the sale, purchase, or transfer of goods,
		  are registered. A sales terms and conditions agreement must be linked to a
		  sales contract before you can use it.</ListItem>
      </List>
   </AimSection>
   <GeneralSection>
      <List>
         <ListIntro>You can create the following contract types:</ListIntro>
         <ListItem> 
            <Link href="/baanerp/td/glossary/glossary#NormalContra_td" role="glossary">Normal contracts</Link>.</ListItem>
         <ListItem> 
            <Link href="/baanerp/td/glossary/glossary#SpeciaContra_td" role="glossary">Special contracts</Link>. A special
		  contract can also be a <Link href="/baanerp/td/glossary/glossary#377" role="glossary">promotional contract</Link>.</ListItem>
      </List>
      <Paragraph>Special contracts are
		mainly used to record agreements that relate to specific projects. For each
		sold-to business partner, you can close multiple special contracts in one
		period. In a specific period you cannot define more than one normal contract
		per item or price group for a sold-to business-partner. Sales schedules and
		terms and conditions agreements can only be linked to normal contracts and not
		to special contracts.</Paragraph>
      <GeneralSection>
         <SectionTitle>Sales contract procedure</SectionTitle>
         <Keyword type="section" order="d1e1285502">
            <Level1>sales contract</Level1>
            <Level2>procedure</Level2>
         </Keyword>
         <ProcedureSection>
            <ProcIntro>
               <Paragraph>To record the agreements that you made with a sold-to
				business partner, take the following steps:</Paragraph>
            </ProcIntro>
            <Steps>
               <Step>
                  <StepTitle>
                     <GUIRef href="/baanerp/td/sls/tdsls3600m000" role="session">Sales Contract - Lines (tdsls3600m000)</GUIRef>
                  </StepTitle>
                  <List>
                     <ListIntro>Use this session to define the following:</ListIntro>
                     <ListItemHead>Sales contract header</ListItemHead>
                     <ListItem>Define the general data for a sales contract header.
					 The information to be defined is mainly related to the sold-to business partner
					 to whom the contract relates. On the contract header, you can also link a <Link href="/baanerp/tc/glossary/glossary#000500" role="glossary" Update="No">terms and conditions agreement</Link>. <List>
                           <ListIntro>The terms and conditions agreement can be linked
						  as follows in this session:</ListIntro>
                           <ListItem>Manually, by selecting an agreement from the <GUIRef href="/baanerp/tc/trm/tctrm1100m000" role="session">Terms and Conditions (tctrm1100m000)</GUIRef> session.</ListItem>
                           <ListItem>By generating an agreement from a template, which
						  is automatically linked to the contract header. Click <GUIRef href="/baanerp/td/sls/tdsls3600m000#create.terms.from.templ" role="command">Generate Terms and Conditions from Template</GUIRef> on the <Link href="/baanerp/tc/glossary/glossary#specific" role="glossary">appropriate</Link> menu to start
						  the <Link href="/baanerp/tc/trm/tctrm2200m000" role="session">Generate Terms and Conditions from Template (tctrm2200m000)</Link> session.</ListItem>
                        </List> Contract header data refers to the <GUIRef href="/baanerp/td/sls/tdsls3500m000" role="session">Sales Contracts (tdsls3500m000)</GUIRef> session.</ListItem>
                     <ListItemHead>Sales contract lines</ListItemHead>
                     <ListItem>Define sales contract lines, which include the
					 agreements with a sold-to business partner about a certain item during a period
					 of time, including prices and discounts. Contract line data refers to the <GUIRef href="/baanerp/td/sls/tdsls3501m000" role="session">Sales Contract Lines (tdsls3501m000)</GUIRef> session.</ListItem>
                     <ListItemHead>Sales contract line logistic data</ListItemHead>
                     <ListItem>If the <Link href="/baanerp/td/sls/tdsls0100s300#tdsls000.ucfs.3" role="formfield">Use Contracts for Schedules</Link> check box is selected in the <GUIRef href="/baanerp/td/sls/tdsls0100s300" role="session">Sales Contract Parameters (tdsls0100s300)</GUIRef> session, define <Link href="/baanerp/td/glossary/glossary#000349" role="glossary">logistic agreements</Link> for the contract line. Contract line
					 logistic data refers to the <Link href="/baanerp/td/sls/tdsls3102m000" role="session">Sales Contract Line Logistic Data (tdsls3102m000)</Link> session.</ListItem>
                  </List>
                  <List>
                     <ListIntro>The following can be linked to a contract:</ListIntro>
                     <ListItem>Both a terms and condtions agreement and contract
					 lines.</ListItem>
                     <ListItem>Only a terms and conditions agreement and no contract
					 lines.</ListItem>
                     <ListItem>Only contract lines and no terms and conditions
					 agreement.</ListItem>
                  </List>
                  <Paragraph>For more information, refer to <Link href="/baanerp/tc/onlinemanual/000500" role="manual">Overview of terms and conditions</Link>.</Paragraph>
               </Step>
               <Step>
                  <StepTitle>Scheduled requirements for a sales contract</StepTitle>
                  <Paragraph>You can define scheduled requirements for a sales
				  contract. This functionality applies if you do not receive schedules from your
				  sold-to business partners, but you do want to set up a list of time-phased
				  deliveries based on a sales contract.</Paragraph>
                  <List>
                     <ListIntro>You can define scheduled requirements for a <Link href="/baanerp/td/glossary/glossary#000220" role="glossary">sales contract</Link> by means of :</ListIntro>
                     <ListItem>Delivery schemes.</ListItem>
                     <ListItem>Sales schedules.</ListItem>
                  </List>
                  <List>
                     <ListIntro>For more information, refer to</ListIntro>
                     <ListItem>
                        <Link href="/baanerp/td/onlinemanual/000421" role="manual">To define contract deliveries by means of delivery schemes</Link>
                     </ListItem>
                     <ListItem>
                        <Link href="/baanerp/td/onlinemanual/000363" role="manual">To define contract deliveries by means of sales schedules</Link>
                     </ListItem>
                  </List>
               </Step>
            </Steps>
         </ProcedureSection>
      </GeneralSection>
      <GeneralSection>
         <SectionTitle>Sales contract retrieval</SectionTitle>
         <List>
            <ListIntro>The following origins search for sales
			 contracts:</ListIntro>
            <ListItem>Sales order line</ListItem>
            <ListItem>Sales schedule header</ListItem>
            <ListItem>Sales schedule line</ListItem>
            <ListItem>
               <GUIRef href="/baanerp/ti" role="package">Manufacturing</GUIRef>, when searching for prices for BOM
			 components.</ListItem>
            <ListItem>
               <GUIRef href="/baanerp/tp" role="package">Project</GUIRef>,
			 when searching for prices.</ListItem>
            <ListItem> 
               <Link href="/baanerp/td/pcg/tdpcg0200m300" role="session">Price Simulator (tdpcg0200m300)</Link>
            </ListItem>
         </List>
         <List>
            <ListIntro>When searching an <GUIRef href="/baanerp/tc/domains/icap#active" role="option">Active</GUIRef> sales contract for these origins, only contracts are found for which the
			 following fields match the original values:</ListIntro>
            <ListItem>
               <GUIRef href="/baanerp/td/sls/tdsls3500m000#tdsls300.ofbp" role="manual">Sold-to Business Partner</GUIRef>
            </ListItem>
            <ListItem>
               <GUIRef href="/baanerp/td/sls/tdsls3501m000#tdsls301.stbp" role="manual">Ship-to Business Partner</GUIRef>
            </ListItem>
            <ListItem>
               <GUIRef href="/baanerp/td/sls/tdsls3501m000#tdsls301.item" role="manual">Item</GUIRef>
            </ListItem>
            <ListItem>
               <GUIRef href="/baanerp/td/sls/tdsls3501m000#tdsls301.cpgs" role="manual">Price Group</GUIRef>
            </ListItem>
            <ListItem>
               <GUIRef href="/baanerp/td/sls/tdsls3501m000#tdsls301.cofc" role="manual">Sales Office</GUIRef>
            </ListItem>
            <ListItem>
               <GUIRef href="/baanerp/td/sls/tdsls3501m000#tdsls301.effn" role="manual">Effectivity Unit</GUIRef>
            </ListItem>
            <ListItem>
               <GUIRef href="/baanerp/td/sls/tdsls3501m000#tdsls301.sdat" role="manual">Effective Date</GUIRef>
            </ListItem>
            <ListItem>
               <GUIRef href="/baanerp/td/sls/tdsls3501m000#tdsls301.edat" role="manual">Expiry Date</GUIRef>
            </ListItem>
         </List>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <Paragraph>Contract validity is rechecked when entering or modifying
			 contract <Emphasis>lines</Emphasis>.</Paragraph>
         </Note>
         <GeneralSection>
            <SectionTitle>Sales contracts and sales schedules</SectionTitle>
            <Paragraph>For <Link href="/baanerp/td/glossary/glossary#SalesSchedu_td" role="glossary" Update="No">sales schedules</Link>,
			 the <GUIRef href="/baanerp/td/sls/tdsls3512m000#tdsls312.egdt" role="manual">Generation Date</GUIRef> from the <GUIRef href="/baanerp/td/sls/tdsls3512m000" role="session">Sales Releases (tdsls3512m000)</GUIRef> session is used to search for valid sales
			 contracts.</Paragraph>
            <List>
               <ListIntro>A sales contract can be linked to a sales schedule
				when:</ListIntro>
               <ListItem>Processing a sales release into a sales
				schedule.</ListItem>
               <ListItem>Entering a sales schedule line.</ListItem>
               <ListItem>Approving a sales schedule line.</ListItem>
            </List>
            <Note>
               <SectionTitle>Note</SectionTitle>
               <Paragraph>If the <Link href="/baanerp/td/sls/tdsls0100s300#tdsls000.ucos.3" role="formfield">Use Customer Order for Schedules</Link> check box is selected in the <GUIRef href="/baanerp/td/sls/tdsls0100s300" role="session">Sales Contract Parameters (tdsls0100s300)</GUIRef> session, when searching a sales contract
				for a sales schedule header, LN also takes into account the <Link href="/baanerp/td/glossary/glossary#000240" role="glossary">customer order number</Link>. </Paragraph>
               <List>
                  <ListIntro>How contracts are linked, depends on the setting of the <Link href="/baanerp/td/sls/tdsls3500m000#tdsls300.adco" role="formfield">Action on Deviating Customer Order</Link> and <Link href="/baanerp/td/sls/tdsls3500m000#tdsls300.aeco" role="formfield">Action on Deviating Empty Customer Order</Link> fields in the <GUIRef href="/baanerp/td/sls/tdsls3500m000" role="session">Sales Contracts (tdsls3500m000)</GUIRef> session.</ListIntro>
                  <ListItemHead>
                     <GUIRef href="/baanerp/td/domains/sls.adco#block" role="option">Block</GUIRef>
                  </ListItemHead>
                  <ListItem>Only contracts are linked for which the <GUIRef href="/baanerp/td/sls/tdsls3500m000#tdsls300.corn" role="manual">Customer Order</GUIRef> in the <GUIRef href="/baanerp/td/sls/tdsls3500m000" role="session">Sales Contracts (tdsls3500m000)</GUIRef> session exactly matches the <GUIRef href="/baanerp/td/sls/tdsls3111m000#tdsls311.corn" role="manual">Customer Order</GUIRef> in the <GUIRef href="/baanerp/td/sls/tdsls3111m000" role="session">Sales Schedules (tdsls3111m000)</GUIRef> session.</ListItem>
                  <ListItemHead>
                     <GUIRef href="/baanerp/td/domains/sls.adco#cont.release" role="option">Continue with Sales Release</GUIRef>
                  </ListItemHead>
                  <ListItem>Contracts can be linked with a different <GUIRef href="/baanerp/td/sls/tdsls3500m000#tdsls300.corn" role="manual">Customer Order</GUIRef> than the sales schedule. In this case,
				  the sales release's <GUIRef href="/baanerp/td/sls/tdsls3508m000#tdsls308.corn" role="manual">Customer Order</GUIRef> is used on the sales
				  schedule.</ListItem>
                  <ListItemHead>
                     <GUIRef href="/baanerp/td/domains/sls.adco#cont.contract" role="option">Continue with Sales Contract</GUIRef>
                  </ListItemHead>
                  <ListItem>Contracts can be linked with a different <GUIRef href="/baanerp/td/sls/tdsls3500m000#tdsls300.corn" role="manual">Customer Order</GUIRef> than the sales schedule. In this case,
				  the sales contract's <GUIRef href="/baanerp/td/sls/tdsls3500m000#tdsls300.corn" role="manual">Customer Order</GUIRef> is used on the sales
				  schedule.</ListItem>
               </List>
            </Note>
         </GeneralSection>
         <GeneralSection>
            <SectionTitle>Sales contracts and sales orders</SectionTitle>
            <Paragraph>For <Link href="/baanerp/td/glossary/glossary#SalesOrder_td" role="glossary" Update="No">sales orders</Link>,
			 the date as specified in the <Link href="/baanerp/td/pcg/tdpcg0100m000#tdpcg000.spdt" role="formfield">Sales Price Date Type</Link> field of the <GUIRef href="/baanerp/td/pcg/tdpcg0100m000" role="session">Pricing Parameters (tdpcg0100m000)</GUIRef> session is used to search for valid sales
			 contracts.</Paragraph>
            <Paragraph>When a sales order is created, LN searches for the
			 price and/or discounts on special contracts and then on normal contracts. If
			 more special contracts are valid, a selection screen pops up that enables you
			 to decide which contract must be used. LN links this sales
			 contract to the sales order and uses the sales contract prices and discounts
			 for the sales order. If the item on the sales contract is <Link href="/baanerp/tc/glossary/glossary#000304" role="glossary" Update="No">unit effective</Link>, the sales order price is
			 inclusive <Link href="/baanerp/tc/glossary/glossary#000450" role="glossary">upgrade prices</Link>. If the item on the sales order is unit
			 effective, but the contract item is not, the sales order price is the contract
			 price increased by the upgrade prices.</Paragraph>
            <Note>
               <SectionTitle>Note</SectionTitle>
               <List>
                  <ListItem>If the <Link href="/baanerp/td/sls/tdsls0100s300#tdsls000.ucos.3" role="formfield">Use Customer Order for Schedules</Link> check box is selected in the <GUIRef href="/baanerp/td/sls/tdsls0100s300" role="session">Sales Contract Parameters (tdsls0100s300)</GUIRef> session, for sales orders (and other
				  origins), LN only
				  retrieves contracts for which the <GUIRef href="/baanerp/td/sls/tdsls3500m000#tdsls300.corn" role="manual">Customer Order</GUIRef> field is empty in the <GUIRef href="/baanerp/td/sls/tdsls3500m000" role="session">Sales Contracts (tdsls3500m000)</GUIRef> session. In this way, sales orders cannot be linked to
				  sales contracts set up for sales schedules.</ListItem>
                  <ListItem>To retrieve terms and conditions from an active contract
				  for an order line, the contract need not be linked to the order line. As a
				  result, the contract number is only filled on the order line if an active
				  contract line is linked to the order line. For more information, refer to <Link href="/baanerp/tc/onlinemanual/000509" role="manual">To retrieve terms and conditions</Link>.</ListItem>
               </List>
            </Note>
         </GeneralSection>
      </GeneralSection>
      <GeneralSection>
         <SectionTitle>Sales contract - additional processes</SectionTitle>
         <Keyword type="section" order="d1e1285812">
            <Level1>sales contract</Level1>
            <Level2>additional processes</Level2>
         </Keyword>
         <List>
            <ListIntro>You can:</ListIntro>
            <ListItem>Print contract acknowledgments to send to the sold-to
			 business partner in the <Link href="/baanerp/td/sls/tdsls3405m000" role="session">Print Sales Contract Acknowledgements (tdsls3405m000)</Link> session.</ListItem>
            <ListItem>Copy one sales contract to another in the <Link href="/baanerp/td/sls/tdsls3801m000" role="session">Copy Sales Contracts (tdsls3801m000)</Link> session.</ListItem>
            <ListItem>Check whether the agreed quantities are met at the end of a
			 contract's effective period in the <Link href="/baanerp/td/sls/tdsls3420m000" role="session">Evaluate Sales Contracts (tdsls3420m000)</Link> session. You can
			 also monitor, by extrapolating, the contract's progress during the effective
			 period. A report is printed that contains the deviations. An evaluation for the
			 complete contract can be executed by not printing the separate contract lines.
			 Small deviations are tolerated and are not printed.</ListItem>
            <ListItem>If certain sold-to business partners do not meet their
			 commitments stated in the contract, you can print and send out reminders in the <Link href="/baanerp/td/sls/tdsls3406m000" role="session">Print Sales Contract Reminders (tdsls3406m000)</Link> session to prevent a breach of
			 contract. LN prints
			 reminders for contracts that exceed the allowed <Link href="/baanerp/td/sls/tdsls3420m000#p.low" role="formfield">Negative Deviation</Link>.</ListItem>
            <ListItem>Terminate or delete sales contracts that are no longer valid,
			 or that have ended early in the <Link href="/baanerp/td/sls/tdsls3203m000" role="session">Terminate and/or Delete Sales Contracts (tdsls3203m000)</Link> session.</ListItem>
         </List>
      </GeneralSection>
   </GeneralSection>
   <RelatedTopics>
      <SectionTitle>Related topics</SectionTitle>
      <RelTopic>
         <Link href="/baanerp/tc/onlinemanual/000500" role="manual">Overview of terms and conditions</Link>
      </RelTopic>
      <RelTopic>
         <Link href="/baanerp/td/onlinemanual/000420" role="manual">Scheduled requirements for a sales contract</Link>
      </RelTopic>
      <RelTopic>
         <Link href="/baanerp/td/onlinemanual/000129" role="manual">Overview of sales schedule handling</Link>
      </RelTopic>
      <RelTopic>
         <Link href="/baanerp/tc/onlinemanual/000301" role="manual">To set up unit effectivity</Link>
      </RelTopic>
   </RelatedTopics>
</ManualTopic>