|
Important! Only Worldspan supports invoice remarks. Previously, Worldspan accepted invoice remarks in AccountingRemark. With the implementation of InvoiceRemark in Pre-Release 11.1, any schema versions with the earlier implementation of mapping to and from AccountingRemarks with TypeInGDS="Other" and Category="FT" are no longer valid. |
An Invoice Remark is an optional field that holds a free form string of text. Invoice Remarks support Air Segment and Booking Traveler association. They can be associated to any Air, Hotel, Vehicle, or Passive reservation.
InvoiceRemark accepts a maximum of 66 characters. If the submitted text is more than 66 characters, the remark is truncated when it is sent in the request. A warning is returned in the response: "Provider supports a max of 66 characters for InvoiceRemark. The text has been truncated and submitted to host."
Request
Include the InvoiceRemark element in the Create Reservation request to add an invoice remark to:
- Air Segments
- Air, Hotel, Vehicle, and Passive Reservations
Include the InvoiceRemark element in UniversalRecordModifyReq to add, update, or delete invoice remarks.
Use AirSegmentRef to link an invoice remark with an Air segment.
Use BookingTravelerRef to link an invoice remark with an Air, Hotel, Vehicle, or Passive reservation.
Note: Association of Invoice Remarks to non-Air segments (HotelReservationRef, VehicleReservationRef, and PassiveSegmentRef) is currently not supported.
Response
The invoice remark is returned in the response:
- CreateReservationRsp/UniversalRecord/InvoiceRemark
- UniversalRecordRetrieveRsp/UniversalRecord/InvoiceRemark
Errors & Warnings
- If InvoiceRemark is provided in a request to any provider other than Worldspan, a warning is returned: "Provider does not support InvoiceRemark."
- If more than 66 characters are submitted in InvoiceRemark, the text is truncated and a warning is returned: "Provider supports a max of 66 characters for InvoiceRemark. The text has been truncated and submitted to host."
- If the AirSegmentRef is not valid, a warning is returned: "Invalid AirSegmentRef for InvoiceRemark", and the remark is not saved or submitted to the host.
- If VehicleReservationRef, HotelReservationRef, or PassiveSegmentRef are provided in the request, a warning is returned: "Provider does not support Segment Association in InvoiceRemark for Vehicle, Hotel or Passive Segments."
- If the AirSegmentRef/Key is provided in a book-on-book with HotelCreateReservationReq, VehicleCreateReservationReq, or PassiveCreateReservationReq on an existing PNR which has an Air segment, the remark is not submitted to the Host and a warning is returned: "Provider does not support AirSegment Association in InvoiceRemark for Non-Air Products."
- If multiple BookingTravelerRef elements are provided in a new booking request, a warning is returned: "Multiple BookingTravelerRef for InvoiceRemark 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, a single PNRA.GRA.GR with PNRA.GRA.GR(13-14) as "00" is submitted.
- If they are not, a warning is sent in the response: "Provider PNR is clustered. Please select all travelers from same cluster for InvoiceRemark." The remark is not submitted to the host.
- If the SurnameNumber is not the same, a warning is sent in the response: "Multiple BookingTravelerRef for InvoiceRemark allowed only with clustered names." The remark is not submitted to the host.
Exceptions
Galileo
Galileo does not support InvoiceRemark.
Apollo
Apollo does not support InvoiceRemark.
