Navigation:  »No topics above this level« Overview

 

Shipping Integration is designed to integrate your shipping software system with your Sage 100 ERP Sales Order shipping system.  It requires that the shipping software be able to export a delimited file for each shipment.  The delimited file can then be read by Shipping Integration and information pulled into Sage 100 ERP.  Many shipping systems, like UPS Worldship or FedEx Ship Manager, are able to read shipping information from Sage 100 ERP orders to speed entry.  Setting these procedures up in the shipping software are outside the scope of this modification, but we have included instructions for UPS Worldship and FedEx Ship Manager.

The key that ties everything together is the document number - either sales order, service order or invoice number (or rental contract for some versions).  For this reason it is critical that each package shipped have a consistent order or invoice number from Sage 100 ERP in one of the Reference fields in the shipping software and that that reference field is set up to export after each shipment.

There are two sides to this process: The shipping software side and the Sage 100 ERP side. There are no changes to the shipping software.  As long as your shipping computer has access to the server where the Sage 100 ERP data resides and has ODBC (Open  DataBase Connectivity) installed, you can usually set it up to read data from the Sales Order header file directly into the shipment in the shipping software.  As mentioned before, it is critical that the Sage 100 ERP document number (sales order, service order, invoice number or contract) be stored in one of the reference fields on the package so it can be exported with the shipment information and tied back to the Sage 100 ERP shipping system invoice.   Even though pulling information into the shipping software is a standard feature, an example will be documented briefly here.

The other side of the function is to pull the shipping software shipment information back into the Sage 100 ERP shipping system.  This is the custom modification provided by the ASI Addition, Shipping Integration.  A standard feature of most modern shipping software, including UPS Worldship and FedEx Ship Manager allows you to create a comma-delimited file with selected information after every shipment.   This file is then read by the Shipping Import function to update the shipping records in Sage 100 ERP.  The order or invoice must be present in the comma-delimited file in a consistent column.  Along with that, the import can optionally update the tracking numbers, the weight, the freight and the Ship Via code from the shipping software to Sage 100 ERP.  This new function is available as a batch process from the Sales Order main menu or from a button on the Sales Order Shipping Data Entry Shipment panel.

The Shipping Integration package does not only pull in UPS WorldShip or FedEx Ship Manager data.  As long as your shipping package can produce a comma-delimited file, you can import the designated shipping data from any other package as well.

 

 ASI Shipping Integration Setup – As of revision 02, a separate menu option, ASI Shipping Integration Setup, was added to the Sales Order Setup menu.

 

Purge Unmatched Shipments – As of revision 02, a separate menu option, Purge Unmatched Shipments, was added to the Sales Order Utilities menu.

 

 Edit Shipping Records – As of revision 02, a separate menu option, Edit Shipping Records, was added to the Sales Order Utilities menu.

Service Order Matching – As of revision 02, you can specify the Service Order Number from ASI Service Center in the import file and Shipping Integration will find the service order.

Added Field Mapping – You can map many additional fields to be filed in on the invoice header or in the tracking lines, including user-defined fields.

Freight per-package and per-shipment surcharges - We have added to option to automatically add a surcharge per package and/or per shipment.   The user can specify a default surcharge in the Shipping Integration options, or can have a surcharge per SHIP VIA.   (For ARM Contracts the SHIP VIA override is not available)

ShipWeight vs Weight - On the sales order invoice and the contract, there are two fields representing weight.  The ShipWeight$ field is a string that hold  the integer weight (no fractional part) and is updated when freight is automatically calculated from weight of the line items.  If the options call for freight calculation from the lines of an invoice or contract, the weight used to calculate freight is stored in the ShipWeight$ string field.   The Weight field represents the actual weight of the total invoice or contract.  A new feature allows the user to select either or both ShipWeight$ and Weight to be updated by the Shipping Integration import.

ARM Contract Matching - Shipping Integration works with Automated Rental Management.  The user must specify a column in the import file for the Contract Number and a separate set of options is available for contract updates.  It is important to note that because ARM is a legacy application, the addition field mapping is NOT available as it is with Sales Order Invoices.  Also, the ability to override the per package or per shipment surcharge is not available for contracts.