Header Section

BASIC ID

All MIRs begin with T5.

This cannot be assumed to be the only occurrence of T5 in a MIR.

TRANSMITTING  SYSTEM

Identifies the CRS transmitting the MIR.

• 1V = Travelport Apollo System

• 1G = Travelport+

IATA ASSIGNED NUMERIC ACCOUNTING CODE AND CHECK DIGIT

• APOLLO(APO) = 5880

• GALILEO(Travelport+) = 7733

If a Back Office System is producing tickets from this MIR, the System Provider Code printed on the tickets should be the code assigned to that ticketing system by the Airline Transport Association ATA or International Air Transport Association IATA.   With the move to 100% E Ticketing it is anticipated that any back office systems still producing paper tickets will stop.

MIR TYPE Indicator

This is controlled by a setting within the “type line” of the Agency’s AAT Table.  The field is currently populated with “92”.

TOTAL RECORD SIZE

Total number of bytes transmitted in this MIR. The largest record that may be transmitted in Travelport Apollo and Travelport+ System is 50,000 characters, then systems error.

RECORD/MESSAGE

SEQUENCE NUMBER

A file/retransmission number assigned by Travelport Apollo System or Travelport+ at the time of issuance.  Also known as the MIR Sequence number. 

The Travelport+ range is 1 to 33,000.  On retransmission the number is not incremented.   It is important to understand the difference between “retransmission” and the TKPDAD functions.   “Retransmission” relates to finding a previously sent MIR and sending it again.   In this case the whole MIR (including the sequence number and date/time) are identical to the original.   TKPDAD creates a new MIR with a new sequence number and a new date/time stamp.

Sequence numbers are unique for each MIR per Pseudo City Code.  To display the sequence number, type: HQB/ACC/DS and HQB/MD to locate the record you are looking for, then HQT in Travelport Apollo System or HQNN in Travelport+ to retransmit.  (Details on this functionality are at the end of this Document).

MIR CREATION DATE AND TIME

DATE OF MIR CREATION(Format:  DDMMMYY). This is CRT date.

TIME OF MIR CREATION

• For Travelport Apollo System, time is Agency local time, and is based on the MIR Options Table setting 12 or 24 Hour Clock. 

• For Travelport+, date and time is GMT/UTC. 

If 24 hour clock, time is left justified.

ISSUING / VALIDATING AIRLINE DATA

AIRLINE CODE

Code of the issuing / validating carrier.    If the Airline Code is 3 characters the Airline Code appears in label T50PCC. If both a 2 character and 3 character code is held in the database both labels will be filled. If Non-Air MIR, this field will be blank filled.

• Travelport Apollo System: blank filled for non-air and MIRs created bypassing 360 FARES.

• Travelport+: blank filled for non-air and when 360 FARES is bypassed or /C is not used with a TKP or TMU entry.

AIRLINE NUMBER

Numeric code of issuing/validating carrier.  (If Non-Air or bypass of 360 FARES or no /C used with TMU/TKP entry, this field will be zero filled).

OFFICIAL AIRLINE NAME

This is the Plating Carrier name as Stored in Travelport Apollo System or Travelport+.

This is the airline name in the form in which it is printed on the ticket. If a Non-Air MIR is sent or bypass of 360 FARES or no /C used with TMU/TKP entry or there is no filed fare in the booking file/PNR, this field will be blank filled.

DATE OF FIRST TRAVEL

(Format:  DDMMMYY).

Date of the first segment in the ticketed itinerary. For Refunds and Open Tickets (tickets issued without creating a PNR/Booking File) and Non-Air PNRs/Booking Files this data element will be populated with blanks.

GTIDS FOLLOW

INPUT CRT LNIATA/GTID

LNIATA/GTID of the CRT which initiated the ticketing command: "HB" or “TKP”. If Refund/Void will show CRT which input Refund/Void entry.

OUTPUT DEVICE GTID GTID of the MIR device receiving the MIR.  DJD, DND and DXD commands reflect this GTID in the input entry.

Carriage return

*********************************************************************

BOOKING AGENCY ACCOUNT CODE

Pseudo city code of agency booking the PNR/Booking File.

