Sage 300
Sage 300 features
Text trimming. Text is stored using the SQL Server char data type. Any spaces at the end of strings are removed.
Company information. Company data is stored in separate databases and additional companies must be added manually.
Automatic Date column conversion. Date columns are stored as decimal numbers in Sage 300. To work with Data Hub, these columns are automatically converted to dates.
Supported versions of Sage 300
App version | Status | Min Software req. | Support added | Notes |
Cloud | Not tested | Using Gateway only | ||
2020 | Supported | ZAP BI / SDMA v9 | November 9 2019 | |
2019 | Supported | ZAP BI / SDMA v8.1 | September 27 2018 | Supported for v7.4 + for existing Sage 300 solution implementations. (Highly recommended to upgrade to the latest Sage 300 solution using ZAP BI 8.1) |
2018 | Supported | ZAP BI / SDMA v8.1 | September 27 2018 | |
2017 | Supported | ZAP BI / SDMA v7.4 | April 18 2017 | |
2016 | Supported | N/A | ||
2014 | Supported | ZAP BI / SDMA v7.4 | October 2016 | |
2012 | Supported | ZAP BI / SDMA v7.4 | October 2016 |
Supported editions
Standard
Advanced
Premium
Supported modules
Accounting (Actuals, Budget)
A/P & A/R Accounting (Historical, Open)
Inventory ((Historical movement, Valuation)
Sales (Order, Invoice< Delivery)
Procurement (Order, Invoice, Pricing, Delivery)
Solution localization support
English
Model-specific support
Account structure/groups/rollups
Segments
Lists
Optional fields (Customer, Vendor, Product)
Address geocoding
Historical currency conversions
Connecting to the data source
The following connection settings need to be defined for a Sage 300-based data source:
Server - The name of the SQL Server instance hosting the Sage 300 database you want to access. Just the server name may be entered if there is only one SQL Server instance on that server. If the server hosts multiple instances, use the syntax ServerName\InstanceName. You can type in the instance name directly, or choose from a list of instances on your local network using the drop-down list.
Authentication - You can provide credentials to authenticate to the SQL Server instance hosting the Sage 300 database (specified above) in two ways. The method used will depend on how your SQL Server instance is configured:
Windows login - Enter a Windows user name and password.
SQL Server login - Enter a SQL Server user name and password.
User Name - Type a user name in the same form you use to log in directly to Windows or SQL Server (depending on which authentication method you chose above). This may be just a user name, or it may include the domain name in canonical form (domain\user) or UPN form (user@fully-qualified_domain_name), depending on your environment.
Password - Type a password for the specified user name.
Optional
One or more optional advanced connection settings can be added or modified for this data source using either of the following:
Advanced panel on the Connect screen when adding the data source.
Properties panel when viewing an existing data source, under the Advanced section.
Sage 300 Datasource company restriction
When using Sage 300 with Data Hub, your plan may limit your company connections to three individual companies. If you attempt to process a model after adding a new company when your limit has been reached, you will receive the following error and your model will not process:
Tip
Example - You have two Sage 300 models in Data Hub. Model 1 has data from two companies. Model 2 has data from a third separate company. If you were to add a further company to model 2, you would exceed the three company limit and therefore error would occur on both models when you attempt to process them.
If you need to continue with the additional company(ies), you will need to upgrade your license.