Run a Global Process Manually in Accounting Center

You can use the Accounting Center's Global Process workspace to run a global process manually. For example, you can submit the Approve Margin panel to perform global processing that approves variation margin.

To run a global process manually in Accounting Center:

1. In Accounting Center, in the left navigation pane, click Processing & Exceptions > Global Processes.
   You see the Global Process workspace. In the left navigation pane, you see global process categories such as Cash, Earnings, and Expenses.
2. Click a category and then click the name of the global process that you want to run.
   For example, click Cash and then click Run Contract Cash. You see the panel for the selected global process.
3. Enter the criteria for the selected global process, and then click Submit.
   After you submit the panel to run a global process, you see the status of the event loopbacks in the Loopbacks pane at the bottom of the panel. 
4. Review the results for the event's loopbacks.
   The Loopbacks pane in each global process panel has a Total Generated column that identifies the number of loopbacks processed. It includes a column for each processing status, such as Total Pending, Total Processed, Total Rejected, and Total Overridden. If the system generated no loopbacks (that is, the system found nothing to process), you see a message that no loopbacks were produced.
5. Click the the Summary tab, and review the total number and processing status of loopbacks processed.
6. Click the Details tab, 
   For each successfully processed row, the Status column shows  Processed. For each rejected row, the Status column shows  Rejected.

Run a Global Process Manually in Automation Center

You can use Automation Center's Monitor workspace to run a global process manually. For example, you can submit the Approve Margin panel to perform global processing that approves variation margin.

To run a global process manually in Automation Center:

1. In Automation Center, in the left navigation, click Automation Desk > Monitor.
   You see the Monitor workspace. 
2. Under Select Type, click Loopbacks.
   Loopbacks is selected by default.
3. On the Home tab, in the View group, click Action Rules.
   You see a list of categories for available global processes, such as Expenses, Earnings, and Settlements. If you created your own action rules for use in the Monitor workspace, you also see categories for those action rules. 

4. Point to a global process category, and then click the name of the global process you want to run.
   You see the panel for the selected global process.

   The legacy global process panel names you can view in Automation Center vary slightly from the global process panel names you can view in Accounting Center.

5. Enter the criteria for the global process, and then click Submit.
   After you submit the panel to run a global process, you see the status of the event loopbacks in the Loopbacks pane at the bottom of the panel.
6. Review the results for the event's loopbacks. 
   The Loopbacks pane in each global process panel has a Total Generated column that identifies the number of loopbacks processed. It includes a column for each processing status, such as Total Pending, Total Processed, Total Rejected, and Total Overridden. If the system generated no loopbacks (that is, the system found nothing to process), you see a message that no loopbacks were produced.
7. Click the the Summary tab, and review the total number and processing status of loopbacks processed.
8. Click the Details tab, 
   For each successfully processed row, the Status column shows  Processed. For each rejected row, the Status column shows  Rejected.

Review Results when You Run a Global Process Manually

When you run a global process manually, you can review the results for the event's loopbacks in the global process panel. You can research additional information for loopback details with a Rejected status in the global process panel.

To review results for a global process that you ran manually:

1. Run a global process manually in Accounting Center or Automation Center. 
   You see the status of the event loopbacks in the Loopbacks pane at the bottom of the panel. The Loopbacks pane in each global process panel has a Total Generated column that identifies the number of loopbacks processed. It includes a column for each processing status, such as Total Pending, Total Processed, Total Rejected, and Total Overridden. If the system generated no loopbacks (that is, the system found nothing to process), you see a message that no loopbacks were produced.
2. Click the the Summary tab, and review the Total Rejected column value.
   The Total Rejected column identifies the total number of loopbacks you processed for the event with a Rejected processing status.
3. Click the Details tab, 
   For each rejected row, the Status column shows  Rejected.
4. Right-click the rejected loopback detail row, and then click Show Loopback Details.
   You see the Loopback Message tab and the Exception Details tab for the selected loopback details row.
5. Click the Exception Details tab. 
   The Exceptions Details tab provides a snapshot of what is in the rejection queue for this message. You see the following three tabs: 
   - Message Details. Provides information regarding the data elements and their associated values. Shows Tag ID, Name, and Value.
   - Message Text. Shows the cryptic tag/value data sent to the engine.
   - Error. Describes the error that occurred.
6. When you review loopback details, you can do the following:
   - Override the loopback status
   - Print or export loopback data
   - Refresh loopback data
   - Close the rejection from the Exception Details
7. If you want to open the rejection queue, click Exceptions to open the Exceptions workspace and correct the problem that caused the rejection. 
   If you are using Automation Center, you can open the rejection queue to display the exceptions for a selected loopback detail.

After the problem that caused the rejection is corrected, you can reprocess the event that initially failed.