<?xml version="1.0" encoding="utf-8"?>
<ManualTopic ID="/baanerp/tt/onlinemanual/pmc_distributor_procedure" xml:lang="en">
	<Header>
		<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">PMC distributor procedure</Title>
	</Header>
	<AimSection><Paragraph class="Default"></Paragraph>
		<List><ListIntro>This chapter describes the PMC distributor procedures. This chapter contains the following sections:</ListIntro>
			<ListItem>Setup</ListItem>
			<ListItem>To create updates</ListItem>
			<ListItem>Feature Pack development</ListItem>
			<ListItem>Customizations</ListItem>
		</List>
	</AimSection>
	<GeneralSection><SectionTitle>Setup</SectionTitle>
		<Paragraph class="Default">This section describes the procedures for the update distributor to set up the PMC administration.</Paragraph>
		<List><ListIntro>The setup consists of the following sections:</ListIntro>
			<ListItem>Setup procedure</ListItem>
			<ListItem>Parameters</ListItem>
			<ListItem>Base VRCs</ListItem>
			<ListItem>Base VRC combinations</ListItem>
		</List>
		<GeneralSection><SectionTitle>Setup procedure</SectionTitle>
			<Keyword type="section" order="IDAEKJZB"><Level1>PMC</Level1>
				<Level2>distributor setup procedure</Level2>
			</Keyword>
			<Keyword type="section" order="IDAMKJZB"><Level1>PMC distributor</Level1>
				<Level2>setup procedure</Level2>
			</Keyword>
			<Figure space-and-orientation="indented-estimated"><FigIntro>This section provides a flowchart that describes the steps of the distributor set-up procedure. The subsequent sections provide a detailed explanation of the procedure.</FigIntro>
				<HTML:IMG width="157" height="336" SRC="../images/pmc_distributor_setup.gif" path="/enterpriseserver/tools/tt/onlinemanual" btb-count="1" btb-count2="1" btb-image-name="pmc_distributor_setup.gif" btb-source-path="C:\SVN\docnl\Technology\EnterpriseServer~8.5\EnterpriseServer" btb-image-path="/enterpriseserver/tools/tt/images/pmc_distributor_setup.gif" ID="IDAMDXBC" alt="[...]" xmlns:HTML="http://www.w3.org/TR/REC-html40"/><FigCaption>Distributor Set-up Procedure</FigCaption>
			</Figure>
		</GeneralSection>
		<GeneralSection><SectionTitle>Parameters</SectionTitle>
			<Keyword type="section" order="IDAMLJZB"><Level1>PMC</Level1>
				<Level2>distributor parameters</Level2>
			</Keyword>
			<Keyword type="section" order="IDAULJZB"><Level1>PMC distributor</Level1>
				<Level2>parameters</Level2>
			</Keyword>
			<Paragraph class="Default">The very first step in the distributor set-up procedure is to define the PMC parameters.</Paragraph>
			<List><ListIntro>The following two group boxess are available:</ListIntro>
				<ListItemHead>Recipient</ListItemHead>
				<ListItem><Paragraph class="Default">Even if you do not use the <Link href="/baanerp/tt/glossary/glossary#pmc_recipient" role="glossary">PMC recipient</Link> part of the PMC module, for technical reasons, you must fill in the parameters in this group box.</Paragraph>
				</ListItem>
				<ListItemHead>Distributor</ListItemHead>
				<ListItem><Paragraph class="Default">The <Link href="/baanerp/tt/glossary/glossary#pmc_distributor" role="glossary">PMC distributor</Link> part of the PMC module uses these parameters, and therefore you must fill in these parameters.</Paragraph>
					<Paragraph class="Default">Most of the parameters are directories on the operating system on which the solution dumps will be stored.</Paragraph>
				</ListItem>
			</List>
			<Paragraph class="Default">For details, refer to the <Link href="/baanerp/tt/pmc/ttpmc0100s000" role="session">Parameters (ttpmc0100s000)</Link> session.</Paragraph>
			<Note><SectionTitle>
                                    Note
                                 </SectionTitle>
				<Paragraph class="Default">Because the definition of the parameters is a once only step, you must be aware of the impact if you change the parameters afterwards.</Paragraph>
				<Paragraph class="Default">If you change the directories on the operating system, you must move the directories and files according to the new directory specifications.</Paragraph>
			</Note>
		</GeneralSection>
		<GeneralSection><SectionTitle>base VRCs</SectionTitle>
			<Keyword type="section" order="IDA1NJZB"><Level1>PMC</Level1>
				<Level2>base VRC</Level2>
			</Keyword>
			<Keyword type="section" order="IDADOJZB"><Level1>base VRC</Level1>
			</Keyword>
			<Paragraph class="Default">You must define a <Link href="/baanerp/tt/glossary/glossary#100249" role="glossary">base VRC</Link> before you can create and link <Link href="/baanerp/tt/glossary/glossary#solution" role="glossary">solutions</Link>, <Link href="/baanerp/tt/glossary/glossary#100257" role="glossary">collections</Link>, <Link href="/baanerp/tt/glossary/glossary#100256" role="glossary">patches</Link>, and <Link href="/baanerp/tt/glossary/glossary#feature_pack" role="glossary">Feature Packs</Link> to the base VRC.</Paragraph>
			<Paragraph class="Default">A base VRC is an administrative identifier for a software product and is not a physical VRC, but must always be connected to a physical VRC, which contains the software components.</Paragraph>
			<Paragraph class="Default">The PMC distributor should connect a base VRC to an <Link href="/baanerp/tt/glossary/glossary#100254" role="glossary">export VRC</Link>, the PMC recipient should connect a base VRC to an <Link href="/baanerp/tt/glossary/glossary#100255" role="glossary">update VRC</Link>.</Paragraph>
			<Note><SectionTitle>
                                    Note
                                 </SectionTitle>
				<Paragraph class="Default">A Feature Pack always starts a new base VRC.</Paragraph>
			</Note>
			<Paragraph class="Default">For details, refer to the <Link href="/baanerp/tt/pmc/ttpmc0110m000" role="session">Base VRC's (ttpmc0110m000)</Link> session.</Paragraph>
		</GeneralSection>
		<GeneralSection><SectionTitle>base VRC combinations</SectionTitle>
			<Keyword type="section" order="IDAQQJZB"><Level1>PMC</Level1>
				<Level2>base VRC combination</Level2>
			</Keyword>
			<Keyword type="section" order="IDAYQJZB"><Level1>base VRC combination</Level1>
			</Keyword>
			<Paragraph class="Default"><Link href="/baanerp/tt/glossary/glossary#base_vrc_combination" role="glossary">Base VRC combinations</Link> are required to define relations between base VRCs.</Paragraph>
			<Paragraph class="Default">Any base VRC must always be a member of a base VRC combination, even if no relations to other base VRCs exist.</Paragraph>
			<Paragraph class="Default">If you have not linked a base VRC to a base VRC combination, you cannot create updates.</Paragraph>
			<Figure space-and-orientation="indented-estimated"><FigIntro>The following example shows a base VRC combination with two base VRCs with a relation:</FigIntro>
				<HTML:IMG width="484" height="243" SRC="../images/pmc_base_vrc_combination.gif" path="/enterpriseserver/tools/tt/onlinemanual" btb-count="1" btb-count2="1" btb-image-name="pmc_base_vrc_combination.gif" btb-source-path="C:\SVN\docnl\Technology\EnterpriseServer~8.5\EnterpriseServer" btb-image-path="/enterpriseserver/tools/tt/images/pmc_base_vrc_combination.gif" ID="IDAL5WBC" alt="[...]" xmlns:HTML="http://www.w3.org/TR/REC-html40"/></Figure>
			<Paragraph class="Default">For details refer to the <Link href="/baanerp/tt/pmc/ttpmc0111m000" role="session">Base VRC Combinations (ttpmc0111m000)</Link> session.</Paragraph>
		</GeneralSection>
	</GeneralSection>
	<GeneralSection><SectionTitle>To create updates</SectionTitle>
		<List><ListIntro>This section describes the following PMC distributor procedures to create software updates:</ListIntro>
			<ListItem>To create solutions</ListItem>
			<ListItem>To create collections</ListItem>
			<ListItem>To create patches</ListItem>
			<ListItem>To create Feature Packs</ListItem>
		</List>
		<GeneralSection><SectionTitle>To create solutions</SectionTitle>
			<Keyword type="section" order="IDA4SJZB"><Level1>PMC</Level1>
				<Level2>create solutions</Level2>
			</Keyword>
			<Keyword type="section" order="IDAGTJZB"><Level1>solution</Level1>
				<Level2>create</Level2>
			</Keyword>
			<Figure space-and-orientation="indented-estimated"><FigIntro>This section describes the procedure steps to create solutions:</FigIntro>
				<HTML:IMG height="513" width="423" SRC="../images/pmc_create_solution.gif" path="/enterpriseserver/tools/tt/onlinemanual" btb-count="1" btb-count2="1" btb-image-name="pmc_create_solution.gif" btb-source-path="C:\SVN\docnl\Technology\EnterpriseServer~8.5\EnterpriseServer" btb-image-path="/enterpriseserver/tools/tt/images/pmc_create_solution.gif" ID="IDA1AXBC" alt="[...]" xmlns:HTML="http://www.w3.org/TR/REC-html40"/></Figure>
			<Paragraph class="Default">You can create or maintain solutions in the <Link href="/baanerp/tt/pmc/ttpmc1100m000" role="session">Solutions (ttpmc1100m000)</Link> session.</Paragraph>
			<Paragraph class="Default">This session is the central session from which you can maintain all aspects of solutions.</Paragraph>
			<Paragraph class="Default">The initial <Link href="/baanerp/tt/glossary/glossary#solution_status_distributor" role="glossary">status</Link> of a solution after creation is In Progress.</Paragraph>
			<List><ListIntro>If you create a solution, you must take the following steps:</ListIntro>
				<ListItemHead>Create defects and connect the defects to the solution</ListItemHead>
				<ListItem><Paragraph class="Default">You can create and connect the defects in the <Link href="/baanerp/tt/pmc/ttpmc1110m000" role="session">Defects by Solution (ttpmc1110m000)</Link> session.</Paragraph>
					<Paragraph class="Default">This step is optional.</Paragraph>
				</ListItem>
				<ListItemHead>Connect software components to the solution</ListItemHead>
				<ListItem><Paragraph class="Default">To connect software components to the solution, use the <Link href="/baanerp/tt/pmc/ttpmc1520m000" role="session">Components by Solution (ttpmc1520m000)</Link> session and the <Link href="/baanerp/tt/pmc/ttpmc1120s000" role="session">Component by Solution (ttpmc1120s000)</Link> session.</Paragraph>
					<Paragraph class="Default">You can also connect software components to a solution in the <Link href="/baanerp/tt/pmc/ttpmc1221m000" role="session">Connect Components to PMC Solution (ttpmc1221m000)</Link> session.</Paragraph>
				</ListItem>
				<ListItemHead>Define dependencies between solutions</ListItemHead>
				<ListItem>To define dependencies between solutions, run the <Link href="/baanerp/tt/pmc/ttpmc1140m000" role="session">Dependencies (ttpmc1140m000)</Link> session.</ListItem>
				<ListItemHead>Validate the solution</ListItemHead>
				<ListItem>To validate a solution, you must click <GUIRef href="/baanerp/tt/pmc/ttpmc1100m000#validate.solution" role="command">Validate Solution</GUIRef> on the <GUIRef href="" role="menu">Specific</GUIRef> menu in the <Link href="/baanerp/tt/pmc/ttpmc1100m000" role="session">Solutions (ttpmc1100m000)</Link> session. This option starts the <Link href="/baanerp/tt/pmc/ttpmc1404s000" role="session">Validate Solution (ttpmc1404s000)</Link> session. This session checks, for example, if components are available, or if components are not compiled in debug mode, and so on.</ListItem>
				<ListItemHead>Export the solution</ListItemHead>
				<ListItem>To export a solution, you must use the <Link href="/baanerp/tt/pmc/ttpmc1200s000" role="session">Export Solution/Patch (ttpmc1200s000)</Link> session.</ListItem>
				<ListItemHead>Release the solution</ListItemHead>
				<ListItem><Paragraph class="Default">To release a solution, you must change the <Link href="/baanerp/tt/pmc/ttpmc1100m000#ttpmc100.dsta" role="formfield">Status</Link> from Exported to Released in the <Link href="/baanerp/tt/pmc/ttpmc1100m000" role="session">Solutions (ttpmc1100m000)</Link> session.</Paragraph>
					<Paragraph class="Default">You can only release a solution if the <Link href="/baanerp/tt/pmc/ttpmc1100m000#ttpmc100.dsta" role="formfield">Status</Link> of the solution is Exported.</Paragraph>
				</ListItem>
				<ListItemHead>Publish the solution</ListItemHead>
				<ListItem><Paragraph class="Default">To publish a solution, select the <Link href="/baanerp/tt/pmc/ttpmc1100m000#ttpmc100.publ" role="formfield">Published</Link> check box in the <Link href="/baanerp/tt/pmc/ttpmc1100m000" role="session">Solutions (ttpmc1100m000)</Link> session.</Paragraph>
					<Paragraph class="Default">You can only publish a solution if the <Link href="/baanerp/tt/pmc/ttpmc1100m000#ttpmc100.dsta" role="formfield">Status</Link> of the solution is Released.</Paragraph>
					<Paragraph class="Default">This step is optional.</Paragraph>
				</ListItem>
				<ListItemHead>View or print solutions</ListItemHead>
				<ListItem><Paragraph class="Default">To view solutions, you must use the <Link href="/baanerp/tt/pmc/ttpmc1521m000" role="session">Components by solution (ttpmc1521m000)</Link> session.</Paragraph>
					<Paragraph class="Default">To print solutions, you must use the <Link href="/baanerp/tt/pmc/ttpmc1420m000" role="session">Print Components by Solution (ttpmc1420m000)</Link> session.</Paragraph>
				</ListItem>
				<ListItemHead>View the solution history.</ListItemHead>
				<ListItem>To view the solution history, you must use the <Link href="/baanerp/tt/pmc/ttpmc1560m000" role="session">Maintenance History (ttpmc1560m000)</Link> session.</ListItem>
			</List>
		</GeneralSection>
		<GeneralSection><SectionTitle>To create collections</SectionTitle>
			<Keyword type="section" order="IDAU0JZB"><Level1>PMC</Level1>
				<Level2>create collections</Level2>
			</Keyword>
			<Keyword type="section" order="IDA20JZB"><Level1>collection</Level1>
				<Level2>create</Level2>
			</Keyword>
			<Figure space-and-orientation="indented-estimated"><FigIntro>This section shows the procedure steps to create collections:</FigIntro>
				<HTML:IMG width="427" height="405" SRC="../images/pmc_create_collection.gif" path="/enterpriseserver/tools/tt/onlinemanual" btb-count="1" btb-count2="1" btb-image-name="pmc_create_collection.gif" btb-source-path="C:\SVN\docnl\Technology\EnterpriseServer~8.5\EnterpriseServer" btb-image-path="/enterpriseserver/tools/tt/images/pmc_create_collection.gif" ID="IDA35WBC" alt="[...]" xmlns:HTML="http://www.w3.org/TR/REC-html40"/></Figure>
			<Paragraph class="Default">You can create or maintain collections in the <Link href="/baanerp/tt/pmc/ttpmc1503m000" role="session">Collections (ttpmc1503m000)</Link> session.</Paragraph>
			<Paragraph class="Default">This session is the central session from which you can maintain all aspects of collections.</Paragraph>
			<Paragraph class="Default">The initial <Link href="/baanerp/tt/glossary/glossary#solution_status_distributor" role="glossary">status</Link> of a collection after creation is In Progress.</Paragraph>
			<List><ListIntro>After you create a collection, take the following steps:</ListIntro>
				<ListItemHead>Connect solutions to the collection</ListItemHead>
				<ListItem>You can connect solutions to a collection in the <Link href="/baanerp/tt/pmc/ttpmc1151m000" role="session">Solutions by Collection (ttpmc1151m000)</Link> session.</ListItem>
				<ListItemHead>Validate the collection</ListItemHead>
				<ListItem>You can validate collections in the <Link href="/baanerp/tt/pmc/ttpmc1402s000" role="session">Validate Collection (ttpmc1402s000)</Link> session.</ListItem>
				<ListItemHead>Export the collection</ListItemHead>
				<ListItem>You can export a collection in the <Link href="/baanerp/tt/pmc/ttpmc1210s000" role="session">Export Collection (ttpmc1210s000)</Link> session.</ListItem>
				<ListItemHead>Release the collection</ListItemHead>
				<ListItem><Paragraph class="Default">To release a collection, you must change the <Link href="/baanerp/tt/pmc/ttpmc1101s000#ttpmc101.dsta" role="formfield">Collection Status</Link> from Exported to Released in the <Link href="/baanerp/tt/pmc/ttpmc1101s000" role="session">Collections (ttpmc1101s000)</Link> session.</Paragraph>
					<Paragraph class="Default">You can only release a collection if the <Link href="/baanerp/tt/pmc/ttpmc1101s000#ttpmc101.dsta" role="formfield">Collection Status</Link> is Exported.</Paragraph>
				</ListItem>
				<ListItemHead>Publish the collection</ListItemHead>
				<ListItem><Paragraph class="Default">To publish a collection, select the <Link href="/baanerp/tt/pmc/ttpmc1101s000#ttpmc101.publ" role="formfield">Published</Link> check box in the <Link href="/baanerp/tt/pmc/ttpmc1101s000" role="session">Collections (ttpmc1101s000)</Link> session.</Paragraph>
					<Paragraph class="Default">You can only publish a collection if the <Link href="/baanerp/tt/pmc/ttpmc1101s000#ttpmc101.dsta" role="formfield">Collection Status</Link> is Released.</Paragraph>
					<Paragraph class="Default">This step is optional.</Paragraph>
				</ListItem>
				<ListItemHead>View the collection history</ListItemHead>
				<ListItem>To view the collection history, use the <Link href="/baanerp/tt/pmc/ttpmc1560m000" role="session">Maintenance History (ttpmc1560m000)</Link> session.</ListItem>
			</List>
		</GeneralSection>
		<GeneralSection><SectionTitle>To create patches</SectionTitle>
			<Keyword type="section" order="IDAW5JZB"><Level1>PMC</Level1>
				<Level2>create patches</Level2>
			</Keyword>
			<Keyword type="section" order="IDA45JZB"><Level1>patch</Level1>
				<Level2>create</Level2>
			</Keyword>
			<Figure space-and-orientation="indented-estimated"><FigIntro>This section describes the procedure to create patches:</FigIntro>
				<HTML:IMG width="430" height="524" SRC="../images/pmc_create_patch.gif" path="/enterpriseserver/tools/tt/onlinemanual" btb-count="1" btb-count2="1" btb-image-name="pmc_create_patch.gif" btb-source-path="C:\SVN\docnl\Technology\EnterpriseServer~8.5\EnterpriseServer" btb-image-path="/enterpriseserver/tools/tt/images/pmc_create_patch.gif" ID="IDAJAXBC" alt="[...]" xmlns:HTML="http://www.w3.org/TR/REC-html40"/></Figure>
			<Paragraph class="Default">You can create or maintain patches in the <Link href="/baanerp/tt/pmc/ttpmc1501m000" role="session">Patches (ttpmc1501m000)</Link> session.</Paragraph>
			<Paragraph class="Default">This session is the central session from which you can maintain all aspects of patches.</Paragraph>
			<Paragraph class="Default">You must clear the <Link href="/baanerp/tt/pmc/ttpmc1501m100#ttpmc100.nvrc" role="formfield">New Base VRC</Link> check box. Otherwise, the patch is a Feature Pack.</Paragraph>
			<Paragraph class="Default">The initial <Link href="/baanerp/tt/glossary/glossary#solution_status_distributor" role="glossary">status</Link> of a patch after creation is In Progress.</Paragraph>
			<List><ListIntro>After you create a patch, you can take the following steps:</ListIntro>
				<ListItemHead>Connect solutions to the patch</ListItemHead>
				<ListItem>To connect solutions to a patch, you must use either the <Link href="/baanerp/tt/pmc/ttpmc1100m000" role="session">Solutions (ttpmc1100m000)</Link> session or the <Link href="/baanerp/tt/pmc/ttpmc1250s000" role="session">Generate Patch (ttpmc1250s000)</Link> session.</ListItem>
				<ListItemHead>Define dependencies between patches</ListItemHead>
				<ListItem>To define dependencies between patches, you must use the <Link href="/baanerp/tt/pmc/ttpmc1140m000" role="session">Dependencies (ttpmc1140m000)</Link> session.</ListItem>
				<ListItemHead>Set or change the password of the patch</ListItemHead>
				<ListItem>To set or change the password of a patch, you must use the <Link href="/baanerp/tt/pmc/ttpmc1105s000" role="session">Password by Patch (ttpmc1105s000)</Link> session.</ListItem>
				<ListItemHead>Validate the patch</ListItemHead>
				<ListItem>To validate a patch, you must use the <Link href="/baanerp/tt/pmc/ttpmc1401s000" role="session">Validate Patch (ttpmc1401s000)</Link> session.</ListItem>
				<ListItemHead>Export the patch</ListItemHead>
				<ListItem>To export a patch, you must use the <Link href="/baanerp/tt/pmc/ttpmc1200s000" role="session">Export Solution/Patch (ttpmc1200s000)</Link> session.</ListItem>
				<ListItemHead>Release the patch</ListItemHead>
				<ListItem><Paragraph class="Default">To release a patch, you must change the <Link href="/baanerp/tt/pmc/ttpmc1501m000#ttpmc100.dsta" role="formfield">Status</Link> from Exported to Released in the <Link href="/baanerp/tt/pmc/ttpmc1501m000" role="session">Patches (ttpmc1501m000)</Link> session.</Paragraph>
					<Paragraph class="Default">You can only release a patch if the <Link href="/baanerp/tt/pmc/ttpmc1501m000#ttpmc100.dsta" role="formfield">Status</Link> is Exported.</Paragraph>
				</ListItem>
				<ListItemHead>Publish the patch</ListItemHead>
				<ListItem><Paragraph class="Default">To publish a patch, select the <Link href="/baanerp/tt/pmc/ttpmc1501m000#ttpmc100.publ" role="formfield">Published</Link> check box in the <Link href="/baanerp/tt/pmc/ttpmc1501m000" role="session">Patches (ttpmc1501m000)</Link> session.</Paragraph>
					<Paragraph class="Default">You can only publish a patch if the <Link href="/baanerp/tt/pmc/ttpmc1501m000#ttpmc100.dsta" role="formfield">Status</Link> of the patch is Released.</Paragraph>
					<Paragraph class="Default">This step is optional.</Paragraph>
				</ListItem>
				<ListItemHead>View the patch history</ListItemHead>
				<ListItem>You can view the patch history in the <Link href="/baanerp/tt/pmc/ttpmc1560m000" role="session">Maintenance History (ttpmc1560m000)</Link> session.</ListItem>
			</List>
		</GeneralSection>
		<GeneralSection><SectionTitle>To create Feature Packs</SectionTitle>
			<Keyword type="section" order="IDA3FKZB"><Level1>PMC</Level1>
				<Level2>create feature packs</Level2>
			</Keyword>
			<Keyword type="section" order="IDAFGKZB"><Level1>feature pack</Level1>
				<Level2>create</Level2>
			</Keyword>
			<Note><SectionTitle>
                                    Note
                                 </SectionTitle>
				<Paragraph class="Default">The process to create Feature Packs requires a specific setup of your development environment.</Paragraph>
				<Paragraph class="Default">The <Link href="#service_pack_development" role="internal">Feature Pack Development</Link> section describes in detail how the setup must look.</Paragraph>
			</Note>
			<Figure space-and-orientation="indented-estimated"><FigIntro>This section describes the procedure steps to create Feature Packs:</FigIntro>
				<HTML:IMG width="428" height="617" SRC="../images/pmc_create_service_pack.gif" path="/enterpriseserver/tools/tt/onlinemanual" btb-count="1" btb-count2="1" btb-image-name="pmc_create_service_pack.gif" btb-source-path="C:\SVN\docnl\Technology\EnterpriseServer~8.5\EnterpriseServer" btb-image-path="/enterpriseserver/tools/tt/images/pmc_create_service_pack.gif" ID="IDASAXBC" alt="[...]" xmlns:HTML="http://www.w3.org/TR/REC-html40"/></Figure>
			<Paragraph class="Default">You can create or maintain Feature Packs in the <Link href="/baanerp/tt/pmc/ttpmc1501m000" role="session">Patches (ttpmc1501m000)</Link> session.</Paragraph>
			<Paragraph class="Default">This session is the central session from which you maintain all aspects of Feature Packs.</Paragraph>
			<Paragraph class="Default">You must select the <Link href="/baanerp/tt/pmc/ttpmc1501m100#ttpmc100.nvrc" role="formfield">New Base VRC</Link> check box, otherwise, the patch is not a Feature Pack.</Paragraph>
			<Paragraph class="Default">The initial status of a Feature Pack after creation is <GUIRef href="" role="manual">In progress</GUIRef>.</Paragraph>
			<List><ListIntro>If you have created a Feature Pack, you must take the following steps:</ListIntro>
				<ListItemHead>Define dependencies between Feature Packs</ListItemHead>
				<ListItem>Define dependencies between Feature Packs in the <Link href="/baanerp/tt/pmc/ttpmc1140m000" role="session">Dependencies (ttpmc1140m000)</Link> session.</ListItem>
				<ListItemHead>Create the Feature Pack header</ListItemHead>
				<ListItem>Create the Feature Pack header in the <Link href="/baanerp/tt/pmc/ttpmc1106m000" role="session">Patch Header (ttpmc1106m000)</Link> session.</ListItem>
				<ListItemHead>Generate obsolete solutions for the Feature Pack</ListItemHead>
				<ListItem>Generate obsolete solutions for the Feature Pack in the <Link href="/baanerp/tt/pmc/ttpmc1252s000" role="session">Generate Obsolete Solutions (ttpmc1252s000)</Link> session.</ListItem>
				<ListItemHead>Generate the Feature Pack</ListItemHead>
				<ListItem>Generate a Feature Pack in the <Link href="/baanerp/tt/pmc/ttpmc1253s000" role="session">Generate Patch for New Base VRC (ttpmc1253s000)</Link> session.</ListItem>
				<ListItemHead>Validate the Feature Pack</ListItemHead>
				<ListItem>Validate a Feature Pack in the <Link href="/baanerp/tt/pmc/ttpmc1401s000" role="session">Validate Patch (ttpmc1401s000)</Link> session.</ListItem>
				<ListItemHead>Export the Feature Pack</ListItemHead>
				<ListItem>Export a Feature Pack in the <Link href="/baanerp/tt/pmc/ttpmc1200s000" role="session">Export Solution/Patch (ttpmc1200s000)</Link> session.</ListItem>
				<ListItemHead>Release the Feature Pack</ListItemHead>
				<ListItem><Paragraph class="Default">To release a Feature Pack, change the <Link href="/baanerp/tt/pmc/ttpmc1501m000#ttpmc100.dsta" role="formfield">Status</Link> from <GUIRef href="" role="manual">Exported</GUIRef> to <GUIRef href="" role="manual">Released</GUIRef> in the <Link href="/baanerp/tt/pmc/ttpmc1501m000" role="session">Patches (ttpmc1501m000)</Link> session.</Paragraph>
					<Paragraph class="Default">You can only release a Feature Pack if the <Link href="/baanerp/tt/pmc/ttpmc1501m000#ttpmc100.dsta" role="formfield">Status</Link> of the Feature Pack is <GUIRef href="" role="manual">Exported</GUIRef>.</Paragraph>
				</ListItem>
				<ListItemHead>Publish the Feature Pack</ListItemHead>
				<ListItem><Paragraph class="Default">To publish a Feature Pack, you must select the <Link href="/baanerp/tt/pmc/ttpmc1501m000#ttpmc100.publ" role="formfield">Published</Link> check box in the <Link href="/baanerp/tt/pmc/ttpmc1501m000" role="session">Patches (ttpmc1501m000)</Link> session.</Paragraph>
					<Paragraph class="Default">You can only publish a Feature Pack if the <Link href="/baanerp/tt/pmc/ttpmc1501m000#ttpmc100.dsta" role="formfield">Status</Link> of the Feature Pack is <GUIRef href="" role="manual">Release</GUIRef>.</Paragraph>
					<Paragraph class="Default">This step is optional.</Paragraph>
				</ListItem>
				<ListItemHead>View the Feature Pack history</ListItemHead>
				<ListItem>You can view the Feature Pack history in the <Link href="/baanerp/tt/pmc/ttpmc1560m000" role="session">Maintenance History (ttpmc1560m000)</Link> session.</ListItem>
			</List>
		</GeneralSection>
	</GeneralSection>
	<GeneralSection ID="service_pack_development"><SectionTitle>Feature Pack development</SectionTitle>
		<Paragraph class="Default">This section describes various aspects applicable to the Feature Pack development and build process.</Paragraph>
		<List><ListIntro>This section describes the following topics:</ListIntro>
			<ListItem>System setup for standard products</ListItem>
			<ListItem>System setup for derived products</ListItem>
			<ListItem>Rules for upgrading derived products</ListItem>
			<ListItem>To build Feature Packs and the Infor Installation Wizard</ListItem>
		</List>
		<GeneralSection><SectionTitle>System setup for standard products</SectionTitle>
			<Paragraph class="Default">The subsequent setup assumes that the distributor side includes a combined development/maintenance environment. This combined environment supports the maintenance of already released Feature Packs, development of a new Feature Pack, and the physical creation of solutions and Feature Packs.</Paragraph>
			<Note><SectionTitle>
                                    Note
                                 </SectionTitle>
				<List><ListIntro>The following examples use the following conventions for VRC naming:</ListIntro>
					<ListItemHead>Version: B61&lt;X&gt;</ListItemHead>
					<ListItem>X = <GUIRef href="" role="manual">M</GUIRef> aintenance, <GUIRef href="" role="manual">D</GUIRef> evelopment</ListItem>
					<ListItemHead>Release: a&lt;Y&gt;</ListItemHead>
					<ListItem>Y = Feature Pack number</ListItem>
					<ListItemHead>Customer: &lt;zzzz&gt;</ListItemHead>
					<ListItem>zzzz = extension/localization code</ListItem>
				</List>
			</Note>
			<Figure space-and-orientation="indented-estimated"><FigIntro>The following figures illustrate the results over time:</FigIntro>
				<HTML:IMG width="484" height="184" SRC="../images/pmc_sp_development_1.gif" path="/enterpriseserver/tools/tt/onlinemanual" btb-count="1" btb-count2="1" btb-image-name="pmc_sp_development_1.gif" btb-source-path="C:\SVN\docnl\Technology\EnterpriseServer~8.5\EnterpriseServer" btb-image-path="/enterpriseserver/tools/tt/images/pmc_sp_development_1.gif" ID="IDABHXBC" alt="[...]" xmlns:HTML="http://www.w3.org/TR/REC-html40"/></Figure>
			<Paragraph class="Default">As soon as the initial master product, B61_a, which for the sake of simplicity is referred to simply as Feature Pack 0 in the remainder of this document, is released, the maintenance starts for B61_a in the maintenance VRC B61M_a. The development of the new Feature Pack is carried out in B61D_a1. All fixes in B61M_a are ported to B61D_a1. In the PMC registry of B61D_a1, these fixes are registered as obsolete solutions. After B61D_a1 is frozen, a final Feature Pack is created for the Feature Pack and installed in the same environment to enable you to perform maintenance on the Feature Pack.</Paragraph>
			<Note><SectionTitle>
                                    Note
                                 </SectionTitle>
				<Paragraph class="Default">The SCM revision data is not available in the Feature Pack VRC B61_a1, because the export/import software does not support the transfer of revisions. Because the original development VRC B61D_a1 is still present, you can still view revisions.</Paragraph>
			</Note>
			<Figure space-and-orientation="indented-estimated"><HTML:IMG width="664" height="303" SRC="../images/pmc_sp_development_2.gif" path="/enterpriseserver/tools/tt/onlinemanual" btb-count="1" btb-count2="1" btb-image-name="pmc_sp_development_2.gif" btb-source-path="C:\SVN\docnl\Technology\EnterpriseServer~8.5\EnterpriseServer" btb-image-path="/enterpriseserver/tools/tt/images/pmc_sp_development_2.gif" ID="IDAKHXBC" alt="[...]" xmlns:HTML="http://www.w3.org/TR/REC-html40"/></Figure>
			<Paragraph class="Default">Currently, you can maintain B61M_a and B61M_a1, Feature Pack 0 and Feature Pack 1, in parallel. You must port bug fixes that are created for Feature Pack 0 between the freeze moment and the time of installation of Feature Pack 1 first. Feature Pack 2, B61D_a2, is currently in development.</Paragraph>
			<Paragraph class="Default">You can repeat this cycle unlimited times for each new Feature Pack.</Paragraph>
		</GeneralSection>
		<GeneralSection><SectionTitle>System setup for derived products</SectionTitle>
			<Paragraph class="Default">The setup becomes a bit more complex if derived products such as localizations or extensions enter the scope.</Paragraph>
			<Note><SectionTitle>
                                    Note
                                 </SectionTitle>
				<Paragraph class="Default">Customizations are also a type of derived products. For customizations, the situation differs somwhat. The section <Link href="#customizations" role="internal">Customizations</Link> describes how to deal with customizations.</Paragraph>
			</Note>
			<Paragraph class="Default">Suppose you must create a localization on top of Feature Pack 1.</Paragraph>
			<Figure space-and-orientation="indented-estimated"><FigIntro>A new VRC is created on top of Feature Pack 1, B61D_a1_loc1:</FigIntro>
				<HTML:IMG width="664" height="303" SRC="../images/pmc_sp_development_3.gif" path="/enterpriseserver/tools/tt/onlinemanual" btb-count="1" btb-count2="1" btb-image-name="pmc_sp_development_3.gif" btb-source-path="C:\SVN\docnl\Technology\EnterpriseServer~8.5\EnterpriseServer" btb-image-path="/enterpriseserver/tools/tt/images/pmc_sp_development_3.gif" ID="IDATHXBC" alt="[...]" xmlns:HTML="http://www.w3.org/TR/REC-html40"/></Figure>
			<Paragraph class="Default">The localization is built on top of the standard Feature Pack and is delivered as a Feature Pack in PMC. Therefore, you must not create master media for derived products. As soon as Feature Pack 0 for the localization is available, the Feature Pack is installed in the maintenance VRC, B61M_a1_loc1.</Paragraph>
			<Figure space-and-orientation="indented-estimated"><FigIntro>The localization is also copied to a development VRC B61D_a2_loc1:</FigIntro>
				<HTML:IMG width="628" height="353" SRC="../images/pmc_sp_development_4.gif" path="/enterpriseserver/tools/tt/onlinemanual" btb-count="1" btb-count2="1" btb-image-name="pmc_sp_development_4.gif" btb-source-path="C:\SVN\docnl\Technology\EnterpriseServer~8.5\EnterpriseServer" btb-image-path="/enterpriseserver/tools/tt/images/pmc_sp_development_4.gif" ID="IDA2HXBC" alt="[...]" xmlns:HTML="http://www.w3.org/TR/REC-html40"/></Figure>
			<Paragraph class="Default">The first action that you must perform is to merge all bug-fixes of the standard VRC B61M_a1 into the localization maintenance VRC B61M_a1_loc1 and to create PMC solutions for the localization.</Paragraph>
			<Paragraph class="Default">In addition, you must merge the B61D_a2 functional enhancements to B61D_a2_loc1.</Paragraph>
			<Paragraph class="Default">From this moment on, the localization follows the same Feature Pack cycle as the standard software.</Paragraph>
			<Paragraph class="Default">Repeat the same approach for Feature Pack 2.</Paragraph>
			<Paragraph class="Default">The physical Feature Packs for the standard software and the localization are created and installed in a separate VRC tree B61_a2 and B61L_a2_loc1. New maintenance and development VRCs are created.</Paragraph>
			<Figure space-and-orientation="indented-estimated"><FigIntro>The maintenance and development VRC for the localization are populated with the components from the installed Feature Pack B61L_a2_loc1.</FigIntro>
				<HTML:IMG width="680" height="544" SRC="../images/pmc_sp_development_5.gif" path="/enterpriseserver/tools/tt/onlinemanual" btb-count="1" btb-count2="1" btb-image-name="pmc_sp_development_5.gif" btb-source-path="C:\SVN\docnl\Technology\EnterpriseServer~8.5\EnterpriseServer" btb-image-path="/enterpriseserver/tools/tt/images/pmc_sp_development_5.gif" ID="IDAIIXBC" alt="[...]" xmlns:HTML="http://www.w3.org/TR/REC-html40"/></Figure>
		</GeneralSection>
		<GeneralSection ID="rules_for_upgrading_derived_products"><SectionTitle>Rules to upgrade derived products</SectionTitle>
			<List><ListIntro>The following rules apply with respect to the creation of Feature Packs for derived products:</ListIntro>
				<ListItem>You must only build Feature Packs for derived products on top of Feature Packs of the parent product. Do not build Feature Packs on top of a Feature Pack plus a number of individual solutions of the parent product. The reason for this is because you can only define PMC dependencies between the Feature Pack of the standard and the derived products. You cannot define PMC dependencies from the Feature Pack of the derived product to individual solutions of the parent product.</ListItem>
				<ListItem>The Feature Pack frequency of derived products can be greater than the Feature Pack frequency of the parent product. Therefore, you can build multiple derived Feature Packs on top of a single Feature Pack of the parent product.</ListItem>
				<ListItem>The Feature Pack frequency of derived products cannot be lower than the Feature Pack frequency of the parent product. If you do not update a derived product in time, you will most likely face various compatibility issues between the parent and the derived product.</ListItem>
			</List>
		</GeneralSection>
		<GeneralSection ID="building_service_packs_and_the_installation_wizard"><SectionTitle>Building Feature Packs and the Infor Installation Wizard</SectionTitle>
			<List><ListIntro>PMC Feature Packs are installable units that you can install by means of the Infor Installation Wizard. Metadata that is included in a Feature Pack controls the behavior of the Infor Installation Wizard. The following aspects are relevant if you want to make your Feature Pack suitable for installation with the Infor Installation Wizard:</ListIntro>
				<ListItem>Before you build a Feature Pack, be sure to fill in the installable unit key, name, and version are filled at your PMC base VRC. If you do not fill in these values, the Infor Installation Wizard will not recognize the installable unit. For more details, refer to the <Link href="/baanerp/tt/pmc/ttpmc0110m000" role="session">Base VRC's (ttpmc0110m000)</Link> session.</ListItem>
				<ListItem>Before you export a Feature Pack, be sure that the Feature Pack header contains the correct properties. Based on the properties defined in the Feature Pack header, the Infor Installation Wizard can automatically perform particular actions at a recipient system, such as create new package combinations, create new update VRCs, and link new update VRCs to an existing or new package combination. For more details, refer to the <Link href="/baanerp/tt/pmc/ttpmc1106m000" role="session">Patch Header (ttpmc1106m000)</Link> session.</ListItem>
			</List>
		</GeneralSection>
	</GeneralSection>
	<GeneralSection ID="customizations"><SectionTitle>Customizations</SectionTitle>
		<Paragraph class="Default">This section describes various aspects relevant to the development and maintenance process of customizations.</Paragraph>
		<Paragraph class="Default">Customizations are, in most cases, built by organizations other than the producer of the related parent standard product.</Paragraph>
		<Paragraph class="Default">The vendor who builds customizations installs the standard parent product in an update VRC.</Paragraph>
		<Paragraph class="Default">The customization is built on top of the installed parent standard product.</Paragraph>
		<Paragraph class="Default">This situation is specific in the sense that PMC serves both as recipient and distributor in such a development environment.</Paragraph>
		<List><ListIntro>The following sections describe best practices how to develop and maintain customizations.</ListIntro>
			<ListItem>Patches and customizations</ListItem>
			<ListItem>Feature Packs and customizations</ListItem>
			<ListItem>Dependencies for customizations</ListItem>
			<ListItem>Other</ListItem>
		</List>
		<GeneralSection><SectionTitle>Patches and customizations</SectionTitle>
			<Paragraph class="Default">In some cases, the vendor of the standard parent product applies patches rather than Feature Packs as a method to provide incremental updates to the market. As opposed to Feature Packs, patches are not cumulative. The installation of a patch in an update VRC requires that you also install all preceding update VRCs in the same update VRC. This issue has consequences for the VRC setup at the distributor.</Paragraph>
			<Paragraph class="Default">In most cases, you use a single environment to develop and to maintain multiple customizations. You build every customization on a specific patch. In addition, you must periodically upgrade existing customizations to a newer patch. As a result, you must have multiple Feature Packs of the standard parent product installed in separate VRCs. The following method is the best way to achieve this:</Paragraph>
			<Paragraph class="Default">Install patch 1 of the standard parent product in update VRC P10U_a1_stnd. When patch 2 is available, install the patch in a new, separate update VRC P10U_a2_stnd, which is derived from P10U_a1_stnd. Patch 2 will have patch 1 as a prerequisite. You cannot install patch 2 in the new update VRC P10U_a2_stnd because patch 1 is not installed in this new update VRC. Therefore, run the <Link href="/baanerp/tt/pmc/ttpmc2290m000" role="session">Copy Solution Registry to Derived Update VRC (ttpmc2290m000)</Link> session and copy the registry of update VRC P10_a1_stnd into P10_a2_stnd. After you perform this step, you can install patch 2 directly in the P10U_a2_stnd update VRC. You can then repeat this same process for subsequent patches. The P10U_a&lt;n&gt;_stnd VRCs must only contain net patches. No additional solutions must be installed in these VRCs that do not belong to the relevant patch.</Paragraph>
			<Paragraph class="Default">At this point, you have a VRC tree in which the net patches are installed in separate VRCs. In general, customizations are developed based on a net patch. However, in some cases customizations are not derived from a net patch, or a customer might want to install parent standard product solutions that have components which overlap with the customization. As a result, the customer must have the option to derive the customization VRC from any possible maintenance stage of the parent standard product. The P10U_a&lt;n&gt;_std update VRCs are introduced to achieve this. For every customization an intermediate VRC layer is introduced in which standard solutions can be installed that do not belong to the underlying patch. You can again use the <Link href="/baanerp/tt/pmc/ttpmc2290m000" role="session">Copy Solution Registry to Derived Update VRC (ttpmc2290m000)</Link> session to populate the PMC registry for the P10U_a&lt;n&gt;_std update VRCs.</Paragraph>
			<Paragraph class="Default">The customization VRCs P10C_a_cusA, P10C_a_cusB, and P10C_a_cusC represent various various customizations that are derived from various patches. Suppose customization P10C_a_cusA is developed based on the net patch 1. During development of the customization, the P10U_a1_stdA VRC will still be empty. After the customization is released and the customer installs the customization, the customer might want to install solutions of the standard parent product that also require an update of the customization. In this case, the customization vendor can install the solutions of the parent standard product in the P10U_a1_stdA VRC, port the solution to the P10C_a_cusA and provide a corresponding solution for the customization VRC. Installation of solutions in the P10U_a1_stdA VRC will only have impact on the P10C_a_cusA customization and will not impact the other customizations in the environment.</Paragraph>
			<Figure space-and-orientation="indented-estimated"><HTML:IMG width="664" height="662" SRC="../images/pmc_customizations_1.gif" path="/enterpriseserver/tools/tt/onlinemanual" btb-count="1" btb-count2="1" btb-image-name="pmc_customizations_1.gif" btb-source-path="C:\SVN\docnl\Technology\EnterpriseServer~8.5\EnterpriseServer" btb-image-path="/enterpriseserver/tools/tt/images/pmc_customizations_1.gif" ID="IDAEBXBC" alt="[...]" xmlns:HTML="http://www.w3.org/TR/REC-html40"/></Figure>
		</GeneralSection>
		<GeneralSection><SectionTitle>Feature Packs and Customizations</SectionTitle>
			<Paragraph class="Default">To a certain extent, the system setup is comparable to the setup described for localizations and extensions described in the section <Link href="#service_pack_development" role="internal">Feature Pack Development</Link>. The main difference lies in the fact that Feature Packs for the parent standard product are now installed in an update VRC by means of PMC. Another differentiator is the fact that Feature Packs are cumulative, which means that Feature Packs also contain all preceding Feature Packs. To upgrade a customization to a higher Feature Pack level, having a VRC available that only contains the net changes of a Feature Pack of the standard parent product can be useful. Suppose you must create a customization on top of Feature Pack 1 for a parent standard product. Feature Pack 1 is installed in the B61U_a1_stnd update VRC and a new VRC B61W_a1_cusA is developed on top of the Feature Pack.</Paragraph>
			<Figure space-and-orientation="indented-estimated"><HTML:IMG width="484" height="303" SRC="../images/pmc_customizations_2.gif" path="/enterpriseserver/tools/tt/onlinemanual" btb-count="1" btb-count2="1" btb-image-name="pmc_customizations_2.gif" btb-source-path="C:\SVN\docnl\Technology\EnterpriseServer~8.5\EnterpriseServer" btb-image-path="/enterpriseserver/tools/tt/images/pmc_customizations_2.gif" ID="IDANBXBC" alt="[...]" xmlns:HTML="http://www.w3.org/TR/REC-html40"/></Figure>
			<Paragraph class="Default">The customization is built on top of the standard Feature Pack and will be delivered as a Feature Pack in PMC, so no master media must be created for the customization. As soon as Feature Pack 0 for the customization is available, the Feature Pack is installed in the maintenance VRC B61M_a1_cusA.</Paragraph>
			<Note><SectionTitle>
                                    Note
                                 </SectionTitle>
				<Paragraph class="Default">In theory, you can also skip the installation of the FP in the B61M_a1_cus1 VRC and start maintenance immediately in the B61D_a1_cus1 VRC. However, best practice is to install and maintain the official build that customers also receive.</Paragraph>
			</Note>
			<Figure space-and-orientation="indented-estimated"><HTML:IMG width="634" height="305" SRC="../images/pmc_customizations_3.gif" path="/enterpriseserver/tools/tt/onlinemanual" btb-count="1" btb-count2="1" btb-image-name="pmc_customizations_3.gif" btb-source-path="C:\SVN\docnl\Technology\EnterpriseServer~8.5\EnterpriseServer" btb-image-path="/enterpriseserver/tools/tt/images/pmc_customizations_3.gif" ID="IDAWBXBC" alt="[...]" xmlns:HTML="http://www.w3.org/TR/REC-html40"/></Figure>
			<Paragraph class="Default">Solutions for Feature Pack 1 of the parent standard product will be installed in the B61U_a1_stnd VRC. When you scan solutions for the parent standard product, you can also print a customization report. The customization report provides an overview of which components must be updated in the B61M_a1_cusA VRC. As soon as you install the standard solution, you can merge the changes to the B61M_a1_cusA VRC and create a corresponding PMC solution for the customization.</Paragraph>
			<Paragraph class="Default">The approach for subsequent Feature Packs is as follows: Install Feature Pack 2 for the parent standard product in the B61U_a2_stnd VRC, which is derived from B61_a VRC. Copy the contents of the B61M_a1_cusA VRC to the B61W_a2_cusA VRC. As a result, all maintenance changes you create on top of Feature Pack 0 of the customization until the moment of the copy action immediately become available in the B61W_a2_cusA VRC. After the copy, you must also port all maintenance changes in the B61M_a1_cusA VRC to the B61W_a2_cusA VRC. Feature Pack 2 for the standard product is cumulative, which means that all changes implemented in Feature Pack 1 are also present in Feature Pack 2. Therefore, you must create an overview of all components that were changed in Feature Pack 2 as compared to Feature Pack 1, and these components also must be present in the customization. To achieve this, you can use the <Link href="/baanerp/tt/adv/ttadv6450m000" role="session">Compare Package VRC's (ttadv6450m000)</Link> session. In this session, specify values in the following fields as follows:</Paragraph>
			<TABLE border="1" borderstyle="default" space-and-orientation="indented-estimated"><TBODY><TR><TD rowspan="1" colspan="1">VRC 1</TD>
						<TD rowspan="1" colspan="1">B61U_a1_stnd</TD>
					</TR>
					<TR><TD rowspan="1" colspan="1">VRC 2</TD>
						<TD rowspan="1" colspan="1">B61U_a2_stnd</TD>
					</TR>
					<TR><TD rowspan="1" colspan="1">Where Software Components present in VRC</TD>
						<TD rowspan="1" colspan="1">B61W_a2_cusA</TD>
					</TR>
				</TBODY>
			</TABLE>
			<Paragraph class="Default">Using these settings enable you to create a net overview of customized components that must be updated to be compatible with the Feature Pack 2 of the parent standard product. You can then merge all changes implemented in Feature Pack 2 of the standard product from the B61U_2_stnd VRC into the B61W_a2_cusA VRC. You can then build Feature Pack 1 for the customization, based on the contents of the B61D_a2_cusA VRC.</Paragraph>
			<Figure space-and-orientation="indented-estimated"><HTML:IMG width="664" height="305" SRC="../images/pmc_customizations_4.gif" path="/enterpriseserver/tools/tt/onlinemanual" btb-count="1" btb-count2="1" btb-image-name="pmc_customizations_4.gif" btb-source-path="C:\SVN\docnl\Technology\EnterpriseServer~8.5\EnterpriseServer" btb-image-path="/enterpriseserver/tools/tt/images/pmc_customizations_4.gif" ID="IDA5BXBC" alt="[...]" xmlns:HTML="http://www.w3.org/TR/REC-html40"/></Figure>
			<Paragraph class="Default">You can repeat this procedure for an unlimited number of Feature Packs. In addition, you can develop and maintain multiple customizations in parallel on various levels of the standard parent product.</Paragraph>
			<Paragraph class="Default">If multiple customization VRCs are derived from, for example, the B61U_a1_stnd VRC, then for every customization, an additional update VRC layer B61U_a1_std is required between the customization VRC and the B61U_a2_stnd VRC. You can use the additional update VRC layer to install additional solutions of the parent product, which you must port to the customization. You must use the <Link href="/baanerp/tt/pmc/ttpmc2290m000" role="session">Copy Solution Registry to Derived Update VRC (ttpmc2290m000)</Link> session to populate the PMC registry for the B61U_a1_std update VRCs. Installation of additional solutions in the B61U_a1_stdA update VRC only impacts the B61M_a_cusA VRC and does not influence the B61M_a1_cusB VRC.</Paragraph>
			<Figure space-and-orientation="indented-estimated"><HTML:IMG width="686" height="325" SRC="../images/pmc_customizations_5.gif" path="/enterpriseserver/tools/tt/onlinemanual" btb-count="1" btb-count2="1" btb-image-name="pmc_customizations_5.gif" btb-source-path="C:\SVN\docnl\Technology\EnterpriseServer~8.5\EnterpriseServer" btb-image-path="/enterpriseserver/tools/tt/images/pmc_customizations_5.gif" ID="IDAICXBC" alt="[...]" xmlns:HTML="http://www.w3.org/TR/REC-html40"/></Figure>
		</GeneralSection>
		<GeneralSection><SectionTitle>Dependencies for customizations</SectionTitle>
			<Paragraph class="Default">Individual solutions, patches and/or Feature Packs for customizations must have dependencies to corresponding updates of the parent standard product. Not having these types of dependencies can result in runtime compatibility problems if only a solution for the standard parent product is installed, while installation of an update for the customizations was also required.</Paragraph>
			<Paragraph class="Default">The best way to establish these dependencies is to define co-requisite dependencies between the updates of the parent product and the corresponding updates for the customized product. The co-requisite dependencies are generated automatically if the customization uses the same solution numbers that were also used in the parent standard product. Of course this method only works if the base VRC of the customization, together with the base VRC of the standard parent product, are part of the same base VRC combination at the distributor side. At the recipient side, the update VRCs for the parent standard product and the customization must also be included in a VRC combination.</Paragraph>
			<Paragraph class="Default">The co-requisite relationship will only be in one direction: from the customization to the standard parent product. This one-directional co-requisite makes it impossible to install a solution for the customization without simultaneously installing the corresponding standard solution for the parent product. However, as long as you have not scanned the customized solution, you can still install a solution for the standard parent product without simultaneously installing the corresponding solution of the customization. This can result in run time compatibility problems. The customization report solves this problem. When you check standard solutions in a customized environment, you can optionally print a customization report, which signals customized components and informs the recipient that, together with the standard solution, an update for the customization must also be installed.</Paragraph>
		</GeneralSection>
		<GeneralSection><SectionTitle>Other</SectionTitle>
			<Paragraph class="Default">The facts described in the sections <Link href="#rules_for_upgrading_derived_products" role="internal">Rules for Upgrading Derived Products</Link> and <Link href="#building_service_packs_and_the_installation_wizard" role="internal">Building Feature Packs and the Infor Installation Wizard</Link> are also applicable to the development and maintenance of customizations.</Paragraph>
		</GeneralSection>
	</GeneralSection>
</ManualTopic>
