Task: Update Ticket Validity Mod

This task updates a specified fare within the itinerary such that ticket validity (Not Valid Before/Not Valid After) is created or the current ticket validity (NVB/NVA) is modified.

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, the task cannot be performed in a sessionless environment. A PNR must exist with a stored fare to accomplish this task.

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

No. This task can only be performed on the Apollo system.

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

The user should have an understanding of Ticketing, Fares, and Reservation is required.

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

The following modifiers are not allowed with the Ticket Validity (NVA/NVB) modifier:

• Modifier DGD – Demand Global MIR

• Modifier DJD –  Non-Faring MIR to Remote location

• Modifier DND – Non-Ticketing MIR to remote

• Modifier DXD – Dual MIR

The following processing notes apply to the NVB and NVA modifiers.

• NVB/NVA modifiers can be used independently or together.

• NVB/NVA modifiers default to the entire itinerary with other modifiers.

• NVB/NVA modifiers can be used in conjunction with the ATFQ, Pricing Record, or ticketing entry.

• NVB/NVA modifiers can be deleted or modified from the ATFQ line.

• NVB/NVA dates are not compared against one another.

• NVB/NVA dates use the same date routine as the Pricing Record.

• No date analysis is made against the itinerary.

• Dates entered with these modifiers override those dates supplied by GlobalFares on outputs only.

• When the NVB/NVA modifiers are used as part of the Pricing Record build entry, the data becomes unchangeable within the Pricing Record Fill-in screen ($NME).
• Modifier input hierarchy remains the same (the HB entry will override the ATFQ, the ATFQ will override the PNR field).
• Pricing/Fare Construction Indicator (FCI): If the system outputs a pricing code of “0”, it checks to see if an NVA/NVB modifier is used. If so, the system changes the pricing code to “5” for agency issued tickets and “2” for United Airlines issued tickets.

• Dates are printed in the current NVB/NVA fields/boxes on the flight coupon and the Post Audit document.

• These modifiers output in current MIR 2 Labels.

• NVB - Fare Basis Section, Label A08NVBC, 7 bytes alphanumeric (DDMMMYY).

• NVA - Fare Basis Section, Label A08NVAC, 7 bytes alphanumeric (DDMMMYY).

• The Pricing/Fare Construction Indicator is part of the Transaction Number in Passenger Data Section, Label A02TRN.

Section 2: Detailed Description

Request:

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

Following are the steps required to carry out this task:

1. Create a PNR with a fare.

2. Send the fare number in the <FareNumInfo>.

3. Send the Ticket Validity (NVB and NVB modifier) in the <TicketValidity>.

Prerequisite tasks:

A PNR must be present on the AAA, with fares.

Expected response:

The response <UpdateModifiers> includes the <FareNumInfo> (which indicates the fare relationship) and the <DPOK> sub-elements.

Error and warning responses:

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

Follow-on requests:

None.

Section 3: Tables

Request (Input) Tags

Response (Output) Tags

Related Samples

DocProdFareRequote_1_0_s23