Check identifier 21010 — Status message
Check identifier 21010 · EDIFACT message type IFTSTA · Format version 202604
Data structure
| Structure (BO4E) | Description | Format | 21010 | Condition |
|---|---|---|---|---|
| stammdaten * | — | object | Must | — |
| MESSLOKATION [ ] * | — | object[] | Must | — |
| messlokationsId * 00010 | The metering location identification. This is the former metering point identifier, e.g. DE 47108151234567 | string | X | — |
| STATUSMITTEILUNG [ ] * | — | object[] | Must | — |
| auftragsstatus * 00020 | Order status | Enum Auftragsstatus | X | — |
GESCHEITERT | — | — | X | — |
ERFOLGREICH | — | — | X | — |
LIEFERUNG_GEPLANT | — | — | X | — |
GEPLANT | — | — | X | — |
ZUGESTIMMT | — | — | X | — |
WIDERSPROCHEN | — | — | X | — |
STOERUNGSFREI | — | — | X | — |
GESTOERT | — | — | X | — |
FESTGESTELLTE_STOERUNG | — | — | X | — |
VERMUTETE_STOERUNG | — | — | X | — |
ABGELEHNT | — | — | X | — |
BEENDET | — | — | X | — |
ANTWORT_DRITTER | — | — | X | — |
BESTAETIGT | — | — | X | — |
UMGESETZT | — | — | X | — |
ENFG_STROMSPEICHER_UND_VERLUSTENERGIE | — | — | X | — |
ENFG_ELEKTRISCH_ANGETRIEBENE_WAERMEPUMPEN | — | — | X | — |
ENFG_UMLAGEERHEBUNG_BEI_ANLAGEN_ZUR_VERSTROMUNG_VON_KUPPELGASEN | — | — | X | — |
ENFG_HERSTELLUNG_VON_GRUENEN_WASSERSTOFF | — | — | X | — |
ENFG_STROMKOSTENINTENSIVE_UNTERNEHMEN | — | — | X | — |
ENFG_HERSTELLUNG_VON_WASSERSTOFF_IN_STROMKOSTENINTENSIVEN_UNTERNEHMEN | — | — | X | — |
ENFG_SCHIENENBAHNEN | — | — | X | — |
ENFG_ELEKTRISCHE_BETRIEBENE_BUSSEN_IM_LINIENVERKEHR | — | — | X | — |
ENFG_LANDSTROMANLAGEN | — | — | X | — |
AENDERUNG_DER_DATEN | — | — | X | — |
KEINE_AENDERUNG_DER_DATEN | — | — | X | — |
ZEITREIHE_AKZEPTIERT | — | — | X | — |
ZEITREIHE_NICHT_AKZEPTIERT | — | — | X | — |
| positionsdaten [ ] * | — | object[] | Must | — |
| positionsnummer * 00030 | positionsnummer | integer | Must | — |
| transaktionsdaten * | — | object | Must | — |
| dokumentennummer * 00040 | EDIFACT reference from the BGM segment / BGM | string | X | — |
| fertigstellungsdatum * 00050 | Completion date / DTM+293 | string (date-time) | X | — |
| nachrichtendatum * 00060 | Creation date of the EDIFact / DTM+137 | string (date-time) | X | — |
| nachrichtenreferenznummer * 00070 | EDIFACT reference from the UNT segment / UTILMD UNT+21 | string | Must | — |
| pruefidentifikator * 00080 | Contains the check identifier from the EDIFact communication / RFF+Z13 | string | X | — |
| absender * | — | object | Must | — |
| rollencodenummer * 00090 | Specifies the code value of the market role. | string | X | — |
| rollencodetyp * 00100 | Indicates the type of the code. | Enum Rollencodetyp | X | — |
BDEW | — | — | X | — |
GS1 | — | — | X | — |
GLN | — | — | X | — |
DVGW | — | — | X | — |
| ansprechpartner | — | object | May | — |
| eMailAdresse 00110 | Email address | string | Must | — |
| nachname 00120 | Surname (family name) of the contact person | string | X | — |
| rufnummern [ ] | — | object[] | May | — |
| nummerntyp 00130 | Phone number type | Enum Rufnummernart | Must | — |
RUF_ZENTRALE | — | — | Must | — |
FAX_ZENTRALE | — | — | Must | — |
SAMMELRUF | — | — | Must | — |
SAMMELFAX | — | — | Must | — |
ABTEILUNGRUF | — | — | Must | — |
ABTEILUNGFAX | — | — | Must | — |
RUF_DURCHWAHL | — | — | Must | — |
FAX_DURCHWAHL | — | — | Must | — |
MOBIL_NUMMER | — | — | Must | — |
| rufnummer 00140 | rufnummer | string | Must | — |
| empfaenger * | — | object | Must | — |
| rollencodenummer * 00150 | Specifies the code value of the market role. | string | X | — |
| rollencodetyp * 00160 | Indicates the type of the code. | Enum Rollencodetyp | X | — |
BDEW | — | — | X | — |
GS1 | — | — | X | — |
GLN | — | — | X | — |
DVGW | — | — | X | — |
Application handbook (AHB)
| Structure (EDIFACT) | Description | Format | 21010 | Condition |
|---|---|---|---|---|
| UNH | — | — | Must | — |
006200010 | Message reference number | — | X | — |
0065 IFTSTA00020 | Multimodal status report | — | X | — |
0052 D00030 | Draft version | — | X | — |
0054 18A00040 | Edition 2018 - A | — | X | — |
0051 UN00050 | UN/CEFACT | — | X | — |
0057 2.0g00060 | Version number of the underlying BDEW message description | — | X | — |
| BGM | — | — | Must | — |
1001 Z0900070 | WiM message(s) | — | X | — |
100400080 | Document number | — | X | — |
| DTM | — | — | Must | — |
2005 13700090 | Document-/ message date/time | — | X | — |
238000100 | Date or time or time span, value | — | X | [931] [494] |
2379 30300110 | CCYYMMDDHHM MZZZ | — | X | — |
| SG1.NAD | — | — | Must | — |
3035 MR00120 | Message recipient | — | X | — |
303900130 | MP-ID | — | X | — |
3055 900140 | GS1 | — | X | — |
3055 29300150 | DE, BDEW (Bundesverband der Energie- und Wasserwirtschaft e.V.) | — | X | — |
3055 33200160 | DE, DVGW Service & Consult GmbH | — | X | — |
| SG1.NAD | — | — | Must | — |
3035 MS00170 | Document-/ message sender or sender | — | X | — |
303900180 | MP-ID | — | X | — |
3055 900190 | GS1 | — | X | — |
3055 29300200 | DE, BDEW (Bundesverband der Energie- und Wasserwirtschaft e.V.) | — | X | — |
3055 33200210 | DE, DVGW Service & Consult GmbH | — | X | — |
| SG2.CTA | — | — | Must | — |
3139 IC00220 | Information contact | — | X | — |
341200230 | Contact | — | X | — |
| SG2.COM | — | — | Must | — |
314800240 | Number / email address | — | X | (([939] [146]) ∨ ([940] [147])) ∧ [534] |
3155 EM00250 | — | X | [1P0..1] | |
3155 FX00260 | Fax number | — | X | [1P0..1] |
3155 TE00270 | Telephone | — | X | [1P0..1] |
3155 AJ00280 | further telephone | — | X | [1P0..1] |
3155 AL00290 | Mobile phone | — | X | [1P0..1] |
| SG14.CNI | — | — | Must | — |
149000300 | Transaction number | — | X | [911] |
| SG14.LOC | — | — | Must | — |
3227 17200310 | Reporting point | — | X | — |
322500320 | Identifier | — | X | [951] [505] |
| SG15.STS | — | — | Must | — |
9015 Z1000330 | MSB change under MsbG | — | X | — |
4405 Z1400340 | successful | — | X | — |
| SG15.RFF | — | — | Must | — |
1153 Z1300350 | Check identifier | — | X | — |
1154 2101000360 | WiM / status message (successful) from the MSBN to the NB | — | X | — |
| SG15.DTM | — | — | Must | — |
2005 29300370 | Completion date/time | — | X | — |
238000380 | Date or time or time span, value | — | X | ([UB3] [26] ∧ ([521] ⊻ [522])) ⊻ ([931] [117]) |
2379 30300390 | CCYYMMDDHHM MZZZ | — | X | — |
| UNT | — | — | Must | — |
007400400 | Number of segments in a message | — | X | — |
006200410 | Message reference number | — | X | — |
Conditions of this table
The free text of the 16 conditions referenced by the rows above. All conditions of the message type are listed in the condition index IFTSTA.
| Marker | Condition |
|---|---|
| [26] | If MP-ID in SG1 NAD+MR in the role NB |
| [117] | If MP-ID in SG1 NAD+MR in the role MSB |
| [146] | If code EM is present in DE3155 in the same COM |
| [147] | If code TE / FX / AJ / AL is present in DE3155 in the same COM |
| [494] | The date stated here must be the point in time at which the document was created, or a point in time before that |
| [505] | Note: Use of the ID of the metering location |
| [521] | Note: Point in time from which the MSBN actually takes over the metering point operation |
| [522] | Note: Point in time from which the gMSB takes over the metering point operation |
| [534] | Note: Only one piece of information may be transmitted in DE3148 |
| [911] | Format: Possible values: 1 to n, starting at 1 for each message and ascending consecutively |
| [931] | Format: ZZZ = +00 |
| [939] | Format: the character string must contain the characters @ and . |
| [940] | Format: the character string must begin with the character + and may only be followed by digits |
| [951] | Format: Metering point identifier |
| [1P0..1] | Note: This is the standard package if no condition applies, e.g. in the COM segment. |
| [UB3] | ([931] ∧ [932] [492] ∧ [490]) ⊻ ([931] ∧ [933] [492] ∧ [491]) ⊻ ([931] ∧ [934] [493] ∧ [490]) ⊻ ([931] ∧ [935] [493] ∧ [491]) |
Example message
UNA:+.? '
UNB+UNOC:3+4045399000053:500+4045399000015:500+{{date}}:{{time}}+M10NFZX3'
UNH+M0WXY2AY+IFTSTA:D:18A:UN:2.0g'
BGM+Z09+M04AL0RA'
DTM+137:202504041200?+00:303'
NAD+MR+4045399000015::293'
NAD+MS+4045399000053::293'
CNI+1'
LOC+172+DE00014545768S0000000000000003054'
STS+Z10+Z14'
RFF+Z13:21010'
DTM+293:202408302200?+00:303'
UNT+11+M0WXY2AY'
UNZ+1+M10NFZX3'[1 item
{6 fields
"data": {3 fields
"stammdaten": {2 fields
"MESSLOKATION": [1 item
{4 fields
"STATUSMITTEILUNG": [1 item
{5 fields
"positionsdaten": [1 item
{1 field
"transaktionsdaten": {10 fields
"absender": {5 fields
"empfaenger": {5 fields
Download: EDIFACT file · BO4E JSON
Belongs to these role views
The check identifier itself carries no market role. This assignment is derived back from the role views in whose process steps it occurs — affected are LF, NB and MSB.
| Role | Party involved | Process | Rulebook | Division | Step |
|---|---|---|---|---|---|
| LF | LF | Start of metering point operation | WiM electricity part 1 | Electricity | Step 7 |
| NB | NB | Start of metering point operation | AWH WiM gas 2.0 | Gas | Step 6 |
| NB | NB | Start of metering point operation | WiM electricity part 1 | Electricity | Step 7 |
| NB | NB | Obligation gMSB | WiM electricity part 1 | Electricity | Step 3 |
| MSB | GMSB | Obligation gMSB | WiM electricity part 1 | Electricity | Step 3 |
| MSB | MSBA | Start of metering point operation | AWH WiM gas 2.0 | Gas | Step 6 |
| MSB | MSBA | Device replacement | AWH WiM gas 2.0 | Gas | Step 3 |
| MSB | MSBA | Start of metering point operation | WiM electricity part 1 | Electricity | Step 7 |
| MSB | MSBA | Device replacement | WiM electricity part 1 | Electricity | Step 3 |
| MSB | MSBA | Obligation gMSB | WiM electricity part 1 | Electricity | Step 3 |
| MSB | MSBN | Start of metering point operation | AWH WiM gas 2.0 | Gas | Step 6 |
| MSB | MSBN | Device replacement | AWH WiM gas 2.0 | Gas | Step 3 |
| MSB | MSBN | Start of metering point operation | WiM electricity part 1 | Electricity | Step 7 |
| MSB | MSBN | Device replacement | WiM electricity part 1 | Electricity | Step 3 |
Business classification
| Attribute | Value |
|---|---|
| Use case (AHB) | Status message |
| AHB | IFTSTA AHB |
| Transmission channel | AS4 |
This check identifier is used in 6 contexts
Regulatory determination and communication direction depend on the process in which the message is sent. A single entry would be misleading — all placements are therefore listed here.
| Process description / rulebook | Process step | Communication | Action |
|---|---|---|---|
| WiM gas | Ch. B 3.3 No. 6b | MSBN → NB | Notification of successful completion of the overall transaction |
| WiM electricity part 1 | Start of metering point operation | MSBN → NB | Notification of the overall transaction |
| WiM electricity part 1 | Obligation gMSB | MSB (corresponds to gMSB on the object metering location) → NB | Confirmation of the takeover of metering point operation |
| WiM electricity part 1 | Device replacement | MSB (corresponds to MSBN on the object metering location) → MSB (corresponds to MSBA on the object metering location) | Point in time of takeover of metering point operation |
| AWH WiM gas 2.0 | Start of metering point operation | MSBN → NB | Notification of the overall transaction |
| AWH WiM gas 2.0 | Device replacement | MSBN → MSBA | Point in time of takeover of metering point operation |
Further relationships from format version 202610
Version 202610 also carries this check identifier in contexts that the table of version 202604 does not know; they are included in the list above. Everything else on this page — use case, rulebook and communication direction — comes from the page's own version. Before adopting it into an implementation specification, check whether what is stated applies to 202604.
Transaction and responses
Role of this check identifier: request. Basis: the transaction data carry neither antwortstatus nor antwortstatusCodeliste, and neither the title nor the action of the Prüfi table begins with “response” or “response message”.
Which messages respond to this
| Role | Check identifier | Use case | Message type | Origin of supply |
|---|---|---|---|---|
| Response | 21012 | Status message | IFTSTA | explicit |
This column is the inverse of the assignment on the response pages — not the next step of a list. The process source says of its own steps that they are »possible messages, not a sequence«.
Check identifiers of the same AHB table: No other check identifier of message type IFTSTA has the same row structure in this version.
Notes on this page
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 54 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 iftsta. 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.
Placeholder from the test data set
The test data set carries placeholders instead of valid values: {{date}} and {{time}} in the UNB interchange envelope of every EDIFACT file. The page replaces these on call with the current date and the current time — in the format that applies at the respective position: in the envelope year, month and day as well as hour and minute, two digits each.
<businessKey> stays in place. It is not a time value, and an invented key would look like a valid one.