Task: ARNK Sell

Air Segment Sell allows for the selling of ARNK (Arrival Unknown) segments.

Section 1: Short Answer

Transaction Name:

PNRBFManagement_7_11

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

AirSegmentSell_6_0

Can this task be performed in a sessionless environment?

No, only in a sessioned environment.

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:

The ARNK segment can be sold at any time.

Required data: Not applicable.

Prerequisite tasks:

There are no prerequisite tasks.

Expected response:

Fields returned are <DispSeqNum> and <Status>, both of which are blank.

Error and warning responses:

EROR KLR: Number of arrays, delimiter character, level number, version number, <Err>, <KlrInErr>, <Text>.

In the following scenario, errors or warnings for 1G are blue and 1V are green.

Scenario: System error

Error: SYSTEM ERROR – IGNORE TRANSACTION RECOMMENDED n (1G)

Error: UNABLE TO PROCESS (1G)

Error: *SYSTEM ERROR* (1G)

Error: UNA PROC (1V)

Error: SYS ERROR OCCURRED (1V)

Follow-on requests:

There are no required follow-on requests.

Section 3: Tables

Request (Input) Tags

<AirSegSellMods>		Terminal Equivalents:			Apollo: Y		Galileo: Y or 0A
	Ordering		KLR	Min/Max		XML Tag
	A		SQA1 1.0	1-1 (1V) 1-99 (1G)		<ARNKSellMods>

Response (Output) Tags

<AirSegSell>
	Ordering	KLR	Min/Max	XML Tag
	A	SRS1 1.0	1-1 (1V) 1-99 (1G)	<AirSell>
	B	EROR 1.0	1-1 (1V) 1-99 (1G)	<ErrText>

Additional Information

PNRBFManagement_7_11 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_7_11 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).