Task: Issue Ticket

Issues a ticket for a specified fare or an MCO within a PNR or BF. All modifier updates must be stored with the fare prior to issuing the ticket or the MCO. No modifiers can be applied at the time of issuance.

Section 1: Short Answer

Transaction Name:

DocProdFareManipulation_4_0

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

No.

Can this task be performed in a sessionless environment?

No.

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

Yes, they are identical.  With the exception of the Detailed Billing Mask processing (DPDB KLR), which is only on the Galileo system.

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

Linkage must be set up to a printer.  If an itinerary and MIR are required, this linkage will need to set up as well.

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

1. A booking/PNR must exist.

2. A fare must exist.
3. Printer linkage must be set up.

Section 2: Detailed Description

Request:

Following are the steps required to carry out this task:

1. The PNR/Booking file must be created with a stored fare.
2. Linkage must be set up to the printer.
3. Send the fare number in the <FareNumInfo>.
4. Send the transaction type in the <TicketingControl>.
5. The <ElectronicTicketFailed> will contain alternate ticketing information if the electronic ticket failed.

Prerequisite tasks:

• A booking/PNR must exist.
• A fare must exist.
• Printer linkage must be set up.

Expected response:

• <FareNumInfo> (KLR DPFI) will contain the fare number.
• <TicketingControl> (KLR DPTK) will contain the control information for ticketing. It will have the “OK” option for transaction type. If more information is needed, the appropriate response will be used. For example, if the FAX number is needed the FX option will be used. When Extended Billing Data (EBD) is required by the credit card vendor (when FOP is CC), then a “DB” transaction code will be returned.
• <RecordLocator> (KLR DPRL) will have the record locator.
• <DetailedBillingMask> (KLR DPBD) will be returned to be filled in with Detailed Billing Mask data when the transaction type in <TicketingControl> is “DB”.

Error and warning responses:

• If printer linkage is not established the following error response will appear:
  ERROR 42 – INVALID ND LINKAGE
• If there isn’t a form of payment the following error response will appear:
  ERROR 4366 – FORM OF PAYMENT REQUIRED

Follow-on requests:

None.

Section 3: Tables

Request (Input) Tags

Response (Output) Tags