Listed below are the Mover Suite fields that are included in a UniGroup Special Services Upload.
UniGroup requires that data be set for the following fields:
• Commodity – Must be set on the order and map to a supported code
•Order Number – Must be set. Used to extract subsidiary code (U, M), booking agent number, order sequence and year, and partial shipment code
• Shipment Type – Must be set and map to a supported code
Refer to the UniGroup Upload Setup and Administration section for a list of all requirements and see the UniGroup Special Services Upload topic for usage information.
NOTE: Only the portion of the upload that is visible within the MoversSuite application list within this content section.
Field Location in MoversSuite |
UniGroup Upload Field |
Order Number |
order_number, order_number.booking_agt_number, order_number.order_sequence_number, order_number.order_year |
Last Name/Company Name |
base_info.origin.shipper_name, base_info.destination.shipper_name |
First Name/MI |
base_info.origin.shipper_name, base_info.destination.shipper_name |
Transportation Coordinator |
base_info.coordinator_name |
For the Salesperson setting, the application references the User ID set for the employee through the Interface Mapping tab within their Personnel Setup record. This ID must link to the UniGroup interface (XML Interface Setup) and match what is established within UniGroup. Additionally, the Subsidiary Code of the Default Branch set for the Salesperson must be UniGroup affiliated; the Agent of the Default Branch set for the Personnel Setup record must link to the UniGroup Van Line (Van Line Code = U or M within Van Line Setup). | |
Salesperson |
base_info.salesman_id code_sub_agt_sape |
Moving From |
|
Location Type must map to a UniGroup supported type defined within Address Location Type Setup. | |
Location Type |
base_info.origin.location_code |
Address |
base_info.origin.street_address |
City |
base_info.origin.city |
State |
base_info.origin.state |
Postal Code |
base_info.origin.zipcode |
Moving To - Primary |
|
Location Type must map to a UniGroup supported type defined within Address Location Type Setup. | |
Location Type |
base_info.destination.location_code |
Address |
base_info.destination.street_address |
City |
base_info.destination.city |
State |
base_info.destination.state |
Postal Code |
base_info.destination.zipcode |
| |
Consignor |
base_info.origin.consignor_lessor, |
Consignor Contact Name |
base_info.origin.contact_name |
Consignor Phone |
base_info.origin.contact_phone |
Consignee |
base_info.destination.consignor_lessor |
Consignee Contact Name |
base_info.destination.contact_name |
Consignee Phone |
base_info.destination.contact_phone |
Range |
|
Load Dates (first date in spread) |
base_info.dates.load.early |
Load Dates (second date in spread) |
base_info.dates.load.late |
Load Dates Time (first in spread) |
base_info.time_load_from |
Delivery Dates (first date in spread) |
base_info.dates.deliver.early |
Delivery Dates (second date in spread) |
base_info.dates.deliver.late |
Delivery Dates Time (first in spread) |
base_info.time_delv_from |
Preferred |
|
Load Dates |
base_info.dates.load.pref |
Delivery Dates |
base_info.dates.deliver.pref |
Valuation |
|
Valuation codes must map to a UniGroup supported type defined within Valuation Setup. | |
Valuation |
base_info.valuation.code |
Per Pound |
base_info.valuation.rate_amt |
Self Haul | |
Self Haul Notes If the MoversSuite Self Haul field is set to “Yes”, then UniGroup is sent a request to haul code of “S” (self haul). If the MoversSuite Self Haul is set to “No” and the Hauling Agent is set, then UniGroup is sent a request to haul code of “R” (request to haul), otherwise a request code of “N” (no self haul/open haul) is sent. | |
Self Haul |
base_info.request_to_haul.code |
Special Instructions | |
Special Instructions (see notes below) |
special_instructions.seq, special_instructions.type, special_instructions.text |
Special Instruction Notes UniGroup allows two entries for special instructions: One for the origin and one for the destination. Each is allowed to be up to 136 characters in length and will be represented by two Sequence numbers: Sequence 1 and 2: Origin Special Instructions (up to 136 characters) Sequence 4 and 5: Destination Special Instructions (up to 136 characters) | |
Weight |
base_info.weight |
Cubic Feet |
base_info.cubic_feet |
Linear Feet |
base_info.linear_feet |
Commodity must map to a UniGroup supported type defined within Commodity Setup. | |
Commodity |
order_type, base_info.proviso, base_info.safeguard_code, base_info.commodity_code |
Shipment Type must map to a UniGroup supported type defined within Shipment Type Setup. | |
Shipment Type |
base_info.type_shipment |
Access this data is through the Shipment Details button. These fields are validated and possibly included in the upload only when the Commodity links to a supported van line code (DISP, ELEC, or SCOM). | |
Number of Pieces |
equipment_to_load.number_of_pieces |
Blanket Wrapped |
equipment_to_load.blanket_wrap |
Cartoned |
equipment_to_load.pack_in_cartons |
Crated |
equipment_to_load.pack_in_crates |
Bubble Wrapped |
equipment_to_load.bubble_wrap |
Skidded |
equipment_to_load.skid |
Size of Van |
equipment_to_load.van_size |
Decking Required |
equipment_to_load.decking |
Number of Straps |
equipment_to_load.nbr_straps |
Flat Floor |
equipment_to_load.flat_floor |
Number of Pads |
equipment_to_load.nbr_pads |
Team Required |
equipment_to_load.two_man_team |
Product Details The following information is provided through the Add Product Information dialog available from within the Shipment Information screen. The application builds a description for each record based on the following fields for each Product Details record listed. The format of the Description is as follows for orders with Commodity type that links to an External Code of ELEC (within Commodity Setup).
M:Model Number + " " + S: Serial Number + " " + D:LengthxWidthxHeight + “ - “ + W:Weight
Example: M:12345 S:AJS-209209528 D:48x24x36 W:125
The format for an order linking to any other Commodity type (DISP, SCOM) is as follows:
Description + “ - “ + Weight#
If a field is not set, then it is not included in the send. For example, if the Weight is not specified, then no dash, weight value, or pound size is built into the description sent to UniGroup. The Auto Fill Description flag within Add Product Information allows you to view and set the Description that is included in the send. UniGroup accepts a field length of 76 characters for the Description. If the Description generated for a product is larger than 76 characters, then the application truncates the Description to accommodate the size restriction. The truncation occurs in the following order:
Truncate the Description to a minimum of 10 characters (if Auto Fill Description is unchecked) If still over 76 characters, the Description is removed (if Auto Fill Description is unchecked) If still over 76 characters, the Model Number is removed If still over 76 characters, then Weight is removed For other shipment types: Truncate the Description to a minimum of 10 characters (if Auto Fill Description is unchecked)
| |
Model Number |
equipment_to_load.model_info.equipment_description |
Serial Number |
equipment_to_load.model_info.equipment_description |
Length |
equipment_to_load.model_info.size_length |
Width |
equipment_to_load.model_info.size_width |
Height |
equipment_to_load.model_info.size_height |
Weight |
equipment_to_load.model_info.equipment_description |
Description |
equipment_to_load.model_info.equipment_description equipment_to_load.model_info.size_description |
The Commodity Code should be set to “DISP” to upload the next 5 fields. Up to six trade show records can upload. | |
Origin/Destination |
show.point_of_service |
Sequence Number |
show.sequence_nbr |
Show |
show.show_code |
Booth Number |
show.booth_code |
Booth Description |
show.exhibit_description |
Up to 50 extra stop records can be included in a single upload. | |
(count of records) |
base_info.number_extra_pickups, base_info.number_extra_deliveries |
Stop Type |
extra_stop.stop_type |
Stop Number |
extra_stop.seq |
Date Range (first in spread) |
extra_stop.early_request_date |
Date Range (second in spread) |
extra_stop.late_request_date |
Contact Information |
|
Name |
extra_stop.contact_name |
Company |
extra_stop.company_name |
Phone |
extra_stop.phone |
Address Information |
|
Address |
extra_stop.address |
City |
extra_stop.city |
State |
extra_stop.state |
Zip |
extra_stop.zip |
For each agent record, the Subsidiary Code is also included in the upload for the Origin, Destination, and Hauling agents. This code is set at the Van Line code associated to the Agent Setup record, which points to the Van Line Code set within Van Line Setup. This code must be either M or U. | |
Booking Agent |
base_info.salesman_agent_nbr |
Origin Agent |
base_info.orgin.agt_number code_sub_agt_org |
Destination Agent |
base_info.destination.agt_number code_sub_agt_dest |
Hauling Agent |
base_info.request_to_haul.agent_nbr code_sub_agt_req code_sub_van_req |
Van Number |
base_info.request_to_haul.van_number |
O/D (Origin/Destination) |
base_info.SIT.code |
In Date Estimated |
base_info.SIT.date |
GBL Number |
base_info.govt_bol_number base_info.nbr_gbl_expnd |
Bases |
|
Origin |
base_info.origin.military_installation |
Destination |
base_info.destination.military_installation |
Payment Method Type must map to a UniGroup supported type defined within Payment Method Type Setup. | |
Payment Method Type |
base_info.payment_type_code, base_info.po_number |
Purchase Order Number |
base_info.po_number |
National Account |
base_info.national_acct_base_nbr, base_info.national_acct_sub_nbr |
Tariff/Rate |
base_info.tariff.number, base_info.proviso |
Section |
Base_info.tariff.section |
RELATED TOPICS:
UniGroup Special Services Upload Contents
UniGroup Special Services Upload XML