Unlocking Your Booking's Past: A Comprehensive Guide to Galileo Travelport History

Understanding how to retrieve the history of a booking in Galileo Travelport is crucial for travel agents and professionals. This historical data provides a complete, unalterable record of every action taken on a Passenger Name Record (PNR) or booking file, from its creation to its final state. This guide will walk you through the intricacies of accessing and interpreting this vital information.

Key Highlights

Comprehensive Record: Booking file history in Galileo meticulously logs every modification, including segment changes, fare updates, passenger details, and special requests, ensuring a complete audit trail.
Dual Access Methods: You can retrieve booking history through the user-friendly Travelport Smartpoint graphical interface or by using efficient, direct terminal commands for more experienced users.
Time-Bound Accessibility: While current bookings are readily accessible, the history of past date bookings can typically be retrieved for up to 13 months after the last travel segment has been completed.

Understanding Galileo Booking File History

The booking file history within Travelport's Galileo system is a fundamental component for managing travel reservations. It serves as an automated, chronological log of all events and changes related to a specific booking.

What is Booking File History?

Booking file history is a detailed, sequential record of every event that occurs during the "life" of a booking file (PNR). This history is generated programmatically by the Galileo system each time a transaction is completed (e.g., an "End Transact" command is entered). It captures manual modifications made by agents as well as automated system updates.

Key Characteristics:

Chronological: Entries are recorded in the order they occur.
Programmatic: The system automatically creates history entries.
Immutable: Once recorded, history entries cannot be manually altered, erased, or replaced, ensuring data integrity.

What Information is Recorded?

The history encompasses a wide array of details, providing a comprehensive overview of the PNR's evolution. This includes, but is not limited to:

Initial creation of the booking file.
Addition, modification, or deletion of segments (flights, hotels, car rentals).
Changes to passenger information (names, contact details, frequent flyer numbers).
Fare information, including fare basis codes, taxes, and ticketing details.
Addition or modification of Special Service Requests (SSRs).
Seat assignment changes.
Ticketing status updates.
Changes to phone fields.
Modifications or deletions of notepad items (confidential or historical). Note that historical notepad items are typically recorded in history only when they are changed or deleted, not when initially added.

Methods to Access Booking History

Galileo Travelport offers two primary ways to access booking file history: through the Travelport Smartpoint graphical user interface (GUI) and via traditional terminal commands (cryptic entries).

Using Travelport Smartpoint (Graphical Interface)

Travelport Smartpoint provides a more visual and often more intuitive way to interact with booking files and their history, especially for users who prefer a graphical environment.

Navigating reservation options in Travelport Smartpoint, which often includes access to booking history.

Accessing Recent Bookings

For recently accessed or created PNRs, Smartpoint often features a "Recent PNRs/Booking Files" option, typically found in the PNR Action Bar. This allows for quick retrieval without needing to re-enter the record locator.

Navigating to the History Section

Once a booking file is displayed in Smartpoint:

Look for a dedicated "History" tab, button, or menu option (e.g., "View History").
The history may be presented in a scrollable window or panel.
Smartpoint often uses an "enhanced view" for history, which provides a more structured and readable format, sometimes with interactive subcategories (often indicated by green text or buttons for different history types like "PD" for past date).

Utilizing Terminal Commands (Cryptic Entries)

For many experienced GDS users, terminal commands offer a fast and efficient way to retrieve booking history. These commands are entered directly into the Galileo terminal window, whether in a standalone emulator or within Smartpoint's terminal interface.

Step 1: Retrieve the Booking File (PNR)

Before you can view its history, the PNR must be active in your session. Use one of the following commands, replacing <Locator> or [Record Locator] with the actual six-character PNR code:

RT<Locator> (e.g., RTABC123)
RI-[Record Locator] (e.g., RI-ABC123)

Step 2: Displaying the History

Once the PNR is retrieved and displayed, use one of these general commands to show its history:

*H
H/HISTORY (or simply H/HIST)

Accessing Specific History Components

Galileo also allows you to view history for specific parts of the PNR:

*HSD: Displays history of seat data or Enhanced Booking File Servicing Field. This can be useful for tracking changes to seat assignments.
*HSI: Displays Service Information history (often related to SSRs).
*HSO: Displays history for Other Service Information (OSI) messages.

Interpreting the Booking History Display

Understanding the layout and content of the history display is key to extracting meaningful information.

Chronological Order and Key Fields

The booking history is displayed with the most recent changes typically at the top. Therefore, to understand the PNR's lifecycle from its inception, you should start reading from the bottom of the history display and work your way up.

Key fields to note in each history entry include:

