Task: Passive Segment Sell

The Passive Segment Sell task adds non-air (car, hotel, tour, etc.) passive sells to a PNR/BF. Passive segment sells are used primarily to perform conversion of agencies to the Galileo system. When this task is used for the sale of auxiliary segments (hotel, car, surface, air taxi, and tour), the segments are process via an Airline code rather than a hotel/car vendor. Passive segment sells can only be requested through vendors that participate with Galileo International.

PNRBFManagement_13 accepts the <InsertSegAfterMods> element from the Air Segment Sell transaction and the <PassiveSegmentSellMods>. This ability combines the Insert After segment function with passive non-air sell.

Section 1: Short Answer

Transaction Name:

PNRBFManagement_13

Can any other transaction perform this task?

Previous versions of PNRBFManagement, PNRBFBuildModify_7_7_1, and PassiveSegmentSell_1_0 transactions can perform this task. Also, the Air Segment Sell transaction can perform air passive sells.

Can this task be performed in a sessionless environment?

This task must be performed in a sessioned environment. All the fields needed to create or retrieve a PNR are not included in <PassiveSegmentSellMods> (1062). <InsertSegAfterMods> (1020)  from the Air Segment Sell transaction can be added for easier inclusion of the passive sell segment.

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

The request and response are mostly identical on Apollo and Galileo.

On Galileo, in the <PassiveSegmentSellRequest>, the <City> element must be "SWI" for  due, paid, and text segments.

If differences are detected in the response, internal tables should be checked for synchronization of information.

Examples of these internal tables are:

List any industry-specific knowledge required to understand this task.

The user must understand the use of passive sell, the use of status codes, the insert after segment functionality, and the fundamentals of sessioning.

Section 2: Detailed Description

Request:

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

Three distinct types of non-air passive sell formats are hotel, car, and tour.

Hotel passive sell requires the following child elements:

 

Car passive sell requires the following child elements:

 

All other types of passive sell, such as surface, air taxi, tour, theatre, limousine, and insurance, require the following child elements:

 

In <PassiveSegmentSellRequest>, the vendor code <Vnd> is used to help translate the TUR type into those listed in the <Type> response of the <NonAirSeg> child element.

<DuePaidTextInd> information populates a standardized format that is built in the PNR/BF; for example Paid and Due indicators. If <DuePaidTextInd> is used, the paid indicator builds **AMOUNT PAID**PAIDnnn.nn** information in the PNR/BF. <DuePaidTextInd> also builds **AMOUNT OWED**DUEnnn.nn** information in the PNR/BF. The correct format is required for the additional processing to occur, such as a paid amount being deducted from an invoice.

<PassiveSegmentSellFreeformRequest> is used to add additional information. A blank line can be requested by filling in the <PropAddrInd> child element with two blanks. The two blanks enable blank lines to be inserted for later itinerary printing purposes.

In the <PassiveSegmentSellRequest>, on Galileo, the <City> element must be "SWI" for  due, paid, and text segments.

Prerequisite tasks:

All of the tasks involved in building or retrieving a PNR should be done BEFORE using the Passive Segment Sell task.

Expected response:

The expected response to the <PassiveSegmentSellMods> is the <PassiveSegmentSellResponse>. The response consists of a <NonAirSeg> child element.

Error and warning responses:

Errors are returned as host application errors.

Follow-on requests:

The following table lists common status codes that can be use to perform follow on activities when using passive sell and status codes in a PNR/BF.

Possible Status Codes For Apollo and Galileo:

 

Status Code

System:

A − Apollo
G −Galileo

Type:

H − Hotel
C − Cars

Description

AK

G

-

Apollo: N/A.

Galileo: Confirmed outside Galileo system. No message sent when canceled.

AL

G

-

Apollo: N/A.

Galileo: Waitlisted outside Galileo system. No message sent when canceled.

AN

G

-

Apollo: N/A.

Galileo: Requested outside Galileo system. No message sent when canceled.

BK

A and G

H and C

Apollo: Booked Confirmed with OA. Generates message if airspace is cancelled, or if N:, P:, or GFAX are changed or added.

Galileo: Booked outside Galileo system – messages still sent and received.

BL

G

-

