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.
Node | Description | Values | Occurs | Example |
---|---|---|---|---|
<PNRCancelRS> | PNR cancel response root element | 1 | ||
@version | Version number. | 0..1 | 1.0 | |
<InfoGroup> | Error and information group | 0..1 | ||
<ForInfo> | Information group | 0..N | ||
@Source | Identifies the source of this element. In other words where the content originates from. Not limited to GDS, applicable to direct connect as well. | 0..1 | 1A, 1V, or other. | |
@SourceRef | PNR Record Locator associated to Source attribute. | 0..1 | ||
@Code | A code to uniquely identify a specific type of ForInfo message. Currently not returned for most ForInfo messages. | 0..1 | I00001 | |
@Lang | ISO language code. A two letter code as defined by ISO-639-1. | 0..1 | de | |
<Text/> | Information text or error text. | 1..N | Free flow text. Example: Invalid flight number | |
</ForInfo> | ||||
<Error> | Error group | 0..N | ||
@ErrorType | Type of error. | 1 | Air | |
@Source | Identifies the source of this element. In other words where the content originates from. Not limited to GDS, applicable to direct connect as well. | 0..1 | 1A, 1V, or other. | |
@SourceRef | PNR Record Locator associated to Source attribute. | 0..1 | ||
<Code/> | Error code or equipment type code. | 1 | 0104 (error code), 747 (equipment code) | |
<Text/> | Information text or error text. | 1..N | Free flow text. Example: Invalid flight number | |
<UnderlyingError> | Errors of the backend system can be returned here. | 0..N | ||
@Code | error code of the backend system. | 0..1 | ||
<Text/> | Information text or error text. | 0..N | Free flow text. Example: Invalid flight number | |
</UnderlyingError> | ||||
</Error> | ||||
<BackOffice> | Generic back office response container. Serves as a placeholder for any context specific content. | 0..1 | ||
</BackOffice> | ||||
</InfoGroup> | ||||
<Status> | PNR cancel result status. Values are: 0 = succesfull PNR cancellation 1 = error, PNR not cancelled If PNR was already cancelled before, the normalized error code XX08071 will be returned with Status 1. | 1 | 0 | |
@Source | Identifies the source of this element. In other words where the content originates from. Not limited to GDS, applicable to direct connect as well. | 0..1 | 1A, 1V, or other. | |
</Status> | ||||
<CancellationFee> | A fee to be paid resulting from the cancellation. | 0..1 | ||
@Amount | The amount of the cancellation fee. Integer value including decimal digits as specified by @NumberOfDecimals without decimal separator. | 1 | 1000 | |
<CurrencyCode> | Currency code. | 1 | USD | |
@NumberOfDecimals | Decimal position in fare amount. | 1 | 2 | |
</CurrencyCode> | ||||
</CancellationFee> | ||||
<CancellationNumber> | If Status = 0 and a vendor cancellation number exists, then vendor cancellation number is returned. For some backend systems (e.g. Expedia) it is possible that one booking can contain multiple hotel segments. If during cancellation of the booking not all hotel segments could be cancelled successfully only for the successfully cancelled ones a CancellationNumber will be returned, but the Status will be 1, because the booking still exists with some active hotel segments. | 0..N | ||
@ConfirmationNumber | Contains the confirmation number of the successfully cancelled hotel segment that belongs to the CancellationNumber. Makes easier identifyable which hotel segments were successfully cancelled. | 0..1 | ||
</CancellationNumber> | ||||
</PNRCancelRS> |
Column | Description |
---|---|
Node | Name 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. |
Description | Description of meaning and usage of the node. |
Values | List of predefined values (each in square brackets) or range of values ("[a] to [z]") allowed for the node, if formally defined in the schema. |
Occurs | Minimum 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. |
Example | Example value for the node. |
XML Schema documentation generated with XX/1 server