About Cost, Hours and Revenue Reported to Activity

Costs, hours and revenue can be reported to an activity from a wide range of connected objects, e.g. Purchase Orders, Shop Orders, Work Tasks, Sales Contracts, Document Packages, Tasks, Resources etc. (Refer to the document "About Activity Connections" for a complete list of objects). As the connected objects are planned and executed, values of cost, hours and revenue are reported back to the activity.

The cost and revenue values will always be reported from the connected objects in base and transaction currency. If multi-currency and/or project currency have been enabled for Budgeting and Forecasting purposes for the project, then cost and revenue will also be reported in base currency using the fixed Budgeting and Forecasting rate and/or the project currency. The values are displayed in base currency on all pages where cost and revenue are available, while the other currencies are displayed only in the Project Connections page.

Note: This document explains how different objects report cost, hours or revenue to an activity, refer to the tables below for detailed information about each object. For information on how connected objects retrieve progress and earned value, refer to the "About Earned Value and Progress" documentation.

Cost/Hours

Connected objects can report cost and hours information to the activity. The type of information retrieved depends on the connected object. The information is reported using the project cost elements that are defined for the connected object. The cost/hours information can be viewed for each activity in the Cost and Hours tabs in the Activity Monitoring page. It is also possible to view cost/hours per sub project or for the whole project in the Sub Project Monitoring and Project Monitoring pages respectively. In the Activity Monitoring page it is possible to view detailed information about the connected objects.

The possible stages of cost/hours values are:

Estimated
Estimated values represent the approximate values of cost or hours before the planning phase of the activity is carried out. Estimates are manually entered in the Estimates tab.
Planned
Planned values represent the current budget which is valid for the activity. Planned values are retrieved from various connected objects. For example, you can use tasks or document packages to define planned values, and these values will be summarized and displayed in the Planned columns. The values in the planned columns will be updated immediately when you change, add or remove objects that report planned cost/hours to the activity. You can also retrieve planned costs and hours from other sources by selecting a relevant Planned Cost Driver for the activity.
Baseline
Baseline values represent the current approved budget which is valid for the activity. Use this column to keep track of the original approved plan, with or without approved scope changes. After a baseline has been created for a project the values entered in the Planned fields will be copied to the Baseline columns. If the planned values are changed thereafter, another baseline will have to be created for the new planned values to be reflected in the Baseline columns.
Planned Committed
Planned committed values are the sum of cost or hours from connected purchase requisitions lines, purchase order lines, shop order requisition lines and shop order lines that have not been released yet.
Committed
Committed values are the sum of remaining costs/hours reserved or ordered by the objects connected to the activity. The total Committed value is reported first when the object reaches a status which commits its values (i.e. Released status on a Purchase Order) and decreases as Used values are reported from each connected object. For a connected purchase order, the committed value will be based on the remaining quantity to be received. For a connected shop order, the committed cost of material will be based on the quantity remaining to be issued, and the committed cost of work and hours will be based on the status and progress of the operation.
Used
Used values are the sum of costs/hours that have been used, as reported from each connected object. Used cost/hours are reported from the transactions (Inventory, Purchase, Operation or Project) created by the object until these are transferred to IFS/Accounting Rules and the corresponding voucher is created. Once a transaction receives the Transferred status it will stop reporting Used Cost/Hours and the voucher will report the Used Cost/Hours instead. Voucher rows that are created and pre-posted with the Project and Activity Sequence will always report Used cost. The utilized hours will be displayed in the Actual Hours field.
Actual
Actual cost is the sum of costs that have actually been used and is reported from the General Ledger (through General Ledger Voucher Row). Actual hours are the hours that have been reported as used, from each object.

Revenue

Connected objects can report revenue information to the activity. The type of information retrieved depends on the connected object. The information is reported using the project revenue elements that are defined for the connected object. The revenue information can be viewed for each activity in the Revenue tab on the Activity Monitoring page. It is also possible to view revenue per sub project or for the whole project in the Sub Project Monitoring and Project Monitoring pages respectively. In the Activity Monitoring page it is possible to view detailed information about the connected objects

The possible stages of revenue values are:

Estimated
Estimated revenue is a speculated approximate amount of revenue that is expected to be generated from the activity. This value is entered before the activity has been properly planned. Estimates are manually entered in the Estimates tab.
Planned
Planned revenue represents either the budgeted values from an object (e.g. Invoicing Plan or Sales Contract Lines) or values generated through cost objects (e.g., Project Transactions) which have a sales price. The value in the planned columns will be updated immediately when you change, add, or remove objects that report planned revenue to the activity.
Preliminary
Preliminary revenue is always generated from a preliminary invoice.
Posted
Posted revenue is always generated from a Hold Table Voucher.
Actual
Actual revenue is always generated from a General Ledger Voucher and will also replace the value in the posted column.

