This article explains how to run Sage 100 Visual Integrator import or export jobs outside the program.
It shows how to create a shortcut or batch file for Sage 100 ERP tasks using the Application Server.
Understand prerequisites and requirements
- Use this process only with the following versions:
- Sage 100 Advanced and Premium
- Sage MAS 200 version 4.40.0.4 or higher
- Use the Sage 100 Application Server for external execution.
- Running jobs this way prevents ODBC path issues that block Sage tasks.
Gather job information
- Open Import Job Maintenance or Export Job Maintenance.
- Select an existing job or create a new one.
- Record the Job Name.
- Open the job.
- Locate the Compiled File Name in the upper-right corner.
- Record the VI program name, such as VIW###.
Create a new application entry in Application Server
Perform setup on the Sage 100 Advanced server
- Open Windows Start, Sage, Sage 100 version directory.
- Select Application Server Configuration.
- Select the Apps tab.
- Click New to open the app properties screen.
- Enter the Job Name as the App Name.
- Caution: The App Name must exactly match the batch file entry.
Configure application settings
- ProvideX EXE: Leave default.
- Server INI: Enter
..\Launcher\Sota.ini. - Lead Program: Enter
StartUp.M4P. - Extra CMD Options: Leave blank.
- Arguments: Leave blank.
- Start-In Directory: Enter the
..\MAS90\Home path. - Init Window: Select Hidden.
Configure options
- Select Allow Client Arguments.
- Clear all other options.
Save and restart
- Click OK.
- Click Apply to save changes.
- Compare settings with the existing Sage 100 entry for accuracy.
- Exit Sage 100 for all users.
- Restart the Application Server or related Windows service.
Create the batch file
Build the batch file structure
A batch file includes three lines:
Line 1:
C:
Line 2:
CD "C:\Sage\MAS 200 Client\Version4\MAS90\HOME"
Line 3:
"C:\Sage\MAS 200 Client\Version4\MAS90\HOME\pvxwin32.exe" -hd ../launcher/sota.ini *Client -ARG "Server Name" "Port" "App Name"
Add required arguments
Append this argument block to Line 3:
-ARG=DIRECT UION UserLogon Password Company VIWxxx AUTO
- Use no space after
-ARG=. - Replace placeholders with actual values:
- UserLogon: Sage 100 login with VI permissions
- Password: User password
- Company: Company code
- VIWxxx: Compiled VI name
- AUTO: Runs silently
Example batch file
C:
CD "C:\Sage\Sage 100 Workstation\MAS90\Home\"
"C:\Sage\Sage 100 Workstation\MAS90\Home\pvxwin32.exe" -hd ../launcher/sota.ini *Client -ARG "SERVER1" "10000" "SOINVOICEIMP" -ARG=DIRECT UION admin password ABC VIWI00 AUTO
Save and run
- Open Notepad.
- Paste the three lines.
- Save the file with a .bat extension.
- Double-click the file to run the job.
Steps for Sage 100 Standard or older MAS versions
Verify setup
- Confirm the task exists as a menu item.
- Confirm Visual Integrator jobs appear on the Jobs menu.
- Assign user access in Role Maintenance.
Create the command line
Use this format:
..\MAS90\Home\Pvxwin32.exe ..\Launcher\Sota.Ini ..\SOA\Startup.M4P -ARG DIRECT UION user password company VIWxxx AUTO
Example command
F: CD F:\Version4\MAS90\Home Pvxwin32.exe ..\Launcher\Sota.Ini ..\SOA\Startup.M4P -ARG DIRECT UION user1 password01 ABC VIWI00 MANUAL
Configure arguments
- Use
UION or UIOFF to control user interface display. - Use
AUTO for silent execution. - Use
MANUAL for testing with prompts.
NOTE:
Use double quotes "" as placeholders for unused fields.
TIP:
Map drives above the MAS90 directory, not directly to it.
Additional information
- Define the source file location in Import Job Maintenance.
- The batch file cannot override the source file path.
How to setup user Roles and set up security and permissions for users to access tasks and options in Role Maintenance for Sage 100
- Solution ID
- 222924450019387
- Last Modified Date
- Wed Jul 01 23:42:17 UTC 2026
- Views
- 0