|
+ Requests
|
|
+ <FareRedisplayMods>
|
4014 2.2
|
|
+ <DisplayAction>
|
DPDT 1.0
|
|
|
|
<Action>
|
Alpha
|
1
|
Field Description:
Action.
Possible Values (List):
I-Fare Index
D-Fare Details (only one fare can be requested per detailed request)
Format (a-alpha):
a
Special Format:
N/A
Examples:
I
How is null data specified?
N/A
What does null data indicate?
No data results in error
|
|
|
|
+ <FareNumInfo>
|
DPFI 1.0
|
|
|
|
+ <FareNumAry>
|
Array
|
n/a
|
|
|
<FareNum>
|
Numeric
|
3
|
Field Description:
Fare number of the item to which the following KLRs relate.
Format (n-numeric):
nnn
Special Format:
Right justified, zero filled.
Examples:
001
How is null data specified?
N/A
What does null data indicate?
No data results in error.
|
|
|
|
|
|
|
|
+ <ManualFareUpdateSaveMods>
|
4016 1.3
|
|
+ <PenMod>
|
DP01 1.0
|
|
|
|
<Pen>
|
Numeric
|
3
|
Description of Field:
Penalty Percentage - mandatory
Format (a-alpha, n-numeric, x-alpha/numeric):
nn(space)
Special Format:
Left justified character blank filled.
Possible Values (List or Range):
e.g., Range
0 - 99
How is null data specified?
NA
What does null data indicate?
No data results in error
|
|
|
|
<NoMinOrMaxStayMod>
|
DP04 1.0
|
|
<NoRestrictionsMod>
|
DP05 1.0
|
|
+ <PICOptMod>
|
DP07 2.0
|
|
|
|
NOTE: Can be passenger related (if so, this KLR will be preceded by a DPPI KLR)
|
|
<PIC>
|
Alphanumeric
|
8
|
Description of Field:
PTC code - mandatory
Format (x-alpha/numeric):
xxxxxxxx
Special Format
Left justified character blank filled.
Examples:
SRC - senior citizen
C08 - child, age 8
IP10 - (Increase Percentage 10%) percentage all passengers
How is null data specified?
NA
What does null data indicate?
e.g., No data results in error
Note: If PTC is not found it will default to the adult fare.
|
|
<PersonalGeoType>
|
Numeric
|
1
|
Field Description:
Designates the Type/Format for the Personal Geography Data
Format (n-numeric):
n
Possible Values (List)
1 - Nation
2 - State/Province
3 - City
How is null data specified?
N/A
What does null data indicate?
This field is required to be sent.
|
|
<PersonalGeoData>
|
Alpha
|
4
|
Field Description:
Personal Geography modifier according to the Type indicated.
Format (a-alpha):
aaaa
Examples:
US Type 1 - 2 character country code
CAPQ Type 2 - 2 character country code plus 2 character state/province code
DEN Type 3 - 3 character city location code
How is null data specified?
N/A
What does null data indicate?
This field is required to be sent.
|
|
|
|
+ <PICOnlyMod>
|
DP08 2.0
|
|
|
|
<PIC>
|
Alphanumeric
|
8
|
Description of Field:
PTC code - mandatory
Format (x-alpha/numeric):
xxxxxxxx
Special Format
Left justified character blank filled.
Examples:
SRC - senior citizen
C08 - child, age 8
IP10 - (Increase Percentage 10%) percentage all passengers
How is null data specified?
NA
What does null data indicate?
e.g., No data results in error
Note: If PTC code is not found an error message will be returned. If there are no valid fares for this PTC, the system will NOT default to an Adult fare
|
|
<PersonalGeoType>
|
Numeric
|
1
|
Field Description:
Designates the Type/Format for the Personal Geography Data
Format (n-numeric):
n
Possible Values (List)
1 - Nation
2 - State/Province
3 - City
How is null data specified?
N/A
What does null data indicate?
This field is required to be sent.
|
|
<PersonalGeoData>
|
Alpha
|
4
|
Field Description:
Personal Geography modifier according to the Type indicated.
Format (a-alpha):
aaaa
Examples:
US Type 1 - 2 character country code
CAPQ Type 2 - 2 character country code plus 2 character state/province code
DEN Type 3 - 3 character city location code
How is null data specified?
N/A
What does null data indicate?
This field is required to be sent.
|
|
|
|
+ <PFMod>
|
DP09 2.0
|
|
|
|
<Acct>
|
Alphanumeric
|
20
|
Field Description:
Account code:
Mandatory field used to input the Account code defined in the client's Private Fare contract
Format (x-alpha/numeric):
xxxxxxxxxxxxxxxxxxxx
Special Format:
Left justified, blank filled.
Examples:
AMEX
IBM
CREATIV
How is null data specified?
N/A
What does null data indicate?
No data results in no error
|
|
<PCC>
|
Alphanumeric
|
4
|
Description of Field:
Pseudo City Code:
Optional field used to input a 3 or 4 character code identifying the agency or client
Format (a-alpha, n-numeric, x-alpha/numeric, c-character):
XXXX
Special Format:
Left Justified Blank Filled
PCCs with less than 4 characters should be padded with a leading zero. For example, X0B should be submitted as 0X0B.
CDATA can also be used to override the attributes of this field. For example,
![CDATA[ X0B]]
In this case the field is forced to right justify with a leading blank.
Field may be null (optional).
Examples:
1WP7
0X0B
![CDATA[ X0B]]
![CDATA[2GK5]]
How is null data specified?
Character blanks
What does null data indicate?
No user data was input.
|
|
<Contract>
|
Alphanumeric
|
10
|
Field Description:
Contract Code:
Optional field used to input the Contract Code defined in the client's Private Fare contract.
Format (x-alpha/numeric):
xxxxxxxxxx
Special Format:
Left justified, blank filled.
Examples:
SIN20
CXEUR
How is null data specified?
Null data is specified by blanks.
What does null data indicate?
Blank if Contract Code does not exist.
|
|
<PFType>
|
Alphanumeric
|
1
|
Field Description:
Private Fare Type:
Optional field used to restrict pricing to Private Fares of a certain type.
Format (x-alpha/numeric):
x
Possible Values:
P = Only private fares will be considered during quote processing. They may or may not be associated to the account code (other field settings may indicate other types of restrictions which will also be applied). If no valid private fare exists to cover the segment, then no quote will be returned.
Q = Only private fares associated with the input account code will be considered during quote processing (other field settings may indicate other types of restrictions which will also be applied). If no valid private fare for the account code exists, then no quote will be returned.
Blank = All fares for the flight segment may be considered in the quote process. A public fare may be used to cover this segment or a private fare may be used to cover this segment. There will be no restrictions applied by this field (although other field settings may indicate other types of restrictions which will be applied.)
How is null data specified?
Null data is specified by blanks.
What does null data indicate?
See Possible Values description.
|
|
|
|
+ <FICMod>
|
DP0A 1.0
|
|
|
|
<FIC>
|
Alphanumeric
|
8
|
Description of Field:
FIC code - mandatory
Format (a-alpha, n-numeric, x-alpha/numeric):
Axxxxxxxx
First character must be an alpha character
Special Format:
Left justified character blank filled.
Examples:
BXE147
Y
How is null data specified?
na
What does null data indicate?
e.g., No data results in error
|
|
|
|
+ <StopoverMod>
|
DP0B 1.0
|
|
|
|
+ <SegNumAry>
|
Array
|
n/a
|
|
|
<SegNum>
|
Numeric
|
3
|
Description of Field:
Segment number of the itinerary item to which this KLR relates
Format (a-alpha, n-numeric, x-alpha/numeric):
nnn
Special Format:
e.g., Left justified zero filled
Possible Values (List or Range):
001 - 999
How is null data specified?
NA
What does null data indicate?
No data results in error.
|
|
|
|
|
|
+ <NoBreakMod>
|
DP0C 1.0
|
|
|
|
+ <SegNumAry>
|
Array
|
n/a
|
|
|
<SegNum>
|
Numeric
|
3
|
Description of Field:
Segment number of the itinerary item to which this KLR relates
Format (a-alpha, n-numeric, x-alpha/numeric):
nnn
Special Format:
e.g., Left justified zero filled
Possible Values (List or Range):
001-999
How is null data specified?
NA
What does null data indicate?
No data results in error.
|
|
|
|
|
|
+ <ConxMod>
|
DP0D 1.0
|
|
|
|
+ <SegNumAry>
|
Array
|
n/a
|
|
|
<SegNum>
|
Numeric
|
3
|
Description of Field:
Segment number of the itinerary item to which this KLR relates
Format (a-alpha, n-numeric, x-alpha/numeric):
nnn
Special Format:
e.g., Left justified zero filled
Possible Values (List or Range):
001 - 999
How is null data specified?
NA
What does null data indicate?
No data results in error .
|
|
|
|
|
|
+ <OnlyBreakMod>
|
DP0E 1.0
|
|
|
|
+ <SegNumAry>
|
Array
|
n/a
|
|
|
<SegNum>
|
Numeric
|
3
|
Description of Field:
Segment number of the itinerary item to which this KLR relates
Format (a-alpha, n-numeric, x-alpha/numeric):
nnn
Special Format:
e.g., Left justified zero filled
Possible Values (List or Range):
001 - 999
How is null data specified?
NA
What does null data indicate?
No data results in error .
|
|
|
|
|
|
+ <BreakMod>
|
DP0F 1.0
|
|
|
|
+ <SegNumAry>
|
Array
|
n/a
|
|
|
<SegNum>
|
Numeric
|
3
|
Description of Field:
Segment number of the itinerary item to which this KLR relates
Format (a-alpha, n-numeric, x-alpha/numeric):
nnn
Special Format:
e.g., Left justified zero filled
Possible Values (List or Range):
001 - 999
How is null data specified?
NA
What does null data indicate?
No data results in error .
|
|
|
|
|
|
+ <PlatingAirVMod>
|
DP0H 1.0
|
|
|
|
<AirV>
|
Alphanumeric
|
3
|
Field Description:
Plating Carrier code
Format (c-character):
cc_ (Blank)
Special Format:
Left justified character blank filled.
How is null data specified?
N/A.
What does null data indicate?
No data results in error.
|
|
|
|
+ <TICMod>
|
DP0I 1.0
|
|
|
|
<TIC>
|
Alphanumeric
|
8
|
Description of Field:
TIC code-mandatory
Format (a-alpha, n-numeric, x-alpha/numeric):
xxxxxxxx
Special Format:
e.g., Left justified character blank filled.
Examples:
CSV25(blank) (blank) (blank)
e.g., Range
NA
How is null data specified?
NA
What does null data indicate?
No data results in error .
|
|
|
|
+ <CommissionMod>
|
DP10 2.0
|
|
|
|
<Amt>
|
Alphanumeric
|
12
|
Field Description:
Amount, including decimal places if required.
Format (x-alpha/numeric):
xxxxxxxxxxxx
Special Format:
Left justified, blank filled.
Examples:
10
10.00
How is null data specified?
N/A
What does null data indicate?
No data results in no error
|
|
<Percent>
|
Alphanumeric
|
5
|
Field Description:
Percentage, including decimal places if required. Can be entered with Capped Amount.
Format (x-alpha/numeric):
xxxxx
Special Format:
Left justified, blank filled.
Examples:
5
5.00
How is null data specified?
N/A
What does null data indicate?
No data results in no error
|
|
<CommCappedAmt>
|
Alphanumeric
|
12
|
Field Description:
Capped Amount (1G only). Can be entered with Commission Percentage
Format (x-alpha/numeric):
xxxxxxxxxxxx
Special Format:
Left justified, blank filled.
Examples:
10
10.00
How is null data specified?
N/A
What does null data indicate?
No data results in no error
|
|
|
|
+ <SoldTicketed>
|
DP20 1.0
|
|
|
|
<SaleLocn>
|
Alpha
|
1
|
Field Description:
Sale Location Indicator
Format (a-alpha):
a
Possible Values(List):
I - Inside
O - Outside
How is null data specified?
N/A
What does null data indicate?
No data results in error
|
|
<TkLocn>
|
Alpha
|
1
|
Field Description:
Ticketing Location Indicator
Format (a-alpha):
a
Possible Values(List):
I - Inside
O - Outside
How is null data specified?
N/A
What does null data indicate?
No data results in error
|
|
|
|
+ <TicketingCurrency>
|
DP21 1.0
|
|
|
|
<TkCurrency>
|
Alpha
|
1
|
Description of Field:
Currency for ticketing:
'L' - local, 'E' - Euros, 'U' - USD, 'C' - CAD
Format (a-alpha, n-numeric, x-alpha/numeric):
a
Special Format:
na
Examples:
U (United States Dollars)
e.g., Range
NA
How is null data specified?
NA
What does null data indicate?
No data results in error
|
|
|
|
+ <BaggageAllowance>
|
DP22 1.0
|
|
|
|
+ <SegNumAry>
|
Array
|
n/a
|
|
|
+ <SegNumInfo>
|
FieldSet
|
n/a
|
|
|
<SegNum>
|
Numeric
|
3
|
Field Description:
Segment number of the itinerary item to which this KLR relates (0 = no segment select)
Format (x-alpha/numeric):
nnn
Special Format:
Right justified, zero filled.
How is null data specified?
N/A
What does null data indicate?
No data results in error
|
|
<AllowCnt>
|
Numeric
|
3
|
Field Description:
Number or weight of bags
Up to 3 numerics, 1-999
Format (x-alpha/numeric):
nnn
Special Format:
Right justified, zero filled.
How is null data specified?
N/A
What does null data indicate?
No data results in error
|
|
<AllowInd>
|
Alpha
|
1
|
Field Description:
Allowance type:
'P' = pieces (count must be 1-99)
'K' = Kilos (count must be 1-99)
'L' = Pounds (count must be 1-99)
' ' = other (count must be 1-999)
Format (x-alpha/numeric):
a
Special Format:
na
How is null data specified?
N/A
What does null data indicate?
No data results in error
Processing notes
- Overrides the global fares allowance.
- Only 3 characters of baggage allowance will print on the ticket.
- Will print in the ALLOW box of each flight coupon.
- Modifier can be varied by segment
- Delimiter between segments is a colon (:), delimiter between segment number and segments data is a lozenge (@), delimiter between GBG and GTD is an end item (|).
- GBG and GTD undergo similar editing because they can be segment related but they are NOT related to each other in any way.
|
|
|
|
|
|
|
|
+ <TicketDesignator>
|
DP23 1.0
|
|
|
|
+ <SegNumAry>
|
Array
|
n/a
|
|
|
+ <SegNumInfo>
|
FieldSet
|
n/a
|
|
|
<SegNum>
|
Numeric
|
3
|
Description of Field:
Segment number of the itinerary item to which this KLR relates (0 = no segment select)
Format (x-alpha/numeric):
nnn
Special Format:
Right justified, zero filled.
How is null data specified?
N/A
What does null data indicate?
No data results in error
|
|
<TkDesignator>
|
Alphanumeric
|
15
|
Description of Field:
Ticket Designator
Format (x-alpha/numeric):
xxxxxxxxxxxxxxx
Special Format:
left justified, blank filled.
Example:
12345678aaasd(blank)(blank)
How is null data specified?
N/A
What does null data indicate?
No data results in error
Processing notes
- Will apply ticket designator to all segments. Will print only 6 characters
- Can be varied by segment
- Delimiter between segments is a colon (:), delimiter between segment number and segments data is a lozenge (@), delimiter between GBG and GTD is an end item (|).
- GBG and GTD undergo similar editing because they can be segment related but they are NOT related to each other in any way.
|
|
|
|
|
|
|
|
+ <TicketValidity>
|
DP24 1.0
|
|
|
|
<Ind>
|
Alpha
|
1
|
Description of Field:
Identify the date field as Not Valid After (NWA) or Not Valid Before (NWB).
Format (a-alpha):
a
Possible Values (List):
'B' - Not Valid Before (NWB)
'A' - Not Valid After (NWA)
How is null data specified?
N/A
What does null data indicate?
No data results in error
|
|
+ <SegNumAry>
|
Array
|
n/a
|
|
|
+ <SegNumInfo>
|
FieldSet
|
n/a
|
|
|
<SegNum>
|
Numeric
|
3
|
Description of Field:
Segment number of the itinerary item to which this KLR relates (0 = no segment select)
Format (n-numeric):
nnn
Special Format:
Right justified, zero filled.
How is null data specified?
N/A
What does null data indicate?
No data results in error
|
|
<NVBDt>
|
Alphanumeric
|
5
|
Description of Field:
Date in DDMMM format
Format (x-alpha/numeric):
xxxxx
Special Format:
DDMMM
Example:
03JUN
How is null data specified?
N/A
What does null data indicate?
No data results in error
Processing Notes:
- May be used independently or together
- Will default to the entire itinerary with other modifiers
- May be used in conjunction with the ATFQ, Pricing Record or ticketing entry
- May be deleted or modified from the ATFQ line
- NVB/NVA dates will not be compared against one another.
- NVB/NVA dates will use the same date routine as the Pricing Record.
- No date analysis will be made against the itinerary.
- Dates entered with these modifiers will override those dates supplied by GlobalFares on outputs only.(The Linear Fare Data (*LF) section of the PNR created by Fare Quote will reflect true GlobalFares data).
- When the NVB/NVA modifiers are used as part of the Pricing Record build entry, the data will become unchangeable within the Pricing Record Fill-in screen ($NME).
- Modifier input hierarchy will remain the same (the HB entry will override the ATFQ, the ATFQ will override the PNR field).
- Pricing/Fare Construction Indicator (FCI): If the system is going to output a pricing code of "0", it will check to see if an NVA/NVB modifier is used; if so, the system will change the pricing code to "5" for agency issued tickets and "2" for United Airlines issued tickets
- OPTAT/TAT: When the NVB/NVA modifiers are used, dates will print in the current fields/boxes.
- ATB: When the NVB/NVA modifiers are used, dates will print in the current NVB/NVA fields/boxes on the flight coupon and the Post Audit document.
- MIR: These modifiers will output in current MIR 2 Labels.
NVB - Fare Basis Section, Label A08NVBC, 7 bytes alphanumeric (DDMMMYY)
NVA - Fare Basis Section, Label A08NVAC, 7 bytes alphanumeric (DDMMMYY)
The Pricing/Fare Construction Indicator is part of the Transaction Number in Passenger Data Section, Label A02TRN
|
|
|
|
|
|
|
|
+ <PrintRLoc>
|
DP25 1.0
|
|
|
|
<RLoc>
|
Alphanumeric
|
6
|
Field Description:
Record locator
Format (x-alpha/numeric):
xxxxxx
Special Format:
Examples:
TP1CDI
How is null data specified?
N/A
What does null data indicate?
No data results in error
|
|
<Vnd>
|
Alphanumeric
|
3
|
Field Description:
Airline/GDS code
Format (x-alpha/numeric):
xxx
Special Format:
Left justified, blank filled
Examples:
1V(blank)
How is null data specified?
N/A
What does null data indicate?
No data results in error
Processing Notes:
- When issuing tickets, the agent can be able to override the Apollo record locator with the record locator and airline code of a PNR originally booked directly in another airline reservation system.
- MIR 62 and 67 will contain the Apollo record locator. MIR 92 contains both.
|
|
|
|
+ <PsgrReceiptOverride>
|
DP26 1.0
|
|
|
|
<Gtid>
|
Alphanumeric
|
6
|
Field Description:
LNIATA/GTID
Format (x-alpha/numeric):
xxxxxx
Special Format:
N/A
Examples:
CDCE1E
CCD0E5
How is null data specified?
Null data is specified by blanks.
What does null data indicate?
Null data results in no error.
|
|
|
|
+ <EndorsementBox>
|
DP27 1.0
|
|
|
|
<Endors1>
|
Alphanumeric
|
29
|
Description of Field:
First endorsement box, free form text
Format (x-alpha/numeric):
xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Special Format:
Left justified, blank filled
Words can be separated by an @ on 1V and a blank on 1G
Examples:
NON@REFUNDABLE
How is null data specified?
N/A
What does null data indicate?
No data results in error
|
|
<Endors2>
|
Alphanumeric
|
29
|
Description of Field:
Second endorsement box, free form text
Format (x-alpha/numeric):
xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Special Format:
Left justified, blank filled
Words can be separated by an @ on 1V and a blank on 1G
Examples:
NON@REFUNDABLE
How is null data specified?
N/A
What does null data indicate?
No data results in error
|
|
<Endors3>
|
Alphanumeric
|
29
|
Description of Field:
Third endorsement box, free form text
Format (x-alpha/numeric):
xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Special Format:
Left justified, blank filled
Words can be separated by an @ on 1V and a blank on 1G
Examples:
NON@REFUNDABLE
How is null data specified?
N/A
What does null data indicate?
No data results in error
|
|
|
|
+ <BulkTicket>
|
DP28 1.0
|
|
|
|
<FareConstructInd>
|
Alpha
|
1
|
Field Description:
1G only
'P' - Print fare construction (equivalent of BT*PC entry)
'S' - Suppress Fare construction
(Blank for 1V system)
Format (x-alpha/numeric, a-alpha):
a
Special Format:
How is null data specified?
N/A
What does null data indicate?
No data results in error.
|
|
|
|
<NonRefundBulkTicket>
|
DP29 1.0
|
|
+ <FreeFormTicket>
|
DP30 1.0
|
|
|
|
<Text>
|
Alphanumeric
|
To End
|
Freeform up to 17 characters. Alpha , numeric and special characters allowed.
Special characters are *-@#
Will print in the FOP area of OPTAT tickets. If used with a CC FOP, part of the CC information will be truncated to make room for all of the GFP data.
A pillow (@) will appear as a blank space.
An asterisk (*) will appear as a slash(/).
A hyphen/dash character will print as entered (-).
On OPTAT tickets only the last 14 characters will print.
Not Valid with ATB Ticketing.
When a credit is used as form of payment, the vendor/card number will print as today; however, the expiration date (if entered) and the extended payment indicator (if entered) will be suppressed from printing when modifier is used.
When a credit card is used as form of payment and a manually obtained APPROVAL code is entered (#*123456), the letter "M" in front of the approval will be suppressed from printing when all 17 characters of the new modifier are used. If 16 or fewer characters are entered, the "M" will print as it does today.
|
|
|
|
+ <GroupTour>
|
DP31 1.0
|
|
|
|
<FareConstructInd>
|
Alpha
|
1
|
Field Description:
For 1G system:
- 'P' - Print fare construction (equivalent of IT*PC entry)
- 'S' - Suppress Fare construction
Blank for 1V system
Format (x-alpha/numeric):
For 1G - x
Blank for 1V
Special Format:
None
Examples:
P
How is null data specified?
N/A
What does null data indicate?
On 1V there is no data.
|
|
|
|
+ <TourCode>
|
DP33 1.0
|
|
|
|
<Rules>
|
Alphanumeric
|
To End
|
Field Description:
1V rules: 1-15 characters, which will print on the ticket.
1G rules: 1-14 characters (except Saudi TAT which allows 1-10)
Format (x-alpha/numeric):
xxxxxxxxxxxxxx - 1G
xxxxxxxxxxxxxxx - 1V
Special Format:
Left Justified. Blank filled.
1V:
Special character pillow (@) appears as blank space.
An asterisk(*) will appear as a slash
A hyphen (-) is allowed and is unchanged
Examples:
E12SIN4
SHELL23CX
How is null data specified?
N/A
What does null data indicate?
No data results in error.
|
|
|
|
+ <NetRemitOverride>
|
DP34 1.0
|
|
|
|
<Amt>
|
Alphanumeric
|
8
|
Field Description:
Dollar Amount
Format (x-alpha/numeric):
xxxxxxxx
Special Format:
8 characters - can currently enter 3 decimal places. Right justified, zero filled.
Examples:
100.00
100
How is null data specified?
N/A
What does null data indicate?
Null data results in error.
|
|
|
|
+ <DocumentSelect>
|
DP42 2.0
|
|
|
|
<TkOnlyInd>
|
Alpha
|
1
|
Description of Field:
Specifies Ticket Only option
Format (a-alpha)
a
Examples:
Set to 'Y' if user wishes to alter the system default of producing a ticket, itin and MIR. Setting this will inhibit itin and MIR, unless these have also been specifically requested (Terminal Equivalent: DTD)
|
|
<ETInd>
|
Alpha
|
1
|
Description of Field:
Specifies Electronic Ticket Only option
Format (a-alpha)
A
Examples:
Set to 'Y' if an Electronic Ticket is required (Terminal Equivalent: DLD, ET)
Set to 'P' if Paper Ticket is required (Terminal Equivalent: PT)
How is null data specified?
Character blanks
What does null data indicate?
Leave blank for system to determine type
|
|
<CouponCnt>
|
Alphanumeric
|
1
|
Description of Field:
Specifies the number of ATB (Automated Ticket and Boarding passes) Post-Audit Coupons ticket option
Format (a-alpha)
A
Special Format:
Setting this field to zero will generate 'GA0'.
Use a blank if you do not want this modifier generated
NOTE: If this field is set, then the next optional field (host/satellite) can also be set.
Examples:
2
Number of coupons (system defaults to 1) (max = 3)
(Terminal Equivalent: GA - 1V only)
How is null data specified?
Character blanks
What does null data indicate?
Leave blank for system default.
|
|
<DestInd>
|
Alpha
|
1
|
Description of Field:
Specifies an ATB Post-Audit Destination ticket option
Format (a-alpha)
A
Example:
Destination for coupons:
'H' - Home
'S' - Satellite
(optional - related to number of Post Audit Coupons)
|
|
<ForceInd>
|
Alpha
|
1
|
Description of Field:
Specifies a Force Audit Coupon ticket option
Format (a-alpha)
A
Example:
Set to 'A' to print an ATB Audit Coupon and override normal BSP setting. (Terminal Equivalent: 1G only - AU modifier)
|
|
<MIRInd>
|
Alpha
|
1
|
Description of Field:
Specifies Machine Interface Record (MIR) Only ticket option
Format (a-alpha)
A
Examples:
Six valid settings:
'A' - Accounting MIR (Terminal Equivalent: DBD - 1V only)
'N' - Non-Accounting MIR (Terminal Equivalent: DAD)
'R' - Non-Accounting Remote MIR (requires GTID/CRS and PCC to be populated: see below) (Terminal Equivalent: DND)
'F' - Non-Faring Remote MIR (requires GTID/CRS and PCC to be populated: see below) (Terminal Equivalent: DJD - 1V only)
'X' - Dual MIR. Issues a ticket, itinerary, a two ticketing MIRs - to the MIR device to which the CRT is physically linked, and a copy of that MIR to the MIR device specified in the following fields (DXD)
Special Format:
If one of these options is set (except for 'X'), the system default of producing a ticket, itin and MIR will be overridden. Setting this will inhibit ticket and itin, unless these have also been specifically requested.
|
|
<Locn>
|
Alphanumeric
|
6
|
Description of Field:
Specifies the Location for data from the MIR only option field.
Format (a-alpha)
A
Special Format:
Required if option 'R', 'G', 'F', or 'X' is selected in MIR Only field. Populated with either the destination GTID (LNIATA - Line Number Interchange Address Terminal Address) for MIRs within the same system, or CRS name (1G or 1V) for MIRs to another system.
|
|
<PCC>
|
Alphanumeric
|
4
|
Description of Field:
Pseudo City Code.
Format (x-alpha/numeric:
XXXX
Special Format:
Left Justified Blank Filled
PCCs with less than 4 characters should be padded with a leading zero. For example, X0B should be submitted as 0X0B.
CDATA can also be used to override the attributes of this field. For example,
![CDATA[ X0B]] In this case the field is forced to right justify with a leading blank.
Examples:
1WP7
0X0B
![CDATA[ X0B]]
![CDATA[2GK5]]
How is null data specified?
Character blanks
What does null data indicate?
No user data was input.
|
|
<ItinInd>
|
Alpha
|
1
|
Description of Field:
Specifies the Itinerary or Invoice type option for the ticket.
Format (a-alpha)
a
Examples:
'I' - normal itin/invoice (Terminal Equivalent: DID)
'P' - Pocket itin (ticketing only) (Terminal Equivalent: DPD - 1V only)
|
|
<FaxInd>
|
Alpha
|
1
|
Description of Field:
Specifies the Itinerary or Invoice fax type option for the ticket.
Format (a-alpha)
a
Examples:
'X' - FAX - Can store the Fax modifier (Terminal Equivalent: GFX) or can use with ticketing.
'D' - Itin FAX - can't be stored, can use with ticketing only (Terminal Equivalent: DFX).
(Terminal Equivalent: 1V only - DFX/GFX)
|
|
<ItinOptInd>
|
Alpha
|
1
|
Description of Field:
Specifies the Itinerary or Invoice type options for the ticket.
Format (a-alpha)
a
Examples:
'F' - itin with no fare information (Terminal Equivalent: GIF/DCD)
'A' - itin with no amounts (Terminal Equivalent: GIN, IN)
'D' - itin, but do not decrement invoice numbers (Terminal Equivalent: GID 1V only)
|
|
<SepInd>
|
Alpha
|
1
|
Description of Field:
Specifies whether there are separate itineraries.
Format (a-alpha)
a
Examples:
Y
N
Note:
If set to 'Y', one itinerary will be printed per passenger (Terminal Equivalent: GIS/ IS)
|
|
<PocketItinCnt>
|
Alphanumeric
|
1
|
Description of Field:
Number of pocket itineraries for ATB (Terminal Equivalent: GP - 1V only).
A pocket itinerary is an option to print a passenger itinerary together with associated information on pocket itinerary stock. The data printed is identical to full length documents.
Format (a-alpha)
a
Special Format:
Setting this field to zero will generate 'GP0', use a blank if you do not want this modifier generated
If this field is set, then the next optional field (host/satellite) can also be set.
How is null data specified?
Character blanks
What does null data indicate?
System default.
|
|
<PocketItinsDestInd>
|
Alpha
|
1
|
Description of Field:
Destination for Pocket Itineraries
Format (a-alpha)
A
Special Format:
(optional - related to number of Pocket Itineraries)
Examples:
'H' - Home
'S' - Satellite
|
|
<DeliveryDocsInd>
|
Alpha
|
1
|
Description of Field:
Specifies the Delivery Documents
Format (a-alpha)
A
Example:
'D' - select delivery documents (Terminal Equivalent: DDD - 1V only)
NOTE: Not valid with any D modifier except DPD, GA, GB, GBN, GFX, GT, GF, GFP, GID, GUSD, GCAD, GIN, GIS
PROCESSING NOTES:
ATB only.
Open to buy not down dated.
The printer 'firmware' (pectab) must be one of the following:
2200 - version 08
2800 - version 05, 07, 08
An error response will be displayed if the agency is using a 2200 printer with firmware versions 04 or 07
Requires Delivery (D-) field in PNR.
FOP is not required on the DDD modifier
Does not go to fare quote.
|
|
|
|
<ItinRmksSuppression>
|
DP44 1.0
|
|
+ <WaitlistSegSelect>
|
DP45 1.0
|
|
|
|
+ <SegNumAry>
|
Array
|
n/a
|
|
|
<SegNum>
|
Numeric
|
3
|
Field Description:
Segment number of the itinerary item to which this KLR relates.
Format (n-numeric):
nnn
Special Format:
Right justified, zero filled.
Examples:
000
001
002
How is null data specified?
N/A
What does null data indicate?
No data results in error.
|
|
|
|
|
|
+ <AuxSegSelect>
|
DP46 1.0
|
|
|
|
+ <SegNumAry>
|
Array
|
n/a
|
|
|
<SegNum>
|
Alphanumeric
|
3
|
Field Description:
Segment number of the itinerary item to which this KLR relates.
Format (x-alpha/numeric):
xxx
Special Format:
Right justified, blank filled.
Examples:
ALL
003
How is null data specified?
N/A
What does null data indicate?
N/A
|
|
|
|
|
|
<NonNegotiableCharge>
|
DP53 1.0
|
|
<PrintTableOverride>
|
DP54 1.0
|
|
+ <Commission>
|
DPCM 1.0
|
|
|
|
<UniqueKey>
|
Alphanumeric
|
4
|
Description of Field:
Unique Key, used in correspondence with other KLRs such as GFSR, to tie information together. Passenger Description Number starting from '0001'
Format (x-alpha/numeric):
xxxx
Left justified, blank filled
Value should be 4 digits, and should include leading zeros.
Examples:
"0003"
How is null data specified?
N/A
What does null data indicate?
No data results in error
|
|
<Amt>
|
Character
|
12
|
Description of Field:
Commission Amount, similar to DP10 KLR. Should contain decimal point.
Format (c-character):
cccccccccccc
left justified blank filled
Examples:
"12.00 "
How is null data specified?
Blanks
What does null data indicate?
When null (blanks) then this field is not applicable
|
|
<Percent>
|
Character
|
5
|
Description of Field:
Commission Percentage, similar to DP10 KLR. Should contain decimal point.
Format (c-character):
ccccc
left justified blank filled
Examples:
"3.00 "
How is null data specified?
Blanks
What does null data indicate?
When null (blanks) then this field is not applicable
|
|
|
|
+ <FareNumInfo>
|
DPFI 1.0
|
|
|
|
+ <FareNumAry>
|
Array
|
n/a
|
|
|
<FareNum>
|
Numeric
|
3
|
Field Description:
Fare number of the item to which the following KLRs relate.
Format (n-numeric):
nnn
Special Format:
Right justified, zero filled.
Examples:
001
How is null data specified?
N/A
What does null data indicate?
No data results in error.
|
|
|
|
|
|
+ <DocProdFareType>
|
DPFT 1.0
|
|
|
|
<Type>
|
Alphanumeric
|
1
|
Fare Type:
Identifies the type of fare to be processed.
Possible Values:
I = All available fares.
N = Public fares only.
P = Private fares only (all types).
C = NET fares only.
A = Airline Private Fares only.
G = Agency Private Fares only.
What does null data indicate?
A blank will result in an error. Data in this field is mandatory when using this KLR.
|
|
|
|
+ <AssocSegs>
|
DPII 1.0
|
|
|
|
+ <SegNumAry>
|
Array
|
n/a
|
|
|
<SegNum>
|
Numeric
|
3
|
Field Description:
Segment Number
Format (n-numeric):
nnn
Possible Values (Range):
001-099
Special Format:
Right justified, zero filled.
Examples:
001
055
How is null data specified?
N/A
What does null data indicate?
No data results in error.
|
|
|
|
|
|
+ <SegmentData>
|
DPOP 1.0
|
|
|
|
<RelSegNum>
|
Numeric
|
2
|
Description of Field:
Relative Itinerary Segment number.
Format (n-numeric):
nn
Special Format:
Right justified zero filled
Possible Values(Range):
00 - 99
How is null data specified?
Zeros
What does null data indicate?
When null - zeros, then this field is not applicable
|
|
<FltNum>
|
Alphanumeric
|
4
|
Description of Field:
Flight Number.
Format (x-alpha/numeric):
xxxx
Special Format:
left justified, blank filled
If flight is open, then OPEN is passed instead of a flight number.
Possible Values (Range):
1 - 9999
OPEN
How is null data specified?
Blanks
What does null data indicate?
When null - blanks, then this field is not applicable
|
|
<BIC>
|
Alpha
|
2
|
Description of Field:
Class of Service. The value of this field should correspond to the class of service used in the itinerary segment.
Format (a-alpha):
aa
Special Format:
left justified blank filled
Example:
Y
How is null data specified?
Blanks
What does null data indicate?
When null -blanks, then this field is not applicable
|
|
<StartDt>
|
Numeric
|
8
|
Description of Field:
Day on which segment departs.
Format(n-numeric):
nnnnnnnn
Special Format::
YYYYMMDD
How is null data specified?
Zeros
What does null data indicate?
When null - zeros, then this field is not applicable
|
|
<TmTrav>
|
Numeric
|
4
|
Description of Field:
Time of Travel.
Format (n-numeric):
nnnn
Special Format:
24 hour format GMT - HHMM,
right justified zero filled
Possible Values (Range):
0001-2400
How is null data specified?
Zeros -Note: when 0000 is a legitimate value, it should be sent as 2400.
What does null data indicate?
When null - zeros, then this field is not applicable
|
|
<SegStatus>
|
Alpha
|
2
|
Description of Field:
Segment Status.
Format (a-alpha):
aa
Special Format:
Left justified blank filled
Possible Values (List):
OK = Confirmed
RQ = Requested
SA = Space Available
How is null data specified?
Blanks
What does null data indicate?
When null - blanks, then this field is not applicable
|
|
|
|
+ <CreditCardFOP>
|
DPP0 1.0
|
|
|
|
<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
|
|
<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
|
|
<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
|
|
<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
|
|
<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
|
|
<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
|
|
<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
|
|
<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)
8 - OB Fee Charged
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
8 - Ob Fee charged
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 2.0
|
|
|
|
<FOPID>
|
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
16 - Special Government Transportation Request
17 - Multiple Receivable
18 - Certificate (CERT for UA)
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.
|
|
<PmtCrncy>
|
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
|
|
+ <AddlDataIDAry>
|
Array
|
n/a
|
|
|
+ <AddlDataID>
|
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
6 - Certificate number
8 - OB Fee Charged
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
|
|
|
|
|
|
|
|
+ <AssocPsgrs>
|
DPPI 1.0
|
|
|
|
+ <PsgrAry>
|
Array
|
n/a
|
|
|
+ <Psgr>
|
FieldSet
|
n/a
|
|
|
<LNameNum>
|
Numeric
|
2
|
Field Description:
Unique, sequential number identifying the last name grouping
Format (n- numeric):
nn
Special Format:
Right justified, padded with zero, one or two characters. If no data, then blank filled.
Examples:
01
02
How is null data specified?
Null data specified by blanks.
What does null data indicate?
No data results in error.
|
|
<PsgrNum>
|
Numeric
|
2
|
Field Description:
Sequential number identifying a passenger within a last name grouping.
Format (n- numeric):
nn
Special Format:
Right justified, padded with zero, one or two characters. If no data, then blank filled.
Examples:
01
02
How is null data specified?
Null data specified by blanks.
What does null data indicate?
No data results in error.
|
|
<AbsNameNum>
|
Numeric
|
2
|
Field Description:
Unique, sequential number identifying each passenger irrespective of last name
Format (n- numeric):
nn
Special Format:
Right justified, padded with zero, one or two characters. If no data, then blank filled.
Examples:
01
blank blank
How is null data specified?
Null data specified by blanks
What does null data indicate?
It's a valid scenario. Null data doesn't result in error
|
|
|
|
|
|
|
|
+ <RateOfExchangeMod>
|
DPRO 1.0
|
|
|
|
<UniqueKey>
|
Alphanumeric
|
4
|
Field Description:
Unique Key, used in correspondence with other KLRs such as GFSR, to tie information together. Passenger Description Number starting from '0001'
Format (x-alpha/numeric):
xxxx
Left justified, blank filled
Value should be 4 digits, and should include leading zeros.
Special Format:
N/A
Examples:
"0001"
How is null data specified?
N/A
What does null data indicate?
No data results in error
|
|
<ROE>
|
Character
|
12
|
Description of Field:
Rate of Exchange - ROE
Format (c-character):
cccccccccccc
left justified blank filled
Examples:
"12.00 "
"12 "
How is null data specified?
Blanks
What does null data indicate?
When null (blanks) then this field is not applicable
|
|
|
|
+ <ItineraryCity>
|
DPUC 1.0
|
|
|
|
+ <ItinCityAry>
|
Array
|
n/a
|
|
|
+ <ItinCityInfo>
|
FieldSet
|
n/a
|
|
|
<CityCode>
|
Alpha
|
5
|
Description of Field:
City Code
Format (a-alpha):
aaaaa
Left justified, blank padded
Examples:
'VVV '
How is null data specified?
Blanks
What does null data indicate?
No data results in error.
|
|
<CityName>
|
Alphanumeric
|
17
|
Description of Field:
Name for City for given City Code
Format (x-alphanumberic):
xxxxxxxxxxxxxxxxx
Left justified, blank padded
Examples:
'PODUNC '
How is null data specified?
Blanks
What does null data indicate?
No data indicates this field is N/A.
|
|
|
|
|
|
|
|
+ <CityCodeMod>
|
DPUR 1.0
|
|
|
|
+ <CityCodeAry>
|
Array
|
n/a
|
|
|
<CityCode>
|
Alpha
|
5
|
Description of Field:
City Code
Format (a-alpha):
aaaaa
Left justified, blank padded
Examples:
'ORD '
How is null data specified?
Blanks
What does null data indicate?
No data results in error.
|
|
|
|
|
|
+ <FareConstruction>
|
GFFC 1.0
|
|
|
|
<UniqueKey>
|
Alphanumeric
|
4
|
Field Description:
Passenger Description Number starting from 0001
Format (x-alpha/numeric):
xxxx
Special Format:
Right justified, zero filled.
Examples:
0001
How is null data specified?
N/A
What does null data indicate?
No data results in error.
|
|
<QuoteNum>
|
Numeric
|
2
|
Field Description:
Quote number (GRFQNB)
Format (n-numeric):
nn
Special Format:
Right justified, zero filled.
Zero, if does not exist.
Examples:
01
How is null data specified?
Null data is specified by Zero.
What does null data indicate?
No data results in error
|
|
<FareConstructText>
|
Alphanumeric
|
To End
|
Field Description:
Format (x-alpha/numeric):
xxxxxxxxxxxxx...
Special Format:
N/A
Examples:
DEN UA CHI Q9.30 1078.14FUA2SFS USD 1087.44
DEN US CHI Q9.30 194.42VHE14NR UA DEN Q9.30 115.35TE21QN USD 328.37 END
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.
Depends upon the Fare construction response.
|
|
|
|
+ <GenQuoteDetails>
|
GFGQ 3.0
|
|
|
|
<UniqueKey>
|
Numeric
|
4
|
Field Description:
Passenger Description Number starting from 0001
Format (n-numeric):
nnnn
Possible Values (Range):
0001 - 9999
How is null data specified?
N/A
What does null data indicate?
No data results in error
|
|
<QuoteNum>
|
Numeric
|
2
|
Field Description:
Quote Number(GRGQNB)
Format (n-numeric):
nn
How is null data specified?
N/A
What does null data indicate?
No data results in error
|
|
<QuoteType>
|
Alpha
|
1
|
Field Description:
Quote Type: Identifies the type of quote being processed.
Format (a-alpha):
a
Possible Values (List):
G = Computer generated, and guaranteed
C = Computer generated, not guaranteed
B = Manual on Galileo
M = Manual on Apollo
How is null data specified?
Character blank
What does null data indicate?
Quote type does not exist
|
|
<LastTkDt>
|
Numeric
|
8
|
Field Description:
Last date to ticket
Format (n-numeric):
nnnnnnnn
Special Format:
YYYYMMDD
Zero if does not exist
Examples:
20030725
How is null data specified?
0
What does null data indicate?
Zero specifies null data.
|
|
<QuoteDt>
|
Numeric
|
8
|
Field Description:
Date of quote
Format (n-numeric):
nnnnnnnn
Special Format:
YYYYMMDD
Zero if does not exist
Examples:
20030519
How is null data specified?
0
What does null data indicate?
Zero specifies null data
|
|
<IntlSaleInd>
|
Alphanumeric
|
4
|
Field Description:
International sale indicator -
Obsolete - always blanks
|
|
<BaseFareCurrency>
|
Alpha
|
3
|
Field Description:
Currency code in which the Base Fare Amount is specified
Format (a-alpha):
aaa
Examples:
USD
EUR
How is null data specified?
N/A
What does null data indicate?
N/A
|
|
<BaseFareAmt>
|
Numeric
|
11
|
Field Description:
Base fare amount. This is the total of all fares and any applicable plus ups and surcharges, but not inclusive of ticketable taxes.
Format (n-numeric):
nnnnnnnnnnn
The amount is right aligned and zero-filled and without a decimal point. The position of the decimal point is determined by the Number of Decimal Places field below
Examples:
00000217488. (if the number of decimal places were 2, this would represent 2174.88)
How is null data specified?
0
What does null data indicate?
Zero specifies null data.
|
|
<LowestOrNUCFare>
|
Numeric
|
11
|
Field Description:
If the query was a Best Buy Compare, this field will contain the price the itinerary will be if the itinerary is left "as booked".
Else this field will be null
Format (n-numeric):
nnnnnnnnnnn
The amount is right aligned and zero-filled and without a decimal point. The position of the decimal point is determined by the Number of Total Decimal Places field below
Examples:
00000000000
How is null data specified?
0
What does null data indicate?
Zero specifies null data.
|
|
<BaseDecPos>
|
Numeric
|
1
|
Field Description:
Number of decimal places for the Base Fare Currency Code
Format (n-numeric):
n
Special Format:
Zero if does not exist
Possible Values (Range):
0 - 3
How is null data specified?
0
What does null data indicate?
Zero specifies null data
|
|
<EquivCurrency>
|
Alphanumeric
|
3
|
Field Description:
Currency code in which the Equivalent Amount is specified
Format (x-alpha/numeric):
xxx
Special Format:
Blank if does not exist
Examples:
GBP
How is null data specified?
N/A
What does null data indicate?
No data results in error
|
|
<EquivAmt>
|
Numeric
|
11
|
Field Description:
The base fare amount converted to the currency of the country of payment, if different from the currency of the Base Fare.
For example, if the base fare amount is 100.00 EUR, then the EquivAmt (in a US travel agency) would be 141.00 USD.
Format (n-numeric):
nnnnnnnnnnn
The amount is right aligned and zero-filled and without a decimal point. The position of the decimal point is determined by the Number of Decimal Places field below
Examples:
000001393002
How is null data specified?
0
What does null data indicate?
Zero specifies null data
|
|
<EquivDecPos>
|
Numeric
|
1
|
Field Description:
Number of decimal places for equivalent fare
Format (n-numeric):
n
Possible Values (Range):
0 - 3
How is null data specified?
0
What does null data indicate?
Zero specifies null data.
|
|
<TotCurrency>
|
Alphanumeric
|
3
|
Field Description:
Currency code of the Total Amount
Format (x-alpha/numeric):
xxx
Special Format:
Blank if does not exist
Examples:
USD
How is null data specified?
N/A
What does null data indicate?
No data results in error
|
|
<TotAmt>
|
Numeric
|
11
|
Field Description:
Base fare plus taxes
Format (n-numeric):
nnnnnnnnnnn
The amount is right aligned and zero-filled and without a decimal point. The position of the decimal point is determined by the Total Decimal Places field below
Example:
00000235800
How is null data specified?
Zeroes
What does null data indicate?
Zero if does not exist
|
|
<TotDecPos>
|
Numeric
|
1
|
Field Description:
Number of decimal places for total fare
Format (n-numeric):
N
Possible Values (Range):
0 - 3
How is null data specified?
0
What does null data indicate?
Zero if no decimal needed
|
|
<ITNum>
|
Alphanumeric
|
15
|
Field Description:
Tour Code (from Category 28)
Format (x-alpha/numeric):
xxxxxxxxxxxxxxx
How is null data specified?
Blanks
What does null data indicate?
Blank if does not exist
|
|
<RteBasedQuote>
|
Alpha
|
1
|
Field Description:
Indicator identifies whether or not the quote is route based.
Note: to determine route- or mileage-based status for international journeys, the indicators in the GERI should be used, since a quote may contain both route- and mileage-based fares.
Obsolete - always 'Y'
|
|
<M0>
|
Alpha
|
1
|
Field Description:
Indicates the quote is mileage based with no mileage surcharge applied
Note: to determine route- or mileage-based status for international journeys, the indicators in the GERI should be used, since a quote may contain both route- and mileage-based fares.
Obsolete - always 'N'
|
|
<M5>
|
Alpha
|
1
|
Field Description:
Indicates the quote is mileage based with a 5M mileage surcharge applied
Note: to determine route- or mileage-based status for international journeys, the indicators in the GERI should be used, since a quote may contain both route- and mileage-based fares.
Obsolete - always 'N'
|
|
<M10>
|
Alpha
|
1
|
Field Description:
Indicates the quote is mileage based with a 10M mileage surcharge applied
Note: to determine route- or mileage-based status for international journeys, the indicators in the GERI should be used, since a quote may contain both route- and mileage-based fares.
Obsolete - always 'N'
|
|
<M15>
|
Alpha
|
1
|
Field Description:
Indicates the quote is mileage based with a 15M mileage surcharge applied
Note: to determine route- or mileage-based status for international journeys, the indicators in the GERI should be used, since a quote may contain both route- and mileage-based fares.
Obsolete - always 'N'
|
|
<M20>
|
Alpha
|
1
|
Field Description:
Indicates the quote is mileage based with a 20M mileage surcharge applied
Note: to determine route- or mileage-based status for international journeys, the indicators in the GERI should be used, since a quote may contain both route- and mileage-based fares.
Obsolete - always 'N'
|
|
<M25>
|
Alpha
|
1
|
Field Description:
Indicates the quote is mileage based with a 25M mileage surcharge applied
Note: to determine route- or mileage-based status for international journeys, the indicators in the GERI should be used, since a quote may contain both route- and mileage-based fares.
Obsolete - always 'N'
|
|
<Spare1>
|
Alpha
|
1
|
Field Description:
Spares. Default 'N'
|
|
<PrivFQd>
|
Alpha
|
1
|
Field Description:
Private fare quoted for one or more segments
Format (a-alpha):
a
Possible Values (List):
Y - Private fare quoted for one or more segments
N
How is null data specified?
N/A
What does null data indicate?
No private fares quoted
|
|
<PFOverrides>
|
Alpha
|
1
|
Field Description:
Private fares overrides/waivers apply
Format (a-alpha):
a
Possible Values (List):
Y - Private fares overrides/waivers apply
N
How is null data specified?
N/A
What does null data indicate?
No Private fares overrides/waivers apply
|
|
<FlatFQd>
|
Alpha
|
1
|
Field Description:
Flat Fare quoted for one or more segments
Format (a-alpha):
a
Possible Values (List):
Y - Flat Fare quoted for one or more segments
N -
How is null data specified?
N/A
What does null data indicate?
No Flat Fare quoted
|
|
<DirMinApplied>
|
Alpha
|
1
|
Field Description:
Directional minimum applied
Format (a-alpha):
a
Possible Values (List):
Y- directional minimum applied
N - directional minimum not applied
How is null data specified?
N/A
What does null data indicate?
directional minimum not applied
|
|
<VATIncInd>
|
Alpha
|
1
|
Field Description:
VAT included in quote
Format (a-alpha):
a
Possible Values (List):
Y - VAT included in quote
N - VAT not included in quote
How is null data specified?
N/A
What does null data indicate?
VAT not included in quote
|
|
<PenApplies>
|
Alpha
|
1
|
Field Description:
Penalty applies
Format (a-alpha):
a
Possible Values (List):
Y - Penalty applies
N - Penalty does not apply
How is null data specified?
N/A
What does null data indicate?
Penalty does not apply
|
|
<Spare2>
|
Alpha
|
1
|
Field Description:
Spare: default value 'N'
|
|
<QuoteBasis>
|
Alpha
|
1
|
Field Description:
For use when a Passenger Type Code has been specified in the query, e.g. in the GQNP query KLR, this field indicates whether the quote returned applies specifically to the query PTC, or whether a default quote (Adult fare) has been returned (does not apply if the GQPO was used in the query)
Format (a-alpha):
a
Possible Values (List):
Y = this is a default Adult quote
N = this is a quote for the specific PTC (or a PTC code was not specified in the query)
How is null data specified?
N/A
What does null data indicate?
same as N
|
TaxDataCnt
Structured data only.
Not in XML.
|
Numeric
|
2
|
Field Description:
Number of tax fields that follow
Format (n-numeric):
nn
Special Format:
Zero if does not exist
Examples:
04
How is null data specified?
0
What does null data indicate?
Zero specifies no tax data follows
|
|
+ <TaxDataAry>
|
Array
|
n/a
|
|
|
+ <TaxData>
|
FieldSet
|
n/a
|
|
|
<Country>
|
Alphanumeric
|
2
|
Field Description:
Tax country code
Format (x-alpha/numeric):
xx
Examples:
US
XF
How is null data specified?
N/A
What does null data indicate?
No data results in error
|
|
<Amt>
|
Alphanumeric
|
8
|
Field Description:
Tax amount (in the currency of the equivalent amount, or base amount if no equivalent amount exists or 'exempt' if tax code exempted)
Format (x-alpha/numeric):
xxxxxxxx
Special Format:
Amount can include decimal point
Text 'exempt '
Examples:
00163.12
00009.00
'exempt '
How is null data specified?
N/A
What does null data indicate?
No data results in error
|
|
|
|
|
|
|
|
+ <InfoMsg>
|
GFMM 1.0
|
|
|
|
<UniqueKey>
|
Alphanumeric
|
4
|
Field Description
Passenger Description Number (Fare Quote entries).
If not 0000 - Message is specific to that passenger type/
If 0000 - Message applies to all passenger types/entire entry.
Format (x-alpha/numeric):
xxxx
Special Format:
Right justified, zero filled.
Examples:
0000
0001
How is null data specified?
Null data is specified by zero.
What does null data indicate?
If 0000 - Message applies to all passenger types/entire entry.
|
|
<QuoteNum>
|
Numeric
|
2
|
Field Description:
Quote number. (GRMQNB)
Format (n-numeric):
nn
Special Format:
Right justified, zero filled.
Zero, if does not exist
Examples:
00
01
How is null data specified?
Null data is specified by zero.
What does null data indicate?
No data results in error.
|
|
<MsgNum>
|
Numeric
|
5
|
Field Description:
Message number. (GRMNBR)
Format (n-numeric):
nnnnn
Special Format:
Zero, if does not exist.
Left justified, zero filled.
Examples:
01005
01006
00000
How is null data specified?
Null data is specified by zero.
What does null data indicate?
No data results in error.
|
|
<AppNum>
|
Numeric
|
5
|
Field Description:
Application number (GRMAPP)
Format (n-numeric):
nnnnn
Special Format:
Zero, if does not exist.
Right justified, zero filled.
Examples:
00000
How is null data specified?
Null data is specified by zero.
What does null data indicate?
No data results in error.
|
|
<MsgType>
|
Numeric
|
2
|
Field Description:
Message Type (GRMTYP)
Format (n-numeric):
nn
Special Format:
Right justified, zero filled.
Zero, if does not exist
Examples:
01 = endorsement messages
02 = information messages
03 = error messages
06 = NVB/NVA dates
How is null data specified?
Null data is specified by zero.
What does null data indicate?
No data results in error
|
|
<Lang>
|
Alphanumeric
|
1
|
Field Description:
Language (GRMLNG)
Format (x-alpha/numeric):
x
Special Format:
Zero, if does not exist
Examples:
0
How is null data specified?
Null data is specified by zero.
What does null data indicate?
No data results in error
|
|
<Text>
|
Alphanumeric
|
To End
|
Field Description:
Message (GRMMSG)
Format (x-alpha/numeric):
xxxx...
Special Format:
Character Blanks, if does not exist
Examples:
LAST DATE TO PURCHASE TICKET : 11APR03
FEE FOR CHANGE/NON-REF
How is null data specified?
Null data is specified by Character Blanks.
What does null data indicate?
N/A
If variable length, specify the maximum allowable length.
256
|
|
|
|
+ <PsgrFacilityCharge>
|
GFPF 1.0
|
|
|
|
<UniqueKey>
|
Alphanumeric
|
4
|
Field Description:
Unique Key. (0000)
Format (x-alpha/numeric):
xxxx
Special Format:
N/A
Examples:
0000
How is null data specified?
N/A
What does null data indicate?
No data results in error.
|
|
<QuoteNum>
|
Numeric
|
2
|
Field Description:
Quote number (GRPQNB)
Format (n-numeric):
nn
Special Format:
Right justified, zero filled.
Zero if does not exist
Examples:
00
How is null data specified?
N/A
What does null data indicate?
No data results in error
|
PFCCnt
Structured data only.
Not in XML.
|
Numeric
|
2
|
Field Description:
Number of PFC Items that follow.
(GRPNPF)
Format (n-numeric):
nn
Special Format:
Right justified, zero filled.
Examples:
01
How is null data specified?
N/A
What does null data indicate?
No data results in error
|
|
+ <PFCAry>
|
Array
|
n/a
|
|
|
+ <PFC>
|
FieldSet
|
n/a
|
|
|
<Airp>
|
Alpha
|
5
|
Field Description:
PFC Airport Code (GRPPFC)
Format (a-alpha):
aaaaa
Special Format:
Character blanks, if does not exist.
Left justified, character blank filled.
Examples:
DEN(blanks)
ORD(blanks)
How is null data specified?
Null data is specified by Character blanks
What does null data indicate?
No data results in error.
|
|
<Amt>
|
Alphanumeric
|
8
|
Field Description:
PFC Amount (GRPPFA)
Format (x-alpha/numeric):
xxxxxxxx
Special Format:
Right justified, zero filled.
Zero, if does not exist
Examples:
00004.50
00000450
On Request KLR
The amount appears without decimals and the decimals are so indicated and assumed based on the "USD" currency
On Response KLR
But when doing a detailed display of the fare it appears with the decimal places
How is null data specified?
N/A
What does null data indicate?
No data results in error
|
|
<Currency>
|
Alphanumeric
|
3
|
Field Description:
PFC Currency Code (GRPCPF)
Format (x-alpha/numeric):
xxx
Special Format:
Character blanks, if does not exist
Examples:
USD
GBP
INR
How is null data specified?
Null data is specified by character blanks.
What does null data indicate?
No data results in error
|
|
|
|
|
|
|
|
+ <SegRelatedInfo>
|
GFSR 3.0
|
|
|
|
<UniqueKey>
|
Alphanumeric
|
4
|
Passenger Description Number starting from '0001'
|
|
<QuoteNum>
|
Numeric
|
2
|
Zero if does not exist (GRSQNB)
|
|
<RelSegNum>
|
Numeric
|
2
|
Zero if does not exist (GRSRSN)
|
|
<NotValidBeforeDt>
|
Numeric
|
8
|
YYYYMMDD (GRSNVB)
Zero if does not exist
|
|
<NotValidAfterDt>
|
Numeric
|
8
|
YYYYMMDD (GRSNVA)
Zero if does not exist
|
|
<Stopover>
|
Alphanumeric
|
1
|
Blank if stopover at offpoint (GRSSTP)
X if no stopover at offpoint
|
|
<FIC>
|
Alphanumeric
|
8
|
Blank if does not exist (GRSFBC)
|
|
<TkDesignator>
|
Alphanumeric
|
8
|
Blank if does not exist (GRSTKT)
|
|
<BagInfo>
|
Alphanumeric
|
8
|
Blank if does not exist (GRSBAG)
|
|
<Fare>
|
Alphanumeric
|
8
|
Blank if does not exist (GRSFBP)
|
|
<HostUseOnly54>
|
Numeric
|
3
|
Host Use Only (GRSTG1)
|
|
<HostUseOnly55>
|
Numeric
|
3
|
Host Use Only (GRSTG2)
|
|
<FareComponentNum>
|
Character
|
2
|
Field not used. Should always be blank.
|
|
<FlownMile>
|
Alphanumeric
|
5
|
Blank if does not exist (GRSFLM)
|
|
<MaxPermittedMile>
|
Alphanumeric
|
5
|
Blank if does not exist (GRSMPM)
|
|
<HostUseOnly76>
|
Alpha
|
1
|
Host Use Only
(GRSTR1)
|
|
<PFOverrideWaivers>
|
Alpha
|
1
|
Y or N N if does not exist (GRSTR1)
|
|
<FlatFQ>
|
Alpha
|
1
|
Y or N N if does not exist (GRSTR1)
|
|
<PermittedDiscFare>
|
Alpha
|
1
|
Y or N N if does not exist (GRSTR1)
|
|
<PFQuoted>
|
Alpha
|
1
|
Y or N N if does not exist
(GRSTR1)
|
|
<Spare1>
|
Alpha
|
3
|
'NNN' if does not exist (GRSTR1)
|
|
<NetFareFIC>
|
Alphanumeric
|
8
|
Fare Basis Code of Net Fare(From Category 35)
Blank if does not exist
(GRSNFB)
|
|
<TkFareFIC>
|
Alphanumeric
|
8
|
Fare Basis Code of Ticket Fare(From Category 35)
Blank if does not exist
(GRSTFB)
|
|
|
|
+ <TaxBreakdown>
|
GFTS 1.0
|
|
|
|
<UniqueKey>
|
Numeric
|
4
|
Field Description:
Passenger Description Number.
Starting from 0001.
Format (n-numeric):
nnnn
Special Format:
Right justified, zero filled.
Examples:
0001
How is null data specified?
N/A
What does null data indicate?
No data results in error.
|
|
<QuoteNum>
|
Numeric
|
2
|
Field Description:
Quote Number (GRCQNM)
Format (n-numeric):
nn
Special Format:
Right justified, zero filled.
Zero, if does not exist.
Examples:
01
How is null data specified?
Null data is specified by Zero.
What does null data indicate?
Zero indicates null data.
|
|
<Spare1>
|
Alpha
|
2
|
Field Description:
Spares (GRCSP1)
Format (a-alpha):
aa
Special Format:
Character Blank filled.
Examples:
Character Blanks
How is null data specified?
Null data is specified by Character Blanks.
What does null data indicate?
No data results in error.
|
|
<TaxCode>
|
Alphanumeric
|
3
|
Field Description:
Tax Code (GRCCDE). Default Value: ZP - US Aviation Excise Tax.
Format (x-alpha/numeric):
xxx
Special Format:
Left justified, Character Blank filled.
Examples:
ZP (Character blank)
How is null data specified?
N/A
What does null data indicate?
No data results in error.
|
|
<TaxCurrency>
|
Alphanumeric
|
3
|
Field Description:
Tax Currency Code (GRCCUR)
Format (x-alpha/numeric):
xxx
Special Format:
Character Blank, if does not exist.
Examples:
USD
How is null data specified?
Null data is specified by Character Blanks.
What does null data indicate?
N/A
|
|
<DecPos>
|
Numeric
|
1
|
Field Description:
Tax Decimal Places (GRCDCP)
Format (n- numeric):
n
Special Format:
Zero if does not exist
Examples:
2
How is null data specified?
Null data is specified by Zero.
What does null data indicate?
Zero indicates no decimal places are entered in the tax amount.
|
|
<Spare2>
|
Alpha
|
8
|
Field Description:
Spare Indicator Byte. Default Value - N.
Format (a-alpha):
aaaaaaaa
Special Format:
N/A
Examples:
NNNNNNNN
How is null data specified?
Null data is specified by 'N'.
What does null data indicate?
'N' indicates that no data is entered or selected.
|
TaxCnt
Structured data only.
Not in XML.
|
Numeric
|
2
|
Field Description:
Number of Taxes (GRCNMT)
Format (n-numeric):
nn
Special Format:
Right justified, zero filled.
Zero, if does not exist.
Examples:
01
02
How is null data specified?
Zero
What does null data indicate?
Zero indicates null data.
|
|
+ <TaxAry>
|
Array
|
n/a
|
|
|
+ <Tax>
|
FieldSet
|
n/a
|
|
|
<City>
|
Alpha
|
5
|
Field Description:
Tax city code (GRCCIT)
Format (a-alpha):
aaaaa
Special Format:
Left justified, Character Blank filled.
Examples:
DEN (Character blanks)
How is null data specified?
N/A
What does null data indicate?
No data results in error.
|
|
<Amt>
|
Numeric
|
11
|
Field Description:
Tax amount (GRCAMT)
Format (n- numeric):
nnnnnnnnnnn
Special Format:
Right justified, zero filled.
Zero, if does not exist
Examples:
00000000300
On Request KLR
The amount appears without decimals and the decimals are so indicated and assumed based on the "USD" currency
On Response KLR
Further when we re-display the fare it appears without the decimal places
How is null data specified?
Null data is specified by Zero.
What does null data indicate?
Zero indicates no amount is entered for tax.
|
|
<Spare3>
|
Alpha
|
1
|
Field Description:
Spare (GRCSP4)
Format (a-alpha):
a
Special Format:
Character Blank, if does not exists.
Examples:
Character Blank
How is null data specified?
Null data is specified by Character Blank.
What does null data indicate?
N/A
|
|
|
|
|
|
|
|
+ <SegMapping>
|
GFZ6 1.0
|
|
|
|
<UniqueKey>
|
Alphanumeric
|
4
|
Not used - always 0000
|
SegCnt
Structured data only.
Not in XML.
|
Numeric
|
2
|
Description of Field:
Number of segment numbers to follow (GZ6NBR)
Format (a-alpha, n-numeric, x-alpha/numeric):
nn
Special Format:
Right justified, zero filled.
Examples:
01
How is null data specified?
N/A
What does null data indicate?
No segments follow.
|
|
+ <SegAry>
|
Array
|
n/a
|
|
|
+ <SegInfo>
|
FieldSet
|
n/a
|
|
|
<Seg>
|
Numeric
|
2
|
Description of Field:
PNR or BF display sequence number (GZ6SGA)
Format (a-alpha, n-numeric, x-alpha/numeric):
nn
Special Format:
Right justified, zero filled
Possible Values (Range):
Range 1G: 01-99
Range 1V: 01-08
How is null data specified?
Character zero
What does null data indicate?
Error.
|
|
<FIC>
|
Alpha
|
1
|
Description of Field:
FIC (Fare Identification Code) entered on this segment
Format (a-alpha, n-numeric, x-alpha/numeric):
a
Possible Values (List or Range):
Y or N Y if FIC entered (GZ6IND)
How is null data specified?
N/A
|
|
<Spares>
|
Alpha
|
7
|
For future expansion
NNNNNNN (GZ8ANN)
|
|
|
|
|
|
|
|
+ <AgntEnteredPsgrDescInfo>
|
GFZ8 1.0
|
|
|
|
<UniqueKey>
|
Alphanumeric
|
4
|
Field Description:
Passenger description number
Format (x-alpha/numeric):
xxxx
Special Format:
Starting from 0001
Examples:
0001
How is null data specified?
N/A
What does null data indicate?
No data results in error
|
|
<AgntEnteredPsgrDesc>
|
Alphanumeric
|
8
|
Field Description:
Agent Entered Pax Description
Format (x-alpha/numeric):
xxxxxxxx
Special Format:
Left justified, blank filled.
Examples:
Blanks
How is null data specified?
N/A
What does null data indicate?
No data results in error
|
|
<QuotedPsgrDesc>
|
Alphanumeric
|
8
|
Field Description:
Quoted Pax Description
Format (x-alpha/numeric):
xxxxxxxx
Special Format:
Left justified, blank filled.
Examples:
FGHTH
Blanks
How is null data specified?
N/A
What does null data indicate?
No data results in error
|
|
<PFCApplies>
|
Alpha
|
1
|
Field Description:
PFC Applies
Format (a-alpha):
a
Special Format:
N/A
Examples:
Y
How is null data specified?
N/A
What does null data indicate?
No data results in error
|
|
<Spare1>
|
Alpha
|
7
|
Field Description:
Spare
Format (a-alpha):
aaaaaaa
Special Format:
Default N.
Examples:
NNNNNNN
How is null data specified?
N/A
What does null data indicate?
No data results in error
|
AppliesToCnt
Structured data only.
Not in XML.
|
Numeric
|
2
|
Field Description:
Number of Passengers
Format (n-numeric):
nn
Special Format:
Right justified, zero filled..
Examples:
01
How is null data specified?
N/A
What does null data indicate?
No data results in error
|
|
+ <ApplesToAry>
|
Array
|
n/a
|
|
|
+ <AppliesTo>
|
FieldSet
|
n/a
|
|
|
<LNameNum>
|
Numeric
|
2
|
Field Description:
Sequential number identifying last name
Format (n-numeric):
nn
Special Format:
Right justified, zero filled.
Examples:
01
How is null data specified?
N/A
What does null data indicate?
No data results in error
|
|
<FNameNum>
|
Numeric
|
2
|
Field Description:
Sequential number identifying first name relative to last name element number
Format (n-numeric):
nn
Special Format:
Right justified, zero filled.
Examples:
02
How is null data specified?
N/A
What does null data indicate?
No data results in error
|
|
<AbsNameNum>
|
Numeric
|
2
|
Field Description:
Sequential number identifying absolute name
Format (n-numeric):
nn
Special Format:
Right justified, zero filled.
Examples:
02
How is null data specified?
N/A
What does null data indicate?
No data results in error
|
|
|
|
|
|
|
|
|
|
+ <CancelStoredFareMods>
|
4020 1.0
|
|
+ <FareNumInfo>
|
DPFI 1.0
|
|
|
|
+ <FareNumAry>
|
Array
|
n/a
|
|
|
<FareNum>
|
Numeric
|
3
|
Field Description:
Fare number of the item to which the following KLRs relate.
Format (n-numeric):
nnn
Special Format:
Right justified, zero filled.
Examples:
001
How is null data specified?
N/A
What does null data indicate?
No data results in error.
|
|
|
|
|
|
+ <AssocPsgrs>
|
DPPI 1.0
|
|
|
|
+ <PsgrAry>
|
Array
|
n/a
|
|
|
+ <Psgr>
|
FieldSet
|
n/a
|
|
|
<LNameNum>
|
Numeric
|
2
|
Field Description:
Unique, sequential number identifying the last name grouping
Format (n- numeric):
nn
Special Format:
Right justified, padded with zero, one or two characters. If no data, then blank filled.
Examples:
01
02
How is null data specified?
Null data specified by blanks.
What does null data indicate?
No data results in error.
|
|
<PsgrNum>
|
Numeric
|
2
|
Field Description:
Sequential number identifying a passenger within a last name grouping.
Format (n- numeric):
nn
Special Format:
Right justified, padded with zero, one or two characters. If no data, then blank filled.
Examples:
01
02
How is null data specified?
Null data specified by blanks.
What does null data indicate?
No data results in error.
|
|
<AbsNameNum>
|
Numeric
|
2
|
Field Description:
Unique, sequential number identifying each passenger irrespective of last name
Format (n- numeric):
nn
Special Format:
Right justified, padded with zero, one or two characters. If no data, then blank filled.
Examples:
01
blank blank
How is null data specified?
Null data specified by blanks
What does null data indicate?
It's a valid scenario. Null data doesn't result in error
|
|
|
|
|
|
|
|
|
|
+ <RestrictFareMods>
|
4022 1.0
|
|
+ <FareNumInfo>
|
DPFI 1.0
|
|
|
|
+ <FareNumAry>
|
Array
|
n/a
|
|
|
<FareNum>
|
Numeric
|
3
|
Field Description:
Fare number of the item to which the following KLRs relate.
Format (n-numeric):
nnn
Special Format:
Right justified, zero filled.
Examples:
001
How is null data specified?
N/A
What does null data indicate?
No data results in error.
|
|
|
|
|
|
|
|
+ <RestoreFareStatusMods>
|
4024 1.0
|
|
+ <FareNumInfo>
|
DPFI 1.0
|
|
|
|
+ <FareNumAry>
|
Array
|
n/a
|
|
|
<FareNum>
|
Numeric
|
3
|
Field Description:
Fare number of the item to which the following KLRs relate.
Format (n-numeric):
nnn
Special Format:
Right justified, zero filled.
Examples:
001
How is null data specified?
N/A
What does null data indicate?
No data results in error.
|
|
|
|
|
|
+ <AssocPsgrs>
|
DPPI 1.0
|
|
|
|
+ <PsgrAry>
|
Array
|
n/a
|
|
|
+ <Psgr>
|
FieldSet
|
n/a
|
|
|
<LNameNum>
|
Numeric
|
2
|
Field Description:
Unique, sequential number identifying the last name grouping
Format (n- numeric):
nn
Special Format:
Right justified, padded with zero, one or two characters. If no data, then blank filled.
Examples:
01
02
How is null data specified?
Null data specified by blanks.
What does null data indicate?
No data results in error.
|
|
<PsgrNum>
|
Numeric
|
2
|
Field Description:
Sequential number identifying a passenger within a last name grouping.
Format (n- numeric):
nn
Special Format:
Right justified, padded with zero, one or two characters. If no data, then blank filled.
Examples:
01
02
How is null data specified?
Null data specified by blanks.
What does null data indicate?
No data results in error.
|
|
<AbsNameNum>
|
Numeric
|
2
|
Field Description:
Unique, sequential number identifying each passenger irrespective of last name
Format (n- numeric):
nn
Special Format:
Right justified, padded with zero, one or two characters. If no data, then blank filled.
Examples:
01
blank blank
How is null data specified?
Null data specified by blanks
What does null data indicate?
It's a valid scenario. Null data doesn't result in error
|
|
|
|
|
|
|
|
|
|
<PretendFareCreationMods>
|
4026 1.0
|
|
+ <TicketingMods>
|
4032 3.3
|
|
+ <PlatingAirVMod>
|
DP0H 1.0
|
|
|
|
<AirV>
|
Alphanumeric
|
3
|
Field Description:
Plating Carrier code
Format (c-character):
cc_ (Blank)
Special Format:
Left justified character blank filled.
How is null data specified?
N/A.
What does null data indicate?
No data results in error.
|
|
|
|
+ <CommissionMod>
|
DP10 2.0
|
|
|
|
<Amt>
|
Alphanumeric
|
12
|
Field Description:
Amount, including decimal places if required.
Format (x-alpha/numeric):
xxxxxxxxxxxx
Special Format:
Left justified, blank filled.
Examples:
10
10.00
How is null data specified?
N/A
What does null data indicate?
No data results in no error
|
|
<Percent>
|
Alphanumeric
|
5
|
Field Description:
Percentage, including decimal places if required. Can be entered with Capped Amount.
Format (x-alpha/numeric):
xxxxx
Special Format:
Left justified, blank filled.
Examples:
5
5.00
How is null data specified?
N/A
What does null data indicate?
No data results in no error
|
|
<CommCappedAmt>
|
Alphanumeric
|
12
|
Field Description:
Capped Amount (1G only). Can be entered with Commission Percentage
Format (x-alpha/numeric):
xxxxxxxxxxxx
Special Format:
Left justified, blank filled.
Examples:
10
10.00
How is null data specified?
N/A
What does null data indicate?
No data results in no error
|
|
|
|
+ <SoldTicketed>
|
DP20 1.0
|
|
|
|
<SaleLocn>
|
Alpha
|
1
|
Field Description:
Sale Location Indicator
Format (a-alpha):
a
Possible Values(List):
I - Inside
O - Outside
How is null data specified?
N/A
What does null data indicate?
No data results in error
|
|
<TkLocn>
|
Alpha
|
1
|
Field Description:
Ticketing Location Indicator
Format (a-alpha):
a
Possible Values(List):
I - Inside
O - Outside
How is null data specified?
N/A
What does null data indicate?
No data results in error
|
|
|
|
+ <TicketingCurrency>
|
DP21 1.0
|
|
|
|
<TkCurrency>
|
Alpha
|
1
|
Description of Field:
Currency for ticketing:
'L' - local, 'E' - Euros, 'U' - USD, 'C' - CAD
Format (a-alpha, n-numeric, x-alpha/numeric):
a
Special Format:
na
Examples:
U (United States Dollars)
e.g., Range
NA
How is null data specified?
NA
What does null data indicate?
No data results in error
|
|
|
|
+ <BaggageAllowance>
|
DP22 1.0
|
|
|
|
+ <SegNumAry>
|
Array
|
n/a
|
|
|
+ <SegNumInfo>
|
FieldSet
|
n/a
|
|
|
<SegNum>
|
Numeric
|
3
|
Field Description:
Segment number of the itinerary item to which this KLR relates (0 = no segment select)
Format (x-alpha/numeric):
nnn
Special Format:
Right justified, zero filled.
How is null data specified?
N/A
What does null data indicate?
No data results in error
|
|
<AllowCnt>
|
Numeric
|
3
|
Field Description:
Number or weight of bags
Up to 3 numerics, 1-999
Format (x-alpha/numeric):
nnn
Special Format:
Right justified, zero filled.
How is null data specified?
N/A
What does null data indicate?
No data results in error
|
|
<AllowInd>
|
Alpha
|
1
|
Field Description:
Allowance type:
'P' = pieces (count must be 1-99)
'K' = Kilos (count must be 1-99)
'L' = Pounds (count must be 1-99)
' ' = other (count must be 1-999)
Format (x-alpha/numeric):
a
Special Format:
na
How is null data specified?
N/A
What does null data indicate?
No data results in error
Processing notes
- Overrides the global fares allowance.
- Only 3 characters of baggage allowance will print on the ticket.
- Will print in the ALLOW box of each flight coupon.
- Modifier can be varied by segment
- Delimiter between segments is a colon (:), delimiter between segment number and segments data is a lozenge (@), delimiter between GBG and GTD is an end item (|).
- GBG and GTD undergo similar editing because they can be segment related but they are NOT related to each other in any way.
|
|
|
|
|
|
|
|
+ <TicketDesignator>
|
DP23 1.0
|
|
|
|
+ <SegNumAry>
|
Array
|
n/a
|
|
|
+ <SegNumInfo>
|
FieldSet
|
n/a
|
|
|
<SegNum>
|
Numeric
|
3
|
Description of Field:
Segment number of the itinerary item to which this KLR relates (0 = no segment select)
Format (x-alpha/numeric):
nnn
Special Format:
Right justified, zero filled.
How is null data specified?
N/A
What does null data indicate?
No data results in error
|
|
<TkDesignator>
|
Alphanumeric
|
15
|
Description of Field:
Ticket Designator
Format (x-alpha/numeric):
xxxxxxxxxxxxxxx
Special Format:
left justified, blank filled.
Example:
12345678aaasd(blank)(blank)
How is null data specified?
N/A
What does null data indicate?
No data results in error
Processing notes
- Will apply ticket designator to all segments. Will print only 6 characters
- Can be varied by segment
- Delimiter between segments is a colon (:), delimiter between segment number and segments data is a lozenge (@), delimiter between GBG and GTD is an end item (|).
- GBG and GTD undergo similar editing because they can be segment related but they are NOT related to each other in any way.
|
|
|
|
|
|
|
|
+ <TicketValidity>
|
DP24 1.0
|
|
|
|
<Ind>
|
Alpha
|
1
|
Description of Field:
Identify the date field as Not Valid After (NWA) or Not Valid Before (NWB).
Format (a-alpha):
a
Possible Values (List):
'B' - Not Valid Before (NWB)
'A' - Not Valid After (NWA)
How is null data specified?
N/A
What does null data indicate?
No data results in error
|
|
+ <SegNumAry>
|
Array
|
n/a
|
|
|
+ <SegNumInfo>
|
FieldSet
|
n/a
|
|
|
<SegNum>
|
Numeric
|
3
|
Description of Field:
Segment number of the itinerary item to which this KLR relates (0 = no segment select)
Format (n-numeric):
nnn
Special Format:
Right justified, zero filled.
How is null data specified?
N/A
What does null data indicate?
No data results in error
|
|
<NVBDt>
|
Alphanumeric
|
5
|
Description of Field:
Date in DDMMM format
Format (x-alpha/numeric):
xxxxx
Special Format:
DDMMM
Example:
03JUN
How is null data specified?
N/A
What does null data indicate?
No data results in error
Processing Notes:
- May be used independently or together
- Will default to the entire itinerary with other modifiers
- May be used in conjunction with the ATFQ, Pricing Record or ticketing entry
- May be deleted or modified from the ATFQ line
- NVB/NVA dates will not be compared against one another.
- NVB/NVA dates will use the same date routine as the Pricing Record.
- No date analysis will be made against the itinerary.
- Dates entered with these modifiers will override those dates supplied by GlobalFares on outputs only.(The Linear Fare Data (*LF) section of the PNR created by Fare Quote will reflect true GlobalFares data).
- When the NVB/NVA modifiers are used as part of the Pricing Record build entry, the data will become unchangeable within the Pricing Record Fill-in screen ($NME).
- Modifier input hierarchy will remain the same (the HB entry will override the ATFQ, the ATFQ will override the PNR field).
- Pricing/Fare Construction Indicator (FCI): If the system is going to output a pricing code of "0", it will check to see if an NVA/NVB modifier is used; if so, the system will change the pricing code to "5" for agency issued tickets and "2" for United Airlines issued tickets
- OPTAT/TAT: When the NVB/NVA modifiers are used, dates will print in the current fields/boxes.
- ATB: When the NVB/NVA modifiers are used, dates will print in the current NVB/NVA fields/boxes on the flight coupon and the Post Audit document.
- MIR: These modifiers will output in current MIR 2 Labels.
NVB - Fare Basis Section, Label A08NVBC, 7 bytes alphanumeric (DDMMMYY)
NVA - Fare Basis Section, Label A08NVAC, 7 bytes alphanumeric (DDMMMYY)
The Pricing/Fare Construction Indicator is part of the Transaction Number in Passenger Data Section, Label A02TRN
|
|
|
|
|
|
|
|
+ <PrintRLoc>
|
DP25 1.0
|
|
|
|
<RLoc>
|
Alphanumeric
|
6
|
Field Description:
Record locator
Format (x-alpha/numeric):
xxxxxx
Special Format:
Examples:
TP1CDI
How is null data specified?
N/A
What does null data indicate?
No data results in error
|
|
<Vnd>
|
Alphanumeric
|
3
|
Field Description:
Airline/GDS code
Format (x-alpha/numeric):
xxx
Special Format:
Left justified, blank filled
Examples:
1V(blank)
How is null data specified?
N/A
What does null data indicate?
No data results in error
Processing Notes:
- When issuing tickets, the agent can be able to override the Apollo record locator with the record locator and airline code of a PNR originally booked directly in another airline reservation system.
- MIR 62 and 67 will contain the Apollo record locator. MIR 92 contains both.
|
|
|
|
+ <PsgrReceiptOverride>
|
DP26 1.0
|
|
|
|
<Gtid>
|
Alphanumeric
|
6
|
Field Description:
LNIATA/GTID
Format (x-alpha/numeric):
xxxxxx
Special Format:
N/A
Examples:
CDCE1E
CCD0E5
How is null data specified?
Null data is specified by blanks.
What does null data indicate?
Null data results in no error.
|
|
|
|
+ <EndorsementBox>
|
DP27 1.0
|
|
|
|
<Endors1>
|
Alphanumeric
|
29
|
Description of Field:
First endorsement box, free form text
Format (x-alpha/numeric):
xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Special Format:
Left justified, blank filled
Words can be separated by an @ on 1V and a blank on 1G
Examples:
NON@REFUNDABLE
How is null data specified?
N/A
What does null data indicate?
No data results in error
|
|
<Endors2>
|
Alphanumeric
|
29
|
Description of Field:
Second endorsement box, free form text
Format (x-alpha/numeric):
xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Special Format:
Left justified, blank filled
Words can be separated by an @ on 1V and a blank on 1G
Examples:
NON@REFUNDABLE
How is null data specified?
N/A
What does null data indicate?
No data results in error
|
|
<Endors3>
|
Alphanumeric
|
29
|
Description of Field:
Third endorsement box, free form text
Format (x-alpha/numeric):
xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Special Format:
Left justified, blank filled
Words can be separated by an @ on 1V and a blank on 1G
Examples:
NON@REFUNDABLE
How is null data specified?
N/A
What does null data indicate?
No data results in error
|
|
|
|
+ <BulkTicket>
|
DP28 1.0
|
|
|
|
<FareConstructInd>
|
Alpha
|
1
|
Field Description:
1G only
'P' - Print fare construction (equivalent of BT*PC entry)
'S' - Suppress Fare construction
(Blank for 1V system)
Format (x-alpha/numeric, a-alpha):
a
Special Format:
How is null data specified?
N/A
What does null data indicate?
No data results in error.
|
|
|
|
<NonRefundBulkTicket>
|
DP29 1.0
|
|
+ <OBFExemptMods>
|
DP2A 1.0
|
|
|
|
+ <OBFExemptAry>
|
Array
|
n/a
|
|
|
+ <OBFExempt>
|
FieldSet
|
n/a
|
|
|
<OBFExemptTypeInd>
|
Alpha
|
1
|
Description of Field:
OB Fees exempt type indicator.
Format (a-alpha, n-numeric, x-alphanumeric, b-character blank):
Alpha
Special Format:
Left justified character blank filled.
List of Possible Values:
T-Exempt on ticketing fee
F-Exempt on FOP fee
How is null data specified?
blank
What does null data indicate?
This can be NULL if no OB Fees exempt sub-codes are explicitly entered
|
|
<OBFExemptSubcode>
|
Alphanumeric
|
2
|
Description of Field:
Explicit OB Fees exempt sub-code data.
Format (a-alpha, n-numeric, x-alphanumeric, b-character blank):
Alphanumeric
List of Possible Values:
C1, C2, 01, 02 etc
How is null data specified?
Blanks
What does null data indicate?
This can only be NULL if no OB fees collected.
|
|
<Spare>
|
Alphanumeric
|
3
|
Description of Field:
Future OB Fees exempt subcode data expansion area spares.
Format (a-alpha, n-numeric, x-alphanumeric, b-character blank):
Alphanumeric
Special Format:
Left justified character blank filled.
List of Possible Values:
Alphanumeric data as defined by ATPCO
How is null data specified?
blank
What does null data indicate?
Will be blank until ATPCO expands to full subcode size.
|
|
|
|
|
|
|
|
+ <FreeFormTicket>
|
DP30 1.0
|
|
|
|
<Text>
|
Alphanumeric
|
To End
|
Freeform up to 17 characters. Alpha , numeric and special characters allowed.
Special characters are *-@#
Will print in the FOP area of OPTAT tickets. If used with a CC FOP, part of the CC information will be truncated to make room for all of the GFP data.
A pillow (@) will appear as a blank space.
An asterisk (*) will appear as a slash(/).
A hyphen/dash character will print as entered (-).
On OPTAT tickets only the last 14 characters will print.
Not Valid with ATB Ticketing.
When a credit is used as form of payment, the vendor/card number will print as today; however, the expiration date (if entered) and the extended payment indicator (if entered) will be suppressed from printing when modifier is used.
When a credit card is used as form of payment and a manually obtained APPROVAL code is entered (#*123456), the letter "M" in front of the approval will be suppressed from printing when all 17 characters of the new modifier are used. If 16 or fewer characters are entered, the "M" will print as it does today.
|
|
|
|
+ <GroupTour>
|
DP31 1.0
|
|
|
|
<FareConstructInd>
|
Alpha
|
1
|
Field Description:
For 1G system:
- 'P' - Print fare construction (equivalent of IT*PC entry)
- 'S' - Suppress Fare construction
Blank for 1V system
Format (x-alpha/numeric):
For 1G - x
Blank for 1V
Special Format:
None
Examples:
P
How is null data specified?
N/A
What does null data indicate?
On 1V there is no data.
|
|
|
|
+ <TourCode>
|
DP33 1.0
|
|
|
|
<Rules>
|
Alphanumeric
|
To End
|
Field Description:
1V rules: 1-15 characters, which will print on the ticket.
1G rules: 1-14 characters (except Saudi TAT which allows 1-10)
Format (x-alpha/numeric):
xxxxxxxxxxxxxx - 1G
xxxxxxxxxxxxxxx - 1V
Special Format:
Left Justified. Blank filled.
1V:
Special character pillow (@) appears as blank space.
An asterisk(*) will appear as a slash
A hyphen (-) is allowed and is unchanged
Examples:
E12SIN4
SHELL23CX
How is null data specified?
N/A
What does null data indicate?
No data results in error.
|
|
|
|
+ <NetRemitOverride>
|
DP34 1.0
|
|
|
|
<Amt>
|
Alphanumeric
|
8
|
Field Description:
Dollar Amount
Format (x-alpha/numeric):
xxxxxxxx
Special Format:
8 characters - can currently enter 3 decimal places. Right justified, zero filled.
Examples:
100.00
100
How is null data specified?
N/A
What does null data indicate?
Null data results in error.
|
|
|
|
+ <ActualSellingFare>
|
DP35 1.0
|
|
|
|
<Amt>
|
Alphanumeric
|
To End
|
Field Description:
ASF Amount
Format (x-alpha/numeric):
xxxx...
Special Format:
Left justified, blank filled.
Examples:
100.00
100
How is null data specified?
N/A
What does null data indicate?
No data results in error.
|
|
|
|
+ <AccountingInfo>
|
DP36 1.0
|
|
|
|
<Info>
|
Alphanumeric
|
To End
|
Field Description:
The Accounting Information code can be a free flow stream of upto 20 characters. The rules differ by country, but the default (if not otherwise specified) is a 1 to 14 character alphanumeric string. The character string can contain other printable but non-alphanumeric characters (BSP dependent).
Format (x-alpha/numeric):
xxxx...
Special Format:
Left justified, blank filled.
Examples:
CASH
SHELL20
How is null data specified?
N/A
What does null data indicate?
No data results in error.
|
|
|
|
+ <CorporateDiscount>
|
DP37 1.0
|
|
|
|
<Info>
|
Alphanumeric
|
To End
|
Field Description:
Accounting Information
Format (x-alpha/numeric):
xxxx...
Special Format:
Left justified, blank filled.
Examples:
Cash
SHELL20
How is null data specified?
N/A
What does null data indicate?
No data results in error.
|
|
|
|
+ <InvoiceFare>
|
DP38 1.0
|
|
|
|
<Currency>
|
Alpha
|
3
|
Field Description:
Currency code
Format (a-alpha):
aaa
Special Format:
Left justified with 3 characters
Examples:
USD
INR
How is null data specified?
N/A
What does null data indicate?
No data results in error.
|
|
<Amt>
|
Alphanumeric
|
To End
|
Field Description:
Amount
Format (x-alpha/numeric):
xxx
Special Format:
Left justified.
Examples:
100.00
100
10000
How is null data specified?
N/A
What does null data indicate?
No data results in error.
|
|
|
|
+ <NettFare>
|
DP39 1.0
|
|
|
|
<Currency>
|
Alpha
|
3
|
Field Description:
Currency code
Format (a-alpha):
aaa
Special Format:
NA
Examples:
USD
INR
How is null data specified?
N/A
What does null data indicate?
N/A
|
|
<Amt>
|
Alphanumeric
|
To End
|
Field Description:
Amount
Format (x-alpha/numeric):
xxx...
Special Format:
Left justified, variable length
Examples:
100.00
100
How is null data specified?
N/A
What does null data indicate?
N/A
|
|
|
|
<NettRemittance>
|
DP40 1.0
|
|
+ <ValueCode>
|
DP41 1.0
|
|
|
|
<ValueInd>
|
Alpha
|
1
|
Field Description:
Pseudo City Code
The Value code is a code entered onto the ticket and determines the supplementary commission an agency will make
Format (a-alpha):
a
Special Format:
One character
Examples:
'Z' commission percentage (0001-0100%),
'D' net fare amount (0000-9999),
'K' commission amount (0000-9999),
'C' commission percentage (0000-0100)
How is null data specified?
N/A
What does null data indicate?
No data results in error.
|
|
<Amt>
|
Alphanumeric
|
To End
|
Description of Field:
Field Description:
Amount
Format (x-alpha/numeric):
xxxx
Special Format:
None
Examples:
AB9999
How is null data specified?
N/A
What does null data indicate?
No data results in error.
|
|
|
|
+ <DocumentSelect>
|
DP42 2.0
|
|
|
|
<TkOnlyInd>
|
Alpha
|
1
|
Description of Field:
Specifies Ticket Only option
Format (a-alpha)
a
Examples:
Set to 'Y' if user wishes to alter the system default of producing a ticket, itin and MIR. Setting this will inhibit itin and MIR, unless these have also been specifically requested (Terminal Equivalent: DTD)
|
|
<ETInd>
|
Alpha
|
1
|
Description of Field:
Specifies Electronic Ticket Only option
Format (a-alpha)
A
Examples:
Set to 'Y' if an Electronic Ticket is required (Terminal Equivalent: DLD, ET)
Set to 'P' if Paper Ticket is required (Terminal Equivalent: PT)
How is null data specified?
Character blanks
What does null data indicate?
Leave blank for system to determine type
|
|
<CouponCnt>
|
Alphanumeric
|
1
|
Description of Field:
Specifies the number of ATB (Automated Ticket and Boarding passes) Post-Audit Coupons ticket option
Format (a-alpha)
A
Special Format:
Setting this field to zero will generate 'GA0'.
Use a blank if you do not want this modifier generated
NOTE: If this field is set, then the next optional field (host/satellite) can also be set.
Examples:
2
Number of coupons (system defaults to 1) (max = 3)
(Terminal Equivalent: GA - 1V only)
How is null data specified?
Character blanks
What does null data indicate?
Leave blank for system default.
|
|
<DestInd>
|
Alpha
|
1
|
Description of Field:
Specifies an ATB Post-Audit Destination ticket option
Format (a-alpha)
A
Example:
Destination for coupons:
'H' - Home
'S' - Satellite
(optional - related to number of Post Audit Coupons)
|
|
<ForceInd>
|
Alpha
|
1
|
Description of Field:
Specifies a Force Audit Coupon ticket option
Format (a-alpha)
A
Example:
Set to 'A' to print an ATB Audit Coupon and override normal BSP setting. (Terminal Equivalent: 1G only - AU modifier)
|
|
<MIRInd>
|
Alpha
|
1
|
Description of Field:
Specifies Machine Interface Record (MIR) Only ticket option
Format (a-alpha)
A
Examples:
Six valid settings:
'A' - Accounting MIR (Terminal Equivalent: DBD - 1V only)
'N' - Non-Accounting MIR (Terminal Equivalent: DAD)
'R' - Non-Accounting Remote MIR (requires GTID/CRS and PCC to be populated: see below) (Terminal Equivalent: DND)
'F' - Non-Faring Remote MIR (requires GTID/CRS and PCC to be populated: see below) (Terminal Equivalent: DJD - 1V only)
'X' - Dual MIR. Issues a ticket, itinerary, a two ticketing MIRs - to the MIR device to which the CRT is physically linked, and a copy of that MIR to the MIR device specified in the following fields (DXD)
Special Format:
If one of these options is set (except for 'X'), the system default of producing a ticket, itin and MIR will be overridden. Setting this will inhibit ticket and itin, unless these have also been specifically requested.
|
|
<Locn>
|
Alphanumeric
|
6
|
Description of Field:
Specifies the Location for data from the MIR only option field.
Format (a-alpha)
A
Special Format:
Required if option 'R', 'G', 'F', or 'X' is selected in MIR Only field. Populated with either the destination GTID (LNIATA - Line Number Interchange Address Terminal Address) for MIRs within the same system, or CRS name (1G or 1V) for MIRs to another system.
|
|
<PCC>
|
Alphanumeric
|
4
|
Description of Field:
Pseudo City Code.
Format (x-alpha/numeric:
XXXX
Special Format:
Left Justified Blank Filled
PCCs with less than 4 characters should be padded with a leading zero. For example, X0B should be submitted as 0X0B.
CDATA can also be used to override the attributes of this field. For example,
![CDATA[ X0B]] In this case the field is forced to right justify with a leading blank.
Examples:
1WP7
0X0B
![CDATA[ X0B]]
![CDATA[2GK5]]
How is null data specified?
Character blanks
What does null data indicate?
No user data was input.
|
|
<ItinInd>
|
Alpha
|
1
|
Description of Field:
Specifies the Itinerary or Invoice type option for the ticket.
Format (a-alpha)
a
Examples:
'I' - normal itin/invoice (Terminal Equivalent: DID)
'P' - Pocket itin (ticketing only) (Terminal Equivalent: DPD - 1V only)
|
|
<FaxInd>
|
Alpha
|
1
|
Description of Field:
Specifies the Itinerary or Invoice fax type option for the ticket.
Format (a-alpha)
a
Examples:
'X' - FAX - Can store the Fax modifier (Terminal Equivalent: GFX) or can use with ticketing.
'D' - Itin FAX - can't be stored, can use with ticketing only (Terminal Equivalent: DFX).
(Terminal Equivalent: 1V only - DFX/GFX)
|
|
<ItinOptInd>
|
Alpha
|
1
|
Description of Field:
Specifies the Itinerary or Invoice type options for the ticket.
Format (a-alpha)
a
Examples:
'F' - itin with no fare information (Terminal Equivalent: GIF/DCD)
'A' - itin with no amounts (Terminal Equivalent: GIN, IN)
'D' - itin, but do not decrement invoice numbers (Terminal Equivalent: GID 1V only)
|
|
<SepInd>
|
Alpha
|
1
|
Description of Field:
Specifies whether there are separate itineraries.
Format (a-alpha)
a
Examples:
Y
N
Note:
If set to 'Y', one itinerary will be printed per passenger (Terminal Equivalent: GIS/ IS)
|
|
<PocketItinCnt>
|
Alphanumeric
|
1
|
Description of Field:
Number of pocket itineraries for ATB (Terminal Equivalent: GP - 1V only).
A pocket itinerary is an option to print a passenger itinerary together with associated information on pocket itinerary stock. The data printed is identical to full length documents.
Format (a-alpha)
a
Special Format:
Setting this field to zero will generate 'GP0', use a blank if you do not want this modifier generated
If this field is set, then the next optional field (host/satellite) can also be set.
How is null data specified?
Character blanks
What does null data indicate?
System default.
|
|
<PocketItinsDestInd>
|
Alpha
|
1
|
Description of Field:
Destination for Pocket Itineraries
Format (a-alpha)
A
Special Format:
(optional - related to number of Pocket Itineraries)
Examples:
'H' - Home
'S' - Satellite
|
|
<DeliveryDocsInd>
|
Alpha
|
1
|
Description of Field:
Specifies the Delivery Documents
Format (a-alpha)
A
Example:
'D' - select delivery documents (Terminal Equivalent: DDD - 1V only)
NOTE: Not valid with any D modifier except DPD, GA, GB, GBN, GFX, GT, GF, GFP, GID, GUSD, GCAD, GIN, GIS
PROCESSING NOTES:
ATB only.
Open to buy not down dated.
The printer 'firmware' (pectab) must be one of the following:
2200 - version 08
2800 - version 05, 07, 08
An error response will be displayed if the agency is using a 2200 printer with firmware versions 04 or 07
Requires Delivery (D-) field in PNR.
FOP is not required on the DDD modifier
Does not go to fare quote.
|
|
|
|
+ <SatelliteTicketPrinting>
|
DP43 1.0
|
|
|
|
<IATANum>
|
Numeric
|
7
|
Field Description:
7 digit agency IATA number
Format (n-numeric):
nnnnnnn
Special Format:
None
Examples:
5645643
How is null data specified?
N/A
What does null data indicate?
No data results in error.
|
|
<ChkDigit>
|
Numeric
|
1
|
Field Description:
Mod 7 check digit for the agency IATA number
Format (n-numeric):
n
Special Format:
None
Examples:
0
How is null data specified?
N/A
What does null data indicate?
No data results in error.
|
|
<Pseudo>
|
Alphanumeric
|
4
|
Field Description:
3 or 4 character pseudo city code (PCC). Valid for
Italian Ticketing variation/Cross Boarder STP (CBSTP).
Format (x-alpha/numeric):
xxxx
Special Format:
Left justified, blank filled. Three or four characters.
Examples:
XZ5
2GK5
How is null data specified?
N/A
What does null data indicate?
No data results in error.
|
|
|
|
<ItinRmksSuppression>
|
DP44 1.0
|
|
+ <WaitlistSegSelect>
|
DP45 1.0
|
|
|
|
+ <SegNumAry>
|
Array
|
n/a
|
|
|
<SegNum>
|
Numeric
|
3
|
Field Description:
Segment number of the itinerary item to which this KLR relates.
Format (n-numeric):
nnn
Special Format:
Right justified, zero filled.
Examples:
000
001
002
How is null data specified?
N/A
What does null data indicate?
No data results in error.
|
|
|
|
|
|
+ <AuxSegSelect>
|
DP46 1.0
|
|
|
|
+ <SegNumAry>
|
Array
|
n/a
|
|
|
<SegNum>
|
Alphanumeric
|
3
|
Field Description:
Segment number of the itinerary item to which this KLR relates.
Format (x-alpha/numeric):
xxx
Special Format:
Right justified, blank filled.
Examples:
ALL
003
How is null data specified?
N/A
What does null data indicate?
N/A
|
|
|
|
|
|
+ <BackOfficeInfo>
|
DP47 1.0
|
|
|
|
<UserCode>
|
Alphanumeric
|
1
|
Field Description:
User Code - optional (terminal - OP)
Format (x-alpha/numeric):
x
Special Format:
N/A
Examples:
2
A
How is null data specified?
N/A
What does null data indicate?
No data results in no error.
|
|
<Process>
|
Alphanumeric
|
1
|
Field Description:
Process code - optional (terminal - PC)
Format (x-alpha/numeric):
x
Special Format:
N/A
Examples:
1
3
How is null data specified?
N/A
What does null data indicate?
No data results in no error
|
|
<Skeada>
|
Alphanumeric
|
8
|
Field Description:
Optional data indicating Skeada plus Line File Number. (terminal - SK)
Format (n-numeric, x-alpha/numeric):
xxxxxx-n
Special Format:
Left justified, blank filled. 1 to 6 alphanumeric, followed by '-', and 1 numeric character.
Data is edited, removing dash and right justifying final numeric i.e.
A4-3 output as 'A4 3'
Examples:
A4-3
USD-1
How is null data specified?
N/A
What does null data indicate?
No data results in no error
|
|
<VAT>
|
Alphanumeric
|
2
|
Field Description:
VAT code - optional (terminal - IV)
Format (x-alpha/numeric):
xx
Special Format:
Right justified, zero filled.
Examples:
A3
3A
How is null data specified?
N/A
What does null data indicate?
No data results in no error
|
|
<ActualFare>
|
Numeric
|
8
|
Field Description:
Optional data indicating Actual Paid Fare. (terminal - PZ)
Format (n-numeric):
nnnnnnnn
Special Format:
Right justified, zero filled. 4 to 8 numeric characters
Examples:
00010248
How is null data specified?
Zero
What does null data indicate?
Zero specifies null data.
|
|
<ExchangeRate>
|
Numeric
|
7
|
Field Description:
Optional data indicating Exchange Rate. (terminal - CM)
Format (n-numeric):
nnnnnnn
Special Format:
Right justified, zero filled. 1 to 7 numeric characters.
Examples:
0048898
How is null data specified?
Zero
What does null data indicate?
Zero specifies null data.
|
|
<PrintDelivery>
|
Alphanumeric
|
10
|
Field Description:
Optional data indicating Print Delivery Note plus Sale Code. (terminal - OP)
Format (a-alpha, x-alpha/numeric):
xxxxxxxxxx
Special Format:
Left justified, blank filled.
1 alpha character ('N' or 'S'), followed by '-', and 1 to 8 numeric.
Examples:
How is null data specified?
N/A
What does null data indicate?
No data results in no error
|
|
<ClientFile>
|
Alphanumeric
|
8
|
Field Description:
Optional data indicating Client/Account File plus Form of Payment. (terminal - CL)
Format (a-alpha, x-alpha/numeric):
xxxxxx-x
Special Format:
Right justified, zero filled.
1 to 6 alphanumeric characters, followed by '-', and 1 character ('A' or 'C').
Examples:
US783-A
How is null data specified?
N/A
What does null data indicate?
No data results in error.
|
|
|
|
+ <EncargosFinanceiros>
|
DP48 1.0
|
|
|
|
<EF>
|
Alphanumeric
|
To End
|
Field Description:
On Brazilian Domestic transactions, when they are paid by invoice, the Fare Amount is subject to an increase according to a percentage called 'Factor de Encargos Financeiros' (FEF). In this case the Equivalent Fare amount will be equal to the Fare Amount plus FEF (and manually input in the Fare Quote by the agent).
The Brazilian BSP has requested that for certain domestic transactions, the Remittance Area on the ticket reflects the Fare Amount rather than the Equivalent Fare Amount, as in this case the FEF should not be reported in the Remittance Area.
The EF modifier indicates to the system that the Fare Amount is to be printed on the Remittance Area instead of the Equivalent Fare as is normal
Format (x-alpha/numeric):
xxxxxxxxxxxxxxxx
Special Format:
Left justified. Blank filled.
Examples:
USD1000
USD10248
How is null data specified?
N/A
What does null data indicate?
N/A.
|
|
|
|
<SysGenItinNumbers>
|
DP49 1.0
|
|
+ <OriginalAgentDetail>
|
DP50 1.0
|
|
|
|
<ExchangeNum>
|
Numeric
|
13
|
Document number for exchange
13 digit ticket number
|
|
<Pt>
|
Alphanumeric
|
3
|
City of issuance 3 character city / airport code
|
|
<Dt>
|
Alphanumeric
|
7
|
Original issue date DDMMMYY - date must be within the last year
|
|
<IATANum>
|
Numeric
|
7
|
Iata number of retail agent (7 numerics)
|
|
<ChkDigit>
|
Numeric
|
1
|
Modula 7 check digit
|
|
|
|
+ <VAT>
|
DP51 1.0
|
|
|
|
<VATAmt>
|
Numeric
|
6
|
Field Description:
VAT Amount
Note - This modifier does not control data that prints on a ticket.
The VAT modifier controls data that prints on an Itinerary/Invoice document and data that is stored in a MIR document. The DYO label @VATPCT defines where the modifier data will print on the Itinerary/Invoice document and only MIR type 04 will store data input on this modifier.
Format (n-numeric):
nnnnnn
Special Format:
Right justified, zero filled.
Examples:
010248
How is null data specified?
Null data specified by zero.
What does null data indicate?
Null data results in error.
|
|
<Type>
|
Alpha
|
1
|
Field Description:
Type
Possible Values (List):
I - Inclusive,
E - Exclusive
Format (a-alpha):
a
Special Format:
Blank if no data.
Examples:
I
How is null data specified?
N/A
What does null data indicate?
Null data results in error.
|
|
|
|
<NonNegotiableCharge>
|
DP53 1.0
|
|
<PrintTableOverride>
|
DP54 1.0
|
|
+ <TktFareConstruction>
|
DPCF 1.0
|
|
|
|
<MaxLen>
|
Numeric
|
4
|
Field Description:
Maximum length for this screen
Format (n-numeric):
nnnn
Special Format:
Right aligned, zero filled.
Examples:
0163
How is null data specified?
N/A
What does null data indicate?
No data results in error
|
FareConstructionLen
Structured data only.
Not in XML.
|
Numeric
|
4
|
Field Description:
Length of following Fare Construction
Format (n-numeric):
nnnn
Special Format:
Right aligned, zero filled.
Examples:
0186
How is null data specified?
N/A
What does null data indicate?
No data results in error
|
|
<FareConstructionText>
|
Alphanumeric
|
VL
|
Field Description:
Fare Construction
Format (x-alpha/numeric):
xxxxxxxxxxxxxxxxxxxxx
Special Format:
Blank filled.
Examples:
23JUL DEN UA ORD Q9.30 1087.14 UA ORD
How is null data specified?
N/A
What does null data indicate?
No data results in error
|
|
|
|
+ <DetailedBillingMask>
|
DPDB 1.0
|
|
|
|
<CCNum>
|
Numeric
|
20
|
Credit Card Number
Format (n-numeric):
nnnnnnnnnnnnnnnnnnnn
Special Format:
Right justified zero filled
no blanks or dashes allowed
What does null data indicate?
No data results in error
|
|
+ <BillingDataInfoAry>
|
Array
|
n/a
|
|
|
+ <BillingDataInfo>
|
FieldSet
|
n/a
|
|
|
<FieldID>
|
Alpha
|
2
|
Description of Field:
Identifies which of the possible detailed billing data items is provided next.
Possible Values:
The data in this field is provided dynamically by the Host System.
|
|
<MinLen>
|
Numeric
|
2
|
Description of Field:
Detailed Billing data field minimum length as provided by the Credit Card Vendor.
Possible Values (Range):
0 to 17. Value should not exceed the Detailed Billing Data field length of 17.
How is null data specified?
Null data is represented by zeros.
What does null data indicate?
If this field is zeros, then this field should be considered optional. In this case, it should actually not be included in the array.
Special considerations?
This field should be considered 'read only' and not altered. It should be returned with the same value it was received with.
|
|
<MaxLen>
|
Numeric
|
2
|
Description of Field:
Detailed Billing data field maximum length as provided by the Credit Card Vendor.
Possible Values (Range):
0 to 17. Value should not exceed the Detailed Billing Data field length of 17.
How is null data specified?
Null data is represented by zeros.
What does null data indicate?
If this field is zeros, then this field should be considered optional. In this case, it should actually not be included in the array.
Special considerations?
This field should be considered 'read only' and not altered. It should be returned with the same value it was received with.
|
|
<DataType>
|
Alpha
|
1
|
Description of Field:
Detailed Billing data, data type as provided by the Credit Card Vendor.
Possible Values (List):
A - Alpha Characters.
N - Numeric Characters.
X - Alphanumeric Characters.
B - Alphanumeric Characters.
D - Date DDMMMYY.
How is null data specified?
Null data is represented by zeros.
What does null data indicate?
If this field is zeros, then the data type should default to 'B' for Alphanumeric.
Special considerations?
This field should be considered 'read only' and not altered. It should be returned with the same value it was received with.
|
|
<FieldDescription>
|
Alphanumeric
|
25
|
Description of Field:
Detailed Billing data, field description for this field ID, as provided by the Credit Card Vendor.
Possible Values:
The data in this field is provided dynamically by the Host System.
How is null data specified?
Null data is represented by zeros.
What does null data indicate?
This field should always contain a value provide by the Host System.
Special considerations?
This field should be considered 'read only' and not altered. It should be returned with the same value it was received with.
|
|
<Data>
|
Alphanumeric
|
17
|
Description of Field:
Detailed Billing Data Field Description represented by the previous identifier, Detailed Billing Data Field ID.
How is null data specified?
If a value was given in the Detailed Billing Data Field ID, then a description should be provided for that ID in this field.
What does null data indicate?
If a value was given in the Detailed Billing Data Field ID, then a description should be provided for that ID in this field.
|
|
|
|
|
|
|
|
+ <ElectronicTicketFailed>
|
DPEF 1.0
|
|
|
|
<CancelInd>
|
Alpha
|
1
|
Description of Field:
Cancel ticketing transaction indicator:
'Y' - cancel
Format (a-alpha):
a
Special Format:
N/A
Examples:
Y
How is null data specified?
N/A
What does null data indicate?
No data results in error.
|
|
<IssuePaperTkInd>
|
Alpha
|
1
|
Description of Field:
Issue paper ticket indicator:
'Y' - issue paper ticket.
Format (a-alpha):
a
Special Format:
N/A
Examples:
Y
How is null data specified?
N/A
What does null data indicate?
No data results in error
|
|
<IssuePaperTkToSTP>
|
Alpha
|
1
|
Description of Field:
Issue Paper Ticket to STP location indicator:
'Y' - on response means that this option is available,
On request means 'Issue Paper Ticket to STP location' (1G only).
Format (a-alpha):
a
Special Format:
N/A
Examples:
Y
How is null data specified?
N/A
What does null data indicate?
No data results in error.
|
|
<STPlocation>
|
Alphanumeric
|
8
|
Description of Field:
STP location
Format (x-alpha/numeric):
xxxxxxxx
Special Format:
N/A
Examples:
99999992
How is null data specified?
N/A
What does null data indicate?
No data results in error.
|
|
|
|
+ <FareNumInfo>
|
DPFI 1.0
|
|
|
|
+ <FareNumAry>
|
Array
|
n/a
|
|
|
<FareNum>
|
Numeric
|
3
|
Field Description:
Fare number of the item to which the following KLRs relate.
Format (n-numeric):
nnn
Special Format:
Right justified, zero filled.
Examples:
001
How is null data specified?
N/A
What does null data indicate?
No data results in error.
|
|
|
|
|
|
+ <FaxData>
|
DPFX 1.0
|
|
|
|
<FaxNum>
|
Alphanumeric
|
20
|
Field Description:
Fax Number. Max is 16 digits. Min is 7.
Format (x-alpha/numeric):
xxxxxxx
Special Format:
Left justified, blank filled. Can include '-'s and spaces.
Examples:
011987654
How is null data specified?
N/A
What does null data indicate?
No data results in error
|
|
<CoverSheetInd>
|
Alpha
|
1
|
Field Description:
Cover sheet. This option is to be clicked to specify whether to include a cover page with your fax or not)
Possible Values (List):
Y-Include cover with your Fax
N-Donot include cover with your Fax
Format (x-alpha/numeric):
a
Special Format:
N/A
Examples:
Y
N
How is null data specified?
N/A
What does null data indicate?
No data results in error
|
|
<TermCondInd>
|
Alpha
|
1
|
Field Description:
- Term and Conditions T
Possible Values (List):
he drop-down is to be clicked to select the desired option:
- Y- for US only: Include the Terms and Conditions in the fax or e-mail.
- N- for US only: Do not include the Terms and Conditions in the fax or e-mail.
- E- English for Canada Globalfax: Include the Terms and Conditions in English language.
- F- French for Canada Globalfax: Include the Terms and Conditions in French language.
- B- Bilingual for Canada Globalfax: Include the Terms and Conditions in French Canadian language.
- N- None for Canada Globalfax: Do not include the Terms and Conditions in the fax or e-mail.)
Format (a-alpha):
a
Special Format:
N/A.
Examples:
Y
N
How is null data specified?
N/A
What does null data indicate?
No data results in error.
|
|
<ToAddr>
|
Alphanumeric
|
46
|
Field Description:
Free format text of ''to'' address
Format (x-alpha/numeric):
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Special Format:
Left justified, blank filled.
Examples:
10 Hamilton Tower
How is null data specified?
N/A
What does null data indicate?
No data results in error
|
|
<FromAddr>
|
Alphanumeric
|
46
|
Field Description:
Free format text of ''from'' address
Format (x-alpha/numeric):
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Special Format:
Left justified, blank filled.
Examples:
10 Hamilton Tower
How is null data specified?
N/A
What does null data indicate?
No data results in error.
|
|
<InvNum>
|
Alphanumeric
|
9
|
Field Description:
Invoice number
Format (x-alpha/numeric):
xxxxxxxxx
Special Format:
Left justified, blank filled.
Examples:
MM867
How is null data specified?
N/A
What does null data indicate?
No data results in error.
|
|
<DeptBillingCode>
|
Alphanumeric
|
14
|
Field Description:
Dept/Billing code
Format (x-alpha/numeric):
xxxxxxxxxxxxxx
Special Format:
Left justified, blank filled.
Examples:
BN876955
How is null data specified?
N/A
What does null data indicate?
No data results in error.
|
|
+ <MsgTextLine>
|
Array
|
n/a
|
|
|
<Text>
|
Alphanumeric
|
60
|
Field Description:
Message Line
Format (x-alpha/numeric):
xxxxxxx...
Special Format:
Left justified, blank filled.
Examples:
Any text
How is null data specified?
N/A
What does null data indicate?
No data results in error
|
|
|
|
|
|
+ <MCOTicketData>
|
DPM1 1.0
|
|
|
|
<TktIssueInd>
|
Alpha
|
1
|
Field Description:
Ticket Issue Indicator
Format (a-alpha):
a
Special Format:
N/A
Possible Values (List):
P - PTA (Pre-paid ticket advice)
T - TOD (Ticket on Departure)
O - OTH (Other)
How is null data specified?
N/A
What does null data indicate?
No data results in error
|
|
|
|
+ <MCOIssue>
|
DPM2 1.0
|
|
|
|
<IssueInd>
|
Alpha
|
1
|
Field Description:
MCO Issue Indicator. This will indicate whether the MCO is to be issued (Y), or stored for issue at a later time (N).
Format (a-alpha):
a
Special Format:
N/A
Possible Values (List):
Y = Yes, issue the MCO
N = No, store only
How is null data specified?
N/A
What does null data indicate?
No data results in error
|
|
|
|
+ <MCOTicketing>
|
DPMA 1.0
|
|
|
|
<TO>
|
Character
|
3
|
Field Description:
Tour Operator - name of honoring carrier or operator.
Format (c-character):
ccc
Special Format:
Left justified, blank filled
Examples:
BA
UA
How is null data specified?
N/A
What does null data indicate?
No data results in error
|
|
<AT>
|
Character
|
5
|
Field Description:
Location of honoring carrier or operator.
Format (c-character):
ccccc
Special Format:
Left justified, blank filled
Examples:
LON
ORD
How is null data specified?
N/A
What does null data indicate?
No data results in error
|
|
<RelatedTktNum>
|
Alphanumeric
|
15
|
Field Description:
Airline form and serial number of any accountable documents issued in connection with the MCO.
Format (n-numeric):
nnnnnnnnnnnnnnn
Special Format:
Left justified, blank filled
Examples:
0015460001234
0167780006755
How is null data specified?
N/A
What does null data indicate?
No data results in error
|
|
|
|
+ <MCOReasonCode>
|
DPMC 1.0
|
|
|
|
<ReasonCode>
|
Alphanumeric
|
1
|
Field Description:
MCO Reason Code
Format (x-alpha/numeric):
x
Possible Values (List):
A - Air transportation
B - Surface transportation
C - Bag shipped as cargo
D - Land arrgs for it
E - Car hire
F - Sleeper / berth
G - Up-grading
H - Under collections
I - Taxes/fees/charges
J - Deposits down payments
K - Refundable Balances
L - Hotel accommodations
M - Sundry charges
N - Cancellation fee
O - Other
P thru Z - airline specific
1 thru 9 - market specific
How is null data specified?
N/A
What does null data indicate?
No data results in error
|
|
|
|
+ <MCOEndorsementData>
|
DPME 1.0
|
|
|
|
<Endorsement>
|
Character
|
54
|
Field Description:
Endorsement data. This is data that can be generated by the system, or entered by the user with functional entries.
Format (c-character):
ccccccccccccccccc.....
Special Format:
Left justified, blank filled
Possible Values:
VALID ONLY ON LH UA
NON ENDORSABLE-NON REF
(this is free form text)
How is null data specified?
N/A
What does null data indicate?
No data results in error
|
|
|
|
+ <PTATODFee>
|
DPMG 1.0
|
|
|
|
<FeeAppliesToInd>
|
Alpha
|
1
|
Field Description:
Indicates if PTA/TOD (Prepaid Ticket Advice / Ticket on Demand) fee is for the entire MCO or is per person
Format (a-alpha):
a
Special Format:
Left justified, blank filled
Possible Values (List):
M - fee is per MCO
P - fee is per Person
Blank - no fee defined for PTA/TOD
How is null data specified?
N/A
What does null data indicate?
No data and results in error
|
|
<FeeTypeInd>
|
Alpha
|
1
|
Field Description:
Indicates if PTA/TOD fee is the actual amount or is a percentage value of the MCO.
Format (a-alpha):
a
Special Format:
Left justified, blank filled
Possible Values (List):
A - value is actual amount
P - value is a percentage of MCO
Blank - no fee defined for MCO
How is null data specified?
N/A
What does null data indicate?
No data results in error
|
|
<FeeValue>
|
Character
|
11
|
Field Description:
Amount of the PTA/TOD fee. This is a fee charged by the airline for issuing the Pre-paid Ticket Advice or Ticket on Demand.
Format (c-character):
ccccccccccc
Special Format:
Right justified, zero filled
Field can contain a decimal point
Examples:
2.50
4.5
100
How is null data specified?
N/A
What does null data indicate?
No data results in error
|
|
|
|
+ <MCONumber>
|
DPMN 2.0
|
|
|
|
<Num>
|
Numeric
|
2
|
Field Description:
MCO Number. This is the number of the MCO that is being updated / issued.
Format (n-numeric):
nn
Special Format:
Right justified, zero filled
Possible Values (Range):
01 - 99
How is null data specified?
N/A
What does null data indicate?
No data results in error
|
|
|
|
+ <MCOMainData>
|
DPMO 2.0
|
|
|
|
<PsgrName>
|
Character
|
57
|
Field Description:
Passenger name
Format (c-character):
ccccccccccccccccccccccccccccccccccccccccccccccccccccccccc
Special Format:
Left justified, blank filled
Examples:
Hanson/Eric
Knight-Jones/Laura
How is null data specified?
N/A
What does null data indicate?
No data results in error
|
|
<TourOperator>
|
Character
|
59
|
Field Description:
Tour Operator - name of honoring carrier or operator.
Format (c-character):
ccccccccccccccccccccccccccccccccccccccccccccccccccccccccccc
Special Format:
Left justified, blank filled
Examples:
United Airlines
British Airways P.L.C.
How is null data specified?
N/A
What does null data indicate?
No data results in error
|
|
<Location>
|
Character
|
59
|
Field Description:
Location of honoring carrier or operator.
Format (c-character):
ccccccccccccccccccccccccccccccccccccccccccccccccccccccccccc
Special Format:
Left justified, blank filled
Examples:
Chicago / O Hare
London / Heath
How is null data specified?
N/A
What does null data indicate?
No data results in error
|
|
<ValidFor>
|
Character
|
58
|
Field Description:
Type of service or purpose for which the MCO is issued.
Format (c-character):
cccccccccccccccccccccccccccccccccccccccccccccccccccccccccc
Special Format:
Left justified, blank filled
Examples:
Air Transportation
How is null data specified?
N/A
What does null data indicate?
No data results in error
|
|
<RelatedTktNum>
|
Alphanumeric
|
15
|
Field Description:
Airline form and serial number of any accountable documents issued in connection with the MCO.
Format (x-alphanumeric):
xxxxxxxxxxxxxxx
Special Format:
Left justified, blank filled
Examples:
0015460001234
0167780006755
How is null data specified?
N/A
What does null data indicate?
No data indicates data not available
|
|
<Commission>
|
Character
|
8
|
Field Description:
Commission. Can be expressed in actual amount or percentage.
Format (c-character):
cccccccc
Special Format:
Right justified, zero filled
Field can include a decimal
If field begins with an A, the following numeric will be used as an amount. If no A is specified the numeric will be used as a percentage.
Examples:
9.25
7
A9.00
How is null data specified?
N/A
What does null data indicate?
No data results in error
|
|
<MCOTax>
|
Character
|
8
|
Field Description:
Amount of taxes or fees levied by the local government for the issuance of the MCO in the country where the MCO is issued.
Format (c-character):
cccccccc
Special Format:
Right justified, zero filled
Field can contain a decimal point
Examples:
15.00
220
How is null data specified?
N/A
What does null data indicate?
No data indicates no data available
|
|
<TaxCode>
|
Alphanumeric
|
3
|
Field Description:
Applicable ISO country code related to tax on MCO.
Format (x-alpha/numeric):
xxx
Special Format:
Left justified, blank filled
Examples:
US
XA
How is null data specified?
N/A
What does null data indicate?
No data indicates no data available
|
|
<MCOAmt>
|
Character
|
12
|
Field Description:
Base amount for MCO.
Format (c-character):
cccccccccccc
Special Format:
Right justified, zero filled
Field can contain a decimal point
Examples:
150.00
5000
How is null data specified?
N/A
What does null data indicate?
No data results in error
|
|
<Currency>
|
Alphanumeric
|
3
|
Field Description:
Currency code for amount.
Format (x-alpha/numeric):
xxx
Special Format:
Left justified, blank filled
Examples:
USD
GBP
How is null data specified?
N/A
What does null data indicate?
No data results in error
|
|
<EquivFarePaid>
|
Character
|
12
|
Field Description:
Exchange value of the currency actually collected.
Format (c-character):
cccccccccccc
Special Format:
Right justified, zero filled
Field can contain a decimal point
Examples:
200.00
4000
How is null data specified?
N/A
What does null data indicate?
No data indicates no data available
|
|
<EquivCurrency>
|
Alphanumeric
|
3
|
Field Description:
Currency code of equivalency fare paid.
Format (x-alpha/numeric):
xxx
Special Format:
Left justified, blank filled
Examples:
SEK
GBP
How is null data specified?
N/A
What does null data indicate?
No data indicates no data available
|
|
<BankSellRate>
|
Character
|
14
|
Field Description:
Pertinent banker's exchange rates used to calculate the amount(s) to be collected in the currency of payment.
Format (c-character):
cccccccccccccc
Special Format:
Right justified, zero filled
Field can contain a decimal point
Examples:
0.625917
0.6106497
How is null data specified?
N/A
What does null data indicate?
No data indicates no data available
|
|
<PlatingCarrier>
|
Alphanumeric
|
3
|
Field Description:
2 character code of plating carrier.
Format (x-alpha/numeric):
xxx
Special Format:
Left justified, blank filled
Examples:
UA
BA
How is null data specified?
N/A
What does null data indicate?
No data results in error
|
|
|
|
+ <MCORemarks>
|
DPMR 1.0
|
|
|
|
<Rmk>
|
Character
|
46
|
Field Description:
Remarks. The remarks field can contain a breakdown of the fare construction, as well as free form text that is entered by the agent.
Format (c-character):
cccccccccccccccccccccccccccccccccccccccccccccc
Special Format:
Left justified, blank filled
Examples:
CHI UA DEN 828.84YUAS USD 828.84 ENDZP1.90ORDXF
How is null data specified?
N/A
What does null data indicate?
No data results in error
|
|
+ <AdditionalRmkAry>
|
Array
|
n/a
|
|
|
<AdditionalRmk>
|
Character
|
80
|
Field Description:
Additional remarks.
Format (c-character):
cccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccc
Special Format:
Left justified, blank filled
Examples:
CHI UA DEN 828.84YUAS USD 828.84 ENDZP1.90ORDXF
How is null data specified?
N/A
What does null data indicate?
No data results in error
|
|
|
|
|
|
+ <MCOTourCode>
|
DPMU 1.0
|
|
|
|
<TourCode>
|
Character
|
15
|
Field Description:
Tour code.
Format (c-character):
cccccccccccccc............
Special Format:
Left justified, blank filled
Possible Values (List or Range):
United Airlines
British Airways
How is null data specified?
N/A
What does null data indicate?
No data results in error
|
|
|
|
+ <CreditCardFOP>
|
DPP0 1.0
|
|
|
|
<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
|
|
<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
|
|
<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
|
|
<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
|
|
<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
|
|
<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
|
|
<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
|
|
<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)
8 - OB Fee Charged
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
8 - Ob Fee charged
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 2.0
|
|
|
|
<FOPID>
|
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
16 - Special Government Transportation Request
17 - Multiple Receivable
18 - Certificate (CERT for UA)
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.
|
|
<PmtCrncy>
|
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
|
|
+ <AddlDataIDAry>
|
Array
|
n/a
|
|
|
+ <AddlDataID>
|
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
6 - Certificate number
8 - OB Fee Charged
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
|
|
|
|
|
|
|
|
+ <TicketingControl>
|
DPTK 3.0
|
|
|
|
<TransType>
|
Alphanumeric
|
2
|
Description of Field:
Type of ticketing message
Format (x-alpha/numeric):
xx
Possible Values (List):
TK - Initial ticketing entry
MR - Multiple receivable request/response
FC - Fare construction request/response (1V only)
ET - Electronic ticket failed request/response
OK - Ticket issued response
ME - Form of payment error response
CO - Fare changed request/response T:CONTINUE (1V only)
FX - DFX screens request/response (1V only)
CC - Credit Card Restriction Override (F|OK - 1V only)
DB - Detailed Billing Data for Credit Cards (1G only)
MO - Misc. Charge Order Request
MA - MCO TKPMCO MCOA data
EE - Itinerary is eligible to issue Eticket
Not yet implemented:
EX - Exchange request/response
ER - Refund request/response
NM - $NME screen request/response (1V only)
UC - Undecodable city code request/response (1V only)
TA - Tax breakdown screen request/response (1V only)
ZP - ZP Tax breakdown screen request/response (1V only)
How is null data specified?
No data results in error
What does null data indicate?
No data results in error
|
|
|
|
|
|
+ <ElectronicTicketDataMods>
|
4034 1.0
|
|
+ <TicketNum>
|
DPDE 1.0
|
|
|
|
<PlatingCarrier>
|
Alphanumeric
|
3
|
Description of Field:
Plating Carrier Code
Format (x-alpha/numeric):
xxx
Special Format:
Left justified, blank filled.
Examples:
UA (blank)
/*A
How is null data specified?
N/A
What does null data indicate?
No data results in error.
|
|
<TkNum>
|
Numeric
|
13
|
Description of Field:
Ticket Number
Format (n-numeric):
nnnnnnnnnnnnn
Special Format:
Right justified, zero filled.
Examples:
0167246466608
How is null data specified?
Blank if not specified.
What does null data indicate?
No data results in error
|
|
<FreqFlyerNum>
|
Alphanumeric
|
20
|
Description of Field:
Frequent Flyer Number
Format (x-alpha/numeric):
xxxxxxxxxxxxxxxxxxxx
Special Format:
Left justified, blank filled.
Examples:
FF00123456(space)
FF001234567
How is null data specified?
Blank, if not specified.
What does null data indicate?
No data results in error.
|
|
<CCNum>
|
Alphanumeric
|
20
|
Description of Field:
Credit Card Number
Format (x-alpha/numeric):
xxxxxxxxxxxxxxxxxxxx
Special Format:
Blank filled.
Examples:
00000371019534732004
How is null data specified?
N/A
What does null data indicate?
No data results in error
|
|
<TelNum>
|
Alphanumeric
|
20
|
Description of Field:
Telephone number,
Format (x-alpha/numeric):
xxxxxxxxxxxxxxxxxxxx
Special Format:
Left justified, blank filled.
Examples:
303-5551212
How is null data specified?
N/A
What does null data indicate?
No data results in error
|
|
<Name>
|
Alphanumeric
|
33
|
Description of Field:
Name
Format (x-alpha/numeric):
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Special Format:
Left justified, blank filled.
Examples:
1Keith/Peter
How is null data specified?
N/A
What does null data indicate?
No data results in error
|
|
<Flt>
|
Alphanumeric
|
4
|
Description of Field:
Flight Number
Format (x-alpha/numeric):
xxxx
Special Format:
Left justified, blank filled.
Examples:
UA12
How is null data specified?
N/A
What does null data indicate?
No data results in error
|
|
<Dt>
|
Alphanumeric
|
8
|
Description of Field:
Date
Format (x-alpha/numeric):
xxxxxxxx
Special Format:
YYYYMMDD
Examples:
20030525
20021203
How is null data specified?
N/A
What does null data indicate?
No data results in error
|
|
<Origin>
|
Alpha
|
5
|
Description of Field:
Origin City Code
Format (a-alpha):
aaaaa
Special Format:
Left justified, blank filled.
Examples:
DEN (2 spaces)
How is null data specified?
N/A
What does null data indicate?
No data results in error
|
|
<End>
|
Alpha
|
5
|
Description of Field:
Destination City Code
Format (a-alpha):
aaaaa
Special Format:
Left justified, blank filled.
Examples:
ORD (2 spaces)
How is null data specified?
N/A
What does null data indicate?
No data results in error
|
|
|
|
|
|
<TicketNumbersMods>
|
4036 1.0
|
|
+ <EnableStoredFareMods>
|
4044 1.0
|
|
+ <FareNumInfo>
|
DPFI 1.0
|
|
|
|
+ <FareNumAry>
|
Array
|
n/a
|
|
|
<FareNum>
|
Numeric
|
3
|
Field Description:
Fare number of the item to which the following KLRs relate.
Format (n-numeric):
nnn
Special Format:
Right justified, zero filled.
Examples:
001
How is null data specified?
N/A
What does null data indicate?
No data results in error.
|
|
|
|
|
|
|
|
+ <PaymentCalculatorMods>
|
4046 1.0
|
|
+ <FareNumInfo>
|
DPFI 1.0
|
|
|
|
+ <FareNumAry>
|
Array
|
n/a
|
|
|
<FareNum>
|
Numeric
|
3
|
Field Description:
Fare number of the item to which the following KLRs relate.
Format (n-numeric):
nnn
Special Format:
Right justified, zero filled.
Examples:
001
How is null data specified?
N/A
What does null data indicate?
No data results in error.
|
|
|
|
|
|
|
|
|
|