Task: Check Electronic Ticket Eligibility

Section 1: Short Answer

Transaction Name:

DocProdETicketCheck_1_0

Can any other transaction(s) perform this same task

No, only DocProdETicketCheck_1_0 can perform this task.

Can this task be performed in a sessionless environment? I

No. However, future development may provide use in a sessionless environment.

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

Yes, both the request and response are identical, except the <PlatingAirVMod> is required in the request on 1G, but optional on 1V. See Section 2.

Industry-specific knowledge required to understand this task:

The end user must have an understanding of the booking process.

Special limits or distinct restrictions:

Section 2: Detailed Description

Request

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

To check itineraries for e-ticket eligibility with the <EligibilityMods> (4042 1.0 Data Record):

  1. Book the itineraries.
  2. Enter the segment numbers of the booked itineraries with the <AssocSegs> tag. This tag is optional. If an <AssocSegs> tag is not sent in the request, all segments in the booked itineraries are checked for e-ticket eligibility.
  3. Enter the plating carrier with the <PlatingAirVMod> tag, which is optional on 1V, but mandatory on 1G. If the <PlatingAirVMod> is not sent in the request, the host uses the first airline code of the booked itinerary as the plating carrier.
  4. If required to enter a pseudo city code, submit the pseudo city code with the <PseudoCity> tag. If the <PseudoCity> is not sent, the host uses the booking pseudo city code for the eligibility checks.
  5. Submit all tags in a single request. The host receives the request and performs the following checks by default.

Prerequisite tasks:

Book the itinerary.

Expected response(s):

The host returns the <Eligibility> (4043 1.0 Data Record) which determines if the booked itinerary is eligible for electronic ticketing. If the eligibility checks pass, a blank <DPOK> tag is returned. The <PlatingAirVMod> is also returned to indicate which plating carrier was used to perform the checks.

If any of the checks fail, an <ErrText> tag is returned. The tag describe which checks failed.

Error and warning responses:

Error messages are a maximum of 64 characters and returned in the format:

ERROR # - descriptive text

The following error messages can display:

 

Core

Error Message

Reason for Error

Both

ERROR 26 - UNABLE TO PROCESS

Check 10 –AAT TKLS check

Both

ERROR 4951 - UNAUTHORIZED/INVALID PLATING CARRIER CODE_

Check 20 – AAT AUTH check failed.

Both

ERROR 26 - UNABLE TO PROCESS

Check 30 – AAT NOET check

Both

ERROR 4952 - ELECTRONIC TICKETING NOT AVAILABLE FOR_

Check 50 – BSP Plating Carrier check failed.

Both

ERROR 4953 - UNABLE - ITINERARY EXCEEDS 16 SEGMENTS

Check 60 – Maximum Itinerary segments check failed.

Both

ERROR 4954 - INTERLINE ELECTRONIC TICKET AGREEMENT NOT FOUND

Check 100 – Interline Table check failed.

Both

ERROR 4955 - ITINERARY NOT ELIGIBLE FOR ELECTRONIC TICKET

Check 80 – BSP E-eligible check failed.

Both

ERROR 4956 - NO ACTIVE AIR SEGMENTS SELECTED

Check 100 – Interline Table check requested when no air segments selected.

1G

ERROR 9052- CARRIER COMBINATION NOT ALLOWED

Check 200 – Plating carrier validation

1G

ERROR 4957- PLATING CARRIER REQUIRES

Plating carrier code requires for this entry

Both

ERROR 4970 - INVALID ET CHECK NUMBER

ET checks format error.

Both

ERROR 4971 - INVALID PSEUDO CITY CODE

Pseudo City Code not valid.

Both

ERROR 4972 - INVALID PLATING CARRIER

Plating carrier format error.

Both

ERROR 26 - UNABLE TO PROCESS

Other errors (system errors, inactive check requested and so on).

Note: Other errors can display. Other programs on the host can issue errors before the e-ticket validation utility is called.

Follow-on requests:

None.

Section 3: Tables

Request (Input) Tags

<EligibilityMods>

Terminal Equivalents:

Apollo: None

Galileo: None

Ordering

KLR

Min/Max

XML Tag

Any

DP0H

0-1

<PlatingAirVMod>

Any

DPII

0-1

<AssocSegs>

Any

DPCH

0-1

<ETicketCheckType>

Any

DPPS

0-1

<PseudoCity>

 

Response (Output) Tags

<Eligibility>

 

Ordering

KLR

Min/Max

XML Tag

A

DPOK

0-1

<DPOK>

B

DP0H

0-1

<PlatingAirVMod>

 

<Eligibility>

 

Ordering

KLR

Min/Max

XML Tag

 

EROR

0-1

<ErrText>

 

Related Samples

DocProdETicketCheck_1_0_1

DocProdETicketCheck_1_0_2

DocProdETicketCheck_1_0_3

DocProdETicketCheck_1_0_4

DocProdETicketCheck_1_0_5

DocProdETicketCheck_1_0_6