Task: Display Document Numbers

The task displays document numbers (ticket numbers).

Section 1: Short Answer

Transaction Name:

DocProdFareManipulation_22

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

No other transaction can perform the same task.

Can this task be performed in a sessionless environment?

No, the task cannot be performed in a sessionless environment as a PNR is required for the task to be accomplished.

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

The responses are identical on both Apollo and Galileo. The only difference between the two systems is that stock control numbers (i.e., first stock control number and last stock control number) differ in length. In Apollo, the length of the first stock control number is 8 alphanumeric characters, and the length of the last stock control number is 2 characters. In Galileo, the length of the first stock control number is 10 alphanumeric characters, and the length of the last stock control number is 3 characters.

List any industry-specific knowledge required to understand this task in terms of the specific business process.

The following knowledge is required for this task:

Loading TINS.
Linking printers.
Basic reservation, fare, and ticketing.

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

None.

Section 2: Detailed Description

Request:

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

Following are the steps required to carry out this task:

Linkage must be set up to the printer.
Ticket Stock needs to be available.
TINS must be available.
The PNR/Booking file must be created with a stored fare.
Ticketing modifiers need to be stored with the fares.
Document/Ticket must be issued.
One <ETicketNum> (DPHT KLR) (Control Information for Ticket Number) per ticket number is thrown out.

Prerequisite tasks:

A ticket should be issued successfully.

Expected response:

The response is <ETicketNum> (DPHT KLR) (Control Information for Ticket Number KLR) with the following fields:

Field Name (<Name>)
First Stock Control (<FirstStockCtrl>)
Last Stock Control (<LastStockCtrl>)
Airline Code (<AirV>)
First Ticket Number (<FirstTkNum>)
Last Ticket Number (<LastTkNum>)
Itin/Invoice Number (<ItinInvNum>)
Currency (<Crncy>)
Fare (<Fare>)
Ticket Type (<TkType>)
Date (<Dt>)
Time (<Tm>)

Error and warning responses:

Not applicable.

Follow-on requests:

None.

Section 3: Tables

Request (Input) Tags

<TicketNumbersMods>		Terminal Equivalents:			Apollo *HT		Galileo *HTI
	Ordering		NWB	Min/Max		XML Tag
			<TicketNumbersMods>	1 - 1		<TicketNumbersMods>

Response (Output) Tags

<TicketNumberData>
	Ordering	KLR	Min/Max	XML Tag
	A	DPHT	1 - 1	<ETicketNum>

Related Samples

DocProdFareManipulation_22_s21

DocProdFareManipulation_22_s23