Task: Issue with MCO

Section 1: Short Answer

Transaction Name:

DocProdFareManipulation_8

Can this task be performed in a sessionless environment?

This task is used in sessioned environments. The Booking File data must be available in order to process this request.

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

The request and response are available only on Galileo.

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

None.

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

Not applicable.

Section 2: Detailed Description

Request:

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

Prior to issuing the MCO, the data for the MCO must be created and stored. Then, referencing the MCO number, the request to issue the MCO can be performed.

Prerequisite tasks:

The Booking File that contains the requested MCO information must be available. Also, a ticketing output device must be linked to the pseudo.

Expected response:

See below.

Error and warning responses:

The following error messages are returned from Category 35 fares:

9095 – NET TICKET DATA MAY NOT BE MODIFIED
To resolve, cancel it and re-quote for published fares or other fare types.
9096 – UNABLE TO TICKET – NET FARE TOUR CODE EXCEEDS MAXIMUM LENGTH
To resolve, cancel and re-quote, changing parameters to get a new quote, such as a public fare, specific fare, etc.
9097 - NOT AUTHORISED TO TICKET THE FILED FARE. CANCEL AND REFILE
To resolve, cancel the stored fare and re-quote as own identity.
9099 – INVALID CAT35 COMMISSION RETURNED. CANCEL AND REFILE
To resolve, cancel and re-quote, changing parameters to get a new quote, such as a public fare, specific fare, etc.

Follow-on requests:

There are no specific follow-on requests associated with this request.

Section 3: Tables

Request (Input) Tags

<TicketingMods>

Terminal Equivalents:

Apollo: N/A

Galileo: MCOPnn

Ordering	KLR	Min/Max	XML Tag
	DP27	1 – 1	<EndorsementBox>
	DPM2	1 – 1	<MCOIssue>
	DPMN	1 – 1	<MCONumber>

Response (Output) Tags – Normal Response for 1G

<Ticketing>

Ordering	KLR	Min/Max	XML Tag
A	DPFI	0 – 1	<FareNumInfo>
B	DPTK	0 – 1	<TicketingControl>
C	DPRL	0 – 1	<RecordLocator>
D	TEXT	1 – 3	<TextMsg>

Response (Output) Tags – Error Response for 1G

<Ticketing>

Ordering	KLR	Min/Max	XML Tag
A	DPFI	0 – 1	<FareNumInfo>
B	DPTK	0 – 1	<TicketingControl>
C	DPRL	0 – 1	<RecordLocator>
D	EROR	0 – 1	<ErrText>

Related Samples

DocProdFareManipulation_8_s5

Additional Information

This task can also be performed by XML transaction MicellaneousChargeOrder_1_0. All of the KLR-level elements listed above are the same, only the child elements are different.