<?xml version="1.0" encoding="utf-8"?>
<ManualTopic ID="/baanerp/tc/onlinemanual/000126" xml:lang="en">
	<Header>
		<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">To use availability types</Title>
		<Keyword><Level1>General calendar data</Level1>
		</Keyword>
		<Keyword><Level1>Calendar defaults</Level1>
		</Keyword>
		<Keyword><Level1>Parent structure (calendar)</Level1>
		</Keyword>
	</Header>
	<GeneralSection><Paragraph>Typically, each <Link href="/baanerp/tc/glossary/glossary#ResoActiType.tc" role="glossary">availability type</Link> corresponds with a particular activity type, and this enables you to categorize the availability of resources according to different activities.</Paragraph>
		<List><ListIntro>The calendar indicates whether the resource is available. For example, the calendar could indicate when:</ListIntro>
			<ListItem>The availability type Transport or Delivery is available for a country.</ListItem>
			<ListItem>The availability type Operation or Maintenance is available for a work center.</ListItem>
			<ListItem>The availability type Service is available for an employee.</ListItem>
		</List>
		<Paragraph>If you want to block a certain task, you do not have to redefine the entire day for all the availability types, but you can simply clear the <GUIRef href="/baanerp/tc/ccp/tcccp0120m000#tcccp020.avlb" role="formfield">Available</GUIRef> check box for the availability type involved on the corresponding day in the <GUIRef href="/baanerp/tc/ccp/tcccp0120m000" role="session">Calendar Working Hours (tcccp0120m000)</GUIRef> session.</Paragraph>
		<Note><SectionTitle>Note</SectionTitle>
			<Paragraph>It is not useful to define a special availability type for nonavailability, because SSA ERP does not maintain and update the working hours and the capacity data of a calendar in the <GUIRef href="/baanerp/tc/ccp/tcccp0120m000" role="session">Calendar Working Hours (tcccp0120m000)</GUIRef> session based on non-available availability types. You can use one of the following sessions to model nonavailability in a calendar:</Paragraph>
			<List><ListItem><GUIRef href="/baanerp/tc/ccp/tcccp0119m000" role="session">Calendar Non-Available Days (tcccp0119m000)</GUIRef>: to define incidental nonavailability, such as a department trip.</ListItem>
				<ListItem><GUIRef href="/baanerp/tc/ccp/tcccp0141m000" role="session">Calendar Recurrences (tcccp0141m000)</GUIRef>: to model recurring nonavailability, such as national holidays.</ListItem>
				<ListItem><GUIRef href="/baanerp/tc/ccp/tcccp0120m000" role="session">Calendar Working Hours (tcccp0120m000)</GUIRef>: to define incidental nonavailabilty by clearing the <GUIRef href="/baanerp/tc/ccp/tcccp0120m000#tcccp020.avlb" role="formfield">Available</GUIRef> check box for a working hours type on a specific date.</ListItem>
			</List>
		</Note>
		<Note><SectionTitle>Note</SectionTitle>
			<Paragraph>The calendar availability is simplified by taking out the multiple parent possibility. Inheritance occurs in one straight line. You can, however, still link as many parents between the standard calendar and the calendar as you wish. For <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef>, you are advised to at least link the company calendar to the calendar. If you link a parent to the calendar, the start and end dates of the parent are simulated as the priority. The dates of the child calendar are then disabled.</Paragraph>
		</Note>
		<Paragraph></Paragraph>
		<Paragraph></Paragraph>
	</GeneralSection>
</ManualTopic>
