CarHotelPNRBFModify_7_5

*Archived Transaction*

Quick Info

CarHotelPNRBFModify_7_5 builds or modifies PNRs and BFs for car and hotel segments. All record requests are optional and can be single or multiple, except End Transact. Processing terminates after the End Transact is encountered.

Review the PNRRetrieve_Notes.html for further information when working with <PNRRetrieve> (2025 Data Record). Note: This reference file was created for 2025 7.5. However, the data is mostly applicable to 2025 7.0 and 2025 7.8 as well.

Selling Car Segments

Required Data

• Car Vendor

• Car Type - Such as economy, midsize, sedan, or wagon.

• City/Airport Code - City or airport code where the car will be picked up.

• Pick-up Date - Date the car will be picked up.

• Traveler's Name

• Arrival Time - The arrival time is required, unless the car booking follows an air segment. If the car follows an air segment, the arrival time defaults to coincide with the flight arrival time.

• Drop-off Time - The drop-time time is required, unless the car booking precedes an air segment. If the car precedes an air segment, the drop-off time defaults to coincide with the flight departure time.

• Drop-off Date - If no drop-off date is indicated, the default is a one-day rental.

• Drop-off Location - If no drop-off location is indicated, the drop-off location defaults to the pick-up location. If the drop-off location is different, the drop-off location must be provided. The vendor may charge a fee for returning the car to a location other than where the rental began. Drop charge information can be found in the rules display for the selected car.

Optional Data

Optional information can be added to the car booking request.

• Corporate Discount Number - A corporate discount number between the traveler's organization and the selected vendor.

• Frequent Traveler Information

• Guarantee Information

• Awards Program Membership Number - A membership number for an awards program the traveler might have with the selected vendor.

• Special Requests - Any special requests for service or equipment, such as a car equipped with a ski rack or a cellular phone.

A car booking can be sold as either a reference sell from an availability display, or as a direct sell.

After a car is booked, the vendor acknowledges the transaction by sending back a confirmation number. This number signifies the agreement between the passenger and vendor for the car rental.

This function normally follows an availability request such as CarTypeAvail_7_0 or CarStandardAvail_6_0.

Selling Hotel Segments

After the traveler selects a hotel property, the hotel room is then sold (booked).

Required Data

Optional Data

Optional information can be added to the hotel booking request.

When a hotel booking is made from the complete availability display, the vendor acknowledges the transaction by sending back a confirmation number. This number signifies the agreement between the passenger and vendor for the hotel booking.

RoomMaster requires that a HotelCompleteAvailability_7_0 be displayed before a sell can be made. To save the hotel booking to the PNR or BF, an end transact must be implemented, using PNRBFEnd_9_0.

Form of Payment

Form of payment may be required to sell car, hotel, or cruise segments, or to guarantee hotel segments. In rare cases, smaller airline vendors may also require a form of payment to be associated with the sale of an air segment.

Retrieving a PNR or BF

It is sometimes necessary to redisplay a PNR/BF to review or modify information in the record. The two (2) most common methods of retrieving a PNR/BF are by record locator or passenger name.

• Record Locator - The record locator is the unique file code generated by the CRS when a PNR/BF is built. Retrieving by the record locator returns a specific PNR or BF.

• Passenger Name - The full or partial name of any of the passengers listed in the PNR/BF can be entered. The first character of the last name is mandatory. The more characters from the last name used, the more specific the search for records matching that criteria. The first name is optional, but when entered, must follow the last name and is delimited by a forward slash (/).
  
  This search can be less specific than that performed by Record Locator because there may be multiple records for that same individual, or there may be multiple travelers with the same last name. In these cases, the host system responds with a Similar Names List. From this list, the user can select the desired PNR/BF.

PNR/BFs can be retrieved through AgencyPNRBFDisplay_7_5 and CarHotelPNRBFModify_7_5.

After the changes are complete, PNRBFEnd_9_0 should be used to save the revised record. If the PNR/BF is retrieved for review only, or if the user decides not to save the changes, PNRBFIgnore_1_0 is used to re-file the record in its original state.

Steps

When retrieving a PNR or BF, the Record Locator may not be available. Therefore, another technique for retrieving the PNR/BF must be employed. The most common technique is to use the passenger's name to perform a similar names list query. When the list of names is returned, each name will have an associated Record Locator ID. To reduce the number of names returned in the similar names query to only a single passenger, it is possible to enter more specific criteria such as the passenger's flight number, departure date, departure location, and destination to name just a few.

Inserting Car and Hotel Segments

For readability and continuity, it is recommended that an itinerary be stored in chronological order. However, itineraries are not always booked in chronological order. For example, a user often reserves the air segment first, then reserves car or hotel segments later. To maintain continuity within the itinerary, these segments must be inserted after the appropriate air segment. "Insert After" functionality is also used when a segment has been canceled and replaced with an alternative booking.

Modifying a Hotel Segment

Itineraries will often change between original booking and actual travel, including travel dates, or preferred hotel options.

Modifying Hotel Dates

The CRS provides functionality to modify hotel booking dates without canceling and rebooking the entire hotel segment. After modification, the dates adjust forwards or backwards, as necessary.

However, it is important to note that some vendor host systems do not recognize modification functions. In these instances, the vendor host system will automatically cancel and rebook the segment. If there is no open availability, the rebook process may complete.

Modifying Optional Hotel Data

Itineraries will often change between original booking and actual travel. Hotel segments can have existing data modified or new optional data added. Although all this data is optional, it does provide supplementary details to the hotel booking that can help both the traveler and the vendor. Optional data includes: special requests, membership program numbers, and rate information.

Modifying a Hotel Room Type

This function allows the type of hotel room to be modified without canceling and rebooking the entire hotel segment. For example, when the hotel reservation was first made, only a standard room with a double bed was available, but now the passenger can book a deluxe room with a king bed.

Modifying a Car Segment

An itinerary will often change between original booking and actual travel. In addition to modifying the reserved rental dates, the type of car or optional preferences can be modified.

Rental Dates

Car segments can be modified because of changes in the travel dates, which adjust forward or backwards, as necessary. The CRS provides such date modification functionality to passengers who need to change their car booking dates. If required, the arrival and drop-off times can also be adjusted. This functionality allows them to make those changes without canceling and rebooking the entire car segment.

However, it is important to note that some vendor host systems do not recognize modification functions. In these instances, the vendor host system will automatically cancel and rebook the segment. If there is no open availability, the rebook process may not complete.

Optional Data

For car segments, changes can include modifying existing data or adding new data, such as, special requests, membership program numbers and rate information. Although this data is purely optional, it does provide supplementary details to the car booking that can help both the traveler and the rental agency.

Car Type

Car segments can be modified to change the car type for travelers who need to change from one car size to another. This functionality allows travelers to change their car selection without canceling and rebooking the entire car segment.

Received By

In terminal applications, the Received By field is part of the mandatory data that must be entered prior to committing (end transacting) a PNR or BF to the host. However, applications using Galileo's Proprietary Structured Data or XML Select Transactions include the Received By field in the commit transaction. For non-terminal transactions, this is the last step required to build a PNR or BF.

Some modifications, such as changes to the itinerary or passenger name field, require the Received By entry in addition to the End Transact. Other modifications, such as General Remarks entries, do not require a Received By entry. End Transact is not a valid command in this situation because some sort of alteration must be made to the record itself in order to End Transact.