Period of performance
Period of performance (POP) is used to enter transactions for an activity that do not fall within the activity's specified date range. Date ranges are assigned to an activity group or activity, and specify the time period during which the activities in the activity group are valid. However, you might incur setup costs for an activity before the activity starts. Similarly, you need to enter transactions for a project after the project has been completed. Use Activity Period of Performance (AC10.6) to establish date tolerances, which allow you to specify activity transactions outside of the date range.
Like date ranges, periods of performance can be assigned at either the activity group or activity level. Both Activity Group (AC00.1) and Activity (AC10.1) provide access to Activity Period of Performance (AC10.6). Periods of performance are managed by system code for the activity or activity group. This allows you to restrict the systems for which transactions can be specified during the period of performance. For example, you want to allow transactions for the Requisitions (RQ) system, but not for others.
Using period of performance templates
You can use a period of performance template to define similar date tolerances for multiple activity groups or activities. After creating a period of performance template on Period of Performance Template (AC10.7), you can assign it to an activity group or activity rather than specifying the number of Begin Days and End Days. To display a listing of the POP Templates, run POP Template Listing (AC211).
Interfacing period of performance dates
You can use Performance Date Interface (AC502) to interface period of performance data from other applications. After interfacing the data, you can use Performance Interface Adjustment (AC50.2) to make any corrections to the interfaced records.