<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/cp/rao/cprao1110m000" xml:lang="en">
	<Header>
		<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Signal Types - by Planner (cprao1110m000)</Title>
	</Header>
	<HelpTopic><AimSection><List><ListIntro>Use this session to define and maintain planner-specific signal settings that determine:</ListIntro>
				<ListItem>Which types of <Link href="/baanerp/cp/glossary/glossary#000371" role="glossary" Update="No">signals</Link> are generated for the planner involved.</ListItem>
				<ListItem>Under which circumstances these signals must be generated.</ListItem>
			</List>
		</AimSection>
		<GeneralSection><Paragraph>Specify the signal types required for the <Link href="/baanerp/td/glossary/glossary#000018" role="glossary">planner</Link> involved, and define the settings for each signal type.</Paragraph>
			<Paragraph>For one signal type, you can define different settings for various cost-price ranges. For example, you can use different tolerance levels for high-cost orders versus low-cost orders.</Paragraph>
			<Paragraph>In the <GUIRef href="/baanerp/cp/rao/cprao1110m000#cprao010.cpra" role="formfield">Minimum Cost Price</GUIRef> field, you can specify a <Link href="/baanerp/cp/glossary/glossary#000405" role="glossary">minimum cost price</Link> for each signal.</Paragraph>
			<Paragraph>By leaving the <GUIRef href="/baanerp/cp/rao/cprao1110m000#cprao010.plid" role="formfield">Planner ID</GUIRef> field empty, you can define a general set of signal types. This general set is used for those signals that are not directed to a specific planner.</Paragraph>
			<Note><SectionTitle>Note</SectionTitle>
				<Paragraph>If you want to generate signals for a specific planner, you must first define a set of signal types for this planner. If you do not, SSA ERP does not generate the signals for this planner.</Paragraph>
			</Note>
		</GeneralSection>
		<RelatedTopics><SectionTitle>Related topics</SectionTitle>
			<RelTopic><Link href="/baanerp/cp/onlinemanual/000041" role="manual">Planning signals in Enterprise Planning</Link>
			</RelTopic>
			<RelTopic><Link href="/baanerp/cp/onlinemanual/000063" role="manual">Types of planning signals</Link>
			</RelTopic>
			<RelTopic><Link href="/baanerp/basictasks/000001" role="manual">To use an overview session</Link>
			</RelTopic>
			<RelTopic><Link href="/baanerp/basictasks/000035" role="manual">To maintain records in an overview session</Link>
			</RelTopic>
		</RelatedTopics>
	</HelpTopic>
	<Fields><FieldHelp ID="cprao010.plid"><Header>
				<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Planner ID</Title>
			</Header>
			<FuncDesc>The employee number of the planner whose set of signal types is shown.</FuncDesc>
			<Note><SectionTitle>Note</SectionTitle>
				<Paragraph>As a rule, a signal is directed to a specific <Link href="/baanerp/td/glossary/glossary#000018" role="glossary">planner</Link> if the signal refers to an item for which an employee code has been entered in the <GUIRef href="/baanerp/cp/rpd/cprpd1100m000#cprpd100.plid" role="formfield">Planner</GUIRef> field in the <GUIRef href="/baanerp/cp/rpd/cprpd1100m000" role="session">Items - Planning (cprpd1100m000)</GUIRef>
				</Paragraph>
			</Note>
			<SimpleSection><Paragraph>If this field is empty, a general set of signal types is displayed, which is used for all <Link href="/baanerp/cp/glossary/glossary#000371" role="glossary">signals</Link> that are not directed to a specific planner.</Paragraph>
			</SimpleSection>
		</FieldHelp>
		<FieldHelp ID="cprpd000.mcpc"><Header>
				<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Minimum Cost Price Currency for Signals</Title>
			</Header>
			<FuncDesc>The currency that SSA ERP uses to express the <Link href="/baanerp/cp/glossary/glossary#000405" role="glossary">minimum cost price</Link>, which you can define in the <GUIRef href="/baanerp/cp/rpd/cprpd0100m000" role="session">EP Parameters (cprpd0100m000)</GUIRef> session.</FuncDesc>
			<SimpleSection><Paragraph>If you defined a different currency for the item in the <GUIRef href="/baanerp/ti/cpr/ticpr0107m000" role="session">Items - Costing (ticpr0107m000)</GUIRef> session, SSA ERP converts this currency to the curency for the minimum cost price.</Paragraph>
			</SimpleSection>
		</FieldHelp>
		<FieldHelp ID="cprao010.sign"><Header>
				<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Signal Type</Title>
			</Header>
			<FuncDesc>Specify the type of signal that SSA ERP can generate during planning.</FuncDesc>
			<SimpleSection><Paragraph>Signal types inform the <Link href="/baanerp/td/glossary/glossary#000018" role="glossary">planner</Link> about the current planning process.</Paragraph>
			</SimpleSection>
		</FieldHelp>
		<FieldHelp ID="cprao010.cpra"><Header>
				<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Minimum Cost Price</Title>
			</Header>
			<FuncDesc>The <Link href="/baanerp/cp/glossary/glossary#000405" role="glossary">minimum cost price</Link> to which the signal type on this line applies.</FuncDesc>
			<SimpleSection><Paragraph>If the <GUIRef href="/baanerp/cp/rao/cprao1110m000#cprao010.cpra" role="formfield">Minimum Cost Price</GUIRef> field for a signal type is blank, you can specify a value. If you do so, <GUIRef href="/baanerp/tc" role="package">Common Data</GUIRef> only generates the corresponding signal type, if the <GUIRef href="/baanerp/ti/cpr/ticpr0107m000#ticpr007.ecpr" role="formfield">Cost Price</GUIRef> of the ordered item lies above the minimum cost price.</Paragraph>
			</SimpleSection>
		</FieldHelp>
		<FieldHelp ID="cprao010.plsp"><Header>
				<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Priority</Title>
			</Header>
			<FuncDesc>The default priority of the signal type. You can use this priority, for example, to display the signals in order of importance.</FuncDesc>
			<AllowedValues><SectionTitle>Allowed values</SectionTitle>
				<Paragraph>Enter a number from one (highest priority) to 100 (lowest priority).</Paragraph>
			</AllowedValues>
		</FieldHelp>
		<FieldHelp ID="cprao010.hori"><Header>
				<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Horizon</Title>
			</Header>
			<FuncDesc>The <Link href="/baanerp/cp/glossary/glossary#000071" role="glossary">signal horizon</Link> of the signal type on this line.</FuncDesc>
			<AllowedValues><SectionTitle>Allowed values</SectionTitle>
				<Paragraph>The value entered must be larger than zero.</Paragraph>
			</AllowedValues>
			<Note><SectionTitle>Note</SectionTitle>
				<List><ListIntro>For some signal types, the horizon has a fixed value. The scope of the horizon is so large that in actuality, the generation of signals of these types is never constrained by the horizon. The signal types involved are the following:</ListIntro>
					<ListItem><GUIRef href="/baanerp/cp/domains/rao.sign#fatal" role="enum">Fatal Error</GUIRef>
					</ListItem>
					<ListItem><GUIRef href="/baanerp/cp/domains/rao.sign#no.supply" role="enum">No Supplying Relationship</GUIRef>
					</ListItem>
					<ListItem><GUIRef href="/baanerp/cp/domains/rao.sign#no.bpid" role="enum">No Supplying Business Partner</GUIRef>
					</ListItem>
					<ListItem><GUIRef href="/baanerp/cp/domains/rao.sign#item" role="enum">Item Error</GUIRef>
					</ListItem>
					<ListItem><GUIRef href="/baanerp/cp/domains/rao.sign#empty.plan.unit" role="enum">No Items for Plan Unit</GUIRef>
					</ListItem>
					<ListItem><GUIRef href="/baanerp/cp/domains/rao.sign#plan.failure" role="enum">Planning Failed</GUIRef>
					</ListItem>
				</List>
			</Note>
		</FieldHelp>
		<FieldHelp ID="cprao010.tole"><Header>
				<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Tolerance (%)</Title>
			</Header>
			<FuncDesc>The tolerance percentage applies to signals that involve a comparison of quantities or percentages, and that indicate that a certain actual value is higher or lower than a certain norm value.</FuncDesc>
			<SimpleSection><Paragraph>The tolerance percentage involved is a percentage of the norm value. If you define a tolerance percentage for a signal type, SSA ERP will ignore minor deviations from the norm value when it generates signals of this type.</Paragraph>
			</SimpleSection>
			<SimpleSection><SectionTitle>Example</SectionTitle>
				<List><ListItem>The signal type is <GUIRef href="/baanerp/cp/domains/rao.sign#inven.hi.max" role="enum">Inventory &gt; Maximum</GUIRef>, the maximum inventory is 50, and the tolerance percentage is ten. In this case, a signal is generated only when the projected inventory is higher than 55.</ListItem>
					<ListItem>The signal type is <GUIRef href="/baanerp/cp/domains/rao.sign#orqa.lo.min" role="enum">Order Quantity &lt; Minimum</GUIRef>, the minimum order quantity is 20, and the tolerance percentage is 15. In this case, a signal is generated only when the order quantity is lower than 17.</ListItem>
				</List>
				<List><ListIntro>The tolerance percentage applies to the following signals types:</ListIntro>
					<ListItem><GUIRef href="/baanerp/cp/domains/rao.sign#inven.lo.safety" role="enum">Inventory &lt; Safety/Plan</GUIRef>
					</ListItem>
					<ListItem><GUIRef href="/baanerp/cp/domains/rao.sign#inven.hi.max" role="enum">Inventory &gt; Maximum</GUIRef>
					</ListItem>
					<ListItem><GUIRef href="/baanerp/cp/domains/rao.sign#demf.dif.act" role="enum">Forecast &lt;&gt; Actual Demand</GUIRef>
					</ListItem>
					<ListItem><GUIRef href="/baanerp/cp/domains/rao.sign#astc.hi.pstc" role="enum">Inventory &gt; Inventory Plan</GUIRef>
					</ListItem>
					<ListItem><GUIRef href="/baanerp/cp/domains/rao.sign#orqa.lo.min" role="enum">Order Quantity &lt; Minimum</GUIRef>
					</ListItem>
					<ListItem><GUIRef href="/baanerp/cp/domains/rao.sign#orqa.hi.max" role="enum">Order Quantity &gt; Maximum</GUIRef>
					</ListItem>
					<ListItem><GUIRef href="/baanerp/cp/domains/rao.sign#over.util" role="enum">Overloaded Resource</GUIRef>
					</ListItem>
				</List>
			</SimpleSection>
			<SimpleSection><Paragraph>For all other signal types, the tolerance percentage is disabled. This includes the signal types <GUIRef href="/baanerp/cp/domains/rao.sign#work.lo.norm" role="enum">Workload &lt; Norm</GUIRef> and <GUIRef href="/baanerp/cp/domains/rao.sign#work.hi.norm" role="enum">Workload &gt; Norm</GUIRef>. For these two signal types, however, you can define a tolerance percentage in the <GUIRef href="/baanerp/cp/rpd/cprpd2100m000" role="session">Resource (cprpd2100m000)</GUIRef> session (in the <GUIRef href="/baanerp/cp/rpd/cprpd2100m000#cprpd200.wlpe" role="formfield">Workload Tolerance</GUIRef> field).</Paragraph>
			</SimpleSection>
			<Note><SectionTitle>Note</SectionTitle>
				<Paragraph>In the case of the signal type <GUIRef href="/baanerp/cp/domains/rao.sign#demf.dif.act" role="enum">Forecast &lt;&gt; Actual Demand</GUIRef>, the demand forecast is used as the norm value, and the tolerance percentage applies in both directions (below and above the demand forecast).</Paragraph>
			</Note>
		</FieldHelp>
		<FieldHelp ID="cprao010.told"><Header>
				<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Tolerance (Days)</Title>
			</Header>
			<FuncDesc>The tolerance in days applies to signals that involve a comparison of dates, and that indicate that a certain date is earlier or later than a certain norm date.</FuncDesc>
			<SimpleSection><Paragraph>The tolerance in days is expressed in working days. If you define a tolerance in days for a signal type, SSA ERP will ignore minor deviations from the norm date when it generates signals of this type.</Paragraph>
			</SimpleSection>
			<SimpleSection><SectionTitle>Example</SectionTitle>
				<List><ListItem>The signal type is <GUIRef href="/baanerp/cp/domains/rao.sign#order.late" role="enum">Finish Date &gt; Requirement Date</GUIRef>, the requirement date is Monday, April 10, and the tolerance in days is two. In this case, a signal is generated only when the order's end date is later than April</ListItem>
					<ListItem>The signal type is <GUIRef href="/baanerp/cp/domains/rao.sign#reschedule.out" role="enum">Reschedule Out</GUIRef>, the requirement date is Friday, August 25, and the tolerance in days is three. In this case, a signal is generated only when the order's end date is earlier than August 22.</ListItem>
				</List>
				<List><ListIntro>The tolerance in days applies to the following signal types:</ListIntro>
					<ListItem><GUIRef href="/baanerp/cp/domains/rao.sign#release.to.late" role="enum">Transfer Late</GUIRef>
					</ListItem>
					<ListItem><GUIRef href="/baanerp/cp/domains/rao.sign#reschedule.in" role="enum">Reschedule In</GUIRef>
					</ListItem>
					<ListItem><GUIRef href="/baanerp/cp/domains/rao.sign#reschedule.out" role="enum">Reschedule Out</GUIRef>
					</ListItem>
					<ListItem><GUIRef href="/baanerp/cp/domains/rao.sign#order.in.safety" role="enum">Order within Safety Time</GUIRef>
					</ListItem>
					<ListItem><GUIRef href="/baanerp/cp/domains/rao.sign#order.in.inter" role="enum">Order in Order Interval</GUIRef>
					</ListItem>
					<ListItem><GUIRef href="/baanerp/cp/domains/rao.sign#order.in.eltm" role="enum">Order in Extra Lead Time</GUIRef>
					</ListItem>
					<ListItem><GUIRef href="/baanerp/cp/domains/rao.sign#order.late" role="enum">Finish Date &gt; Requirement Date</GUIRef>
					</ListItem>
				</List>
			</SimpleSection>
			<SimpleSection><Paragraph>For all other signal types, the tolerance in days is disabled.</Paragraph>
			</SimpleSection>
			<Note><SectionTitle>Note</SectionTitle>
				<Paragraph>For the <GUIRef href="/baanerp/cp/domains/rao.sign#release.to.late" role="enum">Transfer Late</GUIRef> signal type, the tolerance in days is actually used as a special kind of time fence, to indicate when the order should be transferred.</Paragraph>
			</Note>
			<Note><SectionTitle>Note</SectionTitle>
				<List><ListItem><Link href="/baanerp/cp/onlinemanual/000069" role="manual">Order signals</Link>
					</ListItem>
				</List>
			</Note>
		</FieldHelp>
		<FieldHelp ID="cprao010.manu"><Header>
				<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Maximum Number</Title>
			</Header>
			<FuncDesc>The maximum number of signals of this type that SSA ERP generates for a specific item/planner combination.</FuncDesc>
			<SimpleSection><Paragraph>For example, if you set the maximum number of a specific signal type to ten, only the first ten signals of this type are stored for one item (and for a specific planner).</Paragraph>
			</SimpleSection>
			<Note><SectionTitle>Note</SectionTitle>
				<List><ListIntro>For some signal types, the maximum number of signals is a fixed value. The extent of this value is so large that in actuality, the generation of signals of these types is never constrained by the maximum number. The signal types involved are the following:</ListIntro>
					<ListItem><GUIRef href="/baanerp/cp/domains/rao.sign#fatal" role="enum">Fatal Error</GUIRef>
					</ListItem>
					<ListItem><GUIRef href="/baanerp/cp/domains/rao.sign#no.supply" role="enum">No Supplying Relationship</GUIRef>
					</ListItem>
					<ListItem><GUIRef href="/baanerp/cp/domains/rao.sign#no.bpid" role="enum">No Supplying Business Partner</GUIRef>
					</ListItem>
					<ListItem><GUIRef href="/baanerp/cp/domains/rao.sign#item" role="enum">Item Error</GUIRef>
					</ListItem>
					<ListItem><GUIRef href="/baanerp/cp/domains/rao.sign#empty.plan.unit" role="enum">No Items for Plan Unit</GUIRef>
					</ListItem>
					<ListItem><GUIRef href="/baanerp/cp/domains/rao.sign#plan.failure" role="enum">Planning Failed</GUIRef>
					</ListItem>
				</List>
			</Note>
		</FieldHelp>
		<FieldHelp ID="cprao010.disa"><Header>
				<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Disable</Title>
			</Header>
			<FuncDesc>If this check box is selected, no signals of the type specified are generated.</FuncDesc>
			<Note><SectionTitle>Note</SectionTitle>
				<Paragraph>Essentially, disabling a signal type has the same effect as deleting the record for that signal type. However, disabling the signal type has the advantage that you can easily re-enable it.</Paragraph>
			</Note>
		</FieldHelp>
		<FieldHelp ID="cprao010.autp"><Header>
				<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Auto Process</Title>
			</Header>
			<FuncDesc>If this check box is selected,SSA ERP can process the corresponding signal automatically in the <GUIRef href="/baanerp/cp/rao/cprao1220m000" role="session">Process - Signals (cprao1220m000)</GUIRef> session.</FuncDesc>
			<SimpleSection><List><ListIntro>You can only select this check box for the following signal types:</ListIntro>
					<ListItem><GUIRef href="/baanerp/cp/domains/rao.sign#cancel" role="enum">Cancel Order</GUIRef>
					</ListItem>
					<ListItem><GUIRef href="/baanerp/cp/domains/rao.sign#reschedule.in" role="enum">Reschedule In</GUIRef>
					</ListItem>
					<ListItem><GUIRef href="/baanerp/cp/domains/rao.sign#reschedule.out" role="enum">Reschedule Out</GUIRef>
					</ListItem>
				</List>
				<Paragraph>SSA ERP only generates the signal types mentioned above when you carry out <Link href="/baanerp/cp/glossary/glossary#000060" role="glossary">order-based planning</Link>.</Paragraph>
				<Paragraph>After you carried out order-based planning, and SSA ERP generated cancellation and/or rescheduling signals, you can see these signals in the <GUIRef href="/baanerp/cp/rao/cprao1125m000" role="session">Planner/Item Signals (cprao1125m000)</GUIRef> session with the corresponding <GUIRef href="/baanerp/cp/rao/cprao1125m000#cprao020.autp" role="formfield">Auto Process</GUIRef> check box selected.</Paragraph>
			</SimpleSection>
		</FieldHelp>
	</Fields>
	<FormCommands><CommandHelp ID="cprao1410m000"><Header>
				<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Print Signal Types</Title>
			</Header>
			<FuncDesc>Starts the <GUIRef href="/baanerp/cp/rao/cprao1410m000" role="session">Print Signal Types (cprao1410m000)</GUIRef> session.</FuncDesc>
		</CommandHelp>
	</FormCommands>
</Session>
