Page Comparison

1. Do you want to commit returns on the server side?

Determines whether to commit the returns. Options include:

• Yes. Automatically commits returns as they are calculated.
• No. Calculates, but does not commit, returns. You can commit them after reviewing the report.

2. Returns will be committed with the entities you chose in the screen.

Calculates returns for one entity, but stores the returns to a different entity.

3. Would you like to calculate to-date returns?

Determines whether to calculate to-date returns.
Note: To ensure backwards compatibility, Eagle does not recommend setting this option. See Use the MPC  for detailed information about how to store to-date returns.

4. What calculated end date returns do you want to commit?

Specifies the end-date returns you want to commit.
Note: To ensure backwards compatibility, Eagle does not recommend setting this option. See Use the MPC for information.

5. Specify additional options if you wish.

Allows you to set several additional options.
The Do not update Business Calendar check box determines whether to update the Eagle PACE business calendar. Options include:

• Do not update Business Calendar. If you select this check box, the Eagle PACE business calendar is automatically updated. If cleared, the Eagle PACE business calendar is not automatically updated.
  
  You can either select options to assign a Preliminary status to committed returns or to assign a Final status to committed returns.
  The Commit Returns as options determine how a Performance status is assigned to committed returns. Options include:
• Preliminary. Automatically calculates and stores returns, but you control reporting of numbers before they are finalized by configuring certain reports to only show preliminary figures.
• Final. Automatically commits all the returns as final.
• Out-of-tolerance preliminary (Commit Tolerance Field). Commits returns as final, unless they fail a tolerance check that uses a Commit Tolerance field. These portfolio/dates are committed in a preliminary status. For more information about tolerance checks, see "Using Tolerance Checks and Reference Fields."
• Material Difference Check (using Materiality Check Field). Commits first time returns as preliminary. If returns were previously committed for that entity/effective date/source/frequency/performance model, Eagle overwrites only those returns that are materially different from the prior returns. If there is no material difference between the returns, Eagle does not overwrite prior returns for that entity but commits the new returns to the alternate commit source. If there is a material difference from a prior return that has a Preliminary status, Eagle overwrites the prior return. If there is a material difference from a prior return that has a Final status, Eagle commits the new Preliminary return to the alternate commit source and does not overwrite the prior return.
  
  The system identifies material differences using the Materiality Check field in the report's Field Rule or Report Rule. For more information, see "Using Tolerance Checks and Reference Fields."
• Select Alternate Commit Source. This field appears only if you select the Only when materially different option. It specifies the alternate performance source used to commit returns that have a non-material difference and to commit returns with a material difference when the prior returns have a Final status. Choose a source that differs from the source specified in the Select Commit Source field.
  In the Security Commit Options area, you determine the level at which to store committed returns. Options include:
• None. Limits the returns stored to the total and segment levels.
• Rollup Relations with Security Level. Stores returns at both the total portfolio/segment and security levels.                                                                                                                                   Note Note: If Step 1 Option 7 is "No, thank you" you can select from the below 3 options in the enabled dropdown:
  • Single Position
  • Positions by Strategy (allows commit of multiple returns for a security)                
  • Positions by Strategy and Dictionary Classification (allows commit of multiple returns for a security in multiple nodes)
• Rollup Relations Only. Stores returns at both the total portfolio/segment and security relationship only level.                                                                                                                                    Note: If Step 1 Option 7 is "No, thank you" you can select from the below 2 options in the enabled dropdown
  • Single Position (one return for aggregated security position)            
  • Positions by Strategy (allows commit of multiple returns for a security)

6. Select Commit Source

Specifies the source that the report uses to commit performance results to the PERFORM database. The default source, Eagle PACE (source instance 4), appears, but you can select a different performance source. A performance source is a source that has a feedback type of Performance.