Reporting

Planned Cost Driver

The Planned Cost Driver determines from where the Planned Cost and Planned Hours are retrieved. When the Planned Cost Driver for the activity is:

Connected Objects - The planned cost and hours of the activity are retrieved from the objects that are connected to the activity as described in the table below, excluding values from Activity Estimates.
Estimated Cost - The planned cost and hours of the activity are retrieved only from Activity Estimates. Values other than Planned are retrieved according to the table below.
Activity Resources - The planned cost and hours of the activity are retrieved only from the resources allocated to the activity. Values other than Planned are retrieved according to the table below.

Baseline Cost and Hours

All objects that report planned cost or hours will also contribute to Baseline costs and hours when a baseline is set for the project. The Baseline values are copied from the Planned values.

The following tables show how the different objects report cost, hours or revenue information to the activity. Any object which reports any type of cost, hours and revenue to projects will report these values on a cost/revenue element.

Cost, Hours and Revenue Progression of Project Connected Objects

The following tables display the cost, hours and revenue progression for various project-connected objects as they move through different stages during the planning and execution of the project. Any object reporting these values to projects will do so on a cost/revenue element.

There are three tables to display the progression:

Cost and Hours Progression
Cost Progression for Customer Orders with various Supply Options
Revenue Progression.

Cost and Hours Progression

Activity Estimates

Activity Estimates are presented here and not in the table.

Estimated values are taken from the Estimated Cost or Estimated Hours field in the Activity Scope and Schedule/Estimates tab.
Estimated values are reported from the Compatible Unit Estimated Revision given that the Estimated Revision option is enabled. Estimates from the Compatible Unit, Execution Item is reported to the Activity Estimate object connection.

Object	Object Details	Planned	Planned Committed	Committed	Used	Actual
Project Tasks		Planned values are taken from the Planned Cost or Planned Hours field in *Tasks* tab.
Activity Resources		Planned values are taken from the Planned Cost and Planned Hours fields in the Activity Resource Planning/Planning tab. The values are calculated based on the cost associated with the Resource and are updated when planned hours are entered
Document Package		Planned values are taken from the Cost and Hours fields in the Document Package page.
Change Order		Values are taken from the Planned Cost and Planned Hours fields in Change Order Actions page.
Design Object		Planned values are taken from the Total Planned Cost and Total Planned Hours fields on the *Design Object Project Connections* page.
Project Misc. Demand	Supply Option: Purchasing	For a Purchase Part/No Part/Inventory Part requirement line, the planned cost is taken from the Planned Cost field in Planned Cost/Hours per Cost Element assistant (Cost Elements option from the command menu) and summed up to the Total Planned Cost field. Planned Cost is retrieved in the following order: Expected Supplier Price per Unit Costing Inventory Value Estimated Cost For a Purchase Part/Inventory Part requirement line, the planned hours are taken from the Planned Hours field in the Planned Cost/Hours per Cost Element assistant (Cost Elements option from the command menu) and summed up to the Hours Planned field. Hours of Purchase No Part requirement line will follow the same method as above and will not be summed up.
	Supply Option: Shop Order	The planned values are calculated based on part costing, depending on the posting control setup. Cost set 1 values should exist in part costing in order to get the project planned cost. Cost of the non-standard planned components are excluded from the planned cost. Non-Std. Planned items must be entered separately on the Miscellaneous Demand line for both cost and hours. Planned hours are taken from the routing defined for the shop order in *Shop Order Operations* page.
	Supply Option: PMRP / DOP	The planned values are calculated based on part costing, depending on the posting control setup. Cost set 1 values should exist in part costing in order to get the project planned cost. These supply options use the full BOM (Bill of Material) costing for creating planned values.
	Direct Issue from Inventory	When a miscellaneous demand for a part is entered.			When items are issued from standard inventory, or from project inventory (depending on the Material Allocation flag on the project). The cost is updated by the Inventory value.	When the voucher created upon transfer of transaction has been updated in General Ledger.
	Rental Charging	For a rental part requirement line, the planned cost is taken from the Planned Cost field in the *Planned Cost/Hours per Cost Element* assistant (Cost Elements option from the command menu) and summed up in the Total Planned Cost field. Planned cost is retrieved in the following order: Expected Supplier Price per Unit. Costing Inventory Value. Estimated Cost. The expected supplier price per unit is only used as the planned cost and is not transferred to the purchase requisition. The order quotation functionality is not supported for miscellaneous rental parts.	When releasing the Purchase Requisition (PR) and creating the Purchase Order (PO), the Planned Committed Cost will transfer to the Purchase Order Line Part.	When the PO is released.	When rental events and rental transactions have been generated.	When the voucher created upon transfer of transaction has been updated in General Ledger.
