Task: Update Pocket Itineraries

Updates a specific stored fare within the itinerary, such that the pocket itineraries will be issued.

Section 1: Short Answer

Transaction Name:

DocProdFareRequote_5

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

No, only DocProdFareRequote_5 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 available on the Apollo system 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).
• If the Pocket Itins field is set, the optional Pocket Itins Destination of H (home) or S (satellite) can be set.

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

• A PNR/booking file must exist.
• Not valid with the following modifiers:
  • Modifier 9P – Print boarding pass only
  • 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 DID – Itinerary only
  • Modifier DAD – Issue Non-Accountable MIR only

Section 2: Detailed Description

Request:

1. Create the PNR/booking file with a fare.
2. The fare number will be in <FareNumInfo>.
3. If the Pocket Itins field is set, the optional Pocket Itins Destination of H (home) or S (satellite) can be set. The Pocket Itins is an option in <DocumentSelect>.

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_5_s16