<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/tt/pmc/ttpmc1402s000" xml:lang="en">
	<Header>
		<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Validate Collection (ttpmc1402s000)</Title>
		<Keyword ContextSensitive="No"><Level1>PMC</Level1>
			<Level2>validate collection</Level2>
		</Keyword>
		<Keyword ContextSensitive="No"><Level1>collection</Level1>
			<Level2>validate</Level2>
		</Keyword>
	</Header>
	<HelpTopic xml:lang="en"><AimSection><Paragraph class="Default">
                                 Use this session to validate a <Link href="/baanerp/tt/glossary/glossary#100257" role="glossary">collection</Link>.</Paragraph>
			<Paragraph class="Default">A collection must be validated before the <Link href="/baanerp/tt/pmc/ttpmc1210s000" role="session">Export Collection (ttpmc1210s000)</Link> session can export the collection.</Paragraph>
			<List><ListIntro>The validation does the following:</ListIntro>
				<ListItem>Checks whether the dumps of the solutions are present in the <Link href="/baanerp/tt/pmc/ttpmc0100s000#ttpmc000.pexp" role="formfield">Path for Export Dumps</Link> directory that is specified in the <Link href="/baanerp/tt/pmc/ttpmc0100s000" role="session">Parameters (ttpmc0100s000)</Link> session. The dumps of the solutions are placed in this directory when the solutions are exported individually, which you can do through the <Link href="/baanerp/tt/pmc/ttpmc1200s000" role="session">Export Solution/Patch (ttpmc1200s000)</Link> session.</ListItem>
				<ListItem>Checks whether the status of the solutions is <GUIRef href="" role="manual">Released</GUIRef>.</ListItem>
				<ListItem>Checks if any solution in the collection has a <Link href="/baanerp/tt/glossary/glossary#post-requisite" role="glossary">post-requisite</Link> relation with another solution, or a <Link href="/baanerp/tt/glossary/glossary#co-requisite" role="glossary">co-requisite</Link> relation with another solution in the same <Link href="/baanerp/tt/glossary/glossary#100249" role="glossary">base VRC</Link>, and whether the solution with which this relation exists is also part of the collection.</ListItem>
			</List>
			<Paragraph class="Default">If you export a collection, the Validate Collection session starts automatically. If any of the checks fails, the export stops. You can also use the Validate Collection session manually from the <GUIRef href="" role="manual">Specific</GUIRef> menu of the <Link href="/baanerp/tt/pmc/ttpmc1503m000" role="session">Collections (ttpmc1503m000)</Link> session.</Paragraph>
			<Figure space-and-orientation="indented-estimated"><HTML:IMG height="164" width="686" SRC="../images/pmc_ttpmc1402s000.gif" path="/enterpriseserver/tools/tt/ttpmc" btb-count="1" btb-count2="1" btb-image-name="pmc_ttpmc1402s000.gif" btb-source-path="C:\SVN\docnl\Technology\EnterpriseServer~8.5\EnterpriseServer" btb-image-path="/enterpriseserver/tools/tt/images/pmc_ttpmc1402s000.gif" ID="IDACRXBC" alt="[...]" xmlns:HTML="http://www.w3.org/TR/REC-html40"/></Figure>
		</AimSection>
		<RelatedTopics><SectionTitle>
                                 Related topics
                              </SectionTitle>
			<RelTopic><Link href="/baanerp/tt/onlinemanual/pmc_introduction" role="manual">PMC introduction</Link>
			</RelTopic>
			<RelTopic><Link href="/baanerp/tt/onlinemanual/pmc_overview" role="manual">PMC overview</Link>
			</RelTopic>
			<RelTopic><Link href="/baanerp/tt/onlinemanual/pmc_distributor_procedure" role="manual">PMC distributor procedure</Link>
			</RelTopic>
		</RelatedTopics>
	</HelpTopic>
	<Fields><FieldHelp ID="vers" OtherIDs="rele cust"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Base VRC</Title>
			</Header>
			<FuncDesc>A means in PMC to identify products in a unique way. Updates at the distributor side are provided with the base VRC identifier. A base VRC can contain the code of the physical VRC in which the related master product is installed, for example, B61_a, but can also be a code not related to a physical VRC, for example, 7.6_a_tt. At the recipient side, every update VRC is linked to a base VRC identifier. The installation process checks if the base VRC identifier of the update matches with the base VRC identifier of the update VRC. If not, you cannot install the update in that update VRC.</FuncDesc>
		</FieldHelp>
		<FieldHelp ID="csol" OtherIDs="desc"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Collection Code</Title>
			</Header>
			<FuncDesc>A unique identification of the <Link href="/baanerp/tt/glossary/glossary#100257" role="glossary">collection</Link> in the <Link href="/baanerp/tt/glossary/glossary#100249" role="glossary">base VRC</Link>.</FuncDesc>
		</FieldHelp>
		<FieldHelp ID="dsta"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Collection Status</Title>
			</Header>
			<FuncDesc>The following statuses describe the progress of the maintenance of solutions, <Link href="/baanerp/tt/glossary/glossary#100257" role="glossary">Collections</Link>, and <Link href="/baanerp/tt/glossary/glossary#100256" role="glossary">patches</Link>. To keep the descriptions readable, only solutions are described. However, in each case, collections and patches are intended as well, unless explicitly excepted.</FuncDesc>
			<SimpleSection><Paragraph class="Default">The status of the solution is only used at the distributor side. A history of status changes is recorded in the <GUIRef href="" role="manual">Maintenance History</GUIRef> table.</Paragraph>
				<Paragraph class="Default">To distinguish maintained solutions at the distributor side from imported solutions at the recipient side, the status is cleared when the solution is imported. This also applies to patches, but not to collections. The reason is that a collection is not known as such at the recipient side. Only the solutions contained in the collection are known at the recipient side.</Paragraph>
				<List><ListItemHead>In progress</ListItemHead>
					<ListItem>The initial status of the solution upon creation.</ListItem>
					<ListItemHead>Dependencies defined</ListItemHead>
					<ListItem>The dependencies between the various solutions are defined, and the solution is ready to be exported. You must select this status manually, because you might want to create dependencies that cannot be created automatically.</ListItem>
					<ListItemHead>Exported</ListItemHead>
					<ListItem>The solution is exported. The system handles this status. You cannot set the status manually. However, you can set a solution with the status Exported back to In Progress, Solved, Completed, or Dependencies Defined. If you change anything in an exported solution, the status is always set back to Dependencies Defined, and you must export the solution again. Before you can release a solution, the status must be Exported.</ListItem>
					<ListItemHead>Released</ListItemHead>
					<ListItem>The solution is released, which means that the solution is frozen. You can no longer change anything in the solution. To release a solution, you must change the status from Exported to Released, and you must save the solution with this status.</ListItem>
				</List>
			</SimpleSection>
		</FieldHelp>
	</Fields>
	<FormCommands><CommandHelp ID="exec.cont.process"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Validate</Title>
			</Header>
			<FuncDesc>Validates the <Link href="/baanerp/tt/glossary/glossary#100257" role="glossary">collection</Link>.</FuncDesc>
		</CommandHelp>
	</FormCommands>
</Session>
