Check identifier 33001 — Confirmation

An * after a field or group name marks a mandatory field or a mandatory group. The type is beside it; where the value ends up in the EDIFACT segment is shown by the info icon next to the field name.

The status column carries two vocabularies because the manual answers two questions: on a group row, Muss, Soll or Kann states whether the EDIFACT segment must be present; on a field row, X states that this qualifier is used in this check identifier. Both are kept exactly as the source records them.

For this check identifier, the application handbook lists 67 rows. They appear in the order of the handbook, indented by segment: a row without a data element opens a segment, the rows below it are its data elements.

The Condition column names the markers under which the handbook ties a row to a prerequisite; their free text is below the table.

The test data contains one transaction for this check identifier under the message type remadv. Each is stored twice — as a EDIFACT message and as a BO4E JSON. That both representations show the same transaction has been recalculated, not assumed: interchange control reference, message reference number, document number, message date, sender and recipient match in all 517 pairs of the format version; check identifier, transaction number and location ID wherever both representations carry them. Not a single attribute contradicts.