<?xml version="1.0" encoding="utf-8"?>
<ManualTopic ID="/baanerp/ts/onlinemanual/000321" xml:lang="en">
	<Header>
		<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Cost components in Service</Title>
		<Keyword><Level1>cost component</Level1>
		</Keyword>
	</Header>
	<AimSection><Paragraph>In general, cost components are used as a grouping possibility for cost transactions in relation to order systems. In <GUIRef href="/baanerp/ts" role="package">Service</GUIRef>, cost components are used differently from the way they are used in <GUIRef href="/baanerp/ti" role="package">Manufacturing</GUIRef>. The following is a general explanation of the use of cost components in <GUIRef href="/baanerp/ts" role="package">Service</GUIRef>.</Paragraph>
	</AimSection>
	<GeneralSection><SectionTitle>Cost components and cost types</SectionTitle>
		<Paragraph>In <GUIRef href="/baanerp/ts" role="package">Service</GUIRef> there are no constraints that require a cost component to be of a specific <Link href="/baanerp/ts/glossary/glossary#000403" role="glossary">cost type</Link>. It is preferable to use the <GUIRef href="/baanerp/tc/domains/cref#not.appl" role="enum">Not Applicable</GUIRef> cost type within <GUIRef href="/baanerp/ts" role="package">Service</GUIRef>.</Paragraph>
	</GeneralSection>
	<GeneralSection><SectionTitle>Cost transactions</SectionTitle>
		<Paragraph>For service order actual cost transactions, a cost component must be specified. This is because of the integration with <GUIRef href="/baanerp/tf" role="package">Financials</GUIRef>, for global cost control purposes, and for usage in coverage definitions of contracts, service-order quotations, and warranties.</Paragraph>
	</GeneralSection>
	<GeneralSection><SectionTitle>Default value</SectionTitle>
		<List><ListItem>For material cost lines, the cost component is defaulted from item data related to the specified item.</ListItem>
			<ListItem>For labor lines, the cost component is defaulted from the related <Link href="/baanerp/ts/glossary/glossary#Task.ts" role="glossary">task</Link> code.</ListItem>
			<ListItem>Where service order cost lines are copied from <Link href="/baanerp/ts/glossary/glossary#RefereActivi.ts" role="glossary">reference activities</Link> or <Link href="/baanerp/ts/glossary/glossary#000024" role="glossary">planned activities</Link>, the cost component is defaulted from the cost lines of the activity.</ListItem>
		</List>
	</GeneralSection>
	<GeneralSection><SectionTitle>Cost coverage</SectionTitle>
		<Paragraph>In the <GUIRef href="/baanerp/ts/ctm" role="module">Contract Management</GUIRef> module, coverage for contract quotations, contracts, warranties, and service-order quotations can be defined. On the lowest level of coverage term definition of those applications, known as <Link href="/baanerp/ts/glossary/glossary#000056" role="glossary">cost terms</Link>, it is possible to specify coverage identified by means of cost components. During the costing process of service orders, SSA ERP searches in warranty and contract terms, and so on, to get coverage for an actual cost line. In case of coverage definition by means of cost components, SSA ERP searches for a match with the cost component as specified on an actual cost line.</Paragraph>
	</GeneralSection>
</ManualTopic>