Forecast Demand		Purchase Part: For a Purchase Part/Inventory Part requirement line the cost is calculated the same way it is done for Misc. Demand/Misc. Part. Planned Cost is retrieved in the following order: Expected Supplier Price per Unit Costing Inventory Value Estimated Cost and is saved in the Activity Materials and Services page. Manufacturing Part: For a Manufactured Part the cost is calculated the same way it is done for Misc. Demand/Shop Order. If the structure contains other forecasted parts, these will not be included in the planned value. They will have to be entered separately. The values are saved in the Activity Materials and Services page.
Compatible Unit	Execution Item	Planning is done on the Execution Item in the Compatible Unit Navigator. The Compatible Unit must be released to report the planned cost to the activity. Work is executed from the Work Order. If the Work Order planning originates from a Compatible Unit, the Report Planned Cost toggle is not enabled. In the *Compatible Unit Navigator/Work List/Resources tab, enter a line for a resource (Person or Tool/Equipment) with a defined cost rate. In the Compatible Unit Navigator/Work List/Materials* tab, create a line for a Part and specify the quantity required. This applies to parts with the supply code Invent Order and Project Inventory. For non-inventory purchase parts, in the *Compatible Unit Navigator/Work List/No Part Requisition* tab, create a line for a non-inventory Part/No Part and specify the units required.
Compatible Unit	Procurement Activity	Planning is done on the Execution Item in the Compatible Unit Navigator. The Compatible Unit must be released to report the planned cost to the activity. The procurement process that follows is done via PMRP. In the *Compatible Unit Navigator/Work List/Materials* tab, create a line for a Part and specify the quantity required. This applies to parts with the supply code Project Inventory.
Work Task		Work tasks are planned on a Work Order. In the *Work Task/Resources, enter a line and select the demand type: Persons, Crew* or Tool/Equipment. Enter a resource group and/or a resource with a defined cost rate. The resource must be a Maintenance resource. The planned values will be held by the work task object. In the *Work Task/Material* ta tab, create a material requisition line and specify the quantity required. The supplier price is the planned value, held by the purchase requisition object. For parts, the supply code can be Invent Order or Project Inventory: For supply code: Inventory Order, the planned cost is taken as the Inventory value. The demand will be included in the MRP demand/supply calculation. For supply code: Project Inventory, the supplier price is taken as the planned cost for the demand as it will be procured through the project. The demand will be included in the PMRP demand/supply calculation. The planned values will be held by the work task object. To enter a purchase requisition, select the New Maintenance Purchase Requisition from the Purchasing command on the Work Task. Enter a line for a Part/No Part and specify the quantity required. The supplier price is taken as the planned value. The planned values will be held by the purchase requisition object. In the Prepare Work Task/Planning tab, create a line for cost type External or Expenses and specify the quantity and cost required. The planned values are held by the work task object.	When a purchase requisition line is added for a Part/No Part, the planned committed cost is reported by the purchase requisition line object. Note: When a Purchase Order is created from the Purchase Requisition, the reporting of the planned committed cost is inherited by the purchase order line. When the purchase order line is created for the Part/No Part and is in Planned status, the planned committed cost is reported by the purchase order line object.	When releasing the Work Task, the work task object reports committed cost and hours for: Resources (Persons, Tool/Equipment) External Expenses Material Requisition Lines with supply code Invent Order.	Report time on the operations in the *Work Task/Time Reports* tab. When time is reported for a resource of type Person in the *Work Task/Time Reports* tab, the Used Cost is reported by the work task object. When time is reported for a resource of type Tool/Equipment in the *Work Task/Time Reports* tab, the Used Cost is reported by the work task object. When cost is reported for External and Expenses in the *Work Task/Costs* tab, the Used Cost is reported by the work task object. When material with the supply code Invent Order is issued in the *Work Task/Materials* tab, the Used Cost is reported by the work task object. When the Purchase Order Line for a Part/No Part has been received, the Used Cost is reported by the purchase order line object. When the Purchase Order is matched with a Manual Supplier Invoice, the Used Cost is updated by the voucher created when the invoice is posted.	When time is reported for a resource of type Person in the *Work Task/Time Reports* tab. Used/Actual hours is reported by the work task object. When hours is reported for a resource of type Tool/Equipment in the Work Task/Time Reports tab. Used/Actual hours is reported by the work task object.
Request Work Task		Request work tasks are planned on a Request for service. In the *Request Work Task/Resources, enter a line and select the demand type: Persons, Crew, or Tool/Equipment. Enter a resource group and/or a resource that has a defined cost rate. The resource must be defined as a Service resource. The planned values will be held by the work task object. In the Request Work Task/Material* tab, create a requisition line for material, requisition or shipment and specify the quantity required. The supplier price is taken as the planned value. The planned values will be held by the purchase requisition object. The selected supply code determine how the demand is supplied: For supply code: Inventory Order, the planned cost is taken as the Inventory value. The demand will be included in the MRP demand/supply calculation. For supply code: Project Inventory, the supplier price is taken as the planned cost for the demand as it will be procured through the project. The demand will be included in the PMRP demand/supply calculation. The planned values will be held by the work task object. For supply code: Purchase Order, enter a line for a Part/No Part and specify the quantity required. The supplier price is taken as the planned value. The planned values will be held by the purchase requisition object. For supply code: Shipment Order, the planned cost is taken as the Inventory value. In the *Request Work Task/Planned Cost and Sales* tab, create a line for either cost type External or Expenses and specify the quantity and cost required. The planned values are held by the work task object.	Planned committed cost is reported for the purchase flow. When the purchase requisition line is added for a Part or No Part, the planned committed cost is reported by the purchase requisition line object. Note: When a Purchase Order is created from the Purchase Requisition, the reporting of planned committed cost is inherited by the purchase order line. When the purchase order line is created for the Part and it is in Planned status, the planned committed cost is reported by the purchase order line object.	When the Request is released, the associated work task is also updated to released status. The work task object reports committed cost and hours for: Resources (Persons, Tool/Equipment) External Expenses Material Requisition Lines with supply code Invent Order. When reserving Material for the material line with supply code: Shipment Order.	When time is reported on the *Request Work Task/Time Reports* tab for a resource of type Person, Crew or Tool/Equipment, the Used Cost is reported by the work task object. When cost is reported for External and Expenses in the *Request Work Task/Planned Cost and Sales* tab, the Used Cost is reported by the work task object. Material requisitions: When material with the supply code Invent Order is issued in the *Request Work Task/Materials* tab, the Used Cost is reported by the work task object. Purchase Orders Receiving Parts: When the Purchase Order Line for a Part has been received, the Used Cost is reported by the purchase order line object. Invoice Matching: When the Purchase Order is matched with a Manual Supplier Invoice, the Used Cost is updated by the voucher created when the invoice is posted. When the Shipment Order is delivered.	Time is reported in the *Request Work Task/Time Reports* tab. When time is reported for a resource of type Person, the Used/Actual hours are reported by the work task object. When hours are reported for a resource of type Tool/Equipment in the, the Used/Actual hours are reported by the work task object.
Planning Item		The value is taken from the Project Deliverables Design /Cost/Hours tab.			When issuing standard planned items from Inventory.
Customer Order Line		Cost and hours are retrieved from the connected objects, depending on the supply option. Sales Overhead is retrieved from the sales overhead cost calculated for part in Part Cost.		Updated by subsequent supply orders when they are released. Sales Overhead cost is retrieved from Part Cost.	Updated by subsequent supply orders when they are further processed – refer to the relevant object type in this table.
Purchase Requisition Line	Part / No Part		When a PR line is added for a Part/No Part/Rental Part and then released.
Purchase Order Line	Part/ No Part/ Rental Part		When a PO line is created for the Purchase Part/No Part/Rental Part and is in Planned status.	When the order for a Purchase Part/No Part/Rental Part has been released.	When the order for a Purchase Part/No Part has been received. When rental events and rental transactions have been generated for the Rental Part.	When the voucher created upon transfer of transaction has been updated in General Ledger.
Purchase Order Change Order	Part / No Part		The delta (in value) between the current purchase order and the active change order (includes statuses Planned, Released, Authorized) for Part/No Part/Rental Part.			When the voucher created upon transfer of transaction has been updated in General Ledger.
Shop Order Requisition			When a shop order requisition line is added for a part through Project Material Requirements Planning (PMRP) or Project Master Scheduling (Project MS)
Shop Order			When the shop order is in Planned state. Values are taken from the Planned Cost field in the Shop Orders Project Cost Analysis page.	When the Shop Order is released. Values related to operations are taken from the routing defined for the shop order (Shop Order Operation page) When the Shop Order is released. Values related to material are taken from the Shop Order components and Shop Order Costing (Shop Order Costs page) When the Shop Order is released. Values related to Subcontracting are taken from the Shop Order routing and Shop Order Costing. When the Shop Order is released. Overhead values will be taken if General Overheads are defined in Part Cost tab.	Hours are updated when reporting time on the Shop Order. Updated when reporting time and issuing material to the Shop Order.	When the voucher created upon transfer of transaction has been updated in General Ledger.
DOP Header				Reported from connected DOP orders (SO, PO) through the DOP Header.	When hours are Reported from connected DOP orders supply (SO, PO) through the DOP header. Reported from connected DOP order supply (SO, PO) when it is further processed through the DOP Header; refer to the relevant object type in this table. Note! When Transactions have been transferred the used costs are displayed under the voucher rows connections instead of under the DOP header connection.	Reported from connected DOP orders supply (SO, PO) when it is further processed all the way to voucher creation upon transfer of related transactions updated in the General Ledger through the DOP header. Refer to the relevant object type in this table. Note: When Update GL Vouchers has been run, the actual costs are displayed under the General Ledger Voucher Row connections.
Material Requisition Line				When the part is Reserved. For parts with Supply Code = Inventory Order.	When the part is Issued. For parts with Supply Code = Inventory Order.	When the voucher created upon transfer of transaction has been updated in General Ledger.
Project Transaction	Time Reporting			When time is reported on an activity.	When the transactions are confirmed and the value in the Create Cost Accounting field of the Report Code is either Yes or No, Update Project Cost.	When the voucher created upon transfer of transaction has been updated in General Ledger.
Project Transaction	Cost Reporting				When cost is registered in the Project Time and Cost Registration page.	When the voucher created upon transfer of transaction has been updated in General Ledger.
Project Inventory Transfer					When the quantity has been transferred from one project inventory to the present project inventory; the original project inventory decreases in cost.	When the voucher created upon transfer of transaction has been updated in General Ledger.
Sub Contract		Planned cost is reported before activating the revision when selecting the Report Planned Cost slider switch, and is updated when selecting the Update Planned Cost menu option. The planned cost is reported automatically when the revision is activated.	Planned committed cost is reported when call off values are entered on the sub contract. Planned call off amount is equal to the planned committed cost.	Committed cost is reported when the call off is released.
Voucher Row					When voucher rows are created that report cost to a project activity. Examples: When a manual voucher is created that reports cost to the project. When vouchers are created for different transactions, they replace the Used value reported from the originating transactions, e.g. inventory transactions that become MPL vouchers. When a supplier invoice is posted with a Project Id. When receiving and certifying a sub contract valuation.
General Ledger Voucher Row						When vouchers rows that report cost to project activities have been updated to General Ledger.

