Task: Update Itinerary/Invoice FAX

Updates a specific stored fare within the itinerary, such that the Itinerary/Invoice FAX is updated.

Section 1: Short Answer

Transaction Name:

DocProdFareRequote_9

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

No, only DocProdFareRequote_9 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?

This task is for Apollo only.

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 Itinerary/Invoice FAX are in <DocumentSelect> and include:
  • Option X to issue a FAX itinerary with a ticket (GFX). 
  • Option D to issue an itinerary FAX (DFX). This option cannot be used with the task for updated stored modifiers <UpdateModifiersMods>.

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

• A PNR/booking file must exist.
  
• For option X, Issue FAX Itinerary with ticket (GFX), the following modifiers are not allowed:
  • Modifier DFX – Itinerary Invoice FAX
  • Modifier DSD – Itinerary to CRT Screen
  • Modifier DGD – Demand Global MIR
  • Modifier DJD – Non-Faring MIR to Remote location
  • Modifier DND – Non-Ticketing MIR to Remote
  • Modifier DXD – Dual MIR
  • Modifier DPD – Pocket Itinerary only
  • Modifier DDD – Delivery Document
  • Modifier 9P – Print Boarding Pass Only
  • Modifier FEX – Exchange Tickets
    
• Processing notes for GFX modifier
  • The agent must have an account setup with the fax vendor. At this time AT&T is the only vendor. The entry to update the AAT is $-GK4/MAD|IFAX-ATT.
  • The IFAX field in the AAT must be updated with the vendor code.  If the IFAX field in the AAT is blank, the following error will be displayed: INVALID FORMAT/DATA - GFX MODIFIER NOT ALLOWED

• For option D, issue an Itinerary FAX (DFX), the following modifiers are not allowed:
  • Not valid with any other D modifiers
  • Modifier GFX – Issue FAX itinerary/invoice with ticket
  • Modifier GRC – Passenger Receipt Print Override
  • Modifer 9P – Print Boarding Pass Only
  • Modifier FEX – Exchange Tickets
    
• Processing notes for DFX modifier:
  • If used with GIF or GIN modifiers, no fare quote required.
  • May be used for an Amtrak Itin/Invoice.
  • Linkage to an Itinerary printer not needed.
  • The AAT table IFAX field must be set to the designated vendor ID ($-GK4/MAD|IFAX-ATT) and must be checked at ticketing time.
  • FOP, Commission, or Carrier Override not required.
  • Open to buy not down-dated.
  • Does not produce a ticket.
  • $FX fill-in format displayed.
  • IR0DXX,X’10’ = Itin FAX requested.

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 Itinerary/Invoice FAX to be issued with or without a ticket.

Prerequisite tasks:

• A fare must exist.
• A PNR/Booking file must exist.
• The IFAX field of the AAT must be updated with a vendor code.

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.
• When trying to store the DFX modifier, the following response occurs:

ERROR 7751 - INVALID FORMAT/DATA - DFX MODIFIER NOT ALLOWED

T:$BDFX

• When combining the GFX with an invalid modifier (for this example 9P was used), the following response was received:

ERROR 4355 - GFX NOT COMBINABLE WITH 9P

Follow-on requests:

None.

Section 3: Tables

Request (Input) Tags

Response (Output) Tags

Related Samples

DocProdFareRequote_9_s10