Check identifier 21036 — Status message
Check identifier 21036 · EDIFACT message type IFTSTA · Format version 202604
Data structure
| Structure (BO4E) | Description | Format | 21036 | 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 | — |
| positionsdaten [ ] * | — | object[] | Must | — |
| positionsnummer * 00020 | positionsnummer | integer | Must | — |
| transaktionsdaten * | — | object | Must | — |
| dokumentennummer * 00030 | EDIFACT reference from the BGM segment / BGM | string | X | — |
| fertigstellungsdatum * 00040 | Completion date / DTM+293 | string (date-time) | X | — |
| nachrichtendatum * 00050 | Creation date of the EDIFact / DTM+137 | string (date-time) | X | — |
| nachrichtenreferenznummer * 00060 | EDIFACT reference from the UNT segment / UTILMD UNT+21 | string | Must | — |
| pruefidentifikator * 00070 | Contains the check identifier from the EDIFact communication / RFF+Z13 | string | X | — |
| absender * | — | object | Must | — |
| rollencodenummer * 00080 | Specifies the code value of the market role. | string | X | — |
| rollencodetyp * 00090 | Indicates the type of the code. | Enum Rollencodetyp | X | — |
BDEW | — | — | X | — |
GS1 | — | — | X | — |
GLN | — | — | X | — |
DVGW | — | — | X | — |
| ansprechpartner | — | object | May | — |
| eMailAdresse 00100 | Email address | string | Must | — |
| nachname 00110 | Surname (family name) of the contact person | string | X | — |
| rufnummern [ ] | — | object[] | May | — |
| nummerntyp 00120 | 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 00130 | rufnummer | string | Must | — |
| empfaenger * | — | object | Must | — |
| rollencodenummer * 00140 | Specifies the code value of the market role. | string | X | — |
| rollencodetyp * 00150 | Indicates the type of the code. | Enum Rollencodetyp | X | — |
BDEW | — | — | X | — |
GS1 | — | — | X | — |
GLN | — | — | X | — |
DVGW | — | — | X | — |
Application handbook (AHB)
| Structure (EDIFACT) | Description | Format | 21036 | 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 | CCYYMMDDHHMMZZZ | — | X | — |
| SG1.NAD | — | — | Must | — |
3035 MR00120 | Message recipient | — | X | — |
303900130 | MP-ID | — | X | [27] |
3055 900140 | GS1 | — | X | — |
3055 29300150 | DE, BDEW (Bundesverband der Energie- und Wasserwirtschaft e.V.) | — | X | — |
| SG1.NAD | — | — | Must | — |
3035 MS00160 | Document-/ message sender or sender | — | X | — |
303900170 | MP-ID | — | X | [27] |
3055 900180 | GS1 | — | X | — |
3055 29300190 | DE, BDEW (Bundesverband der Energie- und Wasserwirtschaft e.V.) | — | X | — |
| SG2.CTA | — | — | Must | — |
3139 IC00200 | Information contact | — | X | — |
341200210 | Contact | — | X | — |
| SG2.COM | — | — | Must | — |
314800220 | Number / email address | — | X | (([939][146]) ∨ ([940] [147])) ∧ [534] |
3155 EM00230 | — | X | [1P0..1] | |
3155 FX00240 | Fax number | — | X | [1P0..1] |
3155 TE00250 | Telephone | — | X | [1P0..1] |
3155 AJ00260 | further telephone | — | X | [1P0..1] |
3155 AL00270 | Mobile phone | — | X | [1P0..1] |
| SG14.CNI | — | — | Must | — |
149000280 | Transaction number | — | X | [911] |
| SG14.LOC | — | — | Must | — |
3227 17200290 | Reporting point | — | X | — |
322500300 | Identifier | — | X | [951] [505] |
| SG15.STS | — | — | Must | — |
9015 Z2600310 | Device status | — | X | — |
4405 Z3500320 | removed | — | X | — |
| SG15.RFF | — | — | Must | — |
1153 Z1300330 | Check identifier | — | X | — |
1154 2103600340 | WiM / Device status | — | X | — |
| SG15.DTM | — | — | Must | — |
2005 29300350 | Completion date/time | — | X | — |
238000360 | Date or time or time span, value | — | X | [931] [495] |
2379 30300370 | CCYYMMDDHHMMZZZ | — | X | — |
| UNT | — | — | Must | — |
007400380 | Number of segments in a message | — | X | — |
006200390 | Message reference number | — | X | — |
Conditions of this table
The free text of the 13 conditions referenced by the rows above. All conditions of the message type are listed in the condition index IFTSTA.
| Marker | Condition |
|---|---|
| [27] | Only MP-ID from the electricity division |
| [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 |
| [495] | The point in time must be ≤ the value in DE2380 of DTM+137 |
| [505] | Note: Use of the ID of the metering location |
| [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. |
Example message
UNA:+.? '
UNB+UNOC:3+9904446000007:500+9904446000007:500+{{date}}:{{time}}+M0HE93N2'
UNH+UNHM0GHMVF2+IFTSTA:D:18A:UN:2.0g'
BGM+Z09+BGMM0EKV33E'
DTM+137:202504041200?+00:303'
NAD+MR+9904446000007::293'
NAD+MS+9904446000007::293'
CNI+1'
LOC+172+DE0032106765712000000000000000037'
STS+Z26+Z35'
RFF+Z13:21036'
DTM+293:202501152300?+00:303'
UNT+11+UNHM0GHMVF2'
UNZ+1+M0HE93N2'[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 is MSB.
| Role | Party involved | Process | Rulebook | Division | Step |
|---|---|---|---|---|---|
| MSB | MSBA | Device replacement | AWH WiM gas 2.0 | Gas | Step 6 |
| MSB | MSBA | Device replacement | WiM electricity part 1 | Electricity | Step 6 |
| MSB | MSBN | Device replacement | AWH WiM gas 2.0 | Gas | Step 6 |
| MSB | MSBN | Device replacement | WiM electricity part 1 | Electricity | Step 6 |
Business classification
| Attribute | Value |
|---|---|
| Use case (AHB) | Status message |
| AHB | IFTSTA AHB |
| Transmission channel | AS4 |
This check identifier is used in 2 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 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 device removal |
| AWH WiM gas 2.0 | Device replacement | MSBN → MSBA | Point in time of device removal |
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”.
Responses: No response of this format version names this check identifier as a reference — neither explicitly in the Prüfi table nor via the step sequence. That does not mean there is none; it means that the sources do not record one.
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 52 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.