Task: Display Ticket from a PNR

This task can be used by the client to produce additional travel documents (Electronic ticket receipt, Itinerary, etc.) for the passenger listed in the PNR/BF, using other related transactions.

Section 1: Short Answer

Transaction Name:

TicketInfoDisplay_5

Can this task be performed in a sessionless environment?

Yes.

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.

General PNR/BF knowledge, fares, and OB fees.

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

N/A

Section 2: Detailed Description

Request:

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

Retrieve by Record Locator can only be performed on the same core.

In a sessionless environment, a <PNRRetrieveMods> (2024) request is required to retrieve a PNR. See the Request section in Task: Display Canned Remarks from a PNR.

In sessioned environment, a PNR can be retrieved using <PNRRetrieveMods> within TicketInfoDisplay_5. The ticketing information may be retrieved at the same time within the same request.

A <ValidTicketInfoMods> (4038) should be used with the <AssocPsgrs> (DPPI) for requested passenger number, and the <TicketTypeMod> (DPRT) for type of tickets which will be returned (electronic, paper, or both).

Prerequisite tasks:

If this task is performed with a <PNRRetrieveMods> request – no prerequisite task is required.

If only a <ValidTicketInfoMods> is used, a PNR/BF should be retrieved. For example, a PNR/BF can be retrieved by Record Locator. See Task Display Canned Remarks from a PNR.

Expected response:

The expected response is the <PNRRetrieve> (2025) and the <ValidTicketInfo> (4039).

Error and warning responses:

The most common error response for the <PNRRetrieve> is an error that the Record Locator or File Address is not valid for a PNR/BF.

The <ValidTicketInfo> error responses are:

Follow-on requests:

If request was used in sessioned environment there are numerous follow on requests possible. You can display a fare, update PNR/BF, etc. It is highly recommended to End-transact or Ignore the PNR/BF. For example, with the PNRBFManagement transaction, follow the steps in Task Finish Active PNR/BF or Task Ignore Active PNR/BF.

Section 3: Tables

Request (Input) Tags

Retrieve by Record Locator (same core)

<PNRBFRetrieveMods>

Terminal Equivalents:

Apollo:  *123ABC

Galileo: *123ABC

 

Ordering

KLR

Min/Max

XML Tag

 

 

BP02

1 – 1

<PNRAddr>

 

 

BP06

0 – 1

<RequiredData>

Retrieve Ticket Information

<ValidTicketInfoMods>

Terminal Equivalents:

Apollo:

Galileo:

Ordering

KLR

Min/Max

XML Tag

A

DPPI

1-1

<AssocPsgrs>

B

DPRT

1-1

<TicketTypeMod>

Response (Output) Tags

Response by Record Locator (same core)

<PNRBFRetrieve>

If PNR/BF found

 

Ordering

KLR

Min/Max

XML Tag

 

A

CTRL

1 – 1

<Control>

 

B

BP07

0 – 1

<HeaderLine>

 

C

BP08

0 – 1

<GenPNRInfo>

 

D

BP09

0 – 1

<PostScript>

 

E

BP10

0 – 99

<LNameInfo>

 

F

BP12

0 – 99

<FNameInfo>

 

G

BP14

0 – 99

<FreqCustInfo>

 

H

BP16

0 – 99

<PhoneInfo>

 

I

BP32

0 – 1

<TkArrangement>

 

I

BP33

0 – 1

<TAUTkArrangement>

 

I

BP34

0 – 1

<TAWTkArrangement>

 

I

BP35

0 – 1

<TLTkArrangement>

 

I

BP36

0 – 1

<TAMkArrangement>

 

J

DPP0

0 – 1

<CreditCardFOP>

 

J

DPP1

0 – 1

<CheckFOP>

 

J

DPP9

0 – 1

<OtherFOP>

 

K

BP17 

0 – 1

<AddrInfo>

 

L

BP18

0 – 1

<DeliveryAddrInfo>

 

M

IT01

0 – 99

