...
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 the GIPS Composite Management User Guide. For For information about the Entity default stream, see the Generic Streams and Data Uploaders Reference Guide Supported Generic Interfaces V17. 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: | Performance Returns Calc report | 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: | Performance Returns Calc report | Composite constituents that are in the composite at the beginning of the entire calculation period are included. |