Test the Plug-in Implementation

To test a Custom GL Lines plug-in implementation, perform the following tasks:

Create a custom role for the plug-in implementation. The Execute As Role field determines the role under which the plug-in implementation script runs. This role requires the SuiteScript permission.

For more information about the Execute As Role field, see Adding the Plug-in Implementation. For more information about custom roles in NetSuite, see Customizing or Creating NetSuite Roles.
Configure the transaction types, subsidiaries, and accounting books for the plug-in implementation, depending on the accounting features. See Configuring the Custom GL Lines Plug-in Implementation.
Enable the plug-in implementation at Customization > Plug-ins > Manage Plug-ins. See Enabling the Custom GL Lines Plug-in Implementation.
Create transactions that will impact the general ledger and test the script and plug-in behavior.
Examine the GL impact of the transaction. Make sure that the plug-in implementation performs as expected.

Important:
Plug-in implementations modify or supplement NetSuite business logic, changing the manner in which standard business processes run. Make sure that the GL impacts on the transaction types, subsidiaries, and accounting books accurately reflect the customization in the plug-in implementation script file and the plug-in implementation configuration.

You should test your plug-in implementation on each NetSuite version and release in use by your NetSuite customers.

If you use the Custom GL Lines Plug-in with Custom Segments, the plug-in may fail for any one of the following reasons:

Custom segment does not exist.
Custom segment is inactive.
The role set up to run the plug-in does not have permission to set values on the custom segment.
The custom segment does not impact GL.
The Custom Segment feature is not enabled.