CurrencyConversion 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
<CurrencyConversionRS>
Currency conversion 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>
<Conversion>
Conversion 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.
<From>
From conversion group1
<Amount>
The currency amount in the currency converted from which was specified in the request.
The amount is returned without decimal sign. See Attribute NumberOfDecimals.

1 20000
@NumberOfDecimals
The number of rightmost digits of Amount to be interpreted as decimal digits. That is, if Amount is "12590" and NumberOfDecimals is "2", the amount is "125.99" units of currency.
For the From/Amount, the @NumberOfDecimals is the same as specified in the request.

1 2
</Amount>
<CurrencyCode>
ISO 3-letter currency code of the currency converted from.

1 USD
</CurrencyCode>
</From>
<To>
To conversion group1
<Amount>
The currency amount in the currency converted to resulting from conversion of the amount specified in the request.
The amount is returned without decimal sign. See Attribute NumberOfDecimals.

1 18950
@NumberOfDecimals
The number of rightmost digits of Amount to be interpreted as decimal digits. That is, if Amount is "12590" and NumberOfDecimals is "2", the amount is "125.99" units of currency.

1 2
</Amount>
<CurrencyCode>
ISO 3-letter currency code of the currency converted to.

1 USD
</CurrencyCode>
</To>
<ConversionRate>
Rate used to calculate conversion. 1 7381
@NumberOfDecimals
Decimal position in fare amount. 0..1 2
</ConversionRate>
<Rounding/>
The last decimal digit of To/Amount may be rounded. "Rounding" specifies the interger value between 1 and 9, below which the following decimal place was rounded down, instead of up.
E.g: If "Rounding" is 5:
1.234 is rounded down to 1.23
1.235 is rounded up to 1.24

1 5
<Remark/>
Remark on currency conversion. 0..N BSR conversion of USD to FRF via EUR
</Conversion>
</CurrencyConversionRS>

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