| Anchor | ||||
|---|---|---|---|---|
|
Cash activity is stored in the CASH database.
| Anchor | ||||
|---|---|---|---|---|
|
The CASH_ACTIVITY table stores trades and non-trade events, such as cash contributions and withdrawals into or out of the portfolio. Note the TRADES table does not include contributions and withdrawals. Additionally, fewer elements are required than are usually stored with trades. Typically, Eagle Performance only needs to know whether the transaction was an inflow or outflow and the net amount of the transaction. The following table lists the key fields in the CASH_ACTIVITY table that are used in performance calculations.
Column | Description |
|---|---|
ENTITY_ID | Stores the entity identifier, which joins to the ENTITY table. |
CASH_INT | Requires a unique value. |
ORIG_TRANS_NUM | Stores the original transaction number, which requires a unique value. |
EFFECTIVE_DATE | Stores the performance effective date of the transaction. |
SRC_INTFC_INST | Stores the source interface instance, which joins to sources and is used in the performance calculation rule to retrieve the transactions. |
SECURITY_ALIAS | Stores the security alias, which joins to security. |
TRANS_TYPE | Stores the transaction type that is used in the cash adjustment fields. |
AMOUNT | Stores the net amount of the transaction. |
You can also store more information about the transaction. For example, the local currency transaction amount.
One of the requirements of the performance return calculator is that the ORIG_TRANS_NUM column be unique. It is required to be unique because the function for data editing, or scrubbing, of transactions in the database needs to link the original and scrubbed transactions together to prevent double-counting of transactions in the return calculation.