Task: Update MIR

Updates a specific stored fare within the itinerary, such that MIR information is updated. Tickets and itineraries will not print with this task.

Section 1: Short Answer

Transaction Name:

DocProdFareRequote_6

Can any other transaction(s) perform this same task?

No, only DocProdFareRequote_6 can perform this task.

Can this task be performed in a sessionless environment?
No. A PNR/booking file must exist. A fare must exist.

Are the request and response identical on both the Apollo and Galileo systems?

All options are available on Galileo and Apollo except option A, Accounting MIR only. Option A, Accounting MIR only (DBD), is only available on Apollo.

List any industry-specific knowledge required to understand this task in terms of the specific business process.

• A fare must exist.
• A PNR/booking file must exist.
• The task is available through structured data and Focalpoint (terminal emulation).
• The options for the MIR are in <DocumentSelect> and include:
  • Option A, Accounting MIR only (DBD modifier). Option A (DBD modifier) is only available on Apollo.
  • Option N, Non-Accounting MIR only (DAD modifier)
  • Option R, Non-Accounting Remote MIR only (DND modifier). This option requires additional fields in <DocumentSelect> GTID/CRS and city code to be populated.
  • Option X, Dual MIR (DXD modifier). This option requires additional fields in <DocumentSelect> GTID/CRS and city code to be populated.
    

Explain any special limits or distinct restrictions to the input data that may not be readily apparent.

• A PNR/booking file must exist.
  
• Option A, Accounting MIR only (DBD), is for Apollo only. For option A, Accounting MIR only (DBD), the following modifiers are not allowed:
  • Modifier DXD – Dual MIR
  • Modifier DED – Electronic Ticket Delivery Network (ETDN) Validation *
  • Modifier DFX – Itinerary/Invoice FAX
  • Modifier DGD – Demand Global MIR
  • Modifier DJD – Non-Faring MIR to Remote Location
  • Modifier DND – Non-Ticketing MIR to Remote
  • Modifier DSD – Itinerary to CRT Screen
  • Modifier DPD – Pocket Itinerary Only
  • Modifier DDD – Delivery Document
• Processing notes for DBD modifier:
  • Sends an accountable ticketing MIR to the interfaced computer system for agencies that do back room ticketing and do not use just HB: for their ticketing entry. This modifier will add the ticketing information to the ARC Electronic Credit Card Billing system.
  • Open to buy is down-dated.
  • Does not produce a ticket.
    
• For option N, Non-Accounting MIR only (DAD), the following modifiers are not allowed:
  • Modifier DXD – Dual MIR
  • Modifier DND – Non-Ticketing MIR to Remote
  • Modifier DJD – Non-Faring MIR to Remote Location 
  • Modifier DED – Electronic Ticket Delivery Network (ETDN) Validation
  • Modifier DFX – Itinerary/Invoice FAX
  • Modifier DGD – Demand Global MIR
  • Modifier DSD – Itinerary to CRT Screen
  • Modifier DPD – Pocket Itinerary Only
  • Modifier DDD – Delivery Document
• Processing notes for DAD modifier:
  • Sends an accountable ticketing MIR to the interfaced computer system for agencies that do back-room ticketing and do not use just HB:  for their ticketing entry. This modifier will add the ticketing information to the ARC Electronic Credit Card Billing system.
  • Open to buy not down-dated.
  • Does not produce a ticket.
    
• For option R, Non-Accounting Remote MIR only (DND), the following modifiers are not allowed:
  • Any D modifier except DID, PT, IT.
  • Any G modifier except GIF, SALL, SNONE, SLNONE, SRNONE, SXNONE, SXALL, 9P, 9BX, 9B, NVA/NVB on INPUT ONLY.  Valid if the modifiers are stored.
• Processing notes for DND modifier:
  • Does not require form of payment, commission, or carrier override.
  • The purpose for this MIR is to allow travel agents to issue a MIR without updating the ATFQ or ticketing fields in the PNR.
  • Sends a non-accountable MIR to the MIR device targeted in the DND command for a PNR which may or may not have been already ticketed.
  • Sending/Receiving locations must be same MIR type
  • Sending/Receiving locations must be MIR62 or higher.
  • If a fill-in format pricing record is required, zero dollar amounts may be used.
  • Non-ticketing MIR will hand off the last ticket and invoice numbers from TINS history.
  • Both MIRs will buffer if the device at the sending location is down.
  • Open to buy not down-dated.
  • Modifier can be used with Queue Ticketing (Queue Mirring) (e.g., HB:Q/10/DND|2D8303|GK4).
  • Receiving locations MIR GTID must be present in the output section of the AAT table for the transmitting agency.
  • Must be AG, OU, or UA duty code.
    
• For option X, Dual MIR (DXD), the following modifiers are not allowed:
  • Any D modifier except DID
  • Any G modifier, IT
  • SALL, SNONE, SLNONE, SRNONE, SXNONE, SXALL, 9P on INPUT ONLY. Valid if the modifiers are stored.
• Processing notes for DXD modifier:
  • Issues a ticket, an itinerary, a two ticketing MIRs. One MIR is issued to the MIR device to which the CRT is physically linked, and the other MIR is a copy of that MIR to the MIR device targeted in the DXD command.
  • Both MIRs will buffer if device at sending location is down.
  • When using the Dual MIR format, both MIRs are given unique Apollo sequence numbers. Therefore, it is possible to retransmit either of the MIRs using the HQT command. The MIR will be retransmitted to the device indicated for the 'OUTPUT LNIATA' displayed after typing: HQB/ACC/Sequence number.  To transmit the second MIR, emulate the target Pseudo City Code then enter HQB/ACC/Sequence number.
  • Open to buy is down-dated.
  • Sending/Receiving locations must be same MIR type.
  • Sending/Receiving locations must be MIR62 or higher.
  • Must be a different GTID than that which is linked to the MIR device.
  • Sending agency must be linked to a MIR device.
  • One CRT at target agency must be linked to input MIR device.
  • Must be AG, OU, or UA duty code.

Section 2: Detailed Description

Request:

1. Create the PNR/booking file with a fare.
2. The fare number will be in <FareNumInfo>.
3. Use <DocumentSelect> to set up the MIR options for Accounting MIR, Non-Accounting MIR, Non-Accounting Remote MIR, Non-Faring Remote MIR only, or Dual MIR.

Prerequisite tasks:

• A fare must exist.
• A PNR/Booking file must exist.

Expected response:

The response <UpdateModifiers> will include <FareNumInfo> and <DPOK>.

Error and warning responses:

If there is an error, it is sent back in <ErrText> in the <UpdateModifiers> response.

Follow-on requests:

None.

Section 3: Tables

Request (Input) Tags

Response (Output) Tags

Related Samples

DocProdFareRequote_6_s13