Task: Update Itinerary/Invoice Type

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

Section 1: Short Answer

Transaction Name:

DocProdFareRequote_1_0

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

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

The DID modifier is identical for both Apollo and Galileo systems.

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 type are in <DocumentSelect> and include:
  • Option I, Normal Itin/Invoice, prints Itinerary only (DID) Modifier
  • Option P, Pocket Itinerary, prints Itinerary only (DPD) Modifier. The DPD modifier is for Apollo only.  The DPD modifier cannot be stored with the <UpdateModifiersMods> request.

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 I, Normal Itin/Invoice (DID), the following modifiers are not allowed:
  • 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 DID modifier:
  • Issues an Itinerary only from the itinerary printer.  No MIR or ticket is sent unless combined with other modifiers.
  • This modifier can generate an itinerary from a Non-Air PNR.
  • Does not require form of payment, commission, or carrier override.
  • If used with GIF or GIN modifiers, no fare quote required.
  • Open to Buy not down-dated.
  • Does not produce a ticket.
    
• Option P, Pocket Itinerary (DPD), cannot be used with the <UpdateModifiersMods> request.

Section 2: Detailed Description

Request:

Unless otherwise specified, use ALL CAPS in any request data.

The following steps are required to carry out this task:

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 type for normal.

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_1_0_s11

DocProdFareRequote_1_0_s12