Task: Insert After

The Air Segment Sell allows for the functionality "InsertAfter" which updates the AAA with the segment number to be inserted after - allowing the user to place new air segments within an existing itinerary. If the objective is to maintain date and sequence continuity within the itinerary, the new segments must be inserted after the appropriate previous segment, whether that segment is an air, car, or hotel segment.

Note: For readability and continuity, it is recommended that an itinerary be stored in chronological order. However, itineraries are not always booked in chronological order. Examples of changes to an itinerary that require inserting an air segment include:

• Often a user reserves the air segment first, then reserves car or hotel segments later.

• An itinerary that started out as a simple "Point A to Point B" becomes more intricate with additional destinations added between Points A and B.

• An itinerary is affected due to flight cancellations or schedule changes that require alternate air reservations in place of the original reservations.

Section 1: Short Answer

Transaction Name: 

PNRBFManagement_49

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

Previous versions of PNRBFManagement, PNRBFBuildModify_7_7_1 and AirSegmentSell_6_0 transaction can perform this same task.

Can this task be performed in a sessionless environment?

It can be performed in both sessioned and sessionless environments.

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

Yes.

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

Not applicable.

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

Not applicable.

Section 2: Detailed Description

Request:

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

In order for the AAA to be updated and set to ‘Insert After' mode, there needs to be a segment in the itinerary. The segment number within the <InsertSegAfterMods> (1020) needs to correlate with the segment number in the itinerary (i.e., segment number to insert after is ‘02’ in the <InsertSegAfterMods> and therefore the itinerary needs to have segment 02 in order for the AAA to be set up in ‘Insert After’ mode).

Required data:  <SegNum>

For ‘Insert After’, a segment needs to exist in the itinerary and this can be achieved by selling an air segment or an ARNK segment via the <AirSegSellMods> (1060).

Prerequisite tasks:

There are no prerequisite tasks.

Expected response:

Response received with no data (return code is ‘0’).

Error and warning responses:

If an agent’s pseudo is set up as Auto Segment Placement (ASP) user:

<ErrText>:  Number of arrays, delimiter character, level number, version number, error code, tag ID in error, error text.

Scenario:  Agent is set up in ASP (Auto Segment Placement) mode.

• Error:  RESTRICTED – AUTO SEGMENT PLACEMENT USER (1G)

Follow-on requests:

There are no required follow-on requests.

 Section 3: Tables

Request (Input) Tags

Response (Output) Tags

Additional Information

PNRBFManagement_49 can be used for requesting air segments from the Galileo and Apollo systems in the form of a direct sell, reference sell (via general and carrier specific availabilities), rebook/cancel via direct sell, and rebook/cancel via reference sell (via general and carrier specific availabilities). Segments are sold according to the class of service. Generally, it is recommended to store the associated fare quote when the segment is sold, unless the segment is ticketed immediately. (Stored fares are required on Galileo and optional on Apollo). Because fare quotes can change at any time prior to ticketing, storing the fare provides a history of the fare that was quoted to the traveler that can be compared against a later, quoted or ticketed fare.

Air segments may be sold with or without an availability call being made first. However, an initial check of a flight's availability can help prevent frustration and confusion. In selling a flight, the user has basically three (3) types of request codes available:

• NN ('need need') - Considered a "regular sell." The passenger has selected a specific flight on a specific day and is indicating a confirmed seat is desired. When booking a flight in a regular sell, the passenger must know the airline, flight number, class of service, date of departure, number of travelers in the party, and origin and destination.
• LL ('list list') - This code is used to 'waitlist' a passenger on a flight that is already showing fully booked. It is a request to be put on a list, in the event another traveler cancels his/her flight reservation. Normally, a passenger will follow a waitlist request with a regular sell on an alternate flight as backup. When waitlisting a flight, the passenger must know the airline, flight number, class of service, date of departure, number of travelers in the party, and origin and destination.
• NO ('need open') - This code is used when the passenger knows only the airline, and origin and destination required, but may not sure of either the departure date, departure time or both. Because the actual flight might be selected just hours prior to departure, open segments are often booked in the class of service that represents the lowest unrestricted fare available. When this type of air segment is ticketed, the word 'Open' appears where the flight number is normally shown.

PNRBFManagement_49 provides the ability to sell an ARNK segment (arrival unknown) as well as provides an ‘insert after’ function. If an insert after is submitted, the segment(s) are inserted after the specified after. Flight segments are sold and added to the reservation. Additional flight segments may be added to an existing reservation.

To use this transaction, a user should have an agent sign-on. For ‘insert after’, AAT needs to be set up for non-ASP user (SASP field = NO).

Related Samples

PNRBFManagement_49_s13