Project pegging in Procurement
To identify costs, demand, and supply for a project, you can implement project pegging. You can also specify the items for which project pegging is required. For more information, refer to Project pegging overview.
To use project pegging in combination with costing breaks, you must select the Costing Breaks check box in the Implemented Software Components (tccom0100s000) session. For more information, refer to Costing Breaks.
Project pegging in Procurement includes pegging of project costs for purchase documents, such as requisitions, requests for quotation, purchase orders, and purchase (push) schedules. If the item specified for the purchase document requires a peg, a peg distribution must be linked to the document. As a result, the required quantity of the parent document is distributed across distribution lines for combinations of project/budget, project element and/or project activity. For example, if a distribution is used to peg the ordered quantity of a purchase order line, the purchased goods and the related costs are booked to these projects, elements, and activities.
Generating a peg distribution
When you save a purchase document line, a peg distribution can be generated in the Purchase Peg Distribution (tdpur5100m000) session. A peg distribution can be manually specified or automatically defaulted from other documents.
This table shows the documents stored on the distribution line and the related fields:
Document Type for Peg Distribution | Business Object | Business Object Reference |
RFQ Line | RFQ number | position/alternative |
RFQ Response | RFQ number | position/alternative/bidder |
Requisition Line | requisition number | position |
Purchase Order Line | order number | position/sequence |
Purchase Order Receipt | order number | position/sequence/receipt sequence |
Purchase Order Material Supply Line | order number | position/sequence/material sequence |
Stage Payment Line | order number | position/stage payment line |
Purchase Schedule Line | schedule number | position |
Purchase Schedule Receipt | schedule number | position/receipt sequence |
Commingling pegs
If purchase order/schedule lines are project pegged, commingling of pegs is subject to project combination checks. Commingling rules specified in Project Pegging in Common, determine if lines with different pegs can be commingled into one purchase order line or purchase schedule. In general, commingling is executed by planning group, which includes the commingling rules for the linked projects. However, commingling for export license required items is restricted by project. This means if projects are different, separate purchase order lines or purchase schedules are created. To further restrict commingling, you can specify commingling exceptions, which are the pegs that must be excluded from commingling.
ExampleProject 1 with activity 10 and project 1 with activity 20, have a requirement for an export licensed item.
- Without an exception: One purchase order line with two distribution lines are created.
- With an exception for one or both of the activities: One purchase order line per project peg, one purchase order with two purchase order lines are created.
Handling peg data
If the purchased goods and related costs are booked to only one project, the peg is displayed on the purchase document line. When you save the line, LN creates one distribution line for the peg distribution. Peg fields, quantities, or the ordered amount can be updated on both the parent document line and the distribution line, before the lines are synchronized. If additional pegs (distribution lines) are specified in the peg distribution, the peg fields are cleared on the parent document line and the quantities or ordered amount are disabled. The sum of the quantities or ordered amounts on the peg distribution can be updated to the quantities or ordered amount on the parent document line. If the peg distribution's total quantity differs from the quantity on the parent document line, a message with regards to updating the parent document line is displayed: Peg distribution is mandatory for %1$s %2$s - %3$s..
If the Manual Project Peg Modification check box is selected in the Project Pegging Parameters (tcpeg0100m000) session, for all manual actions that affect a peg distribution, you must specify a change reason in the pegged purchase document. The project peg changes and reason codes are logged in the Cost Peg Audit History (tpctm2500m000) session for analysis.
- The reason code applies to the entire peg distribution. So, when you change a single line in a peg distribution, the reason code is applied to all pegs in the peg distribution.
- A message is displayed if a change reason is required. Based on the session, you must specify the change reason either in a field or window. If you do not specify a change reason, you cannot save the pegged purchase document.
- Planned inventory transactions, material transactions, and (financial) integration transactions are not generated for the parent document line, but for the peg distribution. Therefore, transactions are booked by peg
If the Change Requests check box is selected in the Purchase Order Parameters (tdpur0100m400) session, the peg distribution can be modified after purchase order approval or printing only by using the change request process.
Warehouse receipts
For partial warehouse receipts, pegs with the highest priority receive the quantities. The priority of the peg is based on the required date and quantity, as specified in Enterprise Planning, for the required purchase line. The peg with the earliest required date has the highest priority.
If the required date and quantity cannot be retrieved from Enterprise Planning, the following is applicable:
-
Purchase order lines
The priority is based on the dates specified for the inbound order line peg distribution. -
Purchase schedule lines
The priority is based on the dates specified for the purchase schedule line peg distribution. Schedule lines are not linked to individual inbound order lines because, for push schedules, goods are received against a blanket warehouse order, which is linked to the schedule header. During the receipt process for a required quantity, the pegs that match the total quantity to be received for the schedule lines are transferred to Warehousing for use in the receipt process. These schedule lines are transferred, based on line position and the (oldest) planned receipt date. The generated warehouse receipt line peg distribution is a subset of the (aggregated) peg distribution of the schedule lines.
When a receipt is confirmed, the peg distribution (order line) or peg distribution data (schedule line) is copied from the warehouse receipt line to the purchase order/schedule receipt. You cannot update the peg distribution for the purchase order/schedule receipt.
If a receipt correction or an inspection is performed for a receipt line in Warehousing, based on the priority specified for the peg distribution, the peg distribution lines are also updated with the modified quantity. Based on the Warehouse Receipt Distribution Line field in Warehousing, the related distribution lines are updated in the Purchase Peg Distribution (tdpur5100m000) session.
Purchase receipts
For partial purchase receipts and invoice handling, priority rules are not used. Partial purchase receipts are proportionally distributed across the peg distribution lines. You cannot update pegging information on the purchase receipt. However, if a parent document line and the linked distribution line(s) include an ordered amount and no ordered quantity, you can change the ordered amount after receipt in the Change Price and Discounts after Receipt (tdpur4122m000) session. If the received amount is changed for the order line, the amount change is proportionally distributed across the peg distribution lines.