Cost Progression for Customer Orders with Various Supply Options

Cost and hours will be as follows for different supply options in Customer orders.

Note that all objects that report planned cost or hours will also contribute to Baseline costs and hours when a baseline is set for the project. The Baseline values are copied from the Planned values.

Supply Code	Planned	Planned Committed	Committed	Used
Inventory Order	Planned cost is retrieved in following hierarchy: 1. Cost set 1 values from IFS Costing. 2. Inventory value of the inventory part. 3. Estimated material cost of the inventory part. If a Sales Overhead is defined in *Part Cost* page for the particular part, it is also included in planned cost. Cost is reported through the connected Customer Order line.		Updated when subsequent supply orders are released. Cost for the Sales Overhead is reported under Customer Order to the connected activity.	Till delivery transactions are transferred, used cost is reported under Customer Order to the connected activity. After transferring transactions, used cost is reported under respective voucher rows.
Project Inventory	For manufacturing parts, cost is retrieved from part costing where as for purchased parts as in Purchase order Direct (inventory). If a Sales Overhead is defined in *Part Cost* page for the particular part, it is also included in planned cost. Cost is reported under Customer Order to the connected activity.		Updated when subsequent supply orders are released. Cost for the Sales Overhead is reported under Customer Order to the connected activity.	Till delivery transactions are transferred, used cost from Sales Overhead is reported under Customer Order to the connected activity. After transferring transactions, used cost is reported under respective voucher rows.
Purchase Order Direct (inventory)	Planned cost is retrieved in the following order of priority: 1. Price from Supplier agreement. 2. From price list tab in supplier for purchase part page. 3. Price per part from supplier for purchase part. 4. Cost set 1 values from IFS Costing. 5. Inventory value of the inventory part. 6. Estimated material cost of inventory part. If a Sales Overhead is defined in *Part Cost* page for the particular part, it is also included in planned cost. Cost is reported under Customer Order to the connected activity.	When order is created for the Purchase Part and is in the Planned status. Cost is reported under *Pur Req / Pur Order* to the connected activity.	When order for a Purchase Part has been released. Cost for the Purchase Order is reported under Pur Order to the connected activity. Cost for the Sales Overhead is reported under Customer Order to the connected activity.	Till delivery transactions are transferred, used cost is reported under Customer Order to the connected activity. After transferring transactions, used cost is reported under respective voucher rows.
Int. Purchase Order Direct 1 (inventory)	Planned cost is retrieved in the following order of priority: 1. Price from Supplier agreement. 2. From price list tab in supplier for purchase part page. 3. Price per part from supplier for purchase part. 4. Cost set 1 values from IFS Costing. 5. Inventory value of the inventory part. 6. Estimated material cost of inventory part. If a Sales Overhead is defined in *Part Cost* page for the particular part, it is also included in planned cost. Cost is reported under Customer Order to the connected activity.	When order is created for the Purchase Part and is in the Planned status. Cost is reported under Pur Req / Pur Order to the connected activity.	When order for a Purchase Part has been released. Cost for the Purchase Order is reported under Pur Order to the connected activity. Cost for the Sales Overhead is reported under Customer Order to the connected activity.	Till delivery transactions are transferred, used cost is reported under Customer Order to the connected activity. After transferring transactions, used cost is reported under respective voucher rows.
Int. Purchase Order Direct 2 Alt 3 (inventory)	Planned cost is retrieved in following hierarchy: 1.Cost set 1 values from IFS Costing. 2. Inventory value of the inventory part. 3. Estimated material cost of inventory part. If a Sales Over Head is defined in *Part Cost* page for the particular part, it is also included in planned cost. Cost is reported under Customer Order to the connected activity.	When order is created for the Purchase Part and is in the Planned status. Cost is reported under Pur Req / Pur Order to the connected activity.	When order for a Purchase Part has been released. Cost for the Purchase Order is reported under Pur Order to the connected activity. Cost for the Sales Overhead is reported under Customer Order to the connected activity.	Till delivery transactions are transferred, used cost is reported under Customer Order to the connected activity. After transferring transactions, used cost is reported under respective voucher rows.
Non-Inventory	Planed cost is retrieved from Cost field in *Non-Inventory Sales Part* page Cost is reported under Customer Order to the connected activity.		Updated when subsequent supply orders are released.	Till delivery transactions are transferred, used cost is reported under Customer Order to the connected activity. After transferring transactions, used cost is reported under respective voucher rows.
Project	No planned cost reported.	No planned committed cost reported.	No committed cost reported.	No planned cost reported.
Purchase Order Direct (non-inv)	Planned cost is retrieved in the following order of priority: > 1. Price from Supplier agreement. 2. From Price List tab in Supplier for Purchase Part page. 3. Price per part from Supplier for Purchase Part page. Cost is reported under Customer Order to the connected activity.	When order is created for the No Part and is in the Planned status. Cost is reported under Pur Req / Pur Order to the connected activity.	When order for a No Part has been released. Cost for the Purchase Order is reported under Pur Order to the connected activity.	Till arrival transactions are transferred, used cost is reported under Customer Order to the connected activity. After transferring transactions, used cost is reported under respective voucher rows.
Int. Purchase Order Direct 1 (non-inv)	Planned cost is retrieved in the following order of priority: 1. Price from Supplier agreement. 2. From price list tab in Supplier for Purchase Part page. 3. Price per part from Supplier for Purchase Part page. Cost is reported under Customer Order to the connected activity.	When order is created for the No Part and is in the Planned status. Cost is reported under Pur Req / Pur Order to the connected activity.	When order for the No Part has been released. Cost for the Purchase Order is reported under Pur Order to the connected activity.	Till arrival transactions are transferred, used cost is reported under Customer Order to the connected activity. After transferring transactions, used cost is reported under respective voucher rows.
Int. Purchase Order Direct 2 Alt 2 (non-inv)	Planned cost is retrieved in the following order of priority: > 1. Price from Supplier agreement. 2. From Price List tab in Supplier for Purchase *Part* page. 3. Price per part from Supplier for Purchase Part page. Cost is reported under Customer Order to the connected activity.	When order is created for the No Part and is in the Planned status. Cost is reported under Pur Req / Pur Order to the connected activity.	When order for a No Part has been released. Cost for the Purchase Order is reported under Pur Order to the connected activity.	Till delivery transactions are transferred, used cost is reported under Customer Order to the connected activity. After transferring transactions, used cost is reported under respective voucher rows.
Shop Order	Planed cost is retrieved from Cost set 1 values of IFS Costing. If a Sales Overhead is defined in Part Cost page for the particular part, it is also included in planned cost. Cost is reported under Customer Order to the connected activity.	When the shop order is in Planned state. Values are taken from the Planned Cost field in the *Shop Orders Project Cost Analysis* page.	When the shop order is in released state.	Till delivery transactions are transferred, used cost from Sales Overhead is reported under Customer Order to the connected activity. After transferring transactions, used cost is reported under respective voucher rows. Used Cost incurred in shop order is reported as a typical shop order.
DOP Order	Planed cost is retrieved from Cost set 1 values of IFS Costing. If a Sales Overhead is defined in *Part Cost* page for the particular part, it is also included in planned cost. Cost is reported under Customer Order to the connected activity.		When the DOP order is in released state.	Till delivery transactions are transferred, used cost from Sales Overhead is reported under Customer Order to the connected activity. After transferring transactions, used cost is reported under respective voucher rows. Used Cost incurred in DOP is reported as a typical DOP.
Purchase Order Transit (inventory)	Planned cost is retrieved in the following order of priority: 1. Price from Supplier agreement. 2. From Price List tab in Supplier for Purchase Part page. 3. Price per part from Supplier for Purchase Part page. 4. Cost set 1 values from IFS Costing. 5. Inventory value of the inventory part. 6. Estimated material cost of inventory part. If a Sales Overhead is defined in *Part Cost* page for the particular part, it is also included in planed cost. Cost is reported under Customer Order to the connected activity.	When order is created for the Purchase Part and is in the Planned status. Cost is reported under Pur Req / Pur Order to the connected activity.	When order for a Purchase Part has been released. Cost for the Purchase Order is reported under Pur Order to the connected activity. Cost for the Sales Overhead is reported under Customer Order to the connected activity.	Till delivery transactions are transferred, used cost from Sales Overhead is reported under Customer Order to the connected activity. After transferring transactions, used cost is reported under respective voucher rows. Same as Sales Overhead, used cost from Purchase order is reported under Pur Order to the connected activity till arrival transactions are transferred. After transferring, used cost is reported under respective voucher rows.
IntInt. Purch Order Trans 1 (inventory)	Planned cost is retrieved in the following order of priority: 1. Price from Supplier agreement. 2. From Price List tab in Supplier for Purchase Part page. 3. Price per part from Supplier for Purchase Part page. 4. Cost set 1 values from IFS Costing. 5. Inventory value of the inventory part. 6. Estimated material cost of inventory part. If a Sales Overhead is defined in *Part Cost* page for the particular part, it is also included in planned cost. Cost is reported under Customer Order to the connected activity.	When order is created for the Purchase Part and is in the Planned status. Cost is reported under Pur Req / Pur Order to the connected activity.	When order for a Purchase Part has been released. Cost for the Purchase Order is reported under Pur Order to the connected activity. Cost for the Sales Overhead is reported under Customer Order to the connected activity.	Till delivery transactions are transferred, used cost from Sales Overhead is reported under Customer Order to the connected activity. After transferring transactions, used cost is reported under respective voucher rows. Same as Sales Overhead, used cost from Purchase order is reported under Pur Order to the connected activity till arrival transactions are transferred. After transferring, used cost is reported under respective voucher rows.
Int. Purch Order Trans 2 Alt 3(inventory)	Planned cost is retrieved in following hierarchy: 1. Cost set 1 values from IFS Costing. 2. Inventory value of the inventory part. 3. Estimated material cost of inventory part. If a Sales Overhead is defined in *Part Cost* page for the particular part, it is also included in planned cost. Cost is reported under Customer Order to the connected activity.	When order is created for the Purchase Part and is in the Planned status. Cost is reported under Pur Req / Pur Order to the connected activity.	When order for the Purchase Part has been released. Cost for the Purchase Order is reported under Pur Req/Pur Order to the connected activity. Cost for the Sales Overhead is reported under Customer Order to the connected activity.	Till delivery transactions are transferred, used cost from Sales Overhead is reported under Customer Order to the connected activity. After transferring transactions, used cost is reported under respective voucher rows. Same as Sales Overhead, used cost from Purchase order is reported under Pur Order to the connected activity till delivery transactions are transferred. After transferring, used cost is reported under respective voucher rows.
Purchase Order Transit (non-inv)	Planned cost is retrieved in the following order of priority: 1. Price from Supplier agreement. 2. From price list tab in *Supplier for Purchase Part* page. 3. Price per part from Supplier for Purchase Part page. Cost is reported under Customer Order to the connected activity.	When order is created for the No Part and is in the Planned status. Cost is reported under Pur Req / Pur Order to the connected activity.	When order for a No Part has been released. Cost for the Purchase Order is reported under Pur Order to the connected activity.	Till arrival transactions are transferred, used cost is reported under Pur Order to the connected activity. After transferring transactions, used cost is reported under respective voucher rows.
Int. Purch Order Trans 1 (non-inv)	Planned cost is retrieved in the following order of priority: 1. Price from Supplier agreement. 2. From Price List tab in Supplier for *Purchase Part* page. 3. Price per part from Supplier for *Purchase Part* page. Cost is reported under Customer Order to the connected activity.	When order is created for the No Part and is in the Planned status. Cost is reported under Pur Req / Pur Order to the connected activity.	When order for a No Part has been released. Cost for the Purchase Order is reported under Pur Order to the connected activity.	Till arrival transactions are transferred, used cost is reported under Pur Order to the connected activity. After transferring transactions, used cost is reported under respective voucher rows.
Int. Purch Order Trans 2 Alt 2 (non-inv)	Planned cost is retrieved in the following order of priority: 1. Price from Supplier agreement. 2. From Price List tab in *Supplier for Purchase Part* page. 3. Price per part from *Supplier for Purchase Part* page. Cost is reported under Customer Order to the connected activity.	When order is created for the No Part and is in the Planned status. Cost is reported under Pur Req / Pur Order to the connected activity.	When order for a No Part has been released. Cost for the Purchase Order is reported under Pur Order to the connected activity.	Till arrival transactions are transferred, used cost is reported under Pur Order to the connected activity. After transferring transactions, used cost is reported under respective voucher rows.
Not Decided (Inv)	Planed cost is retrieved in following hierarchy: 1.Cost set 1 values from IFS Costing. 2. Inventory value of the inventory part. 3. Estimated material cost of inventory part. If a Sales Overhead is defined in Part Cost page for the particular part, it is also included in planned cost. Cost is reported under Customer Order to the connected activity.		Updated when subsequent supply orders are released. Cost for the Sales Overhead is reported under Customer Order to the connected activity.	N/A
Not Decided (Non-Inv)	Planned cost is retrieved from Cost field in the Non-Inventory Sales Part page. Cost is reported under Customer Order to the connected activity.		Updated when subsequent supply orders are released.	N/A

