Sending Settlement Transactions to Market Participants
After the outbound communication has retrieved the appropriate service quantities, the outbound message creates an outbound message to the market participant (defined as the Recipient on the settlement transaction’s settlement subscription or settlement subscription type).
The Send Settlement Transaction Details algorithm creates one more outbound messages based on the outbound message type defined for the market participant’s Settlement Transaction Notification processing method (see below for more details).
• If the Message Generation Method on the communication type is set to “One Comprehensive Message” the outbound communication creates a single outbound message that contains all the service quantities retrieved.
• If the Message Generation Method on the communication type is set to “Multiple Messages Based on Data” the outbound communication creates a separate outbound message for each of the service quantities retrieved.
Configuring Market Participants for Settlement Transaction Communication
To support sending settlement transactions to market participants, the following processing method must be defined for the market participants to which settlement transactions are sent:
Processing Role | Processing Method |
|---|
Settlement Transaction Notification | How to Send Settlement Subscription Related Information Used to send a settlement transaction outbound message to a market participant. Default Outbound Message Type: The default outbound message type to create for outbound message sent to market participants. The base package does not include an outbound message business object for this. This must be created based on the requirements of each implementation and market participant. If appropriate, override outbound message types can be defined for specific settlement subscription types. |
In addition, the following objects must be configured to send data requests:
• External System
• Outbound Message Type
• Message Sender
`
Parent topic