Sage Intacct

Introduction

The Templates installation provides you with a ready-to-use set of Views, Dashboards and Reports.

The installation (assuming the Central Point is freshly installed and empty), will consist of two steps:

• Configuring the Data Sources for the ERP and Data Warehouse (optional) databases.
• Importing the Templates into the Central Point.

There may be other steps including building and loading the OLAP Cubes.

SEI DataSync

Sage Intacct's data is only accessible from a Cloud platform, so it must be used in conjunction with DataSync.

Prerequisites

• A Sage Intacct production environment
• A destination environment (Cloud or On Premise)
• A valid version of DataSync (refer to Installing DataSync for more information)

Set the Connections

Configuration in Sage Intacct

This section helps you configure the integration of Sage Intacct with DataSync so that they can communicate with each other.

1. In the upper bar, click on the Company category and select Subscriptions located under the Admin tab.
   
2. In the list, find Web Services and drag the slider to enable it. Ignore the warning about additional charges.
   
3. In the upper bar, click on Overview located in the Company tab.
   
   
4. In the Company page, under the Setup section, click on Company Information.
   
5. Go to the Security tab and click on Edit.
   
6. Under the Sign-in settings drop-down menu, in the Password section, click on the pencil located under the IP Filter field.
   
7. In the Username field, enter the Company ID provided by Sage (the one you used to login).
8. In the IP Address Filter Information window, click on Add.
   
9. In the next window, in the Username field, select the User ID you used to log in.
10. In the Start IP Address and End IP Address fields, enter the IP address provided by the Nectari team and click on Save.
    
11. Once your User Name is in the list, you can close the IP Address Filter Information window.
12. Back to the Company Information window, scroll down to the Web Services authorizations drop-down menu and click on Add.
    
13. In the Sender ID field, enter NectariMPP and click on Save.
    

Creating a Role for the User

Before creating a User, you need first to create a Role so that the User can send API requests in DataSync.

1. In the upper bar, click on Roles located in the Company tab.
   
2. In the Roles page, click on Add.
   
3. In the Name field, enter Nectari and click on Save.
   
4. In the Roles Subscription page, tick the Application / Module checkbox and click on the Permissions hyperlink.
   
5. In the Permissions window, click on Read-Only, then on Save.
   
   

6. Once this is done, click on Save.
   

Creating a User

After creating the Role, you can now create the User that will be used to authenticate the connection between DataSync and Sage Intacct.

1. In the upper bar, click on Web Services users, located in the Company tab.
   
   
2. In the Web Services Users page, click on Add.
   
3. Fill in the User ID, Last Name, First Name and Email fields.
4. Under the User Type section, select Business.
5. Under the Admin Privileges section, select Full.
   

6. Once this is done, click on the Role Information tab.
7. Click on one of the lines and select Nectari in the Role Name drop-down list.
   
8. Click on Save and on OK in the pop-up window.
9. In the Password window, enter the password you used to log in your Sage Account and click on Done.

Configuration of Sage Intacct is now complete, so you can now proceed with DataSync connection settings.

Settings in DataSync

1. In DataSync, create a new Source Connection.
2. In the list, select Sage Intacct.
3. In the Connection Properties window:
   1. In the Description field, enter a name for this connection.
   2. Paste this URL address https://api.intacct.com/ia/xml/xmlgw.phtml into the URL field.
      
   3. For the User ID, Password and Company ID fields, enter the credentials you received in the email from Sage Intacct.
   4. Once these fields are filled in, change the other settings (Tracking type etc.) according to your preferences.
      
   5. Click on Save to finish.

Importing the Extractions

This feature allows you to import a pre-defined template or to restore a backup that you may have done yourself with the Export feature (refer to Export an Extraction for more details).

Some pre-defined templates are already available; if you don't have access to them, please contact your partner. An example of a pre-defined template you could use is the one which defines the list of tables and fields to be synchronized to send Sage 300, X3, Acumatica, Salesforce data to the Cloud.

1. Click on one of the extractions in the list then on the Import icon located on the upper right-hand corner.
   
2. In the Import Extraction window, click on the Choose a zip file hyperlink to browse to the location you saved the export .zip file or drag it directly into that window and click on Next.

3. On the left pane, select the type of extraction you want to perform and click on Next.
   

4. Refer to Setup the Extraction Panel to define the extraction and click on Import to finish the process.
   

5. You should have a result similar to this:

 

Validating and Building the Extractions

Once your extraction (source, destination connection and their related tables) is set up, the next step is to validate the setting of an extraction, before being able to run it.

The feature will:

• Ensure that all the tables/fields exist in the source connections,
• Validate all SQL queries or calculated fields,
• Ensure that the data integrity in the destination connection is not affected (ex: change the table structure).

To do so:

1. Select the extraction you want to validate and build in the list and click on the Validate and Build icon.
   
2. In the new window, choose the action which best fits your needs and click on Build (Validate for Migration and Export extraction types).
   

3. Wait for the process to be done.