CRDT (Credit): Indicates the agency, agent sign-on, or system that made the change.
RCVD (Received): Shows the source of the update (e.g., agent's initials, system identifier).
Timestamp: Each entry is marked with the date and time of the modification.

The first few lines at the very bottom of the history will show the original creation details of the PNR.

Understanding Different Entry Types

History entries will clearly delineate what was changed. For example, you might see entries indicating "SEGMENT ADDED," "NAME MODIFIED," "FARE QUOTE STORED," "TICKET ISSUED," or "PHONE FIELD DELETED." Pay attention to these descriptions to follow the sequence of events accurately.

Retrieving History for Past Date Bookings

Accessing the history of bookings where travel has already been completed (past date bookings) has specific rules and procedures.

The 13-Month Retrieval Window

A booking file generally becomes "past date" 24 hours after the completion of the last travel segment within it. While the active PNR is purged from the live system shortly after this, its history (and the PNR itself for retrieval purposes) is typically retained and accessible for up to 13 months after the last travel date.

Commands for Past Date Retrieval

To retrieve a past date PNR and its history, you'll often use a queuing mechanism:

Enter the command to request the past date PNR, using its record locator (often a pseudo record locator if the original has been archived): PQ/R-[Record Locator] (e.g., PQ/R-XYZ789)
The system may require confirmation. If prompted or as standard procedure, you might need to enter: CONFIRM (often after an asterisk prompt from the system)
Depending on the age and size of the file, it might be placed on a specific queue (e.g., Queue 1, Category Past Date). You can check this queue using a command like: Q/1*CPD
Once the PNR is retrieved from the queue and displayed, you can then use the standard history commands (*H, H/HIST) to view its history.

This video provides a visual guide on retrieving past date bookings in Galileo, which is a prerequisite for viewing their history:

This tutorial demonstrates the steps to retrieve a past date booking file in the Galileo system.

Key Considerations and Advanced Topics

Notepad History

Notepad items (NP.) allow agencies to add internal remarks. Confidential notepad items are typically only viewable by the agency that created them. Historical notepad entries (those that have been changed or deleted) are recorded in the booking file history. However, the initial addition of a historical notepad item might not always be logged in the same way as subsequent modifications.

Split Bookings

When a PNR is split (dividing a multi-passenger booking into separate PNRs), both the original and the new booking file(s) will retain the history elements up to the point of the split. The split booking file will usually include a notepad item or a remark indicating the record locator of the other related booking file(s).

Data Purging Rules

As mentioned, active PNRs are generally purged from the live system 24 hours after the last travel segment's date. However, they can remain in certain queues for a short period (e.g., 7 days) before final purging from those queues. The 13-month rule applies to the retrievability of the PNR data and its associated history from archival storage.

Programmatic Access

For developers and larger agencies, Travelport offers APIs like the Reservation Retrieve API. These can be used to programmatically fetch booking details, including historical information, allowing for integration into custom applications or reporting systems.

Visualizing Access Methods: Smartpoint GUI vs. Terminal Commands

Both Travelport Smartpoint's graphical interface and traditional terminal commands offer effective ways to access booking history, each with its own strengths. The radar chart below provides a comparative overview of these methods across several key aspects. This is an opinionated analysis based on general user experiences, where a higher score indicates a stronger performance in that category.

As the chart illustrates, Smartpoint GUI excels in ease of use for novices and visual clarity, making it approachable. Terminal commands, while having a steeper learning curve, offer superior speed for experienced users, greater granular control, and better potential for scripting or automation tasks.

Key Commands at a Glance

Here's a table summarizing some of the most common terminal commands used for retrieving bookings and their history in Galileo Travelport:

Command	Description	System Interface
`RT<Locator>`	Retrieve Booking File by its record locator. Example: `RTABC123`.	Terminal
`RI-[Record Locator]`	Alternative command to retrieve Booking File by record locator. Example: `RI-ABC123`.	Terminal
`*H` or `H/HISTORY`	Display the full booking file history once the PNR is active.	Terminal
`*HSD`	Display history of seat data or Enhanced Booking File Servicing Field.	Terminal
`*HSI`	Display Service Information history (often related to SSRs).	Terminal
`*HSO`	Display Other Service Information (OSI) message history.	Terminal
`PQ/R-[Record Locator]`	Request retrieval of a past date booking file using its pseudo record locator. Example: `PQ/R-XYZ789`.	Terminal
`CONFIRM`	Used to confirm an action, typically after certain commands like past date PNR retrieval requests.	Terminal
`Q/1*CPD`	Check Queue 1, Category Past Date. This queue is often used for holding retrieved past date bookings.	Terminal

Mindmap: The Journey to Booking History Retrieval

This mindmap provides a visual overview of the decision-making process and steps involved in retrieving booking history within the Galileo Travelport system, covering both current and past date scenarios.

mindmap root["Retrieve Galileo Booking History"] id1["Determine Booking Status"] id1_1["Current Booking (Active/Recent)"] id1_1_1["Retrieve PNR"] id1_1_1_1["Smartpoint GUI:
Use PNR Action Bar
or Search Function"] id1_1_1_2["Terminal Command:
RT<Locator> or
RI-[Locator]"] id1_1_2["Display History"] id1_1_2_1["Smartpoint GUI:
'View History' Tab/Option,
Enhanced View"] id1_1_2_2["Terminal Command:
*H, H/HIST,
*HSD (Seats), *HSI (Services)"] id1_2["Past Date Booking
(Up to 13 months post-travel)"] id1_2_1["Request PNR Retrieval (Terminal)"] id1_2_1_1["Command: PQ/R-[Locator]"] id1_2_2["Confirm & Monitor Queue (Terminal)"] id1_2_2_1["Command: CONFIRM (if prompted)"] id1_2_2_2["Command: Q/1*CPD (to check specific queue)"] id1_2_3["Once PNR is Retrieved & Active"] id1_2_3_1["Display History (as per Current Booking methods)"] id2["Interpret History Details"] id2_1["Reading Order: Bottom-up for chronology"] id2_2["Key Fields: CRDT (Agent/System), RCVD (Source), Timestamp"] id2_3["Understand Logged Actions: Segment changes, passenger info updates, fare details, notes, etc."]

This mindmap illustrates the paths from identifying the booking status to interpreting the retrieved historical data, highlighting the different tools and commands available.