/
Original message identification and sender

Original message identification and sender

Several Datahub events have an information field called ‘Original message identification’. This field is used to link related events to each other as a chain of events. The field is not used in the first events of the event chain, but in the following events of an event chain this field contains the identification of the previous message in the chain of events.

Example:

  1. A supplier reports a new agreement using event DH-311-1. This event does not use the ‘Original message identification’ field because it starts the chain of events.

  1. Datahub forwards the information about the new agreement to the DSO using event DH-311-2. For this event, ‘Original message identification’ contains the message identification of the preceding DH-311-1 event.

  1. The DSO confirms the grid agreement using event DH-312-1. Because this event is a reply to the DH-311 event started by the supplier, the ‘Original message identification’ field contains the message identification of the preceding DH-311-2 event.

  1. Datahub forwards the information about the grid agreement confirmation to the supplier using event DH-312-2. In this event, the ‘Original message identification’ field includes the message identification of the preceding DH-312-1 event.

The ‘Original message sender’ field is used in a similar way. In the example above, event DH-311-2 would contain the identification of the supplier who sent the original DH-311-1. In event DH-312-1 the field would include the identification of the sender of the preceding DH-311-2 event (i.e. Datahub). In event DH-312-2 the field would have the identification of the DSO who sent the DH-312-1 event.