Check identifier 17120 — Order placement change of forecast basis
Check identifier 17120 · EDIFACT message type ORDERS · Format version 202610
Data structure
| Structure (BO4E) | Description | Format | 17120 | Condition |
|---|---|---|---|---|
| stammdaten * | — | object | Must | — |
| ANFRAGE [ ] * | — | object[] | Must | — |
| lokationsId * 00010 | Which market or metering location this request applies to. | string | X | — |
| AUFTRAG [ ] * | — | object[] | Must | — |
| ausfuehrungsdatum * 00020 | The execution date describes at which point in time an order is to be executed. | string (date-time) | X | — |
| BILANZIERUNG [ ] * | — | object[] | Must | — |
| prognosegrundlage * 00030 | Forecast basis | Enum Prognosegrundlage | Must | — |
WERTE | — | — | Must | — |
PROFILE | — | — | Must | — |
| transaktionsdaten * | — | object | Must | — |
| dokumentennummer * 00040 | EDIFACT reference from the BGM segment / BGM | string | 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 | — |
| empfaenger * | — | object | Must | — |
| rollencodenummer * 00100 | Specifies the code value of the market role. | string | X | — |
| rollencodetyp * 00110 | Indicates the type of the code. | Enum Rollencodetyp | X | — |
BDEW | — | — | X | — |
GS1 | — | — | X | — |
GLN | — | — | X | — |
DVGW | — | — | X | — |
Application handbook (AHB)
| Structure (EDIFACT) | Description | Format | 17120 | Condition |
|---|---|---|---|---|
| UNH | — | — | Must | — |
006200010 | Message reference number | — | X | — |
0065 ORDERS00020 | Order placement | — | X | — |
0052 D00030 | Draft version | — | X | — |
0054 09B00040 | Edition 2009 - B | — | X | — |
0051 UN00050 | UN/CEFACT | — | X | — |
0057 1.4c00060 | Version number of the underlying BDEW message description | — | X | — |
| BGM | — | — | Must | — |
1001 Z3000070 | Change of forecast basis | — | 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 | — |
| DTM | — | — | Must | — |
2005 20300120 | Execution date/time | — | X | — |
238000130 | Date or time or time span, value | — | X | [UB1] |
2379 30300140 | CCYYMMDDHHMMZZZ | — | X | — |
| SG1.RFF | — | — | Must | — |
1153 Z1300150 | Check identifier | — | X | — |
1154 1712000160 | Order placement change of forecast basis | — | X | — |
| SG2.NAD | — | — | Must | — |
3035 MS00170 | Document-/message sender or sender | — | X | — |
303900180 | MP-ID | — | X | [61] |
3055 900190 | GS1 | — | X | — |
3055 29300200 | DE, BDEW (Bundesverband der Energie- und Wasserwirtschaft e.V.) | — | X | — |
| SG2.NAD | — | — | Must | — |
3035 MR00210 | Message recipient | — | X | — |
303900220 | MP-ID | — | X | [61] |
3055 900230 | GS1 | — | X | — |
3055 29300240 | DE, BDEW (Bundesverband der Energie- und Wasserwirtschaft e.V.) | — | X | — |
| SG2.NAD | — | — | Must | — |
3035 DP00250 | Supply address | — | X | — |
| SG2.LOC | — | — | Must | — |
3227 17200260 | Reporting point | — | X | — |
322500270 | Identifier | — | X | [950] [521] |
| SG29.LIN | — | — | Must | — |
108200280 | Line item number | — | X | [903] |
| SG30.CCI | — | — | Must | — |
7037 Z7700290 | Forecast basis | — | X | — |
| SG30.CAV | — | — | Must | — |
7111 Z3800300 | Forecast based on profiles | — | X | — |
7111 Z3900310 | Forecast based on values | — | X | — |
| UNS | — | — | Must | — |
0081 S00320 | Separation of detail and summary section | — | X | — |
| UNT | — | — | Must | — |
007400330 | Number of segments in a message | — | X | — |
006200340 | Message reference number | — | X | — |
Conditions of this table
The free text of the 7 conditions referenced by the rows above. All conditions of the message type are listed in the condition index ORDERS.
| Marker | Condition |
|---|---|
| [61] | MP-ID only from division electricity |
| [494] | The date stated here must be the point in time at which the document was created, or a point in time before that. |
| [521] | Note: Use of the ID of the market location |
| [903] | Format: Possible value: 1 |
| [931] | Format: ZZZ = +00 |
| [950] | Format: market location ID |
| [UB1] | ([931] ∧ [932] [490]) ⊻ ([931] ∧ [933] [491]) |
Example message
UNA:+.? '
UNB+UNOC:3+9903111000003:500+9900259000002:500+{{date}}:{{time}}+M0C301JD'
UNH+M0HHR9A1+ORDERS:D:09B:UN:1.4c'
BGM+Z30+M0F3L98J'
DTM+137:202610011100?+00:303'
DTM+203:202608182200?+00:303'
RFF+Z13:17120'
NAD+MS+9903111000003::293'
NAD+MR+9900259000002::293'
NAD+DP'
LOC+172+44897654121'
LIN+1'
CCI+++Z77'
CAV+Z38'
UNS+S'
UNT+14+M0HHR9A1'
UNZ+1+M0C301JD'[1 item
{6 fields
"data": {3 fields
"stammdaten": {3 fields
"ANFRAGE": [1 item
{5 fields
"AUFTRAG": [1 item
{4 fields
"positionsdaten": [1 item
{1 field
"BILANZIERUNG": [1 item
{3 fields
"transaktionsdaten": {8 fields
"absender": {4 fields
"empfaenger": {4 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 and NB.
| Role | Party involved | Process | Rulebook | Division | Step |
|---|---|---|---|---|---|
| LF | LF | Order placement for a configuration from the LF to NB | GPKE part 3 | Electricity | Step 1 |
| NB | NB | Order placement for a configuration from the LF to NB | GPKE part 3 | Electricity | Step 1 |
Business classification
| Attribute | Value |
|---|---|
| Use case (AHB) | Order placement change of forecast basis |
| AHB | ORDERS AHB |
| Transmission channel | AS4 |
| Process description / rulebook | Process step | Communication | Action |
|---|---|---|---|
| GPKE part 3 | Order placement for a configuration from LF to NB | LF → NB | Order placement for a configuration at the level of the directly affected location |
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 | 19121 | Notification of change of forecast basis | ORDRSP | 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 ORDERS 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 48 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 orders. 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.