Understand the STAR to PACE Direct Workflow
- Nancy Cohn (Deactivated)
To use STAR to PACE Direct, you define the STAR to PACE Direct interface fields at the entity/basis level in Eagle Accounting or at the master fund/basis level using Eagle's mutual fund accounting solution. You can then transfer the following accounting data automatically on a periodic basis:
Holdings and positions
Trade activity
Traded cash activity
Foreign settled cash activity
Income
General ledger balances
The following figure provides a high level overview of the STAR to PACE Direct workflow.
One of the key modules involved in the STAR to PACE Direct process is the Eagle Integrated Scheduler, which schedules STAR to PACE data transfer events, such as the Batch, Delta, and General Ledger Balances processes. For details about each process, see Transfer Accounting Data.
The system sends the request to the STAR Engine. The STAR to PACE event pulls the data from the ESTAR Cash Tables, ESTAR Income Tables, ESTAR Cost Object (BLOB), ESTAR Ledger Balances Table, and the Reference Tables into a result set and pushes that data into the appropriate tables in the Cash, Holding, Trades, and Ledger databases in Eagle PACE.
A key table in the STAR to PACE Direct process is the STAR Delta Trigger Log. This table is specific to the Delta Process only. The Delta Trigger Log tells the Delta process that a position has changed due to a cost, cash, or income transaction. For details about the Delta Trigger Log, see Perform Data Maintenance. The Delta event can be triggered once per minute, depending on your processing requirements. The event checks the STAR Delta Trigger Log to determine if there is anything new to transfer, and if there is, the event pulls the data and pushes it from Eagle STAR to Eagle PACE.
About the BLOB
Eagle uses relational database architecture to manage data. Standard database tables hold descriptions that identify the data. The binary forms are accommodated using the database Binary Large Object (BLOB) feature, which stores large amounts of history and minimizes input/output for high speed transaction processing.
The BLOB:
Stores information in a tag value format. The tag is a unique number (such as, tag 55) that is assigned a value (such as BUY) for processing by the system.
Defines each element and tag combination as a pair. Multiple pairs of information are stored on a structure defined as a row.
Groups multiple rows together to form a set. A set is a structure with two dimensions where each cell contains a pair.
About the ESTAR Cost Object (BLOB)
The ESTAR Cost Object is a BLOB that contains levels linking to actual events against a position.
For example, Level 150 represents open lots. The information about each open lot is stored in a tag value format. See the highlighted row in the following figure. The following numbers are tags: 55, 35, 40, 45, and 50. Each tag is assigned to a value, which is separated by a colon. For example, the value for tag 55 is BUY.
The ESTAR Cost Object levels include:
Level 100 = Object Summary
Level 120 = Current Position Level
Level 150 = Open Lots
Level 180 = Close Lots
Level 250 = Cancel Open
Level 280 = Cancel Close
Level 350 = Open Adjustment
Level 380 = Close Adjustment
Level 400 = Cancel Close Activity
Level 450 = Cancel Open Adjustment
Level 480 = Cancel Close Adjustment
The following optional levels may also be included:
Level 700 = Work Level
Level 900 = Ledger Postings
Level 600 = GEVENT (secondary events or loopbacks created by an initial event)
About Querying Event Types Using Position Viewer
Tabs in Accounting Center's Position Viewer workspace link to the levels in the ESTAR Cost object, also called the Cost BLOB. For example, the Open Lots tab displays data at "Level 150" in the Cost object, and the Summary tab displays data at "Level 100."
You can use the Position Viewer to query all events that result in the current position, as well as any adjustments or cancellations.