Oracle NetSuite Environment

Prerequisites

To ensure a functional integration, the Oracle NetSuite environment configuration requires that you enable the features below

  • Accounting preferences: Use Account Numbers;
  • Accounting preferences: Approval routing for Journal entries;
  • Define accounting period;
  • Enable SuiteCloud features (OAuth 1.0 + SuiteScript);

Authentication Credentials

  • Obtaining credentials for OAuth 1.0
    • Create an integration record in order to obtain the client credentials required for OAuth 1.0 (Consumer Key and Consumer Secret)
    • Create a dedicated role to allow RESTlet permissions on the integration record.
    • Create a user and assign the previously created role.
    • Create an access token in order to obtain the token credentials for OAuth 1.0 (Token Id and Token Secret). The creation of an access token is conditioned by the existence of: an integration record, a role, an user.

Please note:
  Since the Consumer Key and the Consumer Secret are only displayed once, take note of them, as they will be used later. These credentials will be needed in the AWS Lambda function for computing the OAuth 1.0 digital signature.

Client Credentials

  The Token Id and the Token Secret are also only displayed once, take note of them, as they will be used later. These credentials will be needed in the AWS Lambda function for computing the OAuth 1.0 digital signature.

Token Credentials

Custom Records and Fields

  • Create a custom record
    A custom record is a container where the structures sent from MPO will be listed. Its creation is necessary in order to monitor all the requests sent through the RESTlet.
    The custom record should contain at least the following fields:

    • Input data: where the JSON payload will be saved as string.
    • Journal entry: the NetSuite object where data will actually be posted.
  • Create custom Transaction Line Fields
    The integration offers the option to store additional information for a Journal Line, as custom fields. For each field that is not defined in NetSuite by default, a Transaction Line Field of type String needs to be created.
    ex: Client id, Product id, Transaction type etc.

  • Implement the RESTlet
    The RESTlet script should interact with the following NetSuite entities:

    • Custom record - containing the Data input and the Journal entry object;
    • Booking date (mapped with the NetSuite creation date);
    • Optional transaction line fields (previously defined);
    • Account Number;

Chart of Accounts

The Chart of Accounts provides a complete listing of every account in the accounting system. In Oracle NetSuite, account records can be added manually or by using the CSV import assistant.

Note: After defining the Chart of Accounts in NetSuite, retrieve the internal ID of each Account Number and enter the Id in the description field of the corresponding GL Account in Mambu.

Map Internal ID to GL Account Description

Script Deployment

  1. Navigate to Customization/Scripting/Script Deployments.

Navigate to Script Deployments

  1. Identify the RESTlet script created previously and click on View.

View Script Deployment

  1. Copy the External URL and keep it at hand, this will be needed when setting up the AWS Lambda function in the next step.

RESTlet URL