Override Exceptions

Portfolio Data Center allows you to override the value of a field that failed a validation (which created an exception) for an entity.

To override the value of an error field:

In Portfolio Data Center, from the left navigation, select Portfolio Desk and click the appropriate entity type.
You see the Summary workspace with the available list of entities.
Click the View By drop-down list and select All.
Provide the appropriate search criteria and then click Search.
You see the list of entities as per the defined search criteria.
Select the entity you want to resolve from the Entity Details pane.
You see the system list the associated exceptions for the selected entity in the Exceptions pane.
Scroll to the exception you want to resolve in the Exceptions pane.
Right-click on the exception and select Edit. Otherwise, click Edit in Manage group of Home tab.
You see the Edit Entity workspace.
As you click on a specific exception, the entity field is highlighted below in the Entity Details pane.
Note: A red square indicates that the field has a critical exception. An orange triangle indicates the field has a warning exception.
Right-click on the field and select Override Value. Otherwise, click Edit in Manage group of Home tab.
You see the Edit dialog box.
In the Current Value, the system displays the current value of the field.
Type the appropriate new value for the field in the New Value box.
Select the Make this Null check box to null out the field.
Click the Type list to select the type of override. Options include:
- Override. Select this option to override or edit the field value.
- Default. Select this option to use the new value when no other data update is provided.
Specify the Start Date for the override.
The Start date indicates the first effective date of the edit modification. You can modify the start date to any previous existing history date within that entity. If the selected date is not present in the entity’s history, a duplication of history record action is needed. See Create History Records in Manage History Records for more details.
Specify the End Date for the override.
The End Date indicates the latest effective date of the edit modification. If the End Date is for the latest effective date, then the override data is automatically carry forwarded when the next history date is created. This process continues until such time where another manual override is created or a new data value is populated systematically.
You can provide an End Date for a future effective date also. This sets a specific expiration date, for a specific date range, on the override value. Once the End Date of the override passes, then the next time when a new latest history date is created, the system reverts back to any Policy specific configured overrides, if any, and apply to the incoming data value as indicated.
Select No End Date check box to perform a permanent override.
An example of when to use No End Date is, when an incoming file is known to input incorrect values for a field in which you want to perform an on-going override in place of the updated value. This eliminates reoccurring exceptions to the entity workflow.
Click the Reason Code list to select the type of reason for the override. Core options include:
- File based override
- Incorrect file
- Incorrect manual entry
- Manager request
Note: Reason Codes are essentially Code Values within Eagle and you can configure it according to your preferences.
Specify comments for the override, if any.
Click Save to save the changes.
Click View & submit changes to submit the modified details.
You see the Change Summary dialog which allows you to review all activity before submitting the change request to the PDC engine.
Click Cancel to cancel the changes.
The system updates the field and displays a blue arrow to the left of the field.