<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/tt/pmc/ttpmc1401s000" xml:lang="en">
	<Header>
		<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Validate Patch (ttpmc1401s000)</Title>
		<Keyword ContextSensitive="No"><Level1>PMC</Level1>
			<Level2>validate patch</Level2>
		</Keyword>
		<Keyword ContextSensitive="No"><Level1>patch</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#100256" role="glossary">patch</Link> or <Link href="/baanerp/tt/glossary/glossary#feature_pack" role="glossary">Feature Pack</Link>.</Paragraph>
			<Paragraph class="Default">You must validate a patch or Feature Pack before you can export the patch or Feature Pack by means of the <Link href="/baanerp/tt/pmc/ttpmc1200s000" role="session">Export Solution/Patch (ttpmc1200s000)</Link> session.</Paragraph>
			<List><ListIntro>The validation performs 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 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>, which can only be the case if the solution was exported.</ListItem>
				<ListItem>Checks if any solution in the patch has a <Link href="/baanerp/tt/glossary/glossary#post-requisite" role="glossary">post-requisite</Link> dependency relation with another solution, and whether the other solution is also present in the patch.</ListItem>
				<ListItem>If any solution in the patch has a <Link href="/baanerp/tt/glossary/glossary#co-requisite" role="glossary">co-requisite</Link> relation with another solution, whether the other solution is present in another patch, and a <Link href="/baanerp/tt/glossary/glossary#co-requisite" role="glossary">co-requisite</Link> relation is defined between the current patch and the other patch.</ListItem>
			</List>
			<List><ListIntro>For Feature Packs, the validation performs the following additional checks:</ListIntro>
				<ListItem>The patch header must be present.</ListItem>
				<ListItem>The installable unit key name and the version of the base VRC must be present.</ListItem>
				<ListItem>The prerequisite to the preceding Feature Pack must be defined.</ListItem>
				<ListItem>All solutions created in the previous Feature Pack msut exist as obsolete solutions in this Feature Pack.</ListItem>
			</List>
			<Paragraph class="Default">If you export a patch or Feature Pack, the current session starts automatically. If any of the checks fails, the export stops. You can also run this session manually from the <GUIRef href="" role="manual">Specific</GUIRef> menu of the <Link href="/baanerp/tt/pmc/ttpmc1501m000" role="session">Patches (ttpmc1501m000)</Link> session.</Paragraph>
			<Figure space-and-orientation="indented-estimated"><HTML:IMG height="248" width="683" SRC="../images/pmc_ttpmc1401s000.gif" path="/enterpriseserver/tools/tt/ttpmc" btb-count="1" btb-count2="1" btb-image-name="pmc_ttpmc1401s000.gif" btb-source-path="C:\SVN\docnl\Technology\EnterpriseServer~8.5\EnterpriseServer" btb-image-path="/enterpriseserver/tools/tt/images/pmc_ttpmc1401s000.gif" ID="IDAZQXBC" 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">Patch Code</Title>
			</Header>
			<FuncDesc>A unique identification of the <Link href="/baanerp/tt/glossary/glossary#100256" role="glossary">patch</Link> in a <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">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>
		<FieldHelp ID="type"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Solution Type</Title>
			</Header>
			<FuncDesc>Always: <Link href="/baanerp/tt/glossary/glossary#100256" role="glossary">Patch</Link>.</FuncDesc>
		</FieldHelp>
		<FieldHelp ID="nvrc"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">New Base VRC</Title>
			</Header>
			<FuncDesc>
                                 If this check box is selected, the patch is a Feature Pack.</FuncDesc>
		</FieldHelp>
	</Fields>
	<FormCommands><CommandHelp ID="exec.cont.process"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Print</Title>
			</Header>
			<FuncDesc>Prints the report of the validation.</FuncDesc>
		</CommandHelp>
	</FormCommands>
</Session>
