MODERN TOOLS THAT DRIVE GROWTH EASIER WORKFLOWS FOR SMOOTHER SERVICING BUILT SPECIFICALLY FOR AGENCIES Modern Easy Travel Retailing GET MODERN TRAVELPORT+ Travelport is on a mission to simplify the complexities of an industry we have known and loved for decades. How? With technology that makes travel retailing …

CHLD -- child (this is available on Apollo (1V) CRS after June 14, 2007, and on Galileo (1G) CRS after July 30, 2007). N: Y: CHMC * no description available: N: Y: CHPC * no description available: N: Y: CKIN + freeform airport departure information: N: Y: CLUB -- no description available: N: Y: CORP -- no description available: Y: Y:

A seat map for the flight, if available, can be requested using the SeatMap_5_0 for Apollo (1V) CRS or SeatMap_6 for Galileo (1G) CRS. However, the SeatMap transaction is a stand-alone transaction, and is not a required prerequisite to seat assignment.

Passenger Name Records (PNR) and Booking Files (BF) are essential to storing and booking reservations and associated traveler information. PNRs and BFs perform essentially the same function. However, PNRs are used by the Apollo CRS, while BFs are used by the Galileo CRS.

On Galileo CRS, a user can divide passengers from a group or non-group booking using DG or DP codes respectively. Response A <PNRBFRetrieve> (2025) response returns the new PNR/BF via the PNRBFManagement transaction, with the names and the PNR/BF data that was split out from the original PNR/BF.

While queuing occurs on the Apollo ® or Galileo ® CRS, the function of working with queues is closely related to ticketing and the management of other fulfillment processes. See the PNR Queue and Retrieve eBL which automates the queue and redisplay feature.

The SeatMap_6 transaction is only available on the Galileo (1G) CRS. Apollo (1V) CRS users must still use SeatMap_5_0. Industry-specific knowledge required to understand this task.

On Galileo CRS, a user can divide passengers from a group or non-group booking using DG or DP codes respectively. Response A <PNRBFRetrieve> (2025) response returns the new PNR/BF via the PNRBFManagement transaction, with the names and the PNR/BF data that was split out from the original PNR/BF.

The host system Agent Assembly Area (AAA) must be associated with a Pseudo City Code (PCC) in order for the retrieval request to function properly. This implies that a session is based on the Galileo Terminal IDs (GTIDs) AAA Initialization Table (UAT) configuration. However:

The request and response for this task are identical on both the Apollo and Galileo systems. Industry-specific knowledge required to understand this task. This task uses an NWB structure versus a KLR structure.