Check identifier 23003 — Rejection
Check identifier 23003 · EDIFACT message type INSRPT · Format version 202604
Data structure
| Structure (BO4E) | Description | Format | 23003 | Condition |
|---|---|---|---|---|
| stammdaten * | — | object | Must | — |
| STATUSMITTEILUNG [ ] * | — | object[] | Must | — |
| positionsdaten [ ] * | — | object[] | Must | — |
| antwortstatus * 00010 | antwortstatus | string | X | — |
| lokationsId * 00020 | lokationsId | string | X | — |
| positionsnummer * 00030 | positionsnummer | integer | Must | — |
| verwendungAb 00040 | verwendungAb | string (date-time) | X | — |
| transaktionsdaten * | — | object | Must | — |
| anfragereferenznummer * 00050 | Reference transaction number 'from request message' / ORDERS RFF+TN / IFTSTA RFF+AAV / INSRPT RFF+TN RFF+AAV | string | X | — |
| dokumentennummer * 00060 | EDIFACT reference from the BGM segment / BGM | string | X | — |
| nachrichtendatum * 00070 | Creation date of the EDIFact / DTM+137 | string (date-time) | X | — |
| nachrichtenreferenznummer * 00080 | EDIFACT reference from the UNT segment / UTILMD UNT+21 | string | Must | — |
| pruefidentifikator * 00090 | Contains the check identifier from the EDIFact communication / RFF+Z13 | string | X | — |
| vorgangsnummer * 00100 | Number of the transaction / UTILMD UTILTS IDE+24 / INSRPT INVOIC DOC | string | X | — |
| absender * | — | object | Must | — |
| rollencodenummer * 00110 | Specifies the code value of the market role. | string | X | — |
| rollencodetyp * 00120 | Indicates the type of the code. | Enum Rollencodetyp | X | — |
BDEW | — | — | X | — |
GS1 | — | — | X | — |
GLN | — | — | X | — |
DVGW | — | — | X | — |
| empfaenger * | — | object | Must | — |
| rollencodenummer * 00130 | Specifies the code value of the market role. | string | X | — |
| rollencodetyp * 00140 | Indicates the type of the code. | Enum Rollencodetyp | X | — |
BDEW | — | — | X | — |
GS1 | — | — | X | — |
GLN | — | — | X | — |
DVGW | — | — | X | — |
Application handbook (AHB)
| Structure (EDIFACT) | Description | Format | 23003 | Condition |
|---|---|---|---|---|
| UNH | — | — | Must | — |
006200010 | Message reference number | — | X | — |
0065 INSRPT00020 | Check report | — | X | — |
0052 D00030 | Draft version | — | X | — |
0054 10A00040 | Edition 2010 - A | — | X | — |
0051 UN00050 | UN/CEFACT | — | X | — |
0057 1.1a00060 | Version number of the underlying BDEW message description | — | X | — |
| BGM | — | — | Must | — |
1001 400070 | Check report | — | 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 | — |
| SG2.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 | — |
| SG2.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 | — |
| SG3.DOC | — | — | Must | — |
1001 2200220 | Response to request | — | X | — |
100400230 | Transaction number | — | X | — |
| SG4.RFF | — | — | Must | — |
1153 Z1300240 | Check identifier | — | X | — |
1154 2300300250 | WiM / rejection from the MSB to LF/NB/MSB | — | X | — |
| SG4.RFF | — | — | Must | — |
1153 AAV00260 | Number of the request | — | X | — |
115400270 | Document-/transaction number of the reference message | — | X | — |
| SG7.LIN | — | — | Must | — |
108200280 | Line item number | — | X | [908] [511] |
| SG7.DTM | — | — | May | — |
2005 16300290 | Processing, start date/time | — | X | — |
238000300 | Date or time or time span, value | — | X | ([931] [13] ∧ [495]) ⊻ ([495] ∧ [515]) |
2379 10200310 | CCYYMMDD | — | X | — |
2379 30300320 | CCYYMMDDHHMMZZZ | — | X | — |
| SG7.STS | — | — | Must | — |
9015 E0100330 | Status of the response | — | X | — |
9013 Z2900340 | Rejection (contractual relationship no longer exists) | — | X | — |
9013 ZB800350 | no fault detectable | — | X | — |
| SG8.NAD | — | — | Must | — |
3035 DP00360 | Supply address | — | X | — |
| SG8.LOC | — | — | Must | — |
3227 17200370 | Reporting point | — | X | — |
322500380 | Identifier | — | X | [951] [509] |
| UNT | — | — | Must | — |
007400390 | Number of segments in a message | — | X | — |
006200400 | Message reference number | — | X | — |
Conditions of this table
The free text of the 9 conditions referenced by the rows above. All conditions of the message type are listed in the condition index INSRPT.
| Marker | Condition |
|---|---|
| [13] | If DE2379 = 303 |
| [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 |
| [509] | Note: Use of the ID of the metering location |
| [511] | Note: The numbering starts at 1 in every document |
| [515] | Note: "≤ the value in DE2380 of DTM+137" means that the day stated there must be ≥ the day stated in this DTM if code 102 is entered in DE2379. |
| [908] | Format: possible values: 1 to n |
| [931] | Format: ZZZ = +00 |
| [951] | Format: Metering point identifier |
Example message
Example 1
UNA:+.? '
UNB+UNOC:3+9904446000007:500+9903790000002:500+{{date}}:{{time}}+134096'
UNH+481679+INSRPT:D:10A:UN:1.1a'
BGM+4+NIK KIRS481679BGM'
DTM+137:202304140723?+00:303'
NAD+MR+9903790000002::293'
NAD+MS+9904446000007::293'
DOC+22+123'
RFF+Z13:23003'
RFF+AAV:REF12345678910'
LIN+1'
STS+E01++ZB8'
NAD+DP'
LOC+172+DE0032106765712000000000000000037'
UNT+13+481679'
UNZ+1+134096'[1 item
{6 fields
"data": {3 fields
"stammdaten": {1 field
"STATUSMITTEILUNG": [1 item
{3 fields
"positionsdaten": [1 item
{3 fields
"transaktionsdaten": {11 fields
"absender": {5 fields
"empfaenger": {5 fields
Download: EDIFACT file · BO4E JSON
Example 2
UNA:+.? '
UNB+UNOC:3+9904446000007:500+9903790000002:500+{{date}}:{{time}}+134096'
UNH+481679+INSRPT:D:10A:UN:1.1a'
BGM+4+NIK KIRS481679BGM'
DTM+137:202304140723?+00:303'
NAD+MR+9903790000002::293'
NAD+MS+9904446000007::293'
DOC+22+123'
RFF+Z13:23003'
RFF+AAV:REF12345678910'
LIN+1'
DTM+163:202304111200?+00:303'
STS+E01++ZB8'
NAD+DP'
LOC+172+DE0032106765712000000000000000037'
UNT+14+481679'
UNZ+1+134096'[1 item
{6 fields
"data": {3 fields
"stammdaten": {1 field
"STATUSMITTEILUNG": [1 item
{3 fields
"positionsdaten": [1 item
{4 fields
"transaktionsdaten": {11 fields
"absender": {5 fields
"empfaenger": {5 fields
Download: EDIFACT file · BO4E JSON
Example 3
UNA:+.? '
UNB+UNOC:3+9904446000007:500+9903790000002:500+{{date}}:{{time}}+134096'
UNH+481679+INSRPT:D:10A:UN:1.1a'
BGM+4+NIK KIRS481679BGM'
DTM+137:202304140723?+00:303'
NAD+MR+9903790000002::293'
NAD+MS+9904446000007::293'
DOC+22+123'
RFF+Z13:23003'
RFF+AAV:REF12345678910'
LIN+1'
DTM+163:202304111200?+00:303'
STS+E01++ZB8'
NAD+DP'
LOC+172+DE0032106765712000000000000000037'
LIN+2'
STS+E01++ZB8'
NAD+DP'
LOC+172+DE0032106765712000000000000000038'
UNT+18+481679'
UNZ+1+134096'[1 item
{6 fields
"data": {3 fields
"stammdaten": {1 field
"STATUSMITTEILUNG": [1 item
{3 fields
"positionsdaten": [2 items
{4 fields
{3 fields
"transaktionsdaten": {11 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, MSB and ÜNB.
| Role | Party involved | Process | Rulebook | Division | Step |
|---|---|---|---|---|---|
| LF | LF | Fault rectification in the metering location | AWH WiM gas 2.0 | Gas | Step 2 |
| LF | LF | Fault rectification in the metering location | WiM electricity part 2 | Electricity | Step 2 |
| NB | NB | Fault rectification in the metering location | AWH WiM gas 2.0 | Gas | Step 2 |
| NB | NB | Fault rectification in the metering location | WiM electricity part 2 | Electricity | Step 2 |
| MSB | MSB | Fault rectification in the metering location | AWH WiM gas 2.0 | Gas | Step 2 |
| MSB | MSB-MALO | Fault rectification in the metering location | WiM electricity part 2 | Electricity | Step 2 |
| MSB | MSB-MELO | Fault rectification in the metering location | WiM electricity part 2 | Electricity | Step 2 |
| ÜNB | ÜNB | Fault rectification in the metering location | WiM electricity part 2 | Electricity | Step 2 |
Business classification
| Attribute | Value |
|---|---|
| Use case (AHB) | Rejection |
| AHB | INSRPT AHB |
| Transmission channel | AS4 |
This check identifier is used in 5 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. C 2.3 No. 4a | MSB → LF | Rejection of the fault report |
| WiM gas | Ch. C 2.3 No. 4a | MSB → NB | Rejection of the fault report |
| WiM electricity part 2 | Fault rectification in the metering location | MSB (corresponds to MSB on the object metering location) → fault indicator | Response |
| AWH WiM gas 2.0 | Fault rectification in the metering location | MSB → LF | Response |
| AWH WiM gas 2.0 | Fault rectification in the metering location | MSB → NB | Response |
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: response — rejection. Basis: the title or the action of the Prüfi table begins with “response”; the title names a polarity (rejection).
Which request this message responds to
| Role | Check identifier | Use case | Message type | Origin of supply |
|---|---|---|---|---|
| Request | 23001 | Fault report | INSRPT | from the step sequence |
In which field the request is quoted
| Reference field of this message | EDIFACT segment | Target field in the request |
|---|---|---|
anfragereferenznummer | SG3.DOC+22.SG4.RFF+AAV | dokumentennummer |
RFF+AAV quotes the preceding message via its BGM; the target is the dokumentennummer of the request. Measured: 23001 carries dokumentennummer in BGM+4.
Check identifiers of the same AHB table: No other check identifier of message type INSRPT 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 3 transactions for this check identifier under the message type insrpt. 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.