Eagle provides a list of default code values for the STAR_PERF_FLOW code category. You can add and change these values. After you revise any code value, you must assign a system control value and then refresh the code map cache before you can use the added/changed values.
To add / change a STAR_PERF_FLOW code value:
- In Accounting Center, in the left navigation pane, click Setup > Codes.
You see the Codes workspace. The Codes workspace also is available in other centers. - In the Codes/Code Values tab, click the chevron
to to the right of the magnifying glass to expand the Search Details pane. - Complete the search criteria, as follows: -
Set Code Name to STAR_PERF_FLOW.
- Set Source Name to EAGLE PACE. - Click the Search button in the Search Details pane.
In the grid, you see a row for the code name, STAR_PERF_FLOW. - Click the arrow at the left of the row to expand the row.
You see additional rows for each code value associated with the STAR_PERF_FLOW code category. - At the bottom of the list, click Add Code Value if you want to add a new code value. Or, double-click the row for a code value if you want to change an existing code value.
You can define values for the Code Value Short Description, Code Value Long Description, Source Name, and Code Value System Control. - In the Code Value Short Description box, specify the event type as the code value.
For example, BUY. - In the Code Value Long Description box, specify a value that determines how the event type affects cash flows for performance purposes.
You determine these values from the security flow perspective. The performance_flow_descr system stores the translated value in the PERFORMANCE_FLOW_DESCR field in the cashCASH_activity ACTIVITY table in Eagle PACE stores the translated value.
Options include:
- Positive. The event generates a positive cash flow for performance purposes.
- Negative. The event generates a negative cash flow for performance purposes.
- No Flow. The event generates neither a positive or negative cash flow for performance purposes.
Note: | The fields established with positive/negative flow values (or zeros, when no flow is selected) follow: |
...
...
- In the Source Name list, select the source of the data, that is, EAGLE PACE.
- In the Code Value System Control box, assign a system control value to define how STAR to PACE Direct translates the new code value (that is, event type) in support of Eagle Performance.
For more information, see
...
- Manage System Control Values.
- Click the code category row.
In the Success box, you see the message: Code Value successfully created. The system adds the code value to the CODE_VALUES table for source EAGLE PACE within the category STAR_PERF_FLOW.
...
The system control value determines how STAR to PACE Direct translates an event in support of the Eagle 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.
Note: | You must set the Create Performance Cash Flows in PACE field (tag 5398) equal to Yes, when you configure the STAR to PACE Direct Interface Fields for an entity. See "Define the STAR to PACE Direct Interface Fields", in Chapter 2: Setting Up STAR to PACE Direct for more information. |
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).
Note: | The Cash Event Spawned field (tag 751) is set to Yes whenever a cash activity record is generated. 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. |
...
When you add a new STAR_PERF_FLOW code value, 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 cache to cause the added/changed STAR_PERF_FLOW code value to update in memory.
The following table lists the acceptable system control values with descriptions.
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 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. |
...
The following examples depict system control values associated with several types of transactions that affect Eagle Performance.
...
The fields established with Positive/Negative flow values (or zeros, when you select No Flow) follow:
- base income flow (tag 10720)
- base principal flow (tag 10719)
- base total flow (tag 10718)
- local income flow (tag 10717)
- local principal flow (tag 10716)
- local total flow (tag 10715)
- sys currency income flow (tag 11740)
- sys currency principal flow (tag 11739)
- sys currency total flow (tag 11738)|