PNRBFManagement_9

*Archived Transaction*

Quick Info

PNRBFManagement_9 is used to manage a PNR/Booking File (BF). A number of tasks related to building/modifying/displaying traveler data, such as air, car, and hotel segments are combined in this transaction, including:

Creating and Maintaining PNR/BF Data

• Creating and maintaining Primary PNR/BF data, such as names, phones, addresses, and profiles.

• Creating and maintaining Secondary PNR/BF data, such as such as form of payment, customer and corporate identifiers, and various types of remarks including general remarks, SSRs, OSI, and ticketing remarks.

• Retrieving a PNR/BF by record locator.

• Retrieving a PNR/BF by a carrier code and flight.

• Retrieving a currently active PNR/BF.

• Retrieving a PNR/BF by the traveler name.

• Displaying a PNR/BF.

• Finishing (end transacting) an active PNR/BF, allowing PNR/BFs to be created or modified, and then committed to the CRS in the same call. End transacting is required to store changes on the CRS; changes that are not end transacted are not valid.

• Ignoring (ignore transacting) changes to a PNR/BF.

• Ignoring (Ignore transacting) and re-retrieving active PNR/BF.

Manipulating Air, Car, and Hotel Segments

• Inserting segments.
• Canceling segments.
• Modifying or deleting hotel segment data, including reservation dates, room types, and optional data.
• Modifying or deleting car segment data, including reservation dates, car types, and optional data.
• Selling air, car, and hotel segments.
• Performing passive segment sells.
• Performing direct air segment sells.
• Modifying air segments through class and date changes.
• Modifying air segments through rebooking.
• Selling seats for air segments.
• Reordering itinerary requests

Manipulating Fares

• Storing fare quotes (ATFQ/FF).
• Verifying fare quotes.
• Re-pricing fares quotes.
• Canceling stored fares.
• Creating pretend fares.
• Retain a previously stored fare.
• Sets the tariff display default to a new city code

The tasks available in this transaction are optional and, in many cases, can have more than one occurrence. Tasks are processed in the order received which, in turn, creates the ordering of the air, car and hotel segments. A logical combination of tasks is often required to create or maintain the PNR/BF. For example, an Ignore Active PNR/BF request after an Air Segment Sell via Direct Sell task, and prior to a Finish Active PNR/BF will effectively cancel the air segment.

Unless a specific task order is prescribed by the business logic, there is no strictly defined order for tasks. However, the last task to be processed must always be followed by the Finish Active PNR/BF task to validate the changes to the CRS. If the PNR/BF is not finished (end transacted), new or modified data is not committed to the CRS.

For additional information on PNR/BF Maintenance for Primary and Secondary Fields, see the Primary and Secondary Field Notes topic.

Note: PNRBFManagement_9 replaces PNRBFReservationModify_5_0_2, includes all of the functionality available in PNRBFReservationModify_5_0_2, as well as additional functions. In turn, PNRBFReservationModify_5_0_2 combined existing functionality from several separate transactions into a single transaction. In addition to PNRBFReservationModify_5_0_2, see the Archived Transactions list to see all the transactions that PNRBFManagement_9 replaces.