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

Eagle provides a list of default code values for the STAR_PERF_FLOW code category. You can add and change these values. When 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:

  1. 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.
  2. In the Codes/Code Values tab, click the chevron  to the right of the magnifying glass to expand the Search Details pane.
  3. Complete the search criteria, as follows: -
    Set Code Name to STAR_PERF_FLOW.
    - Set Source Name to EAGLE PACE.
  4. Click the Search button in the Search Details pane.
    In the grid, you see a row for the code name, STAR_PERF_FLOW.
  5. 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.
  6. 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.
  7. In the Code Value Short Description box, specify the event type as the code value.
    For example, BUY.
  8. 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 system stores the translated value in the PERFORMANCE_FLOW_DESCR field in the CASH_ACTIVITY table in Eagle PACE.
    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.
  9. In the Source Name list, select the source of the data, that is, EAGLE PACE.
  10. 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.
    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.
    For more information, see About System Control Values.
  11. 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.
  12. You must refresh the cache to cause the added/changed STAR_PERF_FLOW code value to update in memory.
    For more information, see Refresh the Code Map Cache.

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)|


  • No labels