The SIRVA – Registration Request screen prompts users for a login ID for SIRVA STS as well as SPLC values for each location associated to the MoversSuite lead that was open when a user performed a SIRVA Registration Upload.
Figure 2: SIRVA - Registration Request screen
SIRVA STS requires SPLC codes to exact the location of the following types:
• Pickup (Origin Address)
• Delivery (Destination Address)
• All entered Extra Stops
The request will generate a file in the backend and transmit it to SIRVA. At the bottom of the Name, Address, Phone tab, the application will keep you updated with the status of the upload.
Figure 3: Name, Address, Phone tab
Once the process is finished, the final status can be seen using the Third Party Application Error Management screen.
Figure 4: Third Party Application Error Management screen
Optionally, you can click the button at the bottom of the Name, Address, Phone tab to open up the Third Party Application Error Management screen.
Figure 5: Name, Address, Phone tab
The application allows for multiple requests at the same time.
Messages from the SIRVA STS will typically be in all uppercase lettering and may contain the ATS Program information. The ATS Program will help indicate where the upload process encountered an error as displayed in the table below.
Cross-reference the section that indicates an error to the data sent for the lead in the format listed within SIRVA Registration Upload Content.
ATS Program Name |
Error encountered will be related to the following: |
RGR01 |
GENERAL section, contains the Booker and Self Haul Agents |
RGR02 |
Origin location and OASV/EASV information |
RGR03 |
Destination location and DASV information |
RGR04 |
Shipment Weights and Miles information |
RGR30 |
Bulk items such as VEHICLE, etc. |
RGR32 |
Container/Pack/Unpack information |
RGR34 |
Crates information |
RGR35/CRA55 |
Services like LABR, etc. |
RGR36 |
Valuation information |
RGR38 |
Storage information |