<?xml version="1.0" encoding="utf-8"?>
<Glossary ID="/baanerp/tp/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 TP package</Title>
	</Header>
	<GlossaryEntry ID="000005" Version="B60adoc1" ContextApps="tp"><Term>activity</Term>
		<Definition>The smallest part of the activity structure used for a time-scaled budget. An entity that is used to represent a part of a project in an activity structure.</Definition>
		<SimpleSection><List><ListIntro>SSA ERP distinguishes four activity types:</ListIntro>
				<ListItem>WBS Element.</ListItem>
				<ListItem>Project Cost Account.</ListItem>
				<ListItem>Work Package.</ListItem>
				<ListItem>Planning Package.</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="ActiviBudget.tp" Version="B60adoc1" ContextApps="tp"><Term>activity budget</Term>
		<Definition>An activity budget functions in more or less the same way as an element budget whose budget method depends on the way you structure your project.</Definition>
		<SimpleSection><List><ListIntro>Advantages of an activity budget over an element budget are:</ListIntro>
				<ListItem>An activity budget is defined on a time horizon.</ListItem>
				<ListItem>You can use an activity budget for planning purposes in external scheduling packages.</ListItem>
				<ListItem>You can copy an activity budget to a top-down budget, and use earned value methods to measure project performance. You can either create activity budget lines in SSA ERP or in external scheduling packages.</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000301" Version="B60adoc1" ContextApps="tp"><Term>activity progress</Term>
		<Definition>The progress of an activity.</Definition>
		<SimpleSection><List><ListIntro>SSA ERP distinguishes two types of activity progress:</ListIntro>
				<ListItem>Physical progress</ListItem>
				<ListItem>Schedule (time/duration) progress</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000379"><Term>activity relationship</Term>
		<Definition>Activities are sequenced with respect to work and specific dates to provide realistic schedules. An activity relationship indicates that a certain activity (successor) cannot start or end until another activity (predecessor) starts or ends.</Definition>
		<SimpleSection><List><ListIntro>You can define the following dependencies between the predecessor and the successor activities:</ListIntro>
				<ListItem><GUIRef href="" role="manual">Finish-to-start</GUIRef>: The initiation of the task of the successor depends upon the completion of the task of the predecessor</ListItem>
				<ListItem><GUIRef href="" role="manual">Finish-to-finish</GUIRef>: The completion of the task of the successor depends upon the completion of the task of the predecessor</ListItem>
				<ListItem><GUIRef href="" role="manual">Start-to-start</GUIRef>: The initiation of the task of the successor depends upon the initiation of the task of the predecessor.</ListItem>
				<ListItem><GUIRef href="" role="manual">Start-to-finish</GUIRef>: The completion of the task of the successor depends upon the initiation of the task of the predecessor.</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000326" Version="B60adoc1" ContextApps="tp"><Term>activity structure</Term>
		<Definition>A hierarchical structure that organizes and defines the total scope of the project. Each level represents an increasingly detailed definition of a work project. In contrast to the element structure, the activity structure is activity time oriented.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000356" Version="B60adoc1" ContextApps="tp"><Term>activity/activity budget</Term>
		<Definition>The project budget is an activity budget with the budget control on the</Definition>
		<SimpleSection><Paragraph>activity budget. This means that an activity structure must be filled and that the planning can be used.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="ActualCostOf.tp" Version="B60adoc1" ContextApps="tp"><Term>actual cost of work performed</Term>
		<Definition>The costs incurred to accomplish the work performed within a given period. Synonym: ACWP</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="Adjustment.tp" Version="B60adoc1" ContextApps="tp"><Term>adjustment</Term>
		<Definition>In SSA ERP, a modification to a frozen bottom up budget. Modification will only increase or decrease the budget, for extensions the contract is also changed.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000302" Version="B60adoc1" ContextApps="tp"><Term>advance payment request</Term>
		<Definition>A way to efficiently manage your cash flow by requesting to pay an agreed amount before the project or a specific part of the project starts. The advance payment will be settled with the final invoice. For instance, you can select a project and request an advance payment for certain project materials. The advance can be linked to an installment. For unit rate and cost-plus invoices, the advance payment request is settled with the next invoice(s).</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000023" Version="B60adoc1" ContextApps="tp"><Term>agreement type</Term>
		<Definition>A lumpsum contract or a reimbursable contract. In a reimbursable contract the customer agrees to pay all acceptable costs up to a fixed fee.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000348" Version="B60adoc1" ContextApps="tp"><Term>apportion</Term>
		<Definition>To make a proportionate division or distribution for the earned value. When activity Y is apportioned to activity X, the earned value method of Y and X is the same. Y will copy X. X can have any earned value method.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="ArchivProjec.tp" Version="B60adoc1" ContextApps="tp"><Term>archived projects</Term>
		<Definition>Projects that are stored in an archive company. The project archive company can be used as a repository for historical project data.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000320" Version="B60adoc1" ContextApps="tp"><Term>assemble-to-order</Term>
		<Definition>An environment where a product or service can be assembled after receipt of a customer's order. Synonym: ATO</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000319" Version="B60adoc1" ContextApps="tp"><Term>assembly order</Term>
		<Definition>An order to assemble a product on one or more assembly lines.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000322" Version="B60adoc1" ContextApps="tp"><Term>available-to-promise</Term>
		<Definition>A calculation that determines how many products are available (to sell or consume in a project) at a certain moment in the future.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="BaseliPlanni.tp" Version="B60adoc1" ContextApps="tp"><Term>baseline (planning)</Term>
		<Definition>The baseline can be seen as a snapshot of the active plan's scheduled activities' start data and finish data.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000323" Version="B60adoc1" ContextApps="tp"><Term>bill of material</Term>
		<Definition>A listing of all subassemblies, intermediates, parts, and raw materials that go into the parent assembly. The bill lists the quantity and costs of each component. Synonym: BOM</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000312" Version="B60adoc1" ContextApps="tp"><Term>bottom-up budget</Term>
		<Definition>This budget method defines all work that must be accomplished to complete the budget. A bottom up budget is made for elements or activities.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="BudgCostAnal.tp" Version="B60adoc1" ContextApps="tp"><Term>budget cost analysis</Term>
		<Definition>An analysis of the bottom up budget. You can run several cost analyses for the same budget. Each budget is stored with a combined project code and budget cost-analysis code, so you can compare the budgets.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="BuCoAnCoPr.tp" Version="B60adoc0" ContextApps="tp"><Term>budget cost analysis codes by project</Term>
		<Definition>Codes by which amounts and time quantities of budget lines are calculated for budget cost analysis.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000024" Version="B60adoc1" ContextApps="tp"><Term>budget date</Term>
		<Definition>The date of a budget line.</Definition>
		<SimpleSection><List><ListIntro>This date is used for:</ListIntro>
				<ListItem>Currency conversions that relate to the project. A currency conversion is date-effective. The budget date determines which currency rate is used.</ListItem>
				<ListItem>Prices. These can be date-effective as well. The budget line's of a bottom up date determines the price of the cost object.</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000098" Version="B60adoc1" ContextApps="tp"><Term>budget labor-rate search path</Term>
		<Definition>A search path that determines which cost and labor sales rates from which sessions are used in labor budget lines: labor, trade group, or project. The default labor rate that is used is defined as the level 1 labor rate. If this is not available, level 2 is used, and if this is not available, level 3 is used.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000100" Version="B60adoc1" ContextApps="tp"><Term>budget line</Term>
		<Definition>The most detailed level of a bottom up budget. The elements or activities in a budget can contain an unlimited number of budget lines. Each budget line includes a quantity of a cost object, a cost component to which the cost object is assigned, and a budget date.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000040" Version="B60adoc1" ContextApps="tp"><Term>budget status</Term>
		<Definition>The budget status of an element or activity.</Definition>
		<SimpleSection><List><ListIntro>SSA ERP distinguishes the following statuses:</ListIntro>
				<ListItem>Free: you can enter and change budget lines.</ListItem>
				<ListItem>Actual: you can change the budget data and the budget lines. In addition, you can generate the control data in the Project Production Control (PPC) module. You can log the actual budget history.</ListItem>
				<ListItem>Final: you cannot change the budget data without using budget adjustments.</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000349" Version="B60adoc1" ContextApps="tp"><Term>budget-at-completion</Term>
		<Definition>The total budget amount of the finished activity or OBS element. Synonym: BAC</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000324" Version="B60adoc1" ContextApps="tp"><Term>budgeted costs of work performed</Term>
		<Definition>The sum of the budgets for completed work packages, The work package or project cost account can be finished or partially completed. See earned value concept. Synonym: BCWP</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000325" Version="B60adoc1" ContextApps="tp"><Term>budgeted costs of work scheduled</Term>
		<Definition>The sum of the budgets for all the work scheduled to be accomplished within a given period. Synonym: BCWS</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000084" Version="B60adoc1" ContextApps="tp"><Term>budgeting method</Term>
		<Definition>The way to measure expected productivity.</Definition>
		<SimpleSection><List><ListIntro>SSA ERP distinguishes the following two methods in the bottom up budget:</ListIntro>
				<ListItem>By production rate: the number of production units produced per unit of time.</ListItem>
				<ListItem>By labor norm: the number of hours required to carry out one unit of the cost object.</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000101" Version="B60adoc1" ContextApps="tp"><Term>budget-line status</Term>
		<Definition>The status of the budget line. The status defaults from the element or activity to which it belongs.</Definition>
		<SimpleSection><List><ListIntro>Possible values are:</ListIntro>
				<ListItem>Free: the general data for a budget line has been recorded, and can be changed.</ListItem>
				<ListItem>Actual: you can still change the budget data and generate the control data. You can also log the budget history.</ListItem>
				<ListItem>Final: you cannot change the budget data anymore. You can only add or change the budget lines through a budget adjustment. You can also log the actual budget history.</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="BusineSector.tp" Version="B60adoc1" ContextApps="tp"><Term>business sector</Term>
		<Definition>An area of commercial endeavor. Projects can be categorized according to the business sector to which they refer.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000000000000047" Version="B60adoc1" ContextApps="tp"><Term>calendar file</Term>
		<Definition>A file containing calendar information for one or more calendars.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000316" Version="B60adoc1" ContextApps="tp"><Term>capital project</Term>
		<Definition>A project used for internal use in which deliverables can be booked as fixed assets but delivery of goods is not possible. In a capital project, you are the business partner.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="Categories.tp" Version="B60adoc1" ContextApps="tp"><Term>categories</Term>
		<Definition>A user-definable classification for projects.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="Commitment.tp" Version="B60adoc1" ContextApps="tp"><Term>commitment</Term>
		<Definition>A financial obligation that represents future costs.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000030" Version="B60adoc1" ContextApps="tp"><Term>contract amount</Term>
		<Definition>The total amount of the project contract. For a time-phased budget version, the contract amount is expressed as: contract amount = profit fee + management reserve + distributed budget + undistributed budget The contract amount is used to determine the invoice limit.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000105" Version="B60adoc1" ContextApps="tp"><Term>contract subamount</Term>
		<Definition>The contract amount relating to a particular business partner that is broken down into subamounts expressed in different currencies.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="ControCode.tp" Version="B60adoc1" ContextApps="tp"><Term>control code</Term>
		<Definition>A common parent cost-object level, a level above the special cost object. A control code is used for control purposes. For analysis, you can group cost objects of the same cost type under a control code. If you use a cost object to categorize a group of cost objects, it can be its own control code. You cannot have more than one control code in a tree. This is used for the frozen bottom up budget.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="ControData.tp" Version="B60adoc0" ContextApps="tp"><Term>control data</Term>
		<Definition>Data that is used to monitor a project.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000360" Version="B60adoc1" ContextApps="tp"><Term>cost component</Term>
		<Definition>A cost component is a collection of cost objects with a certain characteristic. A cost component does not depend on the cost type, therefore, for example, a project can be monitored from another dimension. For example, all the costs that refer to electrical work, for example, cable and installation work, are visible if the applicable cost objects are linked to the cost component Electrical work.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000092" Version="B60adoc1" ContextApps="tp"><Term>cost control</Term>
		<Definition>The method that SSA ERP uses to control project costs.</Definition>
		<SimpleSection><List><ListIntro>Cost control involves:</ListIntro>
				<ListItem>Recording actual costs against the expected costs entered in the budget.</ListItem>
				<ListItem>Reporting on any differences between budget, forecast, recorded costs and progress. If an element or activity uses cost control, the expected costs of the individual element as entered in the project budget are carried over to the control budget. If an element or activity does not use cost control, its budgeted costs are aggregated to the next, higher-level element in the budget structure for which cost control is applied.</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000329" Version="B60adoc1" ContextApps="tp"><Term>cost item</Term>
		<Definition>An administrative item that represents certain expenses. The item is not a physical product and cannot be handled logistically.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000003" Version="B60adoc1" ContextApps="tp"><Term>cost object</Term>
		<Definition>It is a type of cost carrier for the resources used in your project.</Definition>
		<SimpleSection><List><ListIntro>Five types of cost objects are available:</ListIntro>
				<ListItem>Material</ListItem>
				<ListItem>Labor</ListItem>
				<ListItem>Equipment</ListItem>
				<ListItem>Subcontracting</ListItem>
				<ListItem>Sundry costs Cost objects can be standard or specific for a project. The cost object is related to a control code for cost controlling purposes.</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000327" Version="B60adoc1" ContextApps="tp"><Term>cost of goods sold</Term>
		<Definition>Cost of Goods Sold (COGS) is the expense a company incurs in order to manufacture, create, or sell a product. It includes the purchase price of the raw material as well as the expenses of turning it into a product.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000078" Version="B60adoc1" ContextApps="tp"><Term>cost plus contract</Term>
		<Definition>A contract based on calculation of time and material after parts of the project are finished. Agreement on prices and labor is made before the project starts.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000009" Version="B60adoc1" ContextApps="tp"><Term>cost price</Term>
		<Definition>The cost object's cost price.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000006" Version="B60adoc1" ContextApps="tp"><Term>cost type</Term>
		<Definition>A way of categorizing cost objects and control codes according to the nature of the costs that they represent.</Definition>
		<SimpleSection><List><ListIntro>SSA ERP Project distinguishes five cost types:</ListIntro>
				<ListItem>Material</ListItem>
				<ListItem>Labor</ListItem>
				<ListItem>Equipment</ListItem>
				<ListItem>Subcontracting</ListItem>
				<ListItem>Sundry costs</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000352" Version="B60adoc1" ContextApps="tp"><Term>cost variance</Term>
		<Definition>Any difference between the estimated cost of an activity and the actual cost of that activity. Synonym: BCWP - ACWP</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="CostContPeri.tp" Version="B60adoc1" ContextApps="tp"><Term>cost-control periods</Term>
		<Definition>In this period project-related costs and revenues are booked.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="CostPlusCont.tp" Version="B60adoc1" ContextApps="tp"><Term>cost-plus contract</Term>
		<Definition>A contract that is carried out based on cost reimbursement and a profit percentage.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000038" Version="B60adoc1" ContextApps="tp"><Term>destination warehouse</Term>
		<Definition>The default project warehouse to which goods are sent before they are used in the project.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000367" Version="B60adoc1" ContextApps="tp"><Term>discrete lines</Term>
		<Definition>Bottom-up estimate lines that are not attached to any primary structure element.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000117" Version="B60adoc1" ContextApps="tp"><Term>distributed budget</Term>
		<Definition>The top down budget part that is distributed over the activities. You can look at a distributed budget on various levels: For the version: distributed budget = the budget assigned to the top activity of the activity structure. This can at most be equal to the sum of the contract amount - profit fee - management reserve</Definition>
		<SimpleSection><Paragraph>For activities: distributed budget = the budget that is already distributed to the lower level activities.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="DocumeTypes.tp" Version="B60adoc1" ContextApps="tp"><Term>document types</Term>
		<Definition>A user-definable classification of project-related documents.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="EarnedValueC.tp" Version="B60adoc1" ContextApps="tp"><Term>earned value concept</Term>
		<Definition>A time-phased method for measuring project performance. It compares the amount of work that was planned with work that was actually accomplished to determine if cost and schedule performance are as planned.</Definition>
		<SimpleSection><List><ListIntro>There are a number of different ways in which you can use the earned value method to determine how budget amounts are to be earned:</ListIntro>
				<ListItem>Milestones are attached to the activity and a percentage or amount of the budget is assigned to each milestone. When you reach a milestone, the assigned budget is earned.</ListItem>
				<ListItem>Start and end percentage: percentage values are assigned to the start and end points of the activities. In other words, the start percentage is earned when the activity starts and the remaining percentage is earned when the activity is completed.</ListItem>
				<ListItem>Percentage completed: budget amounts are earned in proportion to the percentage progress of the activity</ListItem>
				<ListItem>Level of effort: budget amounts are released in proportion to effort. This method is appropriate for time-driven activities where it is assumed that there will be no discrepancy between scheduled work planned (BCWS) and work performed (BCWP).</ListItem>
				<ListItem>Apportioned: apportioned efforts are those which have an intrinsic performance relationship to some other discrete activity. Budget amounts are earned in the same way as for the linked charge.</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="Element.tp" Version="B60adoc1" ContextApps="tp"><Term>element</Term>
		<Definition>The smallest part of an element structure. An element is used to define the (structure of the) work of the project, so that you can carry it out.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="ElemenBudget.tp" Version="B60adoc1" ContextApps="tp"><Term>element budget</Term>
		<Definition>The bottom up budget or control budget that consists of elements. The alternative is an activity budget. The elements can be related in a multilevel hierarchical structure, and each element can contain cost-object budget lines.</Definition>
		<SimpleSection><List><ListIntro>The advantage of an element budget over an activity budget is:</ListIntro>
				<ListItem>Multiple parents makes budgeting easy for repeating work.</ListItem>
				<ListItem>With the use of frequencies calculation of amounts needed of one element is faster and easier.</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="ElemenRelati.tp" Version="B60adoc1" ContextApps="tp"><Term>element relations</Term>
		<Definition>The way to determine the positioning of elements in comparison to other elements. Element relations are the basis of a layered (multilevel) element budget. The elements can also be linked to activities, a relation that is used when you generate control data for an element/activity budget. Elements use frequency as a tool to calculate element amounts fast and can have a multiparent structure.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="ElemenStruct.tp" Version="B60adoc1" ContextApps="tp"><Term>element structure</Term>
		<Definition>The multilevel, multiparent, hierarchical tree-like structure of elements that can be the basis of a budget.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000041" Version="B60adoc1" ContextApps="tp"><Term>element type</Term>
		<Definition>A way to distinguish project elements. A project with a Progress Invoice invoicing method can contain two types of elements: direct and indirect. If the progress is more than 100%, direct elements can have more than 100% progress. Indirect elements can never have more than 100% progress.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000355" Version="B60adoc1" ContextApps="tp"><Term>element/activity budget</Term>
		<Definition>The project budget is an element budget, which is linked to activities in order to create a control budget. This means an element and activity structure must be filled and that the planning can be used.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000357" Version="B60adoc1" ContextApps="tp"><Term>element/element budget</Term>
		<Definition>The project budget is an element budget with the budget control on the elements. This means that an element structure must be filled but that planning cannot be used.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000044" Version="B60adoc1" ContextApps="tp"><Term>equipment</Term>
		<Definition>A cost type that is required for resources, which is not consumed while the project is carried out. Examples of equipment are machinery and tools.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000013" Version="B60adoc1" ContextApps="tp"><Term>equipment group</Term>
		<Definition>A special equipment cost object that acts as a grouping cost object to other equipment cost objects. This is a useful way of grouping together similar equipment cost objects.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000321" Version="B60adoc1" ContextApps="tp"><Term>ERP Configurator's ATO template</Term>
		<Definition>This template is used to configure a product that can be assembled in a mix-model flow according to an engineering model or a process model. The template also includes a final assembly schedule.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000336" Version="B60adoc1" ContextApps="tp"><Term>ERP Configurator's MTO template</Term>
		<Definition>This template is used to configure a product that can be produced. The template configures items, bills of materials, and routings based on a generic product structure.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000374" Version="B60adoc1" ContextApps="tp"><Term>estimate line</Term>
		<Definition>A detailed estimate breakup. For example, if you require item A for the estimate, you enter this item with its specifications on the estimate line.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000361" Version="B60adoc1" ContextApps="tp"><Term>estimate type</Term>
		<Definition>The way in which the calculation of the estimate is performed. An estimate type is either top down or bottom up.</Definition>
		<SimpleSection><Paragraph>Top down</Paragraph>
			<Paragraph>In calculating the cost or sales amount in a top down structure, you distribute a top amount to the lower level elements.</Paragraph>
			<Paragraph>Bottom up</Paragraph>
			<Paragraph>In calculating the cost or sales amount in a bottom up structure, you enter exact amounts for lowest level elements and aggregate them to make the top amount.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000364" Version="B60adoc1" ContextApps="tp"><Term>estimate version</Term>
		<Definition>A means to compare estimates. An estimate can have various versions. Each version is stand-alone and is not derived from the previous version. A version can, however, be copied or compared.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000350" Version="B60adoc1" ContextApps="tp"><Term>estimate-at-completion</Term>
		<Definition>The forecasted total cost of a project, activity, or organization-breakdown-structure element when the defined scope of work is completed. To calculate the estimate-at-completion: Actual costs + ETC Synonym: EAC</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000330" Version="B60adoc1" ContextApps="tp"><Term>estimate-to-complete</Term>
		<Definition>A realistic forecast appraisal of the remaining work. Synonym: ETC</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000046" Version="B60adoc1" ContextApps="tp"><Term>exchange-rate type</Term>
		<Definition>A way to group currency exchange rates. You can assign different currency exchange rates to different invoice-to business partners and/or to different types of transactions (purchase, sales, and so on).</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000369" Version="B60adoc1" ContextApps="tp"><Term>expense tax</Term>
		<Definition>An internal purchase cost that can be booked on a non-finalized project. The transaction costs are posted separately if direct delivery occurs. If a delivery is made through a project warehouse, the expense tax is included in the valuation price or fixed transfer price (FTP).</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000017" Version="B60adoc1" ContextApps="tp"><Term>extension</Term>
		<Definition>The specific agreements within or in addition to the initial contract. An extension falls outside the initial contract with the sold-to business partner. Extensions can be assigned to the bottom up budget.</Definition>
		<SimpleSection><List><ListIntro>t. SSA ERP distinguishes four extension types:</ListIntro>
				<ListItem>Scope change</ListItem>
				<ListItem>Provisional amount</ListItem>
				<ListItem>Fluctuation settlement</ListItem>
				<ListItem>Quantities-to-be-settled</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000331" Version="B60adoc1" ContextApps="tp"><Term>financial result status</Term>
		<Definition>A way to characterize the project's financial results.</Definition>
		<SimpleSection><List><ListIntro>SSA ERP distinguishes three different financial result statuses:</ListIntro>
				<ListItem>Free: This status applies until the project is finished.</ListItem>
				<ListItem>Determine Result: If the project status is Finished, you can select this financial result status.</ListItem>
				<ListItem>Result Determined: The final result is determined and the project status is changed to Closed.</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="FixedPriceCo.tp" Version="B60adoc1" ContextApps="tp"><Term>fixed-price contract</Term>
		<Definition>A contract that is carried out for an agreed fixed price, also called a lump sum.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000332" Version="B60adoc1" ContextApps="tp"><Term>flow shop</Term>
		<Definition>A type of manufacturing organization in which machines and operators handle a standard, usually uninterrupted, material flow. A flow shop is a mass-production shop and has a continuous manufacturing layout.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="FluctuSettle.tp" Version="B60adoc1" ContextApps="tp"><Term>fluctuation settlement</Term>
		<Definition>An extension type. The settlement of the price fluctuations' influence for invoicing purposes. You cannot define this extension type for Cost Plus projects and for projects with <GUIRef href="" role="manual">Invoicing Method</GUIRef> set to Unit Rate.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000106" Version="B60adoc1" ContextApps="tp"><Term>general data</Term>
		<Definition>Data that is not project-specific. This data includes generic information on business partners, countries, elements, and so on. You can either enter this data in the Project Data Management PDM module or in SSA ERP Common data.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000107" Version="B60adoc1" ContextApps="tp"><Term>general project data</Term>
		<Definition>Data that is project-specific.</Definition>
		<SimpleSection><List><ListIntro>Data that is project-specific, for example,:</ListIntro>
				<ListItem>Project cost object</ListItem>
				<ListItem>Project definition</ListItem>
				<ListItem>Project wage rates Enter this data in the Project Data Management (PDM) module.</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000052" Version="B60adoc1" ContextApps="tp"><Term>holdback</Term>
		<Definition>A percentage amount that the customer withholds from the contract amount. This serves as a guarantee that all activities are performed, and that contractual obligations are met. In other words the holdback amount is paid after the project activities have been satisfactorily performed.</Definition>
		<SimpleSection><Paragraph>Synonym: Retainage.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="HoursControP.tp" Version="B60adoc1" ContextApps="tp"><Term>hours-control periods</Term>
		<Definition>SSA ERP uses hours control periods.</Definition>
		<SimpleSection><List><ListIntro>SSA ERP uses hours control periods to:</ListIntro>
				<ListItem>Carry out periodic control of labor hours</ListItem>
				<ListItem>Realize hours accounting</ListItem>
				<ListItem>Process wages and salaries</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000305" Version="B60adoc1" ContextApps="tp"><Term>independent multihome currency</Term>
		<Definition>This approach is required for companies that work in high-inflation countries.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000089" Version="B60adoc1" ContextApps="tp"><Term>installment</Term>
		<Definition>The amount invoiced to the customer when a project completes its corresponding element/activity or reaches a milestone or progress of elements/activities.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="FinancResult.tp" Version="B60adoc1" ContextApps="tp"><Term>interim financial results</Term>
		<Definition>The temporary financial result that you can consult while you carry out the project and which you can transfer to the profit and loss account. There are two interim result types:</Definition>
		<SimpleSection><List><ListItem>Interim Result Costs: transactions associated with costs.</ListItem>
				<ListItem>Interim Result Revenue: transactions associated with revenues.</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000306" Version="B60adoc1" ContextApps="tp"><Term>internal project</Term>
		<Definition>A type of project for which no sold-to business partners are defined and no invoicing is performed. The delivery of items does not apply. An internal project can optionally be capitalized, the value can be sent to the Fixed Assets (FAM) module in <GUIRef href="/baanerp/tf" role="package">Financials</GUIRef>.</Definition>
		<SimpleSection><List><ListIntro>ERP distinguishes two project types:</ListIntro>
				<ListItem>A capital project: deliverables can be booked as fixed assets, delivery of goods is not possible.</ListItem>
				<ListItem>An internal project: cannot be booked on the balance, and delivery of goods is not possible. The result can only be seen in the profit and loss account.</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000095" Version="B60adoc1" ContextApps="tp"><Term>invoice type</Term>
		<Definition>The way to calculate project invoices for a given contract type. The method determines when to issue invoices to the sold-to business partner.</Definition>
		<SimpleSection><List><ListIntro>SSA ERP distinguishes the following invoice methods:</ListIntro>
				<ListItem>Cost-plus invoicing: the amount is based on the financial amounts entered at cost object level plus a profit. This method is only available if the contract type is cost plus.</ListItem>
				<ListItem>Unit-rate invoicing: the amount is based on the financial amounts per unit entered at element or activity level. Unit-rate invoicing applies to both contract types.</ListItem>
				<ListItem>Installment invoicing: the amount is a subdivision of the value. This method is only available if the contract type is fixed price.</ListItem>
				<ListItem>Progress invoicing: the invoice amount is based on progress for element or activity. Two types of elements are permitted: direct and indirect. The calculated amount of the direct elements depends on their own progress. The calculated amount of the indirect elements is based on the progress of the project as a whole and can never be more than 100%.</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000315" Version="B60adoc1" ContextApps="tp"><Term>invoicing method</Term>
		<Definition>This method is only used for contract projects to invoice to <GUIRef href="/baanerp/tf" role="package">Financials</GUIRef>. Capital projects have no invoicing. Sales order project use Sales Control for invoicing.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="Labor.tp" Version="B60adoc0" ContextApps="tp"><Term>labor</Term>
		<Definition>A specific task. You can use labor codes to control the costs of a labor code or of a group of labor codes.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000102" Version="B60adoc1" ContextApps="tp"><Term>labor rate for hours registration search path</Term>
		<Definition>This search path determines which cost and labor sales rates are used in hours registration.</Definition>
		<SimpleSection><List><ListIntro>This search path determines which cost and labor sales rates are used in hours registration:</ListIntro>
				<ListItem>Employee</ListItem>
				<ListItem>Labor</ListItem>
				<ListItem>Project</ListItem>
				<ListItem>Trade groups The default labor rate used, is level 1. If this level has no entry available, level 2 is used, and so on.</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000376" Version="B60adoc1" ContextApps="tp"><Term>landed</Term>
		<Definition>The cost amount plus surcharges.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000375" Version="B60adoc1" ContextApps="tp"><Term>launch</Term>
		<Definition>To copy an estimate version to a project budget. The version estimate lines are copied to project budget lines.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000362" Version="B60adoc1" ContextApps="tp"><Term>leading estimate type</Term>
		<Definition>The estimate type of the structural element. If the leading estimate type is bottom up, SSA ERP calculates the total leading estimate type (LET) amount by summing up the estimate line amounts with the same level type. If the leading estimate type for the top structural element is top down, the total LET is the structural element amount that is defined as top down. Top-down structural elements are only checked to see whether the estimate amounts do not exceed their parent’s amount; they are not actually used for the total estimate.</Definition>
		<SimpleSection><Paragraph>Acronym: LET</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000363" Version="B60adoc1" ContextApps="tp"><Term>leaf node</Term>
		<Definition>The last particle of a structure. If a child is added to the leaf node in the structure, the leaf node becomes a parent and is called a node.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000347" Version="B60adoc1" ContextApps="tp"><Term>level of effort</Term>
		<Definition>A budgeting method in which budget amounts are released in proportion to effort. This method is appropriate for time-driven activities where it is assumed that there is no discrepancy between work planned and work performed.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000373" Version="B60adoc1" ContextApps="tp"><Term>level type</Term>
		<Definition>An estimate type category that determines which estimate lines are used in aggregating totals.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000335" Version="B60adoc1" ContextApps="tp"><Term>make-to-order</Term>
		<Definition>A production environment where a product or service can be made after receipt of a customer's order. The final product is usually a combination of standard items and items custom-designed to meet the special needs of the customer. Synonym: MTO</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000116" Version="B60adoc1" ContextApps="tp"><Term>management reserve</Term>
		<Definition>A contingency fund for unanticipated occurrences, which reduces the risk of scope changes. In a time-phased budget version, this is the amount that is withheld for control purposes rather than distributed to the activity structure or retained for profit. Management reserve is expressed as follows: management reserve = contract amount - profit fee + distributed budget + undistributed budget</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="Milestone.tp" Version="B60adoc1" ContextApps="tp"><Term>milestone</Term>
		<Definition>An activity of zero days that usually represents a significant event in the project. In many cases the completion of a phase of major deliverable. Milestones can be used for the moment of invoicing and the calculation of earned value.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000334" Version="B60adoc1" ContextApps="tp"><Term>mixed model flow</Term>
		<Definition>A type of flow shop in which two or more different products are assembled with relative small changes over time and set-up times. The product sequence can vary, for example, A-A-B-C-A-C-B-B-C-A, and so on.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000007" Version="B60adoc1" ContextApps="tp"><Term>norm</Term>
		<Definition>The number of hours required to carry out one unit of labor. Used in an activity budget with cost type Labor, Equipment or Subcontracting. Number of hours = the number of labor units x norm This norm is useful in situations where the unit of measure for the labor cost object is not a time unit.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="OrganiBreakd.tp" Version="B60adoc1" ContextApps="tp"><Term>organization breakdown structure</Term>
		<Definition>A representation of the structure of a project organization, this is usually depicted as a tree-like hierarchical structure. The organization breakdown structure is used to link the responsibilities of certain project parts, such as the allocation of a financial budget or the realization of project activities to an OBS element. Each OBS element can be linked to an employee. The OBS element is standard and can also be made project specific.</Definition>
		<SimpleSection><Paragraph>Synonym: OBS</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000346" Version="B60adoc1" ContextApps="tp"><Term>percentage completed</Term>
		<Definition>An earned value method in which a time phased budget amounts are released in proportion to the percentual progress of the project.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000368" Version="B60adoc1" ContextApps="tp"><Term>performed</Term>
		<Definition>The budgetted costs according to the progress at the end of the current period. In most cases, ERP calculates the performed as follows: performed = budgetted amount * progress</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="Phases.tp" Version="B60adoc1" ContextApps="tp"><Term>phase</Term>
		<Definition>In <GUIRef href="/baanerp/tp" role="package">Project</GUIRef>, a user-defined project subdivision. Typically, a phase consists of a number of project activities leading to a deliverable.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000359" Version="B60adoc1" ContextApps="tp"><Term>physical progress</Term>
		<Definition>The progress in amounts. This is different from percentage completion, which is the progress in time.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000059" Version="B60adoc1" ContextApps="tp"><Term>plan</Term>
		<Definition>It is a version of an activity structure. You can maintain alternative plans for a project. The active plan is the plan you actually use.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000093" Version="B60adoc1" ContextApps="tp"><Term>planned invoice dates</Term>
		<Definition>The date on which you intend to print an invoice and send it to the customer.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000061" Version="B60adoc1" ContextApps="tp"><Term>planner</Term>
		<Definition>The person or organizational unit associated with a particular project plan.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="PlanniPackag.tp" Version="B60adoc1" ContextApps="tp"><Term>planning package</Term>
		<Definition>A type of activity. Planning packages are identified during planning to time phase major activities within a project cost account. You cannot book costs on this activity type.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000354" Version="B60adoc1" ContextApps="tp"><Term>posting types</Term>
		<Definition>An indication of the entry origin or how the entry is posted to <GUIRef href="/baanerp/tf" role="package">Financials</GUIRef>. Read for entry: transaction, revenue, order, and costs, and so</Definition>
		<SimpleSection><Paragraph>on.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000318" Version="B60adoc1" ContextApps="tp"><Term>price policy</Term>
		<Definition>You can use the price policy to calculate the equipment, item and subcontracting cost price or the purchase price. The sundry costs cost object does not use this policy and labor has its own price search path.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000365" Version="B60adoc1" ContextApps="tp"><Term>primary structure</Term>
		<Definition>The only structure, linked to the estimate version, that can be used to calculate the estimate. This structure is used to check the top-down constraints (if any). The primary structure is one of two structures that you can use to sort estimate lines. Alternatively, you can use the sort structure to sort estimate lines.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000317" Version="B60adoc1" ContextApps="tp"><Term>production progress</Term>
		<Definition>The (part of) the project or resource that is comleted or used.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000115" Version="B60adoc1" ContextApps="tp"><Term>profit fee</Term>
		<Definition>In a time-phased budget version, the profit retained by the company that performs the project. The profit fee is expressed as follows: profit fee = contract amount - management reserve + distributed budget + undistributed budget</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="Progress.tp" Version="B60adoc1" ContextApps="tp"><Term>progress</Term>
		<Definition>The process by which an element or activity is completed over the lifetime of the project. Progress can be recorded at cost type, cost object, or at control code level.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000088" Version="B60adoc1" ContextApps="tp"><Term>progress invoice</Term>
		<Definition>An invoicing method based on progress for elements and activities. The difference with unit rate is twofold.</Definition>
		<SimpleSection><List><ListIntro>Unit rate has:</ListIntro>
				<ListItem>Invoices through installments.</ListItem>
				<ListItem>Invoices settled with the contract amount.</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000090" Version="B60adoc1" ContextApps="tp"><Term>progress motivation lines</Term>
		<Definition>A line or specification in progress-based invoicing. Motivation lines or specifications form the basis for an installment. Motivation lines or specifications contain all the billable amounts and quantities.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000008" Version="B60adoc1" ContextApps="tp"><Term>progress results</Term>
		<Definition>The output from progress registration while a project is in progress. You can switch interim results on or off by project or by cost object within a project. If you switch it off, you can only report completed.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000063" Version="B60adoc1" ContextApps="tp"><Term>project</Term>
		<Definition>An endeavor with a specific objective to be met within the prescribed time and financial limitation, and that has been assigned for definition or execution.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000337" Version="B60adoc1" ContextApps="tp"><Term>project budget</Term>
		<Definition>The budget you work in. Control budget is the frozen budget where progress registration, customer invoicing, cost control, and input for project requirements planning are found. The purchase budget is also derived from the project budget.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000338" Version="B60adoc1" ContextApps="tp"><Term>project cost account</Term>
		<Definition>The only type of activity that can be linked to an organization breakdown structure. At this level functional responsibility for work and costs can be assigned. You can detail short-span jobs in project cost accounts and use it for the execution of a project.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000036" Version="B60adoc1" ContextApps="tp"><Term>project currency</Term>
		<Definition>If the project is performed in another country, the project currency is useful for monitoring. This currency can be an external currency that is not specified as one of the home currencies.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000087" Version="B60adoc1" ContextApps="tp"><Term>project status</Term>
		<Definition>The way to characterize a project. ERP distinguishes the following statuses:</Definition>
		<SimpleSection><List><ListItem>Free: a project definition has been recorded, but the project has not yet been executed. Changes are still possible.</ListItem>
				<ListItem>Active: during the execution of a project you can release, purchase, and register cost transactions.</ListItem>
				<ListItem>Finished: the project is completed but it has not (yet) been financially closed. You can still register cost transactions. Actual purchase orders cannot be present for the project.</ListItem>
				<ListItem>Closed: the project has been financially closed, the project definition can no longer be changed.</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000097" Version="B60adoc1" ContextApps="tp"><Term>project type</Term>
		<Definition>A way to characterize projects.</Definition>
		<SimpleSection><List><ListIntro>A project can have one of the following types:</ListIntro>
				<ListItem>Main project: the project structure is composed of subprojects</ListItem>
				<ListItem>Subproject: the project is a subproject to a main project</ListItem>
				<ListItem>Single project: the project is a stand-alone project and is not part of a main project/subproject structure</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000353" Version="B60adoc1" ContextApps="tp"><Term>project warehouse</Term>
		<Definition>A warehouse that only stores goods that are used for projects. In contradiction to a normal warehouse goods are administrated for a project and its details. The goods in the default project warehouse represent inventory value. The inventory value of a project warehouse is not part of the project costs. When the goods are transferred to the project, they add to the project costs. A project warehouse can be used by one or more projects.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000103" Version="B60adoc1" ContextApps="tp"><Term>provisional amount</Term>
		<Definition>An extension type that you must use if you are not sure of a certain part of the project costs when you develop your project. Settle the differences with the provisional-amounts budget and the actual costs at a later stage. <GUIRef href="" role="manual">Example</GUIRef>: You are building a house with a standard kitchen costing $ 10,000, which is the provisional amount. When the house is almost finished, the customer determines on a more expensive kitchen, which brings the actual costs to $ 12,000. The customer is invoiced for the extra costs of $ 2,000.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000313" Version="B60adoc1" ContextApps="tp"><Term>purchase budget</Term>
		<Definition>A budget which defines a particular demand on a more detailed level than defined in the bottom-up budget. You can also use this to purchase cost objects with a manual order system.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="PurchaBudget.tp" Version="B60adoc1" ContextApps="tp"><Term>purchase budget lines</Term>
		<Definition>A set of budget lines selected from the project budget to buy certain cost objects that are needed to carry out a project.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000002" Version="B60adoc1" ContextApps="tp"><Term>purchase contract</Term>
		<Definition>An agreement with a supplier for the supply of goods or services.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000010" Version="B60adoc1" ContextApps="tp"><Term>purchase price</Term>
		<Definition>The price at which you buy cost objects expressed in the currency in which you bought them.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000340" Version="B60adoc1" ContextApps="tp"><Term>quantities-to-be-settled</Term>
		<Definition>An extension type, which enables you to invoice the difference between the budgeted quantity and the actual quantity for a range of cost objects. Use this type when you are unsure of the quantities that you will spend in the project.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000341" Version="B60adoc1" ContextApps="tp"><Term>requirements list</Term>
		<Definition>The relation that a project has to sales-order lines or sales-quotation lines. The requirement list is created in <GUIRef href="/baanerp/tp" role="package">Project</GUIRef> and triggers the supply chain of order processes.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000314" Version="B60adoc1" ContextApps="tp"><Term>requirements planning</Term>
		<Definition>A SSA ERP package that plans the orders and transfers them to other SSA ERP packages to fulfill the project requirements.</Definition>
		<SimpleSection><List><ListIntro>In the planning you can generate:</ListIntro>
				<ListItem>A project requirement plan to procure material, equipment, and subcontracting, or to collect materials from warehouses</ListItem>
				<ListItem>A requirement list used for manufactured items produced on order</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000303" Version="B60adoc1" ContextApps="tp"><Term>resource-limited scheduling</Term>
		<Definition>A scheduling method in which you cannot overload your resources. This method is prone to project delay.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000035" Version="B60adoc1" ContextApps="tp"><Term>responsibility</Term>
		<Definition>A liability on an individual or groups to perform assigned actions.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="RevenuCode.tp" Version="B60adoc1" ContextApps="tp"><Term>revenue code</Term>
		<Definition>A way to categorize invoiced amounts of the same invoice type in order to analyze revenue history.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000377"><Term>revenue recognition</Term>
		<Definition>For a given contract, revenue recognition is the process that leads to the calculation (and subsequent posting to the General Ledger) of the total revenue that is estimated to have been ‘earned’, on the basis of the progress of the contract.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000342" Version="B60adoc1" ContextApps="tp"><Term>routing operation</Term>
		<Definition>A routing line that specifies the work center, the duration, and set-up times of a <GUIRef href="/baanerp/ti" role="package">Manufacturing</GUIRef> task.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000012" Version="B60adoc1" ContextApps="tp"><Term>sales rate</Term>
		<Definition>The price or rate of cost objects, elements or activities, at which you sell, that are used for your project.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000307" Version="B60adoc1" ContextApps="tp"><Term>sales-order project</Term>
		<Definition>A type of project for which the invoicing and the delivery of goods is carried out in the Sales Control (SLS) module of <GUIRef href="/baanerp/td" role="package">Order Management</GUIRef>. A sales order project is mostly used for product-based projects and is generated from sales orders.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000351" Version="B60adoc1" ContextApps="tp"><Term>schedule variance</Term>
		<Definition>Any difference between the scheduled completion of an activity and the actual completion of that activity. Synonym: BCWP - BCWS</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000344" Version="B60adoc1" ContextApps="tp"><Term>scope change</Term>
		<Definition>Any change to the project scope. A scope change almost always requires an adjustment to the project cost or schedule. A scope change results in more or in less work to be invoiced.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000001" Version="B60adoc1" ContextApps="tp"><Term>search key</Term>
		<Definition>An alternative form of a description used for convenience during searching. Typically, it is an abbreviation, an acronym, or a mnemonic alternative to a full description.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000371" Version="B60adoc1" ContextApps="tp"><Term>sort structure</Term>
		<Definition>A structure that you can use to sort the estimate lines if the amount of estimate lines requires sorting.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000345" Version="B60adoc1" ContextApps="tp"><Term>start and end date percentage</Term>
		<Definition>A earned value method in which percentages are assigned to the start and end of the activities. In other words, at the start of the activity, it is assumed that a particular percentage of the project is completed. Consequently, time phased budget amounts are released based on these percentages.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000370" Version="B60adoc1" ContextApps="tp"><Term>structural element</Term>
		<Definition>A generic term for a project estimate structure element that can have a number of structure types, such as a project element, activity, cost type, an organization breakdown structure element, or an element of a reporting structure. A primary structure element is part of the primary structure that is linked to the estimate version.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000073" Version="B60adoc1" ContextApps="tp"><Term>subcontracting</Term>
		<Definition>A type of cost object representing services purchased from a third party for use in a project.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="SufferTax.tp" Version="B60adoc1" ContextApps="tp"><Term>sufferance tax</Term>
		<Definition>A tax or levy that is payable to a local or municipal authority to compensate for a disruption caused for the duration of a project. For example, a compensation for removing a sidewalk or part of a street to install the water pipes or sewer while constructing a high-rise apartment building.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="SundryCosts.tp" Version="B60adoc1" ContextApps="tp"><Term>sundry costs</Term>
		<Definition>Indirect cost and costs that do not belong to other cost types are booked as sundry costs, for example, insurance costs.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="Surcharges.tp" Version="B60adoc1" ContextApps="tp"><Term>surcharge</Term>
		<Definition>A means of defining indirect project costs. Typically, surcharges are used to cover general overhead costs, including storage, handling, and maintenance costs, management overheads and so on. Surcharges are calculated as a percentage of direct costs and are posted to a sundry-cost object. Surcharges can be calculated based on costs, budgets and revenues.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000308" Version="B60adoc1" ContextApps="tp"><Term>templates for projects</Term>
		<Definition>A user-friendly way to define a project.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000099" Version="B60adoc1" ContextApps="tp"><Term>terms of payment</Term>
		<Definition>The average number of days from the date on which goods or services are ordered and the date on which they are paid.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="ThirdPartie.tp" Version="B60adoc1" ContextApps="tp"><Term>third party</Term>
		<Definition>A person or organization with an indirect or noncontractual interest in a project, for example,: a government body or regulatory agency.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000304" Version="B60adoc1" ContextApps="tp"><Term>time-limited scheduling</Term>
		<Definition>A planning that implies that you cannot delay the project past its current finish date, even if this means overloading your resource.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="TimePhBudget.tp" Version="B60adoc1" ContextApps="tp"><Term>time-phased budget</Term>
		<Definition>A type of budget that is phased and spread out over a period of time. In SSA ERP there are various ways to plan the activities and look at the earned value. The earned value method determines how the budget amounts are released and how the budgeted cost of work scheduled (BCWS) is calculated.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000358" Version="B60adoc1" ContextApps="tp"><Term>top down budget version</Term>
		<Definition>A version is made to be able to track changes in the course of a project budget. More than one version can be defined for a top down budget to support a long-term project. One version of the top down budget will be actual. A version can be closed, which means that no changes can be made to the version data.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000083" Version="B60adoc1" ContextApps="tp"><Term>top element</Term>
		<Definition>The highest element in the multilevel hierarchy of an element structure. The top element is used in the project definition to link the element structure to the project.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000311" Version="B60adoc1" ContextApps="tp"><Term>top-down budget</Term>
		<Definition>A budget method that divides the exacted project amount over the project structure from top to bottom.</Definition>
		<SimpleSection><Paragraph>This budget method is used to time-phase the available budget amount across activities. Top-down budgeting supports different earned value methods.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="TradeGroups.tp" Version="B60adoc1" ContextApps="tp"><Term>trade group</Term>
		<Definition>A group of resources with common skills that can be used for a particular labor cost object. If you cannot yet make detailed assignments for employees, you can use trade groups for scheduling.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="TransaDate.tp" Version="B60adoc1" ContextApps="tp"><Term>transaction date</Term>
		<Definition>The date on which the planned order was last changed.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000118" Version="B60adoc1" ContextApps="tp"><Term>undistributed budget</Term>
		<Definition>The project-budget part that is not yet distributed over the elements. You can look at an undistributed budget on various levels: For version: The undistributed budget equals the contract amount - profit fee - management reserve - distributed budget For activity: The undistributed budget equals the budget amount - distributed budget</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000080" Version="B60adoc1" ContextApps="tp"><Term>unit of measure</Term>
		<Definition>The unit of measure for the cost object. This unit can affect how budget line quantities are calculated.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="UnitRate.tp" Version="B60adoc1" ContextApps="tp"><Term>unit rate</Term>
		<Definition>An invoicing method based on the progress and element or activity sales rate per unit. Invoices are booked against the contract amount with installments.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000372" Version="B60adoc1" ContextApps="tp"><Term>User Defined</Term>
		<Definition>A filtering status that determines whether sales or cost line amounts are used in the calculation of the estimate totals, and whether the line is included in the scope of the estimate.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000085" Version="B60adoc1" ContextApps="tp"><Term>WBS element</Term>
		<Definition>A type of activity. Usually used to break down the project scope into smaller pieces. You can define work for a work-break-down structure element. You can aggregate the costs from project cost accounts or work packages. You cannot book costs on this activity type.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000300" Version="B60adoc1" ContextApps="tp"><Term>WKA</Term>
		<Definition>A Dutch law which dictates that a contractor is liable to pay for a subcontractor's taxes and social security contributions.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000378"><Term>work authorization status</Term>
		<Definition>A formal authorization procedure to begin work on a specific activity. The process helps ensure that the authorized work is done at the right time and in proper sequence.</Definition>
		<SimpleSection><Paragraph>Work authorization status can have the following values:</Paragraph>
			<List><ListItem><GUIRef href="" role="manual">Free</GUIRef>: Work is not authorized for execution.</ListItem>
				<ListItem><GUIRef href="" role="manual">Released</GUIRef>: Work is sanctioned for execution. This status is allowed only for activities under a leading plan and for elements which are part of the leading structure. The parent activity/element and the activity type cannot be changed.</ListItem>
				<ListItem><GUIRef href="" role="manual">On Hold</GUIRef>: Work is under execution and needs to be suspended due to some constraints. The parent activity/element and the activity type cannot be changed.</ListItem>
				<ListItem><GUIRef href="" role="manual">Finished</GUIRef>: Work is executed. The parent activity/element and the activity type cannot be changed.</ListItem>
				<ListItem><GUIRef href="" role="manual">Closed</GUIRef>: Work is completed and all related financial transactions are closed. The parent activity/element and the activity type cannot be changed.</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="WorkBreakdSt.tp" Version="B60adoc1" ContextApps="tp"><Term>work breakdown structure</Term>
		<Definition>The top layer of the activity structure. The WBS can consist of a hierarchy of activities of the WBS element type.</Definition>
		<SimpleSection><Paragraph>Abbreviation: WBS</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="WorkPackag.tp" Version="B60adoc1" ContextApps="tp"><Term>work package</Term>
		<Definition>A type of activity. You can detail short-span jobs in work packages and use it for the execution of a project.</Definition>
	</GlossaryEntry>
</Glossary>
