<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/ts/sbm/tssbm1100m000" xml:lang="en">
   <Header>
      <Title>Subcontract Agreement (tssbm1100m000)</Title>
   </Header>
   <HelpTopic>
      <AimSection>
         <Paragraph>Use this session to list
		  and maintain <Link href="/baanerp/ts/glossary/glossary#000398" role="glossary">subcontract agreements</Link> for
		  your <Link href="/baanerp/ts/glossary/glossary#000399" role="glossary">subcontractors</Link>.</Paragraph>
      </AimSection>
      <GeneralSection>
         <Paragraph>Subcontract agreements
		  can be either manually defined or generated from a <Link href="/baanerp/ts/glossary/glossary#ServicContra_ts" role="glossary">service contract</Link>.</Paragraph>
         <Paragraph>Subcontract agreement
		  information is usually stored as a header and one or more lines. The header is
		  a statement that lists the subcontractor details, contract details, and the
		  customer details. The line includes the items that must be covered and service
		  level requirements.</Paragraph>
         <Paragraph>On the <Link href="/baanerp/tc/glossary/glossary#specific" role="glossary">appropriate</Link> menu, you can start the <GUIRef href="/baanerp/ts/sbm/tssbm1110m000" role="session">Subcontract Agreement Lines (tssbm1110m000)</GUIRef> session. Use this session to view or
		  maintain existing agreement lines and to create new ones.</Paragraph>
      </GeneralSection>
      <RelatedTopics>
         <SectionTitle>Related topics</SectionTitle>
         <RelTopic>
            <Link href="/baanerp/ts/onlinemanual/000095" role="manual">Service contracts</Link>
         </RelTopic>
      </RelatedTopics>
   </HelpTopic>
   <Fields>
      <FieldHelp ID="tssbm100.sbct">
         <Header>
            <Title>Subcontract Agreement</Title>
         </Header>
         <FuncDesc>The agreement between the service organization and the
		subcontractor.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tssbm100.sear">
         <Header>
            <Title>Search Argument</Title>
         </Header>
         <FuncDesc>An alternative form of a description used for convenience
		during searching. A search key is usually an abbreviation, an acronym, or a
		mnemonic alternative to a full description.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="txta.yn">
         <Header>
            <Title>Subcontract Agreement Text</Title>
         </Header>
         <FuncDesc>If this check box is selected, additional text regarding the subcontract
		  agreement has been created.</FuncDesc>
         <RelatedTopics>
            <SectionTitle>Related topics</SectionTitle>
            <RelTopic>
               <Link href="/baanerp/ts/onlinemanual/000069" role="manual">Text (additional)</Link>
            </RelTopic>
         </RelatedTopics>
      </FieldHelp>
      <FieldHelp ID="tssbm100.stat">
         <Header>
            <Title>Status</Title>
         </Header>
         <FuncDesc>The header status can be one of the following:</FuncDesc>
         <SimpleSection>
            <List>
               <ListItem> 
                  <GUIRef href="/baanerp/ts/domains/sbm.stat#free" role="option">Free</GUIRef>. The
				order is entered manually or is generated.</ListItem>
               <ListItem> 
                  <GUIRef href="/baanerp/ts/domains/sbm.stat#printed" role="option">Printed</GUIRef>. The subcontractor
				is informed about the requirement of service, and the service organization
				waits for acknowledgement.</ListItem>
               <ListItem> 
                  <GUIRef href="/baanerp/ts/domains/sbm.stat#active" role="option">Active</GUIRef>.
				The status between the dates specified as effective/expiry dates. The date/time
				on which the status is made active is recorded in the <GUIRef href="/baanerp/ts/sbm/tssbm1100m000#tssbm100.actm" role="field">Activation Time</GUIRef> field. The status will be changed to <GUIRef href="/baanerp/ts/domains/sbm.stat#active" role="option">Active</GUIRef> when the subcontractor agrees to subcontract service for the items listed in
				the subcontract agreement. After the status is made <GUIRef href="/baanerp/ts/domains/sbm.stat#active" role="option">Active</GUIRef>,
				you cannot make any changes in the subcontract agreement.</ListItem>
               <ListItem> 
                  <GUIRef href="/baanerp/ts/domains/sbm.stat#cancel" role="option">Canceled</GUIRef>. If the
				subcontract agreement stands canceled, the <GUIRef href="/baanerp/ts/sbm/tssbm1100m000#tssbm100.cltm" role="field">Cancel Date</GUIRef> field shows the date on which the subcontract agreement is
				canceled. The <GUIRef href="/baanerp/ts/sbm/tssbm1110m000#tcmcs005.dsca" role="field">Cancel Reason</GUIRef> field contains the reason for cancelation.</ListItem>
               <ListItem> 
                  <GUIRef href="/baanerp/ts/domains/sbm.stat#expired" role="option">Expired</GUIRef>. The subcontract
				agreement period is over, and the termination is normal.</ListItem>
            </List>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="tssbm100.efdt">
         <Header>
            <Title>Eff Date</Title>
         </Header>
         <FuncDesc>Depending on its context, an effective date can be the first
		day on which a contract quotation is valid, the first day on which a service
		contract is active, or the first day on which you can use a template for
		quotations or contracts. The effective date often includes the effective time.</FuncDesc>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <Paragraph>If the subcontract
			 agreement is generated from a contract, the effective date is defaulted from
			 the contract header duration.</Paragraph>
         </Note>
      </FieldHelp>
      <FieldHelp ID="tssbm100.exdt">
         <Header>
            <Title>Exp Date</Title>
         </Header>
         <FuncDesc>Depending on its context, an expiry date can be: The last day
		on which a contract quotation is valid. The default expiry date for a quotation
		is the quotation date + effectivity period of quotations [days], as set in the <GUIRef href="/baanerp/ts/soc/tssoc0100m000" role="session">Service Order Parameters (tssoc0100m000)</GUIRef> session; The last day on which a service
		contract is active. After this date it becomes expired; The last day on which
		you can use a template for quotations or contracts. Note that the expiry date
		often includes the expiry time.</FuncDesc>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <Paragraph>If the subcontract
			 agreement is generated from a contract, the expiry date is defaulted from the
			 contract header duration.</Paragraph>
         </Note>
      </FieldHelp>
      <FieldHelp ID="tssbm100.cltm">
         <Header>
            <Title>Cancel Date</Title>
         </Header>
         <FuncDesc>The date on which the subcontract agreement is canceled. If the
		  subcontract agreement is canceled, the cancel date and cancel reason must be
		  entered.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="txtb.yn">
         <Header>
            <Title>Cancel Text</Title>
         </Header>
         <FuncDesc>If this check box is selected, additional text regarding the cancelation of
		  the subcontract agreement has been created.</FuncDesc>
         <RelatedTopics>
            <SectionTitle>Related topics</SectionTitle>
            <RelTopic>
               <Link href="/baanerp/ts/onlinemanual/000069" role="manual">Text (additional)</Link>
            </RelTopic>
         </RelatedTopics>
      </FieldHelp>
      <FieldHelp ID="tcmcs005.dsca">
         <Header>
            <Title>Cancel Reason</Title>
         </Header>
         <FuncDesc>The reason why the subcontract agreement is canceled.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tssbm100.bfbp">
         <Header>
            <Title>Buy-from BP</Title>
         </Header>
         <FuncDesc>The business partner from whom you order goods or services;
		this usually represents a supplier's sales department. The definition includes
		the default price and discount agreements, purchase-order defaults, delivery
		terms, and the related ship-from and invoice-from business partner.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tssbm100.bfad">
         <Header>
            <Title>Buy-from Address</Title>
         </Header>
         <FuncDesc>The buy-from business partner's address.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tssbm100.bfcn">
         <Header>
            <Title>Buy-from Contact</Title>
         </Header>
         <FuncDesc>The person with whom you discuss business transactions. For
		example, you address questions, quotations, and follow-up calls, direct mail,
		and promotional gifts to the contact. The contact's data include the name,
		telephone number, e-mail address, and other details.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tccom140.surn">
         <Header>
            <Title>Buy-from Contact</Title>
         </Header>
         <FuncDesc>The <Link href="/baanerp/tc/glossary/glossary#Contact_tc" role="glossary">contact's</Link> surname.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tssbm100.refa">
         <Header>
            <Title>Reference A</Title>
         </Header>
         <FuncDesc>The reference by which the sold-to business partner identifies
		the purchase order. This reference is printed on the service contract or
		quotation.</FuncDesc>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <Paragraph>Information
			 regarding the <Link href="/baanerp/ts/glossary/glossary#000400" role="glossary">blanket agreement</Link> can be
			 entered here.</Paragraph>
         </Note>
      </FieldHelp>
      <FieldHelp ID="tssbm100.refb">
         <Header>
            <Title>Second Reference</Title>
         </Header>
         <FuncDesc>The reference by which the subcontractor identifies the
		subcontract agreement.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tssbm100.csco">
         <Header>
            <Title>Contract</Title>
         </Header>
         <FuncDesc>The <Link href="/baanerp/ts/glossary/glossary#ServicContra_ts" role="glossary">service contract</Link> on which the subcontract
		  agreement is created/generated. If the contract has items or serialized items
		  for which subcontract agreement information is maintained, the subcontract
		  agreement can be generated for these items through generation of subcontracts.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tssbm100.actm">
         <Header>
            <Title>Activation Time</Title>
         </Header>
         <FuncDesc>The date and time at which the subcontract agreement is made
		  active.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tccom130.namc">
         <Header>
            <Title>Buy-from Address</Title>
         </Header>
         <FuncDesc>The <Link href="/baanerp/tc/glossary/glossary#BusinePartne_tc" role="glossary">business partner's</Link> city.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tssbm100.ofbp">
         <Header>
            <Title>Sold-to BP</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="ofbp.name">
         <Header>
            <Title>Sold-to BP</Title>
         </Header>
         <FuncDesc>The <Link href="/baanerp/tc/glossary/glossary#SoldtoBusine_tc" role="glossary">business partner's</Link> name.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tssbm100.cwoc">
         <Header>
            <Title>Service Office</Title>
         </Header>
         <FuncDesc>A department clearly identified within the company business
		model to manage the sales relations of the business partner. The service office
		is used to identify the locations that are responsible for the service
		activities within the organization.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tssbm100.clst">
         <Header>
            <Title>Cluster</Title>
         </Header>
         <FuncDesc>A set of serialized items that have the same location and are
		owned by the same business partner. Grouping serialized items into a cluster
		enables you to maintain them collectively.</FuncDesc>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <Paragraph>If a cluster is
			 specified, only serialized items belonging to this cluster can be maintained in
			 subcontract agreement lines.</Paragraph>
         </Note>
      </FieldHelp>
      <FieldHelp ID="tssbm100.lcad">
         <Header>
            <Title>Site Address</Title>
         </Header>
         <FuncDesc>The location address of the cluster or serialized item.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tssbm100.rsem">
         <Header>
            <Title>Resp. Employee</Title>
         </Header>
         <FuncDesc>The service employee responsible/contact person for the
		  subcontract agreement.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tssbm100.sfbp">
         <Header>
            <Title>Ship-from BP</Title>
         </Header>
         <FuncDesc>The business partner that ships the ordered goods to your
		organization. This usually represents a supplier's distribution center or
		warehouse. The definition includes the default warehouse at which you want to
		receive the goods and if you want to inspect the goods, the carrier that takes
		care of the transport, and the related buy-from business partner.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tssbm100.sfad">
         <Header>
            <Title>Ship-from Address</Title>
         </Header>
         <FuncDesc>The ship-from business partner's address.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tssbm100.shcn">
         <Header>
            <Title>Ship-from Contact</Title>
         </Header>
         <FuncDesc>The ship-from business partner's contact.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tssbm100.ptbp">
         <Header>
            <Title>Business Partner</Title>
         </Header>
         <FuncDesc>The business partner to which you pay invoices. This usually
		represents a supplier's accounts receivable department. The definition includes
		the default currency and exchange rate, the supplier's bank relation, the
		number of days within which you must pay the invoices, and if the business
		partner uses a factoring company.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="pay.to.name">
         <Header>
            <Title>Business Partner</Title>
         </Header>
         <FuncDesc>The <Link href="/baanerp/tc/glossary/glossary#PaytoBusineP_tc" role="glossary">pay-to business partner's</Link> name.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tssbm100.ptad">
         <Header>
            <Title>Address</Title>
         </Header>
         <FuncDesc>The pay-to business partner's address.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tssbm100.ptcn">
         <Header>
            <Title>Contact</Title>
         </Header>
         <FuncDesc>The pay-to business partner's <Link href="/baanerp/tc/glossary/glossary#Contact_tc" role="glossary">contact</Link>.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tssbm100.pymt">
         <Header>
            <Title>Payment Method</Title>
         </Header>
         <FuncDesc>Specifies when payments will be made.</FuncDesc>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <Paragraph>This field is used
			 for information purposes only.</Paragraph>
         </Note>
      </FieldHelp>
      <FieldHelp ID="tssbm100.ccur">
         <Header>
            <Title>Currency</Title>
         </Header>
         <FuncDesc>All amounts in the subcontract agreement lines are referred by
		  this <Link href="/baanerp/tc/glossary/glossary#Currency_tc" role="glossary">currency</Link>.</FuncDesc>
      </FieldHelp>
   </Fields>
</Session>