Task: ARNK Sell

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

Section 1: Short Answer

Transaction Name: 

PNRBFManagement_37

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

Previous versions of PNRBFManagement, 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:

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

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

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-1 (1V)

1-99 (1G)

<ARNKSellMods>

Response (Output) Tags

<AirSegSell>

 

 

 

Ordering

KLR

Min/Max

XML Tag

 

A

SRS1

1-1 (1V)

1-99 (1G)

<AirSell>

 

B

EROR

1-1 (1V)

1-99 (1G)

<ErrText>

 

Additional Information

PNRBFManagement_37 can be used for requesting air segments from the Galileo and Apollo systems. There are several functions that can be performed:

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. Three basic types of request codes are available for selling a flight:

PNRBFManagement_37 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_37_s53