<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/tt/pmc/ttpmc1240s000" xml:lang="en">
	<Header>
		<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Generate Dependencies (ttpmc1240s000)</Title>
		<Keyword ContextSensitive="No"><Level1>PMC</Level1>
			<Level2>dependency</Level2>
		</Keyword>
		<Keyword ContextSensitive="No"><Level1>dependency</Level1>
			<Level2>generate</Level2>
		</Keyword>
	</Header>
	<HelpTopic xml:lang="en"><AimSection><Paragraph class="Default">
                                 Use this session to generate the dependency relations between solutions that must be installed together at a customer system.</Paragraph>
			<List><ListIntro>The following dependency relations are generated:</ListIntro>
				<ListItem><Link href="/baanerp/tt/glossary/glossary#pre-requisite" role="glossary">Prerequisite</Link> relations.</ListItem>
				<ListItem><Link href="/baanerp/tt/glossary/glossary#co-requisite" role="glossary">Co-requisite</Link> relations to the same solutions in other <Link href="/baanerp/tt/glossary/glossary#100249" role="glossary">base VRCs</Link>, if these solutions have one or more components in common. <List><ListIntro>Conditions for co-requisites:</ListIntro>
						<ListItem>Base VRCs must belong to the same base VRC combination.</ListItem>
						<ListItem>Solution numbers must be identical.</ListItem>
					</List>
				</ListItem>
			</List>
			<List><ListIntro>The following dependency relations cannot be generated, but must be specified manually:</ListIntro>
				<ListItem>Co-requisite relations to solutions in the same base VRC</ListItem>
				<ListItem><Link href="/baanerp/tt/glossary/glossary#post-requisite" role="glossary">Post-requisite</Link> relations</ListItem>
			</List>
			<Paragraph class="Default">To start this session, as shown in the following figure, you can click <Link href="/baanerp/tt/pmc/ttpmc1140m000#exec.user.0" role="section">Generate Dependencies</Link> on the <GUIRef href="" role="manual">Specific</GUIRef> menu of the <Link href="/baanerp/tt/pmc/ttpmc1140m000" role="session">Dependencies (ttpmc1140m000)</Link> session, which in turn you must start from the <GUIRef href="" role="manual">Specific</GUIRef> menu of the <Link href="/baanerp/tt/pmc/ttpmc1100m000" role="session">Solutions (ttpmc1100m000)</Link> session.</Paragraph>
			<Figure space-and-orientation="indented-estimated"><HTML:IMG height="214" width="697" SRC="../images/pmc_ttpmc1240s000.gif" path="/enterpriseserver/tools/tt/ttpmc" btb-count="1" btb-count2="1" btb-image-name="pmc_ttpmc1240s000.gif" btb-source-path="C:\SVN\docnl\Technology\EnterpriseServer~8.5\EnterpriseServer" btb-image-path="/enterpriseserver/tools/tt/images/pmc_ttpmc1240s000.gif" ID="IDAAPXBC" 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="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.csol" OtherIDs="g.p_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="g.p_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="g.delman"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Delete Also Manually Entered</Title>
			</Header>
			<FuncDesc>
                                 If this check box is selected, the dependencies you might have entered manually are deleted when you regenerate the dependencies.</FuncDesc>
		</FieldHelp>
		<FieldHelp ID="g.regdep"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Regenerate Dependencies</Title>
			</Header>
			<FuncDesc>If you select this If this check box is selected, all existing dependency relations are deleted, and the relations are regenerated.</FuncDesc>
			<Note><SectionTitle>
                                    Note
                                 </SectionTitle>
				<Paragraph class="Default">Manually entered relations are not deleted, unless you select the <Link href="/baanerp/tt/pmc/ttpmc1240s000#g.delman" role="formfield">Delete Also Manually Entered</Link> check box.</Paragraph>
			</Note>
		</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 dependency relations.</FuncDesc>
			<SimpleSection><Paragraph class="Default">Existing dependency relations are all retained, unless you select the <Link href="/baanerp/tt/pmc/ttpmc1240s000#g.regdep" role="formfield">Regenerate Dependencies</Link> check box and, optionally, the <Link href="/baanerp/tt/pmc/ttpmc1240s000#g.delman" role="formfield">Delete Also Manually Entered</Link> check box.</Paragraph>
			</SimpleSection>
		</CommandHelp>
	</FormCommands>
</Session>
