|
+ Requests
|
|
+ <PNRBFRetrieveMods>
|
2024 7.0
|
|
+ <TargetCRSInfo>
|
BP01 1.0
|
|
|
|
Do not send this KLR if the PNR resides on the CRS receiving the request under the pseudo city which the Client used to logon to the Host.
|
|
<TargetCRS>
|
Alphanumeric
|
2
|
Description of Field:
Indicates which CRS the PNR or BF should be retrieved from.
Format (a-alpha, n-numeric, x-alpha/numeric):
xx
Special Format:
Field should only be used when retrieving PNRs or BFs outside user's CRS.
Use of this field to retrieve a PNR within Apollo when user is making entry from Apollo will result in an error.
Possible Values (List or Range):
'1V' = Apollo
'1G' = Galileo
How is null data specified?
Character blanks.
What does null data indicate?
Retrieval will take place in users current CRS
|
|
<BranchInd>
|
Alpha
|
1
|
Description of Field:
Indicator wherein a user can ask application to perform a branch retrieval.
Format (a-alpha, n-numeric, x-alpha/numeric):
A
Possible Values (List or Range):
'Y' = User desires branch retrieval
'N' = Do not use branch retrieval
How is null data specified?
Character Blanks
What does null data indicate?
No branch retrieve is desired
|
|
<BranchPCC>
|
Alphanumeric
|
4
|
Description of Field:
Pseudo city for branch retrieval.
Format (a-alpha, n-numeric, x-alpha/numeric):
xxxx
Possible Values (List or Range):
Character blanks = All branches
How is null data specified?
Character blanks.
What does null data indicate?
Retrieval applies to all branches if branch indicator set to "y".
|
|
<AffiliateName>
|
Alphanumeric
|
5
|
Description of Field:
Affiliate name to be used in retrieval.
Format (a-alpha, n-numeric, x-alpha/numeric):
xxxxx
Examples:
AFFL1
How is null data specified?
Character blanks
What does null data indicate?
Use of affiliate data for retrieve not desired.
|
|
|
|
+ <PNRAddr>
|
BP02 1.0
|
|
|
|
This KLR must not be sent with the Air Indexed PNR Retrieve KLR (BP03)
|
|
<FileAddr>
|
Alphanumeric
|
8
|
Description of Field:
Address of PNR or BF on it's respective CRS.
Do not use this tag.
Format (a-alpha, n-numeric, x-alpha/numeric):
xxxxxxxx
Special Format:
This is the hexadecimal displayable value for the PNR / BF's file address.
Examples:
3BD2343F
How is null data specified?
Character blanks.
What does null data indicate?
PNR / BF file address is not available.
|
|
<CodeCheck>
|
Alphanumeric
|
2
|
Description of Field:
Record Code Check for this record.
Do not use this tag.
Format (a-alpha, n-numeric, x-alpha/numeric):
xx
Special Format:
This is the hexadecimal displayable value for the PNR / BF's record code check.
If used, this field must match the PNR or BF record check exactly or retrieval will fail with an error.
Examples:
0C
How is null data specified?
Character blanks
What does null data indicate?
User does not desire use of record code check in retrieval process.
|
|
<RecLoc>
|
Alphanumeric
|
6
|
Description of Field:
This is record locator / confirmation number of the PNR or BF.
Mandatory for the request.
Format (a-alpha, n-numeric, x-alpha/numeric):
xxxxxx
Special Format:
Use this field for retrieval when PNR or BF file address is not available.
Examples:
TM9TQ7
How is null data specified?
Character blanks
What does null data indicate?
User desires use of PNR / Bf file address for retrieval.
|
|
|
|
+ <PNRAirIndex>
|
BP03 1.0
|
|
|
|
This KLR must not be sent with the Direct PNR Retrieve KLR
|
|
<AirV>
|
Alphanumeric
|
3
|
Description of Field:
Airline carrier (vendor) code
Format (x-alpha/numeric):
xxx
Special Format:
Left justified, blank filled
Examples:
UA
CO
How is null data specified?
Character blanks
What does null data indicate?
No data results in error
|
|
<FltNum>
|
Numeric
|
4
|
Description of Field:
Flight number
Format (n-numeric):
nnnn
Special Format:
Right justified, zero filled
Examples:
0001
0010
0430
6743
How is null data specified?
0
What does null data indicate?
No data results in error
|
|
<OpSuf>
|
Alpha
|
1
|
Reserved - Currently ignored
|
|
<StartAirp>
|
Alphanumeric
|
5
|
Description of Field:
Airport code of customer embarkation
Format (a-alpha):
Aaaaa
Special Format:
Left justified, blank filled
Examples:
MCI
OMA
How is null data specified?
Character blanks
What does null data indicate?
No data results in error
|
|
<EndAirp>
|
Alphanumeric
|
5
|
Description of Field:
Airport code of customer's destination
Format (a-alpha):
aaaaa
Special Format:
Left justified, blank filled
Examples:
COS
DFW
How is null data specified?
Character blanks
What does null data indicate?
No data results in error
|
|
<StartDt>
|
Numeric
|
8
|
Description of Field:
Departure date of segment
Format (n-numeric):
Nnnnnnnn
Special Format:
YYYYMMDD
For general timetable this holds the effective date.
How is null data specified?
Zero filled
What does null data indicate?
No data results in error
|
|
|
|
+ <CustNameInfo>
|
BP04 1.0
|
|
|
|
<NameType>
|
Alpha
|
1
|
Blank = Standard name
I = Infant name
G = Group / corporate name
|
|
<CustName>
|
Alpha
|
To End
|
The name to be used in the index search. The first character of the last name is mandatory. The first name is optional and must follow the last name delimited by a slash /
Examples:
S = all last names beginning with S
SMITH = all last names beginning with Smith
SMITH/JOHN = all John Smiths
|
|
|
|
+ <RequiredData>
|
BP06 1.0
|
|
|
|
+ <PNRDataIDAry>
|
Array
|
n/a
|
|
|
<PNRDataID>
|
Alphanumeric
|
2
|
PNR Data Identifier:
Identifies a specific type of PNR data to be displayed in the response.
If all PNR data available is required, this KLR should not be used.
Possible Values (List):
HL = Header lines
GI = General information
PN = Postscript note
NM = Names (includes name remarks)
FF = Frequent flyer numbers
PH = Phones
TA = Ticketing arrangement
FP = Form of payment
AS = Street address
AD = Delivery address
I = All itinerary segments
I1 = Air segments (includes open air segments)
I2 = Hotel segments
I3 = Car segments
I4 = Non-air segments
I5 = Due/paid/text segments
I6 = Flygtaxi segments
I7 = Leisureshopper segments
I8 = ARNK segments
RA = Associated itinerary remarks
RU = Unassociated itinerary remarks
ST = All seat data
SO = OSIs
SR = SSRs
CI = Customer ID
CF = Profile/Clientfile associations
CC = Custom check rules
RG = General remarks
VR = Vendor record locators
RV = Vendor remarks
RI = Associated / unassociated itinerary remarks
QM = Queue minders
DI = Document invoice/itinerary remarks
UD = Global PNR Untranslatable Data
NR = Name Related Data
UF = United Field Data
DS = Data Store Associations
EM = Email
CO = Corporate ID
GD = GIDS Data (Galileo Integrated Data Source)
TK = ETicket Data on Apollo (BP43)
MB = Multi-byte data (BP44)
|
|
|
|
|
|
|
|
+ <EticketRetrievalMods>
|
4090 1.0
|
|
+ <TicketNumber>
|
DPT1 1.0
|
|
|
|
<TktNum>
|
Numeric
|
13
|
Description of Field:
Primary Ticket Number
Format (n - numeric):
nnnnnnnnnnnnn
Special Format:
Right justified, zero filled.
Examples:
0167100004000
How is null data specified?
N/A
What does null data indicate?
No data results in error.
|
|
|
|
|
|
|
|