<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/tt/pmc/ttpmc1250s000" xml:lang="en">
	<Header>
		<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Generate Patch (ttpmc1250s000)</Title>
		<Keyword ContextSensitive="No"><Level1>PMC</Level1>
			<Level2>patch</Level2>
		</Keyword>
		<Keyword ContextSensitive="No"><Level1>patch</Level1>
			<Level2>generate</Level2>
		</Keyword>
	</Header>
	<HelpTopic xml:lang="en"><AimSection><Paragraph class="Default">
                                 Use this session to generate a <Link href="/baanerp/tt/glossary/glossary#100256" role="glossary">patch</Link>.</Paragraph>
		</AimSection>
		<GeneralSection><Paragraph class="Default">The generation of a patch only links a group of solutions to the patch. To link solutions one by one to a patch, you can use the <Link href="/baanerp/tt/pmc/ttpmc1100m000#exec.user.8" role="section">Link Solution to Patch</Link> command on the <GUIRef href="" role="manual">Specific</GUIRef> menu of the <Link href="/baanerp/tt/pmc/ttpmc1100m000" role="session">Solutions (ttpmc1100m000)</Link> session.</Paragraph>
			<Paragraph class="Default">After you link the solutions to a patch, you must define the dependencies of the patch to other patches, and you must validate and export the patch. To carry out these actions, you can use the commands on the <GUIRef href="" role="manual">Specific</GUIRef> menu of the <Link href="/baanerp/tt/pmc/ttpmc1501m000" role="session">Patches (ttpmc1501m000)</Link> session.</Paragraph>
			<Note><SectionTitle>
                                    Note
                                 </SectionTitle>
				<Paragraph class="Default">You cannot include solutions that are already part of another patch.</Paragraph>
				<Paragraph class="Default">Using the <Link href="/baanerp/tt/pmc/ttpmc1100m000#exec.user.9" role="section">Remove Solution from Patch</Link> command on the <GUIRef href="" role="manual">Specific</GUIRef> menu of the <Link href="/baanerp/tt/pmc/ttpmc1100m000" role="session">Solutions (ttpmc1100m000)</Link> session, you can remove a solution from a patch.</Paragraph>
			</Note>
			<Figure space-and-orientation="indented-estimated"><FigIntro>The following figure shows the form of the session:</FigIntro>
				<HTML:IMG height="247" width="693" SRC="../images/pmc_ttpmc1250s000.gif" path="/enterpriseserver/tools/tt/ttpmc" btb-count="1" btb-count2="1" btb-image-name="pmc_ttpmc1250s000.gif" btb-source-path="C:\SVN\docnl\Technology\EnterpriseServer~8.5\EnterpriseServer" btb-image-path="/enterpriseserver/tools/tt/images/pmc_ttpmc1250s000.gif" ID="IDAJPXBC" alt="[...]" xmlns:HTML="http://www.w3.org/TR/REC-html40"/></Figure>
		</GeneralSection>
		<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="g.vers" OtherIDs="g.rele g.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="g.gsol" OtherIDs="g.desc"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Patch</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="csol.f" OtherIDs="csol.t"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Solution Code</Title>
			</Header>
			<FuncDesc>A unique identification of the solution in a <Link href="/baanerp/tt/glossary/glossary#100249" role="glossary">base VRC</Link>.</FuncDesc>
		</FieldHelp>
		<FieldHelp ID="edat.f" OtherIDs="edat.t"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Export Date</Title>
			</Header>
			<FuncDesc>The date on which the solution was exported.</FuncDesc>
		</FieldHelp>
		<FieldHelp ID="etim.f" OtherIDs="etim.t"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Export Time</Title>
			</Header>
			<FuncDesc>The time at which the solution was exported.</FuncDesc>
		</FieldHelp>
	</Fields>
	<FormCommands><CommandHelp ID="exec.cont.process"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Generate</Title>
			</Header>
			<FuncDesc>Generates the <Link href="/baanerp/tt/glossary/glossary#100256" role="glossary">patch</Link>.</FuncDesc>
		</CommandHelp>
	</FormCommands>
</Session>
