Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

PDC allows you to generate Entity Level Authorizations whenever an existing entity has a history record duplicated to a new effective date.

Purpose: PDC tracks entity definitions based on change dates. This means there must exist a complete history record whenever an entity has a change to its definition. Tracking historically accurate definitions of an entity is how Eagle supports historical reporting. The workflow for creating a new definition (that is the history record) of an entity is to select the most recent history record (latest/greatest information) and duplicate it and assign a new effective date.
PDC provides the ability to generate a new fund authorization whenever a history record is duplicated to a new effective date. The concept is that although the newly duplicated record does not represent a new entity within the system, it does represent a new change date definition.

The standard Field Level authorizations are not impacted by this setting. Any existing field level authorizations enabled during this process still generates the authorizations, accordingly.


Configure Duplicate History Entity Level Authorization

PDC allows you to generate Entity Level authorization using System settings configuration for duplicate history records. First, you need to configure the system settings to authorize the new entity setup for duplicate records.

Set Up Duplicate History Authorization in System Settings

New entity authorizations for duplicate records are controlled using the system settings. 

  1. In Portfolio Data Center, from the left navigation, click Setup > System Settings.
    You see the System Settings workspace with the available list of settings.
  2. Select the System Item 39 for 'Authorize duplicate history'.
    This setting regulates the entity authorizations for duplicate records. By default, the setting is configured as 0 (turned off). 
  3. Double-click the respective Value column and set to 1 to enable authorization for duplicate records..
    You see a warning message to confirm the modified setting configuration.

  4. Click Yes to confirm the modified setting changes.
    After enabling the system setting, whenever an existing entity has a history record duplicated, the system generates the pending authorization and sets the release status to 'Incomplete'.  



  • No labels