1. SuiteCloud Platform
  2. Core Plug-ins
  3. Custom GL Lines Plug-in
  4. Custom GL Lines Plug-in Overview
  5. Custom GL Lines Plug-in Process Flow

Custom GL Lines Plug-in Process Flow

A Custom GL Lines plug-in implementation runs based on how the plug-in implementation it's configured. The implementation runs when you save a transaction of the type and subsidiary you've configured. The subsidiary is the subsidiary to which the transaction belongs. The plug-in implementation may also run multiple times, one time for each accounting book configured for the plug-in implementation.

For example, the following plug-in implementation runs when you save an invoice for the Parent Company or Czech Subsidiary, and it runs on both the primary and secondary books.

Custom GL Lines Configuration page

The following diagram shows the processing model of the Custom GL Lines plug-in implementation:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         

The plug-in implementation executes according to the following process:

  1. User saves a transaction for an entity in a subsidiary. If the transaction type, entity, and subsidiary match the plug-in implementation configuration, the plug-in runs on that transaction. The plug-in can run either during transaction the save or asynchronously, depending on the Asynchronous box on the configuration page The subsidiary is the subsidiary to which the transaction belongs.

    NetSuite first creates the standard lines for the primary book.

  2. Plug-in implementation runs on the primary accounting book. NetSuite calls the customizeGlImpact(transactionRecord, standardLines, customLines, book) or customizeGlImpact(context) functions with the primary book AccountingBook object.

    NetSuite creates any custom lines in the primary book set up for the plug-in implementation. If you don't use Multi-Book Accounting, the process is complete. Otherwise, NetSuite continues to map standard and custom lines to the secondary books.

  3. NetSuite determines which lines should be applied to any secondary books. By default, NetSuite maps standard lines to the appropriate secondary accounting books, based on any mapping rules set up for Multi-Book Accounting. NetSuite does the same mapping for all custom lines with the setBookSpecific(bookSpecific) or isBookSpecific() methods set to false.

  4. NetSuite creates standard lines, plus any mapped standard lines and any custom lines that aren't specific to the primary book, in the secondary accounting books.

  5. The plug-in implementation runs on the secondary accounting books configured for the plug-in implementation. NetSuite executes the customizeGlImpact(transactionRecord, standardLines, customLines, book) function for each secondary book AccountingBook object for the transaction.

    NetSuite creates the custom lines on the secondary accounting book.

  6. Transaction save finishes. You can see the general ledger impact of the transaction by going to Actions > GL Impact. If the plug-in runs asynchronously and is still pending, an information message appears on the GL Impact page. Custom GL Lines from asynchronous plug-ins are shown after the plug-in runs. When costing updates are performed (for example, the COGS update), the plug-in may run asynchronously, and the values on the GL Impact page may change after the update.

Important:

The current version of the Custom GL Lines Plug-in is always used.

Related Topics

General Notices