If the PNR/Booking File is booked and ticketed in the same pseudo city, both the Ticketing Agency Account Code and the Booking Agency Account Code are the same. 

Supports US, NL, CH, AT.

If Refund/Void/Spoiled: blank filled.

ISSUING/TICKETING AGENCY ACCOUNT CODE

Pseudo city code of the agency issuing the tickets and/or MIRs using the command: "HB" or “TKP”.

For NL to support current Ticket Delivery Office (TDO) requirement, this field contains the Pseudo city Code of the Ticket Delivery Office.

If Refund/Void MIR, this is the PCC of agency initiating Refund/Void.

AGENCY ACCOUNT NUMBER

ARC/IATA-BSP number for Ticketing Pseudo city. This is the IATA number that prints on the ticket.

Travelport+: When TKPDAD is input, the IATA number of the agency requesting the MIR occurs, not the IATA number on the ticket.

For Switzerland and Austria this is the printing location IATA number. For NL TDO this is the IATA number of the originating agent (HAGT).

RECORD LOCATOR

This record ID is assigned by Travelport Apollo System or Travelport+ and stays with the PNR/Booking File until the PNR/Booking File expires after usage.  Where there is no Booking File or PNR this field contains ZZZZZZ. For example, where an open ticket has been issued or a refund/void/spoiled MIR.

RECORD LOCATOR FROM ORIGINATING (Owning) CRS/Airline

Travelport Apollo System only

Blank on Travelport+

OTHER CRS/AIRLINE CODE

Travelport Apollo System only, blank on Travelport+.

AUTOMATIC / MANUAL Indicator

(Indicator setting identifying whether the other CRS/Airline Record Locator was manually entered or received.

Travelport Apollo System:

Blank = Travelport Apollo System booked or captured, M = Manually entered using the GRL command: HBGRLXXXXXX*AA).

Travelport+: this manual entry functionality does not exist and is blank filled.

BOOKING AGENT SIGN

This is the sign of the agent who created the Booking File or Refund

Travelport+: When the booking file has been created by the Integrated Content function this field will read ZVNHC.   Note this only occurs when the Booking File was created by the Integrated Content function.   If an existing Booking File has integrated content added the sign of the person who originally created the booking file will be shown here.

Note: The Booking Agent Sign now consists of either the 4 character Booking Pseudo city Code and the 2 character "RSPR" code, which is generally the first two characters of an agent's sign (EX:  0W0PSM). 

• In Travelport Apollo System in a Service Bureau sign on situation, the exact sign on the agent typed initially starting with the character "D" (EX:  DRMSM).  This field has a maximum of 6 characters, but may contain blanks. It is left justified.

• In Travelport+ “D” does not appear.

SERVICE BUREAU Indicator

• Y = Service Bureau Sign Used

• N = Regular Agency Sign Used

Travelport Apollo System: This indicator identifies whether the agent signed on to a Service Bureau set using a Service Bureau Sign On Code.  A Service Bureau sign on enables the agent to emulate designated pseudo cities to update  PNR/Booking Files, and/or issue tickets for another location.

Travelport+:  always a N.

ISSUING AGENT DATA

TICKETING AGENT SIGN

This field is picked up from the STD profile and is the RSPR code that is set up when the agent's STD profile is created.  This is the Agent Sign of the agent who issued the ticket  and/or the MIR.

AGENT DUTY CODE

Duty Codes are:

• AG = Agent

• TA = Training (Travelport+)

• OU = Outside User

• MA = Meshing Agent (Used during conversion to Travelport Apollo System & Travelport+)

• SU = GI/NDC user (Travelport+)

PNR/BOOKING FILE CREATION DATE

Date of initial creation of the PNR/Booking File. (Example:  10DEC96). If Refund/Void blank filled.

ELAPSED PNR/BOOKING FILE HANDLING TIME

This field identifies the number of days between the PNR/Booking File Creation Date and the MIR Creation Date.  Contains "000" if MIR and PNR/Booking File creation dates are the same. Based on CRT date. For a Refund this defaults to 000.

Travelport Apollo System: The "time" used to calculate this date is based on the RESO CITY indicated in the agency's AAT Table.  RESO CITY is the Travelport Apollo System servicing city for the agency.

