How to link Tours with Tour Schedules and Guests or Reservations in RMS using the Tour Links Import process.
Overview
The Tour Links Import is part 3 of 3 imports for the Tour Desk in RMS:
- Tour Import: Used to Import your Tours.
- Tour Schedule Import: Used to import the Tour Schedules, Price, and Pickup information.
- Tour Links Import: Used to Link a Tour with a Tour Schedule, and to a Guest or a Reservation.
Import Requirements
Information on the Tour Links Import requirements for RMS.
The import file must be in a comma‑delimited .csv format (field delimiter).
- A downloadable import template is available at the bottom of this article.
- If a data field within this file contains commas, it should be surrounded with "double quotes" (Text Delimiter).
Microsoft Excel can save using a .csv format that matches these requirements.
Header Row
The first row in your CSV file should be a header row containing the field names exactly as listed in the Import File Field Order table below.
RMS will treat the first row as headers and will not import it as data.
About “Legacy” Fields
The fields prefixed with Legacy are used by RMS to identify and link records that already exist in RMS or were imported from a previous (“legacy”) system.
-
LegacyTour_Id
The unique Tour identifier that was used when importing Tours into RMS (for example, the Tour ID from your legacy system or the ID used in the Tour Import). The same value must be used here so RMS can match the Tour Link to the correct Tour record. -
LegacyEntity_id and LegacyEntity_Type
Used to link the Tour to either a Reservation or a Guest in RMS:LegacyEntity_id holds the Reservation ID or Guest ID.
LegacyEntity_Type indicates which type of ID is being used (see Legacy Entity Type Format).
These are standard field names for the Tour Links Import and are required for RMS to correctly associate Tours, Schedules, and Entities.
Import File Field Order
| Order | Field Name | Field Type | Required | Max Characters | RMS Equivalent |
|---|---|---|---|---|---|
| 1 | LegacyTour_Id | Numeric | Y | 20 | Tour ID used for the Tour record imported into RMS |
| 2 | LegacyEntity_id | Numeric | Y | NA | Reservation ID or Guest ID (depending on LegacyEntity_Type) |
| 3 | LegacyEntity_Type | Numeric | Y | 1 |
Entity Type (0 = Reservation ID, 1 = Guest ID) |
| 4 | Tour_Date | Date & Time | Y | NA | Tour Date and Time |
| 5 | Tour_Operator_RMS_Client_ID | Numeric | Y | NA | RMS Client ID of the Tour Operator |
| 6 | Pickup_Point | Alpha Numeric | N | 50 | Pickup Point |
| 7 | Pickup Time | Time | N | 20 | Pickup Time |
| 8 | Tour Confirmed With Operator | Yes/No Field | N | 1 | Confirmed With Operator |
| 9 | Charge To Go On Extras Account | Yes/No Field | N | 1 | Charge On Extras Account |
| 10 | Tour Operator Voucher No | Alpha Numeric | N | 50 | Tour Operator Voucher No |
| 11 | Tour Operator Reference No | Alpha Numeric | N | 50 | Tour Operator Reference No |
| 12 | Notes(Appears On Account) | Alpha Numeric | N | 100 | Client Account Note |
| 13 | Notes(Appears On Voucher) | Alpha Numeric | N | 100 | Voucher Note |
| 14 | Notes (Appears On Tour Desk Report) | Alpha Numeric | N | 100 | Report Note |
| 15 | RMSTicket_Name_Adult | Alpha Numeric | Y | 50 | Ticket Type Description for Adults |
| 16 | RMSTicket_Name_child | Alpha Numeric | Y | 50 | Ticket Type Description for Children |
| 17 | RMSTicket_Name_Infant | Alpha Numeric | Y | 50 | Ticket Type Description for Infants |
| 18 | Adult_QTY | Numeric | Y | NA | Total number of Adults |
| 19 | Child_Qty | Numeric | Y | NA | Total number of Children |
| 20 | Infant_QTY | Numeric | Y | NA | Total number of Infant |
| 21 | Adult_unitPrice | Numeric | N | NA | Total amount charged for all Adults on the Tour |
| 22 | Child_unitPrice | Numeric | N | NA | Total amount charged for all Children on the Tour |
| 23 | Infant_unitPrice | Numeric | N | NA | Total amount charged for all Infants on the Tour |
Pricing Note
The *_unitPrice fields should contain the total amount for that passenger type on the Tour (for example, total for all Adults, total for all Children, total for all Infants), not a per‑person price. RMS will not calculate totals from quantities for these fields; you must provide the full totals you wish to charge.
Date & Time Formats
- Date fields: DD-MM-YYYY (e.g., 25-JAN-2026).
- Time fields: HH:MM:SS (e.g., 14:00:00).
Ensure all Date and Time values in your CSV use these formats.
Legacy Entity Type Format
Use the following values in LegacyEntity_Type to indicate which kind of ID is stored in LegacyEntity_id:
- 0 = Reservation ID
- 1 = Guest ID
The value in LegacyEntity_id must then be a valid Reservation ID or Guest ID in RMS, matching the type you select here.
Import Validation
To ensure that your data is clean, consistent, and ready for the Live production environment after it has been validated and imported into the Training environment, follow these steps:
- In the RMS Side Menu, search for the "Tour Bookings" Report,
- Build this report to view and check the imported Tours.
- Confirm all Tours are linked to the correct Reservations or Guests.
- Verify Tour Dates and Pickup Times match the expected format.
Check pricing fields for correct total amounts for Adults, Children, and Infants (for example, total for all Adults on each Tour). Look for missing or mismatched IDs.
Look for missing or mismatched IDs (for example, LegacyTour_Id, LegacyEntity_id, or Tour_Operator_RMS_Client_ID that do not correspond to existing records).
Downloadable Import File
The attached import file below contains the required file format for a Tour Links import.
Download the file and review the column headers.
Populate the file with the Tour Links data, ensuring that each Tour Link’s information corresponds to the appropriate column.
Save your file as a .csv before running the import.
Previous Article: |
Next Article: |
Comments
0 comments
Please sign in to leave a comment.