Apollo: N/A.

Galileo: Waitlisted outside Galileo system – messages still sent and received.

BN

G

-

Apollo: N/A.

Galileo: Requested outside Galileo system – messages still sent and received.

DL

A

-

Apollo: Deferred from waitlist.

Galileo: N/A.

FS

G

-

Apollo: N/A.

Galileo: Sold on free sales basis.

GK

A

-

Apollo: Group Confirmed (OA only XK not allowed – does not generate a message if cancelled.

Galileo: N/A.

HK

A and G

H and C

Apollo and Galileo: Holds Confirmed. Generates message if cancelled.

HL

A and G

H

Apollo and Galileo: Have Waitlisted.

HN

A and G

H

Apollo and Galileo: Have Requested. No reply received.

HS

G

-

Apollo: N/A.

Galileo: Have sold, inventory adjusted.

HX

G

-

Apollo: N/A.

Galileo: Have canceled (by airline). Call carrier.

IN

A and G

H

Apollo and Galileo: If not holding, need.

IS

A and G

-

Apollo and Galileo: If not holding, sell.

IX

A and G

C

Apollo and Galileo: If holding, cancel.

KK

A and G

H and C

Apollo and Galileo: Confirming Segment.

KL

A and G

H

Apollo and Galileo: Confirming from waitlist.

LL

A and G

-

Apollo and Galileo: Waitlist.

MO

A

-

Apollo: Manual Override for car, hotel, and Apollo direct sell.

Galileo: N/A

NA

G

-

Apollo: N/A

Galileo: Need specified segment or the alternate.

NN

A and G

-

Apollo and Galileo: Need segment.

NO

A and G

H and C

Apollo and Galileo: No action taken.

OX

A and G

H and C

Apollo and Galileo: Cancel only if requested segment (space) is available.

PA

A

-

Apollo: Priority 1 waitlist – emergency travel. Oversales. Mishandled Passengers. Will be active up to 6 hours prior to flight.

Galileo: N/A.

PB

A

-

Apollo: Priority 2 waitlist.

Galileo: N/A.

PD

A

-

Apollo: Priority 4 waitlist.

Galileo: N/A.

PN

A and G

H and C

Apollo and Galileo: Pending need.

RR

A and G

-

Apollo and Galileo: Reconfirmed (International flights)  Can be added with change segment status entry.

SC

A

-

Apollo: Schedule change confirmed.

Galileo: N/A.

SS

A and G

H

Apollo and Galileo: Sell segment.

TK

A and G

-

Apollo and Galileo: Schedule change confirmed (sold segment) either time or new flight.

TL

A and G

-

Apollo and Galileo: Schedule change confirmed time change on a waitlisted segment.

TN

G

-

Apollo: N/A.

Galileo: Requested: advise client of new timings.

UC

A and G

H and C

Apollo and Galileo: Unable, wait list closed.

UN

A and G

H and C

Apollo and Galileo: Unable, not offered, flight no op. Flight had only minor time change or class change (UN followed by HK with new times).

US

A and G

H and C

Apollo and Galileo: Unable to accept sale – flight closed – have waitlisted.

UU

A and G

H

Apollo and Galileo: Unable, have waitlisted.

WK

A

-

Apollo: Was confirmed.

Galileo: N/A.

WL

A

-

Apollo: Was waitlisted/ flight is not operating due to schedule change.

Galileo: N/A.

XK

A and G

H and C

Apollo and Galileo: Delete/suppress.

XX

A and G

H and C

Apollo and Galileo: Cancel.

Section 3: Tables

Request (Input) Tags

<PassiveSegmentSellMods>

Terminal Equivalents:

Apollo: 0HTL, 0TUR, 0CAR

Galileo: 0HTL, 0TUR, 0CAR

Ordering

KLR

Min/Max

KLR Name

A

SQP1

1–1

<PassiveSegmentSellRequest>

B

SQP2

0–M*

*Note: M indicates many.

 

Response (Output) Tags

 <PassiveSegmentSellResponse>

 

Ordering

KLR

Min/Max

KLR Name

 

IT07

1–1

<NonAirSeg>

 

Related Samples

PNRBFManagement_13_s6

PNRBFManagement_13_s80