Project pegging for Service Order and Activities

You must select the Use Project Pegging in Field Service check box in the Service Order Parameters (tssoc0100m000) session to implement project pegging for service orders. If this check box is cleared, the existing project-service integration functionality is implemented.

You can specify the project peg:

  • When creating a new service order.
  • For a service contract. When the service contract is linked to the service order, Infor LN defaults the project peg from the service contract to the service order. However, you can modify the peg data.

If a service order is project pegged, the service order costs are linked to the project when the costs are logged on the service order WIP.

If the serialized item specified for a service order is linked to a service contract configuration line, Infor LN defaults the project pegging data in the Service Orders (tssoc2100m000) and the Service Order Activities (tssoc2110m000) sessions from the Service Contracts (tsctm3100m000) session.

If the Costing Breaks check box is selected in the Implemented Software Components (tccom0100s000) session, the Project Peg Origin field in the Service Orders (tssoc2100m000) session is set to:

  • Top Demand, for the service order generated from a project.
  • Manual, for the service order created manually.
Project pegging for service orders

When you create a service order, if the Use Project Pegging in Field Service check box is selected in the Service Order Parameters (tssoc0100m000) session, the project pegging data in the Service Orders (tssoc2100m000) session is defaulted from the originating object. However, you can modify this value for service orders with the Status, Free.

If the Manual Project Peg Modification check box is selected in the Project Pegging Parameters (tcpeg0100m000) session, you must specify a reason code when you modify the project pegging data on the service order header.

Note
  • When a service order is generated from a project, the project pegging data is transferred from the project to the service order.
  • When a service order is generated from a call, the project pegging data is transferred from the call to the service order.
Project pegging for service order activities

When you create a service order activity, the project pegging data in the Service Order Activities (tssoc2110m000) session is defaulted from:

  • The Costing Breaks - Service Activities (tppdm3116m000) session.
  • The Service Orders (tssoc2100m000) session
  • The Service Contracts (tsctm3100m000) session.

You cannot modify the project pegging data for a service order activity.

Project pegging for service order cost lines

When you create service order cost lines (material, labor or other), the project pegging data is defaulted from the Service Order Activities (tssoc2110m000) session, the Service Orders (tssoc2100m000) session or from:

  • The Costing Breaks - Service Material (tppdm3103m000) session for the material cost line.
  • The Costing Breaks - Service Labor (tppdm3104m000) session for the labor cost line.
  • The Costing Breaks - Service Other Cost (tppdm3105m000) session for the other cost line.
Project pegging for a service order while creating a copy

When you create a copy of an existing service order, the project pegging data is also copied if the Project Pegs check box is selected in the Copy Service Order (tssoc2280m000) session. If the project pegging data of the existing order is modified manually, and this data must be copied to the new service order, you must specify the Change Reason in the Copy Service Order (tssoc2280m000) session.

Project pegging for service order material cost line while planning and releasing

If the Project Pegged Inventory check box is selected in the Service Order Estimated Material Costs (tssoc2120m000) session:

  • At the time of planning a service order, the project pegging data defined on the estimated service order material cost line is considered for the planned inventory transactions created for the estimated material cost lines.
  • At the time of releasing the service order, the project pegging data defined on the service order material cost line is considered for the warehouse orders created for the estimated material cost lines.
  • At the time of performing ATP check, the project pegging data defined on the service order material cost line is considered to check the availability of the project inventory.
Project pegging when subcontracting a service order activity

If a service order activity is subcontracted, a service order other cost line of Cost Type Subcontracting is created, when the service order is planned. The project pegging data is defaulted from the Costing Breaks - Service Material (tppdm3103m000) session if the Costing Breaks check box is selected in the Implemented Software Components (tccom0100s000) session. Else, the project pegging data is defaulted from the linked service order activity.

Project pegging when registering service order actual costs

When the actual costs are registered, project pegging data is linked to the existing financial transactions, to log costs to the appropriate PCL. The integration elements of each financial transaction are extended with the project pegging data.

When the actual costs are registered for the service order material costs and the service order other costs, these costs are logged on the PCL. If the item is specified on the service order material cost line or service order other costs line, this item is used to identify the project cost type. Else, the cost component is used to identify the project cost type. The cost component is identified using the Cost Mappings (tcmcs0149m000) session. However, when hours are logged in LN Service, LN People log the cost on the PCL and to book the project peg on the Labor lines of the service order, a project peg is transferred from LN People.

Project pegging when costing service order actual costs

When costing the service order actual cost lines, the invoice is created in LN Central Invoicing. If the service order is linked by the project peg to a project in LN Project (or by the old Service Order links by Project (tppss65m000)), costs are rolled up to the project:

  • Sales Invoice in LN Central Invoicing
    If the invoice is created in LN Central Invoicing, the invoice is not changed. The revenues and costs are booked to the corresponding Project Cost Ledger (PCL). LN Central Invoicing receives the related project pegs for the actual costs for appropriate booking of the costs. To receive this project pegging data, LN Service creates a Service Order/Approved for Invoicing Project instead of the regular Service Order/Approved for Invoicing.
  • Costs rolled up to the project in LN Project
    If costs are rolled up to the project , then LN Project receives the related project pegs for the actual costs for appropriate booking of costs. In case of internal service orders, internal Costs are logged as Service Order / Transfer to Project WIP, in case of project pegging.
Note

If costs are covered by a contract, (repair) warranty, field change order costs or goodwill, these costs are not rolled up to the project.

Project pegging when closing service orders

When closing a service order, the service order data can be copied to history. The project pegging data of the service order, activities and the cost lines is also copied to history.

When project pegging data is specified in Field Service, the project can be closed if all related service orders are closed. When project pegging data is not specified in Field Service, the project can be closed if all the service orders linked to the Project have the status Final (that is, if all costs are rolled up to the project).

Related topics