Revenue Progression of Project Connected Objects

Updating of revenue on objects is performed against project revenue elements. Revenue objects do not report progress. The objects report revenue to the activity as follows:

Revenue Object	Estimated	Planned	Preliminary	Posted	Actual
Activity Estimate	Retrieved from the Estimated Revenue field in the Activity Scope and Schedule/Estimates tab.
Sales Contract Project (Sales Contract and Application for Payment)		Retrieved from Sales Contract Line Items that have the Active revision status. The Report Planned Revenue slider switch can be used to view the previously planned revenue.
Work Task		When the Work Order Line is transferred to a Customer Order Line.
Request Work Task		When the Request Line is transferred to a Customer Order Line.
Customer Order Line Revenue		When a Customer Order Line or Customer Order Rental Line is connected to an activity.
Customer Order Invoice Line			When a Customer Order Invoice is created.
Invoicing Plan		When the Invoicing Plan Line is created with the Sales Amount.
Project Transaction Revenue		When a Project Transaction is entered which can be invoiced and has a Sales Price.
Invoice Posting Row (Project Invoice) (Instant Invoice) (Customer Invoice)			When the Project/Instant/Customer Invoice is saved.
External Invoice Posting Row (External Customer Invoice)			When the External Customer Invoice is loaded.
Voucher Row				When Hold table voucher rows are created that report revenue to project activities, for example: When a manual voucher is created that reports revenue to the project. When submitting and certifying a sales contract application for payment. When the Customer Order Invoice is posted. When the Project/Instant/Customer Invoice is posted. When the External Customer Invoice is posted.
General Ledger Voucher Row					When Hold table vouchers rows that report revenue to project activities are updated to General Ledger.

A Step by step example on how important activity fields are used:

For this example we work on a project containing only one activity called "Specify and purchase engine for winch". In order to complete this activity some engineers have to do a detailed specification of which engine to buy, and later the purchase department is involved in the communication with the selected supplier. The planned cost driver for all of the objects is Connected Objects, except for the Activity Resources object, for which the planned cost driver is Activity Resources. The progress method is Connected objects.

Step 1

Create the activity: A 01 – Specify and purchase electrical engine, Start date: 3 of July, End date: 28 of July, with number of workdays as 20.
Enter estimated values for the activity. We estimate to buy the engine components for $100,000 and use 30 hours at a cost of $3000 for the specification.

Project Cost Element Estimated Cost Estimated Hours

Material 100,000

Work 3,000
30

Sum 103,000
30

Step 2

Create and connect a document package with two documents; one drawing and one technical specification. Planned hours are 17 + 15 = 32. The cost is $100 per hour. We register the documents, but no progress is accomplished yet.