The following table describes the administrative setup needed to support integration with SIRVA sHub.
|
Important |
|
Errors will occur during upload and download processes if setup is incomplete and/or inaccurate. Contact SIRVA the most accurate list of supported codes and information. |
|
Note |
|
Refer to SIRVA QLAB Integration Setup and Administration for information on setting up SIRVA QLAB Integration. |
|
Setup |
Description | ||||||||||||||||||||||||||||||||||||||||||||||
|
Set the Account # field to a SIRVA-supported account for all needed National Account records. The Account # must be in the correct format and contain no special characters, such as hashes or spaces. | |||||||||||||||||||||||||||||||||||||||||||||||
|
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. | |||||||||||||||||||||||||||||||||||||||||||||||
|
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. | |||||||||||||||||||||||||||||||||||||||||||||||
|
Link Note Type records to SIRVA by associating Van Line Code values to SIRVA supported codes. The following is the currently supported code:
| |||||||||||||||||||||||||||||||||||||||||||||||
|
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 sHub.
| |||||||||||||||||||||||||||||||||||||||||||||||
|
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:
| |||||||||||||||||||||||||||||||||||||||||||||||
|
Link Valuation records to SIRVA by associating External Code values to SIRVA supported codes (a.k.a. Valuation). | |||||||||||||||||||||||||||||||||||||||||||||||
|
Use this setup to define supported van lines for SIRVA by branch. The application will only support SIRVA orders with a van line and branch that match the combination of Van Line and Mapped Branches defined within this setup. The following is a list of supported code values:
| |||||||||||||||||||||||||||||||||||||||||||||||
|
Set SIRVA supported codes (i.e. Container Type) within XmlItemCode fields to link to a MoversSuite material type record (defined in Material Type Setup). This mapping is required for the Guarantee Price Information that is included when the Rate Plan links to an External Code of “GRR” in Rate Plan Setup. Important: The application allows for multiple XmlItemCode values for the same MSS Material Type. However, each XmlItemCode referenced through Guarantee Price Information will be sent to SIRVA individually, therefore “Dish Pack” and “Glass Pack” will be sent as two separate CPU entries. To avoid sending and creating multiple carton records for an individual MoversSuite material, make sure a single mapping exists for each MSS Material Type to a SIRVA XmlItemCode value.
Note: The application does not reference MSS Item Code or Transportation Flag settings for SIRVA.
| |||||||||||||||||||||||||||||||||||||||||||||||
|
Use this setup to define the systems available for SIRVA along with supporting options. |
RELATED TOPICS:
MoversSuite Fields Referenced by SIRVA
SIRVA Download Request Content
SIRVA QLAB Integration Setup and Administration
SIRVA Registration Upload Content