<?xml version="1.0" encoding="utf-8"?>
<ManualTopic ID="/baanerp/ti/onlinemanual/100004" xml:lang="en">
	<Header>
		<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">How to define a product model</Title>
	</Header>
	<GeneralSection><Paragraph>Carry out the following steps to define a product model:</Paragraph>
		<ProcedureSection><Steps><Step><StepTitle>Product Configuration Parameters</StepTitle>
					<Paragraph>In the <Link href="/baanerp/ti/pcf/tipcf0100m000" role="session">Product Configuration Parameters (tipcf0100m000)</Link> session, determine the version of the product configurator. If the product model is in the creation stage, you must use the interpreter version. The advantage of this version is that the generic product model can be tested immediately if new <Link href="/baanerp/ti/glossary/glossary#100003" role="glossary">constraints</Link> are created. If changes are made to these constraints, the constraints need not be <Link href="/baanerp/ti/glossary/glossary#000339" role="glossary">recompiled</Link> first. Refer to the <Link href="/baanerp/ti/pcf/tipcf0100m000#tipcf000.pcfv" role="fieldhelp">Product Configurator Version</Link> field in the <GUIRef href="/baanerp/ti/pcf/tipcf0100m000" role="session">Product Configuration Parameters (tipcf0100m000)</GUIRef> session.</Paragraph>
				</Step>
				<Step><StepTitle>Items - General</StepTitle>
					<Paragraph>In the <GUIRef href="/baanerp/tc/ibd/tcibd0501m000" role="session">Items - General (tcibd0501m000)</GUIRef> session, enter the <Link href="/baanerp/ti/glossary/glossary#GeneriItem.ti" role="glossary">generic items</Link> that you need for the <Link href="/baanerp/ti/glossary/glossary#ProducModel.ti" role="glossary">product model</Link>.</Paragraph>
					<Paragraph>You must decide whether you want to use a PCS budget and/or a PCS project when producing product variants, or you want to use PCF without PCS. A PCS budget is used to calculate the cost price. A PCS project is used to plan, produce, and control the manufacturing process. Consequently, the structure of the product variant is generated by budget or project. The advantage of using PCS is that it provides an item with a detailed cost roll-up, and the possibility of pegging. However, in high volume environments, a detailed cost roll-up is often not necessary. Furthermore, using PCS requires extra time to calculate the project costs and to delete the project structure afterwards.</Paragraph>
					<List><ListItem>If you want to use <GUIRef href="/baanerp/ti/pcs" role="module" Update="No">Project Control (PCS)</GUIRef> for <GUIRef href="/baanerp/ti/pcf" role="module" Update="No">Product Configuration (PCF)</GUIRef>, the <GUIRef href="/baanerp/tc/ibd/tcibd2100s000#tcibd200.opol" role="formfield">Order Policy</GUIRef> field in the <GUIRef href="/baanerp/tc/ibd/tcibd2100s000" role="session">Item - Ordering (tcibd2100s000)</GUIRef> session must be <GUIRef href="/baanerp/tc/domains/opol#on.order" role="enum">To Order</GUIRef>.</ListItem>
					</List>
					<List><ListItem>If you want to use <GUIRef href="/baanerp/ti/pcf" role="module" Update="No">Product Configuration (PCF)</GUIRef> without <GUIRef href="/baanerp/ti/pcs" role="module" Update="No">Project Control (PCS)</GUIRef>, the <GUIRef href="/baanerp/tc/ibd/tcibd2100s000#tcibd200.opol" role="formfield">Order Policy</GUIRef> field in the <GUIRef href="/baanerp/tc/ibd/tcibd2100s000" role="session">Item - Ordering (tcibd2100s000)</GUIRef> session must be <GUIRef href="/baanerp/tc/domains/opol#anonymous" role="enum">Anonymous</GUIRef>.</ListItem>
					</List>
					<Paragraph>If you configure items without PCS projects, standard items are generated instead of customized items. Pegging functionality is secured by the unique item codes of the configured items that can be related back to the sales order.</Paragraph>
				</Step>
				<Step><StepTitle>Product Features</StepTitle>
					<Paragraph>In the <Link href="/baanerp/ti/pcf/tipcf0150m000" role="session">Product Feature (tipcf0150m000)</Link> session, enter the required <Link href="/baanerp/ti/glossary/glossary#100000" role="glossary">product features</Link>. You must define all required product features with possible options in this session.</Paragraph>
				</Step>
				<Step><StepTitle>Product Features by Generic Item and Constraints by Generic Item</StepTitle>
					<Paragraph>In the <Link href="/baanerp/ti/pcf/tipcf1101m000" role="session">Product Features by Generic Item (tipcf1101m000)</Link> session, the product features are linked to a generic item. Product features are controlled by <Link href="/baanerp/ti/glossary/glossary#100003" role="glossary">constraints</Link>, which you can define in the <Link href="/baanerp/ti/pcf/tipcf2110m000" role="session">Generic Item - Constraints (tipcf2110m000)</Link> session.</Paragraph>
				</Step>
				<Step><StepTitle>Generic BOMs and Generic Routing</StepTitle>
					<Paragraph>In the <Link href="/baanerp/ti/pcf/tipcf3110m000" role="session">Generic BOMs (tipcf3110m000)</Link> session and the <Link href="/baanerp/ti/pcf/tipcf3120m000" role="session">Generic Routing (tipcf3120m000)</Link> session, you can enter respectively the <Link href="/baanerp/ti/glossary/glossary#000074" role="glossary">product structure</Link> and the routing. The constraints in step 4 are used to ensure that the product structure and routing are in accordance with the selected options.</Paragraph>
				</Step>
				<Step><StepTitle>Price-List Matrix Codes, Price-List Matrices and Generic Price Lists</StepTitle>
					<Paragraph>The <Link href="/baanerp/ti/pcf/tipcf4110s000" role="session">Price List Matrix Codes (tipcf4110s000)</Link> session, the <Link href="/baanerp/ti/pcf/tipcf4120m000" role="session">Price List Matrices (tipcf4120m000)</Link> session, and the <Link href="/baanerp/ti/pcf/tipcf4101m000" role="session">Generic Price Lists (tipcf4101m000)</Link> session are not mandatory. If a sales price or a purchase price for a generic purchase item must be generated, the price list can be used to define a price list. You can use matrices for different features that have mutual relationships associated to the price. By defining the price list code and the price list matrices, the features and values in the matrices can be entered.</Paragraph>
				</Step>
				<Step><StepTitle>Settings for Generic Item-Data Generation</StepTitle>
					<Paragraph>The <Link href="/baanerp/ti/pcf/tipcf3101m000" role="session">Generic Item - Settings for Data Generation (tipcf3101m000)</Link> session is not mandatory. The item data that arises when configuring <Link href="/baanerp/td/glossary/glossary#ProducVarian.td" role="glossary">product variants</Link> can be defined generically according to your own wishes and insights. You can use this session to create generic settings on how to generate the item code, item description, material, size, text, or standard for a generic item.</Paragraph>
				</Step>
				<Step><StepTitle>Product Configuration Parameters</StepTitle>
					<Paragraph>After you defined the product model, you must change the product configurator version from <GUIRef href="/baanerp/tc/domains/pcfv#interpretor" role="enum">Interpreter Version</GUIRef> to <GUIRef href="/baanerp/tc/domains/pcfv#object" role="enum">Object Version</GUIRef> in the <GUIRef href="/baanerp/ti/pcf/tipcf0100m000" role="session">Product Configuration Parameters (tipcf0100m000)</GUIRef> session.</Paragraph>
				</Step>
				<Step><StepTitle>Compile Constraints by Generic Item</StepTitle>
					<Paragraph>The last step is to <Link href="/baanerp/ti/glossary/glossary#000339" role="glossary">compile</Link> the constraints to generate objects for each item in the <Link href="/baanerp/ti/pcf/tipcf2201m000" role="session">Compile Constraints by Generic Item (tipcf2201m000)</Link> session.</Paragraph>
				</Step>
			</Steps>
		</ProcedureSection>
	</GeneralSection>
	<RelatedTopics><SectionTitle>Related topics</SectionTitle>
		<RelTopic><Link href="/baanerp/ti/onlinemanual/100001" role="manual">How to configure product variants and generate product structures</Link>
		</RelTopic>
	</RelatedTopics>
</ManualTopic>