DATE OF LAST CHANGE TO PNR/BOOKING FILE

(Example:  20MAR96)

The date in which the last "R:" or “R.” was entered for this PNR/Booking File.  If there are no changes, the default is the MIR creation date. This is local CRT date.

If Refund/Void blank filled.

NUMBER OF CHANGES TO PNR/BOOKING FILE

Number of times the PNR/Booking File is manually Received with the "R:" or “R.” entry.  Open Tickets default to 001 when TKPN or HB-entries used. Defaults to 000 for Refund. If Refund/Void blank filled.

Carriage return

*********************************************************************

CURRENCY CODE

Applies to Party Fare.  Non-Air MIRs contain blanks. In Travelport Apollo System the currency is by value of CRT location. In Travelport+ this is the currency held in the filed fare. If there is no filed fare, it is blank filled. If an e-ticket refund this is the currency code of the ticket being refunded.

PARTY FARE

Travelport Apollo System: Base Fare for all ticketed passengers.

Travelport+: Base Fare for all ticketed passengers or for all passengers in the filed fare.

NUMBER OF DECIMAL PLACES IN CURRENCY

Reflects the number of decimals designated by the base currency code of the MIR. This is blank filled when no currency code. This is zero filled when no decimal in the currency.

CURRENCY CODE

The Currency Code here applies to all Taxes and Commission. This is the currency code of the CRT location.

FIRST TAX AMOUNT

Travelport+: zero filled.   Travelport+ tax data is in the A07 section.

FIRST TAX CODE

Identifies the Country or type of tax.  If no tax amount precedes, then this field is blank filled. Travelport+: blank filled.

SECOND TAX AMOUNT

Travelport+: zero filled.

SECOND TAX CODE

Identifies the Country or type of tax.  If no tax amount precedes, then this field is blank filled. Travelport+: blank filled.

THIRD TAX AMOUNT

Travelport+: zero filled.

THIRD TAX CODE

Identifies the Country or type of tax.  If no tax amount precedes, then this field is blank filled. Travelport+: blank filled.

FOURTH TAX AMOUNT

Travelport+: zero filled

FOURTH TAX CODE

Identifies the Country or type or tax.  If no tax amount precedes, then this field is blank filled.

FIFTH TAX AMOUNT

Travelport+: zero filled.

FIFTH TAX CODE

Identifies the Country or type of tax.  If no tax amount precedes, then this field is blank filled.

Note: Currently, in the United States, only the first two tax amounts are used.  In Canada, the first three tax amounts are used.  The U.S. will expand to three tax amounts after the Ticket Exchange Enhancement is completed.  Taxes four and five are provided for future expansion. 

PASSENGER COMMISSION DATA

Only one of T50COM or T50RTE will contain data.   If commission is applied as a percentage T50RTE will contain that percentage and T50COM will be zeros.

COMMISSION AMOUNT**

Commission amount designated or assumed in the ticket issuance or refund. 

If not applicable, field contains zeros.

COMMISSION RATE**

(COST FACTOR)

The commission percentage designated or assumed in the ticket issuance or refund.  If not applicable, field contains zeros.

** Note: Will receive either amount or rate, not both.  A decimal place is not transmitted. Systems are advised to allow for the possibility that both commission fields will be used, not just the percentage.

TOUR CODE

Travelport Apollo System: IT number is entered at fare quote or time of ticketing:  ITUA123456789.  The MIR only shows the data following the "IT" characters.  If not applicable, field is blank.

Travelport+: the first 14 characters are the Tour Code with the first character as the Tour Code Type. The Tour Code Type ‘I’ (IT) or ‘B’ (BT) as entered by the agent.

• I = Inclusive Tour

• B = Bulk Tour

In some cases data printed in the tour code box is actually a Carrier Agreement Reference number (entered using the AI- modifier) or Value Code (VC- modifier).   See A21 section for detail.

Carriage return

*********************************************************************

Indicator BYTES

Note: The following indicators are Yes/No (Y/N) unless otherwise noted.

