About System Control Values

Owned by Nancy Cohn (Deactivated)
Last updated: Apr 03, 2024
4 min read

When you add or edit STAR_PERF_FLOW code values, you need to assign a system control value. The system control value determines how STAR to PACE Direct translates the new code value or event type to support Eagle Performance. You must refresh the code map cache to update the STAR_PERF_FLOW code value in memory.

If you change the system control value for an existing STAR_PERF_FLOW code value, you must rerun STAR to PACE Direct before any "as of" cancel activity is processed. Not doing so will result in an error when you attempt to run STAR to PACE Direct after the cancel activity. The best practice is to either rerun STAR to PACE Direct back to inception date of the affected entities, or back to a historical date when you know there will be no earlier cancel activity. For example, if you have a policy where trades are never rebooked after 90 days, you could rerun STAR to PACE Direct for the prior 90 days only.

The system control value determines how STAR to PACE Direct translates an event in support of Eagle's performance measurement solution. However, not all accounting data is stored the same way in the Eagle PACE CASH_ACTIVITY table: some events require the creation of a reflexive flow, and, for certain types of events, the reflexive flow values may default to zero; and, some accounting data may be stored to the ESTAR_TRADED_CASH_ACTIVITY and ESTAR_SETTLED_CASH_ACTIVITY tables in the ESTAR database, while other accounting data may be generated from the ESTAR Cost object (Cost BLOB).

A reflexive flow is an equal and opposite record that represents the currency cash flow of the transaction. When you set the value for the Create Performance Cash Flows in PACE field to Y, the system creates a currency cash flow. You must set the Create Performance Cash Flows in PACE field (tag 5398) equal to Yes, when you define STAR to PACE Direct interface fields for entities/bases. 

Reflexive flows are not created for currency events. For example, contributions, withdrawals, and FX rate spots are currency cash flows. The system creates only one currency cash flow for these types of transactions, which is inserted into the Eagle PACE CASH_ACTIVITY table. Eagle Accounting creates two cash activity records for one spot transaction. Therefore, it inserts two currency cash flow records for each spot transaction. The system does not create a reflexive flow if the reflexive value is $0 (zero).

The system sets the Cash Event Spawned field (tag 751) to Yes whenever it generates a cash activity record. Some securities or transactions generate cash events based on processing situations. Eagle Performance requires STAR to PACE Direct to recognize these scenarios and store only the generated cash record from the ESTAR_TRADED_CASH_ACTIVITY table.

System Control Value Descriptions

The following table lists the acceptable system control values with descriptions.

System Control Value

Description

System Control Value

Description

0

Do not create a row from the ESTAR Cost Object (BLOB). Retrieve the data from the ESTAR_TRADED_CASH_ACTIVITY table.

1

Create a row from the ESTAR Cost Object (BLOB) only if Cash Event Spawned field (tag 751) = N. Create a reflexive row and zero out the STAR PERF FLOW fields.

2

Create a row from the ESTAR Cost Object (BLOB) only if Cash Event Spawned field (tag 751) = N. Create a reflexive row and do not zero out the STAR PERF FLOW fields.

3

Create a row from the ESTAR Cost Object (BLOB) only if Cash Event Spawned field (tag 751) = N. Do not create a reflexive row and zero out the STAR PERF FLOW fields.

4

Create a row from the ESTAR Cost Object (BLOB) only if Cash Event Spawned field (tag 751) = N. Do not create a reflexive row and do not zero out the STAR PERF FLOW fields.

5

Create a row from the ESTAR Cost Object (BLOB) always. Create a reflexive row and zero out the STAR PERF FLOW fields.

6

Create a row from the ESTAR Cost Object (BLOB) always. Create a reflexive row and do not zero out the STAR PERF FLOW fields.

7

Create a row from the ESTAR Cost Object (BLOB) always. Do not create a reflexive row and zero out the STAR PERF FLOW fields.

8

Create a row from the ESTAR Cost Object (BLOB) always. Do not create a reflexive row and do not zero out the STAR PERF FLOW fields.

9

Create a row from the ESTAR Cost Object (BLOB) always. Do not create a reflexive row and zero out the flow fields. If the event is a cancel on a different date then the original, perform additional logic to find the target.

System Control Value Examples

The following examples depict system control values associated with several types of transactions that affect Eagle Performance:

  • A BUY transaction is stored in the CASH_ACTIVITY table as a positive STAR_PERF_ FLOW. All BUY events generate cash transactions in Eagle Accounting. Therefore, STAR to PACE Direct retrieves the cash activity record from the ESTAR_TRADED_CASH_ACTIVITY table. The system control value is 0.

  • A REVSPLIT transaction is stored in the CASH_ACTIVITY table as a negative STAR_PERF_FLOW. Not all REVSPLIT events generate cash transactions in Eagle Accounting. Therefore, STAR to PACE Direct retrieves the cash activity record from the ESTAR Cost object or Cost BLOB. The system control value is 7.

  • A CLOSEFUTURE transaction is stored in the CASH_ACTIVITY table as a negative STAR_ PERF_FLOW. CLOSEFUTURE events can generate cash transactions (commissions) in Eagle Accounting. Therefore, STAR to PACE Direct retrieves the cash activity record from the ESTAR CASH tables if the Cash Event Spawned field (Tag 751) has a value of Y (Yes). If Tag 751 has a value of N (No), then the cash activity row is created from the ESTAR Cost Object (Cost BLOB). The system control value is 3.