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 7 Next »

The most important thing to keep in mind about loading these tables is that the entity history data is important for GIPS composite calculations. For example, you need to store portfolio strategy changes over time. This may be accomplished by storing strategy code values and effective dates for the changes for particular entities. Entity Inception Date and Termination Date fields should also be populated for portfolios, as the composite maintenance functions rely on this data when adding or removing constituents from composites either manually via the windows or using the automatic composite entity builder. This is done by storing entity history data in the ENTITY_HIST table. If you are storing descriptive information about the portfolio as entity characteristics, then the respective entity characteristic history table also needs to be populated.

You can maintain the data in the entity tables using the PACE Entities windows, or you can build an uploader to maintain them with data provided by another system. For information about maintaining composites manually or automatically, see GIPS Composite Management. For information about the Entity default stream, see the Supported Generic Interfaces V17 Wiki. This data is described in the following table.

Column

Description

Entity Type

Defines whether the composite is a GIPS composite or another type of entity. Use entity type ACOM for GIPS composites. See the following table that describes composite entity types for more information.

Inception_Date

If the INCEPTION_DATE field is NULL, the performance composite does not get picked up in the result set of the Composite Listing report. Constituent entities with Null in this field are not added to composites either manually or via the automated method.

Termination_Date

Used by the Composite Listing report. Constituent entities that are closed but with Null in this field may be incorrectly added to composites either manually or via the automated method.

The following table describes the two types of composite entity types in PACE.

Entity Type

Description

Database Tables

Eagle Performance Reports

Performance Calculation Constituent Inclusion Rule

ACOM

Performance Composite – Complies with GIPS for composite definition, calculation, and presentation

Rules database:
ENTITY
ENTITY_HIST
ENTITY_DETAIL
ENTITY_DETAIL_HISTORY
ENTITY_RANGE_DETAIL

Performance Returns Calc report
Composite Weighted Return Calc report
Performance Analysis report
Composite Analysis report
Composite Monitor
Performance Query Tool

Composite constituents that are in the composite the entire calculation period are included.

COMP

Composite –Does not comply with GIPS for composite definition, calculation, and presentation

Rules database:
ENTITY
ENTITY_HIST
ENTITY_DETAIL
ENTITY_DETAIL_HISTORY

Performance Returns Calc report
Composite Weighted Return Calc report
Performance Analysis report
Performance Query Tool

Composite constituents that are in the composite at the beginning of the entire calculation period are included.

  • No labels