Atlas Integration Initial Setup

This section provides information on enabling the Atlas Integration and establishing the basic settings to support the related processes:

Atlas Revenue Import

Atlas Settlement Statement Import

Atlas SUDS Order Download

Atlas SUDS Order Upload

Additional setup is necessary as specified in the following areas:

Atlas SUDS XML Order Download Setup

Atlas SUDS XML Order Upload Setup

Atlas Revenue Import Setup

AtlasNet Document Integration

The following setup areas are affected by the Atlas Integration and detailed steps are included in the remainder of this topic. Items list accordingly to suggested order of entry, i.e., setup a van line, then setup agent records, etc.

IMPORTANT: Details for each setup area that are specific to the Atlas SUDS integration follow this listing. The setup areas are numbered so that one can scroll through the list and easily find the setup area(s) needed.

Setup Area: MoversSuite Administration > Administration > Van Line

Establish a Van Line Setup record for Atlas Van Lines with a Van Line Code of A. Enter other data as needed.

Figure 20: Van Line Setup

The van line is associated to the MoversSuite Order Number.

Setup Area: MoversSuite Administration > Customer Service > Agent

For each agent that you wish to access the Atlas Integration, link their Agent Setup record to the Van Line of Atlas Van Lines.

Figure 21: Agent Setup

Manage agent assignments through the Agents tab.

Setup Area: MoversSuite Administration > Administration > Branch

For the branch of the orders you wish to have access to the Atlas Integration, link their Branch Setup record to the Agent and Van Line that link to Atlas Van Lines.

Figure 22: Branch Setup

Manage the branch of an order through the Book Order Information screen.

Setup Area: MoversSuite Administration > Administration > XML Interface

Establish an interface for the Atlas Van Lines within XML Interface Setup. Link this record to the established Van Line Item for Atlas and assign an External Code of A.

The Branch Item section comprises all the branches that this Atlas interface is available. Establish items for each supported Atlas branch.

Figure 23: XML Interface Setup

Setup Area: MoversSuite Administration > Administration > XML System

Use the XML System Setup to establish systems, or processes, available for the Atlas Van Line interface. Create a single record specifying the Internal System and External System as AtlasSuds. Add an XML System Option for uploads, and then establish XML System Data Type Map items for the processes you wish to support on your system (specified below).

Figure 24: XML System Setup

For Atlas SUDS Order Uploads, establish an XML System Option titled AtlasSenderQueueName with a Value containing the same path as that of the Request Queue within Queue Service Server Setup. Refer to Atlas SUDS XML Order Upload Setup.

Figure 25: XML System Option

Again, verify that the path setting referenced for the Value set for the XML System Option matches that set for the Request Queue for the Atlas SUDS XML Upload record within Queue Service Server Setup.

Figure 26: Server queue sample within Queue Service Server Setup

Create XML System Data Type Map entries to support the various processes. Defining these records enables the process and allows them to be visible through the Third Party Interface Order Monitor.

Support for the Rating Download

Create a mapping for Atlas - Rating linked to the Xml System Data Type Map of Rating. This defines the process to support an Atlas Revenue Import.

Figure 27: Sample Data Type Map within XML System Setup

Support for Order Uploads and Downloads

To support the Atlas SUDS Order Download processes, create a mapping for Atlas - Suds linked to the Xml System Data Type Map of Order Information.

Figure 28: Sample Data Type Map within XML System Setup

Support for Settlement Statements

Create a mapping for Atlas - Statements linked to the Xml System Data Type Map of Statement. This defines the process to support an Atlas Settlement Statement Import.

Figure 29: Sample Data Type Map within XML System Setup

Setup Area: MoversSuite Administration > Queue > Queue Service

Manage the MoversSuite Queue Service through the Queue Service Setup. This setup contains global settings for all processes on utilizing the queuing service.

Optionally, you can specify a location for the following three message types to store a copy of the message file exchanged between Atlas and the MoversSuite Queue Service:

Atlas Rating Download

Atlas Suds Flat File Download

Atlas Suds Xml Download

Atlas Suds Xml Upload

Figure 30: Queue Service Setup

Setup Area: MoversSuite Administration > Queue > Queue Server

Create Queue Service Server Setup records to establish server records for each supported Atlas process and manage the message files interpreted by the MoversSuite Queue Service.

Refer to the following topics for details on setup needed to support the specific process:

Atlas SUDS XML Order Download Setup

Atlas SUDS XML Order Upload Setup

Atlas Revenue Import Setup

Setup Area: MoversSuite Administration > Military > Branch of Service

Use the Branch of Service Setup to map military service codes supported by Atlas to orders uploaded from MoversSuite.

Figure 31: Branch of Service Setup

The following table lists the branch of service codes supported by Atlas.

Manage Branch of Service records for an order through the Military/Government tab.