• Y = RETRANSMISSION

  Applies to the retransmission of a MIR only.  Travelport Apollo System only: HQB/ACC/11111, HQT does not apply to the retransmission of a ticket or invoice - using HQNN.

• N = An actual document issuance command created this MIR.  (Either an HB or TKP ticketing command or a MIR issuance command such as DAD, DXD, etc.).

Refund/void MIR shows “Y” for retransmission.

MANUAL PRICING

• Y = CONSTRUCTED WITH FILL-IN-FORMAT USING FBC or HHPR.

• N = No pricing record exist.

When a Refund/Void shows “N”.

360 FARES PRICING

• Y = Priced by 360 Fares

• N = Manual priced by agent.

In Refund/Void MIR, when TRA entry “Y” default, otherwise “N”. Travelport+: shows “N”, except when a refund for an electronic ticket.

• Y = 1 FARE BASIS SECTION FOR ALL PASSENGERS

  All passengers in the MIR are booked and ticketed at the same Fare.

• N = A different fare exists for at least one of the passengers in the MIR.

If Refund/Void default to “Y”.

• Y = STP TICKET ISSUED

  Ticket generated to a printer at an alternate location. Where TDO this shows Y on TKP.

• N = Ticket issued locally.

If Refund/Void, default to “N”.

ATB Indicator

(Type of ATB Coupons issued).

• 0 = NON ATB (TAT, OPTAT)

• 1 = ATB (ATB1,OPTAT2)

• 2 = REPRINTED ATB HQNN(Travelport Apollo System)

• 3 = MINI-ITIN (Travelport Apollo System)

• 4 = BOARDING PASS ONLY (ATB OR OPTAT)

• 5 = ELECTRONIC TICKETING (Electronic Ticketing, not ETDN)

• 6 = COUPON PRINT FOR A  ELECTRONIC TICKET (Travelport Apollo System)

• 7 =  ATB2

• 8 =  OTHER

Indicator 5 for electronic ticketing will be the only means by which BOS can identify transactions for printing appropriate wording on accountable documents so that the passenger understands it is an electronic ticket.

EXCHANGE TICKET INFORMATION

• Y = A ticket exchange was issued through Travelport Apollo System or Travelport+ (HBFEX or TKPFEX command), and a Ticket Exchange Section (A10) is present in the MIR.

• N = No Ticket Exchange information exists.

If Refund/Void default to “N”.

CONJUNCTION NUMBER REQUIRED

• Y = More than four air segments (Including Surface Segments) are present in the MIR and a conjuncted ticket number is required.

• N = Four or less air segments exist in the MIR and a conjuncted ticket number is not required.

For Refund/Void MIR if more than one ticket shows “Y”, otherwise “N”.

FARE CONSTRUCTION DATA PRESENT

• Y = Fare Construction Section (A09) is contained in this MIR.

• N = Fare Construction Section (A09) is not contained in this MIR.

For refund/void MIR = “N” except for an electronic ticket.

SEAT DATA INFORMATION

Note: In Refund/Void MIR, defaults to “A”.

Travelport Apollo System:

The Seat Data Information applies to OPTAT Ticket Types 16 and 18, as well as ATB Ticket Type 69,79,80,90.  The stock for these ticket types include boarding passes.  OPTAT Ticket Types 15 & 17 do not include boarding passes.

Travelport+:

The Seat Data information applies to OPTAT Ticket Types 16, 18, 20, 22, and 23.  TAT and OPTAT types 7, 9, 11, 13, 15, 17, 19, 21 do not include boarding passes.  No boarding pass seat data with ATB2 currently.

If producing tickets from the Back Office System using this MIR, the seat data information included in this field may be helpful.

• A = No Seat Data Exists in the PNR/Booking File - "VOID" prints on the boarding pass.  Travelport+ will not issue a Boarding Pass if there is no seat data.

• B = Seat Data Exists in the PNR/Booking File, but no boarding pass is issued.  This indicator is received for Ticket Types 15 and 17, where boarding pass stock is not included.  Where Boarding Pass stock is not included or for segments where Seat Data is present, but the date is outside the date allowance for issuing boarding passes.  Travelport+ will not issue a Boarding Pass if it is outside the date of allowance and/or not in the carrier list.  Travelport+ Ticket Types 7, 9, 11, 13, 15, 17, 19, 21. (Travelport Apollo System only).

