Cryptic response 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
<CrypticRS>
Cryptic response root element1
@version
Version number. 0..1 1.0
<InfoGroup>
Error and information group0..1
<ForInfo>
Information group0..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
<Text/>
Information text or error text. 1..N Free flow text. Example: Invalid flight number
</ForInfo>
<Error>
Error group0..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>
<Screen>
Element containing the response to the cryptic entry. 1 AN15MARMIACDG ** AMADEUS AVAILABILITY - AN ** CDG CHARLES DE GAUL.FR 42 FR 15MAR 0000 THE HEART OF PARIS : MERCURE MONTPARNASSE AND MERCURE TOUR EIFFEL SUFFREN - BOOK RIGHT NOW - >HARTPARMTP OR >HARTPARFRA 1 AF 095 P9 F8 A2 J9 C9 DL Y9 /MIA CDG2F 545P 815A+1E0/744 8:30 K9 H9 WL TL GR BR 2AF:DL8613 C7 D0 I0 Y7 B7 M7 H0 MIA CDG2F 545P 815A+1 0.744 8:30 Q0 K0 L0 U0 3 AA 062 F7 A0 J7 Y7 B7 H7 K7 MIA CDG2A 730P 1030A+1E0.763 9:00 M7 V7 N7 S7 Q7 L0 G7 4 UA 914 F4 C4 D4 Y4 B4 M4 H4 MIA CDG 1 115P 705A+1E1.EQV 11:50 Q4 A4 5 US 026 FR Y9 B9 M9 HR K0 QR MIA CDG 1 305P 940A+1E1.EQV 12:35 VR J9 C9 6 DL1866 F4 A7 Y7 B7 M7 H7 Q7 MIA CVG 3 350P 626P E0.M80 7 K0 L0 U0 DL 044 J7 D7 I0 Y7 B7 M7 H0 CVG 3 CDG2C 700P 840A+1 0.777 10:50 Q0 K7 L0 U0 >
@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.
</Screen>
</CrypticRS>

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