Reviewing Custom GL Lines Plug-in Executions

Custom GL line plug-ins may be set to run asynchronously in the following instances:

If you have multiple custom GL line plug-in implementations that cause long transaction save times, some may be configured to run asynchronously.
If you use both the Custom GL Lines Plug-in and Inventory features, when the cost of goods sold (COGS) changes, cost amounts are updated. The Custom GL Lines Plug-in runs asynchronously to update the GL impact in the transactions.

When a transaction is updated by the COGS process, the GL impact is updated. Then, the Custom GL Lines Plug-in implementations on the transaction are triggered. After a change causes the COGS update, the Custom GL Lines Plug-in process runs to update the GL impact a second time. When you view the GL Impact page, you may see a message at the top of the page to indicate that the GL impact may change. This message appears if an update process is scheduled or in progress.

To address any exceptions that occurred when a custom GL line plug-in was run asynchronously , the Review Custom GL Plug-in Executions page displays Incomplete and Failed executions. You must have the administrator or the Review Custom GL Plug-ins Executions permission to access the Review Custom GL Plug-in Executions page. Go to Customization > Plug-ins > Review Custom GL Plug-in Executions.

The Review Custom GL Plug-in Executions page displays incomplete and failed Custom GL Plug-in executions from subsidiaries and accounting books to which you have access. Transactions appear on this page only if the last run of the custom GL plug-in was incomplete or failed.

By default, failed or incomplete transactions for all accounting periods are displayed. Select the accounting period as required. To include closed periods in the Accounting Period list, check the Include Closed Periods box.

Each task listed displays the transaction ID, transaction type, accounting period, and execution date. An incomplete task has at least one pending or running task for the custom GL plug-in in the selected period.

Note:

If you update a transaction in a closed period that triggers the Custom GL Lines Plug-in, an error appears. You can either ignore the error, or open the period to run the plug-in again.

For any failed executions, you can select the item and then click Execute Selected to run the plug-in again. The page is refreshed, the status of the line becomes incomplete, and the line is displayed on the Incomplete subtab.

You can ignore an error, but if you decide to run the associated custom GL lines plug-in in the future, you have to edit the transactions manually. To ignore an error, check the line and click Ignore Selected. A confirmation message appears. Click Yes to confirm and remove the transaction from the list.

To view information about custom GL line plug-in executions that completed successfully, see the Custom GL Lines Audit Log Page.

Related Topics