<?xml version="1.0" encoding="utf-8"?>
<ManualTopic ID="/baanerp/cp/onlinemanual/000012" xml:lang="en">
	<Header>
		<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Item definition in Enterprise Planning</Title>
		<Keyword><Level1>Item definition</Level1>
			<Level2>Enterprise Planning</Level2>
		</Keyword>
		<Keyword><Level1>Item segmentation</Level1>
			<Level2>Enterprise Planning</Level2>
		</Keyword>
	</Header>
	<GeneralSection><Paragraph><GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef> allows a very flexible definition of item codes using <Link href="/baanerp/tc/glossary/glossary#000069" role="glossary">segmentation</Link>.</Paragraph>
		<Paragraph>An administrator must define the item segmentation, before you can use <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef>.</Paragraph>
		<List><ListIntro>Currently <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef> supports the following logical segments:</ListIntro>
			<ListItem><Link href="/baanerp/tc/glossary/glossary#Cluster.tc" role="glossary">Cluster</Link> segment</ListItem>
			<ListItem><Link href="/baanerp/tc/glossary/glossary#Project.tc" role="glossary">Project</Link> segment</ListItem>
			<ListItem>Item-base segment</ListItem>
		</List>
		<Paragraph>The item-base segment is mandatory.</Paragraph>
		<Paragraph>With the optional cluster segment you can model items by warehouse (or groups of warehouses). So, the cluster segment is necessary if you want to have distribution planning functionality.</Paragraph>
		<Paragraph>With the optional project segment you can define <Link href="/baanerp/ti/glossary/glossary#000098" role="glossary">project items</Link>.</Paragraph>
		<List><ListIntro>You can define anything between 1 and 3 segments. Item code segments have the following order:</ListIntro>
			<ListItem>Cluster</ListItem>
			<ListItem>Project</ListItem>
			<ListItem>Item</ListItem>
		</List>
		<GeneralSection><SectionTitle>How to define the item-code segments</SectionTitle>
		</GeneralSection>
		<Note><SectionTitle>Note</SectionTitle>
			<Paragraph>The segment definition cannot be changed easily afterwards. So be careful when you specify the segments!</Paragraph>
			<Paragraph>You define the segments in the <GUIRef href="/baanerp/tt/gfd/ttgfd4122m000" role="session">Segmented Domains (ttgfd4122m000)</GUIRef> session and the <GUIRef href="/baanerp/tc/ibd/tcibd0500m000" role="session">Item Code Segmentation (tcibd0500m000)</GUIRef> session.</Paragraph>
		</Note>
		<GeneralSection><SectionTitle>Domains</SectionTitle>
			<Paragraph>The segments must correspond to the domain definition of related domains. This is extremelyla important. This means that the conversion (upper, lower case), alignment and length of the segment and its related domain must be the same.</Paragraph>
			<List><ListItem>The item-base segment must correspond to the definition of the cpitem domain.</ListItem>
				<ListItem>The cluster segment must correspond to the definition of the tcemm.clus domain.</ListItem>
				<ListItem>The project segment must correspond to the definition of the tccprj domain.</ListItem>
			</List>
		</GeneralSection>
		<GeneralSection><SectionTitle>Other packages</SectionTitle>
			<Paragraph>The item-base segment in <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef> must have the same length as the item-base segment in the other packages.</Paragraph>
		</GeneralSection>
	</GeneralSection>
	<RelatedTopics><SectionTitle>Related topics</SectionTitle>
		<RelTopic><Link href="/baanerp/cp/onlinemanual/000036" role="manual">To configure Enterprise Planning</Link>
		</RelTopic>
		<RelTopic><Link href="/baanerp/tc/onlinemanual/000087" role="manual">Segmented item codes</Link>
		</RelTopic>
	</RelatedTopics>
</ManualTopic>
