Oracle NetSuite

Prerequisites

• Oracle NetSuite account

• Allowed access to all Account permissions options

• Realm (Account ID)

• Consumer Key

• Consumer Secret

• Token ID

• Token Secret

Setup guide

Step 1: Create NetSuite account

1. Create account on Oracle NetSuite

2. Confirm your Email

Step 2: Setup NetSuite account

Step 2.1: Obtain Realm info

1. Login into your NetSuite account

2. Go to Setup » Company » Company Information

3. Copy your Account ID (Realm). It should look like 1234567 for the Production env. or 1234567_SB2 - for a Sandbox

Step 2.2: Enable features

1. Go to Setup » Company » Enable Features

2. Click on SuiteCloud tab

3. Scroll down to SuiteScript section

4. Enable checkbox for CLIENT SUITESCRIPT and SERVER SUITESCRIPT

5. Scroll down to Manage Authentication section

6. Enable checkbox TOKEN-BASED AUTHENTICATION

7. Scroll down to SuiteTalk (Web Services)

8. Enable checkbox REST WEB SERVISES

9. Save the changes

Step 2.3: Create Integration (obtain Consumer Key and Consumer Secret)

1. Go to Setup » Integration » Manage Integrations » New

2. Fill the Name field (we recommend to put revos-rest-integration for a name)

3. Make sure the State is enabled

4. Enable checkbox Token-Based Authentication in Authentication section

5. Save changes

6. After that, Consumer Key and Consumer Secret will be showed once (copy them to the safe place)

Step 2.4: Setup Role

1. Go to Setup » Users/Roles » Manage Roles » New

2. Fill the Name field (we recommend to put revos-integration-role for a name)

3. Scroll down to Permissions tab

4. (REQUIRED) Click on Transactions and manually add all the dropdown entities with either full or view access level. For more information see FAQ section below.

5. (REQUIRED) Click on Reports and manually add all the dropdown entities with either full or view access level. For more information see FAQ section below.

6. (REQUIRED) Click on Lists and manually add all the dropdown entities with either full or view access level. For more information see FAQ section below.

7. (REQUIRED) Click on Setup and manually add all the dropdown entities with either full or view access level. For more information see FAQ section below.

• Make sure you've done all REQUIRED steps correctly, to avoid sync issues in the future, for more information see FAQ section below.

• Please edit these params again when you rename or customise any Object in Netsuite for revos-integration-role to reflect such changes.

Step 2.5: Setup User

1. Go to Setup » Users/Roles » Manage Users

2. In column Name click on the user’s name you want to give access to the revos-integration-role

3. Then click on Edit button under the user’s name

4. Scroll down to Access tab at the bottom

5. Select from dropdown list the revos-integration-role role which you created in step 2.4

6. Save changes

Step 2.6: Create Access Token for role

1. Go to Setup » Users/Roles » Access Tokens » New

2. Select an Application Name

3. Under User select the user you assigned the revos-integration-role in the step 2.4

4. Inside Role select the one you gave to the user in the step 2.5

5. Under Token Name you can give a descriptive name to the Token you are creating (we recommend to put revos-rest-integration-token for a name)

6. Save changes

7. After that, Token ID and Token Secret will be showed once (copy them to the safe place)

Step 3: Set up the credentials

• Realm (Account ID)

• Consumer Key

• Consumer Secret

• Token ID

• Token Secret Also you have properly Configured Account with Correct Permissions and Access Token for User and Role you've created early.

• As a start date you can use 2024-01-01T00:00:00Z

Frequently Asked Questions

Can I limit access to specific data my NetSuite account?

1. Create a Role with Restricted Permissions: When you create a new role (e.g., revos-integration-role), you can control which data and areas the user can access by setting specific permissions. Instead of giving the user full access to every aspect of NetSuite, you can granularly manage permissions.
• Transactions Tab: You can restrict access to specific transaction types like Sales Orders, Purchase Orders, Invoices, etc. by only adding the required entities to the role.
• Reports Tab: Limit access to specific reports by selecting only the necessary reports or providing view access rather than full access.
• Lists Tab: Control which lists the user can view or modify, such as customer data, items, vendors, etc.
• Setup Tab: Only grant permissions for specific setup-related tasks if necessary. You can withhold access to high-level admin functions that are not relevant to the user.

2. Fine-Tune Access Levels: Each permission you grant can have different access levels:
• View: The user can only view the data but not make any changes.
• Create: The user can create new records but cannot modify existing records.
• Edit: The user can edit existing records but may not have access to delete or create.
• Full: The user has full control over the data, including viewing, editing, creating, and deleting records.

3. Custom Record Types: If you have custom record types or fields, ensure that you only grant access to those custom records that are necessary. This way, the user won’t see or modify any custom data that they are not authorized to access.

4. Restrict Access to Specific Subsidiaries or Departments: If you use subsidiaries or departments in NetSuite, you can restrict a role's access to only data related to specific subsidiaries or departments. This can be particularly helpful in large organizations where certain users should only have access to a particular segment of the business.
• Subsidiary Restrictions: This can be done under the Subsidiary Restrictions tab when editing a role, which limits the data visibility to a particular subsidiary.
• Department/Location Restrictions: You can also apply restrictions based on departments, locations, or classes.

5. Limit SuiteScript and SuiteTalk Access: When setting up integration roles, ensure that you only grant access to the specific script or integration endpoint. This is important when you are using SuiteScript or REST APIs to pull data, as you don’t want the user to have broader access than needed.

6. Monitor Role Usage: After setting up the restricted role, it’s important to monitor the usage. You can regularly check role-based access logs to ensure that the user is only accessing the areas you intended.

• In the Transactions Tab, add Sales Order with View or Edit permissions.

• In the Lists Tab, add Customer with View permissions.

• Do not add permissions for other transaction types, such as invoices or purchase orders, so that the user won’t be able to access or modify these areas.