<?xml version="1.0" encoding="utf-8"?>
<ManualTopic ID="/baanerp/tt/onlinemanual/vrm_package_vrcs" xml:lang="en">
	<Header>
		<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Package VRCs</Title>
		<Keyword ContextSensitive="No"><Level1>Version and release management</Level1>
			<Level2>package VRCs</Level2>
		</Keyword>
		<Keyword ContextSensitive="No"><Level1>Package VRC</Level1>
		</Keyword>
	</Header>
	<AimSection><Paragraph class="Default">Each ERP LN package is distributed as a <Link href="/baanerp/tt/glossary/glossary#000000000000013" role="glossary">package VRC</Link>, which represents a specific version of that package. VRC stands for version release customer code, and it identifies the development stage of the ERP LN software.</Paragraph>
	</AimSection>
	<GeneralSection><List><ListIntro>A VRC consists of the following:</ListIntro>
			<ListItem>A version code that identifies a major ERP LN software modification</ListItem>
			<ListItem>A release code that identifies a minor ERP LN software modification</ListItem>
			<ListItem>A customer extension code that identifies ERP LN software for a specific customer</ListItem>
		</List>
		<Paragraph class="Default">A package, for example, ERP LN Financials, can have more than one version. Each version is identified by a specific package VRC. For example, ERP LN Financials can have a package VRC that contains the standard software of ERP LN Financials and a package VRC that contains the customizations on the standard software of ERP LN Financials.</Paragraph>
		<Paragraph class="Default">As a rule, a new package VRC is derived from a previous package VRC. To avoid duplication of software components, a new VRC only contains those software components that have changed compared to previous VRCs.</Paragraph>
		<Figure space-and-orientation="indented-estimated"><FigIntro>The following figure shows an example of the VRC derivation structure:</FigIntro>
			<HTML:IMG width="486" height="339" SRC="../images/nt_graph_vrm_package_vrcsa.gif" path="/enterpriseserver/tools/tt/onlinemanual" btb-count="1" btb-count2="1" btb-image-name="nt_graph_vrm_package_vrcsa.gif" btb-source-path="C:\SVN\docnl\Technology\EnterpriseServer~8.5\EnterpriseServer" btb-image-path="/enterpriseserver/tools/tt/images/nt_graph_vrm_package_vrcsa.gif" ID="IDA2RWBC" alt="[...]" xmlns:HTML="http://www.w3.org/TR/REC-html40"/><FigCaption>An example of a VRC derivation structure</FigCaption>
		</Figure>
		<List><ListIntro>In this example, B60_a is the VRC that contains the standard software. The following two new VRCs are derived from this VRC:</ListIntro>
			<ListItem>The VRC B60C_a_cus1 contains a customized version of the standard software</ListItem>
			<ListItem><List><ListIntro>The VRC B60_b contains a new version of the standard software. From this new standard VRC, two new customized versions are derived:</ListIntro>
					<ListItem>B60C_b_cus1</ListItem>
					<ListItem>B60C_b_cus2.</ListItem>
				</List> The VRCs B60C_b_cus1 and B60C_b_cus2 contain several customizations on the B60_b standard version.</ListItem>
		</List>
	</GeneralSection>
	<GeneralSection><SectionTitle>Package VRC code</SectionTitle>
		<Paragraph class="Default">A unique identifier identifies package VRCs in ERP LN. ERP LN uses the following format to identify package VRCs, the codes of which are described in the following table:</Paragraph>
		<Paragraph class="Default">pp vvvt_rr_gggn</Paragraph>
		<TABLE border="1" borderstyle="default" space-and-orientation="indented-estimated"><THEAD><TR><TD rowspan="1" colspan="1">Code</TD>
					<TD rowspan="1" colspan="1">Description</TD>
				</TR>
			</THEAD>
			<TBODY><TR><TD rowspan="1" colspan="1">pp</TD>
					<TD rowspan="1" colspan="1">Package code</TD>
				</TR>
				<TR><TD rowspan="1" colspan="1">vvv</TD>
					<TD rowspan="1" colspan="1">Version code</TD>
				</TR>
				<TR><TD rowspan="1" colspan="1">T</TD>
					<TD rowspan="1" colspan="1">Type code. <List><ListIntro>Denotes customizations on standard software. This field is not filled for the standard software. Possible type codes include the following:</ListIntro>
							<ListItem>L Localizations: Customizations for a specific country.</ListItem>
							<ListItem>B Branch: Customizations for a specific line of business.</ListItem>
							<ListItem>C Customer: Customizations ordered by the customer, developed by a dealer or partner.</ListItem>
							<ListItem>O Own: Customizations developed by the customer.</ListItem>
						</List>
					</TD>
				</TR>
				<TR><TD rowspan="1" colspan="1">rr</TD>
					<TD rowspan="1" colspan="1">Release code</TD>
				</TR>
				<TR><TD rowspan="1" colspan="1">ggg</TD>
					<TD rowspan="1" colspan="1">Customer code: This field is not filled for the standard software.</TD>
				</TR>
				<TR><TD rowspan="1" colspan="1">n</TD>
					<TD rowspan="1" colspan="1">Sequence code</TD>
				</TR>
			</TBODY>
		</TABLE>
		<Paragraph class="Default">For example, for the Strangely Brown Chicken company (SBC), the package VRC tc B60O_b_sbc1 represents the first customization on the standard software in the B60_b VRC of ERP LN Common.</Paragraph>
		<Note><SectionTitle>
                                 Note
                              </SectionTitle>
			<Paragraph class="Default">Customers can only create new VRCs for their own customizations from the standard software. Infor or a partner delivers all other VRC types.</Paragraph>
		</Note>
	</GeneralSection>
</ManualTopic>
