Sage 300 - Integration Features and Requirements

Integration Requirements

Listed below are the requirements for integration with Martus via the Sage 300 API. 

• WebScreens must be enabled within Sage 300 and the URL provided to Martus. 
• The Sage 300 company ID must be provided to Martus.   
• The Martus IP addresses listed in the Guide to Support Tools must be whitelisted.

Integration Features

Current Features

• Sync accounts and dimensions from Sage 300 each weeknight via AutoUpdate and ad hoc.

• Sync GL transactions from Sage 300 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 300. 
• Martus' Cash Flow Forecasting is available for Sage 300 integrations at the Premium subscription level.
• Martus honors 12 reporting periods for Sage 300. 
• Martus will recognize any Adjustment entries posted in period 14 on the Transaction Report honoring the date they were posted and closing entries, transactions posted in period 15, will not be included in Martus.
  
  

Dimension Support

As with any Martus configuration, the Implementation Consultant works with the customer to identify the dimensions that are important to budgeting and reporting. (GL accounts are not considered dimensions within Martus.)  

Martus can support whatever segments Sage 300 uses up to the Martus maximum of 8 dimensions.  Account mapping can vary with segment order. A line dimension in Martus must be reserved for Sage 300 account mapping.

Features Not Yet Supported

• Pull a budget from Sage 300 into Martus
• Push a budget from Martus to Sage 300
• Syncing of balance sheet accounts, along with the standard Balance Sheet and Cash Flow Forecast reports
• Multicurrency
• Multi-entity & Consolidation

Unavailable Features - Not Supported by the Capabilities of Sage 300

• Display of attachments associated with transaction detail
• Display of Vendor Name column in transaction detail
• Statistical accounts

Other Notes

• Optional fields in Sage 300 cannot be supported as dimensions within Martus 
• Martus also provides a file-based integration with Sage 300

Sage 300 - Integration Setup & Troubleshooting

Review the requirements and complete the steps below to set up the Martus integration with Sage 300.

Requirements

Sage 300 Server

1. Sage 300 Web Screens must be installed and configured on your server.
   • Martus will need the login URL to access the API via WebScreens.
     It typically appears as: https://{{hostname}}/Sage300WebApi
2. Update the web.config file 
   • Typically stored in the \Sage\Sage300\Online\WebAPI folder
   • Open as Administrator in Notepad
   • Update key AllowWebAPIAccessforAdmin = True & Save
   • Restart the Application pools for Sage 300 to ensure the changes take place
3. Sage 300 server must whitelist Martus IP Addresses for access. 
   1. 52.177.126.2 (for all locations)
      
   2. 145.132.8.78 and 48.221.80.17 (US)
   3. 145.191.64.27 (Canada)
   4. 51.56.16.8 (Australia)

4. Ensure all applicable security standards have been met. (ex. URL - 'https' vs 'http')

5. IIS (Internet Information Services) may need to be present (unknown at this time if this is a requirement).

Sage 300

The user in Martus who is going to make the connection to Sage 300 must be an Admin-level user in Sage 300. 

Steps to Set Up Sage 300 in Martus

1. In Martus, go to Setup > Sage 300.
2. Enter the Database ID from Sage 300 into the Company Id
   1. This is found on the 
3. Enter the User ID from Sage 300.
4. Enter the User Password from Sage 300.
5. Enter the Base URL(used for accessing Web Screens).
   • It typically appears as: https://{{hostname}}/Sage300WebApi
6. Click Save.
   
   
   
   
7. Click Verify Permissions to check the connection. 
8. The last step will be to configure dimensions in Martus. Please connect with Martus Support to determine the ideal dimension setup.
   • In Sage 300, navigate to General Ledger > G/L Setup > Options > Segments tab and screenshot your Sage 300 segments to provide to Martus Support.

Troubleshooting a Failed Connection

Verify Permissions is unsuccessful

1. (Admin) Check the user name & password
2. (IT) The connection may also need to include the port if the connection doesn’t work initially:

https://{{{hostname:port}}}/Sage300WebApi