SalesReport 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.

Comment describing your root element1
Date in ISO 8601 format (yyyy-mm-dd). 0..1 2001-12-25
Pseudo city code. 0..1 LM21
Refund report stored only for previous three months and current month.0..1
Date in ISO 8601 format (yyyy-mm-dd). 0..1 2001-12-25
Date in ISO 8601 format (yyyy-mm-dd). 0..1 2001-12-25
Ticket number (including the leading 3 digit airline code).

0..1 2174851913640
Airline code or number. 0..1 LH or 220


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