• C = Seat Data Exists - Seat Numbers print on boarding pass only.  "VOID" prints on ticket.  This occurs when only a boarding pass is requested using the HB9P command.  Applies only to Ticket Types 16, 18 and 69,79,80,90 (Travelport Apollo System only).

• D = Seat Data Exists - Seat Numbers print on ticket and boarding pass as appropriate for each segment.  HB9B command used or 9B assumed by Travelport Apollo System when the ticket is issued. (Travelport Apollo System only).

A description of Ticket Types can be found in 2K Fare Construction.

TINS DATA PRESENT

Ticket Invoice Numbering System

Based on the AAT Table setting for TKTN and INVN (equal to "Y").

• Y = TINS agency transmission (Option 6).  The CRT is linked to ticket and/or itinerary and MIR devices.  Travelport Apollo System and Travelport+ issues the ticket and/or invoice and sends the MIR to the Back Office System.  If a ticket and an invoice are issued, the ticket and invoice numbers are present in the Passenger Data Section (A02) of the MIR.

• N = Non-TINS agency transmission (Option 5).  The CRT is linked to a MIR device only and the Back Office System issues the ticket.

For refund/void MIR = “Y”.

TICKETING COMMAND USED

• X = DUAL MIR TRANSMITTED (DXD Command Used)  The DXD command has the ability to generate a ticket, itinerary and two MIRs to two different MIR devices.

• N = NON-TICKETING MIR (DND Command Used)  The DND command transmits a MIR only to the MIR device targeted in the command.  This MIR does not enter the fraud package and may or may not contain ticketing information (Ticket and Invoice Numbers).

• J = NON-FARING MIR (DJD Command Used)  The DJD command transmits a MIR only to the MIR device targeted in the command.  This MIR does not enter the fraud package and does NOT contain ANY Fare information (Travelport Apollo System and Travelport+).  The DJD command will also transmit a non-faring MIR for non-participant carriers with or without a MIR device targeted in the command (Travelport Apollo System and Travelport+).

• A = NON-ACCOUNTING MIR (DAD Command Used)  The DAD command transmits a MIR only, to the MIR device the CRT is linked to.  Travelport Apollo System: This MIR does not enter the fraud package and does not contain Ticket and Invoices numbers unless entered in the BOS Ticket Remark section (A14).

• B = ACCOUNTING MIR (DBD Command Used)  The DBD command transmits a MIR only, to the device the CRT is linked to.  This MIR does enter the fraud package and should be used when ticketing from the Back Office accounting System. (Travelport Apollo System only)

• D = EMD Refund (EMDR).

• H = REGULAR MIR (HB or TKP Ticketing Command Used)  This MIR is transmitted to the MIR device the CRT is linked to when the HB Ticketing command is used.  This ticketing command does enter the fraud package and the MIR contains ticket and invoice numbers as they apply to the format entered and the devices the CRT is linked to.

• I = EMD Exchange (EMDI/EXE).

• F = EMD Issue (EMDI).

• L = Electronic Ticket (DLD Command Used in Travelport Apollo System) Identifies that an Electronic Ticket (no flight coupons printed from the Ticket printer) was issued with this PNR. (Travelport Apollo System only)

• G = Global MIR.  This issues a Ticket and Itinerary on the CRS the agent is using, a MIR to the MIR device the agent is linked to, and a MIR to the MIR device that the Booking File/PNR has been borrowed from.  (DGD Command Used).

• C = Cancelled Refund MIR. This shows the issue of a MIR when TRNC is used. (Travelport+ only).

• R = Refund MIR. This shows the issue of a MIR with A23 section when on Travelport+ the TRNE entry is used and when on APO the HBRF/RF or HBRF/RP entry is used.

• S = Spoiled MIR. This shows the issue of a MIR for a spoiled transaction, when RRSP is used on Travelport Apollo System and TRV is used on Travelport+. It shows when a MIR is generated automatically when an electronic ticket fails. In this situation, a spoiled MIR may be generated if an agent chooses to proceed with a paper ticket.  If this occurs, then a spoiled MIR will be generated, followed by a ticketing MIR with H indicator.