Setup Area: MoversSuite Administration > Military > Carrier

The Document Type utilized within the Atlas Settlement Statement Import must match Payee Code values assigned as Carrier Payee Codes for supported Carrier Setup (Military/Government) record. These are needed to identify the carrier record.

Contact Atlas for the latest list of supported carrier payee codes.

Manage carrier assignments through the Military/Government tab.

Setup Area: MoversSuite Administration > Military > Code of Service

Use the Code of Service Setup to map military service codes supported by Atlas to orders uploaded from MoversSuite.

Figure 32: Code of Service Setup

Link External Codes to military assigned codes. For example, map an External Code of 1 for the Atlas Van Lines to the military Code 1, map External Code of 2 to a Code 2, etc.

Manage Code of Service records for an order through the Military/Government tab.

Setup Area: MoversSuite Administration > Administration > Commodity

Establish a link between MoversSuite and booking division records supported by Atlas Integration by creating Commodity Setup records and linking the following to the Atlas Van Lines interface.

Figure 33: Commodity Setup

Commodity Codes are different based on the whether you are implementing the flat file download or XML upload/download. If you are defining a flat file download only, then you must define Commodity Codes that are compatible with Atlas SUDS 1.0. For the XML upload and download, you must define Atlas SUDS 4.0 codes.

Atlas SUDS 1.0 Codes (for flat file download)

Atlas SUDS 4.0 Codes (for XML upload/download)

Manage commodity assignments through the Move Information tab.

Setup Area: MoversSuite Administration > Administration > Commodity Detail

Use the Commodity Detail Setup to map commodity types supported by Atlas to orders uploaded from MoversSuite.

Figure 34: Commodity Detail Setup

The following table lists the commodity codes supported by Atlas.

Manage Commodity Detail records for an order through the Billing Information tab.

Setup Area: MoversSuite Administration > Administration > Haul Mode

Use the Haul Mode Setup to map military service codes supported by Atlas to orders uploaded from MoversSuite.

Figure 35: Haul Mode Setup

The following table lists the Haul Mode codes supported by Atlas.

Manage Haul Mode records for an order through the Billing Information tab.

Setup Area: MoversSuite Administration > Accounting and Financial Services > Service Code (Accounting)

Establish Service Codes supported by Atlas Integration and link them to Item Codes to support rating and settlement processes. Utilize the Service Code (Accounting) Setup to establish the codes supported by Atlas and then link them to Item Code Setup records through the Service Code setting.

Utilize item and service codes through Payment Management and Revenue Entry modules.

Additionally, to support cartons in uploads and downloads, you must establish XML Item Code Setup records.

Setup Area: MoversSuite Administration > Administration > XML Item Code

To upload and download Containers, Packing and Unpacking (CPU) counts, verify that each supported Material Type Setup item is linked to a supported Atlas code. This is done through XML Item Code Setup. Link the supported Atlas code, set as the XML Item Code, to the appropriate Item Code for the Atlas XML interface.

Figure 36: XML Item Code Setup

Create similar XML Item Code Setup records to the one shown above for all supported CPU items for your Atlas Integration. The following is current list of supported XML Item Codes for Atlas.

The Item Code linked to each of the XML Item Code Setup records must tie back to Material Type Setup records. Each of which can be assigned to orders through the Containers, Packing and Unpacking (CPU) feature in MoversSuite. In the example above (Figure 36), the Item Code links to a “Dish Pack” CPU through the Material CPU Type Item setting.

Figure 37: Material Type Setup

Setup Area: MoversSuite Administration > Administration > Move Type

If you wish to include the Type of Move set within Move Information on Atlas uploads and downloads, then link Move Type Setup records to one or more of the following supported codes for each supported branch.

NOTE: The Type of Move is not included in an upload or download if more than one mapping is found or if no mapping record exists.

Setup Area: MoversSuite Administration > Customer Service > Note Type

Verify that the following Van Line Code values are established within Note Type Setup. This mapping is utilized to link incoming notes to MoversSuite types.

Figure 38: Note Type Setup

Utilize note types when adding, editing, or viewing notes from within the Notes tab.

Setup Area: MoversSuite Administration > Administration > Order Cancellation Reason

Link cancellation reasons to the Atlas interface for the following codes to support the Atlas SUDS Order Upload process.

Figure 39: Order Cancellation Reason Setup

The following is a list of known, supported Atlas codes that you can establish as order cancellation reasons.

These records are referenced by the Cancel Order Reason dialog. Of note, to get to the Cancel Order Reason dialog, at least one Order Status Setup record must be defined with the Is Cancelled Status flag set.

Figure 40: Order Status Setup

Setup Area: MoversSuite Administration > Administration > Packing Type

Set packing types for Atlas Integration in the Packing Type Setup.

Figure 41: Packing Type Setup

