<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/ti/pcf/tipcf0100m000" xml:lang="en">
   <Header>
      <Title>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="manual">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>
      <FieldGroup>
         <Title>General</Title>
         <FieldHelp ID="tipcf000.indt">
            <Header>
               <Title>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.dsca">
            <Header>
               <Title>Description</Title>
            </Header>
            <FuncDesc>The description of the parameter set. For example, you can
			 indicate why you changed the parameters.</FuncDesc>
         </FieldHelp>
         <FieldHelp ID="tipcf000.mlcs">
            <Header>
               <Title>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 LN to include or
				exclude certain sets of questions during the product configuration
				process.</Paragraph>
            </SimpleSection>
         </FieldHelp>
         <FieldHelp ID="tipcf000.clan">
            <Header>
               <Title>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 the employee 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>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>Generate Sales Quotation Texts</Title>
            </Header>
            <FuncDesc>If this check box is selected, LN 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>Identifying Item Code</Title>
            </Header>
            <FuncDesc>This parameter affects the way in which LN 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 LN 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 <Link href="/baanerp/ti/pcf/tipcf3101m000" role="session">Generic Item - Settings for Data Generation (tipcf3101m000)</Link> 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, LN generates a new item code for each product variant. To generate the new item
				codes, LN adds a
				sequence number to the generic item code. You can specify the exact position of
				this sequence number in the <GUIRef href="/baanerp/ti/pcf/tipcf0100m000#tipcf000.snfp" role="manual">Sequence Number of Item Code from Position</GUIRef> field and the <GUIRef href="/baanerp/ti/pcf/tipcf0100m000#tipcf000.sntp" role="manual">Sequence Number of Item Code to Position</GUIRef> field of the current session.</Paragraph>
               <Paragraph>If you generate a project structure for a generic item
				with order policy <GUIRef href="/baanerp/tc/domains/opol#anonymous" role="option">Anonymous</GUIRef>, you must clear this check box. In that case,
				the new configured item has no PCS <Link href="/baanerp/td/glossary/glossary#000230" role="glossary">project code</Link> as a distinctive feature, so the item code must be
				distinctive.</Paragraph>
            </SimpleSection>
         </FieldHelp>
         <FieldHelp ID="tipcf000.ustb">
            <Header>
               <Title>Use Standard to Order Item BOM</Title>
            </Header>
            <FuncDesc>In <GUIRef href="/baanerp/ti/pcf" role="module">Product Configuration</GUIRef> (PCF), you sell variants of a certain product. You put
			 together a product according to the customer's wishes by selecting components
			 or subassemblies from a list of predefined features and options. More
			 technically, if you configure a generic item in PCF, the generic BOM is
			 converted to a customized product structure. If customers often select a
			 specific configuration, either on end item or subassembly level, you can create
			 standard items for these fast runners in the <GUIRef href="/baanerp/tc/ibd" role="module">Item Base Data</GUIRef> (IBD)
			 module. The standard item's order policy can be <GUIRef href="/baanerp/tc/domains/opol#on.order" role="option">To Order</GUIRef> or <GUIRef href="/baanerp/tc/domains/opol#anonymous" role="option">Anonymous</GUIRef>.</FuncDesc>
            <SimpleSection>
               <Paragraph>The <GUIRef href="/baanerp/ti/pcf/tipcf0100m000#tipcf000.ustb" role="manual">Use Standard to Order Item BOM</GUIRef> parameter determines whether the components
				of standard-to-order items are used in the customized product structure. You
				can use the <GUIRef href="/baanerp/td/sls/tdsls4244m000" role="session">Generate (Project) Structure for Sales Orders (tdsls4244m000)</GUIRef> session to create a customized product
				structure.</Paragraph>
               <Paragraph>If this check box is selected, and you choose during
				product configuration a subassembly for which a standard-to-order item is
				defined in IBD, this standard-to-order item is used in the customized BOM. Also
				the BOM components of the standard item are selected in the customized BOM
				during generation of the PCS project:</Paragraph>
               <Figure space-and-orientation="indented-estimated">
                  <HTML:IMG xmlns:HTML="http://www.w3.org/TR/REC-html40" height="390" width="666"
                            SRC="../images/tr_graph_tipcf0100m000_sto_bom_yes.gif"
                            alt="[...]"/>
               </Figure>
               <Paragraph>If this check box is cleared, and you select during
				product configuration a subassembly for which a standard-to-order item is
				present in inventory, the standard-to-order item is used in the BOM, but its
				components are derived from the generic (derived-from) item:</Paragraph>
               <Figure space-and-orientation="indented-estimated">
                  <HTML:IMG xmlns:HTML="http://www.w3.org/TR/REC-html40" height="408" width="666"
                            SRC="../images/tr_graph_tipcf0100m000_sto_bom_no.gif"
                            alt="[...]"/>
               </Figure>
            </SimpleSection>
            <Note>
               <SectionTitle>Note</SectionTitle>
               <Paragraph>The cases described above concern standard items with
				order policy <GUIRef href="/baanerp/tc/domains/opol#on.order" role="option">To Order</GUIRef>. If you select during product configuration a standard item with
				order policy <GUIRef href="/baanerp/tc/domains/opol#anonymous" role="option">Anonymous</GUIRef>, this standard item is never customized, so the
				problem of copying components does not occur.</Paragraph>
            </Note>
            <SimpleSection>
               <SectionTitle>To use a standard-to-order item multiple times on a PCS
				project</SectionTitle>
               <Paragraph>The use of this <GUIRef href="/baanerp/ti/pcf/tipcf0100m000#tipcf000.ustb" role="manual">Use Standard to Order Item BOM</GUIRef> parameter is twofold. The parameter not
				only concerns the selection of components for standard-to-order items during
				project generation as described above, it also determines whether a customized
				standard-to-order subassembly can be used multiple times in a PCS project for
				different parent items.</Paragraph>
               <Paragraph>If this check box is cleared, two parent items in a
				specific PCS project cannot have the similar customized standard-to-order
				subassembly as a component. After a specific subassembly is used in the first
				parent item, you cannot use a similar subassembly in a second parent item
				anymore. The reason is that if a subassembly is used in a specific parent item,
				it receives a product variant number that conflicts with the product variant
				number of another parent item that requires the subassembly.</Paragraph>
               <Paragraph>If this check box is selected, a similar customized
				standard-to-order subassembly can be used in several parent items for the same
				project. The first parent item in which the subassembly is used assigns its
				product variant number to the subassembly. Despite of this product variant
				number, the subassembly can be used in other customized product structures,
				with other product variant numbers.</Paragraph>
            </SimpleSection>
            <Note>
               <SectionTitle>Note</SectionTitle>
               <Paragraph>If this check box is selected, and you change a
				customized standard-to-order subassembly in one of the parent items, the
				subassembly is also changed in the other parent items in which the subassembly
				was used.</Paragraph>
            </Note>
         </FieldHelp>
         <FieldHelp ID="tipcf000.stic">
            <Header>
               <Title>Use Standard Item for Configuration</Title>
            </Header>
            <FuncDesc>If this check box is selected, you can copy the customized item product
			 structure to the selected standard item configuration in the <GUIRef href="/baanerp/ti/pcs/tipcs2232m000" role="session">Copy Customized Product Structure to Standard Structure (tipcs2232m000)</GUIRef> session.</FuncDesc>
            <SimpleSection>
               <Paragraph>If this check box is cleared, the customized item will not be copied to a
				standard item configuration.</Paragraph>
            </SimpleSection>
         </FieldHelp>
         <FieldHelp ID="tipcf000.rupv">
            <Header>
               <Title>Allow re-use of Configurations</Title>
            </Header>
            <FuncDesc>If this check box is selected, and you enter the same generic item with the
			 same options on multiple lines on a sales order, LN will use the same
			 item code on both lines, if that is possible.</FuncDesc>
            <SimpleSection>
               <Paragraph>If this check box is cleared, and you enter the same generic item with the
				same options on multiple lines on a sales order, LN uses a different
				item code for each sales order line. It is not permitted to use the same <Link href="/baanerp/ti/glossary/glossary#CustomItem_ti" role="glossary">customized item</Link> with different variant codes on multiple
				order lines.</Paragraph>
            </SimpleSection>
            <Note>
               <SectionTitle>Note</SectionTitle>
               <Paragraph>It is not always possible to use an item code on more than
				one sales order line. For more information, refer to <Link href="/baanerp/ti/onlinemanual/000524" role="manual">Multiple sales order lines with identical product configurations</Link>
               </Paragraph>
            </Note>
            <RelatedTopics>
               <SectionTitle>Related topics</SectionTitle>
               <RelTopic>
                  <Link href="/baanerp/ti/onlinemanual/100009" role="manual">How to use a product model in a sales order</Link>
               </RelTopic>
            </RelatedTopics>
         </FieldHelp>
         <FieldHelp ID="tipcf000.snfp">
            <Header>
               <Title>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 LN 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>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 LN 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>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 situation. 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="option">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 <Emphasis>Enterprise Server</Emphasis>.</Paragraph>
            </SimpleSection>
            <SimpleSection>
               <SectionTitle>Performance aspects</SectionTitle>
               <Paragraph>The setting of this field could affect system performance and database growth. For more information, refer to <Link href="/baanerp/performance/ti/P000012_conf_version" role="manual">Product configurator version</Link>.</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" OtherIDs="tcmcs051.dsca">
            <Header>
               <Title>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>
      </FieldGroup>
      <FieldGroup>
         <Title>Constraint Expression</Title>
         <FieldHelp ID="tipcf000.inpt">
            <Header>
               <Title>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 <Emphasis>Input Option Value</Emphasis> 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" borderstyle="default" space-and-orientation="indented-estimated">
                  <TBODY noTR="4">
                     <TR no="1" isLast="false">
                        <TD rowspan="1" colspan="1">Constraint section</TD>
                        <TD rowspan="1" colspan="1">Before Input</TD>
                     </TR>
                     <TR no="2" isLast="false">
                        <TD rowspan="1" colspan="1">Application</TD>
                        <TD rowspan="1" colspan="1">Enter option value y/n</TD>
                     </TR>
                     <TR no="3" isLast="false">
                        <TD rowspan="1" colspan="1">Domain</TD>
                        <TD rowspan="1" colspan="1">True/false</TD>
                     </TR>
                     <TR no="4" isLast="true">
                        <TD rowspan="1" colspan="1">Initialization</TD>
                        <TD rowspan="1" colspan="1">True</TD>
                     </TR>
                  </TBODY>
               </TABLE>
            </SimpleSection>
         </FieldHelp>
         <FieldHelp ID="tipcf000.disp">
            <Header>
               <Title>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" borderstyle="default" space-and-orientation="indented-estimated">
                  <TBODY noTR="5">
                     <TR no="1" isLast="false">
                        <TD rowspan="1" colspan="1">Constraint section</TD>
                        <TD rowspan="1" colspan="1">Before Input</TD>
                     </TR>
                     <TR no="2" isLast="false">
                        <TD rowspan="1" colspan="1">Application</TD>
                        <TD rowspan="1" colspan="1">Display Option Value y/n</TD>
                     </TR>
                     <TR no="3" isLast="false">
                        <TD rowspan="1" colspan="1">Domain</TD>
                        <TD rowspan="1" colspan="1">True/false</TD>
                     </TR>
                     <TR no="4" isLast="false">
                        <TD rowspan="2" colspan="1">Initialization</TD>
                        <TD rowspan="1" colspan="1">True if the Display Implicit Options parameter is selected</TD>
                     </TR>
                     <TR no="5" isLast="true">
                        <TD rowspan="1" colspan="1">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>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" borderstyle="default" space-and-orientation="indented-estimated">
                  <TBODY noTR="4">
                     <TR no="1" isLast="false">
                        <TD rowspan="1" colspan="1">Constraint section</TD>
                        <TD rowspan="1" colspan="1">Validation</TD>
                     </TR>
                     <TR no="2" isLast="false">
                        <TD rowspan="1" colspan="1">Application</TD>
                        <TD rowspan="1" colspan="1">Validating product configuration</TD>
                     </TR>
                     <TR no="3" isLast="false">
                        <TD rowspan="1" colspan="1">Domain</TD>
                        <TD rowspan="1" colspan="1">True/false</TD>
                     </TR>
                     <TR no="4" isLast="true">
                        <TD rowspan="1" colspan="1">Initialization</TD>
                        <TD rowspan="1" colspan="1">True</TD>
                     </TR>
                  </TBODY>
               </TABLE>
            </SimpleSection>
         </FieldHelp>
         <FieldHelp ID="tipcf000.mess">
            <Header>
               <Title>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 <Emphasis>Message</Emphasis> 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" borderstyle="default" space-and-orientation="indented-estimated">
                  <TBODY noTR="4">
                     <TR no="1" isLast="false">
                        <TD rowspan="1" colspan="1">Constraint section</TD>
                        <TD rowspan="1" colspan="1">Validation</TD>
                     </TR>
                     <TR no="2" isLast="false">
                        <TD rowspan="1" colspan="1">Application</TD>
                        <TD rowspan="1" colspan="1">Generating messages</TD>
                     </TR>
                     <TR no="3" isLast="false">
                        <TD rowspan="1" colspan="1">Domain</TD>
                        <TD rowspan="1" colspan="1">Alphanumeric: a maximum of 80x25 lines of text</TD>
                     </TR>
                     <TR no="4" isLast="true">
                        <TD rowspan="1" colspan="1">Initialization</TD>
                        <TD rowspan="1" colspan="1">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>Item Data</Title>
            </Header>
            <FuncDesc>The <Link href="/baanerp/ti/onlinemanual/tipcf" role="manual">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 data 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 data 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" borderstyle="default" space-and-orientation="indented-estimated">
                  <TBODY noTR="4">
                     <TR no="1" isLast="false">
                        <TD rowspan="1" colspan="1">Constraint Section</TD>
                        <TD rowspan="1" colspan="1">Parameter substitution</TD>
                     </TR>
                     <TR no="2" isLast="false">
                        <TD rowspan="1" colspan="1">Application</TD>
                        <TD rowspan="1" colspan="1">Determine product variant item data</TD>
                     </TR>
                     <TR no="3" isLast="false">
                        <TD rowspan="1" colspan="1">Domain</TD>
                        <TD rowspan="1" colspan="1">Alphabetic characters</TD>
                     </TR>
                     <TR no="4" isLast="true">
                        <TD rowspan="1" colspan="1">Initialization</TD>
                        <TD rowspan="1" colspan="1">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="tipcf010.rutm">
            <Header>
               <Title>Cycle Time</Title>
            </Header>
            <FuncDesc>The <Link href="/baanerp/ti/onlinemanual/tipcf" role="manual">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
				cycle time 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" borderstyle="default" space-and-orientation="indented-estimated">
                  <TBODY noTR="4">
                     <TR no="1" isLast="false">
                        <TD rowspan="1" colspan="1">Constraint section</TD>
                        <TD rowspan="1" colspan="1">Parameter Substitution</TD>
                     </TR>
                     <TR no="2" isLast="false">
                        <TD rowspan="1" colspan="1">Application</TD>
                        <TD rowspan="1" colspan="1">Calculating setup time for operation</TD>
                     </TR>
                     <TR no="3" isLast="false">
                        <TD rowspan="1" colspan="1">Domain</TD>
                        <TD rowspan="1" colspan="1">Fractions</TD>
                     </TR>
                     <TR no="4" isLast="true">
                        <TD rowspan="1" colspan="1">Initialization</TD>
                        <TD rowspan="1" colspan="1">Current value of operation setup time</TD>
                     </TR>
                  </TBODY>
               </TABLE>
            </SimpleSection>
         </FieldHelp>
         <FieldHelp ID="tipcf000.pric">
            <Header>
               <Title>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" borderstyle="default" space-and-orientation="indented-estimated">
                  <TBODY noTR="4">
                     <TR no="1" isLast="false">
                        <TD rowspan="1" colspan="1">Constraint section</TD>
                        <TD rowspan="1" colspan="1">Parameter Substitution</TD>
                     </TR>
                     <TR no="2" isLast="false">
                        <TD rowspan="1" colspan="1">Application</TD>
                        <TD rowspan="1" colspan="1">Calculating purchase or sales price of product variant</TD>
                     </TR>
                     <TR no="3" isLast="false">
                        <TD rowspan="1" colspan="1">Domain</TD>
                        <TD rowspan="1" colspan="1">Fractions</TD>
                     </TR>
                     <TR no="4" isLast="true">
                        <TD rowspan="1" colspan="1">Initialization</TD>
                        <TD rowspan="1" colspan="1">Current value of purchase price or 0.0 for the sales
						price</TD>
                     </TR>
                  </TBODY>
               </TABLE>
            </SimpleSection>
         </FieldHelp>
      </FieldGroup>
   </Fields>
</Session>