• U = Unvoid MIR. This shows the issue of a MIR for an unvoided transaction, when RRVU is used on APO and TRU is used on Travelport+.

• V= Void MIR. This shows the issue of a MIR for a void transaction, when RRVO is used on APO and TRV is used on Travelport+.   It shows when a MIR is generated automatically by HQNN entry.  In this case, a void MIR and a ticketing MIR will be generated.

• Z = EMD Void (EMDV).

SITI/SOTO Indicator

SITI/SOTO is no longer an IATA requirement.   This field is always blank.  This field is always blank.

TRAVEL ADVISORY Indicator

Travelport Apollo System: When a Travel Advisory exists, the advisory detail remark will be present in an Associated Remark (Section A15).

• Y = A Travel Advisory is displayed in the PNR/Booking File.  For information regarding travel advisories see the APO Profile TD*DS/ADVIS).

• N = A Travel Advisory does not apply to this itinerary.

Travelport+: “N” filled.

If a Refund/Void default to “N”.

GROUP MANAGER DATA PRESENT

Travelport Apollo System:

• Y = At least one segment on this itinerary is booked through a GroupManager PNR/BOOKING FILE.  The related air segments have additional fields present in the Airline Data Section (A04).

• N = None of the issued segments are booked through a GroupManager PNR/BOOKING FILE.

Travelport+: “N” filled.

If a Refund/Void default to “N”.

DIRECT BOOKED Indicator

• Y = The PNR/Booking File was created through a direct booking application.

• N = The PNR/Booking File was not created using a direct booking application.

If a Refund/Void default to “N”.

DOMESTIC / INTERNATIONAL Indicator

(This indicator applies to the entire itinerary and matches the Domestic/ International indicator printed on the ticket, as determined by the IATA handbook rules, which uses the Arrival City to decide the setting for this indicator).

• X = INTERNATIONAL ITINERARY

• blank = DOMESTIC ITINERARY

• T = TRANSBORDER ITINERARY (United States, Canada, and Mexico ONLY)

For refund MIR shows X, blank or T.  For void MIR blank filled.

PLATING CARRIER CODE

When the Issuing/Plating Carrier has a three character code, the Carrier code will exist in this field.

Travelport Apollo System: “N” filled.

ISO COUNTRY CODE OF AGENCY

Identifies the Country Code of the agency location.

Travelport Apollo System: “N” filled.

Note: If a dual MIR command is used and an "X" appears in label T50IN12, the following fields (labels T50DMI, T50DST, T50DPC, T50DSQ, T50DLN) are included in the header; otherwise, blanks are sent.

If this is the "Sender's" MIR, then the information contained in this section relates to the Target MIR.  If this is the "Target" MIR, then the information contained in this section relates to the Sender's MIR.

Both MIR devices must be UP in order for all information to appear in the MIR.  If the Target Pseudo MIR device is down, then the following information will be missing:  Sender's MIR will not have the Dual MIR sequence number and Target MIR will not have the Sender's MIR information.

A Dual MIR command sends two identical MIRs to two different MIR GTIDs.  The following example should help to clarify the differences:

SENDER

TARGET PSEUDO CITY CODE              W0P                             GK4

MIR GTID                                  2D8303                        2D8109

MIR SEQUENCE NBR              00045                           00376

DUAL MIR COMMAND BY SENDER:  In APO: HBDXD or in Travelport+: TKPDXD +2D8109+GK4

                MIR 1 /SENDER'S MIR       MIR 2 /TARGET MIR

T50SEQ             00045                     00376

T50OUT             2D8303                    2D8109

T50TPC             W0P                       GK4

T50DST             T                         S

T50DPC             GK4                       W0P

T50DSQ             00376                     00045

T50DLN             2D8109                    2D8303

When a Dual MIR issuance is sent within the same pseudo city the only difference between the sender's MIR and the target's MIR is the GTID.  For example in Travelport Apollo System: HB:DXD+2D8109+W0P or in Travelport+: TKPDXD + 2D8109 + WOP.

DUAL MIR IDENTIFIER

D:

