After you have created an SSP Application record and uploaded its assets to the file cabinet, you can use the Bundle Builder in NetSuite to package the SSP application into a SuiteApp for distribution to other NetSuite accounts. For more information on creating a bundle, see the help topic Creating a Bundle with the Bundle Builder. Note that if you do not want users in target accounts to edit SSP application files, you can lock the SSP application as part of creating the bundle.
Additional notes on bundling SSP applications:
SSP applications are listed in Step 3 of the Bundle Builder, where you select objects to include in the bundle.
When you select an SSP application here, the SSP Application record and all of the files in the file cabinet application folder for the selected SSP application are included in the bundle.
When the bundle is installed in a target account, the complete SSP Application record is copied to that account. Also, all files are copied to an application folder in the target account file cabinet, in the following location:
<Default Target HTML Hosting Root>: /SSP Applications/<Application Publisher>/<Application Name>
As of 2019.1, when you update an installed bundle that includes an SSP application, the script deployments are not updated in the target account. Because script deployments are not updated, the existing touch points are not overwritten and both the Log Level and Status fields are also not updated in the target account. The Log Level and Status fields can be viewed on the Script Deployment page.