<?xml version="1.0" encoding="utf-8"?>
<ManualTopic ID="/baanerp/tp/onlinemanual/000334" xml:lang="en">
	<Header>
		<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">To copy a project structure to SSA ERP Service</Title>
		<Keyword><Level1>Copy structure to SSA ERP Service</Level1>
		</Keyword>
	</Header>
	<AimSection><Paragraph>The project <Link href="/baanerp/tp/glossary/glossary#000326" role="glossary">activity structure</Link> or <Link href="/baanerp/tp/glossary/glossary#ElemenStruct.tp" role="glossary">element structure</Link> and the actual consumed material items, linked to the project are copied to the Service <Link href="/baanerp/ts/glossary/glossary#000310" role="glossary">physical breakdown</Link> structure. The process enables identifying the project items that need service and maintenance. The actual (history) data of the consumed items linked to the project is considered for this tp-ts integration.</Paragraph>
	</AimSection>
	<Note><SectionTitle>Note</SectionTitle>
		<Paragraph>The copying process is handled in <GUIRef href="" role="manual">SSA ERP Service</GUIRef> in the <Link href="/baanerp/ts/cfg/tscfg2210m200" role="session">Copy Project Breakdown Structure (tscfg2210m200)</Link> session. The path to the session is as follows: <GUIRef href="" role="manual">SSA ERP Service --&gt; Configuration Management --&gt; Physical Breakdown Sources --&gt; Copy Project Breakdown Structure</GUIRef> session.</Paragraph>
	</Note>
	<GeneralSection><Paragraph><GUIRef href="" role="manual">Copying actual consumed material items:</GUIRef>
		</Paragraph>
		<Paragraph>The actual consumed material items stored in Project cost history are copied. If the item is marked 'Serialized', a serial number is generated for the item, based on a pre-defined <Link href="/baanerp/tc/glossary/glossary#000300" role="glossary">mask</Link>. If the generation of the serial number fails, an error is reported. It is possible to generate a dummy or final serial number for the material item. You can later replace the dummy serial number with the final number. For elements and activities, the number generated is considered as the final serial number.</Paragraph>
		<Paragraph><GUIRef href="" role="manual">i. You can only copy:</GUIRef>
		</Paragraph>
		<List><ListItem>Actual consumed material items stored in Project cost history.</ListItem>
			<ListItem>Actual consumed material items for which Service item data is defined.</ListItem>
		</List>
		<Paragraph><GUIRef href="" role="manual">ii. You cannot copy:</GUIRef>
		</Paragraph>
		<List><ListItem>Consumables like oil used for a project.</ListItem>
			<ListItem>Actual consumed material items for which Service item data is not defined.</ListItem>
		</List>
		<Paragraph><GUIRef href="" role="manual">Copying the activity structure:</GUIRef>
		</Paragraph>
		<Paragraph>The activity structure as displayed in the <Link href="/baanerp/tp/pss/tppss2500m000" role="session">Activities (tppss2500m000)</Link> session is used as input for the physical breakdown structure. SSA ERP creates a serialized item for each activity. The parent activity is used as the top serialized item in the physical breakdown structure.</Paragraph>
		<Paragraph><GUIRef href="" role="manual">Copying the element structure:</GUIRef>
		</Paragraph>
		<Paragraph>The element structure as displayed in the <Link href="/baanerp/tp/ptc/tpptc1509m000" role="session">Element Budget Structure (tpptc1509m000)</Link> session is used as input for the physical breakdown structure. SSA ERP creates a serialized item for each element. The top element is used as the top serialized item in the physical breakdown structure.</Paragraph>
		<Paragraph>If the project element/activity structure undergoes changes, and the copy process has to be repeated again, the existing physical breakdown structure in Service is not overwritten. The new structure is added to the existing records.</Paragraph>
	</GeneralSection>
	<RelatedTopics><SectionTitle>Related topics</SectionTitle>
		<RelTopic><Link href="/baanerp/tp/onlinemanual/000333" role="manual">Integration of Project with Service</Link>
		</RelTopic>
	</RelatedTopics>
</ManualTopic>
