Configuring the Custom GL Lines Plug-in Implementation
Configure the transaction types, subsidiaries, and accounting books for a Custom GL Lines plug-in implementation from the Plug-In Implementation page. Any configured transaction type with an entity associated with a configured subsidiary triggers the plug-in implementation execution when you save the transaction. If you use the Multi-Book Accounting feature, NetSuite executes the plug-in implementation logic on each of the accounting books you configure for the implementation.
For more information about how the transaction types, subsidiaries, and accounting books affect the running of a plug-in implementation, see Custom GL Lines Plug-in Process Flow.
The SuiteScript permission is required to configure a Custom GL Lines plug-in implementation.
To configure a Custom GL Lines plug-in implementation:
-
Go to Customization > Plug–ins > Plug-in Implementations.
-
Click Edit next to the Custom GL Lines plug-in implementation that you want to configure.
-
Click Configure. The Custom GL Lines: Configuration page appears.
-
By default, plug-ins are run synchronously. If you have multiple plug-ins on a specific transaction type, you may notice that it takes a long time to save transactions. If a transaction type takes a long time to save, you can set one or more of the plug-in implementations to run asynchronously
Every plug-in runs independently and has access only to its own lines and the standard lines, which ensures that if one plug-in fails that the others can run. No priority is assigned to individual plug-ins, meaning that they are run in any order.
-
By default, custom GL lines plug-ins are not run in closed periods and the original GL impact of custom GL lines is preserved. To run the custom GL lines plug-in on transactions in closed periods, check the Run in Closed Periods box. If you check the box and edit a transaction, an error message appears indicating that the GL impact cannot be changed in a closed period.
Note:The Run in Closed Periods setting affects only transactions that have a posting period.
-
The Effective Date and End Date fields are useful when you are updating a script file or adding a new script file for an implementation. In the Effective Date field, enter a start date. The plug-in runs on transaction dates that fall on or after this date. This field is blank by default and is not required.
-
To edit or inactivate the plug-in and preserve the existing GL impact, enter an end date for the older plug-in in the End Date field. The plug-in does not run on transactions dated after this date. This field is blank by default and is not required.
If you are loading a new script for a Custom GL Plug-in implementation, on the configuration for the older version of the plug-in, enter an end date. Add the new script and create a new plug-in implementation with an effective date of the day after the end date of the old plug-in implementation.
If you update the script used by the existing plug-in implementation file, all plug-in implementations that use the file are affected. The best practice is to add a new script file and create a new plug-in implementation with a different effective date.
Note:If the end date of one plug-in implementation is the same as the effective date of another plug-in, both plug-ins run on that date. To ensure that plug-ins do not overlap on transaction dates, the effective date of the new plug-in should be one day after the end date of the older plug-in.
-
Select the transaction types on which the plug-in implementation executes.
To select multiple or all transaction types, press and hold the Ctrl key on your keyboard, then continue selecting transaction types.
Check the ALL box to select all of the transactions types for this configuration.
-
In the Subsidiaries list, select one or more subsidiaries, or check ALL.
-
In the Accounting Books list, select one or more accounting books, or check ALL
-
Click Save.
When configuring additional plug-ins that overlap with an existing implementation, an information message appears about running the plug-in asynchronously. You can save the configuration, but if you notice long transaction save times, consider making one or more plug-in implementations asynchronous to speed the save process.