This section describes the steps and setup areas that must be established to support an integration between MoversSuite and the SIRVA STS system.
PREREQUISITES:
• In addition to this setup, configuration is also required in MoversConnect. Please contact EWS Group Professional Services for setup information related to MoversConnect.
• Confirm Sirva has turned on the MoversSuite OpenAPI Create Registration process.
STEPS:
Information on each step is provided within the Technical Setup Information table following this list.
1. Establish an XML Interface for “Sirva” through XML Interface Setup and define which branch and van lines are supported. See XML Interface Setup in the Technical Setup Information table below.
2. Create the necessary systems to support upload and download requests for the SIRVA interface within XML System Setup. See XML System Setup in the Technical Setup Information table below.
3. Define other values needed referencing the Technical Setup Information table below to support identifying data to exchange between the two systems, such as creating mappings for Commodity Types to External Codes supported on SIRVA.
4. Additional setup may be needed depending on whether you integrate with SIRVA QLAB and SIRVA QPD systems as well. Refer to the following for more information:
SIRVA QLAB Integration Setup and Administration
SIRVA QPD Integration Setup and Administration
Technical Setup Information
The following table describes the administrative setup needed to support integration with SIRVA STS.
IMPORTANT |
Errors will occur during upload and download processes if setup is incomplete and/or inaccurate. Also, make sure that your MoversConnect service is up and running. Contact SIRVA for the most accurate list of supported codes and information. |
Setup |
Description | ||||||||||||||||||||||||||||||||||||||||||||||
Customers defined in SIRVA are managed as National Accounts in MoversSuite. The customer information is assigned to National Accounts through the Account Setup. Assign the SIRVA customer number to the Account Number and assign the SIRVA customer billing location number to the Default Billing Location Number (up to 15 characters). These values are referenced within the National Account section on the Billing Information tab.
You can also attach an Order Memo to a customer referencing SIRVA Master Codes. Refer to the SIRVA Customer Order Memo topic for details. | |||||||||||||||||||||||||||||||||||||||||||||||
Link address location records to SIRVA by associating External Code values to SIRVA supported codes (i.e. Location Site Code) using this setup. The following is a list of supported code values:
| |||||||||||||||||||||||||||||||||||||||||||||||
Use this setup to define agents referenced by SIRVA. In particular, the Agent ID must be in the correct format and not contain any special characters (e.g. spaces, hashes, hyphens)and set the Vanline to one supported by SIRVA. | |||||||||||||||||||||||||||||||||||||||||||||||
Link commodity records to SIRVA by associating External Code values to SIRVA supported codes (i.e. Item Make) using this setup. The following is a list of supported code values:
| |||||||||||||||||||||||||||||||||||||||||||||||
Verify that branch records associate to correct Van Line values. | |||||||||||||||||||||||||||||||||||||||||||||||
Link commodity records to SIRVA by associating Commodity Code values to SIRVA supported codes (i.e. Shipment Type). The following is a list of supported code values:
| |||||||||||||||||||||||||||||||||||||||||||||||
Define container, packing, and unpacking records and use XML Item Code Setup to map these records to container records needed for Guarantee Price Information. Refer to the XML Item Code description within this table for more information. | |||||||||||||||||||||||||||||||||||||||||||||||
Link Move Type records to SIRVA by associating External Code values to SIRVA supported codes (i.e. Hauling Authority Type) through the External Interface Mapping page. The following is a list of supported code values:
Verify that the move types associate to the correct, SIRVA-supported Branch values and the Order Number Style setting is appropriate for SIRVA orders. | |||||||||||||||||||||||||||||||||||||||||||||||
Add a note with the Van Line Code of “Sirva”. This document type will be used to record information on order registration. | |||||||||||||||||||||||||||||||||||||||||||||||
Verify that Order Number formats used for SIRVA associate to the correct Van Line. | |||||||||||||||||||||||||||||||||||||||||||||||
Define the packing type values needed for the Registration upload and associated to an order through the Packing Type field in Move Information. Currently, a type of “Full Service Pack” is supported. Setting this value will instruct the application to indicate a full pack on the Registration upload to SIRVA. | |||||||||||||||||||||||||||||||||||||||||||||||
Link Payment Method records to SIRVA by associating External Code values to SIRVA supported codes. The following is a list of currently supported codes:
| |||||||||||||||||||||||||||||||||||||||||||||||
Link Payment Type records to SIRVA by associating External Code values to SIRVA supported codes. The following is a list of currently supported codes:
| |||||||||||||||||||||||||||||||||||||||||||||||
Assign MoversSuite personnel to the SIRVA supported User ID values within the Interface Mapping tab. These values are required to match employees to SIRVA users. | |||||||||||||||||||||||||||||||||||||||||||||||
Link Product Code records to SIRVA by associating External Code values to SIRVA supported codes. The following is a list of currently supported codes:
| |||||||||||||||||||||||||||||||||||||||||||||||
Link Product Type records to SIRVA by associating External Code values to SIRVA supported codes. The following is a list of currently supported codes:
| |||||||||||||||||||||||||||||||||||||||||||||||
Set the Van Line Code to the Customer Agreement Number supplied by SIRVA, e.g. “GRR” for Guarantee Pricing. The following is a list of currently supported codes:
| |||||||||||||||||||||||||||||||||||||||||||||||
Update user access for the following two Module values:
Order Information Access Type of “Read Only” or “Full” allows user to access the Third Party Interface Order Monitor.
SIRVA Statement Integration This module controls access to the ability to view and process statements.
| |||||||||||||||||||||||||||||||||||||||||||||||
Define service type records mapped to SIRVA Van Line Code values using this setup. | |||||||||||||||||||||||||||||||||||||||||||||||
Create status records to document the progress of a shipment. The following External Codes must be defined for the SIRVA interface in order to exchange data between MoversSuite and the SIRVA STS.
| |||||||||||||||||||||||||||||||||||||||||||||||
Link Shipment Type records to SIRVA by associating Van Line Code values to SIRVA supported codes. The following is a list of currently supported codes:
| |||||||||||||||||||||||||||||||||||||||||||||||
Map an Email Type to SIRVA specifically for a Government Employee Email (“GEE”). Map the following External Code to the SIRVA interface within this setup.
This setting is referenced on SIRVA STS uploads and downloads. Refer to the SIRVA Registration Upload Content for usage.
| |||||||||||||||||||||||||||||||||||||||||||||||
Link Valuation records to SIRVA by associating External Code values to SIRVA supported codes (a.k.a. Valuation). The following is a list of supported code used by SIRVA:
| |||||||||||||||||||||||||||||||||||||||||||||||
Use this setup to define an interface for SIRVA. The SIRVA interface is referenced by other XML setup areas. This setup also allows you to define which van lines are available to exchange data between SIRVA systems and MoversSuite.
Van Line Item Define one or more supported van line by adding Van Line Items referencing the following codes:
Branch Item In addition to mapping the van lines, you can also control which branches are available based on Authority Type. Orders must be associated to a branch defined within this list, otherwise they are unable to connect to SIRVA nor will SIRVA option be available through the Tools Menu. NOTE: The External Code is not referenced for SIRVA Integration.
| |||||||||||||||||||||||||||||||||||||||||||||||
Utilize this setup to map SIRVA containers to MoversSuite containers. Refer to the XML Item Code Setup (SIRVA) topic for a complete list of support values. Create records for each supported container type setting the SIRVA support type within the XML Item Code field and link it to a MoversSuite defined code by setting the Material Type. The list of Material Type values is defined within Material Type Setup.
IMPORTANT: You can link multiple XML Item Code values to a single Material Type. However, we recommend mapping to a Material Type once to avoid creating multiple carton records for billing. Additionally, each XML Item Code value referenced through Guarantee Price Information is sent to SIRVA individually, therefore “Dish Pack” and “Glass Pack” are treated as two separate items even if they both point to the same Material Type.
IMPORTANT: Mappings are required for the Guarantee Price Information that are included when the Rate Plan links to an External Code of “GRR” in Rate Plan Setup.
NOTE: The Include imported items as Transportation revenue flag and Item Code setting are not reference for SIRVA Integration.
| |||||||||||||||||||||||||||||||||||||||||||||||
Use the XML System Setup to define the system available (QLAB, STS, et al) and the properties for processing for SIRVA. |
RELATED TOPICS:
SIRVA Field Mappings in MoversSuite
SIRVA Download Request Content
SIRVA QLAB Integration Setup and Administration
SIRVA QPD Integration Setup and Administration
SIRVA Registration Upload Content