| Id | Business Term | Card. | Definition | |
|---|---|---|---|---|
|
BT-001
|
1..1 |
An identification of the specification containing the total set of rules regarding semantic content, cardinalities and business rules to which the data contained in the instance document conforms. |
||
|
BT-002
|
1..1 |
Identifies the business process context in which the transaction appears, to enable the receiver to process the document in an appropriate way. |
||
|
BT-003
|
1..1 |
An MLS instance must have an identifier. The identifier enables referencing the transaction for various purposes such as from other transactions that are part of the same process. |
||
|
BT-004
|
1..1 |
The date on which the MLS was issued. Must not contain time zone information. |
||
|
BT-005
|
1..1 |
The time assigned by the sender on which the MLS was issued. Must contain time zone information and should be in UTC. |
||
|
BT-006
|
1..1 |
Identifies the sender party’s electronic address. |
||
|
BT-007
|
1..1 |
Identifies the sender party’s electronic address scheme. |
||
|
BT-008
|
1..1 |
Identifies the receiver party’s electronic address. |
||
|
BT-009
|
1..1 |
Identifies the receiver party’s electronic address scheme. |
||
|
BT-010
|
1..1 |
Contains the overall response code. |
||
|
BT-011
|
0..1 |
Contains the human readable overall response text. |
||
|
BT-012
|
1..1 |
The reference to the original business document transmission via the unique identifier of the business message envelope (SBDH) of the original business document. |
||
|
BG-001
|
0..n |
This list contains all issues that share the same location. In case of a negative MLS, at least one such element must be present. |
||
|
BT-013
|
1..1 |
Contains the location of the issue, if it can be determined. |
||
|
BG-002
|
1..n |
Contains a list of all issues that are related to the same issue location. |
||
|
BT-014
|
1..1 |
Contains the human readable description of this particular issue. |
||
|
BT-015
|
1..1 |
Contains the classification of this particular issue. |