Running the Extractions

Once your data have been validated (refer to Validate and Build an Extraction for more details), you can manually run the extraction if you want an immediate result instead of scheduling it.

1. Select the extraction you want to run in the list and click on the Run Extraction Now icon.
   
2. In the upper-right hand corner, choose the action you want to execute and the table(s) then click on Run.

3. Wait for the process to be done.

Data Source Configuration

Environments and Data Sources

The following information is needed to configure the Data Sources:

• Database server credentials: Server name, Instance, Authentication strategy.
• Main ERP database information: Database and schema name.

ERP Data Source

1. In the upper-right hand corner, click on the to access the Administration section.
   
2. On the left pane, select Env. & Data Sources.
3. By default, there is already an environment called Production, which you can rename by double-clicking in the name box. Once changed, press the Enter key.
   
4. In the Data Sources section, click on Add to create the first Data Source.
   
5. Complete the ERP Data Source configuration. See instructions for MS SQL Server below.

Datasource description:

Type:

SQLSERVER

Server:

Database server of Sage Intacct

Database name:

Name of the Sage Intacct database (beware of the case sensitivity)

Database schema name:

SEI schema:

Enter the chosen SEI custom schema for the current environment

Authentication stategy:

UseSpecific

User Name:

SQL User accessing the Sage Intacct database. For example, sa.

Password:

The user's password.

6. Click on Validate then on Save to complete the configuration of the Data Source.

Importing Templates

For each environment, the following previously configured information will be required:

• ERP Database Name
• SEI Custom Schema
• ERP Schema

Download the Template file: TPL_9.5.XXX_SageIntacct.zip.

The X represents the build number of the template (use the highest available).

Running the Import Template

1. In the upper-right hand corner, click on the to access the Administration section.
   
2. In the Administration section, click on the Templates drop-down menu in the left pane.
3. Select Import Template.
4. Choose the specific location where the new templates will be installed and click on Next.
   
   Note

   Usually, the Root folder is used.

5. In the Import Template window, click on Select files....
   
6. Find the folder where you saved the Template.zip file in order to select it then click on Open.
7. In the Data Sources Mapping screen, associate the Data Sources (ERP) listed in the Received Data Sources Description column (those from the template) with the Data Sources you previously defined in the Central Point (listed in the Current Data Sources Description column)
• In the Received Data Sources Description column, ensure that only the Data Sources checkboxes you want to use from the template are ticked off.
• In the Current Data Sources Description column, click on Bind a Data Source to access the drop-down list containing the existing Data Sources and click on Next.
  

In the next screen all of the Templates content is displayed, against what the Central Point already has.

By default, on the first install, everything will be set to Add (leave everything by default) .

• In the case of a first installation, the first four columns will display None and Never Installed, the next three will detail the Template content, and the last three gives you the choice to Add, Update or Skip during the installation.
  Note

  In the case of an update, you can refer to Updating template for more details.

1. Click on Next (this can take time).
   

2. Once this has been completed, a window will be prompted to input the necessary parameters to create the custom objects.
3. If more than one Environment have been created, you will see a column per Environment. You can untick an Environment checkbox, in which case the Global Scripts will not run in it.

4. Complete the parameters, see examples below, and click on Next.
   

5. After importing, an Execution Report will be produced, as shown below.
   Note

   The first section is for the ERP Data Source and the one below it is for the Cube Data Source.

   You can click on the button to see the details of each script individually. If no failures are reported, close the window.

6. If any of the scripts failed to run, a fail icon will be displayed. Click on the fail symbol to view the Report Preview window, which shows the respective SQL script.
   

• Copy this script, debug, and run it separately if needed. Users who are proficient with SQL can debug it straight in the Report Preview window and run it by clicking on the Try to rerun button.
  

Updating template

When performing an upgrade of the SEI software, it will only update the software and not the template. In other words, the existing SEI Data Models and Views won't be affected.

To update a template:

1. After having mapped the Data sources, tick the checkboxes of the objects you want to upgrade and click on Next.
   
   Note

   By default, no checkbox in the Update column will be ticked. If there is a new Data Model / View the Add checkbox will be ticked. Select Skip if you want to ignore it.

   Important

   If you tick the Update checkbox, it will overwrite the existing SEI objects associated with that Data Model or connected to the others (dependencies). Please note that if any customizations have been done, they will be lost.

2. Select the environment in which the scripts will be executed and click on Next.
3. Complete the parameters and click on Next.
4. In the Execution report window, If any of the scripts failed to run, a fail icon will be displayed. Click on the fail symbol to view the Report Preview window, which shows the respective SQL script.
5. Copy this script, debug, and run it separately if needed. Users who are proficient with SQL can debug it straight in the Report Preview window and run it by clicking on the Try to rerun button.
   

Important

Web Browsers have updated their policy regarding Cookies and these changes must be applied to your Web Client if you want SEI embedded into your ERP website, or use Single Sign-On (SSO). Refer to Cookie Management for more details.