<?xml version="1.0" encoding="utf-8"?>
<ManualTopic ID="/baanerp/tp/onlinemanual/000064" xml:lang="en">
	<Header>
		<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">To use an element structure</Title>
		<Keyword><Level1>Structure</Level1>
			<Level2>element</Level2>
		</Keyword>
	</Header>
	<GeneralSection><Paragraph>You can define a parent-child relationship between any two <Link href="/baanerp/tp/glossary/glossary#Element.tp" role="glossary">elements</Link> in your project. The parent element is at a higher level than the child. Parent-child relationships can be one-to-one or one-to-many. On the basis of parent-child relationships, you can create a multi-level, tree-like hierarchy of elements. Typically, many elements in the hierarchy act both as parents (to lower-level elements) and as children (to higher-level ones). You can enter <Link href="/baanerp/tp/glossary/glossary#000100" role="glossary">budget lines</Link> only for elements that are part of the element hierarchy.</Paragraph>
		<Paragraph>Child elements and frequency</Paragraph>
		<Paragraph>You can define a one-to-many parent-child relationship where the parent contains the same child a number of times. In a construction project, for example, you might create a parent element called Heating to contain (say) 40 occurrences of a child element called Radiator. You do so by specifying a frequency of 40 when defining the parent-child relationship between the two elements.</Paragraph>
		<Paragraph>Header elements</Paragraph>
		<Paragraph>In your element hierarchy, you may want to include some elements whose only role is to provide a grouping structure for child elements at lower levels. For this purpose, you can create a special type of element - a header element - with the <GUIRef href="/baanerp/tp/ptc/tpptc1101m000" role="session">Layouts for Extra Elements (tpptc1101m000)</GUIRef> session. A header element contains only a code, description and search key. You cannot enter budget lines for a header element.</Paragraph>
		<Paragraph>The top element</Paragraph>
		<Paragraph>This is the term applied to the element at the highest level in an element structure. For any one project, you could create several sets of element structures, whose elements are unrelated to one another. You specify which element structure you want to use for the project by specifying its top element in the <Link href="/baanerp/tp/pdm/tppdm6100s000#tppdm600.cspa" role="fieldhelp">Top Element</Link> field of the project definition with the <GUIRef href="/baanerp/tp/pdm/tppdm6100s000" role="session">Project (tppdm6100s000)</GUIRef> session you cab also define multiple tops.</Paragraph>
		<Paragraph>Progress and cost recording</Paragraph>
		<List><ListIntro>The ability to create a multi-level hierarchy has two important results:</ListIntro>
			<ListItem>Progress information can accumulate from an element at a lower level to an element at a higher level. See <Link href="/baanerp/tp/onlinemanual/000065" role="manual">To use progress recording</Link>.</ListItem>
			<ListItem>Actual cost information can accumulate from an element at a lower level to an element at a higher level. See <Link href="/baanerp/tp/onlinemanual/000319" role="manual">To use costs</Link>.</ListItem>
		</List>
	</GeneralSection>
	<RelatedTopics><SectionTitle>Related topics</SectionTitle>
		<RelTopic><Link href="/baanerp/tp/onlinemanual/000063" role="manual">To use elements</Link>
		</RelTopic>
	</RelatedTopics>
</ManualTopic>
