An Associated Remark is an optional, multi-item field that holds a free form string of text. Associated Remarks can be associated to any travel segment and most reservations on the Universal Record (UR), and more than one can be associated to the same segment or reservation. Associated remarks are supported in:
- Air, Hotel, Vehicle, and Passive Bookings.
- Book-on-Book (adding air/hotel/vehicle/passive to an existing PNR).
- Book-on-Book (adding air to an existing PNR) on Worldspan .
- Universal Record Modify Add and Delete (Air, Hotel, Vehicle and Passive) and Update (Air, Hotel, and Vehicle).
- Universal Record (UR) Retrieve and Import
Sample (1G): Air, Hotel, Vehicle
Request
Include the AssociatedRemark element in the Create Reservation request to add an associated remark to:
- Segments
- Reservations
Use SegmentRef to link an associated remark with an Air segment.
Use BookingTravelerRef to link an Associated Remark with an Air reservation. Only Worldspan accept BookingTravelerRef in an AssociatedRemark.
Adding Associated Remarks to an Existing Booking
When a reservation is added to an existing PNR, the AssociatedRemark and SegmentRef or BookingTravelerRef in the new request are compared to the ones in the existing reservation.
- If all associated remarks and refs match, the associated remark is not sent.
- If none match or only some match, all associated remarks that do not match are sent in the request.
Adding, Updating, and Deleting Associated Remarks
Associated Remarks can be added (post booking), updated, and deleted using UniversalRecordModifyReq and:
- UniversalAdd/AssociatedRemark
- UniversalUpdate/AssociatedRemark
- UniversalDelete with typeElement = "AssociatedRemark"
Multiple Associated Remarks can be added and updated in one request using UniversalModifyCmd. To delete multiple remarks, send multiple UniversalModifyCmd elements in the request.
Note: Worldspan only support adding and updating Associated Remarks in Air Booking using AirAdd, AirUpdate, and AirDelete.
Associated Remarks and Canceled Segments
Associated Remarks are automatically deleted in the Host if a segment is deleted. However, the associated remarks remain in the local database even though the segment is canceled.
When an Air Reservation is canceled (AirCancelReq):
- If a single segment is deleted, segment details are pulled from AirSegmentRef.
- If multiple segments under one reservation are deleted using the AirReservationLocatorCode, all associated remarks for all segments are also deleted.
When a Hotel or Vehicle Reservation is canceled (HotelCancelReq or VehicleCancelReq), the SupplierLocatorCode must be included to pull segment details, and all associated remarks for that Hotel or Vehicle segment are deleted.
Response
The associated remark is returned in the response:
- CreateReservationRsp/UniversalRecord/Reservation/AssociatedRemark
- UniversalRecordRetrieveRsp/UniversalRecord/AssociatedRemark
If an associated remark cannot be associated to a segment in a create request, because of missing segment information, the booking does not fail, but the remark is not mapped to the Host and a warning is sent in the response.
Within the AssociatedRemark in the response, Key and ProviderReservationInfoRef are populated. Also, for an Air request, AirSegmentRef is populated; for Worldspan only, BookingTravelerRef may be populated if it was sent in the request.
Synchronization occurs for associated remarks between the provider and the Universal Record.
- If the associated remark text is an exact match, nothing occurs.
- If the associated remark that is returned in the provider response does not match the remark in the UR, the provider remark is added to the UR.
- If the UR has an associated remark that is not returned in the provider response, that remark is removed from the UR.
Errors and Warnings
- If BookingTravelerRef is included for any provider other than Worldspan, a warning is returned: "Provider does not support BookingTravelerRef with AssociatedRemark."
- If multiple BookingTravelerRef elements are provided in a new booking request, a warning is returned: "Multiple BookingTravelerRef for AssociatedRemark allowed only with clustered names."
- If multiple BookingTravelerRef elements are included in a book-on-book request for an existing PNR, the system checks that the SurnameNumber of all travelers is the same.
- If the SurnameNumber is the same, the system checks that all BookingTravelerRef on the PNR for the SurnameNumber are included. If they are not, a warning is sent in the response:
- If the SurnameNumber is not the same, a warning is sent in the response: "Multiple BookingTravelerRef for AssociatedRemark allowed only with clustered names." The remark is not submitted to the host.
"Provider PNR is clustered. Please select all travelers from same cluster for AssociatedRemark." The remark is not submitted to the host."
Exceptions
Galileo and Apollo
- Galileo and Apollo supports up to 2 to 70 characters in AssociatedRemark.
- Galileo and Apollo do not support BookingTravelerRef with AssociatedRemark.
Worldspan
- Worldspan support 2 to 65 characters in AssociatedRemark.
- Worldspan supports AssociatedRemarkfor air and non-air Bookings.
- AssociatedRemarks (5RM-) in Worldspan support Name Select.
