TicketVoid request message

Tabular overview of all nodes, which may occur in this message. See legend below for description of table columns.
Note: Some sibling elements or complete sub-trees of the hierarchy may be defined as mutually exclusive alternative choices. This information cannot be expressed in this tabular overview. Please refer to schema diagram for a graphical representation of the message schema.

NodeDescriptionValuesOccursExample
<TicketVoidRQ>
Comment describing your root element1
<IATA/>
IATA number of the agency originating the request.
1 123456
<PseudoCityCode/>
Pseudo City Code of the agency requesting the void/cancel. Used to verify if it has the authority for this request.
1 LNJ2
<TicketNumber/>
The 13-digit number of the ticket to be voided.
1 0012345678912 NOTE: In case of a conjunctive ticket, all tickets belonging to this set will be voided.Hence, it is not necessary to specify all ticket numbers of the tickets forming part of the conjunctive set.
<RecordLocator/>
The record locator of the PNR from which the ticket has been issued.1
</TicketVoidRQ>

Legend

ColumnDescription
NodeName of message node (element or attribute). Nodes in bold type are mandatory, if their parent element occurs in the message. Point mouse cursor at table cell to view complete XPath.
DescriptionDescription of meaning and usage of the node.
ValuesList of predefined values (each in square brackets) or range of values ("[a] to [z]") allowed for the node, if formally defined in the schema.
OccursMinimum and maximum number of times the node must/may occur, if its parent element occurs in the message. Examples:
0..3 Node is optional and may occur up to 3 times.
1..N Node must occur at least one (mandatory) and may occur any number of times.
2 Node must occur exactly twice.
ExampleExample value for the node.

XML Schema documentation generated with XX/1 server