Custom GL Lines Plug-in Implementation Development
You can develop a Custom GL Lines plug-in implementation for each use case where you want to change general ledger entries for transactions. One plug-in implementation can process multiple transaction types, or you can create a separate plug-in implementation for each transaction type.
To create a plug-in implementation, use a development account to build and test it. Then, use SuiteBundler to bundle the plug-in objects and distribute them to other NetSuite accounts. NetSuite administrators use the bundle to install and enable the plug-in implementation. For more information about administration tasks for a Custom GL Lines Plug-in bundle, see Custom GL Lines Plug-in Implementation Administration.
If you use the Custom GL Lines Plug-in with Custom Segments, any segments affected by the implementation must be flagged as having GL impact. When the plug-in uses a custom segment that is not marked as having a GL impact, you'll see an error message.
What you include in a Custom GL Lines plug-in implementation depends on the accounting features used in the NetSuite account and the following properties that you configure for each plug-in implementation:
-
Transaction types. A Custom GL Lines plug-in implementation runs when you save a transaction it's set up for, where the entity for the transaction is associated with a specific subsidiary. You can include code in the script file that applies only to specific transaction types.
-
Subsidiaries. In a One World account, the plug-in implementation affects only the general ledger entries for the subsidiaries you set up for it.
-
Accounting books. The plug-in implementation affects only the accounting books you set up for it. If you use Multi-Book Accounting, you can have the plug-in implementation change or add custom general ledger entries in multiple accounting books. If you do not have the Multi-Book Accounting feature enabled, the plug-in implementation affects only the general ledger entries in the primary accounting book.
You can have more than one Custom GL Lines plug-in implementation enabled in an account. If you enable a plug-in implementation that conflicts with an existing implementation, you receive a warning. Having several implementations for one transaction can cause longer save times. You can save the implementation, but if you notice long transaction save times, try setting one or more plug-in implementations to run asynchronously.
For more information about how a Custom GL Lines plug-in implementation modifies the general ledger impact for a transaction, see Custom GL Lines Plug-in Process Flow.
The following table describes the basic steps to develop a single Custom GL Lines plug-in implementation:
|
Step |
Description |
|---|---|
|
Enable features |
Enable the Custom GL Lines Plug-in and Server SuiteScript features. See Enabling Features for a Custom GL Lines Plug-in Implementation. |
|
Gather required internal IDs |
In a plug-in implementation, you can reference internal NetSuite IDs for records and accounts. Before you create the script file, make sure you note these values. |
|
Create script file |
Create the script file for your Custom GL Lines plug-in implementation. See Plug-in Implementation Script File Creation for SuiteScript 1.0. |
|
Add the plug-in implementation |
Add the plug-in implementation using the plug-in script file and any required utility files that you created in the previous step to the development account. |
|
Test the plug-in implementation |
Test how the plug-in implementation works. |
|
Bundle the plug-in implementation |
Bundle both the plug-in implementation and other required objects for distribution to other NetSuite accounts. |