Additional information for project pegged purchase documents
Standards, conditions, and requirements (clauses) between a customer and contractor can be specified as additional information on project contract lines. Because these clauses also affect the suppliers or subcontractors involved, the clauses can be transferred down the supply chain.
If a purchase document line, such as a requisition line, RFQ line, or purchase order line is generated or manually created and the line is project pegged, the additional information that is specified for the linked (project) contract line(s), is verified. The information in the additional fields of the project contract line(s) is transferred to the additional fields of the purchase document line, only if identical additional field names are specified for both the tables in the Additional Information Definitions (tcstl2100m000) session.
Example
This table shows the additional information fields that are applicable for a purchase document line:
| Contract line | Purchase order line | Field relevant? |
|---|---|---|
| ADI1 | ADI1 | yes |
| ADI2 | - | no |
| - | ADI3 | yes |
If a purchase document line is generated from a source that includes additional information and that also has a peg distribution with additional information, only the additional information of the source document is transferred to the purchase document line that is generated. The additional information of the linked peg distribution is not considered. If an additional information definition is not specified for the source document in the Additional Information Definitions (tcstl2100m000) session, but the source document is linked to a peg distribution with additional information, the additional information from the peg distribution is transferred to the purchase document.
Example
- A purchase requisition line with a peg distribution is manually specified.
- When specifying the pegs, the information in the additional fields of the project contract line(s) is transferred to the additional fields of the requisition line.
- The requisition is converted to an RFQ.
- The additional information of the requisition line is transferred to the RFQ line/ response line. The additional information for the linked peg distribution is not verified, because the requisition line already includes this information. Modifications made by the buyer to the additional information fields on the requisition line, are also transferred to the RFQ line/ response line.
When a project peg is deleted or modified for the purchase document line peg distribution, the additional information fields are not removed or updated. Buyers must review the additional information to determine if data is missing or redundant and must be manually modified. They can generate reports to view the differences between the additional information fields for the purchase document line and the project contract line(s). Additional information fields with matching content are not displayed.
Depending on the purchase document type, buyers can use these sessions to compare the additional information and print the differences:
- Print Purchase Requisition Additional Information Differences (tdpur2406m000)
- Print Purchase RFQ Additional Information Differences (tdpur1421m000)
- Print Purchase RFQ Response Additional Information Differences (tdpur1426m000)
- Print Purchase Schedule Additional Information Differences (tdpur3411m100)
- Print Purchase Order Additional Information Differences (tdpur4410m000)
- Additional information can be compared only if the purchase document has a linked peg distribution. Each peg in the peg distribution is compared with the document line. Consequently, a document line can be displayed more than once on a report.
- If multiple pegs, related to different project contract lines, are linked to a purchase document line, the clauses (additional information) of all these contract lines are transferred to the purchase document line. Contradicting clauses (additional information with the same field name, but a different field value) lead to loss of information. By setting up planning groups and commingling exceptions in Project Pegging in Common, you can avoid this conflict of clauses of different project pegs.