<?xml version="1.0" encoding="utf-8"?>
<ManualTopic ID="/baanerp/tt/onlinemanual/vrm_package_combinations" xml:lang="en">
	<Header>
		<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Package combinations</Title>
		<Keyword ContextSensitive="No"><Level1>Version and release management</Level1>
			<Level2>package combinations</Level2>
		</Keyword>
		<Keyword ContextSensitive="No"><Level1>Package combination</Level1>
		</Keyword>
	</Header>
	<AimSection><Paragraph class="Default">A <Link href="/baanerp/tt/glossary/glossary#000000000000012" role="glossary">package combination</Link> is a collection of various ERP LN packages. Every package combination has a unique <Link href="/baanerp/tt/glossary/glossary#100016" role="glossary">VRC</Link>. The package combination links users to a specific version of the ERP LN software. A package combination can be linked to one or more users and to one or more companies. However, a package combination can contain only one version of a package, which is identified by a package VRC. In fact, a package combination links users to a specific version of the ERP LN software.</Paragraph>
	</AimSection>
	<GeneralSection><Figure space-and-orientation="indented-estimated"><FigIntro>The following figure shows an example of a standard package combination:</FigIntro>
			<HTML:IMG width="489" height="292" SRC="../images/tr_graph_vrm_package_combinationsa.gif" path="/enterpriseserver/tools/tt/onlinemanual" btb-count="1" btb-count2="1" btb-image-name="tr_graph_vrm_package_combinationsa.gif" btb-source-path="C:\SVN\docnl\Technology\EnterpriseServer~8.5\EnterpriseServer" btb-image-path="/enterpriseserver/tools/tt/images/tr_graph_vrm_package_combinationsa.gif" ID="IDAQIYBC" alt="[...]" xmlns:HTML="http://www.w3.org/TR/REC-html40"/><FigCaption>Example of a software environment with a standard package combination</FigCaption>
		</Figure>
		<Paragraph class="Default">This figure shows an example of a standard package combination, which contains a number of standard package VRCs, such as the standard version of ERP LN Financials.</Paragraph>
	</GeneralSection>
	<GeneralSection><SectionTitle>Package combination code</SectionTitle>
		<Paragraph class="Default">Package combinations in ERP LN are identified by a unique identifier. For example, the package combination B61O_b_sbc1 represents SBC’s (Strangely Brown Chicken company) first customization on the standard software in the B61_b VRC of all packages. ERP LN uses the following format to identify package combinations:</Paragraph>
		<Paragraph class="Default">vvvt rr gggn</Paragraph>
		<Paragraph class="Default">The following table provides more information on the codes that you can use to identify package VRCs:</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">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. This field is not filled for the standard software. <List><ListIntro>The following type codes are available:</ListIntro>
							<ListItem>S The standard package combination.</ListItem>
							<ListItem>C The package combination, for a specific customer, ordered by the customer and developed by a dealer or partner.</ListItem>
							<ListItem>O The package combination developed by the customer. This type of package combination contains 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 in 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>
	</GeneralSection>
</ManualTopic>
