The following table describes the administrative setup needed to support integration with Atlas and Atlas SUDS.
Before you begin…
The following setup areas are dependent on one or more other setup areas, therefore MoversSuite recommends performing the setup in the following order:
1. Van Line Setup
2. Agent Setup
3. Branch Setup
4. XML Interface Setup
5. XML System Setup
6. Statement Payment Code Setup
7. Payment Type Setup
8. Shipment Status Setup
9. Valuation Setup
|
Setup Area |
Description | ||||||||||||||||||||||||||||||||||||||||
|
Define Agent records for the Atlas Van Line. | |||||||||||||||||||||||||||||||||||||||||
|
Define Branch records associated to the Atlas Van Line and corresponding Atlas Agent as needed. | |||||||||||||||||||||||||||||||||||||||||
|
Document Type values from the Atlas Settlement Statement Import must match Payee Codes defined in this setup. | |||||||||||||||||||||||||||||||||||||||||
|
Link commodity records to Atlas by associating Commodity Code values to the following supported Atlas codes:
| |||||||||||||||||||||||||||||||||||||||||
|
Link Note Type records to Atlas by associating Van Line Code values to the following supported Atlas codes:
| |||||||||||||||||||||||||||||||||||||||||
|
Use this setup to link pre-defined payment types in MoversSuite to those supported by the Atlas interface. Create the following definitions within this setup:
See Payment Application for more information on payment processing. | |||||||||||||||||||||||||||||||||||||||||
|
Link Payment Type records to the Atlas interface using the following supported Atlas codes:
| |||||||||||||||||||||||||||||||||||||||||
|
Assign personnel to Atlas supported branches and to the Atlas interface using this setup. For supported sales people (Sales) and estimators (OA surveyor), provide their Atlas sales number as the User ID setting for the Atlas interface within the Interface Mapping tab. For supported drivers, enter their Atlas Driver Number within the Dispatch tab. Note: Coordinators are currently not support. User ID and Driver Number Format: The format of the User ID and Driver Number is the agent code (minimum of four digits, zero-filled) followed by the Atlas employee code (up to five digits). For example, Agency of “777” and employee code of “999” would result in “0777-999”. For Auto Dispatching: Verify that drivers referenced by an Atlas order are setup for Auto Dispatching and their Driver Number is in the correct format. | |||||||||||||||||||||||||||||||||||||||||
|
Allow users to process Atlas statements by assigning to their profiles the “Atlas Statement Integration” Security Module. When this module is assigned to a user, they will be able to select the Atlas Statement option through the Import drop-down in Payment Management. Only one assignment per profile is necessary; it applies to all branches (see Security Modules). | |||||||||||||||||||||||||||||||||||||||||
|
Link Shipment Status records to the following codes supported by Atlas. The process that updates the Shipment Status in MoversSuite requires a match to one of the following codes.
| |||||||||||||||||||||||||||||||||||||||||
|
Verify that the “Atlas Statement Integration” module is turned on. | |||||||||||||||||||||||||||||||||||||||||
|
Link Valuation records to the Atlas interface using the following supported Atlas codes:
| |||||||||||||||||||||||||||||||||||||||||
|
Define a van line record for Atlas along with address data, authority, customer, vendor number, etc. in this setup. The following values are recommended for Atlas:
Other values will need to be set accordingly.
| |||||||||||||||||||||||||||||||||||||||||
|
Use this setup to define an interface for “Atlas” that links supported van lines to supported branches. The following is a list of supported code values:
| |||||||||||||||||||||||||||||||||||||||||
|
Use this setup to define the system processes that support the Atlas SUDS Order Download and Atlas Settlement Statement Import. Create a record to define the Atlas system record with the following data:
No XML System Options are needed.
Define XML System Data Type Map records for the order download and statement import processes. This setup allows the processes to be identified through the Third Party Interface Order Monitor. For the SUDS order download:
For the settlement statement:
|