Define mappings for the following supported codes. Instruct the application to consider the item as a non-packing type by checking the Involves No Packing flag for the No_Packing and None type.

NOTE: The application uploads packing information that includes the packing agent along with the Packing Type.

Setup Area: MoversSuite Administration > Accounting and Financial Services > Payment Type

Link payment types to the Atlas interface for the following codes to support the Atlas Settlement Statement Import process.

Figure 42: Payment Type Setup

Manage the payment type of an order through the Billing Information tab.

Setup Area: MoversSuite Administration > Personnel > Personnel 

Update Personnel Setup records for employees that link to Atlas based on their user identifiers. Create Interface Mapping records for supported roles for each person that associates to the Atlas Integration. The following roles are supported for Atlas downloads.

For the above roles, map them the Atlas Van Lines interface and specify their sales number from the Atlas system as the User ID for the appropriate labor area. The identifier is typically the agency identifier followed by the employee code in the following format (where AAAA is for the agency and EEE for the employee code):

AAAA-EEE

For example, if the agency code is 1993 and employee code for a salesperson is 98, then you enter a User ID of 1993-098.

Figure 43: Interface Mapping tab within Personnel Setup

Manage salesperson and coordinator assignments through the Name, Address, Phone tab.

Manage OA surveyor assignments through the Agents tab.

For drivers, enter their identifier as the Driver Number within the Dispatch tab. Reference the same format as mentioned above with the agent code followed by the employee code.

Figure 44: Dispatch tab within Personnel Setup

If Auto Dispatching, then verify that the system is setup, as detailed within the Auto Dispatching topic.

If you wish to grant user access to the Atlas Statement option through the Import option within Payment Management, then assign a single branch record with the Security Module of Atlas Statement Integration within Security Profile Setup. Only one record needs to be assigned to a profile to grant users to this function. NOTE: The Atlas Statement Integration module must also be enabled (see Security Modules).

Figure 45: Security Profile Setup

View driver assignments of an order through the Agents tab and through the Long Distance Dispatch module.

Access to the Atlas options within the Tools Menu is automatic based on the configuration of the order or lead. No additional setup is needed regarding Security Modules.

Setup Area: MoversSuite Administration > Operations > Shipment Status

Define the Shipment Status codes supported by the various Atlas Integration processes within the Shipment Status Setup. Establish links between the Atlas Van Lines interface and the following supported codes.

Figure 46: Shipment Status Setup

The following table lists the codes needed to support all Atlas Integration processes. The code usage varies between each process, i.e., CMP means one thing for a flat file download and represents something else for an order download.

Additionally, those codes with Order Status of Yes are included in the Atlas SUDS Order Upload as User Managed Order Status.

Manage and track shipment progress through the Shipment Status History function.

Setup Area: MoversSuite Administration > Administration > Shipper Phone Type

Link payment types to the Atlas interface for the following codes to support the Atlas SUDS Order Download process.

Figure 47: Shipper Phone Type Setup

The following is a list of External Code values to support MoversSuite phone types.

NOTE: Atlas allows for two phone number references per location. They can be the same type, i.e., two numbers set on the order mapping to the Origin Cell type.

Manage the phone information of an order through the Name, Address, Phone tab.

See Atlas SUDS Order Download for more setup information.

Setup Area: MoversSuite Administration > Accounting and Financial Services > Statement Payment Code

Establish payment codes within Statement Payment Code Setup to support of Atlas Settlement Statement Import process.

Figure 48: Statement Payment Code Setup

Statement payment codes are utilized within the Payment Management module.

Setup Area: MoversSuite Administration > Customer Service > Valuation

Define Valuation Setup records to support exchanging valuation information between MoversSuite and Atlas. The External Code is comprised of a Valuation Type followed by a colon and the Valuation Unit. The Valuation Unit are defined as follows:

The Valuation Types are listed in the table below.

Append the Valuation Unit based on whether the Per Pound flag is checked or not. If the Per Pound flag is checked, then append the Valuation Type with a “:” followed by VPERLB (see Figure 49 below).

Figure 49: Valuation Setup

Manage valuation and related options through the Move Information tab.

Setup Area: MoversSuite Administration > Customer Service > Auto Class

Users must map Auto Class Setup records to known AutoInventory Types set forth on the Atlas side to corresponding External Codes.

The following are the Atlas AutoInventory Types and their External Codes to use for Auto Class Setup:

Setup Area: MoversSuite Administration > Customer Service > Auto Make

It is recommended that Auto Make Setup records are created that match what in in use on the Atlas side. Atlas’ field size is limited to 12 characters. Should you want to enter a value larger than 12 characters within Auto Make, ensure that the first 12 characters match what Atlas supports for Make names.

For example, if they typically enter “Honda” for make, then they should verify that something matching that is established in a MoversSuite using the Auto Make Setup to create a corresponding Auto Make record.