| # Cost pegging in depot repair Overview In Service, it is possible to implement cost pegging in the Depot Repair module. You can peg the service cost to a project, element and/or an activity. To peg a project, specify the project, element, and/or activity information for the call, the contract, the maintenance sales quotation, maintenance sales orders or work orders. You must select the Mandatory Project Peg check box in the Item - General (tcibd0101s000) session if defining the PCA ID is mandatory to peg the cost of the item to the project. Initiation of the pegged transaction The peg is initiated only when a business process is started for transactions that register actual costs. Example are Calls and Maintenance Sales orders. Project Cost Account is an account where the cost is pegged. Costs are pegged through Project Cost Account ID. Following are the two ways you can populate the PCA ID: By entering the PCA ID when you create a new call, contract, maintenance sales quotation, maintenance sales order or an external work order. By specifying the PCA ID on the service contract. The user can also enter the PCA ID manually. Propagation of peg in the depot repair process The PCA ID is propagated to the underlying lines (e.g. from call to MSO to Work order). You can change the PCA ID until the status of the call / contract / maintenance sales quotation / maintenance sales order / work order changes. Propagation of peg to service contract and configuration lines In Service, the service contract can determine whether the call / contract / maintenance sales quotation / maintenance sales order / work order linked to the service contract retrieve the PCA ID from the contract. By default, the configuration lines retrieve the PCA ID from the service contract header. These PCA IDs on the configuration line are propagated to the maintenance sales quotation lines, maintenance sales order part lines and work orders. Note You can define the PCA ID for service contracts that have the status 'Free' or 'Active'. Propagation of peg to a call The PCA ID of the call is retrieved from the service contract header by default, if the call is related to a service contract. You can enter or modify the PCA ID if the call status is ‘Free’. You must specify the reason for the modification. If the call is solved without being transferred ( Example to a maintenance sales order or service order), the call can be invoiced. The costs are booked to the corresponding PCAs. The cost component is used to identify the appropriate project cost type using the cost mapping in Cost Mappings (tcmcs0149m000) session. Propagation of peg to the maintenance sales quotations ERP Enterprise defaults the PCA ID of the quotation header line either from a service call or maintenance sales order part line or a work order. If the PCA ID is not defaulted from these origins, ERP Enterprise defaults the ID from the service contract configuration line if the serialized item is linked to a service contract. The user can enter or change the PCA ID if the maintenance sales quotation status is ‘Free’. Propagation of peg to the maintenance sales order ERP Enterprise defaults the PCA ID of the maintenance sales order from the originating call or maintenance sales quotation. The PCA ID of the order part line is defaulted from a service call or maintenance sales order part line. If the PCA ID is not defaulted from these origins, ERP Enterprise defaults the ID from the service contract configuration line in case the serialized item is linked to a service contract. The user can enter or change the PCA ID if the maintenance sales quotation status is ‘Free’. Propagation of peg to the work order for MSO part line By default, the PCA ID is retrieved from the maintenance sales order. If the installation group or the item is linked to a service contract, the PCA ID is retrieved from the service contract configuration line. If the PCA ID is not defaulted from these origins, ERP Enterprise defaults the ID from the service contract configuration line in case the serialized item is linked to a service contract. The user can enter or change the PCA ID if the maintenance sales quotation status is ‘Free’. Propagation of peg to the work order linked /originating from maintenance sales order ERP Enterprise defaults the PCA ID of the work order (linked/originating from maintenance sales order) from the service contract configuration line if the serialized item is linked to a service contract. If the PCA ID is not defaulted from these origins, ERP Enterprise defaults the ID from the service contract configuration line in case the serialized item is linked to a service contracts. The user can enter or change the PCA ID if the maintenance sales quotation status is ‘Free’. Propagation of peg to the follow-up work order By default, the PCA ID is retrieved from the initiating work order. If the installation group or the item is linked to a service contract the PCA ID is retrieved from the service contract configuration line. If the PCA ID is not defaulted from these origins, ERP Enterprise defaults the ID from the service contract configuration line in case the serialized item is linked to a service contracts. The user can enter or change the PCA ID if the work order status is ‘Free’. Propagation of material request to LN Warehousing from depot repair When warehouse orders are generated from Service in order to request material from a warehouse, the PCA ID is propagated to Warehousing only if the I Inherit Project Peg check box in the Item - General (tcibd0101s000) session is selected. Warehousing uses the PCA ID for the financial bookings to LN Project. Warehousing handles the potential peg transfers as follows: Example Service needs materials B and material C to be used in the repair of item A. For Item B LN Service requests inventory with a peg. For item C, Service requests material with a peg, because the cost for B and C have to be reported to the project. Warehousing checks if there is inventory of item B with the corresponding PCA. In the case of an inventory shortage, Warehousing will checks whether transfer rules apply to meet the LN Service request. Warehousing handles the potential peg transfers in the background. For item C, the process is the same. Service requests the material with a PCA, though there is inventory for item C without a peg. Consider a situation where demand transaction for item A has a peg123 that requires material B and C. When the Inherit Project Peg check box in the Item - General (tcibd0101s000) session for Material B is set to Yes and for Material C is set to No:
| Inherit Peg | Cost Pegged To | Request to Warehouse
Material B | Yes | P1E10A10 | Financially peg costs to: P1E10A10 Inventory from: P1E10A10
Material C | No | P1E10A10 | Financially peg costs to: P1E10A10 Inventory from: <empty peg >
Since material C is without a peg in inventory, the costs are not pegged to the project yet. However, since material B is already cost pegged to the project, the cost do not have to be booked again to the project when the actual outbound process is executed. Propagation of Peg to generate purchase order For project pegged items when purchase orders are generated, the PCA ID from Service ( Example for Subcontracting) , is propagated to ERP Enterprise Order Management to generate the purchase order with the corresponding peg. For material request of type Via Purchase the PCA ID is propagated only if the Inherit Project Peg check box in the Item - General (tcibd0101s000) session is selected. Propagation of peg to book hours When hours are booked in Service, the PCA is processed to ERP Enterprise People to book hours on the work order. Book other costs or bench stock material costs When actual other costs or Bench stock material costs are defined in Service, the costs are logged in the PCL. If the item is defined for the maintenance sales coverage line, this item is used to identify the appropriate project cost type. In case the item is not defined, the cost component is used to identify the appropriate project cost type using the cost mapping in Cost Mappings (tcmcs0149m000) session. Propagation of peg to maintenance sales order coverage line When costing the maintenance sales order coverage lines, the invoice is created in ERP Enterprise Central Invoicing. The revenues and costs are booked to the corresponding PCAs. The revenues and costs are booked to the corresponding PCAs. If the item is defined for the maintenance sales coverage line, this item is used to identify the appropriate project cost type. In case the item is not defined, the cost component is used to identify the appropriate project cost type using the cost mapping in Cost Mappings (tcmcs0149m000) session. LN Central Invoicing receives the related PCA IDs for the actual costs. |