Prevent Commitment if Effective Date Is Before Inception or After Termination Date

You can prevent Eagle Performance from committing returns when the Performance Calculation report's effective date occurs on or before the entity's inception date and/or occurs after the entity's termination date. During the entity's inception month, this option can facilitate the reporting of Month to Date performance by eliminating returns on or before the inception date.

To do so, you can activate the Inception Date Check and/or the Termination Date Check to prevent committing returns that fail the checks. Fields used to perform these checks are present at the report rule and the field rule levels. These fields are available for the Performance Returns reports, but are not available for the Dynamic NAV Returns report or the Composite Weighted Returns report.

After you submit the report, you can identify performance records that failed as a result of the checks through corresponding error messages written to the report log and the report results Diagnostics tab. If you set up a Commit Journal view with a Comments filter that shows Not Normal results, you can review the message for failed records in the COMMENTS column.

To prevent committing returns if the effective date falls on or before inception date or after termination date:

1. Select the Report Rule or Field Rule used by the Performance Returns report.

2. Do one of the following:
   In the Report Rule workspace, select the Specify the Commit Tolerance and Reference Fields link. The Specify Commit Tolerance and Reference Fields dialog box appears. See the following figure.
   
   

   Open

   

   Otherwise, if you are building a Field Rule, these fields appear in the middle of the Field Rule dialog box in the Specify Inception and Termination Date Fields section.

3. In the Do not Commit Returns On or Before field, either select:
   The entity's inception date field to activate the inception date check, and prevent the commit process from committing returns with effective dates that are less than or equal to the entity's inception date, identified by the selected field. You can select the default value, i Entity Inception Date, an internal field that uses the INCEPTION_DATE column in the Entity table, or can select any date format field from the Entity table or the Entity History table. For example, you can select eglEnt-EntityInceptionDate.
   If the Performance Calculation report's end effective date is less than or equal to the inception date for that entity, the system commits no returns at any level for that entity and effective date. If the entity has no inception date set, the system commits no returns at any level for that entity and effective date.
   <none> to omit use of the inception date check. This allows the commit process to commit returns with effective dates that are less than or equal to the entity's inception date.

4. In the Do not Commit Returns After field, either select:
   The entity's termination date field for use as the termination date check. This prevents the commit process from committing returns with effective dates that are greater than the entity's termination date, identified by the selected field. You can select the default value, Entity Termination Date, an internal field that uses the TERMINATION_DATE column in the Entity table, or can select any date format field from the Entity table or the Entity History table.
   
   For example, you can select eglEnt-EntityTerminationDate. If the Performance Calculation report's end effective date is greater than the termination date for that entity, the system commits no returns for that entity and effective date. If the entity has no termination date set, the system commits returns as if you were not using the termination date check. 
   <none> if you do not want to use the termination date check. This allows the commit process to commit returns with effective dates that are greater than the entity's termination date.