<AirSeg>

 

M

IT02

0 – 99

<AirSegOpAirV>

 

M

IT16

0 – 99

<AirSegDetail>

 

M

IT13

0 – 99

<ARNK>

 

M

IT03

0 – 99

<HtlSeg>

 

M

IT04

0 – 99

<HtlSegOptFlds>

 

M

IT05

0 – 99

<CarSeg>

 

M

IT06

0 – 99

<CarSegOptFlds>

 

M

IT07

0 – 99

<NonAirSeg>

 

M

IT09

0 – 99

<DuePaidInfo>

 

M

IT10

0 – 99

<FlygTaxiSeg>

 

M

IT11

0 – 99

<TourSeg>

 

M

IT12

0 – 99

<CruiseSeg>

 

M

IT14

0 – 99

<TrainSeg>

 

N

DPR1

0 – 99

<ItinRmk>

 

O

DPR1

0 – 99

<ItinRmk>

 

P

ST01

0 – 99

<SeatSeg>

 

P

ST02

0 – 9801

<SeatAssignment>

 

Q

BP19

0 – 255

<OSI>

 

R

BP20

0 – 255

<NonProgramaticSSR>

 

R

BP21

0 – 255

<ProgramaticSSR>

 

R

BP22

0 – 255

<ProgramaticSSRText>

 

S

BP23

0 – 1

<CustID>

 

T

BP24

0 – 1

<ProfileClientFileAssoc>

 

U

BP25

0 – 3

<CustomCheckRules>

 

V

BP26

0 – 255

<GenRmkInfo>

 

W

BP27

0 – 99

<VndRecLocs>

 

X

BP28

0 – 99

<VndRmk>

 

Y

DPIR

0 – 99

<InvoiceRmk>

 

Z

BP29

0 – 99

<QMinder>

 

AA

DPIR

0 – 99

<InvoiceRmk>

 

EE

BP40

0 – 99

<Email>

 

FF

BP41

0 – 1

<CorporateID>

 

GG

BP42

0 – 1

<DividedBookingInfo>

 

HH

BP45

0 – 99

<AdditionalID>

 

<PNRBFRetrieve>

If error occurred

 

Ordering

KLR

Min/Max

XML Tag

 

 

EROR

1 – 1

<ErrText>

Response Ticket Information

<ValidTicketInfo>

 

Ordering

KLR

Min/Max

XML Tag

A

DPHT

1-9 for e-tickets
1-25 for paper tickets

<ETicketNum>

B

DPPI

1 per DPHT

<AssocPsgrs>

C

DPSS

1-99 per DPHT

<AirSegInfo>

D

GFFC

0-1 per DPHT

<FareConstruction>

E

GFPF

0-1 per DPHT

<PsgrFacilityCharge>

F

GFGQ

0-1 per DPHT

<GenQuoteDetails>

G

DP27

0-1 per DPHT

<EndorsementBox>

H-Q

DP22

0-1 per DPHT

<BaggageAllowance>

H-Q

DPP0

0-1 per DPHT

<CreditCardFOP>

H-Q

DPP1

0-1 per DPHT

<CheckFOP>

H-Q

DPP9

1-3 per DPHT

<OtherFOP>

H-Q

DP0B

0-99 per DPHT

<OBFees>

H-Q

DP0G

0-1 per DPHT

<TaxExemptMod>

H-Q

DP28

0-1 per DPHT

<BulkTicket>

H-Q

DP29

0-1 per DPHT

<NonRefundBulkTicket>

H-Q

DP31

0-1 per DPHT

<GroupTour>

H-Q

DP32

0-1 per DPHT

<FreeTicket>

H-Q

DP33

0-1 per DPHT

<TourCode>

 

<ValidTicketInfo>

If Error Occured

Ordering

KLR

Min/Max

KLR Name

 

EROR

1-1

<ErrText>

Related Samples

TicketInfoDisplay_5_s1

TicketInfoDisplay_5_s4

TicketInfoDisplay_5_s5