Sage 100 - Integration Features and Requirements

Integration Requirements

Multiple Entities 

A Sage 100 company includes a single entity. Accordingly, a multi-entity Sage 100 customer would need multiple Martus instances. 

Dimension Setup and the Sage 100 Segmented Account 

Martus dimensionalizes the segmented Sage 100 account, naturalizing the GL account segment and treating the remaining segments as dimensions. At the time of implementation, Martus works with the customer/partner to configure the dimension(s) that are important to budgeting and reporting. 

Integration Features

Current Features 

• Sync accounts and dimensions from Sage 100 – each weeknight via AutoUpdate and ad hoc. 
• Sync GL transactions from Sage 100 each weeknight; per standard Martus functionality, the nightly sync (AutoUpdate) updates the current and previous two full months. Ad hoc sync is available to allow the customer to sync any desired range of months. 
• Drilldown in Martus from standard financial summary reports to see transaction details. 
• Export of budget from Martus in a format optimized for import into Sage 100. 
• Support for statistical accounts (based on the non-financial accounts in Sage 100).
• Integration with both the ProvideX and SQL Server database versions of Sage 100.
• Pull existing budgets from Sage 100 (use of this feature is limited to Martus staffers only; this is usually done at the time of implementation and does not need to be done again).

Potential Future Features

• Display vendor/customer name on Transaction Detail

Unavailable Features - Not Supported by the Capabilities of Sage 100

• Display of attachments associated with transaction detail 
• Download budget directly from Martus into Sage 100 
• Multi-currency support 

Description of the Integration 

Update requests are generated in the Martus application by such activities as the nightly Auto Update or an ad hoc sync request. These requests are stored in the Martus cloud.

The Martus EZ Connector for Sage 100 is an additional application provided by Martus that is installed on the Sage 100 Server. 

• For the Standard and Advanced versions of Sage 100, the EZ Connector makes an ODBC connection to the Sage 100 ProvideX database. 
• For the Premium version of Sage 100, the EZ Connector makes a direction connection to the Sage 100 SQL Server database. 

The EZ Connector periodically calls the Martus cloud to see if there are any pending requests, responds to those requests by querying Sage 100, and returns the results to the Martus cloud. The Martus application then updates the Martus database with those results.

Implementation and Upgrades for the Martus EZ Connector for Sage 100 

At the time of implementation, it is the customer/partner responsibility to install and configure the EZ Connector on the server where Sage 100 is installed. In case of updates to this connector, the customer/partner is responsible for installing the updated version provided by Martus and (when necessary) updating any configuration settings within the Martus EZ Connector.

Sage 100 - Integration Setup

Step 1: Ensure all Descriptions on Accounts & Sub Accounts are Filled Out in Sage 100

Martus uses the 'descriptions' on the Sub-Account as the Name in Martus. 

If there is no description when syncing, the Sub Account Code will populate as the name.

1. Click General Ledger > Sub Account Maintenance
2. Select the segment dropdown to review  
3. Click the magnifying glass to review the list of sub accounts
4. We recommend identifying sub Accounts that are missing the 'description' and having a description filled out
   1. Click into each record that does not have description and add a description. Short Description can be added as well but not necessary
5. Click 'Accept' 

Step 2: Setup a Martus User in Sage 100 (Provide X Only)

1. Log into Sage 100
2. Go to the Modules > Library Master
3. Click 'Security'
4. Click 'User Maintenance' 
5. Fill out following fields to create a new user
   1. User Login = MartusUser
   2. First Name = Martus
   3. Last name = User
   4. User Code = MU
   5. Password & Confirm password
   6. Select Company
   7. Select Role = Default
6. Click 'Accept'
7. Keep this login information ready as you will need it to set up Martus EZ Connector 

Step 3: Add Company Code To Martus & Download Martus EZ Connector & MEC File

A Martus admin will need to log into Martus to complete these steps

1. Log into Martus
2. Go to Setup > Sage 100
3. Add Company Code
4. Click 'Save'
5. Click 'Download MEC'
6. Click 'Martus EZ Connector Installer'

Step 4: Install Martus EZ Connector

We recommend installing the Martus EZ Connector on the same server where Sage 100 is stored

1. Install EZConnector from the downloaded file
2. Select 'Windows Service' when prompted
3. Click 'Next'
4. Save in the appropriate location
   1. We recommend installing the Martus EZ Connector on the same server where Sage 100 is stored
5. Click 'Install'

Step 5: Save the MEC File

This MEC File must be saved in the 'Martus.Connector' folder that was just created on the server

1. Move the MEC file into the 'Martus.Connector' folder

Step 6: Launch Martus EZ Connector and Open 'Connection Info' tab

1. Open the Martus EZConnector
2. Click on the name of your Sage 100 company and the Connection Info Tab will appear
3. Click the 'Connection Info' 

Step 7 - Provide X: Fill Out 'Connection Info' Tab 

1. Select Mas 90 ODBC Driver
2. Click on Auto Detect (Connection String will be filled in.)
3. Fill out User Name (MartusUser)
4. Fill out password (from the User that was just created in Sage 100)
5. Click 'Save'

Step 7 - SQL Server Connection 

1. Select SQL Server Drive
2. Fill in Server Name

   Note - Server Name - SQL Server, Server Name or IP Address

3. Choose Authentication
   Authentication - Normally SQL Server (User Name and Password). Windows Authentication is included.

   

4. Fill in Database Name (MAS_ABX)
   Database Name - Sage 100 Company database name.
   
   Note - Skip to step 7 if you are using Windows Authentication.
   
5. Fill in User (from SQL Server User)
6. Fill in Password (from SQL Server user)
7. Click Save
   

Step 8: Test Your Connector

1. Click on the 'Connections' tab
2. Click 'Test'
3. Prompt should pop up letting you know that it passed
4. Auto Run will automatically check please do not uncheck it
5. Connection is now ready!