The general setup needed to support third party application integration with MoversSuite involves the settings listed below. Refer to specific setup areas for detailed information.
Setup Area |
Interface |
Description |
SIRVA |
Accounts referenced by SIRVA STS need to be added and the correct number set within the Account # field. Refer to National Account Setting for SIRVA for more information. | |
Atlas SUDS EasyDPS SIRVA Q2G |
External code values must be entered and match exactly to what is expected by an external interface. The address type must match an external code within the External Interface Mapping of this setup to avoid errors when exchanging address data with SIRVA (SIRVA STS Integration). | |
Agent API SIRVA |
Agent records must be established for the appropriate van line. MoversSuite will automatically add an agent of a van line if no record exists. | |
UniGroup |
Define class elements assigned to auto shipments. | |
SIRVA |
External codes supplied by third party interfaces must be established as Auto Make records in order for auto shipment data to transfer without error. | |
Atlas SIRVA TechMate |
Define the branch to be associated to the setup. | |
EasyDPS |
Verify that needed carriers are defined with the SCAC supported by EasyDPS. | |
UniGroup |
Claim damage types referenced by third party applications must be setup with correct external code references in the Van Line Code field this setup. | |
UniGroup |
Claim denial types referenced by third party applications must be setup with correct external code references in the Van Line Code field this setup. | |
Atlas |
Referenced by the Atlas SUDS Order Upload process. See for Atlas Integration Setup and Administration details on the reference. | |
Atlas EasyDPS SIRVA
|
Associate commodity codes specified within MoversSuite to commodity codes required by the third party. The following setup areas specifically reference this setup: Atlas Integration Initial Setup UniGroup Download Setup and Administration UniGroup Upload Setup and Administration
| |
All |
Import statement data directly into Payment Management from external applications. | |
Atlas Avalara Dynamics GP Crew Punch TransDocs |
Set the values needed for Document Management and TransDocs as well as those needed for Microsoft Dynamics GP. | |
Atlas |
Referenced by the Atlas SUDS Order Upload process. See for Atlas Integration Setup and Administration details on the reference. | |
UniGroup Quotes to Go
AgentConnect
Pass Thru Connector |
Third party applications that import estimates into MoversSuite may require particular lead types. | |
EasyDPS SIRVA UniGroup TechMate |
Container, packing, and unpacking units associated with revenue will need to be linked to appropriate item codes. UniGroup relies on specific carton codes that are defined beginning with the item codes. See UniGroup Upload Setup and Administration for more information. | |
SIRVA |
External codes supplied by third party interfaces will need to be defined and associated with MoversSuite move type records. | |
Atals EasyDPS SIRVA UniGroup TechMate |
Van line codes used by third party applications will need to be mapped to particular Van Line Codes and Note Types. | |
All |
Use this tool to free up Order Numbers in MoversSuite. | |
SIRVA |
Order Numbers format definitions must be associated to all van lines that will be involved with data exchange with MoversSuite. | |
All |
Create a poller to monitors a queue through the API service handle request from local clients to upload orders through MoversConnect. | |
SIRVA UniGroup |
External codes supplied by third party interfaces will need to be defined and linked to MoversSuite payment method records. These setup values are needed by UniGroup Quote to Go. | |
SIRVA UniGroup |
External codes supplied by third party interfaces will need to be defined and linked to MoversSuite payment type records. | |
SIRVA UniGroup TechMate |
Employees associated to move roles (Coordinator, Salesperson, OA Surveyor, Revenue Clerk, etc.) must be defined and be linked by identification numbers through external codes for each interface within the Personnel Interface Mapping.
| |
UniGroup |
Define Point of Service values needed for line items on an EDI invoice imported from the UniGroup Rating Send (UniGroup Downloads) and through the Point of Service field in Add Revenue Item. | |
SIRVA |
External codes supplied by third party interfaces will need to be defined and linked to MoversSuite product code records. | |
SIRVA |
External codes supplied by third party interfaces will need to be defined and linked to MoversSuite product type records. | |
All |
Define the location of message files processed through the MoversSuite queuing service with this setup. | |
All |
Establish specific server instances for each process supported by MoversSuite queueing services. | |
SIRVA |
External codes associated for rating and pricing referenced by third party applications will need to be set within the Van Line Code field, mapping it to a MoversSuite rate plan. | |
Suddath |
Set the external codes to identify services for the third-party applications. | |
SIRVA |
To access the Third Party Interface Order Monitor, the Order Information module must be assigned to personnel (through Security Profile) for the appropriate branch. Note: Any Access Type will work. | |
SIRVA Atlas |
Define distribution codes needed for statement imports. | |
UniGroup |
Set external codes used to identify services by third party applications. | |
Atlas SIRVA UniGroup |
Link Shipment Status records to codes supported by the various interfaces. | |
SIRVA UniGroup |
External codes supplied by third party applications will need to map to a MoversSuite shipment type. | |
All |
This setup information is documented specifically under many integrations, such as SIRVA and UniGroup. Your company can also use the Standard XML Pipeline for other external applications as well. | |
Atlas SIRVA UniGroup |
Use this setup to link pre-defined Payment Code in MoversSuite to those supported by various interfaces. | |
UniGroup |
Set external codes used to identify warehouses by third party applications. | |
UniGroup |
Set external codes used to identify transportation modes in use by third party applications. | |
UniGroup |
Define the data needed to support uploads and downloads from the UniGroup Quotes to Go system. | |
SIRVA |
External codes supplied by third party interfaces will need to be defined for each van line in use and be associated to MoversSuite valuation records. | |
All |
Verify that all van lines referenced by third party applications are established here. | |
All |
Link supported interfaces to MoversSuite orders through external codes and mapped branches. | |
SIRVA TechMate |
Define needed records that map an interface and XML Item Code values to MoversSuite Item Codes or Material Types. | |
All |
Define systems, system options, and data type mappings for supported interfaces within this setup. Define systems used by an interface along with needed system options and corresponding values. |
Technical Note |
One-time table setup includes the following. Consult with a MoversSuite Support professional prior to making modifications to these tables. CountryCodeStandard VanLineCodes XmlExternalInterfaceVanlineMap XmlSystem XmlValuationVanLineCodeMap
|
RELATED TOPICS:
Atlas Integration Setup and Administration
EasyDPS Integration Setup and Administration
SIRVA QLAB Integration Setup and Administration
SIRVA STS Integration Setup and Administration
UniGroup Download Setup and Administration
UniGroup Upload Setup and Administration