In Eagle Accounting, various global process events generate secondary events, or loopbacks. For example, when processing a corporate action, the system first performs a query to determine which entities and securities are eligible for a given corporate action process based on the date range you entered. The query is considered the initial event. The secondary event, or loopback, is the actual processing of the corporate action based on the query results from the initial event.

Each time a loopback is created, the accounting engine writes a record to the ESTAR_LOOPBACK_EVENTS table. When the engine is finished processing the loopback, the record is updated. The Global Process Center looks to this table to determine whether the engine has finished processing an event.

About the Global Process Workspace

For monitoring, the Global Process workspace includes the following areas:

• Loopbacks Summary. Upper pane. Displays the loopback summary timeframe and associated statistics including loopback status and high level totals.
• Loopbacks Search. Criteria to search for loopbacks.
• Loopbacks. Center pane. Displays the status of each submitted and processed job for the specified system date and other search criteria.
• Loopback Details. Bottom pane. Displays account and security details for the selected job.

You can query and review processed or pending jobs.

• LoopBacks Details. Displays account and security detail for each submitted and processed job for the current system date.

View Lookbacks Summary Information

• Last 24 Hours. Displays metrics for jobs that have been processed and rejected in the last 24 hours.

Search for Loopbacks

• LoopBacks. Displays the status of each submitted and processed job for the current system date.

View Loopback Details

You can view loopback details by clicking the row for a specific global job in the Loopbacks pane.The Lookback Details pane 

The detail from the STAR to PACE Batch job (Event Type = ADDMSTARPOS) is shown below in the bottom pane.

While a loopback is being processed, it is assigned a pending status  . It may be in a pending status for less than a second or much longer, depending on the environment and other engine activity. When processing is completed, the loopback is assigned a Processed status  or a Rejected status  .

If the event is successfully processed, you can use the Position Viewer tool and Eagle reports to validate the accounting results. If the loopback failed, you can view rejection details in the Exceptions workspace in Automation Center and resolve any issues. After resolving the issues, you may need to resubmit the event.