Retrieving Past Date Booking File

and
Booking File History - Display &
Read History

ITQLTG03/090921
 Retrieving Past Date Booking File
Answer ID KB0012429

What is Past Date Quick (Booking File)?

Past Date Quicks (PDQs) are PNRs, which have been purged from the system. A PNR is purged 24 hours after the
last date of the segment, whether that segment was cancelled or flown.

Points to Note:
 Booking Files become past date, 24 hours after their last travel date and can only be retrieved up to 13 months
after their last travel date. This is applicable to all PNRs regardless of status (passive or active).

 It is not possible to retrieve a Booking File beyond 13 months.

 PNRs will remain in queue for 7 days and will purge out of the queue programmatically after 7 days.

 Very large PNRs (greater than 28K of data) may only be returned via 24-hour retrieval. A message is displayed to
the user indicating that the record was too large for immediate retrieval and is being queued for 24 hour retrieval

 Past Dated PNRs are to be retrieved ONLY for information purpose & NOT to be rebooked again.

How to retrieve a past date Booking File?

Optional Entries to retrieve the Past Data PNR - H/PQ

Format Description
PQ/24JAN21-SHARP/RICHARD Retrieve BF by departure date and name
PQ/01JAN21–31JAN21–PALIN Retrieval by date range (max. 31 days), own branch
PQ/HTL/15JAN21–ALLEN Retrieve BF by hotel or Room Master segment
PQ/CAR/15JAN21–JOYCE Retrieve BF by Car or Car Master segment
PQ/AIR/10DEC20–MORRE/O Retrieve BF by Air segment

2
 Booking File History - Display and Read History

Answer ID KB0027083

Booking File History

Booking File History is the programmatic recording of the events taking place during the “life” of a
Booking File in a GDS.

The history of a Booking File contains a record of the initial Booking File creation as well as all
modifications (manual and programmatic) that were made since the creation. This record includes
schedule changes, queuing actions and other generated messages.

Creation and development of history is accomplished programmatically within the processor. It cannot be
created manually, erased or replaced. After a transaction is complete, (End Transact) new history data is
written to the Booking File.

The first five lines of the history show the details of the original creation of the Booking File.

***** HISTORY Z9X2L4 *****

** ONLY ACTIVE PRODUCTS EXIST **
** ORIGINAL CREATOR **
RCVD-PSGR/0048812
CRDT- LON AG 81 0826Z/06JUL

The subsequent lines show the most recent changes. After each transaction is displayed in the history there
is a credit line (CRDT), showing which agency or vendor made the change, the sine-on code used and the
date and time (in GMT) that the change took place. The Received Field (RCVD) is automatically stored.
Relevant data appears above the CRDT line.

Booking File history does not contain:

 ARNK segments
 Added phone fields (only changed or deleted phones)
 Original Booking File elements if never changed

When a Booking File is split or divided from another, the split Booking File will not carry any of the past
history. The only history element retained for this new Booking File is the original RCVD name, Date,
agent and duty sign are all from the split and divide transaction.

Flights that arrive at their destination the day after departure, will be moved to the inactive (NON - Active
Products) section of history based on only the departure date.

***** HISTORY M89JPL *****

** NON-ACTIVE PRODUCTS **
1 EK 649 K 24APR CMBDXB HK1 315 600 O*
2 EK 97 K 24APR DXBFCO HK1 910 1325 O*
** ORIGINAL CREATOR **
RCVD-MJ/0850021
CRDT- QSB AG MJ 1118Z/20APR

3
 Itinerary History
Format Description
*H Display entire history of booking file
*HI Display all Itinerary history
*HIA Display Air itinerary only
Booking File Function History
*HIC Display Car itinerary only
*HIH Display Hotel itinerary only
Format Description
*HQT Display history of Queue Trail
*HIN Display Non-air history only
*HIS Display Surface segments only
*HIT Display Tour segments only
*HIX Display Air Taxi segments only
*HVL Display Vendor Locator History

Customer Data History

Format Description
*HAD Display Written Address field history
*HCD Display all Customer Data fields history
*HF Display Form of Payment field history
*HFF Display Filed Fare field history
*HMM Display Mileage Membership history
*HN Display Name field history
*HNP Display Notepad history (when optional historical indicator was used)
*HP Display Phone field history
*HRB Display Review Booking File field history
*HRI Display Associated/Unassociated Remarks field history
*HRQ Display Enhance Booking File Servicing field history
*HSD Display Seat Data field history
*HSI Display Service Information (including Mileage Membership) field history
*HSO Display OSI field history (including Mileage Membership)
*HSR Display SSR field history
*HTD Display Ticketing Data field history
*HTE Display e-ticketing data
*HTI Display current and historical TINS data
*HVR Display Vendor Remarks field history

4
 Booking File History Codes
Answer ID KB0025265 - H/HIST

Itinerary History
Code Explanation
AS Added segment
Booking File Function History
AVL Added vendor locator
Code Explanation
XVL Cancelled vendor locator
APQ Enhanced Booking File Service re-
CF Added confirmation number (cars and hotels) quest added to pseudo city queue
CS Changed car/hotel optional data AQ Added to queue trail
HS Original segment (on Booking File creation DN Divided Name
only)
SC Changed segment status XQ Booking File removed from Queue

VLR Vendor locator reference

XS Cancelled segment

Customer Data History

Code Explanation
AA Added Related Address
AB Added Purchaser field
AC Added Action field
ACD Added Abonnement Card details
ACI Added Customer ID field (Selective Access)
AES Added Estimated Total for hotel accommodation or for car hire
AFB Added Manual Fare quote
AFQ Added Fare Quote field
AI Added Special Remarks
AG Added SSR
AM Added Mileage membership
AMC Added Mileage membership cross accrual
AMT Added Mail to
AN Added Name

5
 Code Explanation
AO Added OSI (including mileage membership)
AOB Added carrier fees
AP Added TOD MCO number
AQP Added to programmatic queue placement
AQT Added to current TAU placement
AR Added routing field
ARQ Added enhanced booking file request
AT Actual ticketing, ticket issue entry
AVI Added incoming Vendor Remark
AVO Added outgoing Vendor Remark
AW Added Written Address
CG Changed SSR
CO Changed OSI
DA Data Added
DM Data Modified
DRQ Deleted Enhance Booking File Servicing field
DR Reinstated Client file
DVI Deleted incoming Vendor Remark
DVO Deleted outgoing Vendor Remark
DU Dynamic Update request
DX Data deleted - Can identify cancellation of a marriage logic association
FP Changed or deleted FOP
HS Original segment status
HSD Denotes flights where historical seat data exists
HSI History of Service Information
IG Service info via incoming teletype
OG Service info via outgoing teletype

6
 Code Explanation
SA Added seat preceded by HSD
SC Changed Seat Data (preceded by HSD)
SX Deleted Seat Data (preceded by HSD)
XA Deleted related address
XC Changed action field
XCD Cancel Abonnement card details
XI Change fare field
XM Cancel mileage membership
XMC Cancel mileage membership cross accrual
XR Changed routing
XCI Changed Customer ID field (Selective Access)
XES Deleted Estimated Total for hotel accommodation or for car hire
XFB Cancelled Manual Fare field
XFQ Cancelled Fare Quote field
XG Deleted or cancelled SSR
XK Replaced TINS field (see Document Production)
XN Changed or deleted Name
XNP Cancelled (historical) notepad
XO Changed or deleted OSI
XP Changed or deleted Phone
XRB Cancelled Review Booking File field
XRQ Cancelled Enhanced Booking File Servicing field
XT Changed or deleted ticket arrangement field
XW Changed/deleted written address field or subfield