Indicates that Dual MIR data exists for this record and the Dual MIR fields follow.

SENDER / TARGET Indicator

• S = Sender's MIR information follows.

  The Sender's MIR contains information relating to the Target MIR.

• T = Target MIR information follows.

  The Target MIR contains information relating to the Sender's MIR.

PSEUDO CITY CODE

Pseudo city code related to the DXD command.

DUAL MIR SEQUENCE NUMBER

Sequence number assigned by Travelport Apollo System/Travelport+ related to the pseudo city code designated in the DXD command.

DUAL MIR GTID

The GTID that the second MIR is directed to.  If this is the Target MIR, this field will identify the GTID where the original MIR was sent.  If this is the Sending MIR, this field will contain the Target GTID entered in the DXD command.

Note: If an STP ticket is issued, and a MIR label T50IN5 is set to “Y”, then the following information is included in the header. Otherwise, blanks are sent.

STP IDENTIFIER

S:

HOST PSEUDO CITY CODE

Used for Two Way Split Ticketing.

In two way split ticketing, the STP printer prints the passenger coupons, boarding passes and pocket itinerary.  The Host printer prints the agents, auditors and charge form coupons.

HOME PSEUDO CITY CODE

Travelport Apollo System: used for Three Way Split Ticketing.

Travelport+: blank filled.

In three way split ticketing, the STP printer prints the passenger coupons, boarding passes and pocket itinerary.  The Host printer prints the agents coupon, and the Home printer prints the auditors coupon and the charge form.

Carriage return

*********************************************************************

ITEM COUNT (NNN = NUMBER OF ITEMS IN SECTION).

NUMBER OF CUSTOMER REMARKS

Travelport Apollo System: One 43 character, "C-" Customer Remark, is allowed per PNR/booking file.

Travelport+: zero filled.

NUMBER OF CORPORATE NAMES

This section is populated when a "C/ or G/" PNR/booking file is created.

NUMBER OF PASSENGER ITEMS

Relates to the number of passengers transmitted in this MIR.

NUMBER OF FREQUENT FLYER ITEMS

This pertains to the number of Frequent Flyer numbers entered in this PNR/booking file.

NUMBER OF TICKETED/PRICED AIRLINE SEGMENTS

NUMBER OF WAITLISTED / NON-PRICED/TICKETED SEGMENTS

This is the number of segments Waitlisted, Not Ticketed, or not included in the Filed Fare.

NUMBER OF SEAT DATA ITEMS

NUMBER OF FARE SECTIONS

This field reflects the number of fare types in this MIR.

Note: The fare information is broken into three different sections:  Fare Value, Fare Basis and Fare Construction.  The Fare Value section (A07) contains all fare and tax information associated to this specific fare item and this section appears only once per fare type.  The Fare Basis section (A08) contains fare/segment related information (i.e., segment value, fare basis code, etc.). and appears once per segment per fare type.  The Fare Calculation section (A09) contains the Linear Fare Calculation printed on the ticket, and is sent only once per fare type, unless a manual linear fare is completed and the calculation is different for each passenger.

Example:  A 3 segment itinerary for two passengers travelling on the same fare contains 1 Fare Value Section, 3 Fare Basis Items and 1 Fare Calculation Section.

The MIR Options Table selection "FARE CALC." provides the ability to receive or not receive the (A09) Fare Calculation section.

NUMBER OF TICKET EXCHANGE ITEMS

NUMBER OF FORM-OF-PAYMENT ITEMS

NUMBER OF PHONE ITEMS

NUMBER OF PASSENGER ADDRESS ITEMS

Includes W- and/or D- addresses.

NUMBER OF BACKOFFICE/TICKET REMARKS

NUMBER OF ASSOCIATED/UNASSOCIATED REMARKS

These remarks are associated or unassociated to Airline or Auxiliary segments.

The Number of RMA/RMU or RI. Remarks. 

NUMBER OF AUXILIARY SEGMENTS

Auxiliary segments include Car, Hotel and Tour Segments).

NUMBER OF LEISURESHOPPER ITEMS

Conditional Label - NDC Identifier NDC: (Travelport+ only)

NDC indicator

Carriage return

- END OF HEADER