<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/ti/rou/tirou1114m000" xml:lang="en">
	<Header>
		<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Effectivity Unit - Process Variables (tirou1114m000)</Title>
	</Header>
	<HelpTopic><AimSection><Paragraph>Use this session to make the target value of a <Link href="/baanerp/ti/glossary/glossary#000366" role="glossary">process variable</Link> customer-specific by linking the process variable to an <Link href="/baanerp/tc/glossary/glossary#000304" role="glossary">effectivity unit</Link>. A process variable is one of the features of a <Link href="/baanerp/ti/glossary/glossary#000364" role="glossary">microrouting</Link>, and is used to establish settings or adjustments for a product.</Paragraph>
		</AimSection>
		<GeneralSection><Paragraph>You can use this session on the <GUIRef href="" role="manual">Effectivity Unit - Process Variables</GUIRef> tab in the <GUIRef href="/baanerp/tc/uef/tcuef0102m000" role="session">Effectivity Unit (tcuef0102m000)</GUIRef> session.</Paragraph>
		</GeneralSection>
		<ExampleSection><SectionTitle>Example</SectionTitle>
			<Paragraph>One of the settings for a beamer is distance. During the sales process, the customer must specify the required distance setting of a beamer. The standard distance setting is 10 meters, which is defined by the process variable DISTANCE. In the <GUIRef href="/baanerp/ti/rou/tirou1111m000" role="session">Operation (Step) - Process Variables (tirou1111m000)</GUIRef> session, you can define that for one of the operations a target value of 10.0 meters is printed on the production order documents.</Paragraph>
			<List><ListIntro>However, for a specific sales order with effectivity unit 4567, a customer wants a distance setting of 15 meters. This value must be entered in the <GUIRef href="/baanerp/ti/rou/tirou1114m000" role="session">Effectivity Unit - Process Variables (tirou1114m000)</GUIRef> session:</ListIntro>
				<ListItem>Effectivity Unit: 4567</ListItem>
				<ListItem>Process variable: DISTANCE</ListItem>
				<ListItem>Target value: 15.0</ListItem>
			</List>
			<Paragraph>This definition overrules the distance setting of 10 meters when a production order is generated for effectivity unit 4567. On the production order document a distance setting of 15 meters is printed.</Paragraph>
		</ExampleSection>
		<GeneralSection><SectionTitle>Linking process variables and effectivity units</SectionTitle>
			<Paragraph>To define the values of process variables desired by the customer is part of the sales process. No detailed knowledge of routings and BOMs is assumed by the sales persons. When configuring effectivity units, you can define process variables for an effectivity unit on the <GUIRef href="" role="manual">Effectivity Unit - Process Variables</GUIRef> tab in the <GUIRef href="/baanerp/tc/uef/tcuef0102m000" role="session">Effectivity Unit (tcuef0102m000)</GUIRef> session.</Paragraph>
			<Paragraph>If the production order for the effectivity unit is created, the standard target value for a process variable is overruled by the value defined in the <GUIRef href="/baanerp/ti/rou/tirou1114m000" role="session">Effectivity Unit - Process Variables (tirou1114m000)</GUIRef> session. Also when production order documents are printed, the standard target value is overruled. As a result, changes made after production order creation but before order document printing are reflected.</Paragraph>
		</GeneralSection>
		<Note><SectionTitle>Note</SectionTitle>
			<List><ListIntro>The following limitations must be noted:</ListIntro>
				<ListItem>If you define a new target value in the <GUIRef href="/baanerp/ti/rou/tirou1114m000" role="session">Effectivity Unit - Process Variables (tirou1114m000)</GUIRef> session, this value overrules existing target values for a specific effectivity unit. With regard to the example above: if you define a target value for DISTANCE, the target values of all process variables DISTANCE are overruled for all production orders for effectivity unit 4567, for any item.</ListItem>
				<ListItem>If you define a target value for a specific process variable in the <GUIRef href="/baanerp/ti/rou/tirou1114m000" role="session">Effectivity Unit - Process Variables (tirou1114m000)</GUIRef> session, but the process variable is not defined in the routing, then the process variable, and consequently the newly created target value, is not displayed in de micro routing. SSA ERP then does not know for which item or operation the process variable must be displayed.</ListItem>
				<ListItem>Changes to the target values in the <GUIRef href="/baanerp/ti/rou/tirou1114m000" role="session">Effectivity Unit - Process Variables (tirou1114m000)</GUIRef> session can always be entered but are only taken into account if the production order status is <GUIRef href="/baanerp/tc/domains/osta#planned" role="enum">Planned</GUIRef> or <GUIRef href="/baanerp/tc/domains/osta#scheduled" role="enum">Scheduled</GUIRef>.</ListItem>
				<ListItem>If a production order has a distribution of more than one effectivity unit, the existing target value is overrruled if: <List><ListItem>The specified effectivity unit is in the distribution</ListItem>
						<ListItem>The specified process variable is used in the micro routing.</ListItem>
					</List>
				</ListItem>
				<ListItem>If for different effectivity units of a specific production order distribution each time another target value is defined for the same process variable, the result is unpredictable. Any of the target values can be used, because only one routing exists, even if the production order has a distribution.</ListItem>
			</List>
		</Note>
		<RelatedTopics><SectionTitle>Related topics</SectionTitle>
			<RelTopic><Link href="/baanerp/tc/onlinemanual/000300" role="manual">Overview of unit effectivity</Link>
			</RelTopic>
			<RelTopic><Link href="/baanerp/ti/onlinemanual/000334" role="manual">Microrouting</Link>
			</RelTopic>
			<RelTopic><Link href="/baanerp/ti/onlinemanual/000346" role="manual">To set up a microrouting</Link>
			</RelTopic>
		</RelatedTopics>
	</HelpTopic>
	<Fields><FieldHelp ID="tirou114.effn"><Header>
				<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Effectivity Unit</Title>
			</Header>
			<FuncDesc><Link href="/baanerp/tc/glossary/glossary#000304" role="glossary">effectivity unit</Link>
			</FuncDesc>
		</FieldHelp>
		<FieldHelp ID="tcuef002.cfrd"><Header>
				<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Configuration Ready</Title>
			</Header>
			<FuncDesc>If this check box is selected, all desired <Link href="/baanerp/tc/glossary/glossary#000331" role="glossary">requirements</Link> are selected for the unit effective item.</FuncDesc>
		</FieldHelp>
		<FieldHelp ID="tirou114.pvar"><Header>
				<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Process Variable</Title>
			</Header>
			<FuncDesc><Link href="/baanerp/ti/glossary/glossary#000366" role="glossary">process variable</Link>
			</FuncDesc>
		</FieldHelp>
		<FieldHelp ID="tirou005.exde"><Header>
				<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Deviation Expressed In</Title>
			</Header>
			<FuncDesc>How the deviation of the target value is expressed, <GUIRef href="/baanerp/ti/domains/exde#absolute" role="enum">Absolute</GUIRef> or as a <GUIRef href="/baanerp/ti/domains/exde#percentage" role="enum">Percentage</GUIRef>.</FuncDesc>
			<DefaultValue><SectionTitle>Default value</SectionTitle>
				<Paragraph>This field has a default value taken from the <GUIRef href="/baanerp/ti/rou/tirou1111m000#tirou005.exde" role="formfield">Deviation Expressed In</GUIRef> field in the <GUIRef href="/baanerp/ti/rou/tirou0105m000" role="session">Process Variables (tirou0105m000)</GUIRef> session.</Paragraph>
			</DefaultValue>
		</FieldHelp>
		<FieldHelp ID="tirou114.tval"><Header>
				<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Target Value</Title>
			</Header>
			<FuncDesc>The process variable's target value.</FuncDesc>
		</FieldHelp>
		<FieldHelp ID="tirou114.upcl"><Header>
				<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Upper Control Limit</Title>
			</Header>
			<FuncDesc>The process variable's upper control limit that is expressed as an absolute value or as a percentage.</FuncDesc>
			<SimpleSection><SectionTitle>Absolute</SectionTitle>
				<Paragraph>If the upper control limit is expressed as an absolute value, the value is defined to which the process variable's target value can be exceeded.</Paragraph>
				<Paragraph>For example, if the target value is 30 and the upper control limit must not exceed 33, 33 is displayed this field.</Paragraph>
			</SimpleSection>
			<SimpleSection><SectionTitle>Percentage</SectionTitle>
				<Paragraph>If the upper control limit is expressed as a percentage, the percentage is defined with which the process variable's target value can be exceeded.</Paragraph>
				<Paragraph>For example, if the target value is 30 and the upper control limit must not exceed 33, 10% is displayed in this field.</Paragraph>
			</SimpleSection>
		</FieldHelp>
		<FieldHelp ID="tirou114.lwcl"><Header>
				<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Lower Control Limit</Title>
			</Header>
			<FuncDesc>The process variable's lower control limit, which is expressed as an absolute value or as a percentage.</FuncDesc>
			<SimpleSection><SectionTitle>Absolute</SectionTitle>
				<Paragraph>If the lower control limit is expressed as an absolute value, the minimum value is defined that the process variable's input value can be lower than the target value.</Paragraph>
				<Paragraph>For example, if the target value is 30, and the lower control limit must not be lower than 27, 27 is entered in this field.</Paragraph>
			</SimpleSection>
			<SimpleSection><SectionTitle>Percentage</SectionTitle>
				<Paragraph>If the lower control limit is expressed as a percentage, the percentage is defined that the process variable's input value can be lower than the target value.</Paragraph>
				<Paragraph>For example, if the target value is 30, and the lower control limit must not be lower than 27, 10% is entered in this field.</Paragraph>
			</SimpleSection>
		</FieldHelp>
	</Fields>
</Session>
