HomeTutorialsShipping SolutionStarship
Last Modified:Wednesday, 28 October 2020 01:28


The following is a tutorial for setting up the interface from the Shipping Solution to Starship via the Starship Developer Interface.

Note: The Starship Developer Interface replaces the older ADE interface which is no longer supported by Starship or Cadacus, Inc.

Below is a short video tutorial about setting-up the Starship tab of the Shipping System Interface.

     NOTE: Chrome or Firefox is recommended for viewing video tutorials as skip controls are more effective than those in IE or Edge.

Shipping / Handheld System Information
   Shipping / Handheld System Information   Video    Version
 Shipping / Handheld System Information - Starship tab


Required Files:

Download the Starship files in zip form here and unzip into a directory on the workstation.

Starship.ini :

Each Starship workstation requires a "StarShip.ini" text file to be placed in the Windows directory (normally c:\Windows).  A sample file is included in the zip file. The system will look in the folder defined by the environment variables GETWINDIR first, if the file is not found it will look in the folder defined by USERPROFILE and then the Windows folder under the folder defined by USERPROFILE. On a standard workstation the windows folder is generally used, the USERPROFILE folder is used on terminal servers and similar multi-user servers.

The "STATION" number parameter must be unique for each Starship workstation. The "Path" must be a directory where the interface files can be read and written and must match the path in the SFSConfiguration.xml file as indicated below. Note:  directory paths used MUST NOT include a space anywhere in the path name.  When the path is added to the StarShip.ini file, it must include a trailing backslash ("\") at the end.  For example, the "Path" line in the StarShip.ini file might look like this:

SFSConfiguration.xml : 

Edit this file and change the three elements with paths as directed by the comments.  The "StarShip Input Path" and "StarShip Output Path" must be the same path and must match the path in the Starship.ini file.  Note:  directory paths used MUST NOT include a space anywhere in the path name.

The paths in the "Field List" and "Default Map" elements must indicate where the following two files will be located.  It is recommended this be the same folder as the SFSConfiguration.xml file.

SFSFieldList.xml :

This file contains the field list sent from the Shipping Solution to Starship.  DO NOT MODIFY THIS FILE.

SFSFieldMap.xml :

This file contains the field mapping for the Shipping Solution to Starship.  DO NOT MODIFY THIS FILE.


Start the Starship client and change the source interface using the options show in the following menu tree.

Install the configuration by choosing, "Source Interface--> Use Source--> StarShip Developer Interface" from the menu.












Choose "Add Company" on the following screen and then browse and select the "SFSConfiguration.xml" file previous stored on the workstation in the next dialog box as shown below.











Since 1991, as developer of the standard EDI, Shipping, and Freight Calculator Solutions for SYSPRO, our products are fully integrated with SYSPRO and drive efficiencies for hundreds of users worldwide.


For 35 years, SYSPRO has had a single product focus resulting in an award-winning ERP system with a track record of success for over 14,000 customers worldwide.