|
+ Responses
|
|
+ <SegCancel>
|
1041 6.0
|
|
|
|
|
1041: - Segment Cancel Response
Version: 06.00
|
SegCancelBlkCnt
Structured data only.
Not in XML.
|
Numeric
|
2
|
Number of canceled blocks returned
|
HtlSegCancelBlkCnt
Structured data only.
Not in XML.
|
Numeric
|
2
|
Number of hotel confirmation numbers returned
|
|
+ <SegCancelAry>
|
Array
|
n/a
|
|
|
+ <SegCancelInfo>
|
FieldSet
|
n/a
|
|
|
<Tok>
|
Numeric
|
2
|
Right justified, zero filled.
|
|
<SegNum>
|
Numeric
|
2
|
PNR segment number canceled. Right justified.
|
|
<Status>
|
Alpha
|
2
|
Status from cancel
XX= Successfully canceled
DM= Cancel denied due to marriage logic
NO= Error
|
|
|
|
|
|
+ <HtlSegCancelAry>
|
Array
|
n/a
|
|
|
+ <HtlSegCancelInfo>
|
FieldSet
|
n/a
|
|
|
<SegNum>
|
Numeric
|
2
|
Hotel segment number canceled
|
CancelNumLen
Structured data only.
Not in XML.
|
Alphanumeric
|
2
|
Length of field to follow. If length is zero Conf Number does not exist.
|
|
<CancelNum>
|
Alphanumeric
|
VL
|
Actual confirmation number returned.
|
|
|
|
|
|
|
|
|
+ <PNRBFRetrieve>
|
2025 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)
|
|
|
|
|
|
+ <HeaderLine>
|
BP07 1.0
|
|
|
|
<Text>
|
Alphanumeric
|
To End
|
Free format text
|
|
|
|
+ <GenPNRInfo>
|
BP08 1.0
|
|
|
|
<FileAddr>
|
Alphanumeric
|
8
|
Blanks if new PNR which has not been End-Transacted
|
|
<CodeCheck>
|
Alphanumeric
|
2
|
Blanks if new PNR which has not been End-Transacted
|
|
<RecLoc>
|
Alphanumeric
|
6
|
Blanks if new PNR which has not been End-Transacted
|
|
<Ver>
|
Numeric
|
3
|
PNR version number (hold counter). Starts at zero.
|
|
<OwningCRS>
|
Alphanumeric
|
2
|
"1V" = Apollo
"1G" = Galileo
|
|
<OwningAgncyName>
|
Alpha
|
24
|
Name of agency which owns the PNR.
|
|
<OwningAgncyPCC>
|
Alphanumeric
|
4
|
Pseudo city code of the agency owning this PNR, i.e. 0CG7, 1GK5. Right justified, zero filled
|
|
<CreationDt>
|
Numeric
|
8
|
YYYYMMDD
|
|
<CreatingAgntSignOn>
|
Alphanumeric
|
8
|
Sign-on code of the agent who created the PNR
|
|
<CreatingAgntDuty>
|
Alphanumeric
|
2
|
Duty code of the agent who created the PNR
|
|
<CreatingAgncyIATANum>
|
Numeric
|
8
|
IATA number of the agency where the PNR was created
|
|
<OrigBkLocn>
|
Alpha
|
5
|
Location where the booking was created. Consists of a 3 character city code followed by a 2 character station code.
|
|
<SATONum>
|
Alphanumeric
|
4
|
SATO number of the original booking location
|
|
<PTAInd>
|
Alpha
|
1
|
Indicates if PTA (Prepaid Ticket Advice) is attached to the PNR.
'Y' or 'N'
Blank if data not available
|
|
<InUseInd>
|
Alpha
|
1
|
Indicates if the PNR is currently being viewed by other agent(s).
'Y' or 'N'.
Blank if data not available
|
|
<SimultaneousUpdInd>
|
Alpha
|
1
|
Indicates if the PNR has been end transacted by another agent while being viewed by this agent.
'Y' or 'N'
Always blank
|
|
<BorrowedInd>
|
Alpha
|
1
|
Indicates if this is a borrowed PNR.
'Y' or 'N'.
Blank if data not available
|
|
<GlobInd>
|
Alpha
|
1
|
Indicates if this is a global PNR.
'Y' or 'N'.
Blank if data not available
|
|
<ReadOnlyInd>
|
Alpha
|
1
|
Indicates if this is a read only PNR which cannot be updated.
'Y' or 'N'.
Blank if data not available
|
|
<FareDataExistsInd>
|
Alpha
|
1
|
Indicates if the PNR contains fare data
'Y' or 'N'.
Blank if data not available
|
|
<PastDtQuickInd>
|
Alpha
|
1
|
Indicates if the PNR has been retrieved from the offline archive database. PDQ PNRs do not contain active segments and cannot be updated.
'Y' or 'N'.
Blank if data not available
|
|
<CurAgncyPCC>
|
Alphanumeric
|
4
|
Pseudo city code this agent is currently signed in to.
Right justified, zero filled.
Blank if agent not signed in to a pseudo city.
|
|
<QInd>
|
Alpha
|
1
|
'Y' This PNR/BF retrieved from queue
'N' not retrieved from queue
|
|
<TkNumExistInd>
|
Alpha
|
1
|
'Y' or 'N' - Indicator whether tickets numbers were issued against this PNR/BF
|
|
<IMUdataexists>
|
Alpha
|
1
|
'Y' or 'N' - Indicator whether IMU data exists for this PNR/BF
|
|
<ETkDataExistInd>
|
Alpha
|
1
|
'Y' or 'N' - Indicator whether Electronic Ticketing data exists for this PNR/BF
|
|
<CurDtStamp>
|
Alpha
|
8
|
Current date in YYYYMMDD format
|
|
<CurTmStamp>
|
Alpha
|
6
|
Current time in HHMMSS format
|
|
<CurAgntSONID>
|
Alpha
|
7
|
Current agent SON ID
|
|
<TravInsuranceInd>
|
Alpha
|
1
|
Indicates Pseudo has Preferred Travel Insurance Option
|
|
<PNRBFTicketedInd>
|
Alpha
|
1
|
Indicates the PNR or BF has been ticketed
|
|
|
|
+ <PostScript>
|
BP09 1.0
|
|
|
|
<Text>
|
Alphanumeric
|
To End
|
Description of Field:
Postscript text that is added to PNR to usually hi-light some needed action.
Format (a-alpha, n-numeric, x-alpha/numeric):
XXXXXXX XXXX etc.
Special Format:
Freeform text. Single item field. (Multiple occurrences not allowed.)
Used only on Apollo (1V)
Examples:
BOOK HOTEL NEAR AIRPORT
How is null data specified?
Character Blanks
What does null data indicate?
Probable error
If variable length, specify the maximum allowable length.
63
|
|
|
|
+ <LNameInfo>
|
BP10 1.0
|
|
|
|
<LNameNum>
|
Numeric
|
2
|
Description of Field:
Unique sequential number identifying this last name
Format (a-alpha, n-numeric, x-alpha/numeric):
All numeric
Examples:
Smith = 01
Jones = 02
How is null data specified?
Character blanks or zeroes
What does null data indicate?
Probable error
|
|
<NumPsgrs>
|
Numeric
|
2
|
Description of Field:
Number of people included with this last name field (number of first names associated with this last name)
Format (a-alpha, n-numeric, x-alpha/numeric):
All Numeric
Examples:
Smith/Pat/Deb = 2
Smith/Dan = 1
Special Format:
Note that number in party applies to last name entries. Even if last names are the same, if they were input separately, they will have an associated number in party.
How is null data specified?
Character blanks or zeroes
What does null data indicate?
Probable error
|
|
<NameType>
|
Alpha
|
1
|
Description of Field:
Name type
Format (a-alpha, n-numeric, x-alpha/numeric):
All Alpha
Possible Values (List or Range):
Blank = Standard
G = Group/Corporate
I = Infant
P = Employee positive space
Z = Employee standby
How is null data specified?
Character Blanks
What does null data indicate?
Standard Adult
|
|
<LName>
|
Alpha
|
To End
|
Description of Field:
Last or surname of person in PNR or BF.
Format (a-alpha, n-numeric, x-alpha/numeric):
All Alpha
Special Format:
Numbers not allowed
Spaces are removed
How is null data specified?
Character Blanks
What does null data indicate?
Probable error
If variable length, specify the maximum allowable length.
Minimum of 2 characters
Maximum of 52 characters
|
|
|
|
+ <FNameInfo>
|
BP12 1.0
|
|
|
|
<PsgrNum>
|
Numeric
|
2
|
Description of Field:
Sequential number identifying this first name relative to the associated Last Name KLR.
Format (a-alpha, n-numeric, x-alpha/numeric):
All Numeric
Examples:
Smith/A = 01
Smith/B = 02
Jones/A = 01
Jones/B = 02
How is null data specified?
Character Zeroes
What does null data indicate?
Probable error
|
|
<AbsNameNum>
|
Numeric
|
2
|
Description of Field:
Unique sequential number identifying this first name.
Format (a-alpha, n-numeric, x-alpha/numeric):
All numeric
Special Format:
Number is assigned dynamically and thus can float/change as number of names in PNR / BF change.
Examples:
Smith/A = 01
Smith/B = 02
Jones/A = 03
Jones/B = 04
How is null data specified?
Character zeroes
What does null data indicate?
Absolute Name Number unavailable
|
|
<FName>
|
Alpha
|
To End
|
Description of Field:
First Name
Format (a-alpha, n-numeric, x-alpha/numeric):
All Alpha
Special Format:
First name required
Minimum length is 1
How is null data specified?
Character Blanks
What does null data indicate?
Probable error
If variable length, specify the maximum allowable length.
52 on Galileo (1G)
55 on Apollo (1V)
|
|
|
|
+ <NameRmkInfo>
|
BP13 1.0
|
|
|
|
<LNameNum>
|
Numeric
|
2
|
Description of Field:
This field always contains the Last Name Element Number from the Last Name KLR to which the remark applies.
Format (a-alpha, n-numeric, x-alpha/numeric):
nn
How is null data specified?
Character Blanks or Zeroes
What does null data indicate?
Probable Error
|
|
<PsgrNum>
|
Numeric
|
2
|
Description of Field:
First name element number within Last name. (Used only on 1G, Galileo)
Format (a-alpha, n-numeric, x-alpha/numeric):
nn
Special Format:
Unused on Apollo (1V)
How is null data specified?
Character Blanks or Zeroes
What does null data indicate?
Field unused (1V) Apollo
Probable error (1G) Galileo
|
|
<AbsNameNum>
|
Numeric
|
2
|
Description of Field:
Absolute name number this remark applies to, corresponds to overall first name number. (Used on 1G, Galileo)
Format (a-alpha, n-numeric, x-alpha/numeric):
nn
Special Format:
Unused on Apollo (1V)
How is null data specified?
Character Blanks or Zeroes
What does null data indicate?
Field unused (1V) Apollo
Probable error (1G) Galileo
|
|
<NameRmk>
|
Alphanumeric
|
To End
|
Description of Field:
Free form text
Format (a-alpha, n-numeric, x-alpha/numeric):
xxxxxxxxxxxxxxxx
How is null data specified?
Character Blanks
What does null data indicate?
Probable Error
If variable length, specify the maximum allowable length.
Minimum of 2 characters
Maximum of 33 characters
|
|
|
|
+ <FreqCustInfo>
|
BP14 1.0
|
|
|
Start Definition of Frequent Flyer Number KLR
The next three fields identify which name the frequent flyer number applies to.
|
|
<LNameNum>
|
Numeric
|
2
|
Description of Field:
This field always contains the Last Name Element Number from the applicable Last Name KLR
Format (a-alpha, n-numeric, x-alpha/numeric):
nn
How is null data specified?
Character Blanks or Zeroes
What does null data indicate?
Probable Error
|
|
<PsgrNum>
|
Numeric
|
2
|
Description of Field:
This field always contains the Passenger Element Number from the applicable First Name KLR
Format (a-alpha, n-numeric, x-alpha/numeric):
nn
Special Format:
Unused on Apollo (1V)
How is null data specified?
Character Blanks or Zeroes
What does null data indicate?
Probable Error (1G)
Unused on Apollo (1V)
|
|
<AbsNameNum>
|
Numeric
|
2
|
Description of Field:
This field always contains the Absolute Name Element ID from the applicable First Name KLR
Format (a-alpha, n-numeric, x-alpha/numeric):
nn
Special Format:
Unused on Apollo (1V)
How is null data specified?
Character Blanks or Zeroes
What does null data indicate?
Probable Error (1G)
Unused on Apollo (1V)
|
|
<FreqCustV>
|
Alphanumeric
|
3
|
Description of Field:
ID of vendor who has issued the Frequent Traveler or Mileage Membership's card.
Format (a-alpha, n-numeric, x-alpha/numeric):
xxx
Examples:
'UA '
'BA '
How is null data specified?
Character blanks
What does null data indicate?
Possible error
|
|
<FreqCustStatus>
|
Alphanumeric
|
2
|
Description of Field:
Freq. Flyer / Mileage Membership status of the passenger.
Format (a-alpha, n-numeric, x-alpha/numeric):
xx
Possible Values (List or Range):
"VP" = VIP.
"1K" = 100,000 Mile Flyer.
"1P" = Premier Executive.
"2P" = Premier.
"EM" = Premier Emeritus.
Blanks = Regular Member.
How is null data specified?
Character Blanks
What does null data indicate?
Regular Member
|
|
<FreqCustNum>
|
Alphanumeric
|
To End
|
Description of Field:
Frequent Flyer or Mileage Membership Account Number
Format (a-alpha, n-numeric, x-alpha/numeric):
xxxxxxxxxxxxxxxxxx
Examples:
VF222865 (Continental)
01110455277 (United)
2165506221 (Delta)
How is null data specified?
Character Blanks
What does null data indicate?
Probable error
If variable length, specify the maximum allowable length.
Maximum length = 25 (1G)
Minimum length = 2 (1G)
Maximum length = 16 (1V)
Minimum length = 6 (1V)
|
|
|
|
+ <PhoneInfo>
|
BP16 1.0
|
|
|
|
<PhoneFldNum>
|
Numeric
|
3
|
Description of Field:
Phone Item Number
Format (a-alpha, n-numeric, x-alpha/numeric):
All Numeric
Examples:
001
How is null data specified?
Character blanks or zeroes
What does null data indicate?
Probable error
|
|
<Pt>
|
Alpha
|
5
|
Description of Field:
City code of phone number.
Format (a-alpha, n-numeric, x-alpha/numeric):
All Alpha
Examples:
DEN
LHR
How is null data specified?
Character blanks
What does null data indicate?
City field unavailable
|
|
<Type>
|
Alpha
|
1
|
Description of Field:
Type of phone data in this phone item.
Format (a-alpha, n-numeric, x-alpha/numeric):
Alpha
Possible Values (List or Range):
R = Residence (home).
B = Business.
A = Agency (1V)
A = Accommodation (1G)
H = Hotel
N = No contact
F = Fax
T = Travel Agency (1V)
E = Email Address (1G)
P = Phone nbr not known (1G)
N = No contact (1G)
All codes above except for A and T should be assumed to be associated with the passenger. For example, F should be interpreted as the fax number of a passenger rather than the fax number of an agency.
How is null data specified?
Character blanks
What does null data indicate?
Data unavailable
|
|
<Phone>
|
Alphanumeric
|
To End
|
Description of Field:
Phone data
Format (a-alpha, n-numeric, x-alpha/numeric):
xxxxxxxxxxxxxxxx
Special Format:
Freeform text
Examples:
Denb/3033976000
LHRf/44456789
How is null data specified?
Character blanks
What does null data indicate?
Data unavailable
If variable length, specify the maximum allowable length.
Overall max length 83 (Apollo)
Overall max length 53 on 1st two phone items, 66 on all others (Galileo)
|
|
|
|
+ <AddrInfo>
|
BP17 1.0
|
|
|
|
<Addr>
|
Alphanumeric
|
To End
|
Description of Field:
Street address. (This is a single item field. There should never be multiple occurrences of this KLR.)
Format (a-alpha, n-numeric, x-alpha/numeric):
xxxxxx@xxxxxx@xxxxx Z/xxxxx
Special Format:
Address format should follow format:
Apollo (1V) CRS: First & last name @ St address @City State Z/Zip code
Or
Galileo (1G) CRS: First & last name * St address *City State P/Postal Code
How is null data specified?
Character blanks
What does null data indicate?
Probable error.
If variable length, specify the maximum allowable length.
7 sub fields maximum. Sub fields have a minimum length of 1 and a maximum length of 37. Overall length of field cannot exceed 190. Zip code required. (1V-Apollo)
5 sub fields maximum. Sub fields have a minimum length of 1 and a maximum length of 37. Overall length of field cannot exceed 119. Postal code required. (1G-Galileo)
|
|
|
|
+ <DeliveryAddrInfo>
|
BP18 1.0
|
|
|
|
<DeliveryAddr>
|
Alphanumeric
|
To End
|
Description of Field:
Delivery Address for Passenger if paper ticket is issued.
Format (a-alpha, n-numeric, x-alpha/numeric):
xxxx
Special Format:
Address is different on the Apollo (1V) and Galileo (1G) CRS. See Examples.
Examples:
1V
JAN TYLER @6901 S. HAVANA @CENTENNIAL CO Z/80112
1G
JAN TESTO*6901 S. HAVANA *CENTENNIAL CO*USA P/80112
What does null data indicate?
No data results in error
If variable length, specify the maximum allowable length.
Additional sub fields can be specified to a maximum of 7. Sub fields have a minimum length of 1 and a maximum length of 37.
|
|
|
|
+ <OSI>
|
BP19 1.0
|
|
|
|
<GFAXNum>
|
Numeric
|
3
|
Number of GFAX (General Facts) item in a-06-AAA (Agent Assembly Area).
|
|
<OSIV>
|
Alphanumeric
|
3
|
Airline Code or YY if OSI applies to all airlines in the PNR
|
|
<OSIMsg>
|
Alphanumeric
|
To End
|
|
|
|
|
+ <NonProgramaticSSR>
|
BP20 1.0
|
|
|
|
<GFAXNum>
|
Numeric
|
3
|
Number of GFAX (General Facts) item in a-06-AAA (Agents Assembly Area).
|
|
<SSRCode>
|
Alpha
|
4
|
Non-programmatic SSR Code
|
|
<Vnd>
|
Alphanumeric
|
3
|
Vendor providing this service.
|
|
<Status>
|
Alpha
|
2
|
Current status of this service request.
See Galileo Formats Guide for a list of valid status codes.
Blank if not applicable to this SSR Code
|
|
<NumRequired>
|
Numeric
|
2
|
Number of services required.
Blank if not applicable to this SSR Code
|
|
<SSRText>
|
Alphanumeric
|
To End
|
Formatted according to AIRIMP standards
|
|
|
|
+ <ProgramaticSSR>
|
BP21 1.0
|
|
|
|
<GFAXNum>
|
Numeric
|
3
|
Number of GFAX (General Facts) item in a-06-AAA (Agents Assembly Area).
|
|
<SSRCode>
|
Alpha
|
4
|
Refer to the list at the end of this section for all SSR Codes.
|
|
<Status>
|
Alpha
|
2
|
Status of the request
|
|
<SegNum>
|
Numeric
|
3
|
Segment Number of the segment to which this SSR applies.
|
|
+ <AppliesToAry>
|
Array
|
n/a
|
|
|
+ <AppliesTo>
|
FieldSet
|
n/a
|
|
|
<LNameNum>
|
Numeric
|
2
|
Unique sequential number identifying the last name grouping.
Eg: Smith=1, Jones=2
|
|
<PsgrNum>
|
Numeric
|
2
|
Sequential number identifying a passenger within a last name grouping.
Eg: Smith/A=1, Smith/B=2, Jones/A=1, Jones/B=2
|
|
<AbsNameNum>
|
Numeric
|
2
|
FOR USE ON GALILEO CORE ONLY:
Unique sequential number identifying each passenger irrespective of last name.
Eg: Smith/A=1, Smith/B=2, Jones/A=3, Jones/B=4
|
|
|
|
|
|
|
|
+ <ProgramaticSSRText>
|
BP22 1.0
|
|
|
|
<Text>
|
Alphanumeric
|
To End
|
|
|
|
|
+ <CustID>
|
BP23 1.0
|
|
|
|
<Text>
|
Alphanumeric
|
To End
|
|
|
|
|
+ <ProfileClientFileAssoc>
|
BP24 1.0
|
|
|
|
<CRSID>
|
Alphanumeric
|
2
|
CRS where Profile/Client File resides.
1V = Apollo
1G = Galileo
|
|
<ActiveInd>
|
Alpha
|
1
|
Indicates whether this Profile/Client File is active.
Y = Active
N = Inactive
Blank if not known.
|
|
<PrefsInd>
|
Alpha
|
1
|
Indicates whether this Profile/Client File has Travelscreen preferences attached.
Y = Preferences exist
N = No preferences exist
Blank if not known.
|
|
|
|
+ <CustomCheckRules>
|
BP25 1.0
|
|
|
|
+ <RuleAry>
|
Array
|
n/a
|
|
|
+ <Rule>
|
FieldSet
|
n/a
|
|
|
<PCC>
|
Alphanumeric
|
4
|
Right aligned zero filled. Eg. 06MY
|
|
<RuleName>
|
Alphanumeric
|
10
|
Left aligned blank filled
|
|
<StatusInd>
|
Alphanumeric
|
1
|
Blank = Active
S = Suspended
|
|
|
|
|
|
|
|
+ <GenRmkInfo>
|
BP26 1.0
|
|
|
|
<CreationDt>
|
Alphanumeric
|
8
|
YYYYMMDD
Blank if not available
|
|
<CreationTm>
|
Numeric
|
4
|
HHMM
Blank if not available
|
|
<GenlRmkQual>
|
Alphanumeric
|
2
|
Blank if no qualifier exists
|
|
<GenRmk>
|
Alphanumeric
|
To End
|
|
|
|
|
+ <VndRecLocs>
|
BP27 1.0
|
|
|
|
+ <RecLocInfoAry>
|
Array
|
n/a
|
|
|
+ <RecLocInfo>
|
FieldSet
|
n/a
|
|
|
<TmStamp>
|
Numeric
|
4
|
Description of Field:
The Time Stamp is the time the reservation is received from the Vendor and is stored in the Booking.
Format (n-numeric):
nnnn
Special Format:
HHMM
HH = hours
MM = minutes
How is null data specified?
Character Blanks
What does null data indicate?
Blank indicates that no Time Stamp value exists.
|
|
<DtStamp>
|
Numeric
|
8
|
Description of Field:
The Date Stamp is the date the reservation is received from the Vendor and is stored in the Booking.
Format
CCYYMMDD
Special Format:
Data will be in CCYYMMDD where
CC = century
YY = current year
MM = numeric month value
DD = numeric day of the month value
How is null data specified?
Character Blanks
What does null data indicate?
Data not available.
|
|
<Vnd>
|
Alphanumeric
|
3
|
Description of Field:
Vendor code of vendor making the request.
Format (x-alpha/numeric):
xxx
Examples:
NCL
How is null data specified?
No data results in error
What does null data indicate?
No data results in error
|
|
<RecLoc>
|
Alphanumeric
|
9
|
Description of Field:
The (Vendor) Record Locator is the Record Locator of the Booking that exists on the Vendor system.
For the Apollo CRS for UA it is the same since the UA bookings are stored on Apollo, hence the Bookings are one in the same.
For the Galileo CRS it is the locator of the Booking on the Apollo core.
For OA flights, the Vendor Locator is the association booking in the other system such as Sabre, Amadeus, etc.
Format (a-alpha, n-numeric, x-alpha/numeric):
xxxxxxxxx
Special Format:
Left Justified Blank Padded
Examples:
KFZMFS
How is null data specified?
Character blanks
What does null data indicate?
PNR or BF has not been created.
|
|
|
|
|
|
|
|
+ <VndRmk>
|
BP28 1.0
|
|
|
|
<DtStamp>
|
Numeric
|
8
|
YYYYMMDD
|
|
<RmkType>
|
Alpha
|
1
|
O = Outgoing - remark originated from the agent
I = Incoming - remark originated from the vendor
|
|
<VType>
|
Alpha
|
1
|
A = Air
H = Hotel
C = Car
L = Leisure shopper
N = Other
|
|
<Rmk>
|
Alphanumeric
|
To End
|
|
|
|
|
+ <QMinder>
|
BP29 1.0
|
|
|
|
<QCat>
|
Alphanumeric
|
2
|
Either 2 alpha characters or 2 numeric characters. A single numeric will have a leading zero. Alphanumeric combinations are not allowed.
Blank if does not exist
|
|
<Text>
|
Alphanumeric
|
To End
|
Optional
|
|
|
|
+ <Untranslatable>
|
BP30 1.0
|
|
|
|
<Data>
|
Alphanumeric
|
To End
|
Upto 256 characters of free format text
|
|
|
|
+ <AgncySimlrNameMatch>
|
BP31 1.0
|
|
|
|
<FileAddr>
|
Alphanumeric
|
8
|
|
|
<CodeCheck>
|
Alphanumeric
|
2
|
|
|
<FirstSegStartDt>
|
Numeric
|
8
|
YYYYMMDD
|
|
<CancelledInd>
|
Alpha
|
1
|
Y= PNR has been cancelled
N or Blank = PNR is active
|
|
<CustName>
|
Alpha
|
To End
|
Example: SMITH/JMR.
Note: 1G returns a maximum of 16 characters in this field, for 1V the maximum is 25 characters.
Longer names are truncated.
|
|
|
|
+ <TkArrangement>
|
BP32 1.0
|
|
|
|
<Text>
|
Alphanumeric
|
To End
|
Optional free text
|
|
|
|
+ <TAUTkArrangement>
|
BP33 1.0
|
|
|
|
<QTAUDt>
|
Alphanumeric
|
5
|
DDMMM
|
|
<BranchPCC>
|
Alphanumeric
|
4
|
Branch where PNR is to be queued. 3 Character codes have a leading zero eg. 06MY
Blank = queue to default pseudo city
|
|
+ <QPlacementAry>
|
Array
|
n/a
|
|
|
+ <QPlacement>
|
FieldSet
|
n/a
|
|
|
<QDt>
|
Alphanumeric
|
5
|
DDMMM
|
|
|
|
|
TextLen
Structured data only.
Not in XML.
|
Numeric
|
2
|
Zero if free text does not exist
|
|
|
|
+ <TAWTkArrangement>
|
BP34 1.0
|
|
|
|
<QTAWDt>
|
Alphanumeric
|
5
|
DDMMM
|
|
<QTAWTm>
|
Numeric
|
4
|
HHMM
Blank if does not exist
|
|
<BranchPCC>
|
Alphanumeric
|
4
|
Branch where PNR is to be queued. 3 Character codes have a leading zero eg. 06MY
Blank if queue to default pseudo city
|
|
<InHouseAcct>
|
Alphanumeric
|
6
|
Blank if does not exist
|
|
+ <QPlacementAry>
|
Array
|
n/a
|
|
|
+ <QPlacement>
|
FieldSet
|
n/a
|
|
|
<QDt>
|
Alphanumeric
|
5
|
DDMMM
|
|
|
|
|
TextLen
Structured data only.
Not in XML.
|
Numeric
|
2
|
Zero if does not exist
|
|
|
|
+ <TLTkArrangement>
|
BP35 1.0
|
|
|
|
<MinutesBeforeDeparture>
|
Numeric
|
3
|
030 Indicates the ticket will be picked up 30 minutes before departure at the UA ticket desk. Only valid for UA issued tickets. Blank if does not exist.
If this field is populated the following four fields will be blank.
|
|
<TkIssueDt>
|
Alphanumeric
|
5
|
DDMMM
|
|
<TkIssueTm>
|
Numeric
|
4
|
HHMM
|
|
<Airp>
|
Alphanumeric
|
5
|
Airport where ticket to be issued.
Blank if does not exist.
|
|
<AirV>
|
Alphanumeric
|
3
|
Airline issuing ticket.
Blank if does not exist.
|
|
<Text>
|
Alphanumeric
|
To End
|
Optional free text
|
|
|
|
+ <TAMTkArrangement>
|
BP36 1.0
|
|
|
|
<TkMailDt>
|
Alphanumeric
|
5
|
DDMMM
|
|
<Text>
|
Alphanumeric
|
To End
|
Optional free text
|
|
|
|
+ <Control>
|
CTRL 1.0
|
|
|
|
<KLRCnt>
|
Numeric
|
5
|
Number of KLRs following this KLR in the Data Record. Range 0 - 99999
|
|
+ <KlrAry>
|
Array
|
n/a
|
|
|
+ <Klr>
|
FieldSet
|
n/a
|
|
|
<ID>
|
Alphanumeric
|
4
|
Record Identifier of a KLR which occurs one or more times in this Data Record
|
|
<NumOccur>
|
Numeric
|
4
|
Number of times the KLR occurs in this Data Record. Range 1 - 9999
|
|
|
|
|
|
|
|
+ <InvoiceRmk>
|
DPIR 1.0
|
|
|
This KLR is a RESPONSE KLR.
Start Definition of Document Itinerary/Invoice Remarks (Ticket Remarks) KLR
|
|
<ItemNum>
|
Numeric
|
3
|
Description of Field: Remarks Item Number. This field is not used for Canned Data Retrieval.
Format (n-numeric):
nnn
How is null data indicated?
Character zeros
What does null data indicate?
No data results in error
|
|
<Keyword>
|
Numeric
|
4
|
Description of Field:
Identifier for the type of data in the Free Text following. This field is not used for Canned Data Retrieval.
Format (n-numeric):
nnnn
Possible Values (List):
3000 = Free text (see below)
3001 = DYO = Design your own (1V/1G)
3002 = FS- = Fare save (1G)
= DS = Dollar save(1V)
3003 = CR- = Canned remark nos.(1V/1G)
3004 = PF- = PTA fee amount (1V)
3005 = NP- = Waived PTA fee amount (1V)
3006 = TK- = Manual ticket numbers (1V/1G)
3007 = CA- = Location,customer & selling agent (1V)
3008 = CA- = Back office branch & account nbr (1G)
3009 = AC- = Account nbr (1G) - same as SA on 1V
3010 = FT- = Freetext (1G)
3011 = DEF = In foreign currency (DEFXX on 1V)
3012 = PT- = PTA number (1V)
3013 = SF- = Service fee (1V)
3014 = SA- = Customer number SA Account (1V)
3015 = SD- = Customer number (1V)
3016 = CD- = Customer number (1V)
3017 = G*RC/ = Routing code (1V Canada only)
3018 = FA- = Faring Agent remark
3019 = PH- = Phone Field Override Remark
3020 = FEE- = New Service Fee Remark
3021 = FTX- = Tax for Service Fee Remark
3022 = AB1- = ARC Service Fee One Remark
3023 = AB2- = ARC Service Fee Two Remark
How is null data specified?
Character zeros
What does null data indicate?
No data results in error
|
|
<Rmk>
|
Alphanumeric
|
To End
|
Description of Field:
Ticket Remarks data. Keyword above defines the type of data expected. This field is not used for Canned Data Retrieval.
Format (x-alpha/numeric):
xxx...
How is null data indicated?
Blanks
What does null data indicate?
No data results in error
If variable length, specify the maximum allowable length.
Length is dependent on the type of data within the freetext. E.G.; if Routing Code, the max length is 2, if
Phone Field override, the max is 60 characters, etc.
|
|
|
|
+ <CreditCardFOP>
|
DPP0 1.0
|
|
|
Start Definition Of Form of Payment (Credit / Debit Card) KLR
Start of Form of Payment KLR general header
|
|
<ID>
|
Numeric
|
2
|
Field Description:
Form of Payment type number
Format (n-numeric):
nn
Possible Values (List)
06 - Credit Card
10 - Debit Card
Special Format:
Right justified.
Examples:
06
How is null data specified?
N/A
What does null data indicate?
Task dependant, for 'some' tasks, no data results in error
|
|
This line is used by automation. Choices = Form of Payment id, 6,10
|
|
<Type>
|
Numeric
|
1
|
Field Description:
Form of payment type
Format (n-numeric):
n
Possible Values (List)
1 - Credit type form of payment
2 - Cash type form of payment
Special Format:
N/A
Examples:
1
How is null data specified?
N/A
What does null data indicate?
Task dependant, for 'some' tasks, no data results in error
|
|
This line is used by automation. Choices = Form of Payment Type, 1,2
|
|
<Currency>
|
Alpha
|
3
|
Field Description:
Currency code of amount paid with FOP
Format (a-alpha):
aaa
Special Format:
Blank Filled.
Examples:
USD (U.S. Dollars)
CAD (Canadian Dollars)
EUR (Euros)
How is null data specified?
Blanks
What does null data indicate?
Task dependant, for 'some' tasks, no data results in error
|
|
<Amt>
|
Numeric
|
12
|
Field Description:
Amount paid with FOP (if not entered then zeroes)
Format (n-numeric):
nnnnnnnnnnnn
Possible Values (List)
000000000000 - 999999999999
Special Format:
Right justified, zero filled.
Examples:
000788392223
How is null data specified?
Zero
What does null data indicate?
Task dependant, for 'some' tasks, no data results in error
|
|
End of Form of Payment KLR general header
|
|
<ExpDt>
|
Numeric
|
4
|
Field Description:
Credit Card Expiration Date
Format (n-numeric):
nnnn (MMYY)
Special Format:
MMYY
Examples:
0505
How is null data specified?
Blanks
What does null data indicate?
Task dependant, for 'some' tasks, no data results in error
|
|
<TransType>
|
Numeric
|
1
|
Field Description:
Credit Transaction Type (If not entered then blanks)
Format (n-numeric):
n
Possible Values (List)
1 - Signature on File
2 - Telephone Order
Special Format:
Blank filled.
Examples:
2
How is null data specified?
Zero or Blanks
What does null data indicate?
When null (blanks) then this field is not applicable
|
|
This line is used by automation. Choice = Transaction type, 1, 2
|
|
<ApprovalInd>
|
Alpha
|
1
|
Field Description:
Outbound only. If source of approval unknown, field is blank.
Format (a-alpha):
a
Possible Values (List):
M - manual,
A - system generated
Character Blank - source of approval unknown.
Special Format:
N/A
Examples:
M
How is null data specified?
Blanks
What does null data indicate?
Task dependant, for 'some' tasks, no data results in error
|
|
This line is used by automation. Choice = Credit Card Approval Code indicator, M, A, Character blank
|
|
<AcceptOverride>
|
Alpha
|
1
|
Field Description:
Credit Card Acceptance Override (CAO). CAO is Apollo only.
Possible Values (List):
Y - Credit Card acceptance override applies.
Format (a-alpha):
a
Special Format:
N/A
Examples:
Blank
How is null data specified?
Blanks
What does null data indicate?
When null (blanks) then this field is not applicable
|
|
This line is used by automation. Choice = Credit Card Acceptance Override, Y
|
|
<ValidationBypassReq>
|
Alpha
|
1
|
Field Description:
Credit Card Validation Bypass requested
Possible Values (List):
Y - Do not validate Credit Card with vendor
N - Validate Credit Card with Vendor.
Format (a-alpha):
a
Special Format:
If 'Y' you must enter the *A Authorization code in the Additional Info Array, in ID number 1 - Credit Card Approval Code.
Examples:
Y
How is null data specified?
Blanks - Defaults to 'N'
What does null data indicate?
When null (blanks) then this field is not applicable
|
|
This line is used by automation. Choice = Credit Card Validation bypass requested, Y
|
|
<Vnd>
|
Alpha
|
2
|
Field Description:
Credit card Vendor alpha code
Format (a-alpha):
aa
Special Format:
Left justified, blank filled.
Examples:
AX
VI
CA
JC
TP
DC
How is null data specified?
N/A
What does null data indicate?
Task dependant, for 'some' tasks, no data results in error
|
|
<Acct>
|
Numeric
|
20
|
Field Description:
Credit Card Number
Format (n-numeric):
nnnnnnnnnnnnnnnnnnnn
Special Format:
Right justified, Zero filled.
Examples:
00000371019534732004
How is null data specified?
N/A
What does null data indicate?
No data results in error
|
|
+ <AdditionalInfoAry>
|
Array
|
n/a
|
|
|
+ <AdditionalInfo>
|
FieldSet
|
n/a
|
|
|
<ID>
|
Numeric
|
1
|
Field Description:
Card Additional Data Indicator.
Format (n-numeric):
n
Possible Values (List):
1 - Credit Card Approval code (8 alphanumeric)
2 - Card Holder (29 alpha with special chars)
3 - Order number - South Africa only (29 alphanumeric)
4 - Card Identification Code as used by
AMEX (4 numeric) on 1V and
AMEX (4 numeric) on 1G
CA (3 numeric) on 1G
DC (3 numeric) on 1G
VI (3 numeric) on 1G
DS (3 numeric) on 1G
5 - Extended payment option, format depending on credit card vendor (4 alphanumeric)
6 - Customer reference (29 alphanumeric)
Special Format:
N/A
Examples:
1
How is null data specified?
N/A
What does null data indicate?
No data results in error
|
|
<Dt>
|
Alphanumeric
|
29
|
Field Description:
Additional Data.
Format (x-alpha/numeric):
xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Special Format:
Left justified, blank filled.
Examples:
A1234 (24 blanks)
512 (26 blanks)
How is null data specified?
N/A
What does null data indicate?
No data results in error
|
|
|
|
|
|
|
|
+ <CheckFOP>
|
DPP1 1.0
|
|
|
|
<ID>
|
Numeric
|
2
|
Field Description:
Form of Payment id -Cheque
Format (n-numeric):
nn
Special Format:
N/A
Possible Values (List or Range):
02- Cheque
Examples:
02
How is null data specified?
N/A
What does null data indicate?
No data results in error
|
|
<Type>
|
Numeric
|
1
|
Field Description:
Form of Payment Type
Format (n-numeric):
n
Special Format:
Zero, if not entered.
Possible Values (List):
1 - Credit type form of payment
2 - Cash type form of payment
Examples:
2
How is null data specified?
N/A
What does null data indicate?
No data results in error.
|
|
<Currency>
|
Alpha
|
3
|
Field Description:
Currency code of amount paid with FOP
Format (a-alpha):
aaa
Special Format:
Left justified, Character Blank filled.
Examples:
USD
How is null data specified?
N/A
What does null data indicate?
No data results in error.
|
|
<Amt>
|
Numeric
|
12
|
Field Description:
Amount paid with FOP
Format (n-numeric):
nnnnnnnnnnnn
Special Format:
Zero, if not entered.
Right justified, zero filled
Examples:
000000064578
How is null data specified?
Null data is specified as zero.
What does null data indicate?
If not entered then field is populated with zeroes.
|
|
+ <AdditionalInfoAry>
|
Array
|
n/a
|
|
|
+ <AdditionalInfo>
|
FieldSet
|
n/a
|
|
|
<ID>
|
Numeric
|
1
|
Field Description:
Additional Data indicator
Format (n-numeric):
n
Special Format:
Left justified, blank filled.
Possible Values (List):
1 - Micron number
2 - Bank (sort) code
3 - Cheque number
4 - Drawee name
5 - Holder name
6 - Free form text
Examples:
4
How is null data specified?
N/A
What does null data indicate?
No data results in error.
|
|
<Dt>
|
Alphanumeric
|
29
|
Field Description:
Additional Data based on the indicator selected in Additional Data Ind field.
Format (x-alpha/numeric):
xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Special Format:
Left justified, Character Blank filled.
Examples:
How is null data specified?
N/A
What does null data indicate?
No data results in error.
|
|
|
|
|
|
|
|
+ <OtherFOP>
|
DPP9 1.0
|
|
|
|
<ID>
|
Numeric
|
2
|
Description of Field:
Form of Payment identification number
Format (n-numeric):
nn
Possible Values (List or Range):
01 - Cash
03 - Nonref
04 - Miscellaneous
05 - Invoice
07 - Government (Travel) Request
08 - Pseudo Cash
09 - Credit (non Credit Card)
11 - AK Bons
12 - Pay Late
13 - Exchange
14 - Money Order
15 - Travelers Check
99 - Freeform etc.
Special Format:
Right justified, zero filled
Example:
07
How is null data specified?
N/A
What does null data indicate?
No data results in error
|
|
<Type>
|
Numeric
|
1
|
Description of Field:
Form of payment type
Format (n-numeric):
n
Possible Values (List or Range):
1 - Credit type form of payment
2 - Cash type form of payment
Special Format:
Right justified, zero filled
Example:
0
1
How is null data specified?
0
What does null data indicate?
Zero indicates null data.
|
|
<Currency>
|
Alpha
|
3
|
Description of Field:
Currency code of amount paid with FOP
Format (a-alpha):
aaa
Special Format:
Left justified, blank filled.
Example:
3 Blanks
USD (U.S. Dollars)
CAD (Canadian Dollars)
EUR (Euros)
How is null data specified?
N/A
What does null data indicate?
No data result in error.
|
|
<Amt>
|
Numeric
|
12
|
Description of Field:
Amount paid with FOP
Format (n-numeric):
nnnnnnnnnnnn
Possible Values (Range):
000000000000 - 999999999999
Special Format:
Right justified, zero filled
Example:
000787822122
How is null data specified?
0
What does null data indicate?
If not entered then field is populated with zeroes
|
|
+ <AdditionalInfoAry>
|
Array
|
n/a
|
|
|
+ <AdditionalInfo>
|
FieldSet
|
n/a
|
|
|
<ID>
|
Numeric
|
1
|
Description of Field:
Additional data indicator
Format (n-numeric):
n
Possible Values (List):
2 - Money Order / Travelers Check number
3 - Government request id
4 - Freeform text
5 - Invoice number
Example:
3
How is null data specified?
N/A
What does null data indicate?
No data results in error
|
|
<Dt>
|
Alphanumeric
|
29
|
Description of Field:
Additional data
Format (x-alpha/numeric):
xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Special Format:
Left justified, blank filled.
Example:
AD2311112 (20 blanks)
How is null data specified?
N/A
What does null data indicate?
No data results in error
|
|
|
|
|
|
|
|
+ <ItinRmk>
|
DPR1 1.0
|
|
|
|
<SegNum>
|
Numeric
|
3
|
Segment number of the itinerary item to which this remark is associated.
Blank if remark is not associated to a segment.
|
|
<RelatesToInd>
|
Alphanumeric
|
2
|
Indicates type of information the remark relates to.
CI = Check-in times
DT = Departure terminal information
AT = Arrival terminal information
Blank if not applicable
|
|
<Rmk>
|
Alphanumeric
|
To End
|
|
|
|
|
+ <ErrText>
|
EROR 1.0
|
|
|
|
NOTE: When this KLR is returned it will be the only KLR present in the response.
|
|
<Err>
|
Alphanumeric
|
8
|
Field Description:
Error code provided for the client.
Format (x-alpha/ numeric):
xxxxxxxx
Special Format:
All EROR KLRs contain an 8-byte error code field. In the interest of standardization and to ensure each error code is unique, applications must adhere to the following error code numbering system:
Byte 1: Alphanumeric Id of the application area owning this error code
Byte 2: Severity number of error. Blank and zero indicates no priority exists. Severity 9 is Catastrophic/Highest Severity.
Bytes 3-8: Numeric in the range 000000 - 999999 identifying the error situation
Possible Values(List):
A = Availability
B = PNR / Booking File
C = Cars
D = Document Production
F = Fares
H = Headlines
I = Infrastructure (SDD)
J = Leisure
L = Links
M = Seating
P = Client File
Q = Queues
R = Hotels
S = Sell
T = Travelscreen
V = Terminal Security
W = Rail
Example:
Err = "A 000510"
Err = "D 000000'
"A" = Availability
"D" = Document Production
" " = Character blank
"000105" = Error number for "NO DISPLAYABLE FLIGHTS"
How is null data specified?
N/A
What does null data indicate?
No data results in error.
|
|
<KlrInErr>
|
Alphanumeric
|
4
|
Field Description:
ID of the KLR that caused this error.
Format (x-alpha/numeric):
xxxx
Special Format:
N/A
Examples:
DP01
AAGA
0000
How is null data specified?
N/A
What does null data indicates?
No data results in error.
|
|
+ <InsertedTextAry>
|
Array
|
n/a
|
|
|
+ <InsertedText>
|
FieldSet
|
n/a
|
|
|
<Offset>
|
Numeric
|
3
|
Field Description:
Location of start of inserted text in Error Text field
Format (n-numeric):
nnn
Special Format:
N/A
Examples:
000
How is null data specified?
N/A
What does null data indicates?
No data results in error
|
|
<Len>
|
Numeric
|
2
|
Field Description:
Length of inserted text
Format (n-numeric):
nn
Special Format:
N/A
Examples:
00
How is null data specified?
N/A
What does null data indicate?
No data results in error
|
|
|
|
|
|
<Text>
|
Alphanumeric
|
To End
|
Field Description:
Complete error message, including any inserted text items
Format (x-alpha/numeric):
xxxxxxxxxxxxxxxxxx
Special Format:
N/A
Examples:
ERROR 4366 - FORM OF PAYMENT REQUIRED
How is null data specified?
N/A
What does null data indicates?
No data results in error.
|
|
|
|
+ <AirSeg>
|
IT01 1.0
|
|
|
|
<SegNum>
|
Numeric
|
2
|
As unpacked in a-06-AAA (Agents Assembly Area)
|
|
<Status>
|
Alpha
|
2
|
Refer to Galileo Formats guide for list of Status Codes
|
|
<Dt>
|
Numeric
|
8
|
Day on which segment departs YYYYMMDD
|
|
<DayChg>
|
Alphanumeric
|
2
|
-1, 00, 01, 02 are valid
|
|
<AirV>
|
Alpha
|
3
|
Left justified.
|
|
<NumPsgrs>
|
Numeric
|
2
|
Number of seats requested on this flight
|
|
<StartAirp>
|
Alpha
|
5
|
Airport Code
|
|
<EndAirp>
|
Alpha
|
5
|
Airport Code
|
|
<BIC>
|
Alpha
|
2
|
Booking code left justified.
|
|
<OpSuf>
|
Alpha
|
1
|
Blank if not applicable
|
|
<COG>
|
Alpha
|
1
|
"Y"= This flight is change of gauge.
"N"= This flight is not a change of gauge.
|
|
<TklessInd>
|
Alpha
|
1
|
"Y"= Ticketless segment
"N"= Not ticketless segment
|
|
<ConxInd>
|
Alpha
|
1
|
Always blank - for future use.
|
|
<FltFlownInd>
|
Alpha
|
1
|
'Y' or 'N' - Indicates if flight has flown or not
|
|
<MarriageNum>
|
Numeric
|
2
|
Air segments with the same number are "married" to one another.
Married segments MAY have change restrictions. For example, it may not be possible to individually cancel or change a segment which is married to other segments without cancelling or changing the other segments also. The rules governing married segments are defined and enforced by the airlines and are outside of the CRS's control.
Blank if not applicable
|
|
<SellType>
|
Alpha
|
1
|
Type of Sell achieved
'O' - Secure sold
'L' - Last seat sold (1V only)
'G' - Guaranteed sold
'S' - Super guaranteed sold
'P' - Passive segment
Blank if not applicable
|
|
<StopoverIgnoreInd>
|
Alpha
|
1
|
Applies to 1G only:
'X' = Treat as a no stopover segment for fare quote.
'I' = Ignore segment for fare quote and ticketing.
Blank if not applicable
|
|
|
|
+ <AirSegOpAirV>
|
IT02 1.0
|
|
|
|
+ <OpAirVInfoAry>
|
Array
|
n/a
|
|
This KLR is returned only when the preceding Air Segment KLR (IT01) is operated by airline(s) different from the one in the IT01 Airline Code field. The IT02 follows the IT01 to which it is related.
|
|
+ <OpAirVInfo>
|
FieldSet
|
n/a
|
|
BlkLen
Structured data only.
Not in XML.
|
Numeric
|
2
|
Length of array item, not including length of this field.
|
|
The following board and off point will be blank when all legs of the IT01 are operated by this airline. In which case the KLR will contain just ONE Operating Airline Item
|
|
<StartAirp>
|
Alpha
|
5
|
Board point of leg operated by this airline.
|
|
<EndAirp>
|
Alpha
|
5
|
Off point of last consecutive leg operated by this airline. All legs between the board and off point must be operated by this airline.
|
|
<AirV>
|
Alphanumeric
|
3
|
Blanks if airline does not have an IATA recognized airline code
|
|
<AirVName>
|
Alphanumeric
|
To End
|
Full airline name
|
|
|
|
|
|
|
|
+ <HtlSeg>
|
IT03 1.0
|
|
|
|
<SegNum>
|
Numeric
|
2
|
As unpacked in A-06-AAA (Agents Assembly Area).
{BR1CODSIT1}
|
|
<Status>
|
Alpha
|
2
|
"HK'= Confirmed.
"NN"= On Request. No yet confirmed.
"KK"= Now confirmed.
"UC"= Unable to confirm, waitlist closed.
Blank= Unknown.
{BR1CSTAIT2}
|
|
<StartDt>
|
Numeric
|
8
|
In CCYYMMDD format.
{BR1CSDTIT2}
|
|
<EndDt>
|
Numeric
|
8
|
In CCYYMMDD format.
{BR1CEDTIT2}
|
|
<NumNights>
|
Numeric
|
2
|
{BR1CNTSGH1}
|
|
<Pt>
|
Alpha
|
5
|
Airport code designating the city of the hotel where the reservation was placed.
{BR1CBPTIT5}
|
|
<HtlV>
|
Alpha
|
3
|
Chain ID designating the hotel vendor with which the reservation was made.
{BR1CPVCIT3}
|
|
<HtlPropNum>
|
Numeric
|
5
|
RoomMaster property number.
{BR1CPRFIT5}
|
|
<RateCode>
|
Alpha
|
7
|
Booking code for the room rate selected.
{BR1CRMSGH5 + BR1CRTCGH3 + BR1CSEQGH1}
|
|
<PropName>
|
Alpha
|
19
|
{BR1CHSNGH22}
|
|
<NumPersons>
|
Numeric
|
1
|
One or two.
{BR1CPERGH1}
|
|
<NumRooms>
|
Numeric
|
1
|
Number of hotel rooms reserved.
{BR1CNPUIT1}
|
|
<ConfNum>
|
Alpha
|
30
|
If there is no confirmation number then this field will be blank.
{BR1CODTGH184 + /CF-}
|
|
<RateTypeSold>
|
Alpha
|
2
|
"RQ"= Rate Quoted
"RG"= Rate Guaranteed
"RT"= Agent Entered
{BR1CILKGH1}
|
|
<RateChgInd>
|
Alpha
|
1
|
"Y"= Rate changes during length of stay.
"N"= No change over the period.
{BR1CSI1GH1, bit 0}
|
|
<MultDayRateInd>
|
Alpha
|
1
|
"Y"= Rate applies to more than one day, as in a package.
"N"= Normal application of rate period.
{BR1CSI1GH1, bit 1}
|
|
<Currency>
|
Alpha
|
3
|
Currency in which rates were sold.
{BR1CCRYGH3}
|
|
<RateDecPos>
|
Numeric
|
1
|
The number of implied places to the right of the implied decimal for the currency the rates are quoted in.
{BR1CDPTGH}
|
|
<ExtraChargesDecPos>
|
Numeric
|
1
|
Number of decimals in rates for extra charges if different from the rate.
|
|
<RateAmt>
|
Numeric
|
9
|
The room rate expressed in the currency defined by Currency Code. Location of implied decimal point specified by Number of Decimals.
{BR1CNBAGH5}
|
|
<MultiLevelRateCode>
|
Alpha
|
6
|
If this is not blank, it is the multilevel code used to sell a negotiated rate.
{BR1CODTGH184 + first 8 bytes}
|
|
|
|
+ <HtlSegOptFlds>
|
IT04 1.0
|
|
|
|
+ <FldAry>
|
Array
|
n/a
|
|
This KLR follows immediately after the parent Hotel Segment KLR
|
|
+ <Fld>
|
FieldSet
|
n/a
|
|
BlkLen
Structured data only.
Not in XML.
|
Numeric
|
3
|
Description of Field:
This is the length of variable length optional field that follows.
Format (n-numeric):
nnn
Special Format:
Right justified, zero filled
Examples:
014
064
How is null data specified?
N/A
What does null data indicate?
No data results in error.
|
|
<ID>
|
Alpha
|
2
|
Description of Field:
This is a code that identifies which optional data is in the variable length field.
Format (a-alpha):
aa
Possible Values (List):
AV = Advance deposit
BS = Booking source
RT = Corporate rate override
RG = Guaranteed rate
RQ = Quoted rate
RR = Rate request
PT = Approximate Total or Approximate Total Plus. May contain an AT, AP, or either with a rate
GT = Payment guarantee
DP = Deposit
AD = Customer address
RA = Rollaway bed adult
RD = Rollaway bed child
CR = Cribs
EX = Extra adult
EC = Extra child
TN = Tour number
RL = Tour room location
MP = Tour meal plan
CD = Corporate discount number
FG = Frequent guest number
FT = Frequent air traveler number
ID = Customer ID number
SI = Special information
NF = Reservation name - first
NL = Reservation name - last
AC = Alternate Currency code
VC = Vendor Currency code
BA = Billing Address for Credit Card
CN = Name on the Credit Card
CV = Security ID Code on Credit Card
MR = Merchant Record Locator (CMR)
CC = Credit Card number from extension
How is null data specified?
N/A
What does null data indicate?
No data results in error.
|
|
<Contents>
|
Alpha
|
VL
|
Description of Field:
This field contains the details of the optional data, based on the type specified in Optional Field Identity. The field size depends on the contents. See comments which follow.
Format (x-alpha/numeric):
xxx
Examples:
AX370000000000028EXP0405
John Q. Smith
AP25800
How is null data specified?
N/A
What does null data indicate?
No data results in error.
If variable length, specify the maximum allowable length.
110
|
|
|
|
|
|
|
|
+ <CarSeg>
|
IT05 1.0
|
|
|
|
<SegNum>
|
Numeric
|
2
|
As unpacked in A-06-AAA (Agents Assembly Area).
{BR1CCODSIT1}
|
|
<Status>
|
Alpha
|
2
|
"HK'= Confirmed.
"NN"= On Request. Not yet confirmed.
"KK"= Now confirmed.
"UC"= Unable to confirm, waitlist closed.
Blank= Unknown.
{BR1CSTAIT2}
|
|
<StartDt>
|
Numeric
|
8
|
CCYYMMDD format
{BR1CSDTIT2}
|
|
<StartTm>
|
Numeric
|
4
|
Pickup time expressed in 24 hour clock format.
{BR1CODTGC220 + /ARR}
|
|
<StartAirV>
|
Alphanumeric
|
3
|
{BR1CODTGC220 + /ARR}
|
|
<StartFltNum>
|
Alphanumeric
|
4
|
{BR1CODTGC220 + /ARR}
|
|
<Airp>
|
Alpha
|
5
|
Airport code where car is being rented.
{BR1CBPTIT5}
|
|
<ActualStartPt>
|
Alpha
|
5
|
Code of actual car pickup location.
{BR1CODTGC220 + /PUP}
|
|
<LocnCat>
|
Alphanumeric
|
1
|
{BR1CODTGC220 + /PUP}
|
|
<LocnExpansion>
|
Numeric
|
1
|
Reserved for future use.
{BR1CODTGC220 + /PUP}
|
|
<LocnNum>
|
Numeric
|
2
|
{BR1CODTGC220 + /PUP}
|
|
<EndDt>
|
Numeric
|
8
|
CCYYMMDD format
{BR1CEDTIT2}
|
|
<EndTm>
|
Numeric
|
4
|
Return time expressed in 24 hour clock format.
{BR1CODTGC220 + /DT-}
|
|
<NumCars>
|
Numeric
|
1
|
Number of cars reserved.
{BR1CNPUIT1}
|
|
<CarV>
|
Alpha
|
3
|
{BR1CPVCIT3}
|
|
<ConfNum>
|
Character
|
30
|
If there is no confirmation number then this field will be blank.
{BR1CODTGC220 + /CF-}
|
|
<RateType>
|
Alpha
|
1
|
"D"= Daily
"E"= Weekend
"W"= Weekly
"M"= Monthly
"H"= Hourly
"P"= Package
Blank= No rate type
{BR1CODTGC220 + /RC- }
|
|
<RateCode>
|
Character
|
6
|
Blank= No rate code
{BR1CODTGC220 + /RC- }
|
|
<RateCat>
|
Alpha
|
1
|
"A"= Association
"B"= Business standard
"C"= Corporate
"G"= Government
"I"= Industry
"K"= Package
"P"= Promotional
"R"= Credential
"S"= Standard
"U"= Consortium
"V"= Convention
Blank= No rate category
{BR1CODTGC220 + /RC- }
|
|
<CarType>
|
Alpha
|
4
|
ECAR, ICAR, etc.
{BR1CCRTGC4}
|
|
<YieldMgmtNum>
|
Numeric
|
1
|
Blank, or 1 through 9
{BR1CODTGC220 + /RC- }
|
|
<Currency>
|
Alpha
|
3
|
Currency in which rates were sold.
{BR1CODTGC220 + /RG- }
|
|
<DecPos>
|
Numeric
|
1
|
The number of implied places to the right of the implied decimal for the currency the rates are quoted in.
{BR1CODTGC220 + /RG- }
|
|
<RateAmt>
|
Numeric
|
9
|
The car rate expressed in the currency defined by Currency. Location of implied decimal point specified by Number of Decimals. This applies to all rate fields.
{BR1CODTGC220 + /RG- }
|
|
<RateGuarInd>
|
Alpha
|
1
|
"G"= Rate guaranteed.
"Q"= Rate quoted.
"T"= Agent entered.
{BR1CODTGC220 + /RG- }
|
|
<MilesOrKm>
|
Alpha
|
1
|
{BR1CODTGC220 + /RG- }
|
|
<MileAllow>
|
Alphanumeric
|
5
|
{BR1CODTGC220 + /RG- }
|
|
<MileRateAmt>
|
Numeric
|
9
|
{BR1CODTGC220 + /RG- }
|
|
<ExtraDayRateAmt>
|
Numeric
|
9
|
{BR1CODTGC220 + /RG- }
|
|
<ExtraDayMileAllow>
|
Character
|
5
|
{BR1CODTGC220 + /RG- }
|
|
<ExtraDayMileRateAmt>
|
Numeric
|
9
|
{BR1CODTGC220 + /RG- }
|
|
<ExtraHourRateAmt>
|
Numeric
|
9
|
{BR1CODTGC220 + /RG- }
|
|
<ExtraHourMileAllow>
|
Character
|
5
|
{BR1CODTGC220 + /RG- }
|
|
<ExtraHourMileRateAmt>
|
Numeric
|
9
|
{BR1CODTGC220 + /RG- }
|
|
|
|
+ <CarSegOptFlds>
|
IT06 1.0
|
|
|
|
+ <FldAry>
|
Array
|
n/a
|
|
This KLR follows immediately after the parent Car Segment KLR
|
|
+ <Fld>
|
FieldSet
|
n/a
|
|
BlkLen
Structured data only.
Not in XML.
|
Numeric
|
3
|
Length of Optional Field Contents to follow.
|
|
<ID>
|
Alpha
|
2
|
Identifies which optional data is represented by this group:
RT = Corporate rate override
RG = Guaranteed rate
RQ = Quoted rate
BS = Booking source
AD = Customer address
ID = Customer ID
PU = Pick up location
TN = Tour number
CD = Corporate ID
SI = Special information
FT = Frequent air traveler number
SQ = Special equipment
GT = Payment guarantee
PR = Prepayment information
DL = Drivers license
DC = Drop off charge
DO = Drop off location
NF = Reservation name - first
NL = Reservation name - last
AC = Alternate Currency code
VC = Vendor Currency code
|
|
<Contents>
|
Alpha
|
VL
|
This field contains the details of the optional data based on the type specified in Optional Field Identity. The field size depends on the contents. See comments which follow.
|
|
|
|
|
|
|
|
+ <NonAirSeg>
|
IT07 1.0
|
|
|
|
<SegNum>
|
Numeric
|
2
|
Description of Field:
Segment number as unpacked in BFWC/AAA.
Format (a-alpha, n-numeric, x-alpha/numeric):
nn
Possible Values (Range):
01-99
How is null data specified?
No data results in error
What does null data indicate?
No data results in error
|
|
<Status>
|
Alpha
|
2
|
Description of Field:
Status code as input in the SQP1
Format (a-alpha, n-numeric, x-alpha/numeric):
aa
Examples:
NN
BK
How is null data specified?
No data results in error
What does null data indicate?
No data results in error
|
|
<Type>
|
Alpha
|
3
|
Description of Field:
Type of non-air segment
Format (a-alpha, n-numeric, x-alpha/numeric):
aaa
Possible Values (List):
HTL - hotel
CAR - car
ATX - auxiliary
SUR - surface
TUR - tour
THE - theater
LIM - limousine
INS - insurance
OTH - other
How is null data specified?
No data results in error
What does null data indicate?
No data results in error
|
|
<StartDt>
|
Numeric
|
8
|
Description of Field:
Start date of service
Format (a-alpha, n-numeric, x-alpha/numeric):
nnnnnnnn
Special Format
YYYYMMDD
How is null data specified?
No data results in error
What does null data indicate?
No data results in error
|
|
<EndDt>
|
Numeric
|
8
|
Description of Field:
End date of service
Format (a-alpha, n-numeric, x-alpha/numeric):
nnnnnnnn
Special Format
YYYYMMDD
How is null data specified?
1G: character blanks for all auxiliary segments (out date appears in free form text)
1V: HTL and CAR segments
What does null data indicate?
Character blanks indicates end date is not present
|
|
<Vnd>
|
Alphanumeric
|
3
|
Description of Field:
Vendor code of carrier or service provider.
Format (a-alpha, n-numeric, x-alpha/numeric):
xxx
Special Format:
Left justified blank filled
How is null data specified?
No date results in error
What does null data indicate?
No data results in error
|
|
<NumPersons>
|
Numeric
|
2
|
Description of Field:
Number in party or number of services required.
Format (a-alpha, n-numeric, x-alpha/numeric):
nn
Special Format:
none
Possible Values (Range):
01-99
How is null data specified?
No data results in error
|
|
<NumNights>
|
Numeric
|
2
|
Description of Field:
Number of nights in hotel
Format (a-alpha, n-numeric, x-alpha/numeric):
nn
Special Format:
For HTL segments only
Possible Values (Range):
01-99
How is null data specified?
Character blanks.
What does null data indicate?
Character blanks indicate non-HTL segments.
|
|
<StartPt>
|
Alpha
|
5
|
Description of Field:
City code of service or departure point of service
Format (a-alpha, n-numeric, x-alpha/numeric):
aaaaa
How is null data specified?
No data results in error
What does null data indicate?
No data results in error
|
|
<EndPt>
|
Alpha
|
5
|
Description of Field:
Arrival city
Format (a-alpha, n-numeric, x-alpha/numeric):
aaaaa
Special Format:
Valid for 1V ATX segments only, blank for all other segment types
How is null data specified?
Character blanks.
What does null data indicate?
Character blanks.
|
|
<SellType>
|
Alpha
|
1
|
Description of Field:
Type of Sell achieved
Format (a-alpha, n-numeric, x-alpha/numeric):
a
Possible Values (List):
I - Instant confirmation
How is null data specified?
Character blank.
What does null data indicate?
Character blank indicates not applicable.
|
CityNameLen
Structured data only.
Not in XML.
|
Numeric
|
3
|
Description of Field:
Length of City Name field.
Format (a-alpha, n-numeric, x-alpha/numeric):
nnn
Possible Values (Range):
0-999
How is null data specified?
Character zeroes
What does null data indicate?
Character zeroes indicate that City Name field does not exist.
|
TextLen
Structured data only.
Not in XML.
|
Numeric
|
3
|
Description of Field:
Length of Free Form Text
Format (a-alpha, n-numeric, x-alpha/numeric):
nnn
Possible Values (Range):
0-999
How is null data specified?
Character zeroes
What does null data indicate?
Character zeroes indicate no text exists
|
|
<CityName>
|
Alphanumeric
|
VL
|
Description of Field:
City name
Format (a-alpha, n-numeric, x-alpha/numeric):
x
Special Format:
1V only: HTL, CAR, ATX segments only
How is null data specified?
No data indicates no city name present
What does null data indicate?
No data indicates no city name present
If variable length, specify the maximum allowable length.
999
|
|
<Text>
|
Alphanumeric
|
VL
|
Description of Field:
Free Form Text
Format (a-alpha, n-numeric, x-alpha/numeric):
x
Special Format:
none
How is null data specified?
No data indicates no free form text present
What does null data indicate?
No data indicates no free form present
If variable length, specify the maximum allowable length.
999
|
|
|
|
+ <OpenAirSeg>
|
IT08 1.0
|
|
|
|
<SegNum>
|
Numeric
|
2
|
As unpacked in BFWC/AAA
|
|
<Dt>
|
Numeric
|
8
|
Date of service or blank if no date
|
|
<AirV>
|
Alphanumeric
|
3
|
'YY '= Any airline
|
|
<FlownInd>
|
Alpha
|
1
|
'Y' or 'N' indicates if flight has flown or not
|
|
<StopoverIgnoreInd>
|
Alpha
|
1
|
Applies to 1G only:
'X' = Treat as a no stopover segment for fare quote.
'I' = Ignore segment for fare quote and ticketing.
Blank if not applicable
|
|
|
|
+ <DuePaidInfo>
|
IT09 1.0
|
|
|
|
<SegNum>
|
Numeric
|
2
|
Description of Field:
As unpacked in BFWC/AAA
Format (a-alpha, n-numeric, x-alpha/numeric):
numeric
Special Format:
n/a
Possible Values (List or Range):
01 - 99
How is null data specified?
No data results in error
What does null data indicate?
No data results in error
|
|
<Type>
|
Alpha
|
1
|
Description of Field:
Type of segment
Format (a-alpha, n-numeric, x-alpha/numeric):
alpha
Special Format:
n/a
Possible Values (List or Range):
S Surface
X Airtaxi
T Tour
H Hotel
C Car
How is null data specified?
No data results in error
What does null data indicate?
No data results in error
|
|
<Dt>
|
Numeric
|
8
|
Description of Field:
Start date
Format:
YYYYMMDD
How is null data specified?
No data results in error
What does null data indicate?
No data results in error
|
|
<DuePaidTextInd>
|
Alpha
|
1
|
Description of Field:
Due/Paid/Text indicator
Format (a-alpha, n-numeric, x-alpha/numeric):
alpha
Special Format:
n/a
Possible Values (List or Range):
D Due Indicator
P Paid Indicator
T Text Indicator
How is null data specified?
No data results in error
What does null data indicate?
No data results in error
|
|
<Price>
|
Numeric
|
10
|
Description of Field:
Due/Paid amount
Format (a-alpha, n-numeric, x-alpha/numeric):
Numeric
Special Format:
Decimal point will not be included in the amount number of decimal places is represented by Decimal position field.
How is null data specified?
No data results in error
What does null data indicate?
No data results in error
|
|
<Currency>
|
Alpha
|
3
|
Description of Field:
Currency code (related to AAT)
Format (a-alpha, n-numeric, x-alpha/numeric):
alpha
Special Format:
n/a
Examples:
GBP, ZAR, USD
How is null data specified?
No data is allowed currency code will be determined by checking users AAT.
What does null data indicate?
Currency code is unknown
If variable length, specify the maximum allowable length.
|
|
<DecPos>
|
Numeric
|
1
|
Description of Field:
Decimal point related to currency
Format (a-alpha, n-numeric, x-alpha/numeric):
n
Special Format:
n/a
Possible Values (List or Range):
.
How is null data specified?
Depending on the currency, no data may result in an error. If not applicable, decimal null character is blank.
What does null data indicate?
Decimal point doesnt exist for currency
|
|
<Text>
|
Alphanumeric
|
To End
|
Description of Field:
Free form text
Format (a-alpha, n-numeric, x-alpha/numeric):
Alpha numeric
Special Format:
n/a
Examples:
HOLLYWOOD TOURS
How is null data specified?
No data results in error
What does null data indicate?
No data results in error
If variable length, specify the maximum allowable length.
Due segments = 53 chars maximum
Paid segments = 53 chars maximum
Text segments = 47 chars maximum
|
|
|
|
+ <FlygTaxiSeg>
|
IT10 1.0
|
|
|
|
<SegNum>
|
Numeric
|
2
|
As unpacked in BFWC/AAA
|
|
<Vnd>
|
Alphanumeric
|
3
|
Left justified
|
|
<NumCars>
|
Numeric
|
2
|
Number of cars
|
|
<City>
|
Alpha
|
5
|
Pick up point
|
|
<StartDepInd>
|
Alpha
|
1
|
A or D
|
|
<AirV>
|
Alphanumeric
|
3
|
Left justified with trailing blank
|
|
<FltNum>
|
Alphanumeric
|
5
|
Right justified with leading zeroes
|
|
<Text>
|
Alphanumeric
|
To End
|
Variable length freetext
|
|
|
|
+ <TourSeg>
|
IT11 1.0
|
|
|
|
<SegNum>
|
Numeric
|
2
|
As unpacked in BFWC/AAA
|
|
<StartDt>
|
Numeric
|
8
|
YYYYMMDD
|
|
<EndDt>
|
Numeric
|
8
|
YYYYMMDD
|
|
<Vnd>
|
Alphanumeric
|
3
|
Left justified
|
|
<PkgID>
|
Alpha
|
14
|
Vendor tour identifier BR1CNUMLH
|
|
<PricingCat>
|
Alpha
|
3
|
BR1CSVCLH
|
|
<ConfNum>
|
Alphanumeric
|
16
|
BR1CVRFLH
|
|
<DocMailDt>
|
Numeric
|
8
|
YYYYMMDD (if mailed) BR1CDMDLT
|
|
<Currency>
|
Alpha
|
3
|
BR1CCURLH
|
|
<BasePrice>
|
Numeric
|
9
|
BR1CBAPLT
|
|
<DecPos>
|
Numeric
|
1
|
BR1CDECLH
|
|
<DepDueDt>
|
Numeric
|
8
|
YYYYMMDD BR1CDDDLT
|
|
<DepAmtDue>
|
Numeric
|
9
|
BR1CDEPLT
|
|
<DepRecvDt>
|
Numeric
|
8
|
YYYYMMDD (if received) BR1CDRDLT
|
|
<OptPrice>
|
Numeric
|
9
|
BR1COPTLT
|
|
<BalanceDueDt>
|
Numeric
|
8
|
YYYYMMDD BR1CBDDLT
|
|
<BalanceAmt>
|
Numeric
|
9
|
BR1CTBDLT
|
|
<BalanceRecvDt>
|
Numeric
|
8
|
YYYYMMDD BR1CBRDLT
|
|
<TotTax>
|
Numeric
|
9
|
BR1CTX1LT + BR1CTX2LT + BR1CTX3LT
|
|
<CancelFee>
|
Numeric
|
9
|
BR1CCPALT
|
|
<TotAmtDue>
|
Numeric
|
9
|
BR1CTBDLT
|
|
<AgncyCommission>
|
Numeric
|
9
|
BR1CCMALT
|
|
|
|
+ <CruiseSeg>
|
IT12 1.0
|
|
|
|
<SegNum>
|
Numeric
|
2
|
As unpacked in BFWC/AAA
|
|
<StartDt>
|
Numeric
|
8
|
YYYYMMDD
|
|
<EndDt>
|
Numeric
|
8
|
YYYYMMDD
|
|
<Vnd>
|
Alphanumeric
|
3
|
Left justified
|
|
<PkgDesc>
|
Alpha
|
30
|
BR1CTNMLH
|
|
<ShipName>
|
Alpha
|
25
|
BR1CSHPLH
|
|
<ConfNum>
|
Alphanumeric
|
16
|
BR1CVRFLH
|
|
<DocMailDate>
|
Numeric
|
8
|
YYYYMMDD (if mailed) BR1CDMDLT
|
|
<Currency>
|
Alpha
|
3
|
BR1CCURLH
|
|
<TotAmt>
|
Numeric
|
9
|
BR1CCTLLC
|
|
<DecPos>
|
Numeric
|
1
|
BR1CDECLH
|
|
<Dep1DueDt>
|
Numeric
|
8
|
YYYYMMDD BR1CDD1LE
|
|
<Dep1RecvDt>
|
Numeric
|
8
|
YYYYMMDD (if received) BR1CDR1LE
|
|
<Dep2DueDt>
|
Numeric
|
8
|
YYYYMMDD BR1CDD2LE
|
|
<Dep2RecvDt>
|
Numeric
|
8
|
YYYYMMDD (if received) BR1CDR2LE
|
|
<BalanceDueDt>
|
Numeric
|
8
|
YYYYMMDD BR1CBDDLE
|
|
<BalanceRecvDt>
|
Numeric
|
8
|
YYYYMMDD (if received) BR1CDBRLE
|
VndTextLen
Structured data only.
Not in XML.
|
Numeric
|
2
|
BR1CLNTLE
|
|
<VndText>
|
Alpha
|
VL
|
BR1CTXTLE
|
|
|
|
+ <ARNK>
|
IT13 1.0
|
|
|
|
<SegNum>
|
Numeric
|
2
|
As unpacked in BFWC/AAA
|
|
|
|
+ <TrainSeg>
|
IT14 1.0
|
|
|
|
<SegNum>
|
Numeric
|
2
|
As unpacked in BFWC/AAA
|
|
<ServiceType>
|
Alpha
|
1
|
R - Rail
B - Bus
|
|
<StartDt>
|
Numeric
|
8
|
YYYYMMDD
|
|
<DayChg>
|
Alphanumeric
|
2
|
-1, 00, 01 to 09 are valid.
Indicates arrival date as number of days before or after departure date.
|
|
<StartTm>
|
Numeric
|
4
|
HHMM
Blank if not available
|
|
<EndTm>
|
Numeric
|
4
|
HHMM
Blank if not available
|
|
<TrainNum>
|
Alphanumeric
|
5
|
Blank if not available
|
|
<TariffType>
|
Alpha
|
1
|
M - Metroliner
C - Conventional
Blank if not available
|
|
<ConfNum>
|
Alphanumeric
|
4
|
Blank if not available
|
StartPtTextLen
Structured data only.
Not in XML.
|
Numeric
|
2
|
Length of Board Point field to follow
|
EndPtTextLen
Structured data only.
Not in XML.
|
Numeric
|
2
|
Length of Off Point field to follow
|
TextLen
Structured data only.
Not in XML.
|
Numeric
|
2
|
Length of Freetext field to follow
Zero if field does not exist
|
|
|
|
+ <AirSegDetail>
|
IT16 1.0
|
|
|
|
+ <SegAry>
|
Array
|
n/a
|
|
This KLR is returned only when the Change Of Gauge field is set to "Y" in the preceding Air Segment KLR (IT01). The IT16 follows the IT01 to which it is related.
|
|
+ <Seg>
|
FieldSet
|
n/a
|
|
|
<StartDt>
|
Numeric
|
8
|
Departure date of this leg. YYYYMMDD format
|
|
<StartAirp>
|
Alpha
|
5
|
Left justified blank filled
|
|
<EndAirp>
|
Alpha
|
5
|
Left justified blank filled
|
|
<Equip>
|
Alphanumeric
|
3
|
Aircraft type operating this leg
|
|
<COGInd>
|
Alpha
|
1
|
'Y'= Change of aircraft at this board point
'N'= No change of aircraft
|
|
|
|
|
|
|
|
+ <SeatSeg>
|
ST01 1.0
|
|
|
|
<AirV>
|
Alpha
|
3
|
Left justified.
|
|
<StartDt>
|
Numeric
|
8
|
Date in YYYYMMDD format.
|
|
<BIC>
|
Alpha
|
2
|
Left justified.
|
|
<StartAirp>
|
Alpha
|
5
|
Airport Code
|
|
<EndAirp>
|
Alpha
|
5
|
Airport Code
|
|
<FltSegNum>
|
Numeric
|
3
|
Segment number of the flight on which seats are assigned.
|
|
<NumPsgrs>
|
Numeric
|
2
|
Number of passengers booked on this air segment.
Note: Do not assume this number equals the number of Seat Assignment (ST02) KLRs to follow because not all passengers necessarily have seats assigned
|
|
<COGNum>
|
Numeric
|
2
|
Indicates the sequence the ST01's should be displayed to the agent for a c.o.g flight
Starts at "01".
Always blank for a non c.o.g flight.
|
|
|
|
+ <SeatAssignment>
|
ST02 1.0
|
|
|
|
The next three fields identify which passenger the seat is assigned to.
|
|
<LNameNum>
|
Numeric
|
2
|
Currently this field is always blank for 1V responses.
Unique sequential number identifying the last name grouping.
Eg: Smith=1, Jones=2
|
|
<PsgrNum>
|
Numeric
|
2
|
Currently this field is always blank for 1V responses.
Sequential number identifying a passenger within a last name grouping.
Eg: Smith/A=1, Smith/B=2, Jones/A=1, Jones/B=2
|
|
<AbsNameNum>
|
Numeric
|
2
|
Unique sequential number identifying each passenger irrespective of last name.
Eg: Smith/A=1, Smith/B=2, Jones/A=3, Jones/B=4
|
|
<Status>
|
Alpha
|
2
|
'NN' - Seats will be requested from airline.
'PN' - Seats have been requested from airline.
'HK' - Seats are confirmed
'NO' - Seat request has been denied by airline.
|
|
<Locn>
|
Alphanumeric
|
5
|
An airline seat location is always 3 bytes, consisting of a 2 digit row number followed by a column letter. The remaining 2 bytes are spares for future rail or ferry seat locations.
Examples: '03A ', '47J '
If a specific seat location has not been assigned this field will be blanks.
|
|
+ <AttribAry>
|
Array
|
n/a
|
|
|
<Attrib>
|
Alphanumeric
|
2
|
Left justified, blank filled
EDIFACT standard is used
|
|
|
CommentLen
Structured data only.
Not in XML.
|
Numeric
|
2
|
'00' if no comment exists.
|
|
<Comment>
|
Alphanumeric
|
VL
|
Free form text.
|
|
|
|
|
|
+ <EndTransaction>
|
2031 6.0
|
|
|
|
|
2031 - End Transaction Response
Version: 06.00
Procedure/TranSession Application Error Severity Code
00No error
01Application error - procedure terminated
Data Record Application Return Codes
00 No error
02 Security violation
03 Simultaneous changes to the PNR
20 Optional error (not critical enough to stop process)
28 Miscellaneous error code
40 Miscellaneous mandatory error
41 Phone field mandatory error
42 Received field mandatory error
43 Itinerary field mandatory error
44 Names field mandatory error
45 Ticketing field mandatory error
|
|
<FileAddr>
|
Numeric
|
8
|
PNR File Address
|
|
<RecCodeChk>
|
Numeric
|
2
|
PNR Record Code Check
|
|
<RecLoc>
|
Alphanumeric
|
6
|
PNR Record Locator
|
|
|
|
|
+ <PNRBFPrimaryBldChg>
|
2101 6.0
|
|
|
|
|
|
<Len>
|
Numeric
|
4
|
Total length including this field
|
|
<RecID>
|
Alphanumeric
|
4
|
'EROR'
|
|
<AryCnt>
|
Numeric
|
3
|
Number of inserted text items in this response block
|
|
<DelimiterCharacter>
|
Alphanumeric
|
1
|
Not used - always 'F'
|
|
<LevelNum>
|
Numeric
|
2
|
Not used - always '00'
|
|
<VersionNum>
|
Numeric
|
2
|
Version of this response block - currently '01'
|
|
<Err>
|
Alphanumeric
|
8
|
Error code for use by the client to construct the error message.
Blank if not available.
|
|
<DataBlkInd>
|
Alphanumeric
|
4
|
The Data Block Indicator from the 2100 request which caused the error.
J = Profile move error
M = Freq Flyer error
N = Name error
P = Phone error
T = Ticketing error
W = Address error
Blank if not known or not applicable.
|
|
+ <InsertedTextAry>
|
Array
|
n/a
|
|
|
+ <InsertedText>
|
FieldSet
|
n/a
|
|
|
<Offset>
|
Numeric
|
3
|
Location of start of inserted text in Error Text field
|
|
|
|
|
|
<Text>
|
Alphanumeric
|
To End
|
Complete error message, including any inserted text items
|
|
|
|
|
+ <PNRBFSecondaryBldChg>
|
2111 6.0
|
|
|
|
|
|
<Len>
|
Numeric
|
4
|
Total length including this field
|
|
<RecID>
|
Alphanumeric
|
4
|
'EROR'
|
|
<AryCnt>
|
Numeric
|
3
|
Number of inserted text items in this response block
|
|
<DelimiterCharacter>
|
Alphanumeric
|
1
|
Not used - always 'F'
|
|
<LevelNum>
|
Numeric
|
2
|
Not used - always '00'
|
|
<VersionNum>
|
Numeric
|
2
|
Version of this response block - currently '01'
|
|
<Err>
|
Alphanumeric
|
8
|
Error code for use by the client to construct the error message.
Blank if not available.
|
|
<DataBlkInd>
|
Alphanumeric
|
4
|
The Data Block Indicator from the 2110 request which caused the error.
C = Customer ID
D = Delivery Address
F = Form of Payment
G = General Remarks
H = Associated Itin Rmks
I = Non Associated Itin Rmks
K = Ticketing Remarks
L = Postscript Note
O = OSI
Q = Q-Minders
S = SSR
V = Vendor Remarks
W = Address
X = Doc/Invoice Remarks
Y = Due/Paid/Text
Blank if not known or not applicable.
|
|
+ <InsertedTextAry>
|
Array
|
n/a
|
|
|
+ <InsertedText>
|
FieldSet
|
n/a
|
|
|
<Offset>
|
Numeric
|
3
|
Location of start of inserted text in Error Text field
|
|
|
|
|
|
<Text>
|
Alphanumeric
|
To End
|
Complete error message, including any inserted text items
|
|
|
|
|
+ <HtlSegSell>
|
6151 6.0
|
|
|
|
|
|
<TypeInd>
|
Alphanumeric
|
1
|
Description of Field:
Type of response.
Format (x-alpha/numeric):
x
Possible Values (List):
0=Normal. The detail sell response follows. This value is a numeric zero, not an alpha.
E= Error message returned.
F= Link sell failed. Only the error message and link free form text returned in a 6152 block.
How is null data specified?
N/A
What does null data indicate?
No data results in an error.
|
|
<NumRuleLines>
|
Numeric
|
2
|
Description of Field:
The number of free form text lines that follow in all 6152 blocks. Can be 0 to 50
Format (n-numeric):
nn
Special Format:
Right justified, zero filled
How is null data specified?
This field will be zero or blank.
What does null data indicate?
There are no free form text blocks.
|
|
+ <TypeIndEFQual>
[Qualified By: TypeInd of E,F]
|
FieldSet
|
n/a
|
|
|
<ErrMsg>
|
Character
|
64
|
Description of Field:
Free form text
Format (c-character):
cccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccc
Special Format:
Left justified, blank filled
Examples:
Room type is closed.
Invalid credit card.
How is null data specified?
N/A
What does null data indicate?
N/A
|
|
<ErrNum>
|
Character
|
4
|
Description of Field:
This is the number that corresponds to the previous error text.
Format (c-character):
cccc
Special Format:
Right justified, zero filled
How is null data specified?
N/A
What does null data indicate?
N/A
|
|
|
|
+ <TypeInd0Qual>
[Qualified By: TypeInd of 0]
|
FieldSet
|
n/a
|
|
|
<SegNum>
|
Numeric
|
2
|
Description of Field:
This field contains the number assigned to is by PNR/BF processing.
Format (n-numeric):
nn
Special Format:
Right justified, zero filled
Possible Values (Range):
01 to 99
How is null data specified?
N/A
What does null data indicate?
N/A
|
|
<SellStatusInd>
|
Alpha
|
1
|
Description of Field:
This indicates the success of the sell request.
Format (a-alpha):
a
Possible Values (List):
S= Sold
N= Need
How is null data specified?
N/A
What does null data indicate?
N/A
|
|
<StartDt>
|
Numeric
|
8
|
Description of Field:
This is the date the customer will arrive (check in) at the hotel.
Format:
CCYYMMDD
Examples:
20030614
How is null data specified?
N/A
What does null data indicate?
N/A
|
|
<EndDt>
|
Numeric
|
8
|
Description of Field:
This is the date the customer will leave (check out) the hotel.
Format:
CCYYMMDD
Examples:
20030829
How is null data specified?
N/A
What does null data indicate?
N/A
|
|
<NumNights>
|
Numeric
|
2
|
Description of Field:
The number of nights sold for this reservation
Format (n-numeric):
nn
Special Format:
Right justified, zero filled
How is null data specified?
N/A
What does null data indicate?
N/A
|
|
<PrimaryCity>
|
Alpha
|
5
|
Description of Field:
The primary city code for the property sold.
Format (a-alpha):
aaaaa
Special Format:
Code is three characters, left justified, and blank filled.
Examples:
DEN
CHI
NYC
How is null data specified?
N/A
What does null data indicate?
N/A
|
|
<Chain>
|
Alphanumeric
|
3
|
Description of Field:
Property's chain code
Format (x-alpha/numeric):
xxx
Special Format:
Left justified, blank filled
Examples:
HI
RA
How is null data specified?
N/A
What does null data indicate?
N/A
|
|
<RoomMasterID>
|
Numeric
|
5
|
Description of Field:
Property's RoomMaster number
Format ( n-numeric):
nnnnn
Special Format:
Right justified, zero filled
Examples:
14853
04205
How is null data specified?
N/A
What does null data indicate?
N/A
|
|
<BIC>
|
Alphanumeric
|
7
|
Description of Field:
The full booking code for the rate sold
Format (x-alpha/numeric):
xxxxxxx
Special Format:
Left justified, blank filled.
Examples:
B1KRAC
A2T000C
How is null data specified?
N/A
What does null data indicate?
N/A
|
|
<NumPersons>
|
Numeric
|
1
|
Description of Field:
This is the number of adults.
Format (n-numeric):
n
Special Format:
N/A
How is null data specified?
N/A
What does null data indicate?
N/A
|
|
<NumRooms>
|
Numeric
|
1
|
Description of Field:
The number of rooms reserved.
Format (n-numeric):
n
Possible Values (Range):
1 to 9
How is null data specified?
N/A
What does null data indicate?
N/A
|
|
<ConfNum>
|
Alphanumeric
|
30
|
Description of Field:
Confirmation number supplied by the hotel. This may be blank for non-link vendors.
Format (x-alpha/numeric):
xxxxxxxxxxxxxxxxxxxxxxxxxx
Special Format:
Left justified, blank filled
Examples:
A44T9QPM
How is null data specified?
This field is blank.
What does null data indicate?
The hotel vendor is not a Link vendor.
|
|
<RateGuarInfo>
|
Alpha
|
2
|
Description of Field:
This indicates the level of guarantee the hotel offers for this rate.
Format (a-alpha):
aa
Possible Values (List):
RT= RoomMaster rate, or rate not guaranteed by vendor
RG= Vendor guaranteed
RQ= Vendor quoted rate, but not guaranteed
How is null data specified?
N/A
What does null data indicate?
N/A
|
|
<RateChgInd>
|
Alpha
|
1
|
Description of Field:
This field indicates if the rate changes during the guest's stay.
Format (a-alpha):
a
Possible Values (List):
Y= Rate changes during length of stay
N= No change over the period
How is null data specified?
This field will be blank.
What does null data indicate?
Blank = N.
|
|
<MultipleDayRateInd>
|
Alpha
|
1
|
Description of Field:
The returned rate is for more than one night.
Format (a-alpha):
a
Possible Values (List ):
Y= Rate applies to more than one day, as in a package
N= Normal application of rate period
How is null data specified?
This field may be blank.
What does null data indicate?
Blank = N.
|
|
<Currency>
|
Alphanumeric
|
3
|
Description of Field:
Currency in which the rate was sold
Format (x-alpha/numeric):
xxx
Examples:
USD
GBP
How is null data specified?
N/A
What does null data indicate?
N/A
|
|
<DecPos>
|
Numeric
|
1
|
Description of Field:
The number of places to the right of the implied decimal for the currency the rates are quoted
Format (n-numeric):
n
Possible Values (Range):
0 - 3
How is null data specified?
N/A
What does null data indicate?
N/A
|
|
<ExtraChargeDecPos>
|
Numeric
|
1
|
Description of Field:
The number of implied decimals in rates for extra charges
Format (n-numeric):
n
Possible Values (Range):
0 - 3
How is null data specified?
N/A
What does null data indicate?
N/A
|
|
<RateAmt>
|
Numeric
|
9
|
Description of Field:
The room amount expressed in the currency defined by Currency. Location of implied decimal point specified by Number of Implied Decimals.
Format (n-numeric):
nnnnnnnnn
Special Format:
Right justified, zero filled
How is null data specified?
N/A
What does null data indicate?
N/A
|
|
<MultilevelRate>
|
Alpha
|
6
|
Description of Field:
The multilevel code used to sell a negotiated rate.
Format (a-alpha):
aaaaaa
Special Format:
Left justified, blank filled
Examples:
A1KRAC
B2DT00
How is null data specified?
This field will be blanks.
What does null data indicate?
No multilevel rate was sold.
|
|
<OptDataNotAcceptedbyV>
|
Alpha
|
10
|
Description of Field:
This field will contain the optional fields that the hotel vendor does not accept. It will be the concatenation of the two byte codes used in the request.
Format (a-alpha):
aaaaaaaaaa
Special Format:
Left justified, blank filled
Examples:
ECFGFTCDNM
How is null data specified?
This field will be blanks.
What does null data indicate?
No optional fields were rejected by the hotel.
|
OptFldCnt
Structured data only.
Not in XML.
|
Numeric
|
2
|
Description of Field:
The number of optional fields that follow at the end of the header
Format (n-numeric):
nn
Special Format:
Right justified, zero filled
How is null data specified?
This field will be zeroes.
What does null data indicate?
No optional fields were used on the sell.
|
|
+ <OptFldAry>
|
Array
|
n/a
|
|
|
+ <OptFld>
|
FieldSet
|
n/a
|
|
|
<ID>
|
Alpha
|
2
|
Description of Field:
Identifies which optional data is represented by this group
Format (a-alpha):
aa
Possible Values (List ):
AC = Alternate Currency
VC = Vendor Currency
AV= Advance deposit
BS= Booking source
RT = Corporate rate override
RG= Guaranteed rate
DP= Deposit
RQ= Quoted rate
RR= Rate request
GT= Payment guarantee
AD= Customer address
RA= Rollaway bed adult
RB = Alternate currency Rollaway bed adult
RD= Rollaway bed child
RE = Alternate Currency Rollaway bed child
CR= Cribs
CS = Alternate Currency Crib
EX= Extra adult
EY = Alternate Currency Extra Child
EC= Extra child
ED = Alternate Currency Extra Child
TN= Tour number
RL= Tour room location
MP= Tour meal plan
CD= Corporate discount number
FG= Frequent guest number
FT= Frequent air traveler number
ID= Customer ID number
SI= Special information
NF= Reservation name - first
NL= Reservation name - last
How is null data specified?
N/A
What does null data indicate?
If no optional data was specified, this field will not be present.
|
Len
Structured data only.
Not in XML.
|
Numeric
|
3
|
Description of Field:
The number of bytes contained in the Optional Field Contents that follows
Format (n-numeric):
nnn
Special Format:
Right justified, zero filled
How is null data specified?
N/A
What does null data indicate?
If no optional data was specified, this field will not be present.
|
|
<Contents>
|
Alpha
|
VL
|
Description of Field:
This field contains the details of the optional data based on the type specified in Optional Field Identity.
Format (a-alpha):
aaaaaaaaaa
Examples:
AX1234567890EXP0405
How is null data specified?
N/A
What does null data indicate?
If no optional data was specified, this field will not be present.
|
|
|
|
|
|
|
|
|
|
|
+ <HtlSegSellText>
|
6152 6.0
|
This section repeats based on the contents of the Items This Block field.
|
|
|
The following detail block will be repeated one or more times when there is free form text to be returned. It is the 6152 transaction.
|
RuleLineCnt
Structured data only.
Not in XML.
|
Numeric
|
2
|
The number of text lines returned in this block. A maximum of 15 is allowed in each HHLT block.
|
|
<TotRuleLineCnt>
|
Numeric
|
4
|
The total number of lines that will be returned from all 6152 blocks
|
|
+ <RuleLineAry>
|
Array
|
n/a
|
|
|
<TxtLine>
|
Character
|
64
|
Repeats n times depending on the value in Items This Block field above.
|
|
|
|
|
|
|
+ <CarSegSell>
|
7151 7.0
|
|
|
|
|
|
Purpose: The response block described here is used both by the Car Sell and modify transactions. The Response Identity field will be set for the particular situation. Any free form text data will be returned in an associated 7152 transaction block.
|
|
<Type>
|
Alphanumeric
|
1
|
Status of the request:
0=No errors, successful sell
E=Error with no items returned
W=Successful sell with warning message
F=Link sell failed, only error message and link text returned in a 7152 block
L=Successful Link sell - Output includes MVS detail and link text
|
|
<RuleLineCnt>
|
Numeric
|
2
|
The number of free form or rule text lines that follow in a 7152 block
|
|
+ <TypeEWFQual>
[Qualified By: Type of E,F,W]
|
FieldSet
|
n/a
|
|
|
|
|
+ <Type0WLQual>
[Qualified By: Type of 0,L,W]
|
FieldSet
|
n/a
|
|
|
The following block of fields contain MVS-generated detail and is returned when the Type Response Returned field is 0, W, or L.
|
|
<SegNum>
|
Numeric
|
2
|
01 to 99
|
|
<SellStatus>
|
Alpha
|
1
|
S=Sold
N=Need
C=Closed
E=Error during validation, non-critical
|
|
<StartDt>
|
Numeric
|
8
|
CCYYMMDD format
|
|
<StartTm>
|
Numeric
|
4
|
Pickup time expressed in 24 hour clock format
|
|
<StartAirV>
|
Alphanumeric
|
3
|
|
|
<StartFltNum>
|
Alphanumeric
|
4
|
|
|
<Airp>
|
Alpha
|
5
|
Airport code where car is being rented
|
|
<PickupLocn>
|
Alpha
|
5
|
Code of actual car pickup location (From the /PUP optional field)
|
|
<LocnExpansion>
|
Numeric
|
1
|
Reserved for future use
|
|
<PickUpAddr>
|
Alphanumeric
|
45
|
Address of pickup location
|
|
<PickUpPhone>
|
Alphanumeric
|
40
|
Phone number of pickup location
|
|
<EndDt>
|
Numeric
|
8
|
CCYYMMDD format
|
|
<EndTm>
|
Numeric
|
4
|
Return time expressed in 24 hour clock format
|
|
<EndAirV>
|
Alphanumeric
|
3
|
Airline code if customer is departing by air
|
|
<EndFltNum>
|
Alphanumeric
|
4
|
Associated flight number when it applies
|
|
<NumCars>
|
Numeric
|
2
|
Number of cars reserved
|
|
<AltV>
|
Alpha
|
3
|
Identification of alternate vendor name used at this location, if any
|
|
<ConfNum>
|
Character
|
30
|
Confirmation number when supplied by Link vendors. MVS does not generate this number.
|
|
<RateCodeDesc>
|
Character
|
55
|
|
|
<HrsPassFailInd>
|
Alpha
|
1
|
Y=Pass
N=Fail
|
|
<RateType>
|
Alpha
|
1
|
D=Daily
E=Weekend
W=Weekly
M=Monthly
H=Hourly
P=Package
|
|
<RateCat>
|
Alpha
|
1
|
A=Association
B=Business standard
C=Corporate
G=Government
I=Industry
K=Package
L=Inclusive
P=Promotional
R=Credential
S=Standard
U=Consortium
V=Convention
X=Negotiated
|
|
<CarType>
|
Alpha
|
4
|
ECAR, ICAR, etc.
|
|
<CarTypeDesc>
|
Alpha
|
30
|
Description of car type selected
|
|
<YieldMgmtNum>
|
Character
|
1
|
Blank, or 1 through 9
|
|
<Currency>
|
Alpha
|
3
|
Currency in which rates were sold
|
|
<DecPos>
|
Numeric
|
1
|
The number of implied places to the right of the implied decimal for the currency the rates are quoted in
|
|
<RateAmt>
|
Numeric
|
9
|
The car rate expressed in the currency defined by Currency. Location of implied decimal point specified by Number of Decimals. This applies to all rate fields. Note: All 9s mean maximum display limit exceeded.
|
|
<NumRateUnits>
|
Alpha
|
3
|
Number of units; used to calculate Base Rate
|
|
<NumExtraDays>
|
Alpha
|
3
|
Number of extra; days used to calculate Base Rate
|
|
<NumExtraHrs>
|
Alpha
|
3
|
Number of extra; hours used to calculate Base Rate
|
|
<BaseRate>
|
Numeric
|
12
|
Sum for Rate type + extra day chg + extra hour chg
|
|
<RateGuarInd>
|
Alpha
|
1
|
G=Rate guaranteed
Q=Rate quoted
T=Agent entered
Blank= (no rate exists)
|
|
<MilesOrKiloInd>
|
Alpha
|
1
|
M= Miles
K= Kilometers or Blank
|
|
<MileAllow>
|
Alphanumeric
|
5
|
|
|
<RequiredChgs>
|
Character
|
15
|
|
|
<AdvBkUnitInd>
|
Alpha
|
1
|
D=Days
H=Hours or Blank
|
|
<NumAdvBkUnits>
|
Numeric
|
3
|
|
|
<AdvBkPassFailInd>
|
Alpha
|
1
|
Y=Pass
N=Fail
Or Blank
|
|
<ExtraDayInd>
|
Alpha
|
1
|
Y=Extra Day fields exist in the Rate Information Section
N=Extra Day fields not included
|
|
<ExtraHourInd>
|
Alpha
|
1
|
Y=Extra Hour fields exist in the Rate Information Section
N=Extra Hour fields not included
|
|
<RuleInfoExistsInd>
|
Alpha
|
1
|
Y=The Rule Information Section is included
N=Rule Information Section does not follow
|
OptFldIDCnt
Structured data only.
Not in XML.
|
Numeric
|
2
|
The number of optional fields that follow at the end of the header
|
|
+ <ExtraDayYQual>
[Qualified By: ExtraDayInd of Y]
|
FieldSet
|
n/a
|
|
|
<RateAmt>
|
Numeric
|
9
|
Note: All 9s mean maximum display limit exceeded.
|
|
<MileRateAmt>
|
Numeric
|
9
|
Note: All 9s mean maximum display limit exceeded.
|
|
|
|
+ <ExtraHrsYQual >
[Qualified By: ExtraHourInd of Y]
|
FieldSet
|
n/a
|
|
|
<RateAmt>
|
Numeric
|
9
|
Note: All 9s mean maximum display limit exceeded.
|
|
<MileRateAmt>
|
Numeric
|
9
|
Note: All 9s mean maximum display limit exceeded.
|
|
|
|
+ <RuleExistsYQual >
[Qualified By: RuleInfoExistsInd of Y]
|
FieldSet
|
n/a
|
|
|
<MinMaxUnitInd>
|
Alpha
|
1
|
H=Hour
D=Day or Blank
|
|
<MinRentalUnits>
|
Character
|
3
|
|
|
<MinRentalPassFailInd>
|
Alpha
|
1
|
Y=Pass
N=Fail
or Blank
|
|
<MaxRentalUnits>
|
Character
|
3
|
|
|
<MaxRentalPassFailInd>
|
Alpha
|
1
|
Y=Pass
N=Fail
or Blank
|
|
<NumAbsMaxDays>
|
Character
|
3
|
The maximum number of days the car can be kept, period!
|
|
<EarlyStartTm>
|
Character
|
4
|
|
|
<EarlyStartPassFailInd>
|
Alpha
|
1
|
Y=Pass
N=Fail
or Blank
|
|
<LatestStartTm>
|
Character
|
4
|
|
|
<LatestStartPassFailInd>
|
Alpha
|
1
|
Y=Pass
N=Fail
or Blank
|
|
<DropOffInd>
|
Alpha
|
1
|
Y=Yes
N=No Indicates Drop Off data exists.
|
|
<DropOffV>
|
Alpha
|
3
|
Vendor ID
|
|
<DropOffNum>
|
Alphanumeric
|
3
|
|
|
<DropOffAddr>
|
Alphanumeric
|
45
|
|
|
<DropOffPhone>
|
Alphanumeric
|
40
|
|
|
<DropOffHrs>
|
Alphanumeric
|
40
|
|
|
<DropChargeAmt>
|
Numeric
|
10
|
|
|
<LatestEndTm>
|
Character
|
4
|
|
|
<LatestEndPassFailInd>
|
Alpha
|
1
|
Y=Pass
N=Fail
or Blank
|
|
<DepAmt>
|
Numeric
|
9
|
Note: All 9s mean maximum display limit exceeded.
|
|
<DepInd>
|
Alpha
|
1
|
D=Number of days
A=Dollar amount
P=Percent of total or Blank
|
|
<DepEffectiveDt>
|
Numeric
|
8
|
CCYYMMDD (Century, Year, Month, Day)
|
|
<DepDiscontinueDt>
|
Numeric
|
8
|
CCYYMMDD (Century, Year, Month, Day)
|
|
<DepDaysPassFailInd>
|
Alpha
|
1
|
Y=Pass
N=Fail
or Blank
|
|
<RateGuarEffectiveDt>
|
Numeric
|
8
|
CCYYMMDD (Century, Year, Month, Day)
|
|
<RateGuarDiscontinueDt>
|
Numeric
|
8
|
CCYYMMDD (Century, Year, Month, Day)
|
|
<GuarRatePassFailInd>
|
Alpha
|
1
|
Y=Pass
N=Fail
or Blank
|
|
|
|
+ <OptFldIDAry>
|
Array
|
n/a
|
|
Comments on Optional Field Contents
Some optional fields are contained in the fixed header part of this transaction, for example, confirmation number.
RG
RQ
RT Only one of these fields will be returned in the output. They are mutually exclusive.
|
|
+ <OptFldID>
|
FieldSet
|
n/a
|
|
|
This section contains the optional fields stored at the host. The following 3 fields are repeated for each optional field.
|
|
<ID>
|
Alpha
|
2
|
Identifies which optional data is represented by this group:
RT=Corporate rate override
RG=Guaranteed rate
RQ=Quoted rate
BS=Booking source
AD=Customer address
ID=Customer ID
PU=Pick up location
TN=Tour number
CD=Corporate ID
SI=Special information
FT=Frequent air traveler number
SQ=Special equipment
GT=Payment guarantee
PR=Prepayment information
DL=Drivers license
DC=Drop off charge
DO=Drop off location
AC=Alternate Currency code
VC=Vendor Currency code
NF=Reservation name - first
NL=Reservation name - last
|
Len
Structured data only.
Not in XML.
|
Numeric
|
3
|
The number of bytes contained in the Optional Field Contents that follows
|
|
<Contents>
|
Alpha
|
VL
|
This field contains the details of the optional data based on the type specified in Optional Field Identity. The field size depends on the contents. See comments which follow.
|
|
|
|
|
|
|
|
|
|
|
+ <CarSegSellText>
|
7152 7.0
|
|
|
|
|
LineDescCnt
Structured data only.
Not in XML.
|
Numeric
|
2
|
The number of text lines returned in this block. A maximum of 15 is allowed in each CART block.
|
|
<TotLineDescCnt>
|
Numeric
|
4
|
The total number of lines that will be returned from all 7152 blocks
|
|
+ <LineDescAry>
|
Array
|
n/a
|
|
|
This section repeats based on the contents of the Items This Block field.
|
|
+ <LineDescInfo>
|
FieldSet
|
n/a
|
|
|
<LineDesc>
|
Numeric
|
1
|
0=Continuation of last rule
1=Pick up rule
2=Deposit Rule
3=Guarantee Rule
4=General Rules includes Link free form text
|
|
<Txt>
|
Character
|
64
|
NOTE: This text may be suppressed depending on the contents of the Return Rule Text Indicator field in the Sell request transaction.
|
|
|
|
|
|
|
|
|
|
|