<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/tt/pmc/ttpmc1140m000" xml:lang="en">
	<Header>
		<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Dependencies (ttpmc1140m000)</Title>
		<Keyword ContextSensitive="No"><Level1>PMC</Level1>
			<Level2>dependency</Level2>
		</Keyword>
		<Keyword ContextSensitive="No"><Level1>dependency</Level1>
		</Keyword>
	</Header>
	<HelpTopic xml:lang="en"><AimSection><Paragraph class="Default">
                                 Use this session to define the dependencies between solutions or <Link href="/baanerp/tt/glossary/glossary#100256" role="glossary">patches</Link>.</Paragraph>
			<Paragraph class="Default">You can generate the dependencies automatically, or define the dependencies manually.</Paragraph>
			<Paragraph class="Default">If not all dependencies that would be generated are present, you receive a warning during the export of the solution or patch.</Paragraph>
			<Paragraph class="Default">After you define all the dependencies, you can change the solution status to <GUIRef href="" role="manual">Dependencies defined</GUIRef> and the solution is ready to be exported. You can change the status in the details session of the <Link href="/baanerp/tt/pmc/ttpmc1100m000" role="session">Solutions (ttpmc1100m000)</Link> session.</Paragraph>
			<Paragraph class="Default">If the status of the solution was <GUIRef href="" role="manual">Exported</GUIRef>, and you change the dependencies, then the solution status is reset to <GUIRef href="" role="manual">Dependencies defined</GUIRef>.</Paragraph>
			<Paragraph class="Default">You can only start the current session through the <GUIRef href="" role="menu">Specific</GUIRef> menu in the <Link href="/baanerp/tt/pmc/ttpmc1100m000" role="session">Solutions (ttpmc1100m000)</Link> session.</Paragraph>
			<Figure space-and-orientation="indented-estimated"><HTML:IMG height="318" width="694" SRC="../images/pmc_ttpmc1140m000.gif" path="/enterpriseserver/tools/tt/ttpmc" btb-count="1" btb-count2="1" btb-image-name="pmc_ttpmc1140m000.gif" btb-source-path="C:\SVN\docnl\Technology\EnterpriseServer~8.5\EnterpriseServer" btb-image-path="/enterpriseserver/tools/tt/images/pmc_ttpmc1140m000.gif" ID="IDATNXBC" 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="ttpmc140.vers" OtherIDs="ttpmc140.rele ttpmc140.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="ttpmc140.csol" OtherIDs="csol.desc"><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="ttpmc140.rver" OtherIDs="ttpmc140.rrel ttpmc140.rcus"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Related VRC</Title>
			</Header>
			<FuncDesc>The <Link href="/baanerp/tt/glossary/glossary#100249" role="glossary">base VRC</Link> of the solution or <Link href="/baanerp/tt/glossary/glossary#100256" role="glossary">patch</Link> to which the current solution or patch is related.</FuncDesc>
			<SimpleSection><Paragraph class="Default">The related VRC can be a different base VRC if the dependency type is <Link href="/baanerp/tt/glossary/glossary#co-requisite" role="glossary">co-requisite</Link> or a <Link href="/baanerp/tt/glossary/glossary#pre-requisite" role="glossary">prerequisite</Link> from a <Link href="/baanerp/tt/glossary/glossary#feature_pack" role="glossary">Feature Pack</Link> to the previous Feature Pack.</Paragraph>
			</SimpleSection>
			<RelatedTopics><SectionTitle>
                                    Related topics
                                 </SectionTitle>
				<RelTopic><Link href="/baanerp/tt/glossary/glossary#000010" role="glossary">dependency</Link>
				</RelTopic>
			</RelatedTopics>
		</FieldHelp>
		<FieldHelp ID="ttpmc140.rsol" OtherIDs="rsol.desc"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Solution</Title>
			</Header>
			<FuncDesc>The solution or <Link href="/baanerp/tt/glossary/glossary#100256" role="glossary">patch</Link> with which a dependency relation exists.</FuncDesc>
			<RelatedTopics><SectionTitle>
                                    Related topics
                                 </SectionTitle>
				<RelTopic><Link href="/baanerp/tt/glossary/glossary#000010" role="glossary">dependency</Link>
				</RelTopic>
			</RelatedTopics>
		</FieldHelp>
		<FieldHelp ID="ttpmc140.dtyp"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Type</Title>
			</Header>
			<FuncDesc>In PMC, the relation between solutions. Dependencies are defined at the PMC distributor side and are part of the meta data of a PMC solution and guarantee that PMC solutions are installed in the correct configuration and sequence at the PMC recipient side.</FuncDesc>
			<SimpleSection><Paragraph class="Default">The following values indicate the dependency type between solutions.</Paragraph>
				<List><ListIntro>Three dependency types are available:</ListIntro>
					<ListItem><Link href="/baanerp/tt/glossary/glossary#pre-requisite" role="glossary">Pre-requisites</Link>
					</ListItem>
					<ListItem><Link href="/baanerp/tt/glossary/glossary#co-requisite" role="glossary">Co-requisites</Link>
					</ListItem>
					<ListItem><Link href="/baanerp/tt/glossary/glossary#post-requisite" role="glossary">Post-requisites</Link>
					</ListItem>
				</List>
				<Paragraph class="Default">You can only install solutions that are dependent on other solutions if the other solutions are already present, or are also installed.</Paragraph>
				<Paragraph class="Default">The same dependency types exist between <Link href="/baanerp/tt/glossary/glossary#100256" role="glossary">Patches</Link>. However, to keep the descriptions readable, only solutions are mentioned, but patches are meant as well. One exception applies: the post-requisite type is not applicable to patches.</Paragraph>
			</SimpleSection>
			<SimpleSection><Paragraph class="Default">You must enter dependencies of type co-requisite and prerequisite for the solution being created.</Paragraph>
				<Paragraph class="Default">You must add post-requisites dependencies to the already released solution and the post-requisite dependency must point to the solution being created.</Paragraph>
			</SimpleSection>
			<Note><SectionTitle>
                                    Note
                                 </SectionTitle>
				<Paragraph class="Default">Be sure to add the post-requisite dependency before you release the new solution.</Paragraph>
			</Note>
			<SimpleSection><Paragraph class="Default">The post-requisite dependency is transferred to the recipient in the dump of the solution being created. This implies that this dependency is only known at the recipient side after the newly created solution has been scanned.</Paragraph>
			</SimpleSection>
		</FieldHelp>
		<FieldHelp ID="ttpmc140.manu"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Manual</Title>
			</Header>
			<FuncDesc>
                                 If this check box is selected, the dependency was not generated, but defined manually.</FuncDesc>
			<Note><SectionTitle>
                                    Note
                                 </SectionTitle>
				<Paragraph class="Default">If you generate or regenerate the dependencies, the <Link href="/baanerp/tt/pmc/ttpmc1240s000" role="session">Generate Dependencies (ttpmc1240s000)</Link> session start. In this session, you can specify whether or not you want to delete existing manually defined dependencies.</Paragraph>
			</Note>
		</FieldHelp>
	</Fields>
	<FormCommands><CommandHelp ID="exec.user.0"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Generate Dependencies</Title>
			</Header>
			<FuncDesc>Starts the <Link href="/baanerp/tt/pmc/ttpmc1240s000" role="session">Generate Dependencies (ttpmc1240s000)</Link> session.</FuncDesc>
		</CommandHelp>
		<CommandHelp ID="ttpmc1440m000"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Print Dependencies (Multi-level)</Title>
			</Header>
			<FuncDesc>Starts the <Link href="/baanerp/tt/pmc/ttpmc1440m000" role="session">Print Dependencies (Multilevel) (ttpmc1440m000)</Link> session.</FuncDesc>
		</CommandHelp>
	</FormCommands>
</Session>
