Multiple Datasets in One Workbook
As of 2020.2, you can connect multiple datasets to a single workbook, and any visualization within the
workbook can be based on a different dataset. This enhancement enables you to analyze different metrics
without switching between browser tabs or creating multiple workbooks. For example, if you are a sales
representative and you want to analyze your actual performance and your sales targets, you can now do
so within the same workbook. From a collaboration perspective, this change also means that you can now
share a single workbook with other users, as opposed to sharing multiple workbooks or datasets.
For more information about creating a workbook using multiple datasets, see the help topic Creating a
Workbook.
As of 2020.2, the following enhancements have been made to the Workbook Formula Builder:
- The Formula field is automatically populated with line numbers for improved readability of longer
formula definitions.
- When you validate a formula, if there are errors, the Formula Builder highlights the line where the
error is located.
- Formula function descriptions now include links to add sample formulas to your definitions, enabling
you to try different functions even if you are not sure about the correct syntax.
To learn more about creating and adding custom formula fields to your datasets, see the help topic
Formula Fields.
Analytics Portlet Supports Workbook Table Views
In 2020.2, you can explore the data of your workbook table views on your dashboard. You can now add
any workbook visualization to the Analytics portlet: charts, pivot tables, and table views.
In your table view portlets, you can do the following:
- View the column summary – When you select a column in your table view, you can also view the
summary of the results in the table footer. The information shown depends on the field type, and can
display information such as the count, count (distinct), average, and so on.
- Sort and filter your results – The table view portlet includes only the sorting and filtering options that
were added in your workbook table view. If you want to change the sorting and filtering options, you
can open the workbook and make any edits in your workbook table view.
For table view portlets, you can set layout options, such as the portlet title and the number of rows visible
in the portlet. As with charts and pivot tables, you can also access your workbooks through table view
portlets.
For more information about setting up the portlet, see the help topics Setting Up the Analytics Portlet and
Workbook-based Portlets.
New Workbook and Dataset Details Panel
A new Details panel is available on the Analytics Home page. To display the panel for any workbook or
dataset that you have access to in your account, click Details.
- For workbooks, the Details panel shows the visualizations that are set up in the workbook and the
underlying datasets that they are based on. On the Details panel, you can display the fields used in
each visualization, open the workbook, or open any of the connected datasets.
- For datasets, the Details panel shows the record types, fields, and criteria that are used to define the
dataset. The owner and last modified date are also displayed on the Details panel. On the Details panel
you can open the dataset or create a workbook based on the dataset.
To learn more about the Details panel, see the help topic Analytics Home Page.
Enhanced Filtering Options for SuiteAnalytics Workbook
In 2020.2, the following filtering enhancements were made to datasets and workbook visualizations:
- Dynamic Date Ranges in Date Fields for Charts and Pivot Tables
- Condition-Based Filters in Numeric Fields for Charts and Pivot Tables
- Enhanced Search Capabilities for Value-Based Filters in Datasets and Table Views
Dynamic Date Ranges in Date Fields for Charts and Pivot
Tables
Previously, you could only filter results by adding specific dates. There was no way to select default date
ranges or dynamic dates, such as today, that update when the workbook is run. Now, you can select
default date ranges and dynamic dates in charts and pivot tables to filter your results.
Condition-Based Filters in Numeric Fields for Charts and Pivot
Tables
Previously, you could add condition-based filters in your datasets and table views to show results that
match a numeric range. If you added the filter to a dataset field, this condition affected the results of all
the associated workbook visualizations. In 2020.2, you can apply this filter to a specific chart or pivot table
without affecting the rest of your visualizations.
Enhanced Search Capabilities for Value-Based Filters in
Datasets and Table Views
Previously, when you defined a value-based filter, you could search for a specific value but the search was
limited to 10,000 value entries. If the desired value was not among the first 10,000 value entries, you had
to scroll down and find it manually. Now, you can search for a specific value with no limitations on the
number of value entries.
For more information, see the help topic Workbook Visualization Filters.
Usability Enhancements for SuiteAnalytics Workbook
As of 2020.2, the usability enhancements described in the following sections were added to SuiteAnalytics
Wokbook.
You can add fields to the Criteria Builder from the Fields list on the left and from the Data Grid. To add
fields from the Data Grid, select the desired field header and drag it to the Criteria Builder.
Order of Workbook Tabs
After you create your visualizations (charts, pivot tables, and table views), you can change the order in
which the workbook visualizations are displayed. To change the order, drag the workbook tab to the
desired position.
Share Workbooks and Datasets with All Users in Account
Previously, to share workbooks and datasets, you assigned all of the roles and users that could view the
workbook or dataset.
In 2020.2, you can share workbooks and datasets with everyone in your NetSuite account, allowing all
users to view your datasets and workbooks. In the dataset or workbook that you want to share, click
Share and then check the Share with All box. All users in your account can work with the dataset or
workbook, including any new users or roles that you add to your account.
For more information about sharing workbooks and datasets, see the help topic Accessing and Sharing
Workbooks and Datasets.
Analytics Videos
In the NetSuite 2020.2 release, links to all SuiteAnalytics Workbook videos are available directly from
NetSuite. On the Analytics Home page, click Learn about Analytics in the upper right of the page. When
you click Learn about Analytics, a panel appears that lists all SuiteAnalytics Workbook videos as well as a
description of each video. The Analytics panel is also available when you are working with workbooks and
datasets.
Dataset Builder Field Search Improvements
To improve field discoverability in SuiteAnalytics Workbook, the following changes have been made to the
Dataset Builder search function for 2020.2:
- You can now search for a field using the internal field ID, which is displayed in the Analytics data
source. For example, you can now use the internal field ID destloc to search for the destination
location field.
- When working in a dataset based on the transaction record type, the transaction line, transaction
accounting line, and account record types are now displayed at the top of the Records list. This makes
it more convenient to add fields from some of the most commonly-used transaction-related record
types to your datasets.
To learn more about locating and joining fields to your datasets, see the help topic Locating Fields in
Workbook.
New Built-in Functions for SuiteQL Queries
In 2020.2, you can use new built-in functions when you run SuiteQL queries using the N/query module.
operations in SuiteQL queries. For example, you can use the CONSOLIDATE built-in function to convert a
currency amount stored in a field to a target currency.
Note: Built-in functions are supported only when using SuiteQL with the N/query module in
SuiteScript. Built-in functions are not supported when using SuiteQL with SuiteAnalytics Connect.
The following built-in functions are new in 2020.2:
- BUILTIN.HIERARCHY – Returns the full hierarchical path to a value
- BUILTIN.NAMED_GROUP – Returns filter options for work groups for some record types
(department, class, location, subsidiary, and entity)
- BUILTIN.PERIOD – Returns the contents of the IN predicate as a subselection
- BUILTIN.RELATIVE_RANGES – Returns dynamic calendar ranges for the filter options that apply to
relative date fields (such as Last Fiscal Year, Current Week, and so on)
For more information, see the help topic Using SuiteQL with the N/query Module in SuiteScript.
SuiteQL for REST Web Services is Generally Available
As of 2020.2, SuiteQL query execution through REST web services is generally available. For more
information, see SuiteQL Query Execution Through REST Web Services Is Generally Available.
Changes to Return Values in SuiteAnalytics Connect
Columns
As of 2020.2, SuiteAnalytics Connect changes the length attribute for return values in some columns and
custom fields.
Note: This change applies to the NetSuite.com data source only.
If you work with the NetSuite.com data source and you are using the column attributes in your
configuration, review them and make adjustments as needed. To avoid error or discrepancies, your
configuration must match the column values listed in the Connect Browser.
The following table shows the list of columns with length changes for return values:
Column Name Previous Length Updated Length
Column Name Previous Length Updated Length
The length attribute has also been changed for custom fields that correspond to phone numbers in the
NetSuite UI. The length has changed from 21 to 32 bytes.
These changes are effective as of 2020.2, but the current version of the Connect Browser does not show
the updated values yet. The changes will be available when the 2020.2 Connect Browser is released at a
later date.
For information about the column attributes, see the help topic Table Summary.
Additional Support for Last Modified Date Field
As of the 2020.2 release, the Last Modified Date field is included in 24 record types for SuiteAnalytics
use in workbooks, SuiteQL, and SuiteAnalytics Connect. This field, which has an ID of lastModifiedDate,
contains a time stamp of the record type instance’s latest edit. The field is typically used for querying
objects that have changed since a particular date.
The following table lists the label and ID of the 24 record types:
Label ID
Account account
Accounting Book accountingBook
Accounting Period accountingperiod
Billing Account billingaccount
Charge charge
Charge Type chargetype
Class classification
Competitor competitor
Currency currency
Currency Exchange Rate currencyrate
Department department
Label ID
Employee employee
Custom Recognition Event Type ratableEventType
Incoterm incoterm
Job Status jobstatus
Location location
Payment Method paymentmethod
Price Level pricelevel
Revenue Element revenueElement
Subscription subscription
Subscription Change Order subscriptionchangeorder
Subscription Line subscriptionline
Subsidiary subsidiary
Terms term
As of August 27, 2020, a new restriction is being enforced to prevent
CSV Import
This release note was updated September 9, 2020.
Newly Supported Record Types for CSV Import
Record Type Newly Exposed or Notes
Updated
Group Newly exposed The group record is a way of grouping entities.
Groups can be static or dynamic. You can create and update static
groups using the CSV Import Assistant.
To import group data, in the Import Assistant, set the Import Type to
Relationship, and the Record Type to Groups.
For more information, see the help topic Group Import.
Vendor prepayment Newly exposed Available if the Vendor Prepayments feature is enabled.
For more information, see the help topic Vendor Prepayment Import.
Commerce category Updated As of 2020.2, to support personalized catalog views you can use the
Commerce Category Import option to import a Customer Segment
Assignment for commerce categories.
For more information see the help topics Commerce Category Import
and Commerce Category Customer Segment Assignment.
Translatable Fields on Saved CSV Imports Supported by
SDF
As of 2020.2, SuiteCloud Development Framework (SDF) supports two translatable fields on the custom
object saved CSV import. You can now define the Name and Description fields in SDF as references to
strings of translation collections. For more information, see Additional Translatable Fields Support for
Translation Collection Customizations.
New Sublist Available for Invoice Record
The BillableExpenses sublist is now available when adding or updating Invoice records via CSV import. For
more information, see the help topic Invoice Import.
SuiteFlow (Workflow Manager)
Localization Context Available for Workflows
As of 2020.2, you can define the localization context for workflows. Localization context filtering allows
you to initiate workflows based on the country of the active record.
The localization context filtering feature is designed to be used to filter the records a workflow should
include when it executes. For example, if you select France as the localization context for a workflow, the
workflow only initiates on records that have France set as the localization context value.
Defining the localization context for workflows enables you to create workflow automations designed for
specific countries. You can combine the localization context with other workflow initiation rules, including
context, event type, and condition or formula. You can also filter the records to be used in a workflow by
multiple country values, instead of by a single country value only. Based on the countries that you have
selected, all of the records with the appropriate localization context are available.
- NetSuite automatically determines the localization context for records. For more information about
this determination, see the help topic Localization Context.
- For more information about localization context, see the help topic Using the Context Filtering Tab.
- For more information about record support, see the help topic Records that Support Localization
Context.
Redirect Option Available When Setting Transform Record
Action Parameters
Previously, when you added the Transform Record action to a workflow, the record was created and saved
in the background. As of 2020.2, you have the option to redirect the user to the unsaved transformed
record instead of creating and saving the record in the background. This feature enables you to review
and edit the changes before saving the record, instead of creating the transformed record and saving it
automatically.
To enable the redirect option, check the Redirect Without Saving box on the Workflow Action page.
For more information, see the help topic Transform Record Action.
Enhanced Sublist Support
As of 2020.2, enhanced sublist support has been added to SuiteFlow. This enhancement builds on the
sublist support added in previous releases, and it enables you to further customize workflows based on
the unique needs of your business.
support for custom fields was limited to the Items sublist only. Now, you can use the custom fields on
the Expenses sublist in Sublist Action Groups.
- The Set Field Display Type workflow action is now supported on the Expenses sublist. You can use the
Set Field Display Type workflow action with standard and custom fields on the Expenses sublist.
- The Set Field Display Type workflow action is now supported on standard fields on the Items sublist.
For more information about Sublist Action Groups, see the help topic Using Sublist Action Groups. For
more information about the Set Field Display Type workflow action, see the help topic Set Field Display
Type Action.
SDF Support for Translation of the Set Field Display Label
Workflow Action
As of 2020.2, you can use SuiteCloud Development Framework (SDF) to add translations to all supported
places in workflows.
In 2020.1, SDF was enhanced to support Translation Collections for the following workflow elements:
- Workflow name
- Workflow State names
- Add Button action
- Return User Error action
- Show Message action
SDF now supports Translation Collections for the Set Field Display Label workflow action. When you
include the Set Field Display Label workflow action in your custom objects in SDF, you can now reference
translation strings from Translation Collections. Translation Collections are also supported for workflow
and state fields.
For more information, see Additional Translatable Fields Support for Translation Collection
Customizations. For more information about SDF support for translatable fields for workflow custom
objects, see the help topic Translatable Fields on Custom Objects.
Employee Change Request Approval Template
In 2020.2, a new Employee Change Request Approval template is available in 2020.2. The Employee
Change Request Approval template provides a predefined template of the approval process for employee
change request types. You can use the new template to create your own employee change request types
and to create approval workflows for employee change request types.
Employee change request types provide managers with the types of changes that they can initiate for
their direct reports. For more information about employee change request types, see the help topic
Setting Up Employee Change Request Types.
For more information, see the help topic Creating a Workflow from a Workflow Template.
SuiteScript
Refer to the following sections for details on SuiteScript updates for NetSuite 2020.2:
- Introducing the Workbook API (Beta)
- New N/compress Module
- Records Catalog
- Asynchronous Query and SuiteQL Execution
- Session Preservation for RESTlets and REST Web Services
- New N/recordContext Module
- Phone Number Objects Added to the N/format/i18n Module
- Enhancements to the N/record and N/currentRecord Modules
- New Parameter Added to validateDelete Entry Point
- Change for Scripting with Manufacturing Preferences
- Advance Notice: Upcoming Deprecation of RESTlet Authentication Through User Credentials
- Advance Notice: Upcoming Deprecation of the Reset Button and Related API
- New SuiteScript Actions
- 2020.2 SuiteScript Record Exposures
- 2020.2 SuiteScript Records Browser
Introducing the Workbook API (Beta)
Warning: The Workbook API is a beta feature. The contents of this feature are preliminary and
may be changed or discontinued without prior notice. Any changes may impact the feature’s
operation with the NetSuite application. NetSuite warranties and product service levels shall not
apply to the feature or to the impact of the feature on other portions of the NetSuite application.
for this feature is also considered a beta version and is subject to revision. Please review Beta
Software Legal Notices. ORACLE CONFIDENTIAL. For authorized use only. Do not distribute to third
parties.
In 2020.2, the Workbook API is available as a beta feature. The Workbook API lets you manage your
datasets and workbooks programmatically as part of SuiteAnalytics Workbook. You can do the following:
- Create new datasets to define your data
- Create dataset conditions and joins with other record types
- Create new workbooks
- Define workbook visualizations, such as charts, pivots, and table views
- Run table views and obtain results
- Load existing datasets or workbooks and manage them
To learn about the Workbook API, see the help topic Workbook API (Beta).
To use the Workbook API in this release, you must enable the Workbook API (Beta) feature on the Enable
Features page in your NetSuite account. This feature controls access to all Workbook API components,
including SuiteScript modules and core plug-ins.
and objects you need to create and manage datasets and workbooks. The N/dataset module lets you
define datasets to use for your workbooks. The N/dataset module is similar to the N/query module
but is designed to work alongside the N/workbook module. You should use the N/dataset module
to create all datasets you plan to use in the Workbook API. The N/workbook module lets you create
workbooks, define supporting workbook components, and run table views. For more information, see
New SuiteScript Modules.
- Granular Workbook elements – The N/dataset and N/workbook modules let you work with granular
components that represent different areas in the SuiteAnalytics Workbook UI. For example, when you
use the N/workbook module to create a pivot definition, you can specify pivot-related properties such
as name, pivot axes, and sorting behavior. You can also define limiting filters (which filter results based
on a limiting number) and conditional filters (which filter results based on simple or complex criteria).
For more information, see Granular Workbook Components.
- New core plug-ins – The new Dataset Builder Plug-in and Workbook Builder Plug-in let you
provide custom implementations for creating datasets and workbooks. You can provide your own
implementations with custom logic that meets your business needs. For more information, see New
Core Plug-ins.
New SuiteScript Modules
The Workbook API adds two new modules:
- N/dataset – This module lets you create datasets to use in workbooks. Datasets are the basis for
all workbooks and workbook components. In a dataset, you combine record type fields and criteria
filters to create a query. The results of this query act as the source data for the workbooks you create.
For example, you can use the dataset.create(options) method to create a dataset.Dataset object,
which represents a dataset. You can populate various properties of the dataset, including columns,
conditions, and data type, and you can run the dataset as a paged or non-paged query to obtain the
results.
- N/workbook – This module lets you create new workbooks and load existing workbooks. You can
create and use objects that represent different SuiteAnalytics Workbook areas and functionality.
For example, you can use the workbook.createTableDefinition(options) method to create a
workbook.TableDefinition object, which represents a table view. This object includes a set of columns
(represented by workbook.TableColumn objects), as well as an underlying dataset on which to base
the table view (represented by a dataset.Dataset object).
Some objects are shared between these modules. To use the Workbook API most effectively, you should
load both the N/dataset and N/workbook modules in your scripts.
Granular Workbook Components
The Workbook API lets you create and work with specific workbook components using dedicated
objects in the N/dataset and N/workbook modules. For example, here are some of the objects related to
workbook pivots:
- workbook.PivotDefinition – This object represents a pivot. You can specify basic pivot properties such
as name, pivot axes, and underlying dataset. You can also specify advanced pivot properties such as
sort definitions, expressions, and limiting and conditional filters.
- workbook.PivotAxis – This object represents one axis in a pivot. You can specify the root data for the
pivot, and you can also apply sorting behavior.
- workbook.LimitingFilter – This object represents a limiting filter, which filters results based on a
limiting number (for example, the five largest transaction amounts).
- workbook.ConditionalFilter – This object represents a conditional filter, which filters results based on
simple or complex criteria (for example, all transactions that occurred in the last 30 days).
Similar objects are available for other workbook components, such as charts and table definitions.
New Core Plug-ins
The Workbook API adds two new core plug-ins:
- Dataset Builder Plug-in – This plug-in lets you replace the default implementation for creating a
dataset with another implementation that better suits your business needs. You can override the
createDataset() function and create a dataset that contains a specific subset of data or uses custom
logic. For example, you can use an implementation that creates a dataset based on user- or role-
specific information. The default implementations in the N/dataset module do not permit you to do
this (they are always based on the current role that is executing a script).
- Workbook Builder Plug-in – This plug-in lets you replace the default implementation for creating
a workbook with another implementation that better suits your business needs. You can override
the createWorkbook() function and create a workbook that contains a specific subset of workbook
components or uses custom logic.
New N/compress Module
A new N/compress SuiteScript module is available with NetSuite 2020.2. The N/compress module includes
methods that support compression and decompression of files. It also supports archiving multiple files in
a single file archive, such as .TAR or .ZIP file.
The following methods are included in the N/compress module:
- compress.gzip(options) - Compresses a file and returns it as a temporary file object.
- compress.gunzip(options) – Decompresses a file and returns it as a temporary file object.
- compress.createArchiver() – Creates a compress.Archiver object.
The following methods are called on the compress.Archiver object:
- Archiver.add(options) - Adds a file to be archived.
- Archiver.archive(options) – Creates an archive with the added file and returns it as a temporary file
object.
For more information, see the help topic N/compress Module.
Records Catalog
In the Records Catalog, you can find information about the record types, fields, and relationships
available for a specific NetSuite channel. Similarly to the SuiteScript Records Browser, the Records Catalog
organizes metadata, such as field IDs and script IDs, and supports learning about the NetSuite data
model. However, unlike the SuiteScript Records Browser, the new Records Catalog includes the custom
records, forms, and fields in the current user’s account and only includes data based on the features
currently enabled in the account. In addition, you can access the Records Catalog within your NetSuite
account.
In NetSuite 2020.2, the Records Catalog is introduced with record metadata that is available to the
SuiteScript Analytic API channel. This channel includes data for creating constructed queries and SuiteQL
from the SuiteScript Records Browser for this release, with the exception of the SuiteScript Workbook API
Beta. You can access metadata for the SuiteScript Workbook API using the Analytics Browser.
For more information about using the Records Catalog, see the help topic Records Catalog Overview.
Session Preservation for RESTlets and REST Web Services
In NetSuite 2020.2, interoperability between SuiteScript scripts, RESTlets, and SuiteTalk REST APIs is
improved by allowing authentication for an already established session to be passed using an HTTPS
call. Previously, when an HTTPS call was used from one NetSuite script type to another, users had to
reauthenticate in the second script even though they were still logged in to NetSuite.
The new functionality includes new https.requestRestlet(options) and https.requestSuiteTalkRest(options)
methods, which are available for server scripts only.
New N/recordContext Module
The N/recordContext module is introduced in NetSuite 2020.2. You can use this new method and enum to
determine which country a script is using for execution.
This feature has the following method and enum:
- recordContext.getContext(options) – Returns the record context object for a record.
- recordContext.ContextType – Holds the values for the context type. In this release, the context type
localization is supported.
For more information, see N/recordContext Module.
For more information about record localization context, see the help topic Localization Context.
Phone Number Objects Added to the N/format/i18n
Module
In NetSuite 2020.2, the N/format/i18n module now includes phone number objects. You can also use new
methods to set phone numbers into various international formats.
- format.PhoneNumberFormatter – Represents the object that formats a phone number as a string.
- format.PhoneNumberParser – Represents the object that parses a string as a phone number.
The following methods are called on these objects:
- PhoneNumberFormatter.format(options) – Formats a phone number object as a string.
- PhoneNumberParser.parse(options) – Parses a string as a phone number.
For more information, see N/format/i18n Module.
For more information about this feature in the UI, see Introducing Worldwide Support for Phone Number
Formatting.
Enhancements to the N/record and N/currentRecord
Modules
In NetSuite 2020.2, the following enhancements are added to the N/record and N/currentRecord
modules:
- New record.Column and currentRecord.Column properties:
- Column.isDisabled – Indicates whether the column is disabled.
- Column.isDisplay – Indicates whether the column is displayed.
- Column.isMandatory – Indicates whether the column is mandatory.
- Column.isSortable – Indicates whether the column is sortable.
For more information, see the help topics N/currentRecord Module and N/record Module.
New Parameter Added to validateDelete Entry Point
In NetSuite 2020.2, the parameter scriptContext.lineCount is added to the validateDelete entry point in
clients scripts. By defining this property, you can indicate the lines to be deleted when validateDelete is
triggered by the Clear All Lines button in the UI. For more information, see the help topics validateDelete
and SuiteScript 2.0 Client Script Entry Points and API.
Asynchronous Query and SuiteQL Execution
In NetSuite 2020.2, you can use the N/task module to run constructed queries and SuiteQL queries
asynchronously. A constructed query is a query that you build using the methods and objects in the N/
query module. The N/query module also provides methods (such as query.runSuiteQL(options)) to run
SuiteQL queries. By default, constructed queries and SuiteQL queries run synchronously. Now, you can
create tasks for these queries using the N/task module and submit them for asynchronous processing.
The task.create(options) method now accepts new enum values from the task.TaskType enum:
task.TaskType.QUERY for a constructed query or task.TaskType.SUITE_QL for a SuiteQL query.
The task.create(options) method returns a task.QueryTask object for a constructed query or a
task.SuiteQLTask object for a SuiteQL query. You can also call task.checkStatus(options) to check the
current status of a submitted constructed query or SuiteQL query task.
For more information, see the help topic N/task Module.
Change for Scripting with Manufacturing Preferences
As of 2020.2, most manufacturing preferences available on the Order Management subtab of the
Accounting Preferences page are being moved or copied to a new Manufacturing Preferences page. For
details of which preferences are being moved and which are being copied to the new page, see the help
topic Manufacturing Preferences Overview.
As part of this change, moved manufacturing preferences are no longer scriptable
with the SuiteScript 1.0 nlapiLoadConfiguration(type) function. Instead, the
SuiteScript 1.0 nlapiGetContext().getPreference(preference_ID) or the SuiteScript 2.0
runtime.User.getPreference(options) method can be used to access these read-only preferences.
Before your account is upgraded to 2020.2, review your scripts to find any that use the SuiteScript 1.0
nlapiLoadConfiguration(type) function to access moved manufacturing preferences. To ensure these
scripts continue to function after your account is upgraded, you should update these scripts to use the
SuiteScript 2.0 runtime.User.getPreference(options) method instead.
So instead of nlapiGetContext().getPreference(<preference_ID>), use require([‘N/
runtime’],function(runtime){runtime.getCurrentUser().getPreference(<preference_ID>)});
Advance Notice: Upcoming Deprecation of the Reset
As of NetSuite 2021.1, the Reset button on forms and the related SuiteScript 1.0 and 2.0 API will no longer
be supported. Both standard and custom Reset buttons will be removed from all forms. The SuiteScript
APIs Form.addResetButton(options) and nlobjForm.addResetButton(label) for adding custom reset
button will no longer be supported in beforeLoad User Event scripts.
Advance Notice: Upcoming Deprecation of RESTlet
Authentication Through User Credentials
As of NetSuite 2021.1, user credentials authentication for newly created RESTlets will not be supported.
Any RESTlets created after January 1, 2021 with user credentials authentication will stop working after
the account is upgraded to 2021.1.
This change is effective as of January 1, 2021, but goes into effect when your account is upgraded
to 2021.1. If you attempt to use user credentials to authenticate a new RESTlet after your account is
upgraded, an HTTP error response will be returned. This change will not affect RESTlets created before
January 1, 2021, except for RESTlets included in bundles or SuiteApps that are installed into target
accounts as of January 1, 2021 or later.
You must ensure that RESTlet integrations created as of January 1, 2021 or later use an alternative
authentication method, such as token-based authentication (TBA) or OAuth 2.0.
You also must ensure that RESTlets included in bundles or SuiteApps use TBA or OAuth 2.0 for
authentication. This change applies to all RESTlets included in bundles or SuiteApps, not only to RESTlets
created as of January 1, 2021 or later. The installation of bundles or SuiteApps changes the creation date
of script records. For this reason, you must ensure that all RESTlets in a bundle or SuiteApp are updated
to use TBA or OAuth 2.0.
For information about setting up TBA for RESTlets, see the help topic Setting up Token-based
Authentication for a RESTlet integration.
For information about using OAuth 2.0 for RESTlets, see the help topic Using OAuth 2.0 for RESTlet
Authentication.
New SuiteScript Actions
Invoice markforgrouping Mark for Grouping Makes an invoice eligible for grouping
Invoice ungroupinvoice Remove From Removes an invoice from an existing invoice
Grouping group
Invoice unmarkforgrouping Unmark for Makes an invoice not eligible for grouping
Grouping
Invoice Group groupinvoices Group Invoices Groups invoices into groups based on the
customer name and common criteria
Invoice Group unlinkinvoices Unlink Invoices Removes invoices from an invoice group
Supply Change approve Approve all pending Approves the supply change order with the given
Order recordId
Supply Change reject Reject all pending Rejects the supply change order with the given
Order recordId
Supply Plan launch Launch Launches the supply planning engine
Definition
2020.2 SuiteScript Record Exposures
Record Type Newly Exposed Notes
or Updated
Commerce Updated As of NetSuite 2020.2, the customer segment assignment sublist is
Category available on commerce category records. This sublist includes the
customersegment and customersegmentsize fields. Note that you cannot
create, edit, or delete commerce category sublists using SuiteScript.
Goal Newly exposed The goal record is available when the Performance Management feature is
enabled.
The goal record is scriptable in both server and client SuiteScript.
Performance Metric Newly exposed The performance metric record is available when the Performance
Management feature is enabled.
The performance metric record is scriptable in both server and client
SuiteScript.
Performance Newly exposed The performance review record is available when the Performance
Review Management feature is enabled.
The performance review record is scriptable in both server and client
SuiteScript.
This record can be created, edited, deleted, and searched.
Performance Newly exposed The performance review schedule record is available when the
Review Schedule Performance Management feature is enabled.
The performance review schedule record is scriptable in both server and
client SuiteScript.
Planned Order Newly exposed The planned order record is available when the Material Requirements
Planning feature is enabled.
The planned order record is scriptable in both server and client SuiteScript.
The planned order record cannot be copied or transformed.
Planning Item Newly exposed The planning item category record is available when the Material
Category Requirements Planning feature is enabled.
The planning item category record is scriptable in both server and client
SuiteScript.
Record Type Newly Exposed Notes
or Updated
The planning item category record cannot be transformed.
Planning Item Newly exposed The planning item group record is available when the Material
Group Requirements Planning feature is enabled.
The planning item group record is scriptable in both server and client
SuiteScript.
The planning item group record cannot be transformed.
Planning Rule Newly exposed The planning rule group record is available when the Material
Group Requirements Planning feature is enabled.
The planning rule group record is scriptable in both server and client
SuiteScript.
The planning rule group record cannot be transformed.
Supply Change Newly exposed The supply change order record is available when the Material
Order Requirements Planning feature is enabled.
The supply change order record is scriptable in both server and client
SuiteScript.
The supply change order record cannot be created, copied, or transformed.
Supply Plan Newly exposed The supply plan definition record is available when the Material
Definition Requirements Planning feature is enabled.
The supply plan definition record is scriptable in both server and client
SuiteScript.
The supply plan definition record cannot be transformed.
2020.2 SuiteScript Records Browser
The 2020.2 SuiteScript Records Browser is not yet available.
SuiteTalk Web Services Integration
- Fully Supported Record Types for REST Web Services in 2020.2
- REST Web Services Support for CRUD Operations on Basic, Journal, and Header Only Custom
Transactions and on Custom Lists
- Pricing Sublist on Item Records Available Through REST Web Services (Beta)
- Improved Error Handling in REST Web Services
- REST Query Service
- SuiteQL Query Execution Through REST Web Services Is Generally Available
- Support for Dataset Execution Through REST Web Services (Beta)
- Support for Getting a List of Datasets Through REST Web Services (Beta)
- SOAP Web Services
- Deprecation of SOAP Web Services Authentication Through User Credentials
- Integration Records Supported by SDF
- New Transformation Pairs and Generic Transaction Link Available for Sales and Purchase Custom
Transaction Types
- New Field Available for Currency Rate Record
- New Type Added to the GetCustomizationId Operation
- InventoryDetail Subrecord Available for Inbound Shipment Record
- SOAP Web Services Version 2020.2
- Araxis Merge Diff File for the 2020.2 Endpoint
- 2020.2 SOAP Schema Browser
Fully Supported Record Types for REST Web Services in
2020.2
The following table lists the record types that are fully supported as of 2020.2.
Record Type Notes
Charge The charge record is not a subrecord and has no subrecords.
The record ID for a charge REST record is charge.
The charge record is available if SuiteBilling features are enabled. For more information, see the
help topic Enabling SuiteBilling Features.
Contact The contact record is not a subrecord and has no subrecords.
The record ID for a contact REST record is contact.
Contact Category The contact category record is not a subrecord and has no subrecords.
The record ID for a contact category REST record is contactcategory.
All elements on this record are accessible through REST web services.
Contact Role The contact role record is not a subrecord and has no subrecords.
The record ID for a contact role REST record is contactrole.
All elements on this record are accessible through REST web services.
Email Template The email template record is not a subrecord.
The record ID for the email template REST record is emailtemplate.
The record ID for the email template REST subrecord is CrmTemplateCategorySubsidiary.
You must enable the CRM feature before you can use this record through REST web services.
Usage The usage record is not a subrecord and has no subrecords.
The record ID for a usage REST record is usage.
The usage record is available if SuiteBilling features are enabled. For more information, see the
help topic Enabling SuiteBilling Features.
For a list of every fully supported record, see the help topic REST Web Services Supported Records.
Except for fully supported records, all records listed in the REST API Browser are available as beta records
in REST web services. For more information about working with the browser, see the help topic The REST
API Browser.
REST Web Services Support for CRUD Operations on Basic,
Journal, and Header Only Custom Transactions and on
Custom Lists
As of 2020.2, you can use all CRUD (create, read, update, and delete) operations on custom list records
and on basic, journal, and header only custom transactions. Sales and purchase custom transactions are
not supported.
You can use CRUD operations to perform business processing on custom lists and custom transactions.
about working with custom transactions in the UI, see the help topic Custom Transactions.
For information about using CRUD operations, see the sections under Working with Records.
Pricing Sublist on Item Records Available Through REST
Web Services (Beta)
Warning: Pricing sublist support on item records is a beta feature. The contents of this feature
are preliminary and may be changed or discontinued without prior notice. Any changes may
impact the feature’s operation with the NetSuite application. NetSuite warranties and product
service levels shall not apply to the feature or to the impact of the feature on other portions of the
NetSuite application. NetSuite may review and monitor the performance and use of this feature.
The documentation for this feature is also considered a beta version and is subject to revision.
Please review Beta Software Legal Notices. ORACLE CONFIDENTIAL. For authorized use only. Do
not distribute to third parties.
As of 2020.2, you can create, update, and access pricing sublist (pricing matrix) data on item records
through REST web services.
The pricing sublist is supported when the following features are enabled:
- Multiple Currencies
- Multiple Prices
- Quantity Pricing
For each item, you can set multiple prices based on the following:
- Currency used for item prices. See the help topic Enabling the Multiple Currencies Feature.
- Price levels available for the item, as defined in the price level user-defined list. See the help topic
Using Multiple Pricing.
- The quantity of items being sold, when the Quantity Pricing feature is enabled. See the help topic
Using Quantity Pricing.
- Item Pricing
- Setting Up Item Pricing
- Using Item Records
In REST web services, you can create or update price values on a per-row, per-column basis by using
the POST operation. You can access the price values on a per-row, per-column basis by using the GET
operation.
To create or update a pricing sublist, you send a POST request similar to the following and specify the
pricing sublist data in the request body in an array of items:
POST https://demo123.suitetalk.api.netsuite.com/services/rest/record/v1/inventoryitem
“price”: {
“items”: [
{
“currencyPage” : { “id” : “1” },
“priceLevel” : { “id” : “1” },
“quantity” : { “value” : 5 },
“price”: 25.5
},
…
]
}
To access a pricing sublist, you send a GET request similar to the following:
For more information, see the help topic Working with the Pricing Sublist on Item Records (Beta).
Improved Error Handling in REST Web Services
As of 2020.2, error messages in REST web services contain more detailed information about error details,
error codes, and error paths.
The updated error messages provide information about the location of the error. The error messages
clarify whether an error occurred in the request URL, the request headers, the query parameters, or the
request body.
The updated and unified error messages also provide more information about the cause of errors and
provide possible solutions.
For more information, see the help topic Error Handling in REST Web Services.
SuiteQL Query Execution Through REST Web Services Is
Generally Available
As of 2020.2, SuiteQL query execution through REST web services is generally available.
SuiteQL is a query language based on the SQL database query language. SuiteQL provides advanced
query capabilities that can be used to access NetSuite records.
To execute SuiteQL queries through REST web services, send a POST request to the suiteql resource,
and specify the query in the request body after the query parameter q. The following example shows a
SuiteQL query executed through REST web services using the Prefer HTTP request header:
POST https://demo123.suitetalk.api.netsuite.com/services/rest/query/v1/suiteql
Prefer: transient {
“q”: “SELECT email, COUNT(*) as count FROM transaction GROUP BY email”
}
For more information about SuiteQL in general, see the help topic SuiteQL.
The Analytics Browser provides information about all record types and fields that are available through
the analytics data source. For information, see the help topic Analytics Browser.
For more information about executing SuiteQL queries through REST web services, see the help topic
Executing SuiteQL Queries Through REST Web Services.
Support for Dataset Execution Through REST Web Services
(Beta)
Warning: Dataset execution through REST web services is a beta feature. The contents of this
feature are preliminary and may be changed or discontinued without prior notice. Any changes
may impact the feature’s operation with the NetSuite application. NetSuite warranties and product
service levels shall not apply to the feature or to the impact of the feature on other portions of the
NetSuite application. NetSuite may review and monitor the performance and use of this feature.
The documentation for this feature is also considered a beta version and is subject to revision.
Please review Beta Software Legal Notices. ORACLE CONFIDENTIAL. For authorized use only. Do
not distribute to third parties.
Prior to 2020.1, you defined, visualized, and analyzed SuiteAnalytics Workbook source data in a single
workbook object.
As of 2020.1, workbooks and datasets exist as separate objects, each with their own respective owners
and accessibility rights. In a dataset, you define your workbook source data by selecting record types,
fields, and criteria for further analysis in a workbook.
As of 2020.2, REST web services support the execution of datasets. Dataset execution replaces the
previously available workbook execution function. In REST web services, you can execute saved datasets.
You can execute both standard and custom datasets by using the dataset ID in your GET request.
To execute a dataset, you send a GET request similar to the following:
Datasets must be created in the SuiteAnalytics Workbook UI and cannot be created through REST web
services. For information about creating datasets, see the help topic Defining a Dataset.
For more information, see the help topic Working with SuiteAnalytics Datasets in REST Web Services
(Beta).
Support for Getting a List of Datasets Through REST Web
Services (Beta)
Warning: Getting a list of datasets through REST web services is a beta feature. The contents
of this feature are preliminary and may be changed or discontinued without prior notice. Any
changes may impact the feature’s operation with the NetSuite application. NetSuite warranties
and product service levels shall not apply to the feature or to the impact of the feature on other
portions of the NetSuite application. NetSuite may review and monitor the performance and use
of this feature. The documentation for this feature is also considered a beta version and is subject
to revision. Please review Beta Software Legal Notices. ORACLE CONFIDENTIAL. For authorized use
only. Do not distribute to third parties.
In SuiteAnalytics Workbook, you analyze your company data using two distinct objects: a dataset and a
workbook.
Datasets are the basis for all workbooks and workbook components in your account. In a dataset, you
combine record type fields and criteria filters to create a query. The results of this query act as the source
data for your workbooks.
As of 2020.2, you can list all existing SuiteAnalytics Workbook datasets through REST web services.
Datasets must be created in the SuiteAnalytics Workbook UI and cannot be created through REST web
services. For information about creating datasets, see the help topic Defining a Dataset.
To list all existing datasets, you send a GET request similar to the following:
The result contains the name, ID, and description of the datasets, and it provides information about the
record type the dataset works on.
You cannot use collection paging when you list all datasets. A request for a list of datasets returns all
datasets on a single page.
For more information, see the help topic Working with SuiteAnalytics Datasets in REST Web Services
(Beta).
Deprecation of SOAP Web Services Authentication Through
User Credentials
As of the 2020.2 SOAP web services endpoint, authentication through request-level credentials is not
supported. The Passport complex type is not supported. If you attempt to authenticate through request-
level credentials in SOAP web services 2020.2 and later endpoints, the web services request is not
processed, and an error message is returned.
This change does not affect web services integrations that use 2020.1 and earlier endpoints. You can
continue to use request-level credentials in endpoints 2020.1 and earlier. However, you are encouraged
to use token-based authentication (TBA) for all of your integrations. TBA is available in all supported
endpoints. If you are using an earlier endpoint that does not support TBA, you are advised to upgrade to
one of the supported endpoints. For information about supported endpoints, see the help topic Support
for Existing WSDL Versions.
You must ensure that SOAP web services integrations created with 2020.2 and later SOAP web services
endpoints use TBA. Authentication through user credentials continues to be supported in integrations
that use SOAP web services 2020.1 and earlier endpoints. For more information, see the help topic Token-
based Authentication and Web Services.
Integration Records Supported by SDF
As of 2020.2, SuiteCloud Development Framework (SDF) supports referencing integration records from an
SDF project. For more information, see Integration Record Support.
New Transformation Pairs and Generic Transaction Link
Available for Sales and Purchase Custom Transaction Types
As of 2020.2, new transaction transformation pairs are available for the custom sales and custom
purchase record types.
- Custom Sale to Invoice
- Custom Sale to Cash Refund
- Custom Sale to Credit Memo
- Custom Sale to Cash Sale
- Cash Sale to Custom Sale
- Return Authorization to Custom Sale
- Custom Purchase to Vendor Credit
- Custom Purchase to Vendor Payment
- Custom Purchase to Vendor Bill
- Vendor Bill to Custom Purchase
- Vendor Return Authorization to Custom Purchase
- Purchase Order to Custom Purchase
For more information, see the help topic Sales and Purchase Custom Transaction Types.
In addition to the new transformation pairs, the source and transformed transactions are linked together
with a generic transaction link.
For more information about transaction links, see the help topic Using Transaction Links.
New Field Available for Currency Rate Record
The currencyRateType field is now available in SOAP WebServices for the currencyRate record. This is a
required field when the Currency Exchange Rate Types feature is enabled. For more information, see the
help topic Currency Rate.
New Type Added to the GetCustomizationId Operation
The new type customRecordCustomField has been added to the getCustomizationID operation. This way
you can find the internal ID of a custom field in a custom record more easily. For more information, see
the help topic getCustomizationId.
InventoryDetail Subrecord Available for Inbound Shipment
Record
The inventoryDetail subrecord is now available when working with Inbound Shipment records in SOAP
web services.
Note: Subrecords are not supported in the searchBasic operation. The information from the
subrecord will be missing in the SOAP web services response, but the operation will not be
terminated by unexpected error. If you need to search for the inventoryDetail subrecord, you must
use the inboundShipmentSearchBasic operation.
SOAP Web Services Version 2020.2
SOAP web services version 2020.2 is available. When your implementation is upgraded to 2020.2, the
2020.2 WSDL becomes available in your production account.
You do not need to upgrade your WSDL when the new version is generally available. NetSuite supports
each endpoint for three years. For information about the supported generally available versions, see the
help topic Support for Existing WSDL Versions.
Araxis Merge Diff File for the 2020.2 Endpoint
The Araxis Merge diff file highlights the schema changes between the 2020.1 and 2020.2 endpoints. The
Araxis Merge diff file is not yet available, but this section provides details about the types of information it
will include.
- About the Araxis Merge Diff File
- Using the Araxis Merge Diff File
About the Araxis Merge Diff File
NetSuite publishes an Araxis Merge diff file for every new endpoint. Depending on the scope of the
release, changes described in the Araxis Merge diff file may include:
- New record types
- Elements (fields) that have been added, removed, or changed
- New sublists (lists)
- New joins
- New search filters and search return columns
- New platform operations
Using the Araxis Merge Diff File
Important: The screenshots in this section are for illustrative purposes only. They do not reflect
changes related to any specific endpoint.
The Araxis Merge diff file is generated using Araxis Merge. When you click the Araxis Merge diff file link
(when it is available), a page appears that offers an overview of all schema changes.
The following screenshot shows how this summary page looks. In this example, the highlighted rows
indicate that an XSD has been modified. The integers at the center indicate the number of changed lines
in the file. To see the exact differences, click the report link in the column on the right, or click the name of
the file in either column.
When you click any of these links, the Araxis Merge diff file shows a page with two columns. The previous
version of the file is displayed on the left, and the new version is displayed on the right. Changed
elements are highlighted.
For example, the following screenshot shows an excerpt from the report on platform.commonTypes.xsd.
Notice the addition of two values to the PermissionCode enumeration: _accessPaymentAuditLog and
_advancedPDFHTMLTemplates.
The Araxis Merge diff file also shows changes to data types. The following screenshot is a snapshot of
transactions.sales.xsd. Notice that the chargeType element changed from an enumeration to a RecordRef.
2020.2 SOAP Schema Browser
The 2020.2 SOAP Schema Browser is not yet available.
SuiteCloud SDK
Development Framework (SDF) projects. These tools are the SuiteCloud IDE plug-ins and command-line
interfaces (SuiteCloud CLI).
This release note was updated August 26, 2020.
Generally, plug-in behavior changes in 2020.2 are designed to support SDF. In addition, SuiteCloud IDE
plug-ins for versions 2017.1 and later have compatibility requirements. The version of your plug-in must
match the version of your NetSuite account before you can use the plug-in to create SDF projects.
For information about additional features that impact SuiteCloud IDE plug-ins and SuiteCloud CLI, see the
release note for SuiteCloud Development Framework.
2020.2 SuiteCloud CLI for Node.js Is Now Available
SuiteCloud CLI for Node.js is now available for download. To install it, see the help topic Installing CLI for
Node.js.
preferred code editor, to develop SDF projects. This CLI is optimized for the end-user experience. It is
interactive and guides you through all the steps of the communication between your local project and
your account. For more information about CLI for Node.js, see the help topic CLI for Node.js Guide.
SuiteCloud CLI for Node.js is an open-source project published in npm. To get the latest changes, see
SuiteCloud CLI for Node.js.
2020.2 SuiteCloud CLI for Java Is Now Available
SuiteCloud CLI for Java is now available for download. To install it, see the help topic Installing CLI for Java.
code editor, to develop SDF projects. You can also create batch and shell scripts that use CLI commands
to automate your project validation and deployment processes. When used with your own IDE, CLI for
Java acts as an alternative to SuiteCloud IDE plug-ins. For more information about CLI for Java, see the
help topic CLI for Java Guide.
CLI for Java is supported on Windows, Linux, and Mac OS X. For more information, see the help topic CLI
for Java Installation Prerequisites.
2020.2 SuiteCloud IDE Plug-in for WebStorm Is Now
Available
SuiteCloud IDE plug-in for WebStorm is now available for download. For more information, see the help
topic Update SuiteCloud IDE Plug-in for WebStorm.
Important: When your account is upgraded to 2020.2, your IDE plug-in for WebStorm is not
updated automatically to the 2020.2 version. After your account upgrade, you must manually
update the IDE plug-in for WebStorm.
2020.2 SuiteCloud IDE Plug-in for Eclipse Is Now Available
SuiteCloud IDE plug–in for Eclipse is now available for download. For more information, see the help topic
Updating Eclipse for Use with SuiteCloud IDE Plug-in.
Important: When your account is upgraded to 2020.2, your IDE plug-in for Eclipse is not
updated automatically to the 2020.2 version. After your account upgrade, you must manually
update the IDE plug-in for Eclipse.
New Templates for Installation Preferences Files in
SuiteCloud IDE Plug-ins
Every time you create a SuiteApp project, it includes a locking.xml and a hiding.xml file inside the
InstallationPreferences folder. These files are templates and include comments that you can use as
examples to apply installation preferences in your SuiteApp project.
For existing SuiteApp projects, when you create an installation preference file in the project, the file uses
the new template.
For more information about how to create an installation preference file in SuiteCloud IDE plug-in, see
one of the following topics:
- Setting Installation Preferences in SuiteCloud IDE Plug-in for WebStorm
- Setting Installation Preferences in a SuiteApp Project in SuiteCloud IDE Plug-in for Eclipse
The locking.xml file template is as follows:
The hiding.xml file template is as follows:
For more information about installation preferences, see the following topics:
- SuiteCloud Development Framework Project Components
- Installation Preferences in a SuiteApp Project
- Locking Custom Objects in an SDF SuiteApp Project
- Hiding Files in an SDF SuiteApp Project
- Locking Files in an SDF SuiteApp Project
## Removed Commands in SuiteCloud CLI for Java
The following commands have been removed from CLI for Java:
- savetoken
- issuetoken
- revoketoken
You need to use the authenticate command to authenticate your accounts in SuiteCloud CLI for Java. For
more information, see SuiteCloud CLI for Java New Authentication Method.
## SuiteCloud CLI for Java New Authentication Method
Important: Browser-based authentication is not compatible with Windows Subsystem for
Linux.
You must use token-based authentication (TBA), through the authenticate command, to authenticate
your accounts in SuiteCloud CLI for Java. You can either enter a previously issued NetSuite TBA token
with the savetoken option, or use browser-based authentication. For example, to use browser-based
authentication, run the following command in an SDF project: sdfcli authenticate —authid myDevRole.
For more information, see the help topic authenticate.
Note: An authentication ID (authID) is a custom alias you give to a specific account-role
combination. You can use authIDs to identify roles using the authid option to interact with
commands such as deploy or importfiles in CLI for Java.
To revoke TBA tokens in CLI for Java, you must use the revoke option in the manageauth command.
For more information, see the help topic manageauth.
## SuiteCloud CLI for Java New Command
The package command is available in CLI for Java. This command generates a ZIP file from your project.
For more information, see the help topic package.
## SuiteCloud CLI for Node.js New Commands
The following two new commands are available for CLI for Node.js:
- account:ci — This non-interactive command sets up an account to use with your projects.
For more information, see the help topic account:ci.
- account:manageauth — This command manages authentication IDs (authIDs) for all your projects. You
can list the authentication IDs available in your local machine, edit them, and remove them.
For more information, see the help topic account:manageauth.
- file:upload— This command uploads files from your project to NetSuite.
For more information, see the help topic file:upload.
- project:package — This commands generates a ZIP file from your project, respecting the structure
specified in the deploy.xml file, and applying local validation.
For more information, see the help topic project:package.
In addition to these two commands, the log option has been added to the project:deploy and
project:validate commands. This option sets the log file location. For more information, see the help
topics project:deploy and project:validate.
The excludefiles option has been added to the object:import command. For more information, see the
help topic object:import.
## SuiteCloud IDE Plug-in for WebStorm Multiple Projects
You can attach multiple SDF projects in a WebStorm window. You can trigger SuiteCloud IDE plug-in for
WebStorm actions through the user interface and through keyboard shortcuts.
If you use shortcuts, the action is applied to the active project in the WebStorm project tree.
For more information, see the help topic Working with SDF Projects in SuiteCloud IDE Plug-in for
WebStorm.
SuiteCloud IDE Plug-in for WebStorm New General
## Settings
You can customize the configuration for SDF projects. The settings you configure are applied to all SDF
projects you work on in SuiteCloud IDE plug-in for WebStorm. The following settings are available:
- Automatic add dependencies
- Skip warnings when deploying to production
- Skip warnings when overwriting custom objects
- Skip warnings when overwriting files
The new general settings window is under File > Settings > Tools > NetSuite.
Note: You can also access it by right-clicking the project folder and selecting NetSuite > NetSuite
Settings.
For more information, see the help topic Customizing SDF Project Configuration in SuiteCloud IDE plug-in
for WebStorm.
## SuiteCloud IDE Plug-in for WebStorm New Project Settings
Important: When upgrading SuiteCloud IDE plug-in for WebStorm to 2020.2, the
authentication IDs you previously stored are deleted. You need to issue a new TBA token and save
it in the plug-in. For more information about how to issue TBA tokens in NetSuite, see the help
topic User Access Token – Create a TBA Token.
## There is a new project settings window in SuiteCloud IDE plug-in for WebStorm. You can set default
configurations for a project. By doing so, this setup is applied every time you perform a validation action,
such as validating or deploying your project.
To access the new project settings window, go to File > Settings > Tools > NetSuite > Project Settings.
For more information, see the help topic Changing Project Settings in SuiteCloud IDE Plug-in for
WebStorm.
SuiteCloud IDE Plug-in for WebStorm New Account
## Settings
Important: When upgrading SuiteCloud IDE plug-in for WebStorm to 2020.2, the
authentication IDs you previously stored are deleted. You need to issue a new TBA token and save
it in the plug-in. For more information about how to issue TBA tokens in NetSuite, see the help
topic User Access Token – Create a TBA Token.
In previous releases, to use an account in SuiteCloud IDE plug-in for WebStorm, you needed to add your
account domain and then, configure the roles in that account that you wanted to use.
As of 2020.2, to use an account in SuiteCloud IDE plug-in for WebStorm, you only need to add your
account. Furthermore, the master password option has been removed because the projects are securely
authenticated through your account.
To access the new accounts window, go to File > Settings > Tools > NetSuite > Accounts.
For more information, see the help topic SuiteCloud IDE Plug-in for WebStorm Account Setup.
SuiteCloud IDE Plug-in for WebStorm New Project
## Structure
As of 2020.2, projects created in SuiteCloud IDE plug-in for WebStorm have the same structure as
projects created in SuiteCloud CLI for Node.js. With this update, you can create and interact with the same
project with either of the tools.
Note: Existing projects are compatible with SuiteCloud IDE plug-in for WebStorm 2020.2.
The updated structure is as follows:
- Account customization projects
myACP
> src
> AccountConfiguration
> FileCabinet
> SuiteScripts
> Templates
> Web Site Hosting Files
> Objects
> Translations
deploy.xml
manifest.xml
suitecloud.config.js
For more information, see the help topic Account Customization Projects.
- SuiteApp projects
com.mycompany.mysuiteapp
> src
> FileCabinet
> SuiteApps
> com.mycompany.mysuiteapp
> Web Site Hosting Files
> InstallationPreferences
> Objects
> Translations
deploy.xml
manifest.xml
suitecloud.config.js
For more information, see the help topic SuiteApp Projects.
2020.2 Custom SDF Objects Not Fully Supported in
## SuiteCloud IDE Plug-in for Eclipse
You cannot use the Create Object in Account or the Edit in Account options in SuiteCloud IDE plug-in for
## Eclipse for the following SDF custom objects:
- Workbook (workbook) — For more information about this SDF custom object, see the help topic
Custom Workbook Objects.
- Dataset (dataset) — For more information about this SDF custom object, see the help topic Custom
Dataset Objects.
- Published Dashboard (publisheddashboard) — For more information about this SDF custom object,
see the help topic Published Dashboards as XML Definitions.
You must create these objects in NetSuite and then, import them back to your SDF project.
Note: You can create Published Dashboards through the NetSuite context menu. For more
information, see the help topic Creating an XML Definition in SuiteCloud IDE Plug-in for Eclipse.
For more information about the fully supported SDF custom objects, see the help topic Customizations
Supported by SuiteCloud Development Framework.
## SuiteCloud Development Framework
SuiteCloud Development Framework (SDF) is a development framework and deployment mechanism.
## Customers and partners can use SDF to create customization projects for internal use within their
organizations or for commercial distribution. For more information about SDF, see the help topic
SuiteCloud Development Framework Overview.
For a complete list of custom records and customizations that are supported by SDF, see the help topic
Customizations Supported by SuiteCloud Development Framework.
With the release of SuiteCloud Development Framework, the SuiteCloud Terms of Service were updated
in September 2016 to specifically include SuiteCloud Development Framework as one of the listed
SuiteCloud Technologies and to make other clarifying changes. You can review the complete updated
terms at http://www.netsuite.com/termsofservice.
Note: For current NetSuite 2020.2 limitations when developing SDF custom objects with
SuiteCloud IDE, see 2020.2 Custom SDF Objects Not Fully Supported in SuiteCloud IDE Plug-in for
Eclipse.
## Filter Workflow Executions by Localization Context Support
## SuiteCloud Development Framework (SDF) supports localization context filtering for workflows. You
can use the localization record context feature to filter the records a workflow should include when it
executes. A record’s localization context represents the country or countries associated with that record.
You can configure localization context filtering in workflow custom objects by using the
initlocalizationcontext field, which specifies the localization context of the records associated with the
workflow.
If a workflow has localization context filtering set up in custom objects in an SDF project, that filtering
works in all target accounts where the SDF project is deployed. The context filtering also works in
accounts when an SDF SuiteApp is installed from the SuiteApp Marketplace.
For more information about workflow execution filtering by localization context, see Localization Context
Available for Workflows.
Additional Translatable Fields Support for Translation
## Collection Customizations
SuiteCloud Development Framework (SDF) now supports more translatable fields on the following custom
objects:
- center
- centercategory
- centertab
- customlist
- customrecordtype
- customtransactiontype
- savedcsvimport
- suitelet
- translationcollection
- workflow
When creating SDF custom objects, you can reference strings that are located in a Translation Collection.
After the SDF project is deployed to an account, the NetSuite UI displays the translated strings for the
fields in the account language. If a field has no translation in the account language, the NetSuite UI
displays the default translation.
For the list of supported translatable fields, see the help topic Translatable Fields Supported in Custom
Objects.
## Additional Transaction Form Fields Support
SuiteCloud Development Framework (SDF) now supports the following transaction form fields in
transactionForm custom objects:
- Email Message Template – Defined by the emailMessageTemplate element in the XML definition, and
specifies which transaction email template to use for the transaction type when sending transaction
emails with a PDF attachment.
- Linked Forms – Defined by the linkedForms element in the XML definition, and specifies the chain of
transaction forms that are used when the user converts one transaction into another. Each transaction
form in the chain is defined by the linkedForm field group that specifies the following fields:
- type – Specifies the transaction type for the linked form.
- form – Specifies the form name, which can be either a standard transaction form or a reference to
the script ID of a custom transaction form.
- Never Empty – Defined by the neverEmpty element in the XML definition, and specifies that the user
must enter at least one row for the sublist when neverEmpty is set to T (true).
- Roles – Defined by the roles element in the XML definition, and specifies the custom transaction form
as the preferred form for specific roles. Each role field group is defined by the following fields:
- id – Specifies the name of a standard role or the script ID of a custom role.
- preferred – Specifies whether the role is the preferred role.
- Space Before – Defined by the spaceBefore element in the XML definition, and specifies whether
to include blank lines before a field when spaceBefore is set to an integer number that specifies the
number of spaces.
- Total Box – Defined by the totalBox element in the XML definition, and specifies the fields that you
want to show in the form totals.
For examples of those fields in SDF, see the help topic Custom Transaction Form Field Examples.
## Additional Portlets Support
The publisheddashboard custom object in SuiteCloud Development Framework (SDF) now supports the
following portlets:
- Analytics Portlets — Analytics portlets in SDF are represented with the analytics element. You can
specify this element in a dashboard of a publisheddashboard custom object.
Note: The Analytics portlet only exports values from custom workbooks. It does not export
values from standard workbooks.
For more information about Analytics portlets, see the following help topics:
- Workbook-based Portlets
- Workbooks Overview
- analytics
- Event Scheduler Portlets — Event Scheduler portlets in SDF are represented with the scheduler
element. You can specify this element in a dashboard of a publisheddashboard custom object.
For more information about Event Scheduler portlets, see the following help topics:
- Using the Event Scheduler Portlet
- scheduler
- Key Performance Indicator (KPI) Scorecard Portlets — KPI Scorecard portlets in SDF are
represented with the kpireport element. You can specify this element in a dashboard of a
publisheddashboard custom object.
For more information about KPI Scorecard portlets, see the following help topics:
- KPI Scorecards Overview
- KPI Scorecard Portlet
- kpireport
- Links Portlets — Links portlets in SDF are represented with the tasklinks element. You can specify
this element in a dashboard of a publisheddashboard custom object. The Links portlet supports the
following portlets:
- Reports Links portlets
- Activities Links portlets
For more information about Links portlets, see the following help topics:
- The Reports Page
- The Activities Page
- tasklinks
- Recent Records Portlets — Recent Records portlets in SDF are represented with the recentrecords
element. You can specify this element in a dashboard of a publisheddashboard custom object.
For more information about Recent Records portlets, see the following help topics:
- Reviewing Recent Records
- Using the Recent Records Menu
- recentrecords
- Recent Reports Portlets — Recent Reports portlets in SDF are represented with the recentreports
element. You can specify this element in a dashboard of a publisheddashboard custom object.
For more information about Recent Reports portlets, see the following help topics:
- The Reports Page
- recentreports
- Settings Portlets — Settings portlets in SDF are represented with the settings element. You can
specify this element in a dashboard of a publisheddashboard custom object.
For more information about Settings portlets, see the following help topics:
- Settings Portlet
- settings
- Tasks Portlets — Tasks portlets in SDF are represented with the list element and are predefined
by a task record type. You can specify this element in a dashboard of a publisheddashboard custom
object.
For more information about Tasks portlets, see the following help topics:
- Tasks Portlet
- list
The following example defines an Analytics portlet that displays 20 visible rows in a table:
TABLE
[scriptid=custworkbook1.custview2135234234]
My Analytics Portlet
20
Portlets are specified in a publisheddashboard custom object. For more information about published
dashboards in SDF, see the help topic Published Dashboards as XML Definitions.
For more information about portlets supported by the publisheddashboard custom object in SDF, see the
help topic Supported Published Dashboard Object Portlets.
## Financial Institution Parser Plug-in Support
## SuiteCloud Development Framework (SDF) supports customizing the Financial Institution Parser Plug-
in interface. The plug-in interface provides a way to create your own parsers for specific bank and credit
card data for reconciliation, as well as obtain corporate card expense data for employee expense reports.
For information about customizing and using a Financial Institution Parser Plug-in implementation in
## NetSuite, see the following help topics:
- Financial Institution Parser Plug-in
- Format Profile Creation
You can customize the plug-in interface in SDF by defining fiparserplugin custom objects. For
information about the available fields, see the help topic fiparserplugin.
Each fiparserplugin custom object requires a scriptfile field reference to a SuiteScript file that
implements some of the following interface functions based on your business workflow:
- parseData()
- getStandardTransactionCodes()
- getExpenseCodes()
- getConfigurationPageUrl()
The following example defines an fiparserplugin custom object named “Financial Institution Parser
1” that references the SuiteScript file connectionprofile1.js:
F
DEBUG
Financial Institution Parser 1
F
T
F
[/SuiteApps/connectionprofile1.js]
TESTING
For more information about defining fiparserplugin objects, see the help topic Financial Institution
Parser Plug-ins as XML Definitions.
## Integration Record Support
## SuiteCloud Development Framework (SDF) supports referencing integration records from an SDF
project. The integration record itself is not stored in the SDF project. Instead, the integration record is
represented by an integration custom object. The scriptid attribute in an integration custom object
acts as a unique identifier for the integration record in SDF SuiteApps. This ID provides a way to auto-
install the integration record in a NetSuite account as part of the SDF SuiteApp installation, and remove
the integration record when the SDF SuiteApp is uninstalled. For more information about the scriptid
attribute, see the help topic integration. For information about auto-installation, see the help topic Auto-
Installation of Integration Records.
Note: You cannot create an integration record using SDF. The integration custom object
represents the integration record by its scriptid attribute value, but the custom object does not
contain any fields or data. To create an integration record in your account, see the help topic
Creating an Integration Record.
For more information about referencing integration records in SDF projects, see the help topic
Integration Records as XML Definitions.
Dataset Builder Plug-in and Workbook Builder Plug-in
## Support (Beta)
## Warning: The Dataset Builder Plug-in and Workbook Builder Plug-in are part of the Workbook
## API, which is a beta feature. The contents of this feature are preliminary and may be changed
or discontinued without prior notice. Any changes may impact the feature’s operation with the
## NetSuite application. NetSuite warranties and product service levels shall not apply to the feature
or the impact of the feature on other portions of the NetSuite application. NetSuite may review
and monitor the performance and use of this feature. The documentation for this feature is also
considered a beta version and is subject to revision. Please review Beta Software Legal Notices.
ORACLE CONFIDENTIAL. For authorized use only. Do not distribute to third parties. Pre-General
Availability Draft: October 23, 2020.
## SuiteCloud Development Framework (SDF) supports customizing Dataset Builder Plug-in and Workbook
## Builder Plug-in. These plug-ins provide a way to implement dynamic datasets and workbooks in
SuiteAnalytics Workbook. Dynamic datasets and workbooks can display data based on role restrictions,
permission restrictions, enabled features, and other user-based settings. To create datasets and
workbooks to display this type of data, you must use a plug-in. For more information about these plug-
ins, see the help topics Dataset Builder Plug-in Interface Overview and Workbook Builder Plug-in Interface
Overview.
You can use SDF to customize the plug-ins by defining the following objects:
- datasetbuilderplugin — The custom object that defines each Dataset Builder Plug-in.
Each datasetbuilderplugin custom object requires a scriptfile field reference to a SuiteScript file
that implements the following interface function:
- createDataset()
For more information about the available fields, see the help topic datasetbuilderplugin.
The following example defines a datasetbuilderplugin custom object named "Dataset Builder 1" that
specifies the SuiteScript file dsbuilder.js:
A custom dataset builder
F
DEBUG
Dataset Builder 1
F
T
F
[/SuiteApps/com.example.yourapp/dsbuilder.js]
TESTING
- workbookbuilderplugin — The custom object that defines each Workbook Builder Plug-in.
Each workbookbuilderplugin custom object requires a scriptfile field reference to a SuiteScript file
that implements the following interface function:
- createWorkbook()
For more information about the available fields, see the help topic workbookbuilderplugin.
The following example defines a workbookbuilderplugin custom object named "Workbook Builder 1"
that specifies the SuiteScript file wbbuilder.js:
A custom workbook builder
F
DEBUG
Workbook Builder 1
F
T
F
[/SuiteApps/com.example.yourapp/wbbuilder.js]
TESTING
For more information about defining datasetbuilderplugin and workbookbuilderplugin objects, see the
help topics Dataset Builder Plug-ins as XML Definitions and Workbook Builder Plug-ins as XML Definitions.
SDF Support of SuiteAnalytics Workbooks Is Now Generally
## Available
## SDF support of SuiteAnalytics Workbooks is now generally available and is no longer considered to
be a beta feature. For information about SuiteAnalytics Workbooks custom objects, see the help topic
SuiteAnalytics Workbooks.
## Minor Updates to Custom Objects
Note the following information about updates to SuiteCloud Development Framework (SDF) support for
custom objects as of 2020.2:
## Object Field Type Notes
workflow isredirectwithoutsaving boolean Specifies whether to transform a record on the client
side instead of the server side. The default value is F,
which means that the record is transformed on the
server side. For more information, see Redirect Option
Object Field Type Notes
Available When Setting Transform Record Action
Parameters.
initlocalizationcontext multi-select list Specifies the localization contexts used to filter the
workflow execution. For more information, see Filter
Workflow Executions by Localization Context Support.
SuiteApps (Bundles) Released by NetSuite
## Accounting SuiteApps
This release note was updated October 28, 2020.
## Following are the 2020.2 accounting enhancement to SuiteApps:
- Sequential Liability Now Generally Available
- Sales Return Accounting Now Generally Available
- Fixed Assets Management Enhancements
- SuiteApprovals SuiteApp 6.00.0
Sequential Liability Now Generally Available
View the New Feature Training for Sequential Liability.
## Sequential Liability SuiteApp version 1.02 is now generally available. This SuiteApp provides a unified view
of accounts payable, accounts receivable, projects, and cash balances while enabling financial controllers
to pay vendors confidently. This SuiteApp helps effectively manage cash flow for transactions where
payment to vendors is linked to receipt from customers.
Using this SuiteApp, you can have an overall view of your subsidiary’s project-related payable and
receivable transactions. You can also view more details about the payable and receivable transactions for
a specific project.
Enhancements in this version include the Sequential Liability dashboard and the addition of Sequential
Liability information on the project record.
With Sequential Liability version 1.02, you can now do the following:
- View Sequential Liability tiles on the dashboard for the following KPIs: payable balance, receivable
balance, total receipts to date, and total payments to date for a project or subsidiary.
- View A/P and A/R details on the project record.
For more information on this SuiteApp, see the help topic Sequential Liability SuiteApp.
## Sales Return Accounting Now Generally Available
## Sales Return Accounting SuiteApp version 1.01.0 is now generally available. This SuiteApp enables you to
monitor sales returns separately in your account to meet standard retail accounting requirements.
You can install this SuiteApp for any industry vertical.
## Sales Return Accounting SuiteApp enables you to:
- Define accounting configurations using sales accounts, sales returns accounts, subsidiaries,
accounting books, and transaction types.
- Create and edit sales returns account mapping record if you have the Custom Records Entries
permission enabled in your account.
- Import sales and sales return transactions through CSV or Web Services.
- Map memo fields and segments to sales return accounts for analytics.
## Following are the bundle details for this SuiteApp:
- Bundle Name: Sales Return Accounting
- Bundle ID: 318158
- Version number: 1.01.0
For more information, see the help topic Sales Return Accounting.
Fixed Assets Management Enhancements
## Optimized Fixed Assets Reporting
The following Fixed Assets Management reports have been optimized to address performance and other
issues:
- Depreciation Schedule Report – In previous versions, customers that have a high volume of assets
under one subsidiary and asset type encounter a time limit exceeded error. This report has been
optimized so that customers will no longer encounter the error when processing large amounts of
data.
- Subsidiary name in Fixed Assets reports – To avoid the 300–character limit error, the Subsidiary
field in all standard Fixed Assets reports now shows the parent company name and the direct parent
company at the beginning of the subsidiary name.
- Asset Register Saved Search – The Acquisition column in the Asset Register Saved Search has been
corrected to exclude the acquisition cost on asset transfer.
## New Japan Depreciation Methods
The following additional depreciation methods are introduced for Japan:
- Japan Old Straight Line and Japan Old Declining Balance – These depreciation methods are used
for assets purchased before April 1, 2007. Using these methods, when the asset equals 5% of the
original cost, the asset will be depreciated using the Straight Line method over 5 years (60 months) or
until the residual value equals 1 JPY.
The Old Straight Line yearly depreciation limit is calculated as 90% of the acquisition cost, multiplied by
the depreciation rate.
- Japan Special Depreciation – Companies that meet requirements specified by the Japanese tax
authority may apply a special depreciation to their assets. This method is an accelerated depreciation
and is applied in addition to the regular depreciation of an asset. The special depreciation will enable
customers to complete the depreciation process early and calculate their taxable income. The special
depreciation may be applied to an asset within the first 3 years of its life.
The new depreciation methods for Japan are included in the Japan Schedule 16 (1) and Japan Schedule
16 (2) reports.
Note: The special depreciation can be applied only to assets that use the Japan Straight Line,
Japan 200% Declining Balance, and Japan 250% Declining Balance methods.
## French Derogatory Depreciation
To help customers comply with the depreciation requirements of the French tax authority, Fixed Assets
## Management now supports the French Derogatory Depreciation method. The derogatory depreciation is
calculated from the difference between the tax and the accounting value model depreciation amount for
the duration of the asset life. Customers can review the depreciation amount on the Review Derogatory
## Depreciation page. When the amount is finalized, the system will generate the Derogatory Histories. The
derogatory journals will also be recorded for the difference between the accounting and the derogatory
tax method.
## SuiteApprovals SuiteApp 6.00.0
Important: SuiteApprovals SuiteApp 6.00.0 is available for early access testing in Sandbox
accounts. The target availability to all production accounts is in November 2020.
SuiteApprovals version 6.00.0 includes the Email Approval preference, which you can enable to allow
approval of supported records through email.
When this preference is enabled, you can define email approvals for your organization through the
following:
- Email Approval Settings
- Approval Request Email Recipient – Set up and use the automatically generated email address
retrieved by the SuiteApprovals email capture plug-in.
- Approval Request Email Expiration (Days) – Enter the number of days given to email recipients
to send back a response.
- Invalid Response Default Sender – Select the employee you want to assign as sender of
validation error messages to approvers whose email replies are invalid.
- Attach Records to Email Approval Requests
If you prefer to attach a PDF copy of the record for approval to every email, enable the Advanced
PDF/HTML Templates feature. When this feature is enabled, you can set your preferred PDF template
for each supported record type in the Email Approval settings.
- Email Approval Log
## Valid email replies from approvers are automatically logged in the system. You can control access to
the approval log and records with permission assignments. You can assign an approver to manage
the approval log, review and evaluate the email replies, and implement each approval action to target
records. You can also create an approval rule specific to the email approval log.
To manage the number of approval logs, you can also set the number of days for retaining email
responses in the system. When the retention period is met, all email approval logs are removed from
the system except for those that are still under review.
For more information, see the help topic SuiteApprovals Version 6.00.0.
## Administration SuiteApps
This release note was updated October 21, 2020.
## Following are the 2020.2 administration enhancements to SuiteApps:
- Application Performance Management (APM) Enhancements
- Measuring Performance of Commerce Websites
- New Application Performance Management (APM) Sensors
Application Performance Management (APM) Enhancements
enhancements:
- New Performance Health Dashboard
- Navigation and Label Changes
- Accounts with Integration-Specific Limits on Concurrency Monitor
- New Script and Plug-in Types
## New Performance Health Dashboard
## Application Performance Management (APM) SuiteApp version 1.12.0 introduces the Performance Health
Dashboard. The new dashboard lets you monitor issues that may affect the performance of your record
pages, scripts, saved searches, integrations, and processors.
The Performance Health Dashboard is a visual tool that displays high-level information about account
issues by using tiles, figures, and tables. From the Performance Health Dashboard, you can navigate to
other tools in the APM SuiteApp to investigate the cause of an issue. Use the dashboard as a starting
point for investigating issues in your account.
To start using the dashboard, go to Customization > Performance > Performance Health Dashboard.
For more information, see the help topic Monitoring Account Performance.
## Navigation and Label Changes
With Application Performance Management (APM) SuiteApp version 1.12.0, you can see an updated
navigation menu where the Performance Health Dashboard is positioned on top of the other APM pages.
With this change, the dashboard will serve as the starting point when you investigate issues.
The following table lists the changes to the navigation and labels:
Navigation before APM 1.12.0 Navigation with APM 1.12.0
## Dashboard Performance Health Dashboard (new page)
Page Time Summary Record Pages Monitor (previously Dashboard)
## SuiteScript Analysis Page Time Summary
SuiteCloud Processors Monitor Page Time Details (previously accessed only with Page Time Summary)
SuiteCloud Processor Jobs Details SuiteScript Analysis
Web Services Analysis Script Queue Monitor
Concurrency Monitor SuiteCloud Processors Monitor
Search Performance Analysis SuiteCloud Processor Jobs Details
Search Performance Details Web Services Analysis
APM Setup Concurrency Monitor
Search Performance Analysis
Search Performance Details
## APM Setup
To view the updated menu, go to Customization > Performance.
For more information, see the help topic Accessing Application Performance Management.
## Accounts with Integration-Specific Limits on Concurrency Monitor
With Application Performance Management (APM) SuiteApp version 1.12.0, you can use the Concurrency
Monitor tool to view performance data for accounts with integration-specific limits. Prior to this update,
the Concurrency Monitor tool can only show data for accounts without integration-specific limits.
The update applies to both dashboards available with Concurrency Monitor tool, the Concurrency Monitor
and Concurrency Details dashboards. You can view a different display depending on the governance type
that applies to your account. If you are using an account with integration-specific limits, the Concurrency
Monitor dashboard lets you see separate sets of data for allocated limits and unallocated limits.
To start using the Concurrency Monitor tool, go to Customization > Performance > Concurrency Monitor.
For more information, see the help topic Monitoring Web Services and RESTlet Concurrency.
## New Script and Plug-in Types
With Application Performance Management (APM) SuiteApp version 1.12.0, you can view performance
data about the following script and plug-in types on Page Time Details and SuiteScript Analysis:
Script Types Plug-in Types
Bundle Installation Custom GL Lines
Client Payment Gateway
Map/Reduce Revenue Management
Mass Update Tax Calculation
Portlet
RESTlet
Scheduled
SDF Installation
Suitelet
User Event
## Workflow Action
For more information, see the help topic Script and Plug-in Types in Application Performance
Management.
## Banking SuiteApps
This release note was updated October 7, 2020.
## Following is the 2020.2 banking enhancements to SuiteApps:
- Bank Feeds Support for Financial Institutions Operating within Europe
- Automatic Import of Bank Statement Files Through Enhanced SFTP Connectivity
Bank Feeds Support for Financial Institutions Operating within
Europe
View the New Feature Training for Bank Feeds SuiteApp version 20.2.
## Bank Feeds SuiteApp version 20.2 is expanding its support by enabling you to connect your NetSuite
account to multiple financial institutions that operate in Europe. This feature automates the transfer of
your bank data from thousands of financial institutions in Europe to your NetSuite account for your bank
reconciliation task.
## Version 20.2 automatically provisions your account with a new format profile record. This new record is
exclusive for bank feeds integration with financial institutions that are under the PSD2 (Revised Payment
## Services Directive) European regulation. This expansion lets you:
- Configure a connection through an authorized account information service provider to your preferred
financial institutions operating in countries located in Europe and are PSD2 compliant.
- Manage your connection to your financial institutions by updating your Multi-Factor Authentication
(MFA) token, rebuilding, and deleting bank feeds connections.
- Manage associated financial accounts by identifying which accounts you want to include or exclude
from daily automatic bank data import.
For more information, see the help topic Bank Feeds SuiteApp.
Automatic Import of Bank Statement Files Through Enhanced
## SFTP Connectivity
Previously, with the Bank Connectivity SuiteApp, connecting to your financial institutions using SFTP
(Secure File Transfer Protocol) connectivity requires manual trigger and import of bank statement files
into NetSuite.
Auto Bank Statement Import (ABSI) SuiteApp introduces an automated way of importing bank statement
files into NetSuite daily.
Note: The new ABSI SuiteApp is replacing the Bank Connectivity SuiteApp, which is targeted for
deprecation in April 2021.
The ABSI SuiteApp uses the latest version of the SFTP Connectivity Plug-in to automatically retrieve and
upload bank and credit card statement files into NetSuite daily. This added feature enables finance users
to focus more on reconciling the bank and credit card transactions between NetSuite and your financial
institutions.
The ABSI SuiteApp enables you to:
- Securely connect to your financial institutions through the enhanced SFTP connectivity configuration.
- Eliminate manual process of triggering your SFTP connection to fetch the statement files from your
financial institutions.
For more information, see help topic Auto Bank Statement Import SuiteApp.
Food and Beverage SuiteApps
Following is the 2020.2 food and beverages enhancement to SuiteApps:
## Lot and Serial Number Trace
The Lot and Serial Number Trace SuiteApp helps you to trace components, semi-finished, or finished
goods from a raw material supplier through to the customer. You can perform forward trace and
backward trace. For component items, you can use forward trace to trace the source of procurement,
consumption, and delivery transactions. Forward trace also lists the delivery transactions of the assembly
items. For finished goods, you can use backward trace to list the source of manufacturing and delivery
transactions. Backward trace also lists sourcing transactions of component items. The SuiteApp also lists
various quantity details.
## Following are the SuiteApp details:
- Bundle Name: Lot and Serial Number Trace
- Bundle ID: 322956
- Version number: 1.00.0
- Availability: Public
Note: The Lot and Serial Number Trace SuiteApp supersedes the SuiteSolutions - Lot Traceability
SuiteApp (bundle ID – 132060).
For more details, see the help topic Lot and Serial Number Trace.
## Integration SuiteApps
This release note was updated September 16, 2020.
## Following is the 2020.2 integration enhancements to SuiteApps:
- NetSuite-Oracle Content and Experience Integration Renamed to Oracle NetSuite Content Cloud
## Service
- NetSuite-Oracle Content and Experience Integration General Availability and Enhancements
NetSuite-Oracle Content and Experience Integration Renamed
to Oracle NetSuite Content Cloud Service
In version 1.00.3, the NetSuite-Oracle Content and Experience Integration SuiteApp is renamed to Oracle
NetSuite Content Cloud Service.
For more information on this SuiteApp, see the help topic Oracle NetSuite Content Cloud Service.
NetSuite-Oracle Content and Experience Integration General
## Availability and Enhancements
The NetSuite-Oracle Content and Experience Integration SuiteApp is a cloud-based file repository
that uses Oracle Content and Experience Cloud to improve content management and collaboration in
NetSuite. The SuiteApp lets you create corresponding folders in Oracle Content for your NetSuite records.
## Then, upload all project-related files in the generated folders in Oracle Content to search, collaborate, and
share project documents, digital assets, and content in one location. For this release, you can enable the
NetSuite-Oracle Content and Experience Integration SuiteApp on project and project task records only.
enhancements:
- Using the OAuth2.0 authorization protocol, you must log in through Oracle Identity Cloud Service
(IDCS) using dedicated service administrator credentials to configure the SuiteApp.
- Using the Single Sign-on feature, you can use Oracle IDCS log in credentials to access NetSuite.
- You can enter the placeholder {RELATEDRECORDS} in your email template to retrieve information
about any project, project task, or milestone task related to the deleted record.
- You can use the SuiteApp on project records created from project templates.
- You can track project records not connected to Oracle Content using a predefined saved search
included in the SuiteApp. This saved search can be added as a reminder on the Reminders portlet or
as a Custom Search portlet on your NetSuite home page.
For more information on this SuiteApp, see the help topic Oracle NetSuite Content Cloud Service.
Inventory Management SuiteApps
## Following are the 2020.2 inventory management enhancements to SuiteApps:
- Quality Management Enhancements
- Actual vs. Theoretical Variance Reports
- Auto Assign UPC SuiteApp General Availability and Enhancements
Quality Management Enhancements
## Fulfillment Triggers
The NetSuite 2020.2 Quality Management SuiteApp enables you to define and carry out quality
inspections to support sales order fulfillment. Inspections can be associated with any combination of item,
location, customer, and shipping status to ensure inspections meet your organization’s requirements. You
can assign quality specifications to fulfillment transactions to initiate inspection activities based upon this
data.
The Quality Management SuiteApp monitors NetSuite transactions and evaluates inspection needs line-
by-line. After an inspection is triggered it is executed in the Quality tablet interface in the same manner as
other inspections that quality engineers perform.
To learn more, see Fulfillment Triggers.
## Sampling CSV
The NetSuite 2020.2 Quality Management SuiteApp CSV upload feature helps to streamline activities to
capture large volumes of sample data. The SuiteApp provides a pre-formatted template in the Quality
tablet interface that quality engineers can use to efficiently collect Excel data offline into the tablet.
Uploading to the tablet interface accelerates data transfer to NetSuite with minimal interruption to tablet
usage. CSV uploads can accommodate as much as 8 Mb of Excel data.
## Engineers are then notified by email if errors are encountered during data upload so they can address
the problem using focused inline editing or re-importing the data set. The system manages the file
cabinet cleanup to avoid excessive use of this resource.
To learn more, see the help topic Inspection Sampling CSV.
## Scriptable Inspection Triggers
The NetSuite 2020.2 Quality Management SuiteApp includes a SuiteScript 2.0 module that enables you
to initiate predefined inspection activities (specifications) from within SuiteScript 2.0 customizations to
## NetSuite. This enhancement enables you to extend inspection capabilities to address your unique market
and organizational inspection needs. Exposing this API ensures that implementations are streamlined and
have the necessary safeguards to avoid inconsistent inspection data.
To learn more, see Scriptable Inspection Triggers.
## Quality Connection to External Quality Management System
The NetSuite 2020.2 Quality Management SuiteApp enables external applications to obtain notifications
about inspection needs. The NetSuite SuiteSignOn standard transmits an SSO OAuth token to authorize
the web service to interact with Quality Management data from a third-party application. Quality
## Management can redirect inspections to external applications via an individual trigger rule (context
record). This capability enables the incremental transfer of inspection responsibilities to an outside Quality
Management System including support for hybrid or multiple QMS environments.
## Actual vs. Theoretical Variance Reports
## Shelf-to-Sheet Count SuiteApp version 1.02.0 includes Actual vs. Theoretical Variance Reports. The reports
are based on two consecutive Shelf-to-Sheet Count records, which are required for generating the
reports. The Dollar Variance Report calculates the variance between actual and theoretical costs or usage
of food ingredients in monetary value ($). The Unit Variance Report calculates the variance between actual
and theoretical costs or usage of food ingredients in terms of quantity. A significant or large variance
value implies some losses or wastage of food ingredients in storage or preparation, errors in inventory,
improper portioning, or theft.
For more information, see the help topic Actual vs. Theoretical Variance Reports in the Help Center.
Auto Assign UPC SuiteApp General Availability and
Enhancements
enhancements:
- You can now set the following custom preferences:
- Deactivate Items Without UPC Code
- Automatically Assign UPC to New Item
These preferences will determine the status of newly created items and the Universal Product Code
(UPC) assignment option for those items.
- You can exclude items from automatic UPC code assignment using mass update.
- You can use the All Assigned UPC Codes with Item saved search to display UPC codes that are in use
and the items associated with them.
- You can select a new option, Do not Assign New UPC Code, in the UPC Code Assignment field on an
item record.
For more information, see the help topic Auto Assign UPC.
## Localization SuiteApps
This release note was updated October 7, 2020.
## Following are 2020.2 localization enhancements to SuiteApps:
- ANZ Localization
- Contra Account Sheets Now Generally Available
- China Localization Enhancements to Compliance and Reporting Requirements
- Country-Specific Reports General Availability and Enhancements
- EMEA Localization Enhancements
- France Localization Enhancements
- Germany Localization (Beta) Enhancements
- India Localization Enhancements
- India Localization SuiteTax Engine SuiteApp Enhancements
- Ireland Localization
- Japan Localization Enhancements
- Norway Tax Reports
- Philippine Localization
- United Kingdom Localization Enhancements
## ANZ Localization
The ANZ Localization SuiteApp provides localization features such as customized transaction fields,
records, and report templates specific to Australia and New Zealand.
The SuiteApp provides the following features and capabilities:
- A tax report template for generating the Taxable Payments Annual Report
- Additional setup and rules for records and transactions specific to Australia and New Zealand
customers and users
- Automatic updates of new localization features and enhancements for Australia and New Zealand
accounts
The ANZ Localization SuiteApp requires the Tax Reporting Framework SuiteApp to generate tax reports
and is currently only supported in the Legacy environment.
To learn more about the SuiteApp, see the help topic ANZ Localization.
China Localization Enhancements to Compliance and
## Reporting Requirements
## China Localization SuiteApp version 1.00.15 includes enhancements to improve report printing
performance and adds new capabilities that support compliance to China CAS regulations.
The China Localization SuiteApp provides important financial reports that are needed to operate in China.
These reports are updated with the following enhancements:
## Report Name Enhancements
China Subledger Report ■ Memo field input character limit is extended to 300. Display is truncated for printing
on fixed-line forms such as the 5-line, 8-line, and 2-per-page voucher layouts.
## China Cash & Bank
Journal Ledger ■ The Creator, Approver, and Poster fields now show the middle name of each
person.
China Voucher List ■ Standard ISO currency codes are used for label of foreign currency fields.
- The generally accepted term “FX” is now used for the foreign currency column English
translation.
- Support for Accounting Context to enable printing of vouchers using China GAAP
accounts or other selected contexts is added.
China Voucher List ■ The China Voucher List page now shows the Creator, Approver, and Poster fields for
each voucher.
- You can now change the sorting order of the vouchers before printing them. You can
sort by voucher number, date, document type, or document number.
- You now have the option to select a voucher and print immediately from the Voucher
List search page.
- Issues on formatting, page splitting, and content printing have been resolved.
China Voucher Printing ■ Support for Accounting Context to enable printing using China GAAP accounts is
Report added.
- Issues on formatting, page splitting, and content printing have been resolved.
For more information, see the following help topics:
- Generating China Voucher Printing Report
- Generating the China Voucher List
- China Subledger Report
- China Cash & Bank Journal Ledger Report
- China Account Balance Report
## Contra Account Sheets Now Generally Available
The Contra Account Sheets SuiteApp is now generally available. This SuiteApp enables you to generate
transaction records with contra account information. These records can be used by accountants to view
the account balance or transactions. Records can be also filtered, for example, by customer, vendor, or
employee. You can generate reports for various time periods and export them to PDF format.
For more information, see the help topic Contra Account Sheets.
Country-Specific Reports General Availability and
## Enhancements
The Country-Specific Reports SuiteApp enables you to create, edit, or view complex financial reports
for different countries. It also serves as a framework supporting various Localization SuiteApps. After this
release, this SuiteApp is no longer a beta feature and is generally available to all NetSuite users.
adjustments:
- For each variable (basic report building block), you can choose a starting point and an end point for
the date range of referenced data. Setting relative periods on variable level is necessary for the Net
profit and Unrealized gains from previous periods to be properly displayed in reports. This feature
ensures that Period End Closing processes are correctly reflected in financial reports created by the
Country-Specific Reports SuiteApp.
- You can add a special macro to the report template to display the balance of each variable split into
balances of individual accounts. This means that for each variable in a report, you will see the list of
accounts it consists of.
- If a report uses the lists of accounts feature and the second comparative column, even inactive
accounts are listed in it (those active in at least one of the periods).
- New filter variables have been added. In exported files, you can see additional information about
selected filter values (at the time when the report export was run). Accounting Book, Comparative
Period From, and Comparative Period To filter variables are available.
- For the Accountant user role, the permission level to access Report, Variable, and Export records
decreases to View.
- The Subsidiary Context filter now also lists elimination subsidiaries.
For more information, see the help topic Country-Specific Reports Overview.
## EMEA Localization Enhancements
EMEA Localization SuiteApp now delivers the following payment templates provided by the Electronic
## Bank Payment SuiteApp:
- BACS – Bank of Ireland
- SEPA Credit Transfer (HSBC)
- SEPA Credit Transfer (Austria)
- SEPA Credit Transfer (ABN AMRO)
- SEPA Direct Debit (ABN AMRO)
For more information, see the help topic EMEA Localization.
## France Localization Enhancements
For more information, see the help topic France Localization.
## France Electronic Bank Payment Templates
Version 2.03.0 enables bank payments processing using the provided payment templates in the following
formats:
- SEPA Credit Transfer (France)
- CFONB
- FR International CFONB320
- FR International ISO20022
Using these payment templates requires the Electronic Bank Payments SuiteApp.
## New France Financial Reports
A new saved report, FR Balance Auxiliaire, is available in the new version.
## Apart from the France financial saved reports, the France Localization SuiteApp also provides the
following financial reports that were built using the Country-Specific Reports SuiteApp:
- France Balance Sheet
- France Income Statement
- France Soldes intermédiaires de gestion (SIG)
You can view these reports on the Country-Specific Reports page, which is provided by the Country-
Specific Reports SuiteApp.
The new version also provides saved search-type Lettrage reports, which list matched transactions by
customer and vendor.
## Saved Searches for FEC Compliance
To aid in validating transactions, the France Localization SuiteApp provides saved searches that list
transactions that do not conform to the requirements of the Fichier ďEcritures Comptables (FEC).
## France VAT Reports for Cash Basis and Accruals
To fulfill the VAT reporting requirement in France, customized VAT reports are provided so that you can
declare VAT on accruals or cash basis depending on the nature of the goods sold.
## Germany Localization (Beta) Enhancements
The Germany Localization SuiteApp now supports new VAT reports, which reflect the temporary VAT
rate deductions adopted due to COVID-19.
India Localization Enhancements
enhancements:
- Electronic Invoicing Features for India - To comply with the electronic invoicing requirements for
## India, the SuiteApp now enables you to do the following:
- Generate e-invoices that comply with the GSTIN standards for cash sale, credit memo, invoice, and
vendor credit transactions.
- Register e-invoices with the Invoice Registration Portal (IRP).
- Send the certified e-invoices to customers or vendors.
- View trail of activities in detail in the E-Document Audit Trail subtab.
- Generate and send e-invoices for certification in bulk.
- Generate E-Way Bill along with e-invoice, if you provide E-Way Bill details in the transaction.
- Add and display the Electronic Documents portlet on the dashboard.
The SuiteApp also includes templates and certification sending methods that let you integrate with the
GST Suvidha Providers (GSPs). ClearTax is configured in the SuiteApp as the GSP.
To use the electronic invoicing features, you must install the latest version of the Electronic Invoicing
SuiteApp. To know more about getting access, contact your NetSuite account manager or NetSuite
customer support.
- Changes to the Port Code Field Type - The Port Code field type is changing from free text to
dropdown type for cash sale, credit memo, cash refund, invoice, and vendor bill transactions. The field
is populated with a list of port codes as per the ICEGATE portal to select from.
- Changes to E-Way Bill Date Field Name and Type - In the E-Way Bill Details section, the E-Way Bill
## Date field name is changing to E-Way Bill Valid From. Also, you can now view both date and time
in the field. Consequently, all existing transactions will display a default time of 00:00. The impacted
transaction records include bill credit, cash sale, cash refund, credit memo, and invoice transactions.
For more information, see the help topics Electronic Invoicing for India and India Goods and Services Tax
(GST).
India Localization SuiteTax Engine SuiteApp Enhancements
enhancements:
- Support for Goods and Services (GST) Compensation Cess calculation for all GST supported
transaction types and the export of calculated cess amount in an E-Way Bill.
- Automatic selection of the default India HSN or SAC codes on transactions line items when entering
assembly items in a transaction record.
- Addition of a new Create from Bill ID field that displays the bill ID for which the system created the
TIjournal record.
- Addition of a new India Vendor Wise Transaction saved search that lists vendor wise transaction
details.
- Support for Union Territory of Ladakh businesses to enable calculation of taxes on transactions and
generation of reports using the SuiteApp.
For more information, see the help topics India Goods and Services Tax (GST), Applying Tax Deduction at
Source on Vendor Bills, and Tax Deduction at Source Tax Details.
## Ireland Localization
The Ireland Localization SuiteApp works with the Tax Reporting Framework SuiteApp by providing the
Irish SuiteTax-based report templates. You can select them from the list of country-specific templates on
the Country Tax Reports page. The following report templates are available:
- Ireland VAT Report: Return of Trading Details
- Ireland VAT Reports: Return Form VAT3
- Intrastat
- EC Sales List
Ireland Localization SuiteApp also delivers the following payment templates provided by the Electronic
## Bank Payment SuiteApp:
- SEPA Credit Transfer specifications of the Bank of Ireland
- SEPA Credit Transfer specifications of HSBC
- BACS scheme of electronic bank payment by the Bank of Ireland
Installing the Ireland Localization SuiteApp requires EMEA Localization SuiteApp.
For more information, see the help topic Ireland Localization.
Japan Localization Enhancements
## Japan Localization Setup Subtab
The new Japan Localization Setup subtab is now available on a Japan subsidiary record for OneWorld
accounts or on the Company Information page for accounts without OneWorld.
## On the Japan Localization Setup subtab, you can configure the following settings:
- Use Holiday Checking
- Consumption Tax Form Print Option
- Statement Search
- Invoice Summary Template
- Save Invoice Summary In
- Save Printed PO In
For more information, see the help topic Japan Localization Setup.
## Support for Japan Subcontract Act and Purchase Order Numbering
An Apply Subcontract Act box is available on vendor records with a Japan subsidiary. Check this box
for vendors with transactions that are subject to the Subcontract Act. If the box is checked for a vendor,
approved purchase orders created for that vendor will display a custom Print button and a Print History
subtab.
When you click the Print button on a purchase order, the system automatically logs the number of times
the purchase order was printed. You can find this information in the Number of Times Printed field on
the Print History subtab of the purchase order.
You can also specify where printed purchase orders will be saved. On the Japan Localization Setup subtab,
you can specify a folder in the Save Printed PO In field.
For more information, see the help topic Subcontract Act and Purchase Order Numbering.
## Invoice Summary Generation Status Page
The status of invoice summary generation jobs can be viewed on the Invoice Summary Generation
## Status page, from Transactions > Customers > Generate Invoice Summary. Click View Invoice Summary
## Generation Status, then click Refresh to update the statuses. The Invoice Summary Batch Records table
has a Status column that displays any of the following statuses of invoice summary generation jobs:
- Queued
- Invalid
- Hanging
- Error
For generation jobs with Hanging status, the administrator can resubmit them by clicking Resolve
Hanging Generation.
For more information, see the help topic Viewing Invoice Summary Generation Status.
Inclusion of Custom Payment Adjustment Records in the Invoice
## Summary
Payment adjustments or accounts receivables (AR) can be included in the invoice summary using the
following custom transactions that come with the Japan Localization SuiteApp:
- AR Adj Debit Invoice Summary – This record is used to subtract accounts receivables from the total
net payments.
- AR Adj Credit Invoice Summary – This record is used to add accounts receivables to the total net
payments.
The custom transactions are available from Customization > Lists, Records, & Fields > Transaction Types >
AR Adj Debit Invoice Summary or AR Adj Credit Invoice Summary > New Transaction.
If included in the invoice summary, the amounts in these custom transactions are applied or reflected in
the Payments Received this Period of the invoice summary, with AR credits added to this amount and AR
debits deducted from it.
For more information, see the help topic Including Payment Adjustments in the Invoice Summary.
## Netherlands Localization Enhancements
The Netherlands Localization SuiteApp version 1.01.0 provides electronic bank payment templates in the
following formats specific to the Netherlands:
- Equens – ClieOp
- Equens – ClieOp (ING Bank)
- SEPA Credit Transfer (Netherlands)
Using these templates requires the Electronic Bank Payments SuiteApp, which handles the processing of
payments for vendor bills, customer refunds, employer expenses, and partner commissions.
For NetSuite accounts with the Electronic Bank Payments SuiteApp, which installed payment templates,
installing the Netherlands Localization SuiteApp will update those templates to formats compliant to the
Netherlands standards.
For more information, see the help topic Netherlands Localization.
## Norway Tax Reports
The Norway Tax Reports SuiteApp delivers templates to generate the Norway Standard Audit File for Tax
(SAF-T) reports. Submitting these reports on monthly basis is mandatory for all Norwegian companies
with a turnover exceeding 5,000,000 Norwegian Krones. The report structure is based on the SAF-T
standard format by the Organization for Economic Cooperation and Development (OECD).
To install the Norway Tax Reports SuiteApp, you must have the following SuiteApps installed in your
## NetSuite account:
- EMEA Localization
- Norway Localization
- International Tax Reports
- Supplementary Tax Calculation
- Tax Audit Files
- Tax Reporting Framework
For more information, see the help topic Norway Tax Reports SuiteApp.
## Philippine Localization
The Philippine Localization SuiteApp supports Philippine invoicing with SuiteTax.
You can install this SuiteApp in NetSuite Philippine accounts with the following setup:
- SuiteTax feature is enabled and properly set up.
- SuiteTax Engine is installed.
This SuiteApp is available and can be installed from the NetSuite SuiteApp Marketplace. It is developed
with SuiteScript version 2.1, using the SuiteCloud Development Framework (SDF).
For more information, see the help topic Philippine Localization.
## Philippine Invoicing with SuiteTax
The Philippine Localization SuiteApp includes Philippine standard forms, document types, and PDF/HTML
templates for invoicing. You can use them to print VAT invoices or VAT official receipts in PDF or HTML.
## Companies with Computerized Accounting System (CAS) can use the PDF/HTML templates. Companies
without CAS or are using loose-leaf books of accounts can use the pre-formatted templates. Printed
transactions that use Philippine PDF/HTML templates comply with tax regulations set by the Bureau of
Internal Revenue (BIR) for VAT-registered payers. For more information, see the help topic Philippine
Invoicing with SuiteTax.
## Philippine Document Numbering
After setting up the Philippine Document Numbering feature, it automatically generates and assigns a
document number to the following document types:
- Sales Invoice
- Billing Statement
- Collection Receipt
- Official Receipt
- Credit Memo
For more information, see the help topic Setting Up Document Numbering.
## Permit to Use (PTU), Inclusive Serial Number, and BIR-required Details
You can include the Permit To Use (PTU) Number and Inclusive Serial Number when you print VAT
invoices or VAT official receipts. The numbers are set up on Subsidiary or Location records for OneWorld,
or on the Company Information page without OneWorld. Also, when you print transactions that use
## Philippine PDF/HTML templates, the footer indicates other BIR-required details. These details include
document validity and non-VAT invalid input tax claim. For more information, see the help topic Setting Up
Permit to Use and Inclusive Serial Number.
## Including VAT in Printing Philippine Documents
The Include VAT in Printing box is available on Philippine subsidiary records for OneWorld, or on the
## Company Information page without OneWorld. You can check this box to include VAT in the transaction
amount when you print Philippine documents. For more information, see the help topic Including VAT in
Printing Philippine Documents.
## Specifying Liability on Philippine Documents
You can specify the users or persons who processed a Philippine document. On Philippine documents,
fields are available to enter the names of users or persons who prepared, reviewed, approved, and
received the transaction upon submission to the tax agency or customer. The names entered in the fields
are indicated in the footer of Philippine document printouts. For more information, see the help topic
Specifying Persons Who Processed Philippine Documents.
## United Kingdom Localization Enhancements
The United Kingdom Localization SuiteApp now delivers the following payment templates:
- BACSTEL –IP (internet service variation of BACS)
- BACS (Bacs Payment Schemes Limited)
- BACS – Albany ALBACS-IP (Albany ePAY Bureau)
- BACS – Bank of Scotland (Bank of Scotland PLC)
- BACS DD
- HSBC Faster Payments
- HSBC UK CHAPS
- HSBC UK BACS
- HSBC BACS or Faster Payments
- SVB BACS
- SVB CHAPS
- SEPA Credit Transfer (SVB)
- SVB Faster Payments
- SVB BACS or Faster Payments
For more information, see the help topic United Kingdom Localization.
Manufacturing SuiteApps
## Following are the 2020.2 manufacturing enhancement to SuiteApps:
- Production Result Trigger in Advanced Manufacturing
- Manufacturing Mobile Work Order Actual Production Start and End Dates
## Production Result Trigger in Advanced Manufacturing
In NetSuite 2020.2, Advanced Manufacturing enables you to define and perform quality tablet production
reporting inspections in response to Advanced Manufacturing tablet reporting. Existing build/completion
## Quality Management triggers, which are still available, create a single inspection for production activities
regardless of the number of times tablet reporting occurs. This new trigger enables you to initiate
inspections each time the operator submits production counts from the tablet. This feature enables you
to model more accurately the inspection needs of the business.
To learn more, see the help topic Collecting Data.
Manufacturing Mobile Work Order Actual Production Start and
## End Dates
In NetSuite 2020.2, Manufacturing Mobile automatically updates actual production start and end dates
when you report data through the Manufacturing Mobile scanner. You can still manually edit these dates
when necessary.
This release enhances how the manufacturing mobile scanner captures shop floor data and integrate
seamlessly with NetSuite.
To learn more, see the help topic Mobile Data Collection.
## Non-Profit SuiteApps
This release note was updated October 21, 2020.
Following are the 2020.2 non-profit enhancements to SuiteApps:
## NFP Labor Expense Allocation
The NFP Labor Expense Allocation SuiteApp allocates payroll costs, including salary and fringe benefits, to
benefiting program, project, or grant segments.
The key benefits of using the NFP Labor Expense Allocation SuiteApp include:
- Automatic allocation of personnel costs to benefiting project, department, class, program, grant, or
other NFP segments.
- Viewing and reporting on total direct costs, including the actual labor costs, of running a program or
project.
## Following are the SuiteApp details:
- Bundle name: NFP Labor Expense Allocation
- Bundle ID: 305364
- Version number: 1.00.0
- Availability: Public
For more details, read the help topic NFP Labor Expense Allocation.
## Order Management SuiteApps
This release note was updated October 7, 2020.
## Following are the 2020.2 order management enhancements to SuiteApps:
- Dunning Letter Notifications for Grouped Invoices
- Electronic Bank Payments Enhancements
- Grid Order Management Enhancements
- Multi-Language Support for Return Authorization from Case
- Enhanced Validations and Defaulting Enhancement
## Dunning Letter Notifications for Grouped Invoices
Dunning SuiteApp version 1.04.9 lets you disable the individual dunning notifications for grouped invoices
that are sent by email or printed letters.
A new Dunning Notifications for Group Invoices box is added to the Dunning Letters subtab on the
## Customer form. By default, this box is checked and individual dunning notifications for grouped invoices
are disabled. If you want to send individual dunning notifications for grouped invoices, clear the Dunning
Notification for Group Invoice box.
Note: The individual dunning notifications are disabled only in accounts that have the Invoice
Grouping feature and invoice level dunning enabled.
For more information on sending dunning letter notifications, see the help topic Sending and Printing
Dunning Letters.
Electronic Bank Payments Enhancements
Processing Automated Batch and Approval Routing using
## SuiteScript 2.0
Starting 2020.2, all functions for processing EFT Batch Processing and Approval Routing using the
## Electronic Bank Payments SuiteApp now use SuiteScript 2.0. This change does not have any impact
on the existing feature to process EFT batch and approval routing using Electronic Bank Payments.
Additionally, the system sends an email to the user who triggered the batch processing and to the email
recipients listed on the Batch Details subtab of the Company Bank Details page.
## Processing Customer Refund using SuiteScript 2.0
As of 2020.2 release, all functions for processing Customer Refunds using the Electronic Bank Payments
SuiteApp now use SuiteScript 2.0. This change does not have any impact on the existing feature to
process customer refunds using Electronic Bank Payments.
## Processing Bank Details page using SuiteScript 2.0
In the Electronic Bank Payments SuiteApp version 2020.2, all functions for setting up bank records on the
## Bank Details page now use SuiteScript 2.0. This change does not have any impact on existing processes. A
role based restriction is introduced, in which a user cannot view or edit Entity Bank Details. This happens
when the user does not have permission for the subsidiary attached to the entity record. Administrator
should provide the access to the respective users for editing the bank details.
The update also removes old scripts and deploys new scripts. The scripts are listed in the following table:
## Old Scripts New Scripts
## Generic Entity Bank Detail Initializer - Entity Bank Details CS -
customscript_2663_entity_bank_details_ue customscript_10782_entity_bank_ue
## Generic Entity Bank Detail Validator - Entity Bank Details UE -
customscript_2663_entity_bank_details_cs customscript_10782_entity_bank_cs
## Changes to DTAZV Templates
In 2020.2, the following new mandatory fields are added to the DTAZV payment templates on the
Company Bank Details page. The same fields are added to the Bank Details page as optional fields.
- A-Number
- State Number
- Customer Zip
## Changes to Custom Payment File Templates
In 2020.2, the SuiteApp enables you to add custom help text for the Entity Reference field on custom
templates. This field is similar to the Reference field on a Payment File Template when defining XML
content. The custom help text is provided to help the users in using these fields more efficiently.
Grid Order Management Enhancements
## Grid Printing Layout Changes
## Grid Order Management version 6.02.0 provides significant layout improvements in the PDF files
generated through grid printing. The new layout is now available for the following transaction records:
- Invoices
- Packing slips
- Picking tickets
- Purchase orders
- Sales orders
page orientation.
- Headers and footers – The header and footer formats remain consistent across all supported
transactions. The header includes company and transaction details, while the footer displays the bar
code and page number.
- Number and currency formats – The updated grid print templates follow user preferences. You can
personalize how numbers and currencies appear in the printout.
- Grid table elements - Matrix items with grid templates appear on the grid tables. The grid table
displays elements such as item name, column and row attributes, and item quantities. Each grid
table has a maximum of six column attributes. If the column attributes in the grid template exceed
this number, the attributes overflow to the next grid table. All grid tables show the calculated total
quantity, but only single grid tables display aggregate item quantities for each column attribute.
- Item list elements - Following the grid table, nongrid items appear on the item list. The item list
includes all items that do not belong to any grid table, including nonmatrix items, matrix items without
grid templates, and payment items. The item list displays elements, such as the item quantities,
names, and calculated total quantity.
- Invoice, Purchase Order, and Sales Order printout fields - Invoice, purchase order, and sales order
printouts display item rates, amounts, and the calculated total amount on both the grid table and item
list. The last page of the document shows a summary of details, including the tax total and calculated
sum of discounts, markups, shipping costs, and gift certificates. The summary also displays the grand
total quantity and grand total amount.
- Packing Slip printout fields - Packing slip printouts show ordered, backordered, and shipped
quantities. The last page of the document also contains the customer return form.
To learn more about this feature, see the help topic Grid Order Management.
Grid Order Management Script Deployment Updates
## Management script deployments:
- Payment PostBack
- Web Store
- Web Application
This change does not affect existing SuiteApp installations. When existing customers get the latest
SuiteApp version, these execution contexts remain active. If you are an existing customer, you should
manually inactivate these three contexts in the following scripts:
- GOM Grid Printout Transaction Form CS
- GOM Grid Printout Transaction Form UE
- GOM Transaction CS
- GOM Transaction Form UE
- WD GOM Hide Field Common Handling UE
For more information about excluding these execution contexts, Removal of Payment PostBack, Web
Store, and Web Application Execution Contexts from Grid Order Management Script Deployments,
SuiteAnswers ID 95685.
## Multi-Language Support for Return Authorization from Case
Return Authorization from Case SuiteApp version 1.00.1 is now translated into the following supported
languages:
- Chinese (Simplified)
- Chinese (Traditional)
- Czech
- Danish
- Dutch
- English
- Finnish
- French
- French (Canada)
- German
- Indonesian
- Italian
- Japanese
- Korean
- Norwegian
- Portuguese (Brazil)
- Russian
- Spanish
- Spanish (Latin America)
- Swedish
- Thai
- Turkish
- Vietnamese
To set the language preference, you must enable the Multi-Language feature in your account. For more
information, see the help topic Multi-Language Support.
## Enhanced Validations and Defaulting Enhancement
Enhanced Validations and Defaulting SuiteApp version 1.00.8 includes a change on how inventory is
validated when the Prevent Negative Inventory preference is enabled.
When editing the item quantity in an existing transaction, the system does not count the previously
granted items when validating the new value entered. For example, the quantity of an item in a
transaction is 4. When you edit the quantity to 5, only the difference of 1 is counted as the requested
quantity and is checked in the inventory.
In previous versions, the system recognizes the new item quantity as the requested quantity and validates
this value, including previously granted items, in the inventory.
For more information about this SuiteApp, see the help topic Enhanced Validations and Defaulting.
Projects SuiteApps
## Following are the 2020.2 projects enhancement to SuiteApps:
- Project Risk Forecast Now Available
- RACG Calendar Follows First Day of Week Account Preference
## Project Risk Forecast Now Available
Project Risk Forecast version 1.00 lets project managers assign a risk level to projects (low, medium, high,
or none). When charge-based projects are assigned a risk level, finance users can generate a report that
can help recognize the financial impact of risks on future revenue.
For more information about this SuiteApp, see the help topic Project Risk Forecast.
## RACG Calendar Follows First Day of Week Account Preference
of Week preference from the user's NetSuite account. Previously, you cannot set the start of week to
Monday. You can set the preference at Home > Set Preferences, then select a value in the First Day Of
Week field under Localization. This setting applies to all user roles.
- Optimization of searches to USR engine – This enhancement changes the technology behind the
searching mechanism in SuiteApps to improve the performance of an initial load of the RACG.
For more information, see the help topic Resource Allocation Chart/Grid SuiteApp.
SuiteBuilder Customization SuiteApps
Following is the 2020.2 SuiteBuilder Customization enhancements to SuiteApps:
## Bill Data Presentment (Beta) Enhancements
## Warning: Bill Data Presentment SuiteApp is a beta feature. The contents of this feature are
preliminary and may be changed or discontinued without prior notice. Any changes may impact
the feature's operation with the NetSuite application. NetSuite warranties and product service
levels shall not apply to the feature or to the impact of the feature on other portions of the
NetSuite application. NetSuite may review and monitor the performance and use of this feature.
The documentation for this feature is also considered a beta version and is subject to revision.
Please review Beta Software Legal Notices. ORACLE CONFIDENTIAL. For authorized use only. Do
not distribute to third parties.
## Template Assignment
This feature enables you to assign templates to customers, customer groups, or transaction subsidiaries.
You can set template assignments from the Report Editor page or by going to Bill Presentment > Editors
> Template Assignment.
When a template is assigned to a customer, customer group, or transaction subsidiary, the assigned
template will be used when printing BDP invoices for the customer or subsidiary. If there are multiple
template assignments associated with the invoice, the most recent template assignment will be used.
If there is no template assignment associated with the invoice customer or subsidiary, the preferred
template will be used.
## Bulk Print and Email
This feature enables you to print and email invoices in bulk using standard or custom BDP templates. You
can use the preferred template or assigned template, or you can select a specific template to use for the
bulk print or email request.
The following new pages are available for bulk print and email requests:
- Print BDP Invoice – This page enables you to print multiple invoices using BDP templates. The
invoices will be combined in a single PDF file, which will be available for download after the PDF
generation is complete. The PDF file will also be saved in the file cabinet.
To access the Print BDP Invoice page, go to Bill Presentment > Editors > Print BDP Invoice or click the
Print button on the Report Editor page.
- Email BDP Invoice – This page enables you to generate multiple invoices using BDP templates and
send them through email. The generated invoices will be sent to the email address specified on the
customer record associated with each invoice. You also have the option to modify the customer email
address and include additional recipients for each invoice.
To access the Email BDP Invoice page, go to Bill Presentment > Editors > Email BDP Invoice or click the
Email button on the Report Editor page.
Advanced Formatting Options
on the Report Editor page:
- Enhanced table formatting options – The following new properties are now available for table and
table column:
- Theme – This new table property enables you to apply a predefined set of styles (font, border, and
background) to a table element.
- Row Style – This section enables you to apply a background color to specific table rows. You
can specify a condition to determine to which rows the style will be applied. You can also create
multiple table row styles.
- Table Column Styles – On the table column properties, you can now set styles for the table
header, column body, subfooter, and footer. You can set the background color, font, and border
for each table section. Under column body style, you can also specify a condition to determine to
which column cell the style will be applied.
- Text formatting options – You can set the font face, size, color, and style for text elements in the
template. The font properties are available for table column, pie chart, static text, and dynamic text.
- Color picker – Version 20.2 provides a convenient and flexible way to set color values using a color
picker. Click the color picker next to the color field to select a color from the color palette or spectrum,
or to enter values in the RGB fields.
SuitePeople SuiteApps
## Following are the 2020.2 SuitePeople enhancement to SuiteApps:
- Onboarding and Offboarding Plans Enhancements
- Deprecation of TribeHR Payroll Integration
## Onboarding and Offboarding Plans Enhancements
Onboarding/Offboarding Plans version 1.02.0 changes the Status label in plans for clarity. The following
table shows the enhancements made in this update.
Plan Section Onboarding/Offboarding New Label for Description
## Role Status Field
## Header Coordinator Plan Status Shows the status of the entire onboarding or
Section offboarding plan.
Assignee Assignee Status Shows tasks assigned to the employee.
In previous versions, the Status field shows the
overall status of the plan including unassigned
tasks. With this update, this field now only reflects
the overall status of assigned tasks.
Tasks Subtab Coordinator or Employee Task Status Shows the status of the specific onboarding or
offboarding task.
For more information, see the help topic Working with Plans.
## Deprecation of TribeHR Payroll Integration
As of 2020.1, the TribeHR Payroll Integration SuiteApp is deprecated. You can no longer use this SuiteApp
to synchronize time-off transactions with SuitePeople U.S. Payroll.
## Taxation SuiteApps
This release note was updated September 16, 2020.
## Following are the 2020.2 taxation enhancements to SuiteApps:
- SuiteTax SuiteApps
- U.S. Sales Tax and Canada GST Now Generally Available
- Canada Data Provisioning Enhancements
- Automatic Tax Calculation for Shipping in VAT Countries
- SuiteTax Reports is now Tax Reporting Framework
- Legacy Tax SuiteApps
- Legacy Tax Support in Tax Reporting Framework
- Support for Norway Standard Audit File for Tax (SAF-T) Financial Report
- International Tax Reports Enhancements
▬ Austria VAT Rate Update
▬ Ireland VAT Rate Update
▬ Saudi Arabia VAT Rate Update
▬ Germany VAT Rate Update
## SuiteTax SuiteApps
Important: The SuiteTax enhancements in this section are applicable only to NetSuite
production and Sandbox accounts where the SuiteTax feature is enabled. For NetSuite accounts
without SuiteTax, see Legacy Tax SuiteApps.
## U.S. Sales Tax and Canada GST Now Generally Available
## SuiteTax is now generally available for NetSuite accounts with U.S. and Canada subsidiaries. This feature
is an addition to the existing International VAT feature, which has been available since October 2019. The
SuiteTax Engine and SuiteTax Data Records SuiteApps provide tax codes, tax rates, and tax calculations
for U.S., Canada and, over 100 VAT countries.
The SuiteTax Engine SuiteApp includes:
- Tax determination based on ZIP +4
- Origin and destination-based taxes
- Intrastate and interstate sales
- Exemption certificate management, covering both blanket and individual certificates and validity dates
- Item taxability rules by state
The SuiteTax Data Records SuiteApp includes:
- Automatic provisioning of tax codes and tax rates for your tax jurisdictions (state, province, county,
city, district)
- Automated monthly tax rate updates for 110 countries
- Tax rate change history for each tax code
You also have the option to use an external tax partner solution in SuiteTax. The SuiteCloud Developer
Network (SDN) partners who can integrate with SuiteTax using an API include Avalara, Sovos, Taxjar,
Thomson Reuters, Vertex, and Wolters Kluwer. To learn more about the SDN partners, see SuiteApp.com.
For more information, see the help topics SuiteTax Engine and Tax Records in SuiteTax.
Contact your Account Manager to find out how you can get access to SuiteTax.
## Canada Data Provisioning Enhancements
## SuiteTax Engine version 2.00.10 provisions tax related data for Canada nexuses. This update supports
specific tax determination rules in Canada, such as Goods and Services Tax (GST), Provincial Sales Tax
(PST)/ Retail Sales Tax (RST)/ Quebec Sales Tax (QST), and Harmonized Sales Tax (HST). The SuiteApp
creates separate tax types, tax codes, and tax agencies for each of these Canada sales taxes. In addition,
the Canada nexus default tax codes and tax groups for all the provinces are adjusted based on the new
data structure.
## Automatic Tax Calculation for Shipping in VAT Countries
SuiteTax Engine version 2.00.10 supports automatic tax calculation for shipping items and shipping
methods in countries with VAT.
This feature uses the same logic used in the automatic tax calculation for goods. For example, if an entity
default tax code or nexus default tax codes apply to the transaction, they also apply to the shipping
method or shipping item.
This feature also uses the standard lookup logic for goods.
## SuiteTax Reports is now Tax Reporting Framework
## SuiteTax Reports SuiteApp changes its name to Tax Reporting Framework. All references to SuiteTax
Reports in the Help Center and SuiteAnswers is changed to Tax Reporting Framework.
If you have the SuiteTax Reports SuiteApp installed in your account, the bundle details are automatically
updated from SuiteTax Reports version 2.00.4 to Tax Reporting Framework version 1.00.0.
For more information about Tax Reporting Framework, see the help topic Tax Reporting Framework.
## Legacy Tax SuiteApps
Important: The legacy tax enhancements in this section are applicable only to NetSuite
accounts without the SuiteTax feature. For NetSuite accounts with SuiteTax, see SuiteTax
SuiteApps.
## Legacy Tax Support in Tax Reporting Framework
In Tax Reporting Framework version 1.00.0, generating country tax reports in Legacy Tax environments is
supported. You can now generate tax reports using the Country Tax Reports page.
For more information, see the help topic Legacy Tax Support in Tax Reporting Framework.
## Support for Norway Standard Audit File for Tax (SAF-T) Financial Report
Tax Audit Files version 1.78.0 includes enhancements for the Audit Files Field Mapping page to support
the Norway Standard Audit File for Tax (SAF-T) financial report.
Starting January 1, 2020, companies with a turnover exceeding 5,000,000 Norwegian Krone are mandated
to comply with the submission of the Norway SAF-T report. The Norway SAF-T financial report is a
standard file format for exporting various types of accounting transactional data in XML format.
The report structure is based on the SAF-T standard format by the Organization for Economic
Cooperation and Development (OECD).
The first version of the Norway SAF-T financial report is comprised of three main sections:
- Header – Shows general information about the company and audit file
- Master Files – Shows information about general ledger account, suppliers, customers, and tax table
- General Ledger Entries – Shows accounting transactions
To successfully generate the Norway SAF-T financial report, you must complete the following tasks:
- Ensure that you are using Tax Audit Files version 1.78.0
- Install the latest versions of the following SuiteApps:
- NetSuite Norway Localization SuiteApp (ID 270800)
- EMEA Localization SuiteApp (ID 303903)
- International Tax Reports SuiteApp (ID 43003)
- Supplementary Tax Calculation SuiteApp (ID 123426)
- Tax Reporting Framework SuiteApp (ID 237699)
- Norway Tax Reports SuiteApp (ID 333158)
- Set the Use Account Numbers preference on the Accounting Preferences page
- Enable the Multiple Currencies feature on the Enable Features page
Note: When EMEA Localization SuiteApp is installed, ensure that the Registration Number on the
subsidiary record is provided. You must review the related configuration and mandatory fields for
the Norway SAF-T financial report explained in Norway Standard Audit File for Tax (SAF-T) Financial.
The Account Files Field Mapping page is also updated to support the following account and tax codes
mapping categories for the Norway SAF-T financial report:
- NO-SAFT: 2 Digit Standard Accounts
- NO-SAFT: 4 Digit Standard Accounts
- NO-SAFT: Income Statement RF-1167
- NO-SAFT: Income Statement RF-1175
- NO-SAFT: Income Statement RF-1323
- NO-SAFT: Standard Tax Codes
To learn more, see the help topic Norway Standard Audit File for Tax (SAF-T) Financial.
International Tax Reports Enhancements
## Austria VAT Rate Update
## International Tax Reports version 3.117.0 includes automatic provisioning of reduced rate tax codes for
newly created Austria subsidiaries and nexuses. These new tax codes are effective from July 1, 2020 until
## December 31, 2020:
## Tax Code Description Tax Properties
R3-AT Reduced Rate at 5% according to Section 28 Abs. 52 Z 1 from July ■ Rate of 5%
1, 2020 – December 31, 2020
## Tax Code Description Tax Properties
- Reduced Rate
- Available on both Sales and
## Purchases
ER3-AT EC sales and purchases (goods) - reduced rate at 5% according to ■ Rate of 0%
## Section 28 Abs. 52 Z 1 from July 1, 2020 – December 31, 2020
- EC Code
- Reduced Rate
- Available on both Sales and
## Purchases
- Notional Rate Derived from R3-
## AT (5%)
The Austria VAT report will be updated to properly report R3-AT and ER3-AT tax codes in the following
boxes, respectively:
## Box Description Reported Tax Code
009 Sales at 5% according to § 28 Abs. 52 Z 1 from July 1, 2020 until December R3–AT
31, 2020
010 5% according to § 28 Abs. 52 Z 1 from July 1, 2020 until December 31, ER3-AT
2020
To learn more about the new tax codes and Austria VAT form update, see the help topics Tax Code Table
for Austria and What goes into each box - Austria VAT report.
## Ireland VAT Rate Update
International Tax Reports 3.117.0 supports Ireland’s temporary reduction of standard VAT rates due to
COVID-19 effective from September 1, 2020 until February 28, 2021.
## Automatic Provisioning of Temporary Tax Codes
The update includes automatic provisioning of the following tax codes for newly created Ireland
subsidiaries or nexuses:
## Tax Code Description Tax Properties
S1-IE Standard Rate at 21% from September 1, 2020 to February 28, ■ Rate of 21%
2021
- Available on both Sales and
## Purchases
RC1-IE Reverse charge sales in country from September 1, 2020 until ■ Rate of 0%
## February 28, 2021
- Reverse Charge Code
- Notional Rate Derived from S1-IE
(21%)
- Available on both Sales and
## Purchases
I1-IE Purchase of goods from outside of EC from September 1, ■ Rate of 21%
2020 until February 28, 2021
- Import
- Available on both Sales and
## Purchases
## Tax Code Description Tax Properties
IS1-IE Purchase of services from outside of EC from September 1, ■ Rate of 0%
2020 until February 28, 2021
- Reverse Charge Code
- Notional Rate Derived from S1-IE
(21%)
- Applies to Service Items, Import
- Available on both Sales and
## Purchases
ES1-IE EC sales/purchases to another EC country (goods) from ■ Rate of 0%
## September 1, 2020 until February 28, 2021
- EC Code
- Notional Rate Derived from S1-IE
(21%)
- Available on both Sales and
## Purchases
ESSP1-IE EC purchases (services) from outside of EC from September 1, ■ Rate of 0%
2020 until February 28, 2021
- EC Code
- Reverse Charge Code
Note: This tax code is applicable to intra-
community purchase transaction. ■ Notional Rate Derived from S1-IE
(21%)
- Applies to Service Items, Available
on both Sales and Purchases
ESS1-IE EC sales (services) from outside of EC from September 1, 2020 ■ Rate of 0%
until February 28, 2021
- EC Code
- Notional Rate Derived from S1-IE
Note: This tax code is applicable to intra-
(21%)
community sales transaction.
- Applies to Service Items
- Available on both Sales and
## Purchases
The Ireland VAT3 form is also updated to properly report the new tax rates in the appropriate boxes.
To learn more about Ireland’s COVID-19 tax response and VAT3 form updates, see the help topics
Temporary Tax Codes for Ireland COVID-19 Tax Response and What goes into each box - Ireland VAT 3
report.
## Saudi Arabia VAT Rate Update
International Tax Reports version 3.116.0 includes automatic provisioning of tax codes for newly created
Saudi Arabia subsidiaries and nexuses with the following properties:
Tax Code Description Tax Properties
## S-KSA Standard Rate - Domestic ■ 15% Rate
- Available on both Sales and Purchases
Tax Code Description Tax Properties
## IMG-KSA Standard Rate - Imports (Goods) ■ 15% Rate
- Available on Purchase transactions
## IMS-KSA Standard Rate - Imports (Services) ■ 0% Rate
- Available on Purchase transactions
- Reverse Charge Code
- Notional Rate Derived from IMG-KSA (15%)
- Applies to Service Items
## RCP-KSA Reverse Charge - Purchases ■ 0% Rate
- Available on Purchase transactions
- Reverse Charge Code
- Notional Rate Derived from S-KSA (15%)
- Applies to Service Items
To learn more, see the help topic Tax Code Table for Saudi Arabia.
## Germany VAT Rate Update
## International Tax Reports version 3.116.0 supports the temporary reduction of Germany tax rates due to
COVID-19. This tax rate update is applicable to Standard VAT Rate (16%) and Reduced VAT Rate (5%) from
July 1, 2020 until December 31, 2020.
## Automatic Provisioning of Temporary Tax Codes
The update includes automatic provisioning of tax codes for newly created Germany subsidiaries or
nexuses with the following properties:
## Tax Code Description Tax Properties
## S2-DE Standard Rate from July 1, 2020 until December 31, 2020 ■ 16% Rate
- Available on both Sales and
## Purchases
## R1-DE Reduced Rate from July 1, 2020 until December 31, 2020 ■ 5% Rate
- Reduced Rate
- Available on both Sales and
## Purchases
ES1-DE EC Sales/Purchases to another EC country (Goods) - Standard ■ 0% Rate
## Rate from July 1, 2020 until December 31, 2020
- EC Code
- Notional Rate Derived from S2-DE
(16%)
- Available on both Sales and
## Purchases
ER1-DE EC Sales/Purchases (Goods and Related Services) - Reduced ■ 0% Rate
## Rate from July 1, 2020 until December 31, 2020
- EC Code
- Notional Rate Derived from R1-DE
(5%)
- Reduced Rate
## Tax Code Description Tax Properties
- Available on both Sales and
## Purchases
ESSP1-DE EC Purchases (Services) from July 1, 2020 until December 31, ■ 0% Rate
2020
- EC Code
- Reverse Charge
- Applies to Service Items
- Notional Rate Derived from S2-DE
(16%)
- Available on both Sales and
## Purchases
## ESSS1-DE EC Sales (Services) from July 1, 2020 until December 31, 2020 ■ 0% Rate
- EC Code
- Applies to Service Items
- Notional Rate Derived from S2-DE
(16%)
- Available on both Sales and
## Purchases
SS1-DE Applicable for Mobile Devices from July 1, 2020 until December ■ 0% Rate
31, 2020
- Reverse Charge
- Notional Rate Derived from S2-DE
(16%)
- Available on both Sales and
## Purchases
## RC1-DE Reverse Charge from July 1, 2020 until December 31, 2020 ■ 0% Rate
- Reverse Charge
- Notional Rate Derived from S2-DE
(16%)
- Available on both Sales and
## Purchases
IS1-DE Purchases of Services from outside EU from July 1, 2020 until ■ 0% Rate
## December 31, 2020
- Reverse Charge
- Notional Rate Derived from S2-DE
(16%)
- Applies to Service Items
- Import
- Available on both Sales and
## Purchases
For more details, see the help topic Germany COVID-19 Tax Response: Temporary Tax Codes.
The tax codes will be reported in the following boxes of Germany Monthly/Quarterly VAT Return:
## Box Description Reported Tax Codes
41 Sales of goods and services transactions within the EU Sales Net Amount of ES1-DE, ER1-DE
35 Sales which are subject to other VAT rates Sales Net Amount of S2-DE, R1-DE
## Box Description Reported Tax Codes
36 Sales which are subject to other VAT rates Sales Tax Amount of S2-DE, R1-DE
95 Intra-community aquisitions, which are subject to other VAT rates Purchases Net Amount of ES1-DE, ER1-DE
98 Intra-community aquisitions, which are subject to other VAT rates Purchases Notional Tax Amount of ES1-
## DE, ER1-DE
60 Taxable sales, where recipient is liable for tax payment Sales Net Amount of SS1-DE, RC1-DE
21 Net amount of sales of services within the EU Sales Net Amount of ESSS1-DE
46 Net amount of purchases of services within the EU Purchases Net Amount of ESSP1-DE
47 VAT of purchases of services with standard notional rate within Purchases Notional Amount of ESSP1-DE
the EU
84 Other services (§ 13b para 2 No. 1, 2, 4 to 11 UStG) Purchases Net Amount of SS1-DE, RC1-
## DE, IS1-DE
85 Tax amount of other services (§ 13b para 2 No. 1, 2, 4 to 11 UStG) Purchases Notional Amount of SS1-
## DE, RC1-DE, IS1-DE
66 Purchase VAT on invoices from other businesses, from services Purchases Tax Amount of S2-DE, R1-DE
provided and from intra-community triangulations
61 Notional tax amount of purchases within the EU Purchases Notional Amount of ES1-
## DE, ER1-DE
67 Input VAT from supplies subject to reverse charge Purchases Notional Amount of ESSP1-
## DE, IS1-DE, RC1-DE, SS1-DE
To learn more about the details of the VAT form, see the help topic What goes into each box - Germany
Monthly/Quarterly VAT report.
## Vendors, Purchasing, and Receiving SuiteApps
Following is the 2020.2 vendors, purchasing, and receiving enhancement to SuiteApps:
## SuiteApprovals Support for Vendor Bills
In SuiteApprovals SuiteApp version 5.01.00, approvers of vendor bills can access records using a
customized Employee Center role.
- Administrators must customize the Employee Center role to allow approvers to use this capability.
- Customize the Employee Center role to set the Bill permission to View.
- Assign the customized Employee Center role to vendor bill approvers.
- The SuiteApprovals portlet is accessible from the Personalize Dashboard palette.
When logged in using the customized Employee Center role, the vendor bill approver can add to the
dashboard the SuiteApprovals | Records for Approval portlet.
- The SuiteApprovals portlet displays the number of vendor bills for approval, and the link to the page
listing the records.
Approvers must still access each vendor bill record to approve or reject the transaction.
For more information, see the help topic SuiteApprovals Version 6.00.0.
Wholesale Distribution SuiteApps
Following is the 2020.2 wholesale distribution enhancements to SuiteApps:
## Bill of Lading
A bill of lading is a document that primarily serves as a legally binding agreement between the carrier and
shipper or freight owner. It helps the carrier process the cargo according to the original contract. A bill of
lading is presented to the carrier, outlining the individual shipping orders included in a shipment.
The Bill of Lading SuiteApp provides a simplified interface to print the Bill of Lading document for selected
item fulfillments. With this SuiteApp, you can:
- Search for item fulfillments using different filters.
- Select desired item fulfillments.
- Generate PDF files containing standalone bill of lading, master bill of lading, or both.
- Save bill of lading PDF files to file cabinet.
- Print bill of lading directly from the Item Fulfillment page.
- Select default templates or customized templates for generating standalone as well as master bill of
lading.
- Manage bill of lading preferences.
## Following are the SuiteApp details:
- Bundle Name: Bill of Lading
- Bundle ID: 312584
- Version number: 1.00.0
- Availability: Public
For more information, see the help topic Bill of Lading.