<?xml version="1.0" encoding="utf-8"?>
<Glossary ID="/baanerp/tl/glossary/glossary" xml:lang="en">
	<Header>
		<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Glossary for the TL package</Title>
	</Header>
	<GlossaryEntry ID="000005"><Term>hard reference</Term>
		<Definition>A reference from one table to another table that is defined in the data dictionary.</Definition>
		<Antonym><Link href="/baanerp/tl/glossary/glossary#000006" role="glossary">soft reference</Link>
		</Antonym>
	</GlossaryEntry>
	<GlossaryEntry ID="IDA252MB"><Term>hard reference</Term>
		<Definition>See: <Link href="#000006" role="internal">soft reference</Link>
		</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000004"><Term>multicompany environment</Term>
		<Definition>A collection of companies.</Definition>
		<SimpleSection><Paragraph class="Default">A multicompany environment is used to limit a table sharing set to a fixed set of companies.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000048" ContextApps="tt"><Term>reference type</Term>
		<Definition>See: <Link href="/baanerp/tt/glossary/glossary#000046" role="glossary">reference</Link>
		</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000101" ContextApps="tlvsc"><Term>rule</Term>
		<Definition>A criterion to measure the quality of software components.</Definition>
		<SimpleSection><Paragraph class="Default">The rules used by <Link href="/baanerp/tl/glossary/glossary#000100" role="glossary" Update="No">VSC</Link> are, among other things, based on the Infor ERP LN Software Coding Standards (SCS), the Infor ERP LN Software Programming Standards (SPS), and the Infor ERP LN Performance Guide.</Paragraph>
			<List><ListIntro>Some examples of rules are:</ListIntro>
				<ListItem>A table code must have the following structure: <Emphasis>pp mmm s xx</Emphasis>, where <Emphasis>pp</Emphasis> is the package code, <Emphasis>mmm</Emphasis> is the module code, <Emphasis>s</Emphasis> is the submodule code (only when numeric), and <Emphasis>xx</Emphasis> is the sequence number.</ListItem>
				<ListItem>A message called in a script, should not be expired.</ListItem>
				<ListItem>A query that performs an update must have a 'with retry' clause.</ListItem>
			</List>
			<Paragraph class="Default">Most rules are hardcoded in the VSC software. However, some rules that are used to analyze scripts are implemented as <Link href="/baanerp/tl/glossary/glossary#000105" role="glossary">source analyze codes</Link>.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000106" ContextApps="tlvsc"><Term>rule database</Term>
		<Definition>A database with detailed information about <Link href="/baanerp/tl/glossary/glossary#000101" role="glossary" Update="No">rules</Link>.</Definition>
		<SimpleSection><List><ListIntro>The rule database contains:</ListIntro>
				<ListItem>Detailed information about the rules that are implemented in VSC.</ListItem>
				<ListItem>Information about rules that might be added in future VSC versions.</ListItem>
			</List>
			<Paragraph class="Default">This database is intended for internal use by the ERP LN development department only, and is therefore not delivered with the VSC software.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="IDA512MB"><Term>soft reference</Term>
		<Definition>See: <Link href="#000005" role="internal">hard reference</Link>
		</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000006"><Term>soft reference</Term>
		<Definition>A reference from one table to another table that is embedded in a program script or dll.</Definition>
		<Antonym><Link href="/baanerp/tl/glossary/glossary#000005" role="glossary">hard reference</Link>
		</Antonym>
	</GlossaryEntry>
	<GlossaryEntry ID="000105" ContextApps="tlvsc"><Term>source analyze code</Term>
		<Definition>A code that is used by <Link href="/baanerp/tl/glossary/glossary#000100" role="glossary" Update="No">VSC</Link> to perform user-defined checks on scripts such as UI scripts, DLLs and DALs.</Definition>
		<SimpleSection><Paragraph class="Default">Each source analyze code is linked to an expression text and to a warning message. The expression text contains a search pattern, which is used to find errors.</Paragraph>
			<Paragraph class="Default">For details, refer to <Link href="/baanerp/tl/onlinemanual/vsc_source_analyze_codes" role="manual">Source Analyze Codes</Link>.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000002" ContextApps="tltsm"><Term>table set</Term>
		<Definition>A set of tables that is being considered for table sharing. By using the <GUIRef href="/baanerp/tl/tsm" role="manual">Table Sharing Modeler</GUIRef> tool you can simulate what happens if these tables, and <Emphasis>only</Emphasis> these tables, are shared.</Definition>
		<SimpleSection><List><ListIntro>You can have two kinds of table sets:</ListIntro>
				<ListItem>A small table set which corresponds with a specific functional requirement, for example, <Emphasis>central purchasing</Emphasis>. You can use this table set to find out which other tables need to be shared because of table references.</ListItem>
				<ListItem>An extended table set that contains not only the tables that must be shared for functional reasons, but also all other tables that must be shared for technical reasons. You can use this table set to verify the completeness of the table set. You can also use this table set to do the actual table linking.</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000001"><Term>Table Sharing Modeler</Term>
		<Definition>A tool to analyze and set up a table sharing configuration that suits the purpose of the ERP LN user without jeopardizing the data integrity.</Definition>
		<SimpleSection><Paragraph class="Default">The Table Sharing Modeler is implemented in the <GUIRef href="/baanerp/tl/tsm" role="module">Table Sharing Modeler</GUIRef> module in the <GUIRef href="/baanerp/tl" role="module">Tools Add-ons</GUIRef> package.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000003"><Term>table sharing set</Term>
		<Definition>A proposed table sharing configuration.</Definition>
		<SimpleSection><Paragraph class="Default">A table sharing set contains a collection of table sets. The table sharing set defines for each of these table sets exactly which logical companies are linked to which physical companies.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000103" ContextApps="tlvsc"><Term>verification code</Term>
		<Definition>A code that identifies a selection of <Link href="/baanerp/tl/glossary/glossary#000100" role="glossary" Update="No">VSC</Link> checks for software components in one or more package combinations.</Definition>
		<SimpleSection><Paragraph class="Default">A verification code is usually linked to one or more <Link href="/baanerp/tl/glossary/glossary#000104" role="glossary" Update="No">verification filters</Link>.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000104" ContextApps="tlvsc"><Term>verification filter</Term>
		<Definition>A selection of <Link href="/baanerp/tl/glossary/glossary#000100" role="glossary" Update="No">VSC</Link> checks for which warnings must be generated.</Definition>
		<SimpleSection><Paragraph class="Default">A <Link href="/baanerp/tl/glossary/glossary#000103" role="glossary">verification code</Link> usually is linked to one generic verification filter and one or more specific verification filters.</Paragraph>
			<List><ListIntro>The generic filter defines the checks that are executed to verify all software components in all packages. Depending on the filter settings, the checks in the generic filter can generate two types of <Link href="/baanerp/tl/glossary/glossary#000102" role="glossary" Update="No">warnings</Link>:</ListIntro>
				<ListItem>"Filtered to Handle" warnings. You must handle these warnings immediately. You must either solve or accept these filtered warnings.</ListItem>
				<ListItem>"Non-filtered" warnings that you do not have to handle immediately.</ListItem>
			</List>
			<Paragraph class="Default">Specific filters are used to reduce the number of "FiItered to Handle" warnings for a specific package, module or VRC. Each specific filter is derived from the generic filter, and therefore executes exactly the same checks as the generic filter. In a specific filter, you can indicate for each check whether you want to generate "FiItered to Handle" warnings or "Non-filtered" warnings.</Paragraph>
			<Paragraph class="Default">Note: you cannot disable checks, or add extra checks in a specific filter. If you select a check, which is not present in the generic filter, VSC ignores this check.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000100" ContextApps="tlvsc"><Term>Verify Software Components</Term>
		<Definition>A utility to perform a quality check on the software components, which are developed or changed in Infor ERP LN.</Definition>
		<Acronym>VSC</Acronym>
	</GlossaryEntry>
	<GlossaryEntry ID="IDAAG3MB"><Term>VSC</Term>
		<Definition>See: <Link href="#000100" role="internal">Verify Software Components</Link>
		</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000102" ContextApps="tlvsc"><Term>warning</Term>
		<Definition>A message that explains an error that is found during a <Link href="/baanerp/tl/glossary/glossary#000100" role="glossary" Update="No">VSC</Link> check.</Definition>
		<SimpleSection><List><ListIntro>Depending on the <Link href="/baanerp/tl/glossary/glossary#000104" role="glossary">verification filter</Link> settings, VSC generates:</ListIntro>
				<ListItem>"Filtered to Handle" warnings. You must handle these warnings immediately. You must either solve or accept these filtered warnings.</ListItem>
				<ListItem>"Non-filtered" warnings that you do not have to handle immediately.</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
</Glossary>
