<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/ti/pcf/tipcf0100m000" xml:lang="en">
	<Header>
		<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Product Configuration Parameters (tipcf0100m000)</Title>
	</Header>
	<HelpTopic><AimSection><Paragraph>Use this session to set the <Link href="/baanerp/tc/glossary/glossary#Parameters.tc" role="glossary">parameters</Link> that control the functioning of the <Link href="/baanerp/ti/onlinemanual/tipcf" role="module">Product Configuration (PCF)</Link> module.</Paragraph>
		</AimSection>
		<GeneralSection><Paragraph>You can change the descriptions of predefined variables. In the <GUIRef href="/baanerp/ti/pcf" role="module">Product Configuration</GUIRef> module, you can define constraints by generic item. A number of variables that are predefined in the <GUIRef href="/baanerp/ti/pcf/tipcf0100m000" role="session">Product Configuration Parameters (tipcf0100m000)</GUIRef> session are used in these constraints. Once you saved the parameters, you can no longer change them.</Paragraph>
		</GeneralSection>
		<RelatedTopics><SectionTitle>Related topics</SectionTitle>
			<RelTopic><Link href="/baanerp/ti/onlinemanual/000177" role="manual">Parameter sessions</Link>
			</RelTopic>
			<RelTopic><Link href="/baanerp/ti/onlinemanual/100007" role="manual">How to test the product model</Link>
			</RelTopic>
			<RelTopic><Link href="/baanerp/ti/onlinemanual/100011" role="manual">PCF procedures</Link>
			</RelTopic>
		</RelatedTopics>
	</HelpTopic>
	<Fields><FieldHelp ID="tipcf000.indt"><Header>
				<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Introduction Date</Title>
			</Header>
			<FuncDesc>The date and time that the parameters were changed. The parameters are valid up to the effective date of a more recent parameter setting. The current set has no effective date.</FuncDesc>
		</FieldHelp>
		<FieldHelp ID="tipcf000.mlcs"><Header>
				<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Multilevel PCF Choice Structure</Title>
			</Header>
			<FuncDesc>If this check box is selected, product configuration is applied at multiple levels of the generic product structure.</FuncDesc>
			<SimpleSection><Paragraph>You can use a multi-level question structure for the configuration of <Link href="/baanerp/td/glossary/glossary#ProducVarian.td" role="glossary">product variants</Link>. The advantage of using this structure is that product features are linked to the proper generic items, which results in a more modular configuration structure.</Paragraph>
				<Paragraph>The structure also enables SSA ERP to include or exclude certain sets of questions during the product configuration process.</Paragraph>
			</SimpleSection>
		</FieldHelp>
		<FieldHelp ID="tipcf000.clan"><Header>
				<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">PCF in Customer's Language</Title>
			</Header>
			<FuncDesc>If this check box is selected, the product configurator displays the descriptions of <Link href="/baanerp/ti/glossary/glossary#100000" role="glossary">features</Link>, <Link href="/baanerp/ti/glossary/glossary#100001" role="glossary">options</Link>, and <Link href="/baanerp/ti/glossary/glossary#100003" role="glossary">constraints</Link> in the customer's language. This feature is an important aid for a proper communication with the customer, particularly in the case of telephone sales.</FuncDesc>
			<SimpleSection><Paragraph>If this check box is cleared, the product configurator displays the descriptions of product features, options and constraint validation messages in your own language.</Paragraph>
			</SimpleSection>
			<Note><SectionTitle>Note</SectionTitle>
				<Paragraph>The <GUIRef href="/baanerp/ti/pcf" role="module">Product Configuration</GUIRef> module is language-independent, which means that you can record, for example, the descriptions of product features and options in any language. This is especially of value for the communication with customers and other external relations.</Paragraph>
			</Note>
		</FieldHelp>
		<FieldHelp ID="tipcf000.diop"><Header>
				<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Display Implicit Options</Title>
			</Header>
			<FuncDesc>If this check box is selected, implicit option values are visualized by the product configurator. This means you use <Link href="/baanerp/ti/glossary/glossary#100003" role="glossary">constraints</Link> to determine whether or not certain product features or questions must be filled, and whether a default option value is applicable. With the input of an implicit option value you can also use constraints to indicate whether or not the relevant product feature must be visible during the product configuration process.</FuncDesc>
			<Note><SectionTitle>Note</SectionTitle>
				<Paragraph>You can always deviate from the setting by explicitly specifying this in the constraint of the relevant product feature.</Paragraph>
			</Note>
			<SimpleSection><Paragraph>If this check box is cleared, implicit options are not visualized by the product configurator.</Paragraph>
			</SimpleSection>
		</FieldHelp>
		<FieldHelp ID="tipcf000.text"><Header>
				<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Generate Sales Quotation Texts</Title>
			</Header>
			<FuncDesc>If this check box is selected,SSA ERP generates sales quotation texts for <Link href="/baanerp/td/glossary/glossary#SalesQuotat.td" role="glossary">sales quotations</Link> after the product configuration process.</FuncDesc>
		</FieldHelp>
		<FieldHelp ID="tipcf000.idic"><Header>
				<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Identifying Item Code</Title>
			</Header>
			<FuncDesc>This parameter affects the way in which SSA ERP generates the item code for the product variant when you run the <GUIRef href="/baanerp/td/sls/tdsls4244m000" role="session">Generate (Project) Structure for Sales Orders (tdsls4244m000)</GUIRef> session in the <GUIRef href="/baanerp/ti/pcs" role="module">Project Control</GUIRef> module.</FuncDesc>
			<SimpleSection><Paragraph>If this check box is selected, the customized item code that SSA ERP generates in the <GUIRef href="/baanerp/ti/pcs" role="module">Project Control</GUIRef> module is identical to the generic item code, or to the code generated using the <GUIRef href="/baanerp/ti/pcf/tipcf3101m000" role="session">Generic Item - Settings for Data Generation (tipcf3101m000)</GUIRef> session. Different <Link href="/baanerp/td/glossary/glossary#ProducVarian.td" role="glossary">product variants</Link> that are linked to the same project then refer to the same customized item.</Paragraph>
				<Paragraph>If this check box is cleared,SSA ERP adds a sequence number to the generic item code to generate new item codes for each product variant in the <GUIRef href="/baanerp/ti/pcs" role="module">Project Control</GUIRef> module. You can specify the exact position of this sequence number in the <GUIRef href="/baanerp/ti/pcf/tipcf0100m000#tipcf000.snfp" role="formfield">Sequence Number of Item Code from Position</GUIRef> field and the <GUIRef href="/baanerp/ti/pcf/tipcf0100m000#tipcf000.sntp" role="formfield">Sequence Number of Item Code to Position</GUIRef> field of the current session.</Paragraph>
				<Paragraph>If you configure a standard item, that is, if you configure a generic item with order policy <GUIRef href="/baanerp/tc/domains/opol#anonymous" role="enum">Anonymous</GUIRef>, the check box must be cleared. In that case, the new configured item has no PCS project code as a distinctive feature, so the item code must be distinctive. If the check box is cleared, a new item code is generated by adding a sequence number to the generic item. Also when you use the <GUIRef href="/baanerp/ti/pcf/tipcf3101m000" role="session">Generic Item - Settings for Data Generation (tipcf3101m000)</GUIRef> session to generate new item codes for configured standard items you must clear the check box. If two items are generated with the same configuration, the item codes for these items will be the same. Consequently, you need a sequence number to distinguish between the items.</Paragraph>
			</SimpleSection>
		</FieldHelp>
		<FieldHelp ID="tipcf000.snfp"><Header>
				<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Sequence Number of Item Code from Position</Title>
			</Header>
			<FuncDesc>This field indicates from which position in the item code the sequence number is generated. If the item code generated by SSA ERP does not uniquely identify a product variant, the product configurator automatically generates a unique code by adding a sequence number to the generated item code.</FuncDesc>
			<SimpleSection><Paragraph>If it becomes apparent during the product configuration or product generation process that the number of positions for the sequence number is insufficient to uniquely identify the item code, the product configurator automatically expands the sequence number either to the left or to the right.</Paragraph>
			</SimpleSection>
		</FieldHelp>
		<FieldHelp ID="tipcf000.sntp"><Header>
				<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Sequence Number of Item Code to Position</Title>
			</Header>
			<FuncDesc>This field indicates to which position in the item code the sequence number is generated. If the item code generated by SSA ERP does not uniquely identify a product variant, the product configurator automatically generates a unique code by adding a sequence number to the generated item code.</FuncDesc>
			<SimpleSection><Paragraph>If it becomes apparent during the product configuration or product generation process that the number of positions for the sequence number is insufficient to uniquely identify the item code, the product configurator automatically expands the sequence number either to the left or to the right.</Paragraph>
			</SimpleSection>
		</FieldHelp>
		<FieldHelp ID="tipcf000.pcfv"><Header>
				<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Product Configurator Version</Title>
			</Header>
			<FuncDesc>The product configurator version.</FuncDesc>
			<SimpleSection><ProcedureList><ListIntro>The use of the product configurator can be divided in two parts:</ListIntro>
					<ListItem>Product model definition.</ListItem>
					<ListItem>Use of the product model in an operational siuation. In the development stage, the constraints must be tested to ensure that no errors are present, so that the model can be used in the operational situation.</ListItem>
				</ProcedureList>
			</SimpleSection>
			<Note><SectionTitle>Note</SectionTitle>
				<Paragraph>you can always switch from one version to another.</Paragraph>
			</Note>
			<SimpleSection><SectionTitle>Interpreter Version</SectionTitle>
				<Paragraph>Constraints must be tested to ensure that no errors are present. As a result, during runtime, constraints are continually read in, and interpreted or compiled. The advantage of the <GUIRef href="/baanerp/tc/domains/pcfv#interpretor" role="enum">Interpreter Version</GUIRef> mode is that you can immediately test a generic product model after changes are made to certain constraints, without first having to recompile all constraints. A disadvantage is that the performance of the product configurator is reduced.</Paragraph>
			</SimpleSection>
			<SimpleSection><SectionTitle>Object Version</SectionTitle>
				<Paragraph>This version is available for the operational situation. During runtime, constraints are directly executed by the product configurator as objects, without the necessity to repeatedly read in and interpret or compile constraints. Compared to the interpreter version, the object version may result in a considerable performance improvement, especially in the case of more complex constraints. Prior to using the object version, all constraints must be compiled in the <Link href="/baanerp/ti/pcf/tipcf2201m000" role="session">Compile Constraints by Generic Item (tipcf2201m000)</Link> session. For this purpose, you need the compiler 'bic6.2' of <GUIRef href="" role="manual">Enterprise Server</GUIRef>.</Paragraph>
			</SimpleSection>
			<RelatedTopics><SectionTitle>Related topics</SectionTitle>
				<RelTopic><Link href="/baanerp/ti/onlinemanual/100004" role="manual">How to define a product model</Link>
				</RelTopic>
			</RelatedTopics>
		</FieldHelp>
		<FieldHelp ID="tipcf000.ngpv"><Header>
				<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Number Group for Product Variants</Title>
			</Header>
			<FuncDesc>The <Link href="/baanerp/tc/glossary/glossary#NumberGroup.tc" role="glossary">number group</Link> for <Link href="/baanerp/td/glossary/glossary#ProducVarian.td" role="glossary">product variants</Link>.</FuncDesc>
			<RelatedTopics><SectionTitle>Related topics</SectionTitle>
				<RelTopic><Link href="/baanerp/tc/onlinemanual/000004" role="manual">To use number groups and series</Link>
				</RelTopic>
			</RelatedTopics>
		</FieldHelp>
		<FieldHelp ID="tcmcs051.dsca"><Header>
				<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Number Group for Product Variants</Title>
			</Header>
			<FuncDesc>The name of the parameter set.</FuncDesc>
		</FieldHelp>
		<FieldHelp ID="tipcf000.inpt"><Header>
				<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Input Option Value</Title>
			</Header>
			<FuncDesc>The <GUIRef href="/baanerp/ti/pcf" role="module">Product Configuration</GUIRef> module enables you to record constraints per generic item. A number of variables predefined in the <GUIRef href="/baanerp/ti/pcf/tipcf0100m000" role="session">Product Configuration Parameters (tipcf0100m000)</GUIRef> session are used in these constraints. These variables can be filled only once. This means that once product constraints are defined, the descriptions of the variables can no longer be changed.</FuncDesc>
			<SimpleSection><Paragraph>The <GUIRef href="/baanerp/ti/pcf/tipcf0100m000#tipcf000.inpt" role="formfield">Input Option Value</GUIRef> variable enables you to indicate for each product feature whether or not the product configurator must prompt you to enter an option value.</Paragraph>
				<Paragraph>This variable has the following features:</Paragraph>
				<TABLE border="1"><TBODY><TR><TD>Constraint section</TD>
							<TD>Before Input</TD>
						</TR>
						<TR><TD>Application</TD>
							<TD>Enter option value y/n</TD>
						</TR>
						<TR><TD>Domain</TD>
							<TD>True/false</TD>
						</TR>
						<TR><TD>Initialization</TD>
							<TD>True</TD>
						</TR>
					</TBODY>
				</TABLE>
			</SimpleSection>
		</FieldHelp>
		<FieldHelp ID="tipcf000.disp"><Header>
				<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Display Option Value</Title>
			</Header>
			<FuncDesc>Indicates for each product feature whether the product configurator must display that feature during the product configuration process in case of an implicit option value.</FuncDesc>
			<SimpleSection><Paragraph>This variable has the following features:</Paragraph>
				<TABLE border="1"><TBODY><TR><TD>Constraint section</TD>
							<TD>Before Input</TD>
						</TR>
						<TR><TD>Application</TD>
							<TD>Display Option Value y/n</TD>
						</TR>
						<TR><TD>Domain</TD>
							<TD>True/false</TD>
						</TR>
						<TR><TD rowspan="2">Initialization</TD>
							<TD>True if the Display Implicit Options parameter is selected</TD>
						</TR>
						<TR><TD>False if the Display Implicit Options parameter is cleared</TD>
						</TR>
					</TBODY>
				</TABLE>
			</SimpleSection>
			<Note><SectionTitle>Note</SectionTitle>
				<Paragraph>Value is true if the Input Option Value field is true.</Paragraph>
			</Note>
		</FieldHelp>
		<FieldHelp ID="tipcf000.vali"><Header>
				<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Validating</Title>
			</Header>
			<FuncDesc>The <GUIRef href="/baanerp/ti/pcf" role="module">Product Configuration</GUIRef> module enables you to record constraints per generic item. A number of variables predefined in the <GUIRef href="/baanerp/ti/pcf/tipcf0100m000" role="session">Product Configuration Parameters (tipcf0100m000)</GUIRef> session are used in these constraints. These variables can be filled only once. This means that once product constraints are defined, the descriptions of the variables can no longer be changed.</FuncDesc>
			<SimpleSection><Paragraph>This field indicates whether or not the product configurator validates a given product configuration. As a result, you can control the product configuration process and also prevent the configuration or generation of unallowed product variants. Note that product configuration covers all generic product information, such as product features and options, generic item data, generic bills of material, generic routing, and generic price lists.</Paragraph>
				<Paragraph>This variable has the following features:</Paragraph>
				<TABLE border="1"><TBODY><TR><TD>Constraint section</TD>
							<TD>Validation</TD>
						</TR>
						<TR><TD>Application</TD>
							<TD>Validating product configuration</TD>
						</TR>
						<TR><TD>Domain</TD>
							<TD>True/false</TD>
						</TR>
						<TR><TD>Initialization</TD>
							<TD>True</TD>
						</TR>
					</TBODY>
				</TABLE>
			</SimpleSection>
		</FieldHelp>
		<FieldHelp ID="tipcf000.mess"><Header>
				<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Message</Title>
			</Header>
			<FuncDesc>The <GUIRef href="/baanerp/ti/pcf" role="module">Product Configuration</GUIRef> module enables you to record constraints per generic item. A number of variables predefined in the <GUIRef href="/baanerp/ti/pcf/tipcf0100m000" role="session">Product Configuration Parameters (tipcf0100m000)</GUIRef> session are used in these constraints. These variables can be filled only once. This means that once product constraints are defined, the descriptions of the variables can no longer be changed.</FuncDesc>
			<SimpleSection><Paragraph>The <GUIRef href="/baanerp/ti/pcf/tipcf0100m000#tipcf000.mess" role="formfield">Message</GUIRef> field enables you to generate messages during the product configuration process. These messages are displayed as warnings, notices, or explanations. Messages can be recorded in constraints in the form of texts or text blocks. When you have chosen product configuration in the customer's language, you can enter message in constraints in any language. Consequently, the product configurator generates and displays the message in the language linked to the customer's language code.</Paragraph>
				<Paragraph>This variable has the following features:</Paragraph>
				<TABLE border="1"><TBODY><TR><TD>Constraint section</TD>
							<TD>Validation</TD>
						</TR>
						<TR><TD>Application</TD>
							<TD>Generating messages</TD>
						</TR>
						<TR><TD>Domain</TD>
							<TD>Alphanumeric: a maximum of 80x25 lines of text</TD>
						</TR>
						<TR><TD>Initialization</TD>
							<TD>Standard message</TD>
						</TR>
					</TBODY>
				</TABLE>
			</SimpleSection>
			<Note><SectionTitle>Note</SectionTitle>
				<Paragraph>If a message is recorded in a foreign language, the (system) language code must be added to the variable Message.</Paragraph>
				<List><ListIntro>For example:</ListIntro>
					<ListItem>message = "this is a message"</ListItem>
					<ListItem>message.3 = "dies ist eine Meldung"</ListItem>
				</List>
			</Note>
		</FieldHelp>
		<FieldHelp ID="tipcf000.itmd"><Header>
				<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Item Data</Title>
			</Header>
			<FuncDesc>The <Link href="/baanerp/ti/onlinemanual/tipcf" role="module">Product Configuration (PCF)</Link> module enables you to record constraints per generic item. A number of variables predefined in the <GUIRef href="/baanerp/ti/pcf/tipcf0100m000" role="session">Product Configuration Parameters (tipcf0100m000)</GUIRef> session are used in these constraints. These variables can be filled only once. This means that once product constraints are defined, the descriptions of the variables can no longer be changed.</FuncDesc>
			<SimpleSection><Paragraph>The <GUIRef href="/baanerp/ti/pcf/tipcf0100m000#tipcf000.itmd" role="formfield">Item Data</GUIRef> field enables you to let the product configurator determine the data of a product variant item, such as item code, item description, material, size, norm, and item text. The variable <GUIRef href="/baanerp/ti/pcf/tipcf0100m000#tipcf000.itmd" role="formfield">Item Data</GUIRef> can be used in the "parameter substitution" part of a generic item data constraint.</Paragraph>
				<Paragraph>This variable has the following features:</Paragraph>
				<TABLE border="1"><TBODY><TR><TD>Constraint Section</TD>
							<TD>Parameter substitution</TD>
						</TR>
						<TR><TD>Application</TD>
							<TD>Determine product variant item data</TD>
						</TR>
						<TR><TD>Domain</TD>
							<TD>Alphabetic characters</TD>
						</TR>
						<TR><TD>Initialization</TD>
							<TD>Current value of item data</TD>
						</TR>
					</TBODY>
				</TABLE>
			</SimpleSection>
			<Note><SectionTitle>Note</SectionTitle>
				<Paragraph>Text blocks for item text generation have first priority.</Paragraph>
			</Note>
		</FieldHelp>
		<FieldHelp ID="tipcf000.leng"><Header>
				<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Length</Title>
			</Header>
			<FuncDesc>The <GUIRef href="/baanerp/ti/pcf" role="module">Product Configuration</GUIRef> module enables you to record constraints per generic item. A number of variables predefined in the <GUIRef href="/baanerp/ti/pcf/tipcf0100m000" role="session">Product Configuration Parameters (tipcf0100m000)</GUIRef> session are used in these constraints. These variables can be filled only once. This means that once product constraints are defined, the descriptions of the variables can no longer be changed.</FuncDesc>
			<SimpleSection><Paragraph>With the <GUIRef href="/baanerp/ti/pcf/tipcf0100m000#tipcf000.leng" role="formfield">Length</GUIRef> field you can let the product configurator calculate for example the length of a BOM component, based on a formula.</Paragraph>
				<Paragraph>This variable has the following features:</Paragraph>
				<TABLE border="1"><TBODY><TR><TD>Constraint section</TD>
							<TD>Parameter Substitution</TD>
						</TR>
						<TR><TD>Application</TD>
							<TD>Calculating length of BOM component</TD>
						</TR>
						<TR><TD>Domain</TD>
							<TD>Fractions</TD>
						</TR>
						<TR><TD>Initialization</TD>
							<TD>Current value of BOM component's length</TD>
						</TR>
					</TBODY>
				</TABLE>
			</SimpleSection>
			<Note><SectionTitle>Note</SectionTitle>
				<Paragraph>Unit of BOM component must have physical quantity Length or Area.</Paragraph>
			</Note>
		</FieldHelp>
		<FieldHelp ID="tipcf000.widt"><Header>
				<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Width</Title>
			</Header>
			<FuncDesc>The <GUIRef href="/baanerp/ti/pcf" role="module">Product Configuration</GUIRef> module enables you to record constraints per generic item. A number of variables predefined in the <GUIRef href="/baanerp/ti/pcf/tipcf0100m000" role="session">Product Configuration Parameters (tipcf0100m000)</GUIRef> session are used in these constraints. These variables can be filled only once. This means that once product constraints are defined, the descriptions of the variables can no longer be changed.</FuncDesc>
			<SimpleSection><Paragraph>With the <GUIRef href="/baanerp/ti/pcf/tipcf0100m000#tipcf000.widt" role="formfield">Width</GUIRef> field you can for example let SSA ERP calculate the width of a BOM component.</Paragraph>
				<Paragraph>This variable has the following features:</Paragraph>
				<TABLE border="1"><TBODY><TR><TD>Constraint section</TD>
							<TD>Parameter Substitution</TD>
						</TR>
						<TR><TD>Application</TD>
							<TD>Calculating width of BOM component</TD>
						</TR>
						<TR><TD>Domain</TD>
							<TD>Fractions</TD>
						</TR>
						<TR><TD>Initialization</TD>
							<TD>Current value of BOM component's width</TD>
						</TR>
					</TBODY>
				</TABLE>
			</SimpleSection>
			<Note><SectionTitle>Note</SectionTitle>
				<Paragraph>Physical quantity of BOM component's unit must be Area.</Paragraph>
			</Note>
		</FieldHelp>
		<FieldHelp ID="tipcf000.noun"><Header>
				<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Number of Units</Title>
			</Header>
			<FuncDesc>The <GUIRef href="/baanerp/ti/pcf" role="module">Product Configuration</GUIRef> module enables you to record constraints per generic item. A number of variables predefined in the <GUIRef href="/baanerp/ti/pcf/tipcf0100m000" role="session">Product Configuration Parameters (tipcf0100m000)</GUIRef> session are used in these constraints. These variables can be filled only once. This means that once product constraints are defined, the descriptions of the variables can no longer be changed.</FuncDesc>
			<SimpleSection><Paragraph>With the <GUIRef href="/baanerp/ti/pcf/tipcf0100m000#tipcf000.noun" role="formfield">Number of Units</GUIRef> field you can let SSA ERP calculate for example a BOM component's number of units, based on a formula.</Paragraph>
				<Paragraph>This variable has the following features:</Paragraph>
				<TABLE border="1"><TBODY><TR><TD>Constraint section</TD>
							<TD>Parameter Substitution</TD>
						</TR>
						<TR><TD>Application</TD>
							<TD>Calculation of a BOM component's number of units</TD>
						</TR>
						<TR><TD>Domain</TD>
							<TD>Integers</TD>
						</TR>
						<TR><TD>Initialization</TD>
							<TD>Current value of a BOM component's number of units</TD>
						</TR>
					</TBODY>
				</TABLE>
			</SimpleSection>
			<Note><SectionTitle>Note</SectionTitle>
				<Paragraph>Unit of BOM component must have physical quantity Length or Area.</Paragraph>
			</Note>
		</FieldHelp>
		<FieldHelp ID="tipcf000.qana"><Header>
				<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Net Quantity</Title>
			</Header>
			<FuncDesc>The <GUIRef href="/baanerp/ti/pcf" role="module">Product Configuration</GUIRef> module enables you to record constraints per generic item. A number of variables predefined in the <GUIRef href="/baanerp/ti/pcf/tipcf0100m000" role="session">Product Configuration Parameters (tipcf0100m000)</GUIRef> session are used in these constraints. These variables can be filled only once. This means that once product constraints are defined, the descriptions of the variables can no longer be changed.</FuncDesc>
			<SimpleSection><Paragraph>With the <GUIRef href="/baanerp/ti/pcf/tipcf0100m000#tipcf000.qana" role="formfield">Net Quantity</GUIRef> field you can let SSA ERP calculate the net quantity of a BOM component, based on, for example, a formula.</Paragraph>
				<Paragraph>This variable has the following features:</Paragraph>
				<TABLE border="1"><TBODY><TR><TD>Constraint section</TD>
							<TD>Parameter Substitution</TD>
						</TR>
						<TR><TD>Application</TD>
							<TD>Calculating net quantity of BOM component</TD>
						</TR>
						<TR><TD>Domain</TD>
							<TD>Fractions</TD>
						</TR>
						<TR><TD>Initialization</TD>
							<TD>Current value of net quantity of BOM component</TD>
						</TR>
					</TBODY>
				</TABLE>
			</SimpleSection>
			<Note><SectionTitle>Note</SectionTitle>
				<Paragraph>If the values of length, width (if any) and number of units are known, the net quantity is automatically derived from these values assuming the net quantity is not filled.</Paragraph>
			</Note>
		</FieldHelp>
		<FieldHelp ID="tipcf000.sutm"><Header>
				<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Setup Time</Title>
			</Header>
			<FuncDesc>The <Link href="/baanerp/ti/onlinemanual/tipcf" role="module">Product Configuration (PCF)</Link> module enables you to record constraints per generic item. A number of variables predefined in the <GUIRef href="/baanerp/ti/pcf/tipcf0100m000" role="session">Product Configuration Parameters (tipcf0100m000)</GUIRef> session are used in these constraints. These variables can be entered only once. This means that once you defined product constraints, you can no longer change the descriptions of the variables.</FuncDesc>
			<SimpleSection><Paragraph>With the <GUIRef href="/baanerp/ti/pcf/tipcf0100m000#tipcf000.sutm" role="formfield">Setup Time</GUIRef> field you can let SSA ERP calculate, for instance, the cycle time for an operation.</Paragraph>
				<Paragraph>This variable has the following features:</Paragraph>
				<TABLE border="1"><TBODY><TR><TD>Constraint section</TD>
							<TD>Parameter Substitution</TD>
						</TR>
						<TR><TD>Application</TD>
							<TD>Calculating setup time for operation</TD>
						</TR>
						<TR><TD>Domain</TD>
							<TD>Fractions</TD>
						</TR>
						<TR><TD>Initialization</TD>
							<TD>Current value of operation setup time</TD>
						</TR>
					</TBODY>
				</TABLE>
			</SimpleSection>
		</FieldHelp>
		<FieldHelp ID="tipcf000.prte"><Header>
				<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Production Rate</Title>
			</Header>
			<FuncDesc>The <GUIRef href="/baanerp/ti/pcf" role="module">Product Configuration</GUIRef> module enables you to record constraints per generic item. A number of variables predefined in the <GUIRef href="/baanerp/ti/pcf/tipcf0100m000" role="session">Product Configuration Parameters (tipcf0100m000)</GUIRef> session are used in these constraints. These variables can be filled only once. This means that once product constraints are defined, the descriptions of the variables can no longer be changed.</FuncDesc>
			<SimpleSection><Paragraph>This field expresses the number of products manufactured per unit of time. Depending on the parameter setup, the time unit is hour or minute. The production rate provides an alternative to recording operation times. The operation with the lowest production rate is considered the "bottleneck" for RPT items.</Paragraph>
			</SimpleSection>
		</FieldHelp>
		<FieldHelp ID="tipcf000.rutm"><Header>
				<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Cycle Time</Title>
			</Header>
			<FuncDesc>The <Link href="/baanerp/ti/onlinemanual/tipcf" role="module">Product Configuration (PCF)</Link> module enables you to record constraints per generic item. A number of variables predefined in the <GUIRef href="/baanerp/ti/pcf/tipcf0100m000" role="session">Product Configuration Parameters (tipcf0100m000)</GUIRef> session are used in these constraints. These variables can be filled only once. This means that once you have defined product constraints, you can no longer change the descriptions of the variables.</FuncDesc>
			<SimpleSection><Paragraph>With the variable <GUIRef href="/baanerp/ti/pcf/tipcf0100m000#tipcf000.rutm" role="formfield">Cycle Time</GUIRef> field you can let the product configurator calculate, for example, the cycle time for an operation, according to a formula.</Paragraph>
				<Paragraph>This variable has the following features:</Paragraph>
				<TABLE border="1"><TBODY><TR><TD>Constraint section</TD>
							<TD>Parameter Substitution</TD>
						</TR>
						<TR><TD>Application</TD>
							<TD>Calculating setup time for operation</TD>
						</TR>
						<TR><TD>Domain</TD>
							<TD>Fractions</TD>
						</TR>
						<TR><TD>Initialization</TD>
							<TD>Current value of operation setup time</TD>
						</TR>
					</TBODY>
				</TABLE>
			</SimpleSection>
		</FieldHelp>
		<FieldHelp ID="tipcf000.pric"><Header>
				<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Price</Title>
			</Header>
			<FuncDesc>The <GUIRef href="/baanerp/ti/pcf" role="module">Product Configuration</GUIRef> module enables you to record constraints per generic item. A number of variables predefined in the <GUIRef href="/baanerp/ti/pcf/tipcf0100m000" role="session">Product Configuration Parameters (tipcf0100m000)</GUIRef> session are used in these constraints. These variables can be filled only once. This means that once product constraints are defined, the descriptions of the variables can no longer be changed.</FuncDesc>
			<SimpleSection><Paragraph>With this field you can let the product configurator calculate the purchase or sales price for a product variant, based on, for example, a formula. The final purchase or sales price for a product variant may be composed of multiple price and/or surcharge components. Some data can be recorded in the generic purchase or sales price list for each generic item.</Paragraph>
				<Paragraph>This variable has the following features:</Paragraph>
				<TABLE border="1"><TBODY><TR><TD>Constraint section</TD>
							<TD>Parameter Substitution</TD>
						</TR>
						<TR><TD>Application</TD>
							<TD>Calculating purchase or sales price of product variant</TD>
						</TR>
						<TR><TD>Domain</TD>
							<TD>Fractions</TD>
						</TR>
						<TR><TD>Initialization</TD>
							<TD>Current value of purchase price or 0.0 for the sales price</TD>
						</TR>
					</TBODY>
				</TABLE>
			</SimpleSection>
		</FieldHelp>
		<FieldHelp ID="tipcf000.dsca"><Header>
				<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Description</Title>
			</Header>
			<FuncDesc>The description of the parameter set. For example, you can indicate why you changed the parameters.</FuncDesc>
		</FieldHelp>
	</Fields>
</Session>
