<?xml version="1.0" encoding="utf-8"?>
<Glossary ID="/baanerp/cp/glossary/glossary" xml:lang="en">
	<Header>
		<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Glossary for the CP package</Title>
	</Header>
	<GlossaryEntry ID="000127" Version="B60adoc1" ContextApps="cp"><Term>actual receipts</Term>
		<Definition>The supply quantity that has already been received from the goods flow, that is, from actual orders.</Definition>
		<SimpleSection><Paragraph>The actual receipts are only recorded for the current plan period. These receipts have already been included in the inventory on hand.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000093" Version="B60adoc1" ContextApps="cp"><Term>actual scenario</Term>
		<Definition>The scenario that contains the operational master plan and/or order planning, as opposed to scenarios used only for simulation (what-if analysis).</Definition>
		<SimpleSection><Paragraph>The actual scenario is the only scenario from which you can transfer planned orders to the execution level.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000402" Version="B60adoc1" ContextApps="cp"><Term>aggregation relationship</Term>
		<Definition>A specification, expressed as a percentage, how items are aggregated or disaggregated.</Definition>
		<SimpleSection><Paragraph>To aggregate items means that different items are grouped to form product families for planning purposes. This is also called a planning bill of material. To disaggregate items means that a product family is split up into smaller families, or into items.</Paragraph>
			<Paragraph>Aggregation relationships can have the same structure as a single-level bill of material. However, similar to production bills of materials, also multilevel structures can be created.</Paragraph>
			<Paragraph></Paragraph>
		</SimpleSection>
		<ExampleSection><SectionTitle>Example</SectionTitle>
			<Paragraph></Paragraph>
			<Figure><HTML:IMG SRC="../images/nt_graph_GL000402.gif" height="216" width="396" xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40"/><FigLegend><LegendEntry><Symbol>PL 1</Symbol>
						<Desc>Plan level 1 (product family)</Desc>
					</LegendEntry>
					<LegendEntry><Symbol>PL 2</Symbol>
						<Desc>Plan level 2 (items)</Desc>
					</LegendEntry>
					<LegendEntry><Symbol>BC</Symbol>
						<Desc>Bicycles</Desc>
					</LegendEntry>
					<LegendEntry><Symbol>MB</Symbol>
						<Desc>Mountain bike</Desc>
					</LegendEntry>
					<LegendEntry><Symbol>T</Symbol>
						<Desc>Tandem</Desc>
					</LegendEntry>
					<LegendEntry><Symbol>RB</Symbol>
						<Desc>Racing bike</Desc>
					</LegendEntry>
				</FigLegend>
			</Figure>
		</ExampleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000108" Version="B60adoc1" ContextApps="cp"><Term>allocation rule</Term>
		<Definition>The rule that defines how <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef> determines the quantity that must be supplied by a supplier or supplying cluster. For example, a percentage of the total supply or the supplier's capability to supply.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000025" Version="B60adoc1" ContextApps="cp"><Term>allowed demand</Term>
		<Definition>The maximum volume that you want to sell to customers in a particular channel. When this maximum is reached in a certain channel ATP period, you accept no more customer orders for that channel.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="415" Version="5.2b" ContextApps="tt"><Term>ATP/CTP horizon</Term>
		<Definition>The date until which SSA ERP performs ATP and CTP checks.</Definition>
		<SimpleSection><Paragraph>The ATP horizon is expressed as a number of working days during which SSA ERP can carry out ATP and CTP checks. Beyond the ATP/CTP horizon, SSA ERP does not check ATP or CTP: all customer orders are accepted.</Paragraph>
			<Paragraph></Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000030" Version="B60adoc1" ContextApps="cp"><Term>available-to-promise</Term>
		<Definition>The item quantity that is still available to be promised to a customer.</Definition>
		<SimpleSection><Paragraph>In SSA ERP, available-to-promise (ATP) is part of a more extended framework of order promising techniques called capable-to-promise (CTP). If an item's ATP is insufficient, CTP goes beyond ATP in that it also considers the possibility of producing more than was initially planned.</Paragraph>
			<Paragraph>In addition to the standard ATP functionality, SSA ERP also uses channel ATP. This term refers to the availability of an item for a certain sales channel, taking into account the sales limits for that channel.</Paragraph>
			<Paragraph>For all other types of order promising functionality used in SSA ERP, the term CTP is used.</Paragraph>
			<Paragraph>Acronym: ATP</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000029" Version="B60adoc1" ContextApps="cp"><Term>capable-to-promise</Term>
		<Definition>The combination of techniques used to determine the quantity of an item that you can promise to a customer on a specific date.</Definition>
		<SimpleSection><Paragraph>Capable-to-promise (CTP) involves an extension of the standard available-to-promise (ATP) functionality. CTP goes beyond ATP in that it also considers the possibility of producing more than was initially planned, when an item's ATP is insufficient.</Paragraph>
			<List><ListIntro>In addition to the standard ATP functionality, CTP comprises the following techniques:</ListIntro>
				<ListItem>Channel ATP: restricted availability for a certain sales channel</ListItem>
				<ListItem>Product family CTP: order promising on the basis of availability on product family level rather than on item level</ListItem>
				<ListItem>Component CTP: check if there are enough components available to produce an extra quantity of an item</ListItem>
				<ListItem>Capacity CTP: check if there is enough capacity available to produce an extra quantity of an item</ListItem>
			</List>
			<Paragraph>Synonym: CTP</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000092" Version="B60adoc1" ContextApps="cp"><Term>capacity CTP</Term>
		<Definition>The capacity of a resource that is available in a plan period for additional production of a plan item in connection with a customer order.</Definition>
		<SimpleSection><Paragraph>The capacity CTP is used in capable-to-promise calculations.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000034" Version="B60adoc1" ContextApps="cp"><Term>capacity CTP check</Term>
		<Definition>An availability check on the capacity necessary to produce an extra quantity of an item to deliver a customer order on time.</Definition>
		<SimpleSection><Paragraph>The capacity CTP check is performed on resources in the item's bill of critical capacities or on the work centers of the item's routing, depending on the order horizon. Only the resources defined as CTP critical are checked.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000041" Version="B60adoc1" ContextApps="cp"><Term>capacity CTP reservation</Term>
		<Definition>Resource capacity reserved for the (as yet unplanned) production of items for which the demand could not be covered by the ATP of the items themselves.</Definition>
		<SimpleSection><List><ListIntro>This reservation is made in the following situation:</ListIntro>
				<ListItem>There is a demand for item A that cannot be covered by this item's ATP.</ListItem>
				<ListItem>A capacity CTP check is carried out for item A.</ListItem>
				<ListItem>The bill of critical capacities for item A contains resource R.</ListItem>
				<ListItem>Resource R is defined as CTP critical.</ListItem>
				<ListItem>The capacity CTP of resource R is higher than zero.</ListItem>
			</List>
			<Paragraph>If the demand for item A is recorded as a customer order, a capacity CTP reservation is recorded for resource R, and the resource's capacity CTP is reduced accordingly.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000111" Version="B60adoc1" ContextApps="cp"><Term>capacity utilization</Term>
		<Definition>The number of hours that a resource is used for production.</Definition>
		<SimpleSection><Paragraph>Alternatively, a percentage indicating the capacity use as a proportion of the total available capacity.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000037" Version="B60adoc1" ContextApps="cp"><Term>channel ATP</Term>
		<Definition>The item quantity that can still be promised to customers in a particular sales channel.</Definition>
		<SimpleSection><Paragraph>The channel ATP depends on the allowed demand for a channel. The total allowed demand for one channel ATP period forms the initial value of the channel ATP in that period. Every time a demand is recorded within this channel and within this channel ATP period, this demand is subtracted from the channel ATP.</Paragraph>
			<Paragraph>Channel ATP is used to limit the supply that goes to specific channels, and to secure that enough quantity is left to supply other important customers.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000076" Version="B60adoc1" ContextApps="cp"><Term>channel ATP check</Term>
		<Definition>A check on the quantity that can be promised to a customer based on the allowed demand for the channel to which the customer belongs.</Definition>
		<SimpleSection><Paragraph>Note that the main purpose of channel ATP is to reserve a certain quantity of the product for other channels, for example, for strategic reasons.</Paragraph>
		</SimpleSection>
		<ExampleSection><SectionTitle>Example</SectionTitle>
			<Paragraph>A customer belongs to the direct marketing sales channel. The allowed demand for this channel is 50,000 piece per period. A quantity can be promised to the customer, as long as the total sales volume for that channel in that period does not exceed 50,000.</Paragraph>
		</ExampleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000020" Version="B60adoc1" ContextApps="cp"><Term>channel master plan</Term>
		<Definition>An item-specific logistic plan that contains sales targets and constraints for a specific combination of a sales channel and plan item.</Definition>
		<SimpleSection><Paragraph>A channel is a grouping of customers and items.</Paragraph>
			<Paragraph>A channel master plan supports sales-related functions such as demand forecasting and due-date quoting, as well as aggregation.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000081" Version="B60adoc1" ContextApps="cp" Expired="Yes"><Term>class</Term>
		<Definition>A feature or a group of features of items.</Definition>
		<SimpleSection><Paragraph>Classes offer a method to group items. For example, when the color of items is an important feature for planning a certain resource, you can define a color class.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000084" Version="B60adoc1" ContextApps="cp" Expired="Yes"><Term>class value</Term>
		<Definition>A particular instance of a class feature.</Definition>
		<ExampleSection><SectionTitle>Example</SectionTitle>
			<Paragraph>Class: color Class values: red, blue, white</Paragraph>
		</ExampleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000315" Version="B60adoc1" ContextApps="cp"><Term>cluster</Term>
		<Definition>In <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef>, a grouping of warehouses connected to each other by supplying relationships.</Definition>
		<SimpleSection><Paragraph>A cluster represents a geographical location that consists of one or more warehouses. <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef> considers these warehouses as one unit for planning purposes.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000410" Version="B60adoc1" ContextApps="cp" Expired="Yes"><Term>cluster</Term>
		<Definition>In <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef>, a grouping of warehouses connected to each other by supplying relationships.</Definition>
		<SimpleSection><Paragraph>A cluster represents a geographical location that consists of one or more warehouses. <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef> considers these warehouses as one unit for planning purposes.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000054" Version="B60adoc1" ContextApps="cp"><Term>clustered item</Term>
		<Definition>A plan item in <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef> that is linked to a particular warehouse cluster. The inventory data for a clustered item represents only the quantities related to that specific cluster.</Definition>
		<SimpleSection><Paragraph>In the item code of a clustered item, the cluster segment contains the code of the cluster.</Paragraph>
			<Paragraph>You can use clustered items to model distribution planning within a site or between sites.</Paragraph>
			<Paragraph>The planning methods in <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef> use the total inventory of a clustered item in all warehouses in the cluster. Note that a cluster can also contain just one warehouse.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000035" Version="B60adoc1" ContextApps="cp"><Term>component CTP check</Term>
		<Definition>An availability check on the components necessary to produce an extra quantity of an item to deliver a customer order on time.</Definition>
		<SimpleSection><Paragraph>The type of check that is performed on a component item itself depends on the CTP parameters for the component in question.</Paragraph>
			<Paragraph>The component CTP check is performed on components in the bill of critical materials or the bill of material, depending on the order horizon. Only components defined as CTP critical are checked.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000042" Version="B60adoc1" ContextApps="cp"><Term>component CTP reservation</Term>
		<Definition>The item quantity reserved to be used as critical components for the (as yet unplanned) production of other items.</Definition>
		<SimpleSection><List><ListIntro>This reservation is made when the ATP data in an item master plan is updated and the following is true:</ListIntro>
				<ListItem>The cumulative ATP for plan item A drops below zero.</ListItem>
				<ListItem>The plan item settings for item A are set to enable component CTP checks.</ListItem>
				<ListItem>The bill of critical material for item A contains item B.</ListItem>
				<ListItem>Item B is defined as CTP critical in the plan item settings.</ListItem>
			</List>
			<Paragraph>In this case, a component CTP reservation is recorded for item B, and the ATP of item B is reduced accordingly. The quantity of item A that will be produced with the reserved quantity of the component is stored as CTP Reservation Receipts.</Paragraph>
		</SimpleSection>
		<Note><SectionTitle>Note</SectionTitle>
			<Paragraph>To guarantee that SSA ERP can carry out an ATP check correctly, you must fill the Warehouse field in the <GUIRef href="/baanerp/cp/rpd/cprpd3120m000" role="session">Bill of Critical Materials (cprpd3120m000)</GUIRef> session. Common Data explodes the ATP of a main item to plan items that have the same cluster as the warehouse you specified on the bill of critical materials of the main item.</Paragraph>
		</Note>
	</GlossaryEntry>
	<GlossaryEntry ID="000072" Version="B60adoc1" ContextApps="cp"><Term>consumed demand forecast</Term>
		<Definition>The part of the demand plan that has been consumed by the actual demand in a specific period.</Definition>
		<SimpleSection><Paragraph>As a rule, the demand forecast, extra demand, and special demand are gradually filled by actual orders. This process is referred to as consumption of forecast demand by actual demand.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000097" Version="B60adoc1" ContextApps="cp"><Term>critical capacity requirements</Term>
		<Definition>The production capacity of a resource, required by a plan item for the execution of that plan item's production plan.</Definition>
		<SimpleSection><Paragraph>The critical capacity requirements are based on a plan item's bill of critical capacities.</Paragraph>
			<Paragraph>The critical capacity requirements are specified by plan period.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000039" Version="B60adoc1" ContextApps="cp"><Term>critical in CTP</Term>
		<Definition>A plan item that is critical in CTP must be checked during a component CTP check for a higher level item in the bill of critical materials. A resource that is critical in CTP must be checked during a capacity CTP check for a plan item, if this resource is included in the plan item's bill of critical capacities.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000130" Version="B60adoc1" ContextApps="cp"><Term>critical material requirements</Term>
		<Definition>The quantity of a plan item that is required to serve as critical components for the production of another plan item.</Definition>
		<SimpleSection><Paragraph>The critical material requirements are based on the production plan for an (end) item, and on its bill of critical materials.</Paragraph>
			<Paragraph>The critical material requirements are specified by plan period. In the item master plan, critical material requirements are recorded as dependent material demand.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000038" Version="B60adoc1" ContextApps="cp"><Term>CTP time fence</Term>
		<Definition>The number of working days from the current moment, during which SSA ERP does not perform CTP checks.</Definition>
		<SimpleSection><Paragraph>The CTP time fence must be smaller than the ATP/CTP horizon.</Paragraph>
			<Paragraph>Durign the period of the CTP time fence, CTP is considered to be zero.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000040" Version="B60adoc1" ContextApps="cp"><Term>cumulative ATP</Term>
		<Definition>The total item quantity that you can promise to deliver in a particular plan period.</Definition>
		<SimpleSection><Paragraph>You can use the cumulative ATP to check the availability of an item when you receive a sales order or an inquiry.</Paragraph>
		</SimpleSection>
		<Note><SectionTitle>Note</SectionTitle>
			<Paragraph>If the item's cumulative ATP is insufficient, SSA ERP can carry out a capacity and/or component CTP check to see if the demand can be met by increasing the production of the item.</Paragraph>
		</Note>
	</GlossaryEntry>
	<GlossaryEntry ID="000091" Version="B60adoc1" ContextApps="cp"><Term>cumulative capacity CTP</Term>
		<Definition>The total resource capacity that is still available for additional production up to and including a particular plan period.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="413" Version="5.2b" ContextApps="cp"><Term>cumulative order lead time</Term>
		<Definition>The total value of the item purchase lead time and the cumulative production lead time of all components.</Definition>
		<SimpleSection><Paragraph>Enterprise Planning uses the cumulative order lead time to determine the minimum value of the planning horizon.</Paragraph>
		</SimpleSection>
		<Acronym>COLT</Acronym>
	</GlossaryEntry>
	<GlossaryEntry ID="000113" Version="B60adoc1" ContextApps="cp"><Term>customer deliveries</Term>
		<Definition>The sales order quantities and the sales schedule quantities that have already been delivered to the customers involved.</Definition>
		<SimpleSection><Paragraph>The customer deliveries are part of the actual demand. These deliveries are used to consume the demand forecast, and to generate a new demand forecast.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000112" Version="B60adoc1" ContextApps="cp"><Term>customer orders</Term>
		<Definition>The sales orders that have not yet been delivered to the customers involved.</Definition>
		<SimpleSection><Paragraph>The customer orders are part of the actual demand and are used to consume the demand forecast.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000307" Version="B60adoc1" ContextApps="cp" Expired="Yes"><Term>cycle number</Term>
		<Definition>A number that SSA ERP assigns to each individual cycle you enter for a specified resource. SSA ERP numbers the cycles in order of date.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000031" Version="B60adoc1" ContextApps="cp"><Term>delivery schedule</Term>
		<Definition>The dates and quantities of an item that can be promised to a customer.</Definition>
		<SimpleSection><Paragraph>With this report you can determine how much volume can be delivered on time and how much is delivered late.</Paragraph>
			<Paragraph>According to the item master plan, more chairs will be completed later that month. Some of those newly produced chairs have already been promised to other customers.</Paragraph>
		</SimpleSection>
		<ExampleSection><SectionTitle>Example</SectionTitle>
			<Paragraph>A customer wants to order 80 office chairs, to be delivered on May 1. However, the CTP quantity on that day is only 30 chairs.</Paragraph>
		</ExampleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000015" Version="B60adoc1" ContextApps="cp"><Term>demand forecast</Term>
		<Definition>The item quantity that is forecast to be sold in a plan period, on the basis of seasonal patterns and/or historical demand data.</Definition>
		<SimpleSection><Paragraph>The demand forecast is part of the demand plan for a plan item or channel.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000009" Version="B60adoc1" ContextApps="cp"><Term>demand plan</Term>
		<Definition>The expected demand for an item, specified by period.</Definition>
		<SimpleSection><List><ListIntro>The demand plan is the sum of</ListIntro>
				<ListItem>Demand forecast</ListItem>
				<ListItem>Extra demand</ListItem>
				<ListItem>Special demand</ListItem>
			</List>
			<Paragraph>The demand plan belongs to the master plan for an item or channel.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000074" Version="B60adoc1" ContextApps="cp"><Term>dependent demand</Term>
		<Definition>A demand related to a demand for another item.</Definition>
		<SimpleSection><List><ListIntro>Two basic types of dependent demand exist:</ListIntro>
				<ListItem>Demand for components that are used to manufacture an item.</ListItem>
				<ListItem>Demand that originates from another warehouse location or a related site.</ListItem>
			</List>
			<Paragraph>The dependent demand is equal to the sum of the following fields:</Paragraph>
			<List><ListItem>Dependent material demand</ListItem>
				<ListItem>Dependent Scheduled Demand</ListItem>
				<ListItem>Dependent Distribution Demand</ListItem>
			</List>
			<Paragraph><GUIRef href="/baanerp/tc" role="package">Common Data</GUIRef> explodes the ATP and the Dependent Demand of a main item to plan items that have the same cluster as the warehouse you specified on the bill of critical materials of the main item.</Paragraph>
		</SimpleSection>
		<Note><SectionTitle>Note</SectionTitle>
			<Paragraph>In <GUIRef href="/baanerp/tc" role="package">Common Data</GUIRef> you must specify a warehouse on the BCM line in the Bill of Critical Materials (cprpd3120m000) session to guarantee that the dependent demand explosions for a plan item are allocated to the correct warehouse and plan item.</Paragraph>
		</Note>
	</GlossaryEntry>
	<GlossaryEntry ID="000121" Version="B60adoc1" ContextApps="cp"><Term>dependent distribution demand</Term>
		<Definition>Demand that comprises the following:</Definition>
		<SimpleSection><List><ListItem>Demand arising when, at another warehouse location within the same plan site, or at a related plan site, a planned distribution order is generated.</ListItem>
				<ListItem>Demand which has the form of a customer order, and which is related to a multisite requirement from another site. The customer order in question is generated when, at the other site, a planned distribution order is transferred to the execution level.</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000119" Version="B60adoc1" ContextApps="cp"><Term>dependent material demand</Term>
		<Definition>Demand for an item that results from the explosion of requirements of a production plan or a planned production order for another item.</Definition>
		<SimpleSection><Paragraph>In other words, when requirements for an item's production plan or planned production orders are exploded, this leads to dependent material demand for items that occur in the former item's bill of (critical) material.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000120" Version="B60adoc1" ContextApps="cp"><Term>dependent scheduled demand</Term>
		<Definition>Demand that comprises the following:</Definition>
		<SimpleSection><List><ListItem>Demand for an item resulting from the explosion of requirements of a production order for another item. In other words, when requirements for a shop-floor order for an item are exploded, this leads to dependent scheduled demand for the estimated materials of the shop-floor order.</ListItem>
				<ListItem>Demand for an item in the form of a warehousing order (transfer order) from another warehouse location within your site. In other words, when at the other location a planned distribution order is transferred to the execution level, this leads to dependent scheduled demand in your item's master plan.</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000126" Version="B60adoc1" ContextApps="cp"><Term>distribution deliveries</Term>
		<Definition>The quantity that has been delivered to other sites to meet dependent distribution demand.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000300" Version="B60adoc1" ContextApps="cp"><Term>distribution plan</Term>
		<Definition>The item quantity that is planned to be delivered by internal or sister-company suppliers. These planned deliveries are shown in the item master plan as planned distribution orders (outside the order horizon).</Definition>
		<SimpleSection><Paragraph>The distribution plan belongs to the supply plan for a plan item.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000028" Version="B60adoc1" ContextApps="cp" Expired="Yes"><Term>due date quoting (DDQ)</Term>
		<Definition>The process of calculating and reporting the date that an item can be delivered.</Definition>
		<SimpleSection><Paragraph>If the customer-order quantity exceeds the available quantity on the desired date, SSA ERP can generate a delivery schedule.</Paragraph>
			<Paragraph>SSA ERP can also report the reasons for failing to deliver the item on time, for example shortage of a component.</Paragraph>
			<Paragraph>Due-date quoting is closely related to concepts like order promising, available-to-promise (ATP), and capable-to-promise (CTP).</Paragraph>
			<Paragraph>Synonym: DDQ</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000368" Version="B60adoc1" ContextApps="cp"><Term>efficiency factor</Term>
		<Definition>efficiency factor</Definition>
		<SimpleSection><Paragraph>A variable that SSA ERP uses to take into account differences in the productivity when, for example, working overtime, hiring extra man craft, or working in different shifts. Efficiency factors impact on lead-time calculation in <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef>.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000026" Version="B60adoc1" ContextApps="cp"><Term>enterprise resources planning</Term>
		<Definition>An information-processing system to control the production and distribution of goods, including financial accounting.</Definition>
		<SimpleSection><Paragraph>Synonym: ERP</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000027" Version="B60adoc1" ContextApps="cp"><Term>execution level</Term>
		<Definition>Within <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef>, the designation of the SSA ERP packages that control the execution of orders and the actual goods flow, such as:</Definition>
		<SimpleSection><List><ListItem><GUIRef href="/baanerp/ti" role="package">Manufacturing</GUIRef>
				</ListItem>
				<ListItem><GUIRef href="/baanerp/td" role="package">Order Management</GUIRef>
				</ListItem>
				<ListItem><GUIRef href="/baanerp/wh" role="package">Warehouse Management</GUIRef>
				</ListItem>
			</List>
		</SimpleSection>
		<SimpleSection><Paragraph><GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef> uses planning algorithms to carry out simulations and optimizations. The other packages control the execution of orders, and the goods flow.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000016" Version="B60adoc1" ContextApps="cp"><Term>extra demand</Term>
		<Definition>An extra item quantity that is expected to be sold in a plan period, on top of the regular demand forecast.</Definition>
		<SimpleSection><Paragraph>The extra demand is part of the demand plan for a plan item or channel.</Paragraph>
		</SimpleSection>
		<ExampleSection><SectionTitle>Example</SectionTitle>
			<Paragraph>An extra demand can be defined for an unusual large customer order or an extra market demand because of sales promotions.</Paragraph>
		</ExampleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000056" Version="B60adoc1" ContextApps="cp"><Term>extra lead time</Term>
		<Definition>Time reserved for extra activities that are necessary to fully complete a planned order.</Definition>
		<SimpleSection><Paragraph><GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef> treats the extra lead time in the same way as the safety time: the order must be delivered earlier based on the extra lead time.</Paragraph>
			<Paragraph>The extra lead time is expressed in days or in hours.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000032" Version="B60adoc1" ContextApps="cp"><Term>family CTP check</Term>
		<Definition>A CTP check that is carried out at a higher product-family level, instead of the level of the item itself.</Definition>
		<SimpleSection><Paragraph>Like the regular CTP check for an item, a family CTP check can involve several types of ATP and CTP checks.</Paragraph>
			<Paragraph>In this case, you can configure SSA ERP so that, when the CTP of the mountain bike must be checked, SSA ERP will in fact check the CTP of the bicycle family.</Paragraph>
		</SimpleSection>
		<ExampleSection><SectionTitle>Example</SectionTitle>
			<Paragraph>The mountain-bike item is part of the bicycle family.</Paragraph>
		</ExampleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000033" Version="B60adoc1" ContextApps="cp"><Term>family CTP horizon</Term>
		<Definition>The time period for which SSA ERP performs the capable-to-promise (CTP) check for an item on a higher product-family level, instead of the level of the item itself.</Definition>
		<SimpleSection><Paragraph>The start date of the family CTP horizon is defined in the plan-item settings. The end date coincides with the CTP time fence.</Paragraph>
			<List><ListIntro>The application of family CTP depends on the plan period in which the delivery date of a customer order falls:</ListIntro>
				<ListItem>If the plan period falls before the family CTP horizon, SSA ERP checks the CTP of the item itself.</ListItem>
				<ListItem>If the plan period falls within the family CTP horizon, SSA ERP checks the CTP on a higher product-family level.</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="411" Version="5.2a" ContextApps="cp"><Term>family item</Term>
		<Definition>A product family of an item that represents a group of similar plan items (or families). The items are aggregated to the level of the family item to give a more general plan than the one devised for individual items.</Definition>
		<SimpleSection><Paragraph>The aggregation relationships specify the percentage of each plan item in the product family.</Paragraph>
		</SimpleSection>
		<Synonym>product family</Synonym>
	</GlossaryEntry>
	<GlossaryEntry ID="000077" Version="B60adoc1" ContextApps="cp"><Term>family site</Term>
		<Definition>The logistic company in which an item family has been defined.</Definition>
		<SimpleSection><Paragraph>The family site makes it possible to redirect CTP checks to a central logistic company.</Paragraph>
			<Paragraph>When a customer order is received, the CTP is checked at the family level in the central site.</Paragraph>
		</SimpleSection>
		<ExampleSection><SectionTitle>Example</SectionTitle>
			<Paragraph>A large manufacturer of sports articles produces baseball bats in several states. A central master plan is maintained at headquarters (the central site). Each site has the bat defined as an item, and aggregation relationships have been set up to a product family of baseball bats at the central site.</Paragraph>
		</ExampleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000100" Version="B60adoc1" ContextApps="cp"><Term>firm-planned order</Term>
		<Definition>A planned order that can no longer be modified by <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef> in an order-planning run. However, you can manually change a firm-planned order's start date and finish date, or the order quantity.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000306" Version="B60adoc1" ContextApps="cp"><Term>fixed delivery code</Term>
		<Definition>In <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef> a code that is used for order planning on the basis of fixed delivery moments.</Definition>
		<SimpleSection><Paragraph>For each fixed delivery code you can specify delivery moments in the <GUIRef href="/baanerp/cp/rpd/cprpd2120m000" role="session">Fixed Deliveries (cprpd2120m000)</GUIRef> session. In the <GUIRef href="/baanerp/cp/rpd/cprpd2220m100" role="session">Add Delivery Pattern (cprpd2220m100)</GUIRef> session you can also add delivery moments from a specific delivery pattern.</Paragraph>
			<Paragraph>For each plan item you can select the appropriate fixed delivery code.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="416" Version="5.2b" ContextApps="tt"><Term>fixed delivery moment</Term>
		<Definition>A specific date and time that you define as a firm and unchangeable time point on which goods must be delivered to you.</Definition>
		<SimpleSection><Paragraph>If you defined fixed delivery moments for a plan item, SSA ERP sets the unconstrained planned finish date back to the nearest fixed delivery moment.</Paragraph>
			<Paragraph>You can define incidental fixed delivery moments, or define a pattern of recurrring fixed delivery moments.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="417" Version="5.2b" ContextApps="tt"><Term>fixed delivery pattern</Term>
		<Definition>A schedule of recurring fixed delivery moments.</Definition>
		<SimpleSection><Paragraph>Enterprise Planning uses calendar recurrences to create fixed delivery patterns.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000057" Version="B60adoc1" ContextApps="cp"><Term>fixed lead time</Term>
		<Definition>The estimated time necessary to carry out a planned order.</Definition>
		<SimpleSection><Paragraph>To plan an order's lead time, <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef> can either use a fixed lead time or more detailed routing data. When using a fixed lead time, the results are less precise, but the calculation is faster.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000058" Version="B60adoc1" ContextApps="cp"><Term>fixed lead-time horizon</Term>
		<Definition>The time period for which <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef> uses a fixed lead time to plan orders.</Definition>
		<SimpleSection><Paragraph>Planning with a fixed lead time is faster than planning on the basis of routing data, but the results are less precise.</Paragraph>
			<Paragraph>The start date of the fixed lead-time horizon is defined in the plan-item settings. The end date coincides with the end of the order horizon.</Paragraph>
			<Paragraph>Before the fixed lead-time horizon, <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef> plans on the basis of routing data. Within the fixed lead-time horizon, Enterprise Planning plans using a fixed lead time.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000068" Version="B60adoc1" ContextApps="cp"><Term>forecast horizon</Term>
		<Definition>The number of days into the future on which the calculation of the inventory plan is based.</Definition>
		<SimpleSection><Paragraph>The forecast horizon is expressed as a number of calendar days.</Paragraph>
			<Paragraph>The forecast-based calculation of the inventory plan is based on the following principle: The inventory plan must be equal to the expected demand during a certain forecast horizon.</Paragraph>
		</SimpleSection>
		<ExampleSection><SectionTitle>Example</SectionTitle>
			<Paragraph>If the forecast horizon is 10 days, SSA ERP aims at an inventory level for each plan period that is sufficient to cover the demand for the next 10 days.</Paragraph>
		</ExampleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000067" Version="B60adoc1" ContextApps="cp"><Term>forecast time fence</Term>
		<Definition>The date up until which Enterprise Planning ignores the demand forecast when generating master plans and planned orders.</Definition>
		<SimpleSection><Paragraph>The forecast time fence is expressed as a number of working days from the date you carry out the simulation.</Paragraph>
			<Paragraph>In the forecast time fence, Enterprise Planning only considers actual customer orders. Beyond the forecast time fence, total demand is a combination of actual orders and forecasts.</Paragraph>
			<Paragraph>A reasonable value for the forecast time fence is the minimum time period between the receipt of customer orders and the requested delivery dates.</Paragraph>
			<Paragraph>To calculate the forecast time fence, <GUIRef href="/baanerp/tc" role="package">Common Data</GUIRef> uses the calendar that you specified for the enterprise unit of the default warehouse to which the plan item belongs.</Paragraph>
			<Paragraph>If you did not specify an enterprise unit for the default warehouse of the plan item, Enterprise Planning uses the company calendar to calculate the forecast time fence.</Paragraph>
		</SimpleSection>
		<Note><SectionTitle>Note</SectionTitle>
			<Paragraph><GUIRef href="/baanerp/tc" role="package">Common Data</GUIRef> moves the forecast time fence towards the end of the plan period in which the time fence falls, because Enterprise Planning must know whether a plan period falls in or out of the forecast time fence.</Paragraph>
		</Note>
	</GlossaryEntry>
	<GlossaryEntry ID="000044" Version="B60adoc1" ContextApps="cp"><Term>goods flow</Term>
		<Definition>A collective term for all transactions that influence the inventory of items, such as customer orders, production orders, and inventory adjustments.</Definition>
		<SimpleSection><Paragraph>Goods-flow data is recorded at the execution level of SSA ERP. When the goods-flow data in <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef> is updated, this data is loaded into <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef> as a basis for the planning. This data includes both historical and planned goods-flow transactions, as well as current inventory data.</Paragraph>
			<Paragraph>For product families, SSA ERP generates the goods-flow data by aggregation through the aggregation relationships.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000075" Version="B60adoc1" ContextApps="cp"><Term>independent demand</Term>
		<Definition>A demand that is unrelated to demand for other items.</Definition>
		<SimpleSection><List><ListIntro>Examples of independent demand:</ListIntro>
				<ListItem>Demand for finished goods.</ListItem>
				<ListItem>Demand for components required for destructive testing.</ListItem>
				<ListItem>Service part requirements.</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000131" Version="B60adoc1" ContextApps="cp"><Term>infinite planning</Term>
		<Definition>A supply-planning method that does not take any capacity constraints or material constraints into account.</Definition>
		<SimpleSection><Paragraph>Infinite planning starts from the assumption that there are no critical constraints. In other words, it assumes that it is always possible to find or arrange the necessary resource capacity and the necessary materials to produce an item.</Paragraph>
			<Paragraph>Infinite planning is especially suitable in situations in which it is no problem to flexibly add resource capacity, and in which the supply of components is easy.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000090" Version="B60adoc1" ContextApps="cp" Expired="Yes"><Term>inheritance</Term>
		<Definition>The ability to derive certain features from other plan items through inheritance relationships. These features are determined by the classes to which a plan item belongs.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000125" Version="B60adoc1" ContextApps="cp"><Term>internal deliveries</Term>
		<Definition>The quantity that has been delivered internally, that is, within the same site, to meet dependent demand.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000011" Version="B60adoc1" ContextApps="cp"><Term>inventory plan</Term>
		<Definition>The desired inventory level, specified by period.</Definition>
		<SimpleSection><Paragraph>The inventory plan is part of the item master plan.</Paragraph>
			<Paragraph>The inventory plan can also be a constant inventory level.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000019" Version="B60adoc1" ContextApps="cp"><Term>item master plan</Term>
		<Definition>An item-specific, overall logistic plan that contains planning data and logistic targets for sales, internal and external supply, and inventory. All planning data in the item master plan is specified by plan period. <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef> uses this data to carry out master-planning simulations.</Definition>
		<SimpleSection><List><ListIntro>Within the item master plan, you can distinguish the following subplans:</ListIntro>
				<ListItem>Demand plan</ListItem>
				<ListItem>Supply plan</ListItem>
				<ListItem>Inventory plan</ListItem>
			</List>
			<Paragraph>In addition, an item's master plan contains information about actual demand, actual supply, planned supply in the form of planned orders, and expected inventory.</Paragraph>
			<Paragraph>If an item has a master plan and channels have been defined for this item, each channel usually has its own channel master plan. A channel master plan contains channel-specific information only, that is, demand data and information about sales restrictions.</Paragraph>
			<Paragraph>Item master plans and channel master plans are defined within the context of a scenario. These scenarios can be used for what-if analyses. One of the scenarios is the actual plan.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000370" Version="B60adoc1" ContextApps="cp"><Term>item order plan</Term>
		<Definition>item order plan</Definition>
		<SimpleSection><Paragraph>A time-phased overview of your order planning.</Paragraph>
			<Paragraph>The item order plan contains overview values for demand and forecast on one hand, and the other hand it provides information about scheduled receipts (actual orders) and planned supply (planned orders).</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000372" Version="B60adoc1" ContextApps="cp"><Term>iteration</Term>
		<Definition>iteration</Definition>
		<SimpleSection><Paragraph>A master planning method used by the workload-control planning engine to take into account material constraints and pass them on from the lower to the higher levels in the bill of critical materials (BCM).</Paragraph>
			<List><ListIntro>An iteration consists of:</ListIntro>
				<ListItem>A reverse planning pass during which SSA ERP plans items in order of decreasing phase number (first the components and than the end item).</ListItem>
				<ListItem>A normal planning run during which items are planned in order of increasing phase number, to recompute the consequences of material constraints for all parts of the BCM structure.</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000305" Version="B60adoc1" ContextApps="cp"><Term>line assembly configuration (LAC)</Term>
		<Definition>A planning product for assembly-driven manufacturers, for example, the automotive industry. The main functionality of LAC is assembly line planning for generic FAS items.</Definition>
		<SimpleSection><Paragraph>In LAC, a fast MRP engine calculates the requirements for assembly parts that must be supplied to the assembly line. The planning of the assembly parts themselves is carried out by <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef>. LAC calculates the requirements, based on forecast and actual sales orders, and replicates the requirements to <Link href="/baanerp/cp/onlinemanual/cp" role="package">Enterprise Planning</Link>.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000059" Version="B60adoc1" ContextApps="cp"><Term>master-based planning</Term>
		<Definition>A planning concept in which all planning data is accumulated into time buckets with predefined lengths.</Definition>
		<SimpleSection><Paragraph>In master planning, all demand, supply, and inventory data is handled in terms of these time buckets, and is stored in master plans.</Paragraph>
			<Paragraph>In master planning, supply is planned in the form of a supply plan. This supply plan is calculated on the basis of demand forecasts, actual orders, and other information. For production planning, this planning method only considers critical requirements, as recorded in an item's bill of critical materials and bill of critical capacities.</Paragraph>
		</SimpleSection>
		<Note><SectionTitle>Note</SectionTitle>
			<Paragraph>In <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef>, you can maintain a master plan for an item, even if you plan all supply with order planning.</Paragraph>
		</Note>
	</GlossaryEntry>
	<GlossaryEntry ID="000061" Version="B60adoc1" ContextApps="cp"><Term>master-planning engine</Term>
		<Definition>The planning algorithm used in master planning to plan supply.</Definition>
		<SimpleSection><Paragraph>The master-planning engine generates a supply plan for each item involved.</Paragraph>
			<List><ListIntro>The following master-planning engines are available:</ListIntro>
				<ListItem><GUIRef href="/baanerp/cp/domains/rpd.plme#infinitplanning" role="enum">Infinite Planning</GUIRef>
				</ListItem>
				<ListItem><GUIRef href="/baanerp/cp/domains/rpd.plme#workloadcontrol" role="enum">Workload Control</GUIRef>
				</ListItem>
			</List>
			<Paragraph>For each plan unit, you can choose the appropriate planning engine. If an item has not been assigned to a plan unit, infinite planning is used by default.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000303" Version="B60adoc1" ContextApps="cp"><Term>master-planning horizon</Term>
		<Definition>That part of the planning horizon which falls outside the order horizon, and for which <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef> uses master planning to plan supply.</Definition>
		<SimpleSection><Paragraph>The master-planning horizon is not defined on its own, but depends on the definition of the order horizon and the planning horizon.</Paragraph>
			<Paragraph>If the order horizon coincides with the planning horizon, there is no master horizon. In this case, <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef> plans all supply with order planning.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000405" Version="B60adoc1" ContextApps="cp"><Term>minimum cost price</Term>
		<Definition>minimum cost price</Definition>
		<SimpleSection><Paragraph>A price limit that you can define for a signal type in Enterprise Planning.</Paragraph>
			<Paragraph>If you define a minimum cost price for a certain signal type, Enterprise Planning does not generate the corresponding signal for items that cost less than the minimum cost price.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000304" Version="B60adoc1" ContextApps="cp"><Term>multicompany distribution order</Term>
		<Definition>A distribution order in which two separate logistical companies are involved.</Definition>
		<SimpleSection><Paragraph>In SSA ERP, the user can determine if the multicompany planned distribution must be tranferred to either a purchase order, or a warehouse transfer. To do so, the user must define the order type for a specific company relation.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000079" Version="B60adoc1" ContextApps="cp"><Term>net change date</Term>
		<Definition>The date on which something changes that affects the current master plan or the current planned orders. For example, a higher demand or a change in a BOM.</Definition>
		<SimpleSection><Paragraph>When a net-change simulation is performed, then items are selected based on the net-change date and flag. For example, when the flag is set and the date is outside the order horizon, then the item is skipped.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000078" Version="B60adoc1" ContextApps="cp"><Term>net-change simulation</Term>
		<Definition>A recalculation of planned orders or a master plan that starts at the earliest change in the planning data since the last simulation.</Definition>
		<SimpleSection><Paragraph>Antonym: Regeneration</Paragraph>
		</SimpleSection>
		<Note><SectionTitle>Note</SectionTitle>
			<Paragraph>Net-changes simulations are only used for the actual scenario. For other scenarios, <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef> always performs a full regeneration of the master plan or the order planning.</Paragraph>
		</Note>
	</GlossaryEntry>
	<GlossaryEntry ID="000301" Version="B60adoc1" ContextApps="cp"><Term>nettable warehouse</Term>
		<Definition>A warehouse that is usually provisioned by production or purchase.</Definition>
		<SimpleSection><Paragraph>The distinction nettable-nonnettable is not used anymore in the current version.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000055" Version="B60adoc1" ContextApps="cp"><Term>nonclustered item</Term>
		<Definition>A plan item in <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef> that is planned without referring to a particular warehouse cluster.</Definition>
		<SimpleSection><Paragraph>In the item code of a nonclustered item, the cluster segment is empty.</Paragraph>
			<Paragraph>If clustered items exist that have the same item-base segment as the nonclustered item, these items are physically identical, but the inventory data differs (for example, the quantity on hand). The inventory data for a nonclustered item does not include the quantities related to specific clusters. You can use clustered items to model distribution planning within a site or between sites.</Paragraph>
			<Paragraph>If SSA ERP is installed without cluster segments, all plan items are nonclustered items.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000043" Version="B60adoc1" ContextApps="cp"><Term>nonconsumed demand forecast</Term>
		<Definition>The part of the forecast demand that has not yet been consumed by actual demand.</Definition>
		<SimpleSection><Paragraph>As a rule, the demand forecast, extra demand, and special demand are gradually filled by actual orders. This process is referred to as consumption of forecast demand by actual demand.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="414" Version="5.2b" ContextApps="cp"><Term>noncritical cumulative order lead time</Term>
		<Definition>The total value of the item purchase lead time and the cumulative production lead time of all noncritical components.</Definition>
		<SimpleSection><Paragraph>Enterprise Planning uses the noncritical cumulative order lead time to determine the minimum value of the order horizon.</Paragraph>
		</SimpleSection>
		<Acronym>noncritical COLT</Acronym>
	</GlossaryEntry>
	<GlossaryEntry ID="000302" Version="B60adoc1" ContextApps="cp"><Term>nonnettable warehouse</Term>
		<Definition>A warehouse that is usually provisioned by distribution, that is, by other warehouses at the same site or at a related site.</Definition>
		<SimpleSection><Paragraph>The distinction nettable-nonnettable is not used anymore in the current version.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000310" Version="B60adoc1" ContextApps="cp"><Term>operation storage horizon</Term>
		<Definition>The number of future working days for which SSA ERP stores the operations for planned orders.</Definition>
		<SimpleSection><Paragraph>For planned orders beyond the operation storage horizon, you cannot analyze the capacity use of planned orders and you cannot transfer the planned orders to the execution level.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000401" Version="B60adoc1" ContextApps="cp"><Term>order group</Term>
		<Definition>A collection of planned production orders, which you can use as a selection criterion to transfer planned production orders from Enterprise Planning to the Shop Floor Control (SFC) module of Manufacturing.</Definition>
		<SimpleSection><Paragraph>SFC can use the same collection of production orders to organize manufacturing tasks.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000065" Version="B60adoc1" ContextApps="cp"><Term>order horizon</Term>
		<Definition>The time period for which <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef> uses order-based planning to plan supply.</Definition>
		<SimpleSection><Paragraph>The order horizon is expressed as a number of working days from the date you carry out the simulation.</Paragraph>
			<Paragraph>If the order horizon is zero, <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef> does not use order-based planning for the item involved.</Paragraph>
			<Paragraph>To calculate the order horizon, SSA ERP uses the calendar that you specified for the enterprise unit of the default warehouse to which the plan item belongs.</Paragraph>
			<Paragraph>If you did not specify an <Link href="/baanerp/tc/glossary/glossary#000011" role="glossary">enterprise unit</Link> for the default <Link href="/baanerp/tc/glossary/glossary#Warehouse.tc" role="glossary">warehouse</Link> of the plan item, <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef> uses the company calendar to calculate the order horizon.</Paragraph>
		</SimpleSection>
		<Note><SectionTitle>Note</SectionTitle>
			<Paragraph>SSA ERP moves the order horizon towards the end of the <Link href="/baanerp/cp/glossary/glossary#000109" role="glossary">plan</Link> period) in which it falls, because <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef> must know whether a <Link href="/baanerp/cp/glossary/glossary#000109" role="glossary">plan period</Link> falls within the order horizon.</Paragraph>
		</Note>
	</GlossaryEntry>
	<GlossaryEntry ID="000051" Version="B60adoc1" ContextApps="cp"><Term>order status</Term>
		<Definition>The status assigned to a planned order in <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef>.</Definition>
		<SimpleSection><List><ListIntro>The order status can either be:</ListIntro>
				<ListItem><GUIRef href="/baanerp/cp/domains/rrp.osta#planned" role="enum">Planned</GUIRef>
				</ListItem>
				<ListItem><GUIRef href="/baanerp/cp/domains/rrp.osta#firmplanned" role="enum">Firm Planned</GUIRef>
				</ListItem>
				<ListItem><GUIRef href="/baanerp/cp/domains/rrp.osta#confirmed" role="enum">Confirmed</GUIRef>
				</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000060" Version="B60adoc1" ContextApps="cp"><Term>order-based planning</Term>
		<Definition>A planning concept in which planning data is handled in the form of orders.</Definition>
		<SimpleSection><Paragraph>In order planning, supply is planned in the form of planned orders. SSA ERP takes into account the start and finish dates of individual planned orders. For production planning, this method considers all material and capacity requirements, as recorded in an item's BOM and routing.</Paragraph>
		</SimpleSection>
		<Note><SectionTitle>Note</SectionTitle>
			<Paragraph>In <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef>, you can maintain a master plan for an item, even if you plan all supply with order planning.</Paragraph>
		</Note>
	</GlossaryEntry>
	<GlossaryEntry ID="000114" Version="B60adoc1" ContextApps="cp"><Term>performance indicator</Term>
		<Definition>A value that indicates how well a particular aspect of a certain scenario in <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef> performs. This figure concerns a specific resource, a range of resources, a specific plan item, or a range of plan items. The figure involved can represent a quantity, an amount of money, or a percentage.</Definition>
		<SimpleSection><Paragraph>Performance indicators are especially useful to compare different scenarios, resources, or plan items.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000045" Version="B60adoc1" ContextApps="cp"><Term>phase number</Term>
		<Definition>A number that determines the order in which plan units and plan items are planned.</Definition>
		<SimpleSection><Paragraph>As a rule, plan units and plan items are planned in order of increasing phase number: first phase number 0, then phase number 1, and so on.</Paragraph>
			<Paragraph>An item has separate phase numbers for master planning and order planning. For items that belong to a plan unit, the master phase-number equals the plan unit's master phase-number.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000109" Version="B60adoc1" ContextApps="cp"><Term>plan period</Term>
		<Definition>One of a series of time buckets into which all planning data in a master plan is accumulated.</Definition>
		<SimpleSection><Paragraph>Plan periods are defined in the context of a scenario.</Paragraph>
			<Paragraph>Plan periods are identified by a period number, and are defined in days, weeks, or months.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000110" Version="B60adoc1" ContextApps="cp"><Term>plan site</Term>
		<Definition>A business location or logistic organization with its own logistic plan, which is centrally coordinated by a multisite scenario.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000010" Version="B60adoc1" ContextApps="cp"><Term>plan status</Term>
		<Definition>An indication of whether the data in a scenario can still be changed.</Definition>
		<SimpleSection><Paragraph>The plan status can be <GUIRef href="/baanerp/cp/domains/rpd.plst#open" role="enum">Open</GUIRef> or <GUIRef href="/baanerp/cp/domains/rpd.plst#closed" role="enum">Closed</GUIRef>.</Paragraph>
			<Paragraph>When a scenario has the <GUIRef href="/baanerp/cp/domains/rpd.plst#closed" role="enum">Closed</GUIRef> plan status, you can no longer modify it.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000004" Version="B60adoc1" ContextApps="cp"><Term>plan unit</Term>
		<Definition>A group of plan items that is planned as a single unit.</Definition>
		<SimpleSection><Paragraph>A plan unit groups a set of plan items that share the production capacity of certain resources.</Paragraph>
			<Paragraph>A plan unit is planned with a specific planning engine. You can specify a planning method and planning parameters for each plan unit.</Paragraph>
			<Paragraph>A plan unit often corresponds to a production department. Usually, a production system distinguishes no more than three to five plan units.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000049" Version="B60adoc1" ContextApps="cp"><Term>planned distribution order</Term>
		<Definition>An order in <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef> for an internal supplier or sister company to deliver a quantity of an item.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000050" Version="B60adoc1" ContextApps="cp"><Term>planned order</Term>
		<Definition>A supply order in <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef> that is created for planning purposes, but which is not an actual order yet.</Definition>
		<SimpleSection><List><ListIntro><GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef> works with planned orders of the following types:</ListIntro>
				<ListItem>Planned production order</ListItem>
				<ListItem>Planned purchase order</ListItem>
				<ListItem>Planned distribution order</ListItem>
			</List>
			<Paragraph>Planned orders are generated in the context of a particular scenario. As a rule, planned orders are only generated within the order horizon. However, planned distribution orders are also used outside the order horizon, where they make up the distribution plan.</Paragraph>
			<Paragraph>You must manually transfer and confirm planned orders for To-Order items, Nonproject items, and Unconfirmed orders. You cannot transfer these orders to the execution level in a batch, that is using the Transfer Planned Orders (cppat1210m000) session. If you do not manually transfer or confirm planned orders for To-Order items with an empty project segment, SSA ERP does not take the corresponding orders into account for transfer.</Paragraph>
			<Paragraph>The planned orders of the actual scenario can be transferred to the execution level, where they become actual supply orders.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000047" Version="B60adoc1" ContextApps="cp"><Term>planned production order</Term>
		<Definition>A planned order in <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef> to produce a certain quantity of an item.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000048" Version="B60adoc1" ContextApps="cp"><Term>planned purchase order</Term>
		<Definition>A planned order in <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef> to purchase a certain quantity of an item from a supplier (buy-from business partner).</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000101" Version="B60adoc1" ContextApps="cp"><Term>planned requirement date</Term>
		<Definition>The date for which SSA ERP identifies a material requirement.</Definition>
		<SimpleSection><Paragraph>If the projected inventory at that date is less than the required quantity, the planning engine generates a planned order or a reschedule-in signal.</Paragraph>
			<Paragraph>The planned requirement date of a manually entered planned order is equal to the planned order's finish date.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000066" Version="B60adoc1" ContextApps="cp"><Term>planning horizon</Term>
		<Definition>The time period for which SSA ERP maintains planning data for an item.</Definition>
		<SimpleSection><Paragraph>The planning horizon is expressed as a number of working days from the date you carry out the simulation.</Paragraph>
			<Paragraph><GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef> does not generate supply plans or planned orders beyond an item's planning horizon.</Paragraph>
			<Paragraph>To calculate the planning horizon, <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef> uses the calendar that you specified for the enterprise unit of the default warehouse to which the plan item belongs.</Paragraph>
			<Paragraph>If you did not specify an enterprise unit for the default warehouse of the plan item, Enterprise Planning uses the company calendar to calculate the planning horizon.</Paragraph>
		</SimpleSection>
		<Note><SectionTitle>Note</SectionTitle>
			<Paragraph><GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef> moves the planning horizon to the end of the plan period in which it falls.</Paragraph>
		</Note>
	</GlossaryEntry>
	<GlossaryEntry ID="000107" Version="B60adoc1" ContextApps="cp"><Term>priority rule</Term>
		<Definition>The rule on which Enterprise Planning bases the choice of suppliers. For example, the costs, supply time, or the priority of the supplier.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000018" Version="B60adoc1" ContextApps="cp"><Term>production plan</Term>
		<Definition>The planned receipts of manufactured items, specified by period.</Definition>
		<SimpleSection><Paragraph>These receipts are the quantity that must be produced internally.</Paragraph>
			<Paragraph>Note that the production plan does not include the quantity of the plan item that is delivered by other sites or warehouse locations.</Paragraph>
			<Paragraph>The production plan is part of the supply plan for a plan item.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000046" Version="B60adoc1" ContextApps="cp"><Term>projected inventory</Term>
		<Definition>The expected inventory level at the end of a plan period.</Definition>
		<SimpleSection><Paragraph>Note that the projected inventory of plan periods that are entirely in the past equals the inventory on hand.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000023" Version="B60adoc1" ContextApps="cp"><Term>purchase plan</Term>
		<Definition>The item quantity that is planned to be delivered by external suppliers, specified by period.</Definition>
		<SimpleSection><Paragraph>The purchase plan belongs to the supply plan for a plan item.</Paragraph>
			<Paragraph>Note the distinction between purchase plan and distribution plan. The distribution plan covers the volume to be delivered by internal or sister-company suppliers.</Paragraph>
		</SimpleSection>
		<Note><SectionTitle>Note</SectionTitle>
			<Paragraph>SSA ERP uses the purchase plan to create planned orders, and not to purchase schedule quantities.</Paragraph>
		</Note>
	</GlossaryEntry>
	<GlossaryEntry ID="000022" Version="B60adoc1" ContextApps="cp"><Term>reference date</Term>
		<Definition>A date that determines when a rolling scenario is shifted forward in time.</Definition>
		<ExampleSection><SectionTitle>Example</SectionTitle>
			<TABLE border="1"><TBODY><TR><TD>Reference date</TD>
						<TD>January 5</TD>
					</TR>
					<TR><TD>Rolling frequency</TD>
						<TD>14 days</TD>
					</TR>
				</TBODY>
			</TABLE>
			<Paragraph>On or after January 19, the scenario is shifted forward 14 days. The new reference date will be January 19.</Paragraph>
		</ExampleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000400" Version="B60adoc1" ContextApps="cp"><Term>release time fence</Term>
		<Definition>The date until which you want to be able to transfer planned production orders for a particular plan item to Manufacturing.</Definition>
		<SimpleSection><Paragraph>The release time fence is expressed as a number of working days from the date you carry out the simulation.</Paragraph>
			<Paragraph>Enterprise Planning needs operation data to transfer planned production orders to ERP Manufacturing. As a rule, Enterprise Planning stores operation data for a planned order only if the order's start date falls within the plan item's release time fence.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000008" Version="B60adoc1" ContextApps="cp"><Term>resource</Term>
		<Definition>A group of machines or employees in Enterprise Planning, corresponding to a work center in other SSA ERP packages.</Definition>
		<SimpleSection><Paragraph>Each operation performed to manufacture an item requires a certain capacity amount from a resource (for example, production hours). The capacity of the resource can be a constraint in the planning.</Paragraph>
			<Paragraph>The availability of a resource can be specified by using the resource calendar.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000132" Version="B60adoc0" ContextApps="cp"><Term>resource master plan</Term>
		<Definition>A time-phased overview of the capacity use at a certain resource.</Definition>
		<SimpleSection><List><ListIntro>In a resource master plan, the following types of capacity use are recorded per plan period:</ListIntro>
				<ListItem>Critical capacity requirements from master-based planning</ListItem>
				<ListItem>Capacity use related to planned orders</ListItem>
				<ListItem>Capacity use related to SFC (production) orders and service activities</ListItem>
				<ListItem>Capacity use related to PCS (project) activities</ListItem>
			</List>
			<Paragraph>In addition, the resource master plan contains capacity CTP information.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000308" Version="B60adoc1" ContextApps="cp"><Term>resource order plan</Term>
		<Definition>A period based overview of the capacity utilization of a specific resource and of the orders that require resource capacity.</Definition>
		<SimpleSection><Paragraph>The resource order plan can contain the following order types/entities:</Paragraph>
			<List><ListItem>Critical capacity requirements from <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef>
				</ListItem>
				<ListItem>Planned production orders from <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef>
				</ListItem>
				<ListItem>Production orders from the <GUIRef href="/baanerp/ti/sfc" role="module">Shop Floor Control</GUIRef> module of <GUIRef href="/baanerp/ti" role="package">Manufacturing</GUIRef>
				</ListItem>
				<ListItem>Project activities from the <GUIRef href="/baanerp/ti/pcs" role="module">Project Control</GUIRef> module of <GUIRef href="/baanerp/ti" role="package">Manufacturing</GUIRef>
				</ListItem>
				<ListItem>Service order activities fromt the <GUIRef href="" role="manual">Service Order Control (SOC)</GUIRef> module or the <GUIRef href="" role="manual">Work Order Control (WCS)</GUIRef> module of <GUIRef href="" role="manual">Service</GUIRef>
				</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000309" Version="B60adoc1" ContextApps="cp"><Term>resource planning horizon</Term>
		<Definition>The time period for which SSA ERP performs resource planning.</Definition>
		<SimpleSection><Paragraph>You can see the results of this planning in the resource master plan.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000021" Version="B60adoc1" ContextApps="cp"><Term>rolling frequency</Term>
		<Definition>The number of days after which a rolling scenario is shifted forward in time.</Definition>
		<SimpleSection><Paragraph>The number of days by which a plan is shifted forward equals the value of the scenario's rolling frequency.</Paragraph>
			<Paragraph>Note that the rolling frequency is defined in calendar days.</Paragraph>
		</SimpleSection>
		<ExampleSection><SectionTitle>Example</SectionTitle>
			<Paragraph>If the rolling frequency is seven days, the scenario will be shifted forward seven days, every seventh day.</Paragraph>
		</ExampleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000006" Version="B60adoc1" ContextApps="cp"><Term>rolling scenario</Term>
		<Definition>A particular type of scenario that is shifted forward in time. You can specify a rolling frequency to determine the number of days after which SSA ERP must roll the scenario.</Definition>
		<SimpleSection><Paragraph>In the course of time, the current date will reach or exceed a certain reference date plus the rolling frequency. When this is the case, the scenario's start date and finish date, the plan period division, and the reference date itself are shifted forward.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000007" Version="B60adoc1" ContextApps="cp"><Term>scenario</Term>
		<Definition>The identification of one out of various possible planning solutions.</Definition>
		<SimpleSection><Paragraph>Each scenario represents one overall planning solution, and involves particular settings for the planning of items and resources. You can use scenarios to analyze and compare various planning options and to find the best planning solution. For example, you can vary demand forecasts or sourcing strategies.</Paragraph>
			<Paragraph>One of the scenarios is the actual scenario, which corresponds with the actual planning situation. You can only transfer planned orders and production plans from the actual scenario to the execution level of SSA ERP.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000124" Version="B60adoc1" ContextApps="cp"><Term>scheduled distribution receipts</Term>
		<Definition>The quantity scheduled to be received from the orders created when planned distribution orders are transferred to the execution level, (that is, transfer orders and/or purchase orders.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000122" Version="B60adoc1" ContextApps="cp"><Term>scheduled production receipts</Term>
		<Definition>The quantity scheduled to be received from (actual) production orders.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000123" Version="B60adoc1" ContextApps="cp"><Term>scheduled purchase receipts</Term>
		<Definition>The quantity scheduled to be received from (actual) purchase orders and purchase schedules.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000371" Version="B60adoc1" ContextApps="cp"><Term>signal</Term>
		<Definition>A short standardized message that SSA ERP generates to advise the user to change or correct a specific planning parameter, value, or constraint to avoid undesired results or conflicts in planning.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000071" Version="B60adoc1" ContextApps="cp"><Term>signal horizon</Term>
		<Definition>The number of days for which <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef> generates signals of a certain type.</Definition>
		<SimpleSection><Paragraph>The signal horizon is expressed as a number of working days from the date you carry out the simulation.</Paragraph>
			<Paragraph>Beyond the signal horizon, Enterprise Planning does not generate signals of the particular signal type involved.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000117" Version="B60adoc1" ContextApps="cp"><Term>source allocation rule</Term>
		<Definition>The rule that defines how a required volume is divided over the following sources of supply:</Definition>
		<SimpleSection><List><ListItem>Production</ListItem>
				<ListItem>Purchase</ListItem>
				<ListItem>Distribution</ListItem>
			</List>
		</SimpleSection>
		<SimpleSection><Paragraph>The source allocation rule is either Percentage or Priority.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000104" Version="B60adoc1" ContextApps="cp"><Term>sourcing strategy</Term>
		<Definition>The subdivision of the planned supply of a plan item over the following sources:</Definition>
		<SimpleSection><List><ListItem>Production</ListItem>
				<ListItem>Purchase</ListItem>
				<ListItem>Distribution</ListItem>
			</List>
		</SimpleSection>
		<SimpleSection><Paragraph>Sourcing strategies are defined within the context of a scenario.</Paragraph>
			<Paragraph>You can define sourcing strategies for clusters, item groups, and plan items.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000017" Version="B60adoc1" ContextApps="cp"><Term>special demand</Term>
		<Definition>An extra item quantity that is expected to be sold in a plan period, on top of the forecast demand, and for a specific reason. For example, a special sales action.</Definition>
		<SimpleSection><Paragraph>You can view and maintain special demand in the <GUIRef href="/baanerp/cp/dsp/cpdsp2100m000" role="session">Special Demand by Item (cpdsp2100m000)</GUIRef> session. Here you can also record a reason for each instance of special demand.</Paragraph>
			<Paragraph>The assembly-part demand forecast from <GUIRef href="/baanerp/cf" role="package">Configurator</GUIRef> is also stored as special demand.</Paragraph>
			<Paragraph>The special demand is part of the demand plan for a plan item or channel.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000073" Version="B60adoc1" ContextApps="cp"><Term>supply plan</Term>
		<Definition>The total supply that is planned in master planning.</Definition>
		<SimpleSection><List><ListIntro>The supply plan of an item consists of:</ListIntro>
				<ListItem>Production plan</ListItem>
				<ListItem>Purchase plan</ListItem>
				<ListItem>Distribution plan (shown in the item master plan as planned distribution orders)</ListItem>
			</List>
			<Paragraph>The item master plan also takes into account the supply planned in order planning (planned orders). However, this type of supply is not part of the item's supply plan. In other words, a supply plan usually exists only outside the item's order horizon.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000105" Version="B60adoc1" ContextApps="cp"><Term>supply strategy</Term>
		<Definition>The methods by which the supply of plan items is divided over multiple suppliers.</Definition>
		<SimpleSection><List><ListIntro>The supply strategy defines the priority rules and allocation rules that direct the planning engines in the choice of suppliers. There are separate supply strategies for:</ListIntro>
				<ListItem>External suppliers (planned purchase orders)</ListItem>
				<ListItem>Internal suppliers (planned distribution orders)</ListItem>
			</List>
			<Paragraph>You can define supply strategies for clusters, item groups, and plan items.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000106" Version="B60adoc1" ContextApps="cp"><Term>supply type</Term>
		<Definition>In SSA ERP, the type of supplier (internal or external) for which a supply strategy is used.</Definition>
		<SimpleSection><Paragraph>SSA ERP uses internal suppliers to generate distribution orders, and external suppliers to generate purchase orders.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000005" Version="B60adoc1" ContextApps="cp"><Term>supplying relationship</Term>
		<Definition>A distribution link between a supplying warehouse cluster and a receiving cluster. The clusters involved can be in the same site, or in different sites.</Definition>
		<SimpleSection><Paragraph><GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef> uses supplying relationships for distribution planning: the supplying relationships represent valid supply paths for particular items or groups of items. You can specify supplying relationships at the level of individual items, but also at more general levels.</Paragraph>
			<Paragraph>The supplying relationships also determine the costs of supply, lot size rules, and other parameters.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000115" Version="B60adoc1" ContextApps="cp"><Term>supplying site</Term>
		<Definition>The site from which a plan item is delivered through the multisite distribution structure.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000063" Version="B60adoc1" ContextApps="cp"><Term>time fence</Term>
		<Definition>The date until which an item's supply plan and planned orders are frozen.</Definition>
		<SimpleSection><Paragraph>The time fence is expressed as a number of working days or working hours from the date you carry out the simulation.</Paragraph>
			<Paragraph>As a rule, <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef> does not regenerate the supply plan or the planned orders within the time fence. However, you can overrule this behavior when you run a master-plan simulation or order simulation.</Paragraph>
			<List><ListIntro>The time fence is meant to prevent:</ListIntro>
				<ListItem>Disturbance of orders that have already started (at the shop-floor level).</ListItem>
				<ListItem>Generation of planned orders with start dates in the past (that is, orders that are late).</ListItem>
			</List>
			<Paragraph>Usually, the lead time of an item's production process is a reasonable value for the time fence.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000064" Version="B60adoc1" ContextApps="cp"><Term>workday</Term>
		<Definition>A day on which work can be performed.</Definition>
		<SimpleSection><Paragraph>Lead times, horizons, and time fences in <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef> are defined in workdays (except for the forecast horizon).</Paragraph>
			<Paragraph>Enterprise Planning converts workdays to working hours, minutes, and seconds on the basis of the basic day capacity.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000014" Version="B60adoc1" ContextApps="cp"><Term>workload</Term>
		<Definition>The amount of work scheduled for a resource.</Definition>
		<SimpleSection><List><ListIntro>The term workload is used in the following contexts:</ListIntro>
				<ListItem>In the Workload Control (WLC) module, workload is defined as the total capacity used in a certain plan period. For example: 50 hours of production in week 23.</ListItem>
				<ListItem>In the <GUIRef href="/baanerp/cp/pat/cppat1210m000" role="session">Transfer Planned Orders (cppat1210m000)</GUIRef> session, workload is the required capacity for the production orders that must still be carried out. For example: resource R has a total workload of 300 hours of production orders that must still be carried out.</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000013" Version="B60adoc1" ContextApps="cp"><Term>workload control</Term>
		<Definition>A constraint-based method for supply planning, aimed at creating a feasible planning solution by leveling the workload on a resource.</Definition>
		<SimpleSection><Paragraph>Workload control is based on the idea that workload levels and production lead times are related.</Paragraph>
			<Paragraph>This method is used to control both the workload by resource and the lead time per item.</Paragraph>
			<Paragraph>Synonym: WLC</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000052" Version="B60adoc1" ContextApps="cp"><Term>workload norm</Term>
		<Definition>The amount of work that must await execution on the shop floor for a resource.</Definition>
		<SimpleSection><Paragraph>If the workload is much lower than the workload norm, there is a risk that the resource becomes idle. If the workload is much higher, the production lead times can become unacceptably long.</Paragraph>
			<Paragraph>Note that the workload norm is expressed in hours.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000053" Version="B60adoc1" ContextApps="cp"><Term>workload tolerance</Term>
		<Definition>The percentage by which the resource's workload is allowed to deviate from the workload norm.</Definition>
	</GlossaryEntry>
</Glossary>
