<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/ti/asl/tiasl8100m000" xml:lang="en">
	<Header>
		<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Process Trigger Definition (tiasl8100m000)</Title>
	</Header>
	<HelpTopic><AimSection><Paragraph>Use this session to define the processes that occur at a specific line station, or the session that is triggered by that event.</Paragraph>
		</AimSection>
		<GeneralSection><Paragraph>The concept of process triggering holds that an event at a certain line station is used as a trigger to fire the execution of a session. For example, the completion of a line station order can be used as a trigger to execute the <GUIRef href="/baanerp/ti/asc/tiasc5451m000" role="session">Start Print Work Instructions (tiasc5451m000)</GUIRef> session to print work instructions for the next line station. This way you can also use events on a main assembly line to trigger processes on a supplying line to synchronize the production process. Refer to the Field help in the following paragraphs for a list of events that can be used as triggers, and sessions that can be triggered.</Paragraph>
			<Note><SectionTitle>Note</SectionTitle>
				<List><ListItem>The concept of process in this session bears no relationship to either the process industries (chemical engineering) or to the distinction between process engineering and production engineering used elsewhere in <GUIRef href="/baanerp/ti/asc" role="module">Assembly Control</GUIRef>.</ListItem>
					<ListItem>You must use the <GUIRef href="/baanerp/ti/asl/tiasl8210m000" role="session">Display and Handle Process Triggers (tiasl8210m000)</GUIRef> session to enable the triggers.</ListItem>
				</List>
			</Note>
		</GeneralSection>
		<RelatedTopics><SectionTitle>Related topics</SectionTitle>
			<RelTopic><Link href="/baanerp/ti/onlinemanual/000301" role="manual">Assembly control overview</Link>
			</RelTopic>
		</RelatedTopics>
	</HelpTopic>
	<Fields><FieldHelp ID="tiasl800.prcs"><Header>
				<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Process</Title>
			</Header>
			<FuncDesc>You can use four events as triggers in <GUIRef href="/baanerp/ti/asc" role="module">Assembly Control</GUIRef>.</FuncDesc>
			<SimpleSection><List><ListIntro>These events are:</ListIntro>
					<ListItem><GUIRef href="/baanerp/ti/domains/asl.prtr#complete.lso" role="enum">Complete Line Station Orders</GUIRef>
					</ListItem>
					<ListItem><GUIRef href="/baanerp/ti/domains/asl.prtr#offset.lso" role="enum">Offset Line Station Orders</GUIRef>
					</ListItem>
					<ListItem><GUIRef href="/baanerp/ti/domains/asl.prtr#start.order" role="enum">Start Assembly Order</GUIRef>
					</ListItem>
					<ListItem><GUIRef href="/baanerp/ti/domains/asl.prtr#freeze.lso" role="enum">Freeze Line Station Orders</GUIRef>
					</ListItem>
				</List>
			</SimpleSection>
		</FieldHelp>
		<FieldHelp ID="tiasl800.trst"><Header>
				<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Trigg. by Stn</Title>
			</Header>
			<FuncDesc>The line station on which the event takes place that triggers the session. For example, you can state that the session must be carried out on a main assembly line when the order is completed in a supplying assembly line.</FuncDesc>
			<SimpleSection><Paragraph>You define the trigger in the <GUIRef href="/baanerp/ti/asl/tiasl8100m000#tiasl800.prcs" role="formfield">Process</GUIRef> field.</Paragraph>
			</SimpleSection>
		</FieldHelp>
		<FieldHelp ID="tiasl800.lstn"><Header>
				<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Station</Title>
			</Header>
			<FuncDesc>The line station for which the triggered process has to be performed, such as the printing of the work instructions on that line station. This can either be the same line station as the one that triggers the process, or another one.</FuncDesc>
		</FieldHelp>
		<FieldHelp ID="tiasl800.wfml"><Header>
				<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Session/Model</Title>
			</Header>
			<FuncDesc>The name of the formal workflow process or the session name of the session that you want to trigger, which you have defined in your workflow model.</FuncDesc>
			<SimpleSection><List><ListIntro>You can trigger the following sessions:</ListIntro>
					<ListItem><Link href="/baanerp/ti/asc/tiasc8210m000" role="session">Replenish Shop Floor Warehouse (tiasc8210m000)</Link>
					</ListItem>
					<ListItem><Link href="/baanerp/ti/asc/tiasc7200m000" role="session">Generate WIP Transfer (tiasc7200m000)</Link>
					</ListItem>
					<ListItem><Link href="/baanerp/ti/asc/tiasc7201m000" role="session">Execute WIP Issue (tiasc7201m000)</Link>
					</ListItem>
					<ListItem><Link href="/baanerp/ti/asc/tiasc7202m000" role="session">Execute WIP Receipt (tiasc7202m000)</Link>
					</ListItem>
					<ListItem><Link href="/baanerp/ti/asc/tiasc5451m000" role="session">Start Print Work Instructions (tiasc5451m000)</Link>
					</ListItem>
					<ListItem><Link href="/baanerp/ti/asc/tiasc4200m000" role="session">Request Start - Assembly Order on Line Station (tiasc4200m000)</Link>
					</ListItem>
				</List>
			</SimpleSection>
		</FieldHelp>
		<FieldHelp ID="tiasl800.kopr"><Header>
				<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Type</Title>
			</Header>
			<FuncDesc>The name of a process used by the software in the <GUIRef href="/baanerp/tg" role="package">Enterprise Modeler</GUIRef> package.</FuncDesc>
			<SimpleSection><List><ListIntro>In this field, you have the following options:</ListIntro>
					<ListItem><Emphasis>Formal Workflow Process</Emphasis> This option is not implemented. So, choose the next one.</ListItem>
					<ListItem><Emphasis>Session</Emphasis> A SSA ERP session in the <GUIRef href="/baanerp/ti/asc" role="module">Assembly Control</GUIRef> module.</ListItem>
				</List>
			</SimpleSection>
		</FieldHelp>
		<FieldHelp ID="tiasl800.devi"><Header>
				<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Device</Title>
			</Header>
			<FuncDesc>If the process produces a report, the device that prints or displays the report.</FuncDesc>
		</FieldHelp>
		<FieldHelp ID="tiasl800.jsty"><Header>
				<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Job Sequence Type</Title>
			</Header>
			<FuncDesc>The planned requirement date and the planned requirement time of the assembly part requirements are calculated on the basis of what you enter in the <GUIRef href="/baanerp/ti/asc/tiasc8210m000#ptwf.job.sequence" role="formfield">Job Sequence Type</GUIRef> field in the <Link href="/baanerp/ti/asc/tiasc8210m000" role="session">Replenish Shop Floor Warehouse (tiasc8210m000)</Link> session.</FuncDesc>
			<SimpleSection><List><ListIntro>You can schedule materials based on the planned sequence of the line station for which the materials are scheduled (called-off), but this is not always a realistic solution because the planned sequence can differ from the actual sequence. If the planned and actual sequences differ, you can send a message based on the actual sequence on the trigger line station, which is the line station on which the triggers are activated. With this solution, materials are only scheduled for the assembly orders that have already passed the trigger point. SSA ERP calculates the arrival times of the materials based on:</ListIntro>
					<ListItem>The number of line stations between the supply line station and the trigger line station.</ListItem>
					<ListItem>The cycle time. You can also set triggers based on the planned sequence of the supply station. In this case, SSA ERP takes into account line buffer variations, for which a safety lead time can be defined, and the scheduled delay.</ListItem>
				</List>
				<Paragraph>Note The planned requirement date of items that are ordered with order-controlled batch is always based on the planned start times of the assembly orders. Therefore, the calculation of the planned requirement date, based on the actual sequence, can only be used by <Link href="/baanerp/wh/glossary/glossary#000404" role="glossary">order-controlled/batch</Link> items.</Paragraph>
				<Paragraph>The field can have the values <GUIRef href="/baanerp/ti/domains/asc.jsty#planned" role="enum">Planned</GUIRef> and <GUIRef href="/baanerp/ti/domains/asc.jsty#actual" role="enum">Actual</GUIRef>.</Paragraph>
				<Paragraph>If the assembly order at <GUIRef href="/baanerp/ti/asl/tiasl8100m000#tiasl800.trst" role="formfield">Trigg. by Stn</GUIRef> is not completed or closed, the <GUIRef href="/baanerp/ti/asc/tiasc8210m000#ptwf.job.sequence" role="formfield">Job Sequence Type</GUIRef> can only be set to <GUIRef href="/baanerp/ti/domains/asc.jsty#planned" role="enum">Planned</GUIRef>, because no actual timings will be present for the order at this line station.</Paragraph>
				<Paragraph>You can set the <GUIRef href="/baanerp/ti/asc/tiasc8210m000#ptwf.job.sequence" role="formfield">Job Sequence Type</GUIRef> to <GUIRef href="/baanerp/ti/domains/asc.jsty#planned" role="enum">Planned</GUIRef> or <GUIRef href="/baanerp/ti/domains/asc.jsty#actual" role="enum">Actual</GUIRef>, if the assembly order at <GUIRef href="/baanerp/ti/asl/tiasl8100m000#tiasl800.trst" role="formfield">Trigg. by Stn</GUIRef> is completed or closed. This is because the actual timings will be present for the order at this line station. If you select Planned, the assembly parts are ordered in a supply line sequence that is based on the planned start time of the line station order. If you select Actual, the assembly parts are ordered in a sequence that is based on the actual sequence.</Paragraph>
				<List><ListIntro>You can consider the next sequenced assembly order in the line sequence, if the following conditions are met:</ListIntro>
					<ListItem>The assembly parts are order controlled SILS assembly parts.</ListItem>
					<ListItem>The supply messages for the assembly order which triggered the supply are generated. The next sequenced orders are considered on the basis of the batch size that is defined for the KIT in the <Link href="/baanerp/wh/wmd/whwmd4500m000" role="session">Items - Warehousing (whwmd4500m000)</Link> session in <GUIRef href="/baanerp/wh" role="package">Warehouse Management</GUIRef>.</ListItem>
				</List>
				<Paragraph>When the replenish process is executed, order controlled SILS / batch messages are generated. These messages are not automatically transferred to <GUIRef href="/baanerp/wh" role="package">Warehouse Management</GUIRef> and <GUIRef href="/baanerp/td/pur" role="module">Purchase Control</GUIRef>. To transfer these messages, the <GUIRef href="/baanerp/ti/asc/tiasc8220m000" role="session">Transfer Assembly Part Supply Messages (tiasc8220m000)</GUIRef> must be run, which is normally run as a scheduled job.</Paragraph>
				<Paragraph>The transfer order number is only filled if the Order Controlled SILS/Batch Messages are transferred to <GUIRef href="/baanerp/wh" role="package">Warehouse Management</GUIRef> and <GUIRef href="/baanerp/td/pur" role="module">Purchase Control</GUIRef>, using the <Link href="/baanerp/ti/asc/tiasc8220m000" role="session">Transfer Assembly Part Supply Messages (tiasc8220m000)</Link> session. The Transfer Order Number is filled in the <Link href="/baanerp/ti/asc/tiasc8510m000" role="session">Line Station - Assembly Part Supply Transfer (Batch) (tiasc8510m000)</Link> session and in the <Link href="/baanerp/ti/asc/tiasc8520m000" role="session">Line Station - Assembly Part Supply Transfer (SILS) (tiasc8520m000)</Link> session.</Paragraph>
			</SimpleSection>
		</FieldHelp>
	</Fields>
</Session>
