Auditing peg changes in purchase documents

In Infor LN 10.4, project peg auditing allows you to track manual actions that affect peg distributions in pegged documents. Project peg audit change reason codes are used to register why project pegs were manually added, removed, or changed. The information is logged centrally for analysis.

If the new Manual Project Peg Modification check box is selected in the Project Pegging Parameters (tcpeg0100m000) session, for manual actions that affect a peg distribution, you must specify a change reason code in the pegged purchase document. The reason code must be of the type Project Peg Audit History and is logged in the Cost Peg Audit History (tpctm2500m000) session.

The reason code applies to the entire peg distribution (all lines). So, when you change a single line in a peg distribution, the reason code is applied to all pegs in the peg distribution.

Example: A purchase order line has three distribution lines. If you change distribution line 1 and specify a change reason code, three distribution lines are logged in the Cost Peg Audit History (tpctm2500m000) session with the same reason code. Next, if you change distribution line 2 and specify a reason code, three distribution lines are logged, with the change reason code of line 2.

If a change reason is required, a message is displayed. Depending on the session, you must specify the change reason either in a field or in a related window. If you do not specify a change reason, you cannot save the pegged purchase document.

The following table shows the sessions from which a peg distribution can be affected by a manual action, which means a change reason code is required. This table also shows whether the reason code must be specified in a field or in a Select Change Reason for Cost Peg Audit History window: