<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/ti/asc/tiasc2103m000" xml:lang="en">
	<Header>
		<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Assembly Order - Blocking Reasons (tiasc2103m000)</Title>
	</Header>
	<HelpTopic><AimSection><Paragraph>Use this session to view, insert, or remove blocking reasons. An order is blocked if it has at least one blocking reason and unblocked if it has no blocking reasons.</Paragraph>
		</AimSection>
		<GeneralSection><Paragraph>A blocked assembly order is blocked from sequencing, starting from the buffer, backflushing, delivery, and closing. So there is no possibility to process the order. Only, if the order was already started when it was blocked, it can be completed to prevent loss of information. The order will be stopped at the next line segment, that is: It cannot be started from the next buffer. If an order is unblocked, it can be processed again.</Paragraph>
			<Paragraph>Before you can view, insert, or remove blocking reasons, you must select an order. To insert a new blocking reason, click New Record and select the reason you want to insert. To remove a blocking reason, select and delete it.</Paragraph>
			<GeneralSection><SectionTitle>Blocking reasons</SectionTitle>
				<Paragraph>If you want to block an order, you must choose a blocking reason. Blocking reasons are grouped in types. An order can have several blocking reaons, but these reasons must be of different types. So, an order cannot have two blocking reasons of type <GUIRef href="/baanerp/tc/domains/mcs.rstp#inv.shortage" role="enum">Inventory Shortage</GUIRef>.</Paragraph>
				<List><ListIntro>In this session, you can use the following two types of blocking reasons:</ListIntro>
					<ListItem><GUIRef href="/baanerp/tc/domains/mcs.rstp#inv.shortage" role="enum">Inventory Shortage</GUIRef> Use a reason of this type to block orders for inventory shortage reasons.</ListItem>
					<ListItem><GUIRef href="" role="manual">Undefined</GUIRef> All other reasons fall under this type.</ListItem>
				</List>
			</GeneralSection>
			<GeneralSection><SectionTitle>Consequences for other orders</SectionTitle>
				<List><ListIntro>Blocking or unblocking an order can have consequences for other orders as well. These consequences depend on the relation of the order in question to other orders.</ListIntro>
					<ListItem>If you block a child order, the parent order also receives the Blocked status, but without a blocking reason. The blocking is inherited downstream the assembly line. Other child orders of the parent order upstream from the assembly line where the blocking reason is inserted, are not blocked.</ListItem>
					<ListItem>If you unblock a child order, SSA ERP unblocks the parent order too, unless the parent order has other blocked child orders.</ListItem>
					<ListItem>If you block a parent order, the status of the child orders does not change. You can continue to process the child order, but you cannot proceed to processing the parent order. Therefore, the product of the child order must be stored untill the parent order is unblocked.</ListItem>
					<ListItem>If you unblock a parent order, this has no effect for the child orders. But you can only unblock a parent order if it has no blocked child orders. This actually means that unblocking a parent order is only possible if you blocked this order directly, and subsequently, no child orders were blocked. Otherwise, you have to unblock the parent order by unblocking the child orders.</ListItem>
				</List>
			</GeneralSection>
		</GeneralSection>
		<RelatedTopics><SectionTitle>Related topics</SectionTitle>
			<RelTopic><Link href="/baanerp/ti/onlinemanual/000301" role="manual">Assembly control overview</Link>
			</RelTopic>
			<RelTopic><Link href="/baanerp/ti/onlinemanual/000182" role="manual">Critical items</Link>
			</RelTopic>
			<RelTopic><Link href="/baanerp/ti/onlinemanual/000306" role="manual">Assembly orders</Link>
			</RelTopic>
			<RelTopic><Link href="/baanerp/ti/onlinemanual/000323" role="manual">Line sequencing and rule types in Assembly Control</Link>
			</RelTopic>
			<RelTopic><Link href="/baanerp/ti/onlinemanual/000305" role="manual">Assembly line station utilization</Link>
			</RelTopic>
		</RelatedTopics>
	</HelpTopic>
	<Fields><FieldHelp ID="tiasc203.asso"><Header>
				<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Assembly Order</Title>
			</Header>
			<FuncDesc>The order selected to view, insert, or remove blocking reasons.</FuncDesc>
		</FieldHelp>
		<FieldHelp ID="tiasc203.blrs"><Header>
				<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Blocking Reason</Title>
			</Header>
			<FuncDesc>The blocking code identifies the blocking reason. Blocking reasons are grouped in blocking types. For example, <GUIRef href="/baanerp/tc/domains/mcs.rstp#inv.shortage" role="enum">Inventory Shortage</GUIRef> is a blocking reason type. An order can have several blocking reasons if these reasons differ in type. The code can represent additional information, especially if a text file is attached to it.</FuncDesc>
		</FieldHelp>
		<FieldHelp ID="tiasc203.crdt"><Header>
				<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Creation Date</Title>
			</Header>
			<FuncDesc>The date on which the blocking reason was inserted.</FuncDesc>
		</FieldHelp>
		<FieldHelp ID="tiasc203.user"><Header>
				<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">User</Title>
			</Header>
			<FuncDesc>The person who inserted the blocking reason.</FuncDesc>
		</FieldHelp>
		<FieldHelp ID="f.text"><Header>
				<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Text</Title>
			</Header>
			<FuncDesc>A blocking reason may require additional information, for example: when the blocking reason is to be removed. This information can be stored in an attached text file. Double-click the record and use the Text Editor to read, create, select, or edit a text.</FuncDesc>
		</FieldHelp>
	</Fields>
</Session>
