|
+ Requests
|
|
+ <InsertSegAfterMods>
|
1020 5.0
|
|
|
|
|
1020 - Segment Insert After Request
Version: 05.00
|
|
<SegNum>
|
Numeric
|
2
|
Determines insertion point for next segment
|
|
|
|
|
+ <AirSegCancelMods>
|
1040 5.0
|
|
|
|
|
1040 - Segment Cancel Request
Version: 05.00
|
CancelBlkCnt
Structured data only.
Not in XML.
|
Numeric
|
2
|
Number of cancellations this transaction. This is the total number of cancellation requests contained in this transaction. By definition this can range from 1 to the number of actual segments in the itinerary.
|
|
+ <CancelBlkAry>
|
Array
|
n/a
|
|
|
+ <CancelBlk>
|
FieldSet
|
n/a
|
|
|
<ReqNum>
|
Numeric
|
2
|
Will be echoed back in response. Right justified, zero filled.
|
|
<SegNum>
|
Numeric
|
2
|
PNR segment number to cancel. If this field contains the characters FF then the entire itinerary (air, car and hotel, SSRs and seats) will be canceled.
|
|
|
|
|
|
|
|
|
+ <AirSegSellMods>
|
1060 5.0
|
|
|
|
|
1060 - Air Segment Sell Request
Version: 05.00
|
SellBlkCnt
Structured data only.
Not in XML.
|
Numeric
|
2
|
The total number of airline segments to be sold in the itinerary of a single PNR/BF. The maximum value for this field is 8.
|
|
<OutputMsg>
|
Alpha
|
1
|
Y=Return output messages
N=Do not return output messages
|
|
+ <SellBlkAry>
|
Array
|
n/a
|
|
|
+ <SellBlk>
|
FieldSet
|
n/a
|
|
|
<ReqNum>
|
Numeric
|
2
|
Will be echoed back in response. Right justified, zero filled.
|
|
<AirV>
|
Alpha
|
3
|
Owning airline of the flight number, left justified.
|
|
<FltNum>
|
Numeric
|
4
|
Right justified, zero filled
|
|
<BIC>
|
Alpha
|
2
|
Booking code left justified. The booking code for this field must come from a fare quote transaction (Super $BB, Flight Specific or Normal $BB). This means that a booking cannot occur until a fare quote has been performed.
|
|
<Dt>
|
Numeric
|
8
|
Date of flight in YYYYMMDD format
|
|
<StartAirp>
|
Alpha
|
5
|
Left justified
|
|
<EndAirp>
|
Alpha
|
5
|
Left justified
|
|
<ReqType>
|
Alpha
|
2
|
NN=Need (used on regular sell)
LL=Waitlist
NO=Open segment
|
|
<SeatCnt>
|
Numeric
|
1
|
A minimum value of 1 and a maximum value of 9
|
|
<Filler>
|
Numeric
|
2
|
Spare byte - reserved for passenger expansion
|
|
<LinkAirVInd>
|
Alpha
|
1
|
Y=This segment connects to next
N=This segment does not connect
|
|
|
|
|
|
|
|
|
+ <PrimaryBuildMods>
|
2100 5.0
|
|
|
|
|
|
+ <ItemAry>
|
Array
|
n/a
|
|
|
+ <Item>
|
FieldSet
|
n/a
|
|
2100 - PNR/BF Primary Build/Change Request
Version: 05.00
Start Definition of Optional Data Block Indicators. The End Mark must follow the last optional field.
Definition of Data Block Indicators
IndicatorDescriptionIndicatorDescription
JProfile Move
NNamePPhone
TTicketingWStreet Address
|
|
<BlkInd>
|
Alphanumeric
|
2
|
J=Profile Move Data Block
T=Indicates modify Ticketing field
N=Indicates modify of Names
P=Indicates modify Phone field
W=Indicates Address field
E=Indicates End mark.
|
|
+ <BlkIndNQual>
[Qualified By: BlkInd of N]
|
FieldSet
|
n/a
|
|
BlkLen
Structured data only.
Not in XML.
|
Numeric
|
4
|
Actual length of data block that follows
|
|
<NameEditType>
|
Alphanumeric
|
1
|
Indicates type of name field edit:
A=Add names. Adding names is only valid for initial PNR Build
C=Change existing name field
|
NameCnt
Structured data only.
Not in XML.
|
Numeric
|
1
|
Number of people in this Name Element. Must be a num ber between 1 and 9 and will determine the number of oc currences of the First Name Item field (see below).
|
|
<LNameID>
|
Numeric
|
1
|
Sequential number identifying last name
|
LNameLen
Structured data only.
Not in XML.
|
Numeric
|
2
|
|
|
<LName>
|
Numeric
|
VL
|
Minimum of 2 and maximum of 55 characters per name field
|
RmkLen
Structured data only.
Not in XML.
|
Numeric
|
2
|
Length of Name Remarks field. If zero, then no Name Re marks exists. If Name Remarks exists then the minimum length is 2 and maximum length is 33
|
|
<Rmk>
|
Numeric
|
VL
|
Actual name remarks
|
|
+ <SubNameAry>
|
Array
|
n/a
|
|
|
+ <SubName>
|
FieldSet
|
n/a
|
|
|
<ID>
|
Numeric
|
1
|
Unique sequential number relative to Last Name Element Number
|
|
<AbsID>
|
Numeric
|
1
|
Unique sequential number identifying Absolute Name
Example:Smith/A/B 1/2
Jones/A/B 3/4
|
FNameLen
Structured data only.
Not in XML.
|
Numeric
|
2
|
Length of first name field. If zero, then no first name ex ists.
|
FreqFlyerCnt
Structured data only.
Not in XML.
|
Numeric
|
2
|
Number of Frequent Traveler numbers. If zero, then no Frequent Traveler numbers exist.
|
|
+ <FreqFlyerAry>
|
Array
|
n/a
|
|
|
+ <FreqFlyer>
|
FieldSet
|
n/a
|
|
|
<AirV>
|
Alpha
|
3
|
The Frequent traveler Vendor and Number can occur mul tiple times depending on the Number Frequent Traveler field.
|
|
|
|
|
|
|
|
|
|
|
|
+ <BlkIndTQual>
[Qualified By: BlkInd of T]
|
FieldSet
|
n/a
|
|
BlkLen
Structured data only.
Not in XML.
|
Numeric
|
4
|
Actual length of data block that follows
|
Len
Structured data only.
Not in XML.
|
Numeric
|
2
|
|
|
<TkFld>
|
Alpha
|
VL
|
Actual ticketing field. The valid ticketing fields are
TL30 = This is used when the customer wants to pick up their ticket 30 minutes before departure at the United Air port Ticket Counter.
TL1159P/DDMMM = This is used when the customer wants to pickup the ticket from a City Ticket Office. Date is defined as DDMMM format.
TAM/DATE/FOP = This is used if customer wants Air lines to mail their tickets. Date is DDMMM format and FOP is valid credit card 2 character code. If TBM is spec ified, then address field must be present in the PNR.
TAM/DATE/SWX. = This is used if the customer wants Airline to Federal Express their tickets using SWIFTIX.
TAU/DATE = This field is used when customer wants to ticket with either a preferred agency or an agency of their choice.
|
|
|
|
+ <BlkIndJQual>
[Qualified By: BlkInd of J]
|
FieldSet
|
n/a
|
|
BlkLen
Structured data only.
Not in XML.
|
Numeric
|
4
|
Actual length of data block that follows
|
|
<MARName1>
|
Alpha
|
4
|
Profile MAR (Master Account Record) name
|
|
<MARName2>
|
Alpha
|
21
|
Profile BAR (Business Account Record) name
|
|
<MARName3>
|
Alpha
|
21
|
Profile PAR (Passenger Account Record) name
|
|
|
|
+ <BlkIndPQual>
[Qualified By: BlkInd of P]
|
FieldSet
|
n/a
|
|
BlkLen
Structured data only.
Not in XML.
|
Numeric
|
4
|
Actual length of data block that follows
|
|
<PhoneEditType>
|
Alphanumeric
|
1
|
Indicates type of phone field edit:
A=Add phone field
D=Delete phone field
C=Change existing phone field
|
|
+ <PhoneEditTypeAQual>
[Qualified By: PhoneEditType of A]
|
FieldSet
|
n/a
|
|
|
<City>
|
Alpha
|
5
|
3-char city code of phone number. The remaining 2 char acters are spares.
|
|
<Locn>
|
Alphanumeric
|
1
|
For non-agencies, the type of phone:
R=Residence (home)
B=Business
A=Agency
For agencies, there are no restrictions.
|
Len
Structured data only.
Not in XML.
|
Numeric
|
2
|
Length of phone field which follows
|
|
<Num>
|
Alpha
|
VL
|
Phone number. The suggested format for a US domestic phone number is /XXX-XXX-XXXX. The first character of this field must be a slash (/). However, the rest of this field is free form (Apollo does not edit the content or for mat) to accommodate a variety of phone formats, e.g., En gland 0793 888454. Other European phone numbers might include an international access code, a country code, a city code, and a number, e.g., Zurich, Switzerland 010 411 258 3250.
|
|
|
|
+ <PhoneEditTypeCQual>
[Qualified By: PhoneEditType of C]
|
FieldSet
|
n/a
|
|
|
<NumPhoneFlds>
|
Numeric
|
2
|
Number of phone field to modify
|
|
<City>
|
Alpha
|
5
|
3-character city code of phone number. The remaining 2 characters are spares.
|
|
<Locn>
|
Alphanumeric
|
1
|
For non-agencies, the type of phone:
R=Residence (home)
B=Business
A=Agency
For agencies, there are no restrictions.
|
Len
Structured data only.
Not in XML.
|
Numeric
|
2
|
Length of phone field which follows
|
|
<Num>
|
Alpha
|
VL
|
Phone number. The suggested format for a US domestic phone number is /XXX-XXX-XXXX. The first charac ter of this field must be a slash (/). However, the rest of this field is free form (Apollo does not edit the content or format) to accommodate a variety of phone formats, e.g., England 0793 888454. Other European phone numbers might include an international access code, a country code, a city code, and a number, e.g., Zurich, Switzerland 010 411 258 3250.
|
|
|
<NumPhoneFlds>
[Qualified By: PhoneEditType of D]
|
Numeric
|
2
|
Number of phone field to delete. Note: numbers must be specified in reverse order.
|
|
|
|
+ <BlkIndWQual>
[Qualified By: BlkInd of W]
|
FieldSet
|
n/a
|
|
BlkLen
Structured data only.
Not in XML.
|
Numeric
|
4
|
Actual length of data block that follows
|
|
<AddrEditType>
|
Alphanumeric
|
1
|
Indicates type of street field edit:
A=Add street address field
D=Delete street address field. No Data required.
C=Change existing street address
|
|
+ <AddrEditTypeACQual>
[Qualified By: AddrEditType of A,C]
|
FieldSet
|
n/a
|
|
Len
Structured data only.
Not in XML.
|
Numeric
|
3
|
|
|
<Addr>
|
Alpha
|
VL
|
This is required if the customer chooses TBM (Ticket By Mail) as ticketing arrangement. Address format should look like this: First & last name @ St address@City State Z/Zip code. additional sub fields can be specified. Sub fields have a minimum length of 1 and a maximum length of 37.
|
|
|
|
|
|
+ <BlkIndEQual>
[Qualified By: BlkInd of E]
|
FieldSet
|
n/a
|
|
BlkLen
Structured data only.
Not in XML.
|
Numeric
|
4
|
Actual length of data block that follows
|
|
<EndMark>
|
Alpha
|
1
|
E=Character to mark the end. If any of the following optional fields are included, this end mark must follow the last optional field.
|
|
|
|
|
|
|
|
|
|
|
+ <PNRBFSecondaryBldChgMods>
|
2110 5.0
|
|
|
|
|
|
+ <ItemAry>
|
Array
|
n/a
|
|
|
+ <Item>
|
FieldSet
|
n/a
|
|
2110 - PNR/BF Secondary Build/Change Request
Version: 05.00
Start Definition of Optional Data Block Indicators. Any of the optional fields shown in the remaining description of the 2130 may be included. The End Mark must follow the last optional field.
Definition of Data Block Indicators
IndicatorDescriptionIndicatorDescription
CCustomer IDDDelivery Address
FForm of PaymentGGeneral Remarks
HAssociated Itin RmksINon Associated Itin Rmks
JProfile MoveKTicketing Remarks
OOSIQQ-Minders
SSSR
XDoc/Invoice RemarksYDue/Paid/Text
Start Definition of Form of Payment (FOP) Fields.
|
|
<DataBlkInd>
|
Alphanumeric
|
2
|
F=Indicates FOP
C=Indicates Customer ID
D=Indicates delivery address Field
O=Indicates OSI Field
S=Indicates SSR Field
K=Indicates Ticket Remarks
G=Indicates General Remarks
H=Indicates Assoc. Itin Remarks
I=Indicates Non-Assoc. Itin Remarks
Q=Indicates Q-minder
X=Indicates modify DOC/Invoice
Y=Indicates modify Due/Paid/Text
E=Indicates End mark
|
|
+ <FOPQual>
[Qualified By: DataBlkInd of F]
|
FieldSet
|
n/a
|
|
DataBlkLen
Structured data only.
Not in XML.
|
Numeric
|
4
|
Actual length of data block that follows
|
|
<EditTypeInd>
|
Alphanumeric
|
1
|
A=Add
D=Delete
C=Change
|
|
+ <AddChgQual>
[Qualified By: EditTypeInd of A,C]
|
FieldSet
|
n/a
|
|
|
<TypeInd>
|
Numeric
|
1
|
Type of FOP block to follow
0=FOP does not exist
1=Variable Length Field
2=Credit Card
|
|
+ <VarLenQual>
[Qualified By: TypeInd of 1]
|
FieldSet
|
n/a
|
|
Len
Structured data only.
Not in XML.
|
Numeric
|
2
|
Length of form of payment field. If zero then no FOP exists.
|
|
|
|
+ <CCQual>
[Qualified By: TypeInd of 2]
|
FieldSet
|
n/a
|
|
|
<CC>
|
Alpha
|
2
|
Credit card format is as follows:
A 2-byte credit card type:
|
|
<ExpDt>
|
Numeric
|
4
|
Credit Card Expiration Date format: MMYY
|
|
<ExtTxt>
|
Numeric
|
8
|
Freeform text - depending on credit card
|
AcctLen
Structured data only.
Not in XML.
|
Numeric
|
2
|
Length of credit card number to follow
|
|
<Acct>
|
Numeric
|
VL
|
Credit card number
|
|
|
|
|
|
|
|
+ <CustIDQual>
[Qualified By: DataBlkInd of C]
|
FieldSet
|
n/a
|
|
DataBlkLen
Structured data only.
Not in XML.
|
Numeric
|
4
|
Actual length of data block that follows
|
|
<EditTypeInd>
|
Alphanumeric
|
1
|
Indicates type of Customer ID edit:
A=Add Customer ID field
D=Delete Customer ID field
C=Modify existing Customer ID
|
|
+ <AddChgQual>
[Qualified By: EditTypeInd of A,C]
|
FieldSet
|
n/a
|
|
Len
Structured data only.
Not in XML.
|
Numeric
|
2
|
Max length = 43
|
|
|
|
|
|
+ <DeliveryAddrQual>
[Qualified By: DataBlkInd of D]
|
FieldSet
|
n/a
|
|
DataBlkLen
Structured data only.
Not in XML.
|
Numeric
|
4
|
Actual length of data block that follows
|
|
<EditTypeInd>
|
Alphanumeric
|
1
|
Indicates type of delivery Address field edit:
A=Add delivery address field
D=Delete delivery address field
C=Modify existing delivery address
|
|
+ <AddChgQual>
[Qualified By: EditTypeInd of A,C]
|
FieldSet
|
n/a
|
|
Len
Structured data only.
Not in XML.
|
Numeric
|
3
|
|
|
<DeliveryAddr>
|
Alpha
|
VL
|
Address format should look like this: First & last name @ St address@City State Z/Zip code. additional sub fields can be specified. Sub fields have a minimum length of 1 and a maximum length of 37.
|
|
|
|
|
|
+ <TkRmkQual>
[Qualified By: DataBlkInd of K]
|
FieldSet
|
n/a
|
|
DataBlkLen
Structured data only.
Not in XML.
|
Numeric
|
4
|
Actual length of data block that follows
|
|
<EditTypeInd>
|
Alphanumeric
|
1
|
A=Add new Ticketing Remark
D=Delete Ticketing Remark
C=Modify Ticketing Remark
|
|
+ <AddQual>
[Qualified By: EditTypeInd of A]
|
FieldSet
|
n/a
|
|
Len
Structured data only.
Not in XML.
|
Numeric
|
2
|
|
|
|
<DelNumQual>
[Qualified By: EditTypeInd of D]
|
Numeric
|
2
|
|
|
+ <ChgQual>
[Qualified By: EditTypeInd of C]
|
FieldSet
|
n/a
|
|
Len
Structured data only.
Not in XML.
|
Numeric
|
2
|
|
|
|
|
|
|
+ <GenlRmkQual>
[Qualified By: DataBlkInd of G]
|
FieldSet
|
n/a
|
|
DataBlkLen
Structured data only.
Not in XML.
|
Numeric
|
4
|
Actual length of data block that follows
|
|
<EditTypeInd>
|
Alphanumeric
|
1
|
Indicates type of General Remarks field edit:
A=Add General Remarks field
D=Delete General Remarks field
C=Modify existing General Remarks field
Only General Remarks fields with the PA qualifier can be deleted or changed.
|
|
+ <AddQual>
[Qualified By: EditTypeInd of A]
|
FieldSet
|
n/a
|
|
Len
Structured data only.
Not in XML.
|
Numeric
|
2
|
Length of General Remarks field that follows. Range of 2-64.
|
|
<Rmk>
|
Alpha
|
VL
|
Free form contents of the General Remarks field
|
|
|
<DelNumQual>
[Qualified By: EditTypeInd of D]
|
Alpha
|
2
|
Number of General Remarks field to delete
|
|
+ <ChgQual>
[Qualified By: EditTypeInd of C]
|
FieldSet
|
n/a
|
|
|
<Num>
|
Alpha
|
2
|
Number of General Remarks field to modify
|
Len
Structured data only.
Not in XML.
|
Numeric
|
2
|
Length of General Remarks field which follows
|
|
<Rmk>
|
Alpha
|
VL
|
Free form contents of the General Remarks field
|
|
|
|
|
|
+ <OSIQual>
[Qualified By: DataBlkInd of O]
|
FieldSet
|
n/a
|
|
DataBlkLen
Structured data only.
Not in XML.
|
Numeric
|
4
|
Actual length of data block that follows
|
|
<EditTypeInd>
|
Alphanumeric
|
1
|
A=Add new OSI
D=Delete existing OSI
C=Modify existing OSI
|
|
+ <AddQual>
[Qualified By: EditTypeInd of A]
|
FieldSet
|
n/a
|
|
|
<OSIV>
|
Alpha
|
3
|
Airline Code or YY for multiple airlines
|
Len
Structured data only.
Not in XML.
|
Numeric
|
2
|
Length of OSI field
|
|
<OSI>
|
Alpha
|
VL
|
OSI message anywhere from 1 to 69 characters
|
|
|
<DelNumQual>
[Qualified By: EditTypeInd of D]
|
Alpha
|
3
|
GFAX number of OSI item to be deleted
|
|
+ <ChgQual>
[Qualified By: EditTypeInd of C]
|
FieldSet
|
n/a
|
|
|
<OSINum>
|
Alpha
|
3
|
GFAX number of OSI item to be modified
|
|
<OSIV>
|
Alpha
|
3
|
Airline Code or YY for multiple airlines
|
Len
Structured data only.
Not in XML.
|
Numeric
|
2
|
Length of OSI field
|
|
<OSI>
|
Alpha
|
VL
|
OSI message anywhere from 1 to 69 characters
|
|
|
|
|
|
+ <SSRQual>
[Qualified By: DataBlkInd of S]
|
FieldSet
|
n/a
|
|
DataBlkLen
Structured data only.
Not in XML.
|
Numeric
|
4
|
Actual length of data block that follows
|
|
<EditTypeInd>
|
Alphanumeric
|
1
|
A=Add new SSR
D=Delete existing SSR
|
|
+ <AddQual>
[Qualified By: EditTypeInd of A]
|
FieldSet
|
n/a
|
|
|
<SSRCode>
|
Numeric
|
4
|
Refer to the table of SSR codes at the end of this section.
|
Comment: The SSR applies to all names if the next three fields contain blanks.
|
|
<LNameNum>
|
Numeric
|
1
|
Sequential number identifying last name
|
|
<PsgrNum>
|
Numeric
|
1
|
Unique sequential number identifying passengers relative to Last Name Element Number
|
|
<AbsNameNum>
|
Numeric
|
1
|
Unique sequential number identifying Absolute Name
Example:Smith/A/B 1/2
Jones/A/B 3/4
|
Comment: The SSR applies to all flights if the following flight details contain blanks.
|
|
<FltNum>
|
Numeric
|
4
|
|
|
<AirV>
|
Alpha
|
3
|
Left justified
|
|
<Dt>
|
Alpha
|
8
|
Date in YYYYMMDD format
|
|
<BIC>
|
Alpha
|
2
|
Left justified
|
|
<StartAirp>
|
Alpha
|
5
|
Airport Code
|
|
<EndAirp>
|
Alpha
|
5
|
Airport Code
|
Len
Structured data only.
Not in XML.
|
Numeric
|
2
|
|
|
<Txt>
|
Alpha
|
VL
|
Freeform information, maximum of 24 bytes
|
|
|
<DelNumQual>
[Qualified By: EditTypeInd of D]
|
Alpha
|
3
|
GFAX (General Facts) number of SSR item to be deleted
|
|
|
|
+ <AssocRmkQual>
[Qualified By: DataBlkInd of H]
|
FieldSet
|
n/a
|
|
DataBlkLen
Structured data only.
Not in XML.
|
Numeric
|
4
|
Actual length of data block that follows
|
|
<TransTypeInd>
|
Alphanumeric
|
1
|
Indicates which type of association follows - followed by type of change to remark
A=Air
C=Car (Car Master only)
H=Hotel (Room Master only)
|
|
+ <AirQual>
[Qualified By: TransTypeInd of A]
|
FieldSet
|
n/a
|
|
|
<StartDt>
|
Alpha
|
8
|
Date in YYYYMMDD format
|
|
<AirV>
|
Alpha
|
3
|
Left justified
|
|
<StartAirp>
|
Alpha
|
5
|
Airport Code
|
|
<EndAirp>
|
Alpha
|
5
|
Airport Code
|
|
<OpSuf>
|
Numeric
|
1
|
Use the CDATA structure to include a character blank.
|
|
<BIC>
|
Alpha
|
2
|
Left justified
|
|
|
|
+ <CarQual>
[Qualified By: TransTypeInd of C]
|
FieldSet
|
n/a
|
|
|
<StartDt>
|
Alpha
|
8
|
Date in YYYYMMDD format
|
|
<Vnd>
|
Alpha
|
3
|
Left justified
|
|
<Airp>
|
Alpha
|
5
|
Airport Code where car is rented
|
|
<Type>
|
Alpha
|
4
|
Type of car
|
|
|
|
+ <HtlQual>
[Qualified By: TransTypeInd of H]
|
FieldSet
|
n/a
|
|
|
<StartDt>
|
Alpha
|
8
|
Date in YYYYMMDD format
|
|
<Vnd>
|
Alpha
|
3
|
Left justified
|
|
<Airp>
|
Alpha
|
5
|
Airport Code designating city where hotel is
|
|
<PropNum>
|
Numeric
|
5
|
Unique property number
|
|
<RateCode>
|
Alpha
|
7
|
Type or room booked
|
|
|
|
<ModifyTypeInd>
|
Alphanumeric
|
1
|
Type of change to follow
A=Add new Itinerary Remark
D=Delete Itinerary Remark
C=Change Itinerary Remark
|
|
+ <AddQual>
[Qualified By: ModifyTypeInd of A]
|
FieldSet
|
n/a
|
|
ADD - Associated Itinerary Remarks
|
RmkCnt
Structured data only.
Not in XML.
|
Alpha
|
1
|
|
|
+ <RmkAry>
|
Array
|
n/a
|
|
|
+ <RmkInfo>
|
FieldSet
|
n/a
|
|
Len
Structured data only.
Not in XML.
|
Numeric
|
2
|
Range = 2-65 characters
|
|
<Rmk>
|
Alpha
|
VL
|
Itinerary Remarks text
|
|
|
|
|
|
|
|
+ <DelQual>
[Qualified By: ModifyTypeInd of D]
|
FieldSet
|
n/a
|
|
Change - Associated Itinerary Remarks
|
RmkCnt
Structured data only.
Not in XML.
|
Alpha
|
1
|
|
|
|
|
+ <ChgQual>
[Qualified By: ModifyTypeInd of C]
|
FieldSet
|
n/a
|
|
RmkCnt
Structured data only.
Not in XML.
|
Alpha
|
1
|
|
|
+ <RmkAry>
|
Array
|
n/a
|
|
|
+ <RmkInfo>
|
FieldSet
|
n/a
|
|
DELETE - Associated Itinerary Remarks
|
Len
Structured data only.
Not in XML.
|
Numeric
|
2
|
|
|
|
|
|
|
|
|
|
|
+ <NonAssocRmkInd>
[Qualified By: DataBlkInd of I]
|
FieldSet
|
n/a
|
|
DataBlkLen
Structured data only.
Not in XML.
|
Numeric
|
4
|
Actual length of data block that follows
|
|
<EditTypeInd>
|
Alphanumeric
|
1
|
A=Add new Itinerary Remark
D=Delete Itinerary Remark
C=Modify Itinerary Remark
|
|
+ <AddQual>
[Qualified By: EditTypeInd of A]
|
FieldSet
|
n/a
|
|
Len
Structured data only.
Not in XML.
|
Numeric
|
2
|
Range = 2-65 characters
|
|
<Rmk>
|
Alpha
|
VL
|
Itinerary Remarks text
|
|
|
<ItemNum>
[Qualified By: EditTypeInd of D]
|
Alpha
|
2
|
|
|
+ <ChgQual>
[Qualified By: EditTypeInd of C]
|
FieldSet
|
n/a
|
|
Len
Structured data only.
Not in XML.
|
Numeric
|
2
|
|
|
|
|
|
|
+ <QMinderQual>
[Qualified By: DataBlkInd of Q]
|
FieldSet
|
n/a
|
|
DataBlkLen
Structured data only.
Not in XML.
|
Numeric
|
4
|
Actual length of data block that follows
|
|
<EditTypeInd>
|
Alphanumeric
|
1
|
A=Add new Ticketing Remark
D=Delete Ticketing Remark
C=Modify Ticketing Remark
|
|
+ <AddQual>
[Qualified By: EditTypeInd of A]
|
FieldSet
|
n/a
|
|
|
<PCC>
|
Alpha
|
4
|
Right justified, zero filled
|
Len
Structured data only.
Not in XML.
|
Numeric
|
2
|
Range = 2-65 characters
|
|
<QMinder>
|
Alpha
|
VL
|
Q-Minder text
|
|
|
<DelNumQual>
[Qualified By: EditTypeInd of D]
|
Alpha
|
2
|
|
|
+ <ChgQual>
[Qualified By: EditTypeInd of C]
|
FieldSet
|
n/a
|
|
|
<PCC>
|
Alpha
|
4
|
Right justified, zero filled
|
Len
Structured data only.
Not in XML.
|
Numeric
|
2
|
Range = 2-65 characters
|
|
<QMinder>
|
Alpha
|
VL
|
Q-Minder text
|
|
|
|
|
|
+ <DOCInvoiceQual>
[Qualified By: DataBlkInd of X]
|
FieldSet
|
n/a
|
|
DataBlkLen
Structured data only.
Not in XML.
|
Numeric
|
4
|
Actual length of data block that follows
|
|
<EditTypeInd>
|
Alphanumeric
|
1
|
A=Add new Itinerary Remark
D=Delete Itinerary Remark
C=Modify Itinerary Remark
|
|
+ <AddQual>
[Qualified By: EditTypeInd of A]
|
FieldSet
|
n/a
|
|
|
<Keyword>
|
Alpha
|
3
|
Keyword
DYO=design your own
CR=canned remark nos.
AC=agency account & branch details
AR=replace sign on code
FT=accounting free text
FS=fare save
TK=ticket number field
|
Len
Structured data only.
Not in XML.
|
Numeric
|
2
|
Variable length of text to follow
|
|
<Txt>
|
Alpha
|
VL
|
Variable length
|
|
|
<DelNumQual>
[Qualified By: EditTypeInd of D]
|
Alpha
|
2
|
|
|
+ <ChgQual>
[Qualified By: EditTypeInd of C]
|
FieldSet
|
n/a
|
|
|
<Keyword>
|
Alpha
|
3
|
Keyword
DYO=design your own
CR=canned remark nos.
AC=agency account & branch details
AR=replace sign on code
FT=accounting free text
FS=fare save
TK=ticket number field
|
Len
Structured data only.
Not in XML.
|
Numeric
|
2
|
Variable length of text to follow
|
|
<Txt>
|
Alpha
|
VL
|
Variable length
|
|
|
|
|
|
+ <DuePaidTextQual>
[Qualified By: DataBlkInd of Y]
|
FieldSet
|
n/a
|
|
DataBlkLen
Structured data only.
Not in XML.
|
Numeric
|
4
|
Actual length of data block that follows
|
|
<EditTypeInd>
|
Alphanumeric
|
1
|
A=Add new
D=Delete
C=Modify
|
|
+ <AddQual>
[Qualified By: EditTypeInd of A]
|
FieldSet
|
n/a
|
|
|
<Type>
|
Alpha
|
2
|
AS=surface
AX=airtaxi
AT=tour operator
AH=airimp hotel
AC=airimp car
|
|
<DuePaidTxtInd>
|
Alpha
|
1
|
D, P, T
|
|
<Price>
|
Numeric
|
10
|
Due, Paid amount
|
Len
Structured data only.
Not in XML.
|
Numeric
|
2
|
Length of text to follow
|
|
|
<SegNum>
[Qualified By: EditTypeInd of D]
|
Alpha
|
4
|
Uniquely identifies this item
|
|
+ <ChgQual>
[Qualified By: EditTypeInd of C]
|
FieldSet
|
n/a
|
|
|
<SegNum>
|
Alpha
|
4
|
Uniquely identifies this item
|
|
<Type>
|
Alpha
|
2
|
AS=surface
AX=airtaxi
AT=tour operator
AH=airimp hotel
AC=airimp car
|
|
<DuePaidTxtInd>
|
Alpha
|
1
|
D, P, T
|
|
<Price>
|
Numeric
|
10
|
Due, Paid amount
|
Len
Structured data only.
Not in XML.
|
Numeric
|
2
|
Length of text to follow
|
|
|
|
|
|
+ <EndQual>
[Qualified By: DataBlkInd of E]
|
FieldSet
|
n/a
|
|
DataBlkLen
Structured data only.
Not in XML.
|
Numeric
|
4
|
Actual length of data block that follows
|
|
<EndMark>
|
Alpha
|
1
|
E=Character to mark the end. If any of the following optional fields are included, this end mark must follow the last optional field.
|
|
|
|
|
|
|
|
|
|
|
+ <SeatSellMods>
|
3030 5.0
|
|
|
|
|
CnclCnt
Structured data only.
Not in XML.
|
Numeric
|
2
|
Description of Field:
Defines number of occurrences of Definition of a Seat Cancellation
Format (n-numeric):
nn
Examples:
01
How is null data specified?
No data results in error
What does null data indicate?
No data results in error
|
ReqCnt
Structured data only.
Not in XML.
|
Numeric
|
2
|
Description of Field:
Defines number of occurrences of Definition of a Seat Request
Format (n-numeric):
nn
Examples:
01
How is null data specified?
No data results in error
What does null data indicate?
No data results in error
|
ModCnt
Structured data only.
Not in XML.
|
Numeric
|
2
|
Description of Field:
Defines number of occurrences of Definition of a Seat Modify
Format (n-numeric):
nn
Examples:
01
How is null data specified?
No data results in error
What does null data indicate?
No data results in error
|
|
+ <CnclAry>
|
Array
|
n/a
|
|
|
+ <CnclInfo>
|
FieldSet
|
n/a
|
|
|
<ID>
|
Alpha
|
1
|
Description of Field:
Always set to C
Format (a-alpha):
a
Possible Values (List):
C
How is null data specified?
No data results in error
What does null data indicate?
No data results in error
|
|
<Num>
|
Numeric
|
2
|
Description of Field:
This field is user defined and as such does not have to be in a particular order
Format (n-numeric):
nn
Examples:
01
How is null data specified?
No data results in error
What does null data indicate?
No data results in error
|
|
<AirV>
|
Alpha
|
3
|
Description of Field:
Owning airline
Format (a-alpha):
aaa
Special Format:
Left justified, blank filled
Examples:
BAblank
How is null data specified?
No data results in error
What does null data indicate?
No data results in error
|
|
<FltNum>
|
Numeric
|
4
|
Description of Field:
Flight number
Format (n-numeric):
nnnn
Special Format:
Right justified, include leading zeroes
Examples:
0013
How is null data specified?
No data results in error
What does null data indicate?
No data results in error
|
|
<OpSuf>
|
Alphanumeric
|
1
|
Description of Field:
Product reference suffix
Format (x-alpha/numeric):
x
How is null data specified?
Character blanks
What does null data indicate?
Character blanks is standard for field
|
|
<Dt>
|
Alphanumeric
|
8
|
Description of Field:
Departure Date
Format (x-alpha/numeric):
xxxxxxxx
Special Format:
YYYYMMDD
How is null data specified?
No data results in error
What does null data indicate?
No data results in error
|
|
<StartAirp>
|
Alpha
|
5
|
Description of Field:
Boarding Point city code
Format (a-alpha):
aaaaa
Special Format:
Left justified blank filled
Examples:
LHRblankblank
How is null data specified?
No data results in error
What does null data indicate?
No data results in error
|
|
<EndAirp>
|
Alpha
|
5
|
Description of Field:
Off city
Format (a-alpha):
aaaaa
Special Format:
Left justified blank filled
Examples:
LHRblankblank
How is null data specified?
No data results in error
What does null data indicate?
No data results in error
|
|
<BIC>
|
Alpha
|
2
|
Description of Field:
Class of service and class modifier
Format (a-alpha):
aa
Special Format:
Left justified blank filled.
Examples:
Jblank
JN
How is null data specified?
No data results in error
What does null data indicate?
No data results in error
|
|
|
|
|
|
+ <ReqAry>
|
Array
|
n/a
|
|
|
+ <ReqInfo>
|
FieldSet
|
n/a
|
|
|
<ID>
|
Alpha
|
1
|
Description of Field:
Always set to R
Format (a-alpha):
a
Possible Values (List):
R
How is null data specified?
No data results in error
What does null data indicate?
No data results in error
|
|
<Num>
|
Numeric
|
2
|
Description of Field:
This record is structured to allow multiple seat requests in a single input. The request number field allows correlation of the results of each request with a response.
Format (n-numeric):
nn
Examples:
03
How is null data specified?
No data results in error
What does null data indicate?
No data results in error
|
|
<AirV>
|
Alpha
|
3
|
Description of Field:
Owning airline
Format (a-alpha):
aaa
Special Format:
Left justified, blank filled
Examples:
BAblank
How is null data specified?
No data results in error
What does null data indicate?
No data results in error
|
|
<FltNum>
|
Numeric
|
4
|
Description of Field:
Flight number
Format (n-numeric):
nnnn
Special Format:
Right justified, include leading zeroes
Examples:
0013
How is null data specified?
No data results in error
What does null data indicate?
No data results in error
|
|
<OpSuf>
|
Alphanumeric
|
1
|
Description of Field:
Product reference suffix
Format (x-alpha/numeric):
x
How is null data specified?
Character blanks
What does null data indicate?
Character blanks is standard for field
|
|
<Dt>
|
Alphanumeric
|
8
|
Description of Field:
Departure Date
Format (x-alpha/numeric):
xxxxxxxx
Special Format:
YYYYMMDD
How is null data specified?
No data results in error
What does null data indicate?
No data results in error
|
|
<StartAirp>
|
Alpha
|
5
|
Description of Field:
Boarding city
Format (a-alpha):
aaaaa
Special Format:
Left justified blank filled
Examples:
LHRblankblank
How is null data specified?
No data results in error
What does null data indicate?
No data results in error
|
|
<EndAirp>
|
Alpha
|
5
|
Description of Field:
Off city
Format (a-alpha):
aaaaa
Special Format:
Left justified blank filled
Examples:
LHRblankblank
How is null data specified?
No data results in error
What does null data indicate?
No data results in error
|
|
<BIC>
|
Alpha
|
2
|
Description of Field:
Class of service and class modifier
Format (a-alpha):
aa
Special Format:
Left justified blank filled.
Examples:
Jblank
JN
How is null data specified?
No data results in error
What does null data indicate?
No data results in error
|
|
<ReqType>
|
Alpha
|
1
|
Description of Field:
Type of seat requested. You cannot request generic and specific seat requests for the same passenger/flight/date
Format (a-alpha):
a
Possible Values (List):
G=Generic. A seat request is generic when the seat request is being made by specifying the characteristics of the seats desired. For example, non-smoking aisle or smoking window is defined as a generic seat request.
S=Specific. A seat request is specific when the seat request is being made by specifying the seat location of the seat(s) desired. For example, 02A or 25K is defined as a specific seat request.
E=Exact. Apollo should return an error code rather than an alternate seat if the requested seat(s) is not available.
P=Purchase Premier Seat. To unlock Economy seats during seat pick. (Restricted for UA use only and should only be used for Economy Plus sales).
How is null data specified?
No data results in error
What does null data indicate?
No data results in error
|
|
+ <AttribQual>
[Qualified By: ReqType of G]
|
FieldSet
|
n/a
|
|
AttribCnt
Structured data only.
Not in XML.
|
Numeric
|
2
|
Description of Field:
Number of passengers booked for travel. Seat Characteristics apply to all passengers booked for travel.
Format (n-numeric):
nn
Examples:
02
How is null data specified?
No data results in error
What does null data indicate?
No data results in error
|
|
+ <AttribAry>
|
Array
|
n/a
|
|
|
<Attrib>
|
Alpha
|
2
|
Description of Field:
Generic seat characteristics.
Format (a-alpha):
aa
Special Format:
Left justified, blank filled. Blank if specific seat request. EDIFACT Standard is used.
Possible Values (List):
Wblank - window seat
Nblank - non smoking seat
Ablank - aisle
How is null data specified?
No data results in error
What does null data indicate?
No data results in error
|
|
|
|
|
|
+ <SeatQual>
[Qualified By: ReqType of S,P,E]
|
FieldSet
|
n/a
|
|
SeatCnt
Structured data only.
Not in XML.
|
Numeric
|
2
|
Description of Field:
Seat Characteristics will apply to all passengers booked for travel
Format (n-numeric):
nn
Examples:
02
How is null data specified?
No data results in error
What does null data indicate?
No data results in error
|
|
+ <SeatAry>
|
Array
|
n/a
|
|
|
<Seat>
|
Alphanumeric
|
5
|
Description of Field:
Specific seat requested. Repeated for each passenger. Examples: 03A, 22K, etc. Seat letters A-L are valid, excluding I.
Format (x-alpha/numeric):
xxxxx
Special Format:
Right justified, blank filled
This field must use CDATA for XML
Examples:
blankblank33A
How is null data specified?
No data results in error
What does null data indicate?
No data results in error
|
|
|
|
|
|
|
|
|
|
+ <ModAry>
|
Array
|
n/a
|
|
Modify only operates with leg specific flights. Modify will not operate with journey specific flights.
Example: ORD to JFK to LHR where JFK is a Change of Gauge.
To Modify: Separate modify for ORD to JFK and separate modify for JFK to LHR
Modify for ORD to LHR is not allowed.
|
|
+ <ModInfo>
|
FieldSet
|
n/a
|
|
|
<ID>
|
Alpha
|
1
|
Description of Field:
Always set to M
Format (a-alpha):
a
Possible Values (List):
M
How is null data specified?
No data results in error
What does null data indicate?
No data results in error
|
|
<Num>
|
Numeric
|
2
|
Description of Field:
This record is structured to allow multiple seat modifies in a single input. The request number field allows correlation of the results of each request with a response.
Format (n-numeric):
nn
How is null data specified?
No data results in error
What does null data indicate?
No data results in error
|
|
<AirV>
|
Alpha
|
3
|
Description of Field:
Owning airline
Format (a-alpha):
aaa
Special Format:
Left justified, blank filled
Examples:
BAblank
How is null data specified?
No data results in error
What does null data indicate?
No data results in error
|
|
<FltNum>
|
Numeric
|
4
|
Description of Field:
Flight number
Format (n-numeric):
nnnn
Special Format:
Right justified, include leading zeroes
Examples:
0013
How is null data specified?
No data results in error
What does null data indicate?
No data results in error
|
|
<OpSuf>
|
Alphanumeric
|
1
|
Description of Field:
Product reference suffix
Format (x-alpha/numeric):
x
How is null data specified?
Character blank
What does null data indicate?
Character blank is standard for field
|
|
<Dt>
|
Numeric
|
8
|
Description of Field:
Departure Date
Format (n-numeric):
nnnnnnnn
Special Format:
YYYYMMDD
How is null data specified?
No data results in error
What does null data indicate?
No data results in error
|
|
<StartAirp>
|
Alpha
|
5
|
Description of Field:
Boarding city
Format (a-alpha):
aaaaa
Special Format:
Left justified blank filled
Examples:
LHRblankblank
How is null data specified?
No data results in error
What does null data indicate?
No data results in error
|
|
<EndAirp>
|
Alpha
|
5
|
Description of Field:
Off city
Format (a-alpha):
aaaaa
Special Format:
Left justified blank filled
Examples:
LHRblankblank
How is null data specified?
No data results in error
What does null data indicate?
No data results in error
|
|
<BIC>
|
Alpha
|
2
|
Description of Field:
Class of service and class modifier
Format (a-alpha):
aa
Special Format:
Left justified blank filled.
Examples:
Jblank
JN
How is null data specified?
No data results in error
What does null data indicate?
No data results in error
|
|
<ReqType>
|
Alpha
|
1
|
Description of Field:
Type of seat requested. You cannot request generic and specific seat requests for the same passenger/flight/date
Format (a-alpha):
a
Possible Values (List):
G=Generic. A seat request is generic when the seat request is being made by specifying the characteristics of the seats desired. For example, non-smoking aisle or smoking window is defined as a generic seat request.
S=Specific. A seat request is specific when the seat request is being made by specifying the seat location of the seat(s) desired. For example, 02A or 25K is defined as a specific seat request.
P=Purchase Premier Seat. To unlock Economy seats during seat pick. (Restricted for UA use only and should only be used for Economy Plus sales).
How is null data specified?
No data results in error
What does null data indicate?
No data results in error
|
|
+ <AttribQual>
[Qualified By: ReqType of G]
|
FieldSet
|
n/a
|
|
AttribCnt
Structured data only.
Not in XML.
|
Numeric
|
2
|
Description of Field:
Number of passengers booked for travel
Format (n-numeric):
nn
How is null data specified?
No data results in error
What does null data indicate?
No data results in error
|
|
+ <AttribAry>
|
Array
|
n/a
|
|
|
<Attrib>
|
Alpha
|
2
|
Description of Field:
Seat Characteristics
Format (a-alpha):
aa
Special Format:
Left justified, blank filled. Blank if specific seat request. EDIFACT Standard is used.
Possible Values (List):
Wblank - window seat
Nblank - non smoking seat
Ablank - aisle
How is null data specified?
No data results in error
What does null data indicate?
No data results in error
|
|
|
|
|
|
+ <SeatQual>
[Qualified By: ReqType of S,P,E]
|
FieldSet
|
n/a
|
|
SeatCnt
Structured data only.
Not in XML.
|
Numeric
|
2
|
Description of Field:
Defines number of occurrences of Definition of a Seat Cancellation, number of passengers booked for travel
Format (n-numeric):
nn
How is null data specified?
No data results in error
What does null data indicate?
No data results in error
|
|
+ <SeatAry>
|
Array
|
n/a
|
|
|
<Seat>
|
Alphanumeric
|
5
|
Description of Field:
Specific seat requested. Repeated for each passenger. Examples: 03A, 22K, etc. Seat letters A-L are valid, excluding I.
Format (x-alpha/numeric):
xxxxx
Special Format:
Right justified, blank filled
This field must use CDATA for XML
Examples:
blankblank33A
How is null data specified?
No data results in error
What does null data indicate?
No data results in error
|
|
|
|
|
|
|
|
|
|
|
|
|
+ <HtlSegSellMods>
|
6150 6.0
|
|
|
|
|
|
<StartDt>
|
Numeric
|
8
|
Description of Field:
This is the date the customer will arrive (check in) at the hotel.
Format:
CCYYMMDD
Examples:
20030614
How is null data specified?
N/A
What does null data indicate?
No data results in error
|
|
<EndDt>
|
Numeric
|
8
|
Description of Field:
This is the date the customer will leave (check out) the hotel.
Format:
CCYYMMDD
Examples:
20030829
How is null data specified?
N/A
What does null data indicate?
No data results in error
|
|
<NumPersons>
|
Numeric
|
1
|
Description of Field:
This is the number of adults that will occupy a room. If the customer entered more than 2 on the selection screen, then 2 should be used here. Additional persons should be included in the extra persons field.
Format ( n-numeric):
n
Special Format:
If the customer entered more than 2 on the selection screen, then 2 should be used here. Additional persons should be included in the extra persons field.
Possible values (Range):
1 - 2
How is null data specified?
N/A
What does null data indicate?
No data results in error
|
|
<NumRooms>
|
Numeric
|
1
|
Description of Field:
The number of rooms to be reserved
Format (n-numeric):
n
How is null data specified?
N/A
What does null data indicate?
No data results in error
|
|
<Chain>
|
Alphanumeric
|
3
|
Description of Field:
Property's chain code
Format (a-alpha):
aaa
Special Format:
Left justified, blank filled
Two characters followed by a blank
Examples:
MC
HH
How is null data specified?
N/A
What does null data indicate?
No data results in error
|
|
<RoomMasterID>
|
Numeric
|
5
|
Description of Field:
The property's RoomMaster number
Format (n-numeric):
nnnnn
Special Format:
Right justified, zero filled
How is null data specified?
N/A
What does null data indicate?
No data results in error
|
|
<BIC>
|
Alphanumeric
|
7
|
Description of Field:
The full booking code for the rate being sold
Format (x-alpha/numeric):
xxxxxxx
Special Format:
Left justified, blank filled
Examples:
A1KRAC
B2TC00
How is null data specified?
N/A
What does null data indicate?
No data results in error
|
|
<RateAccess1>
|
Character
|
6
|
Description of Field:
First rate access code from availability if this is a multi level rate. Otherwise, blank.
Format (c-character):
cccccc
Special Format:
Left justified, blank filled
Examples:
SWEST
ATT
How is null data specified?
Character blanks
What does null data indicate?
No multi level rates was requested.
|
|
<RateAccess2>
|
Character
|
6
|
Description of Field:
Second rate access code from availability if this is a multi level rate. Otherwise, blank.
Format (c-character):
cccccc
Special Format:
Left justified, blank filled
Examples:
SWEST
ATT
How is null data specified?
Character blanks
What does null data indicate?
No multi level rate was requested.
|
|
<RateAccess3>
|
Character
|
6
|
Description of Field:
Third rate access code from availability if this is a multi level rate. Otherwise, blank.
Format (c-character):
cccccc
Special Format:
Left justified, blank filled
Examples:
SWEST
ATT
How is null data specified?
Character blanks
What does null data indicate?
No multi level rate was requested.
|
|
<NumExtraAdults>
|
Numeric
|
1
|
Description of Field:
0 to 3. Identifies the number of additional adults that will use the room.
Format (n-numeric):
n
Examples:
1, 2 or 3
How is null data specified?
Field will be blank or zero.
What does null data indicate?
No extra adults are expected.
|
|
<NumExtraChildren>
|
Numeric
|
1
|
Description of Field:
0 to 3. Number of children in the room.
Format (n-numeric):
n
Examples:
1, 2 or 3
How is null data specified?
Field will be blank or zero.
What does null data indicate?
No children are expected.
|
|
<NumCrib>
|
Numeric
|
1
|
Description of Field:
0 to 3. The number of cribs required for the booking.
Format (n-numeric):
n
Examples:
1, 2 or 3
How is null data specified?
Field will be blank or zero.
What does null data indicate?
No cribs are expected.
|
|
<NumAdultRollaway>
|
Numeric
|
1
|
Description of Field:
0 to 3. The number of adult rollaway beds required.
Format (n-numeric):
n
Examples:
1, 2 or 3
How is null data specified?
Field will be blank or zero.
What does null data indicate?
No adult rollaways are requested.
|
|
<NumChildRollaway>
|
Numeric
|
1
|
Description of Field:
0 to 3. The number of child rollaway beds required.
Format (n-numeric):
n
Examples:
1, 2 or 3
How is null data specified?
Field will be blank or zero.
What does null data indicate?
No child rollaways are requested.
|
|
<SellSource>
|
Alpha
|
1
|
Description of Field:
This indicates if the entries that lead up to this Sell were from the hotel or from RoomMaster or if there were no preceeding entries.
Format (a-alpha):
a
Examples:
R = Rate came from RoomMaster
I = Rate came from Inside Availability
D = Direct sell
How is null data specified?
N/A
What does null data indicate?
No data results in error
|
|
<RetRuleTxtInd>
|
Alpha
|
1
|
Description of Field:
Determines if free form text for rules should be returned in the response
Format (a-alpha):
a
Possible Values (List):
Y = Return Text
N = Do not return Text
How is null data specified?
Field will be blank.
What does null data indicate?
Blank = N
|
|
<OnReqInd>
|
Alpha
|
1
|
Description of Field:
Blank is the default. Copied from the 6112 - HOC response Room Type on Request field
Format (a-alpha):
a
Examples:
Y = The requested room is available on by contacting the hotel property.
N = The requested room is readily available.
How is null data specified?
The field will be blank
What does null data indicate?
Blank = N.
|
OptFldIDCnt
Structured data only.
Not in XML.
|
Numeric
|
2
|
Description of Field:
The number of optional fields that follow at the end of this request
Format ( n-numeric):
nn
Special Format:
Right justified, zero filled
How is null data specified?
This field will be zeros or blank.
What does null data indicate?
No optional fields were requested.
|
|
+ <OptFldIDAry>
|
Array
|
n/a
|
|
|
+ <OptFldID>
|
FieldSet
|
n/a
|
|
|
<ID>
|
Alpha
|
2
|
Description of Field:
Identifies which optional data is represented by this group:
Format (a-alpha):
aa
Possible Values (List ):
AC = Alternate Currency
BS = Booking source
ID = Special Identifier
RR = Rate request
GT = Payment guarantee
DP = Deposit
AD = Customer address
TN = Tour number
RL = Tour room location
MP = Tour meal plan
CD = Corporate discount number
FG = Frequent guest number
FT = Frequent air traveler number
SI = Special information
NF = Reservation name - first
NL = Reservation name - last
CF = Confirmation number
How is null data specified?
N/A
What does null data indicate?
No data results in an error.
|
Len
Structured data only.
Not in XML.
|
Numeric
|
3
|
Description of Field:
The number of bytes contained in the Optional Field Contents that follows
Format (a-alpha, n-numeric, 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 an error.
|
|
<Contents>
|
Alpha
|
VL
|
Description of Field:
This field contains the details of the optional data based on the type specified in Optional Field Identity. The field size depends on the contents. See comments which follow.
Format (a-alpha):
aaaaaaaaaa
Examples:
Non-smoking Room Only
AX1234567890EXP0405
How is null data specified?
N/A
What does null data indicate?
No data results in an error.
|
|
|
|
|
|
|
|
|
+ <HtlModifyDtMods>
|
6155 6.0
|
|
|
|
|
6155 - Hotel Modify Date Request - Version 6.00
Purpose: This transaction should be used only when the dates of a hotel segment are to be changed. The response will be the 6151 transaction which is common to both sell and modify.
|
|
<SegNum>
|
Numeric
|
2
|
The segment number that must be modified
|
|
<StartDt>
|
Alpha
|
8
|
CCYYMMDD. This is the date the customer will arrive (check in) at the hotel. Both dates are required when ei ther is changed.
|
|
<EndDt>
|
Alpha
|
8
|
CCYYMMDD. This is the date the customer will leave (check out) the hotel. Both dates are required when either is changed.
|
|
|
|
|
+ <HtlModifyRoomMods>
|
6156 6.0
|
|
|
|
|
6156 - Hotel Modify Room Request - Version 6.00
Purpose: This transaction should be used only when the room booking code, number in party, or num ber of rooms in a hotel segment is to be changed. The response will be the 6151 transaction which is common to both sell and modify.
|
|
<SegNum>
|
Numeric
|
2
|
The segment number that must be modified
|
|
<NumAdults>
|
Numeric
|
1
|
1 or 2. This is the number of adults.
|
|
<NumRooms>
|
Numeric
|
1
|
Change to the number of rooms to be reserved
|
|
<BIC>
|
Alpha
|
7
|
The full booking code for the new rate being sold
|
|
+ <RateAccessAry>
|
Array
|
n/a
|
|
|
<RateAccess>
|
Alpha
|
6
|
Used only to validate if the booking code is being changed
|
|
|
|
|
|
|
+ <HtlModifyOptionalMods>
|
6157 6.0
|
|
|
|
|
6157 - Hotel Modify Optional Request - Version 6.00
Purpose: This transaction should be used only when the optional fields of a hotel segment are to be changed. The response will be the 6151 transaction which is common to both sell and modify.
|
|
<SegNum>
|
Numeric
|
2
|
The segment number that must be modified
|
|
<NumExtraAdults>
|
Numeric
|
1
|
0 to 3. Identifies the number of additional adults that will use the room. Use only to change.
|
|
<NumExtraChildren>
|
Numeric
|
1
|
0 to 3. Number of children in the room. Use only to change.
|
|
<NumCrib>
|
Numeric
|
1
|
0 to 3. The number of cribs required for the booking. Use only to change.
|
|
<NumAdultRollaway>
|
Numeric
|
1
|
0 to 3. The number of adult rollaway beds required. No distinction is being made between child and adult rolla way beds. Use only to change.
|
|
<NumChildRollaway>
|
Numeric
|
1
|
0 to 3. The number of child rollaway beds required. No distinction is being made between child and adult rolla way beds. Use only to change.
|
OptFldCnt
Structured data only.
Not in XML.
|
Numeric
|
2
|
The number of optional fields that follow at the end of the header.
|
|
+ <OptFldAry>
|
Array
|
n/a
|
|
|
+ <OptFld>
|
FieldSet
|
n/a
|
|
|
<ID>
|
Alphanumeric
|
2
|
Identifies which optional data is represented by this group:
BS=Booking source
RT=Corporate rate override
RR=Rate request
GT=Payment guarantee
DP=Deposit
AD=Customer address
TN=Tour number
RL=Tour room location
MP=Tour meal plan
CD=Corporate discount number
FG=Frequent guest number
FT=Frequent air traveler number
SI=Special information
NF=Reservation name - first
NL=Reservation name - last
CF=Confirmation number
|
Len
Structured data only.
Not in XML.
|
Numeric
|
3
|
The number of bytes contained in the Optional Field Contents that follows
|
|
<Contents>
|
Alpha
|
VL
|
This field contains the details of the optional data based on the type specified in Optional Field Identity. The field size depends on the contents.
|
|
|
|
|
|
|
|
|
+ <HtlModifyDeleteMods>
|
6158 6.0
|
|
|
|
|
6158 - Hotel Modify Delete Request - Version 6.00
Purpose: This transaction should be used only when the optional fields of a hotel segment are to be deleted. The response will be the 6151 transaction which is common to both sell and modify.
|
|
<SegNum>
|
Numeric
|
2
|
The segment number that must be modified
|
The following series of bytes contain indicators to identify which optional fields should be deleted with this modify. A Y means delete this optional field. N means no action for the corresponding field.
Delete Field Flags
|
|
<Spare1>
|
Alpha
|
1
|
NReserved
|
|
<Spare2>
|
Alpha
|
1
|
NReserved
|
|
<Spare3>
|
Alpha
|
1
|
NReserved
|
|
<CorporateRateOverrideInd>
|
Alpha
|
1
|
Y or N
|
|
<RateReqInd>
|
Alpha
|
1
|
Y or N
|
|
<PmtGuarInd>
|
Alpha
|
1
|
Y or N
|
|
<AdultRollawayBedInd>
|
Alpha
|
1
|
Y or N
|
|
<ChildRollawayBedInd>
|
Alpha
|
1
|
Y or N
|
|
<CribsInd>
|
Alpha
|
1
|
Y or N
|
|
<ExtraAdultInd>
|
Alpha
|
1
|
Y or N
|
|
<ExtraChildInd>
|
Alpha
|
1
|
Y or N
|
|
<TourNumInd>
|
Alpha
|
1
|
Y or N
|
|
<TourRoomLocnInd>
|
Alpha
|
1
|
Y or N
|
|
<TourMealPlanInd>
|
Alpha
|
1
|
Y or N
|
|
<CorporateDiscNumInd>
|
Alpha
|
1
|
Y or N
|
|
<FrequentGuestInd>
|
Alpha
|
1
|
Y or N
|
|
<FrequentFlyerInd>
|
Alpha
|
1
|
Y or N
|
|
<Spare4>
|
Alpha
|
1
|
NReserved (/ID)
|
|
<SpclInfoInd>
|
Alpha
|
1
|
Y or N
|
|
<Spare5>
|
Alpha
|
1
|
NReserved
|
|
<Spare6>
|
Alpha
|
1
|
NReserved
|
|
|
|
|
+ <CarSegSellMods>
|
7150 6.0
|
|
|
|
|
|
<StartDt>
|
Numeric
|
8
|
CCYYMMDD (Century, Year, Month, Day). Set this to the car pickup date.
|
|
<StartTm>
|
Numeric
|
4
|
Pickup time expressed in 24 hour clock format
|
|
<StartAirV>
|
Alphanumeric
|
3
|
Airline code if customer is arriving by air
|
|
<StartFltNum>
|
Alphanumeric
|
4
|
Associated flight number when it applies
|
|
<Airp>
|
Alpha
|
5
|
Airport code where car is being rented
|
|
<EndDt>
|
Numeric
|
8
|
CCYYMMDD (Century, Year, Month, Day). Set to the car return date.
|
|
<EndTm>
|
Numeric
|
4
|
Return time expressed in 24 hour clock format
|
|
<EndAirV>
|
Alphanumeric
|
3
|
Airline code if customer is departing by air
|
|
<EndFltNum>
|
Alphanumeric
|
4
|
Associated flight number when it applies
|
|
<DropLocn>
|
Character
|
25
|
The location where car will be returned if other than pick up location
|
|
<CarV>
|
Alpha
|
3
|
The 2-character car company vendor code followed by a blank
|
|
<CarType>
|
Alpha
|
4
|
Car type sold. Example: ICAR LWAR FCAR
|
|
<YieldMgmtNum>
|
Character
|
1
|
From the CAL transaction
|
|
<RateType>
|
Alpha
|
1
|
D=Daily
E=Weekend
W=Weekly
M=Monthly
P=Package
|
|
<RateCat>
|
Alpha
|
1
|
Rate Category returned from CAL transaction
|
|
<Rate>
|
Alphanumeric
|
6
|
Rate code returned from CAL transaction
|
|
<Currency>
|
Alpha
|
3
|
The Currency code from a previous CAL response. Else for direct sell requests, the user selected currency code.
|
|
<RefDBKey>
|
Numeric
|
10
|
Use the Rate Data Base Key value from a prior CAL or CAA here.
|
|
<PrevRefAvail>
|
Alpha
|
1
|
L=If Data Base Key from prior CAL
A=If Data Base Key from prior CAA
|
|
<NumCars>
|
Numeric
|
1
|
The number of cars being sold MUST be 1 only.
|
|
<RetRuleTxtInd>
|
Alpha
|
1
|
Determines if free form text for rules should be returned in the response.
Y=Return text
N=Do not return text
|
|
+ <OptFldIDAry>
|
Array
|
n/a
|
|
|
+ <OptFldID>
|
FieldSet
|
n/a
|
|
|
<ID>
|
Alpha
|
2
|
Identifies which optional data is represented by this group:
RT=Corporate rate override
BS=Booking source
AD=Customer address
ID=Customer ID
PU=Pick up location
TN=Tour number
CD=Corporate ID
SI=Special information
FT=Frequent air traveler number
SQ=Special equipment
GT=Payment guarantee
PR=Prepayment information
DL=Drivers license
DC=Drop off charge
NF=Reservation name - first
NL=Reservation name - last
CF=Confirmation number
|
Len
Structured data only.
Not in XML.
|
Numeric
|
3
|
The number of bytes contained in the Optional Field Contents that follows
|
|
<Contents>
|
Alpha
|
VL
|
This field contains the details of the optional data based on the type specified in Optional Field Identity. The field size depends on the contents. See comments which follow.
|
|
|
|
|
|
|
|
|
+ <CarModifyDateMods>
|
7155 6.0
|
|
|
|
|
|
<SegNum>
|
Numeric
|
2
|
Use the segment number for the segment to be changed.
|
|
<StartDt>
|
Numeric
|
8
|
CCYYMMDD. Use this field only if the pick up date is to be changed. Otherwise fill with zeros.
|
|
<StartTm>
|
Numeric
|
4
|
Pickup time expressed in 24-hour clock format, only if the time changes
|
|
<StartAirV>
|
Alphanumeric
|
3
|
Use only if there is a change to arriving airline. Arrival Flight information can only be input if arrival time is entered. Must enter both an airline code and flight number.
|
|
<StartFltNum>
|
Alphanumeric
|
4
|
Use only if there is a change to arriving airline. Arrival Flight information can only be input if arrival time is entered. Must enter both an airline code and flight number.
|
|
<EndDt>
|
Numeric
|
8
|
CCYYMMDD. Use this only if the return date is to be changed. Otherwise fill with zeros.
|
|
<EndTm>
|
Numeric
|
4
|
Dropoff time expressed in 24-hour clock format. Only if the time changes.
|
|
<EndAirV>
|
Alphanumeric
|
3
|
Use only if there is a change to departure airline. Departure Flight information can only be input if dropoff time is entered. Must enter both an airline code and flight number.
|
|
<EndFltNum>
|
Alphanumeric
|
4
|
Use only if there is a change to departure airline. Departure Flight information can only be input if dropoff time is entered. Must enter both an airline code and flight number.
|
|
|
|
|
+ <CarModifyTypeMods>
|
7156 5.0
|
|
|
|
|
|
<SegNum>
|
Numeric
|
2
|
Use the segment number for the segment to be changed.
|
|
<CarType>
|
Alpha
|
4
|
Specify the new car type. Example: IDAR
|
|
|
|
|
+ <CarModifyOptionalMods>
|
7157 5.0
|
|
|
|
|
7157 - Car Modify Optional Request - Input - Version 5.00
Purpose: This transaction should be used only when the optional fields of a car segment are to be changed or added. The response will be the 7151 transaction which is common to both sell and modify.
|
|
<SegNum>
|
Numeric
|
2
|
Use the segment number for the segment to be changed.
|
OptFldCnt
Structured data only.
Not in XML.
|
Numeric
|
2
|
The number of optional fields that follow.
|
|
+ <OptFldAry>
|
Array
|
n/a
|
|
|
+ <OptFld>
|
FieldSet
|
n/a
|
|
|
<ID>
|
Alphanumeric
|
2
|
Identifies which optional data is represented by this group:
RT=Corporate rate override
BS=Booking source
AD=Customer address
ID=Customer ID
PU=Pick up location
AR=Arrival time
TN=Tour number
CD=Corporate ID
SI=Special information
FT=Frequent air traveler number
SQ=Special equipment
DT=Dropoff time
RC=Rate code
DO=Dropoff location
GT=Payment guarantee
PR=Prepayment information
DL=Drivers license
DC=Dropoff charge
CF=Confirmation number
|
Len
Structured data only.
Not in XML.
|
Numeric
|
3
|
The number of bytes contained in the Optional Field Contents that follows
|
|
<Data>
|
Alpha
|
VL
|
This field contains the details of the optional data based on the type specified in Optional Field Identity. The field size depends on the contents.
|
|
|
|
|
|
|
|
|
+ <CarModifyDeleteMods>
|
7158 5.0
|
|
|
|
|
|
<SegNum>
|
Numeric
|
2
|
Use the segment number for the segment to be changed.
|
|
<DelRateOverrideInd>
|
Alphanumeric
|
1
|
Y or N
|
|
<Spare>
|
Alpha
|
1
|
NCannot be deleted (/BS-)
|
|
<DelAddrInd>
|
Alphanumeric
|
1
|
Y or N
|
|
<DelCustIdInd>
|
Alphanumeric
|
1
|
Y or N
|
|
<DelPickupLocnInd>
|
Alphanumeric
|
1
|
Y or N
|
|
<DelStartTmInd>
|
Alphanumeric
|
1
|
Y or N
|
|
<DelTourNumInd>
|
Alphanumeric
|
1
|
Y or N
|
|
<DelCorpIDInd>
|
Alphanumeric
|
1
|
Y or N
|
|
<DelSpclInfoInd>
|
Alphanumeric
|
1
|
Y or N
|
|
<DelFreqTravNbrInd>
|
Alphanumeric
|
1
|
Y or N
|
|
<DelSpclEquipInd>
|
Alphanumeric
|
1
|
Y or N
|
|
<DelPmtGuarInd>
|
Alphanumeric
|
1
|
Y or N
|
|
<DelPrepayInfoInd>
|
Alphanumeric
|
1
|
Y or N
|
|
<DelDriversLicenseInd>
|
Alphanumeric
|
1
|
Y or N
|
|
<DelDropOffChargeInd>
|
Alphanumeric
|
1
|
Y or N
|
|
<Spare5>
|
Alpha
|
6
|
NReserved
|
|
|
|
|
|
|