Report frequencies generate lists of dates of which result and target values are reflective in Performance Scorecard reports. Collection frequencies generate a series of dates on which measure result and target values are meant to be entered or available. Extensions enable you to identify the day by which values must be entered. For example, assume a measure has a result collection date of May 26. If you specify a three day collection extension, results can be entered up to and including May 29, but not afterward.
For example, assume that a company creates a measure called Sales to track the amount of money made each month on sales. To avoid overlapping with other months, the Sales measure could have a reporting frequency of monthly, with a period of the last day. This ensures that sale figures for the month of January, for example, only display in January and not February. If sale figures are not available in January, but usually by the middle of the following month (February), a collection frequency specifying the 15th of every month can be used. To ensure that results cannot be entered after February 18th, specify an extension of 3. These frequency settings ensure that although sale figure results for January are not collected until February 15th, they are displayed for January in reports. They also ensure that Sales result values cannot be entered more than three days after February 15th. .
The same frequency rules apply to target values. The target collection frequency generates dates by which target values are expected to be entered. The target reporting frequency identifies the dates with which target values are associated, in reports.
When collection extension expire, measures lock, preventing users from entering result and target values. An administrator can break the lock. See the Oracle Hyperion Performance Scorecard Administrator's Guide