<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/tt/pmc/ttpmc2105s000" xml:lang="en">
	<Header>
		<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Open Patch (ttpmc2105s000)</Title>
		<Keyword ContextSensitive="No"><Level1>PMC</Level1>
			<Level2>open patch</Level2>
		</Keyword>
		<Keyword ContextSensitive="No"><Level1>patch</Level1>
			<Level2>open</Level2>
		</Keyword>
	</Header>
	<HelpTopic xml:lang="en"><AimSection><Paragraph class="Default">
                                 Use this session to open a <Link href="/baanerp/tt/glossary/glossary#100256" role="glossary">patch</Link> by entering a password. When the patch is opened, the solutions contained in the patch can be handled individually.</Paragraph>
			<Paragraph class="Default">A password is required to open the patch, because opening a patch and handling the solutions individually is not a recommended practice, and only intended to solve specific problems.</Paragraph>
			<Paragraph class="Default">This session must be started from the <GUIRef href="" role="menu">Specific</GUIRef> menu of the <Link href="/baanerp/tt/pmc/ttpmc2102m000" role="session">Process Patches (ttpmc2102m000)</Link> session.</Paragraph>
		</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_recipient_procedure" role="manual">PMC recipient procedure</Link>
			</RelTopic>
		</RelatedTopics>
	</HelpTopic>
	<Fields><FieldHelp ID="ttpmc105.vers" OtherIDs="ttpmc105.rele ttpmc105.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="ttpmc105.csol"><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>.</FuncDesc>
		</FieldHelp>
		<FieldHelp ID="pass"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Password</Title>
			</Header>
			<FuncDesc>The password to open the <Link href="/baanerp/tt/glossary/glossary#100256" role="glossary">patch</Link>.</FuncDesc>
		</FieldHelp>
	</Fields>
</Session>
