Version 7.1
Contents of this Topic: Show
OMS integrates with the standalone FedEx Ship Manager (Cafe) shipping software by means of an ODBC connection , which allows data to pass back and forth between the systems so that the user does not need to manually re-type shipping and tracking information. If you have multiple OMS store files, the steps outlined in this topic have to be performed for each store file , and a different "Integration Profile" should be created in Ship Manager for each data file. The Integration Profile contains user preferences and field mapping information, as well as the ODBC connection to the OMS store file.
Contact FedEx to obtain the Ship Manager software (FedEx Web site). You must already have an established account with FedEx before the software can be installed and the registration process can be completed.
The images in this topic were produced in an Access 2003/Windows XP environment and may differ slightly in other environments, but the same functionality is available in later editions. Refer to the Help system of the installed versions of Access or Windows for more assistance.
The images for the FedEx Ship Manager software in this topic may be slightly out of date, but should provide enough guidance for the user to complete the necessary steps.
Enterprise Edition users who use an SQL database as a their OMS store data file must perform some additional steps that are not necessary when an MS Access database is used.
If you are not an Enterprise user or do not use an SQL database, skip to MS Access Store Data File: Define an ODBC Connection and continue with those instructions.
Launch Microsoft Access.
Create a blank MS Access database (File>New>Blank Database) named OMExternalShipping.mdb, or something similar, in the C:\StoneEdge directory of the workstation where FedEx Ship Manager is installed.
Open the newly created database and go to File > External Data> ODBC Database.
Select Link to the data source by creating a linked table and click OK.
The Select Data Source dialog opens.
Click on the Machine Data Source tab and locate the System DSN for the Order Manager's store data file (which was created when the SQL database was converted from an MS Access database).
It should be noted that the Order Manager is a 32-bit application and an ODBC connection made through the Order Manager (Convert to SQL process, Worldship Setup function ) will not be visible via the default ODBC Data Source Administrator utility of a 64-bit Operating system. Refer to Knowledge Base topic, Windows 64-Bit Operating System Considerations, for instructions on locating the compatible 32-bit ODBC utility.
Select the correct DSN and click OK.
The Link Tables dialog opens.
While holding either the Shift or Ctrl keys down, select the tables, dbo.Orders and dbo.ShippingMethods, and click OK.
The OMExternalShipping: Database screen appears, showing the linked tables.
Although, the shipping information query has "Worldship" in it's name, this same query is also used for any external shipping software package that supports the use of an ODBC connection, such as FedEx Ship Manager or DHL DBConnect, etc.
From the MS Access menu (not pictured), select File > External Data > Import & Link > Access.
Click Browse and navigate to the Order Manager's program file (SEOrdManEnt2007.mdb).
Click Browse and navigate to the Order Manager's program file (SEOrdManEnt2007.mdb).
Select Import tables, queries, forms , reports, macros, and modules into the current database. Click OK.
The Import Objects dialog opens, select the Queries tab.
Select WorldshipOrdersSQL, and click OK.
If you want to Save the Import Steps, select that box.
Click Close.
The WorldshipOrdersSQL query is now listed in the Queries section of the OMExternalShipping database.
Create a new System DSN for the OMExternalShipping database, using the 32-bit version of the ODBC Data Source Administrator utility.
Windows XP users simply go to Control Panel > Administrative Tools > Data Sources (ODBC). If a 64-bit edition of Windows is used, review the Knowledge Base topic Windows 64-bit Operating System Considerations for information about how to execute the 32-bit compatible utility.
When the ODBC Data Source Administrator form appears, click Add.
Click Finish.
The ODBC Microsoft Access Setup screen opens. Enter a meaningful name in the Data Source Name field, and optionally, a description.
Click Select and navigate to the location of the database created in step 2 (OMExternalShipping.mdb) of section, Create an Intermediary Database and Link Tables in OMS 's Store File.
Click the OK buttons on the Select Database screen and the ODBC Microsoft Access Setup screen.
The user is returned to the ODBC Source Administrator screen, where the new connection is visible.
An ODBC connection to OMS 's store data file must be created on each workstation where Ship Manager will be used to print shipping labels for OMS orders.
If an ODBC connection to the store data file has already been defined for some other purpose, such as for use with another external shipping application, it is possible to use that same ODBC definition in conjunction with Ship Manager. In that case, skip to Configuring FedEx Ship Manager and follow those instructions. Otherwise, complete the following steps:
Go to Main Menu > Settings > System Functions > Store Setup Wizard > Shipping.
Click Create System DSN/ODBC Connection.
The Enter name for System DSN dialog box opens.
Enter a name for the ODBC connection between Ship Manager and your store's data file, such as "OMSTOREDATAFILE". The name cannot have spaces or punctuation in it. If more than one store file is used, and you will be printing labels for orders from both stores through FedEx Ship Manager, it might be helpful to use the store name in the System DSN to easily tell them apart.
Be aware that an ODBC connection made through OMS (Shipping Setup Wizard or UPS WorldShip Setup) is 32-bit and is not visible via the default Data Connections utility in the Administrative Tools section of the Control Panel of a 64-bit Windows operating system. Refer to Windows 64-Bit Operating System Considerations, for more information.
Microsoft Access is a 32-bit application and cannot use an ODBC connection created in 64-bit mode.
Click OK create the ODBC connection. Make a note of the name as you will need it later when setting up Ship Manager.
The program pops a message box to indicate the creation of the ODBC connection and the addition of the WorldShip queries to the OMS store data file.
Click OK to acknowledge the end of the process.
Once the FedEx Ship Manager application has been downloaded and installed,you can create an Integration Profile to complete the connection between OMS and Ship Manager.
Launch the Ship Manager software.
Select Integration from the menu and click FedEx ® Integration Assistant.
At the Welcome > Introduction screen, click Continue (not pictured).
At the Welcome > Before You Begin screen, click Continue (not pictured).
At the Begin > Create screen, select Create a New Profile and then click Continue (not pictured).
If you use an SQL database as your OMS store file:
the Import Map should point to the intermediary database, OMExternalShipping.mdb, created way back in step 2 of the section entitled, Create an Intermediary Database and Link Tables in OMS 's Store File
the Export Map should point to the ODBC connection for the OMS store data file, OMStoreDataFile, created in the section entitled, MS Access Store Data File: Define an ODBC Connection
If you use an MS Access database as your OMS store data file:
the Import and Export maps created in Ship Manager should both point to the same database (ODBC connection) that represents the OMS store data file, OMStoreDataFile
Click Continue.
At the Import > Shipping screen, it is recommended that you select Yes for all of the settings on this page.
Click Continue.
At the Import > Lookup screen, select After I enter a lookup value and click Continue (not pictured).
At the Import > Information screen, complete the Recipient and Package field lists.
Click Recipient and select all of the fields in the table below:
Address 1 | Address 2 |
City | Company |
Contact Name | Country |
Phone | Postal Code |
State/Province | ID |
Click Return to close the Recipient form.
Click Package and select the fields listed in the following table:
Bill Transportation To | Customer Reference |
Package Type | Residential Delivery Flag |
Service Type | Weight |
It is necessary to use the vertical scroll bar to locate some of these fields, which are not all visible in the image below.
Click OK.
The WorldShipOrders table is used for any external shipping software integration, not just for UPS WorldShip.
These fields can be mapped on a one-by-one basis or respond Yes to the pop-up message shown below to set all unselected tables to WorldShipOrders. Even though the Bill Transportation To and Package Type fields do not require a table selection, it is OK to leave the WorldShipOrders table selected for those fields.
While still at the Import > Match screen, click Select Index after all of the OMS fields have been mapped to the corresponding Ship Manager fields.
The Primary Index screen opens. Click Tables at the bottom of the page.
A list of fields found in the WorldShipOrders table appear in the Lookup dialog box.
Select the Order Number field from the list and then click OK. A colored line will appear to indicate the relationship has been made.
Click Continue and proceed to the Import > Conversion screen.
Click Service Type to map the names of FedEx Ship Manager method names (radio buttons) to your OMS shipping methods (drop-down lists). Use the vertical scroll bars to see additional shipping methods.
For each FedEx shipping method that you use, click its radio button in the FedEx list, To (FSM value), and select the corresponding shipping method name from the adjacent drop-down list in the OMS method name list, From (your value).
Click Continue to proceed to the Export > Destination screen. This is where the export map gets created.
Remember, if you use an SQL database as your OMS store file, the ODBC connection used for the ShipManager export map should point to the store data file, not the intermediary database.
When do you want to export to your data source?
At the end of day
How do you want to update your data source?
Insert a new record
Click Continue to proceed to the Export > Information screen.
Click Tracking Number on the side of the screen and select the field labeled Tracking Number (not pictured).
Click Return and then select Package.
Select the box labeled Customer Reference.
Click OK to proceed to the Export > Match screen and map the following fields:
FedEx Field Name |
Select a Table |
Select a Field |
Tracking Number |
Tracking |
TrackingID |
Customer Reference |
Tracking |
OrderNum |
Click Continue to proceed to the Finish > Summary screen, which shows a summary of the integration profile.
To review or change the settings that have been made, click Edit next to any of the sections.
If satisfied with the settings, click Continue to proceed to the Finish > Instructions screen.
Click Finish. The application prompts you to provide a name for the new integration profile.
Click Finish to complete the integration between FedEx ShipManager and OMS .
At that time, the ShipManager software opens the Lookup Value screen.
Enter the number of an approved OMS order in the Lookup: field and click OK.
The ShipManager screen is populated with the shipping information pulled from OMS , and you are ready to print a shipping label.
Once the integration steps have been completed, to print OMS shipping labels through ShipManager, follow these steps:
Launch the FedEx ShipManager software.
Click on the [Integration] menu item and select the name of the profile that was created during the setup process from the drop-down list. Refer to step 33 in the previous section.
The Lookup Value dialog box opens.
Enter the OMS order number of an approved order and press [OK].
The order information populates the screen.
Review the fields for accuracy and print the label.
Windows 64-Bit Operating System Considerations
Created: 9/26/11
Revised: 5/29/13
Published: 04/14/16