About Loopback Processing Status
A loopback has one of the following processing status values. You can view a colored icon that identifies the status for each row when you view loopback details.
| Icon | Color | Status | Description |
|---|---|---|---|
| Green | Processed | Loopback processed successfully |
| Yellow | Pending | Submitted; loopback still submitting |
| Red | Rejected | Loopback processed with errors |
| Blue | Overridden | Loopback was overridden |
About the Loopback Lifecycle
During its lifecycle, the loopback's processing status indicates whether it finished processing and whether it processed successfully.
Phase 1: Eagle Accounting event runs, creating a loopback
You can submit the event through a panel, schedule it to run automatically, or through a generic stream. If the event creates a loopback, you can view and track the loopback in the Global Process workspace.
Event Examples: BUY, SELL, COUPON, CASHDIV, MISCIN, MATURITY, SHORTSELL, OPENFUTURE, NONTAXMERGR
Phase 2: Loopback is Pending until processing completes
While the system is processing a loopback, it assigns the loopback a 
Pending status. The loopback remains in a Pending status until processing of the event is complete, that is, while the system is processing it or while it is in a queue waiting for the system to process it. The loopback may be in Pending status for less than 1 second or for much longer, depending on environment data and on other engine activity.
Phase 3: Loopback is Processed or Rejected
When processing completes, the system assisgs assigns the loopback either a Processed successfully or Rejected status, as follows:
| If the system processes the loopback successfully, it is included in the Total Processed column and has a Processed status. |
| If the system processes the loopback and the loopback is rejected, or fails, it is included in the Rejected Column and has a Rejected status. |
Each time a loopback is created, the accounting engine writes a record to the ESTAR_LOOPBACK_EVENTS table. When the engine finishes processing the loopback, it updates the record. When you view loopback information, the system looks to this table to determine whether the engine finished processing an event.
Phase 4: Validation
| If the loopback is Processed, you can validate accounting results in Position Viewer and other Eagle reports. |
| If the loopback is Rejected, research the rejection. Review the rejection details in the Exceptions workspace and resolve the issue. You may need to resubmit the event. |
About Loopback Summary Level Information
Loopback summary information displays the loopbacks associated with the last loopbacks query executed. You see the number of loopbacks per MT Type/Event Type combination for a given time frame.
In the results shown for the following EARN event, of 350 loopbacks generated, 1 is pending, 236 processed successfully, and 113 processed with errors.
About Loopback Detail Level Information
Loopback details provide detailed information for a selected loopback summary row. After you click a row for a specific global job in the Loopbacks pane, you can view its corresponding loopback details in the Loopbacks pane.
The detail from the Run Income Accruals job (Event Type = EARN) appears in the following figure.
About Loopback Message and Exception Details
When you view loopback details, you can additionally view the loopback message associated with loopback details. You can also view the rejection details for loopback details with a Rejected status. The Exception Details tab includes Message Details, Message Text, and Error Description tabs. These tabs provide a snapshot of the information in the Exception workspace rejection queue for the selected loopback details.
About Action Rules for Loopbacks
You can research loopback details with a Rejected status to see why the loopback was rejected. You can view the Exception Details tab for loopback details to see an error description, and you can review information about the loopback message and the exception message to understand the cause of the problem. In some cases, you can then select the Exceptions workspace to fix the issue, and can choose an option like the Quick Fix option to correct the problem. In other cases, such as missing reference data, you may need to correct information elsewhere before you can resubmit the loopback for processing.
In cases that involve engine-level errors that occurred during a loopback (for example, accrual related errors), the system does not store the panel used to submit the failed message. To repair errors of this nature, some Eagle clients find it useful to create an action rule. Action rules are available for use in many Eagle centers. Action Rules are essentially conditional "if/then, and/or" statements. By default, action rules require that you identify a Message Type (MT) and Submessage Type, to which the rule applies. You can also identify other data elements that can help to specifically identify the original event, and determine the panel to use in the repair process.
You can create action rules for use with loopbacks in the Global Process and Monitor workspaces. The action rules are a key to facilitating the process of correcting and resubmitting rejected events in the Exceptions or Global Process workspace. They allow users to automate the process of selecting the correct panel.
For example, say your earnings global proccess often fails due to a missing FX rate. Whenever you research the error associated with earnings loopback rejections, you see an error message related to a missing FX rate, and you then need to open Reference Data Center to add an exchange rate. You can set up an action rule that recognizes the error associated with a missing FX rate for this global process. Then whenever you select the loopback detail row for the earnings global process associated with that error, the system automatically provides an action rule option for you to open the panel needed to supply the missing FX rate
| Info |
|---|
Action rules are already established in the core Eagle Accounting solution. Creating or modifying action rules is typically done only when an Eagle client deploys customized panels. |