Product: Sage 100
Article Link: https://help.truecommerce.com/en/articles/15946201-sage-100-issue-documents-not-found-on-import-search
Issue: When performing an integrated search to import documents from Sage 100 within Transaction Manager, the search returns no results and no error messages are displayed.
Reason: Several conditions can prevent Transaction Manager from locating documents in Sage 100 during an import search — including the Sage Customer Number not being matched in the Partner List, documents belonging to a closed batch in Sage 100, or a missing SOTAMAS90 entry under the User Data Source Name (DSN) in the Windows Open Database Connectivity (ODBC) Data Source Administrator.
Solution - Verify the Partner List
The Sage Customer Number on the documents must match what is configured in the Partner List for the Trading Partner those documents belong to. If the Customer Number does not match, Transaction Manager will be unable to locate the documents during the search.
Verify that the Sage Customer Number on the documents being searched is listed in the Partner List for the appropriate Trading Partner.
Navigate: Trading Partners → (Partner) → Translations → Partner List
Solution - Check for a Closed Batch
In Sage 100, Invoices and Advance Ship Notices (856) that belong to a closed batch cannot be retrieved by Transaction Manager during an import search. If documents are part of a batch that has been closed, they will not appear in the search results.
Determining whether a batch is closed and reopening it falls outside of TrueCommerce Support. Please work with your Sage 100 administrator for assistance with batch management.
Solution - Add the Missing User DSN ODBC Entry
Transaction Manager leverages the Open Database Connectivity (ODBC) solution from Windows and will require a SOTAMAS90 entry to be present under the User Data Source Name (DSN) tab of the Windows Open Database Connectivity (ODBC) Data Source Administrator in order to locate documents during an import search.
While the System DSN may already have a TCSotaMas90 entry, the User DSN also requires its own SOTAMAS90 entry. If the User DSN entry is missing, Transaction Manager may fail to find any results or display connection errors.
Local administrator access is required to modify ODBC settings. If you do not have local admin rights, contact your IT department for assistance.
Opening the ODBC Data Source Administrator
Open the Windows ODBC Data Source Administrator using one of the following methods:
Option A — Windows Search
Search: Type ODBC in the Windows Search Bar
Select: "ODBC Data Sources (32-bit)" or "ODBC Data Sources (64-bit)" depending on your system
Option B — Run Dialog
Press: Windows Key + R
Type: odbcad32.exe
Press: Enter
Checking the User DSN Tab
Once the ODBC Data Source Administrator is open:
Select: The User DSN tab
Verify: That SOTAMAS90 is listed in the data source list
If SOTAMAS90 is not present under the User DSN tab, it will need to be added manually.
Adding the User DSN Entry
Select: Add
Find: MAS 90 4.0 ODBC Driver in the driver list
Select: Finish
A new configuration window will appear. Under the Basic tab, fill in the following fields:
Data Source Name: SOTAMAS90
Description: SOTAMAS90
Database Directory: Enter the file path to your Sage 100 server directory
Select: Apply
The Database Directory path should match the Sage 100 server path configured in Transaction Manager under Business System → (Company) → Company Configuration → Integration Options.
Restarting the Integration Service
After adding the User DSN entry, the Transaction Manager Integration Service must be restarted for the change to take effect.
Navigate: Windows Search Bar → type Services
Select: The Services gear icon to open the Services window
Scroll: Locate Transaction Manager Integration Service
Right-click: Transaction Manager Integration Service → Stop
Right-click: Transaction Manager Integration Service → Start
If the Stop or Start options are greyed out, Services must be run as an administrator. Right-click the Services application and select "Run as Administrator," or contact your IT department for assistance.
Once the service has been restarted, return to Transaction Manager and perform the import search again. If documents are still not found, further review by Integration Support may be required.
Additional Resources
rev 07/15/26