Connector configurations

Connector authentication

You can enter authentication credentials for NetSuite and Revenue and save the details. The following are the NetSuite authentication details:

• Consumer key & consumer secret  
• Access token details, that is, token ID and token secret
• NetSuite tenant Aaccount ID
• NetSuite tenant API services URL, that is, the NetSuite SuiteTalk API and REST services URL available in the Company URLs tab on the Company Information page

The following are the Revenue authentication details:

• User name 
• Password
• Role & client name
• Revenue Tenant Host URL

Connector email notifications

Click the wheel icon to configure the email notifications. Connector is pre-configured to send email alerts for failure scenarios. You can choose to receive notifications upon successful and warning scenarios. 

Add the email recipients in the Email Configuration window and click Save.

Connector solution instance

Here's an overview of solution instance: 

• Solution instances allow you to include different objects to be pushed from NetSuite to Revenue, such as Orders, Invoices, or Credit Memos. 
• Connector has the flexibility to choose one or more objects and any combination of objects to be pushed from NetSuite and ingest them into Revenue.
• Supports incremental data ingestion.

The purpose of the Solutions Instances tab is to allow you to create a solution instance to select and contain the objects from NetSuite that need to be ingested into Revenue whenever connector is executed.

Inbound Connector for NetSuite supports business critical transactional objects like Sales Orders, Invoices, Credit Memos and custom objects.

To create a solution instance, complete the following steps:

1. In the Solutions Instances tab, click the + icon in the upper-right corner to create a solution instance.
2. Enter the name for the solution instance.
3. Select the list of objects that must be grouped/packaged into the solution instance and toggle on the flag. For example, it could be Orders and Invoices or Only Invoices or Only Orders and all three Objects for the Inbound.
   • In case of Inbound Connector, each object has a toggle to enable, a field name to enter the ERP Object name (NetSuite dataset) and the Revenue Object Name (ZR template name).
4. Click Save to save the solution instance. Or, you can click Cancel to undo the changes that you made.

You can create multiple solution instances.

You can edit the previously created solution instance, with the ability to toggle On / Off the object or change the value in the ERP object name/ Revenue object name (ZR template name).

Connector field mapping

The purpose of this tab is to allow you to map the source and target field for each object of the solution instance that is selected:

1. Select the solution instance from the list of the Solution Instances drop-down.
   • Based on the solution instance selected, the corresponding list of objects selected in the solution instance will be displayed in the Object drop-down menu. 
   • Based on the object selected in Solution Instances, the list of values (LOVs) will be populated for both the Source and Target columns as picklist or drop-down fields.
2. Map the Source and Target fields based on the user or their business flow requirements.
   • The Source and Target columns will change based on the object selected in the solution instance.
3. Save the field mapping. You can edit or delete each of the field mapping.

You can Cancel/Undo the changes that are made in the field mapping to retain the existing/previous mapping as it is.

You can click the Refresh icon to dynamically load the field metadata changes from NetSuite and Revenue.

Connector execution

For connector execution, complete the following steps:

1. On the Execution tab, select the solution instance from the list of Solution Instances drop-down menu.

2. Click the gear icon to open the window to choose the execution mode.

3. For execution mode, select either On-Demand or Scheduled for each solution instance.

4. Click the Run or Schedule button.

   • Choose the desired frequency when the Scheduled mode of execution is selected.

5. Open the Execution link to open the Run details window.

   • Each task in the connector flow will be displayed indicating success or error.

6. Click on the download icon to download the summary log.

Upon completion of execution, you will receive an email notification with an attachment that provides high level details of: 

• Connector execution status
• The object type
• Revenue transaction file template name
• The upload file name
• The number of records ingested into Revenue along with the fields that are mapped per each Object

Validate transactions in Revenue inbound staging 

After a connector is executed, you will receive an email notification with a file containing the following details:

• Connector execution status
• The name of the solution instance datasets
• Revenue template details
• The total number of transactions ingested into Revenue Line staging table   

You can go into Revenue, navigate to the File Transaction upload template, and verify the transactions ingested by the connector by using the Upload File name created by the connector.

You can navigate to the Inbound Transaction Stage UI to verify the transactions.