In this app, you can display a list and the details of all inbound and outbound market messages.

These messages include those that come from or go to the market processes of SAP Market Communication for Utilities, as well as messages that only get routed through SAP Market Communication for Utilities.

Note

This app doesn't display incoming market communication messages that have a general technical issue, for example, unencrypted emails or emails with a corrupt attachment. You can review and manually handle those messages in the Display Message Exchange Issues app.

All messages that are handled by market processes result in transfer documents that are linked to the process document of the respective process. For monitoring the transfer and process documents, you use the Monitor Transfer Documents and Monitor Process Documents apps.

In the Display Market Messages app, you can filter the list to check the individual statuses and attributes of a subset of messages. From the list, you can rerun the routing service and resend messages.

In addition, you can drill down further into the details of a single message, seeing the transactions inside, if and where they were forwarded and copied to. In case of issues, you can navigate to the routing clarification or error information.

Navigate directly to the related market process in the Display Market Processes app.

The button Go to Market Process navigates to the related market process in the Display Market Processes app. There, you can view process details, additional data, deadline details, and more.

Navigate to the error information available in the Display Message Exchange Issues app.

The message exchange issue is found in the Display Message Exchange Issues app by using the correlation ID. There, you can review the issue type, issue status, and the technical details of the error for more information.

This option is only valid for market messages with Error as their message processing status.

If no data is found in the Display Message Exchange Issues app, report an incident.

Change the message processing status manually or terminate the further processing of subsequent issues and processes.

Setting the status manually gives you more control for accurate record keeping of your market messages that have an incomplete status. For example, if the message processing status never updated after an error was resolved, you can set the status to completed, which is displayed as Completed Manually. If you choose to stop processing the message in the market communication system, you can set the status to terminated, which is displayed as Terminated Manually.

Additionally, you can terminate the further processing of subsequent message exchange issues and processes by selecting Terminated for <Filtered / Selected> and selecting Terminate Subsequent Issue and Terminate Subsequent Processes.

Note You can terminate subsequent processes only for outbound market messages that originate from the process engine. You can determine the source system of the market message by using the filter Source System. If a market message doesn't have a related message exchange issue, or the related issue is already in a final status, you can't terminate the subsequent issue.

For more information about terminating market messages and message exchange issues, and step-by-step instructions, see Terminating in Display Market Messages App.

You can review the Status Setting History section in the message details for a record of the changes.

Selection of Message Processing Status

By selecting <Message Processing Status> for Filtered, you are setting that status for all messages that have been filtered out by your filter settings, not just the ones currently loaded on the screen. You can view the created job in the Display Async Job Logs app for more details.

By selecting <Message Processing Status> for Selected, you are setting that status for only the messages that you've individually selected.

Displays the transaction status which is updated based on any new APERAK message.

Transaction status is updated based on any new APERAK message. The following transaction statuses are possible:

Transaction statuses
Transaction status	Message direction	Description
Positive APERAK Sent	Inbound	APERAK validation is successful for the inbound message
Negative APERAK Sent	Inbound	Inbound message has an APERAK validation failure
APERAK Missing	Inbound Outbound	Default status. When there is no APERAK sent or received for the inbound or outbound messages respectively.
Positive APERAK Received	Outbound	APERAK validation is successful for the outbound message
Negative APERAK Received	Outbound	Outbound message has an APERAK validation failure
Internal Negative APERAK for 3rd Partner	Outbound Split	Outbound split message partially or entirely failed the internal APERAK validation. This status is valid only for outbound split messages intended for a third party or external market partner.
Empty	Inbound Outbound

Transaction status isn't updated for CONTRL messages or APERAK messages without transaction references (so called header level APERAK).

For non-split REMADV messages, the transaction status displayed in this field is updated correctly based on the response APERAK.

For split REMADV and split and non-split COMDIS messages, this field remains empty, because the response APERAK only updates the message on the header level.

Displays the transaction status which is updated based on any new APERAK message.

Transaction status is updated based on any new APERAK message. The following transaction statuses are possible:

Transaction statuses
Transaction status	Message direction	Description
Positive APERAK Sent	Inbound	APERAK validation is successful for the inbound message
Negative APERAK Sent	Inbound	Inbound message has an APERAK validation failure
APERAK Missing	Inbound Outbound	Default status. When there is no APERAK sent or received for the inbound or outbound messages respectively.
Positive APERAK Received	Outbound	APERAK validation is successful for the outbound message
Negative APERAK Received	Outbound	Outbound message has an APERAK validation failure
Internal Negative APERAK for 3rd Partner	Outbound Split	Outbound split message partially or entirely failed the internal APERAK validation. This status is valid only for outbound split messages intended for a third party or external market partner.
Empty	Inbound Outbound

Transaction status isn't updated for CONTRL messages or APERAK messages without transaction references (so called header level APERAK).

For non-split REMADV messages, the transaction status displayed in this field is updated correctly based on the response APERAK.

For split REMADV and split and non-split COMDIS messages, this field remains empty, because the response APERAK only updates the message on the header level.

Lists related process documents, their statuses and descriptions, and navigates to Monitor Process Documents app.

Navigate directly to the details page in the Monitor Process Documents app by clicking the link.

If there are multiple process documents, select Show All to view a list of process documents related to the market message. You can navigate to the process document details page in the Monitor Process Documents app using the individual process document number, or you can go to the list page by selecting Show All.

Lists each instance the message processing status of the message was manually changed.

Display and download the status information for outbound AS4 and Web API messages.

For outbound market messages sent via AS4, this button displays the non-repudiation receipt (NRR) information. NRR provides proof that a message was received and processed, including details about integrity and authenticity.

For outbound Web API messages, this button displays the status response payload for the message. In case of a failure, the status information shows a description of the error.

Show, copy, and download the payload.

When displaying the payload, you have the following options:

Download as Pure TXT File: Download the TXT file with its original formatting. For EDIFACT messages, this means no line breaks.
Download as TXT File: Download the TXT file with the formatting as seen on the screen.
Copy to Clipboard: Copy the payload to your clipboard with the formatting as seen on the screen.

Note The message payload is downloaded using UTF-8 character encoding.

If the message has Rejected By Internal CONTRL, Negative CONTRL Sent, or Ext. Negative CONTRL Received as its business status, you can view the payload of the negative CONTRL as well and generate an explanation of the negative CONTRL if you have the required AI service.

Show, copy, and download the payload.

When displaying the payload, you have the following options:

Download as Pure TXT File: Download the TXT file with its original formatting. For EDIFACT messages, this means no line breaks.
Download as TXT File: Download the TXT file with the formatting as seen on the screen.
Copy to Clipboard: Copy the payload to your clipboard with the formatting as seen on the screen.

Note The message payload is downloaded using UTF-8 character encoding.

If the message has Rejected By Internal CONTRL, Negative CONTRL Sent, or Ext. Negative CONTRL Received as its business status, you can view the payload of the negative CONTRL as well and generate an explanation of the negative CONTRL if you have the required AI service.

Reimport the selected transactions again.

Transactions can be reimported for non-split and split inbound market messages that are forwarded to your own market partner. The message must have a completed message processing status. Transactions in negative APERAK, CONTRL, REMADV, or COMDIS messages can't be reimported.

Optional: Positive APERAK Response: When reprocessing transactions, you can skip sending a positive APERAK response to your market partner by selecting the option.

Once you've reprocessed a transaction, you can find the reprocessing information in the Reprocessing History section.

For more information see, Reprocessing a Transaction.

Lists all market processes that are directly related to the current message and enables you to navigate to the Display Market Processes and Monitor Process Documents apps for further details.

By clicking the market process, you can navigate to the message details in the Display Market Processes app.

To view process details in the Monitor Process Documents app, select the related process and then choose Details.

Show, copy, and download the payload.

When displaying the payload, you have the following options:

Download as Pure TXT File: Download the TXT file with its original formatting. For EDIFACT messages, this means no line breaks.
Download as TXT File: Download the TXT file with the formatting as seen on the screen.
Copy to Clipboard: Copy the payload to your clipboard with the formatting as seen on the screen.

Note The message payload is downloaded using UTF-8 character encoding.

If the message has Rejected By Internal CONTRL, Negative CONTRL Sent, or Ext. Negative CONTRL Received as its business status, you can view the payload of the negative CONTRL as well and generate an explanation of the negative CONTRL if you have the required AI service.

Show, copy, and download the payload.

When displaying the payload of a Web API message, you have the following options:

Download as Pure JSON File: Download the JSON file without line breaks and white space.
Download as JSON File: Download the JSON file with its original formatting.
Copy to Clipboard: Copy the payload to your clipboard with the formatting as seen on the screen.

Note The message payload is downloaded using UTF-8 character encoding.

Lists each instance the message processing status of the message was manually changed.

Creates a readable summary of the negative CONTRL by using AI based on BDEW documents.

Note

This AI capability requires purchasing an SAP AI Units license. The eligible AI service is SAP Market Communication for Utilities, AI-assisted CONTRL-message explanation.

For more information about the AI services available for use and the applicable capacity unit values, refer to SAP AI Services List Information published on SAP site .

This explanation can be generated for the following scenarios:

Rejected By Internal CONTRL: An internal negative CONTRL generated by the market message transfer (MMT) component
Negative CONTRL Sent: A negative CONTRL sent to your market partner
Ext. Negative CONTRL Received: A negative CONTRL you receive from your market partner

When generating the explanation, AI uses the payload of the original message, the negative CONTRL, and the relevant BDEW document to describe the issues in plain language so that you can easily understand the cause and take corrective actions. Currently, DVGW documents aren't supported. You should verify the the.

Tip

See room for improvement? Help us refine the generated explanation by giving feedback.

Displays the transaction status which is updated based on any new APERAK message.

Transaction status is updated based on any new APERAK message. The following transaction statuses are possible:

Transaction statuses
Transaction status	Message direction	Description
Positive APERAK Sent	Inbound	APERAK validation is successful for the inbound message
Negative APERAK Sent	Inbound	Inbound message has an APERAK validation failure
APERAK Missing	Inbound Outbound	Default status. When there is no APERAK sent or received for the inbound or outbound messages respectively.
Positive APERAK Received	Outbound	APERAK validation is successful for the outbound message
Negative APERAK Received	Outbound	Outbound message has an APERAK validation failure
Internal Negative APERAK for 3rd Partner	Outbound Split	Outbound split message partially or entirely failed the internal APERAK validation. This status is valid only for outbound split messages intended for a third party or external market partner.
Empty	Inbound Outbound

Transaction status isn't updated for CONTRL messages or APERAK messages without transaction references (so called header level APERAK).

For non-split REMADV messages, the transaction status displayed in this field is updated correctly based on the response APERAK.

For split REMADV and split and non-split COMDIS messages, this field remains empty, because the response APERAK only updates the message on the header level.

Lists each instance the market message was resent or reimported with additional details.

You can view who reprocessed the message and why for each instance.

Filter market messages based on the date and time the messages were archived at.

After archiving a market message, the date and time is recorded in the field Archived At in the message header.

For more information about archiving, see Archiving Market Messages and Processes

Filter market messages based on the transaction ID.

Transaction ID is the unique reference number that identifies a transaction within the market message.

Narrow down your search by transaction reason.

Transaction reason displays the transaction reason extracted from the EDIFACT market message payload.

Filter market messages based on the DTD reply code extracted from the EDIFACT payload.

The DTD reply code is extracted from the EDIFACT market message.

Filter by the number of transactions rejected by negative APERAK messages received for the market message in the electricity division.

When at least one transaction in the market message (excluding APERAK and CONTRL messages) received a negative APERAK, the market message has the Ext. Negative APERAK Received business status.

If the market message was rejected by a negative CONTRL, no information is provided in this field.

Filter by the number of transactions accepted by positive APERAK messages received for the market message in the electricity division.

When all transactions in the market message (excluding APERAK and CONTRL messages) received a positive APERAK, the market message has the Positive APERAK Received business status.

If the market message was rejected by a negative CONTRL, no information is provided in this field.

Filter market messages based on their source system in the system landscape.

Source Systems
Source System	Explanation
External Market Partner	The market message originates from an external market partner's system.
Internal Market Partner	The market message originates from an internal market partner's system. The market partner can be in an associated organization, or a market partner within your customer network.
Manual Upload	The market message has been manually uploaded.
MMT	The market message originates from your market message transfer system.
Process Engine	The market message originates from your business system.

Filter by the number of transactions missing APERAK messages for the market message in the electricity division.

When at least one transaction in the market message (excluding APERAK and CONTRL messages) hasn't received an APERAK message, the market message has the APERAK Missing business status. However, if a negative APERAK has been received, the Ext. Negative APERAK Received business status is given priority.

If the market message was rejected by a negative CONTRL, no information is provided in this field.

Filter the market messages by the unique reference number found inside the payload.

Filter the market messages based on their archiving status.

The default setting for the filter Is Archived is No, which means that only messages that have no Archived At timestamp filled are displayed on the list page.

Filter by the communication market partner role.

Narrow down your search by selecting one or more communication market partner roles.

Filter by the own market partner role.

Narrow down your search by selecting one or more own market partner roles.

Filter by the ID given to the market message when it's sent using AS4.

Filter by the date and time when the system received an inbound message or started to process an outbound message.

Filter by the direction of the market message: Inbound, Outbound, or Split.

The message direction is determined by the perspective of the system. If the market message was received into the system, it's Inbound. If the message was sent by the system, it's Outbound.

If the market message was split into the contained transactions, and forwarded or copied to different market partners, it's labeled as Split.

Filter by entering the ID of the market participant from your organization who can be the original sender or receiver of the market message.

For outbound messages, the sender is the own market partner, and the receiver is the communication market partner. For inbound messages, it's the opposite.

Filter by the general technical status of the market message processing.

For split market messages, the message processing status displayed in the header of the split message is determined by the status of the forwarded messages.

The following statuses are possible:

Started: The message processing has begun.
Error: The message processing ran into an error. Go to the error information to learn more.
If no data is found in the Display Message Exchange Issues app, report an incident.
Routing Pending: The message went to the routing service that tried to determine routing targets for the message and the contained transactions. However, the service has failed to determine a unique target for at least one of the transactions, which requires manual intervention by you using the Clarify Message Routing app.
Completed: 1. An inbound message has been received and handed over to a predefined market process or routed to a target receiver. In the case of an original message that has been split and routed, all transactions were split into new messages and successfully routed to a target receiver.
2. An outbound message has been sent out to the communication market partner. In the case of an original message that has been split and routed, all transactions were split into new messages and routed to a target receiver.
Completed with Negative Validation: 1. An inbound message failed the validation (the CONTRL or APERAK validation) for at least one transaction, and the corresponding rejection was sent back to the communication market partner. The transactions that passed the validation continue to be processed.
2. An outbound message coming from a market process or internal market partner failed the validation, and a rejection has been sent back to the process or internal market partner. The transactions that passed the validation continue to be processed.
Completed with Limitations (routing case only): No routing result was determined for one or more transactions within the maximum waiting time, and the fallback routing to the default receiver was used.
Completed Manually: The message processing is considered done, and the status was set manually by you or another user.
When this status is set, no technical change is made or triggered. It's for tracking purposes only, allowing you to clean up your list of market messages. This status is useful for scenarios like when the message had an issue that was later resolved, but the Error status never changed, among others.
Terminated Manually: The message processing is terminated, and the status was set manually by you or another user.
When this status is set, the message processing in the market communication system is stopped. This status is also displayed when you use the termination functionality in the Display Message Exchange Issues app to stop the processing of the market message along with the related message exchange issue.
Sending Failed: Sending the market message via AS4 or Web API from the AS4 or Web API service provider to the communication market partner failed.
You should actively monitor messages with this status. To find out more details about the cause, select Display Status Information to view the Web API status response payload (for Web API messages) or the NRR information (for AS4 messages).
To resolve the issue, try reprocessing the message. If reprocessing isn't successful, contact your AS4 or Web API service provider, or your market partner, depending on the cause of the failure. For example, if the status information message is "Receiver system not reachable" or "Receiver partner ID doesn't exist", contact your AS4 or Web API service provider. If the status information message is "Receiver AS4 certificate is expired" or "Receiver AS4 certificate is missing", you should contact your communication market partner directly.
Note If you use the integrated AS4 or Web API service provider, report an incident to SAP for more information. If you use an external AS4 or Web API service provider, contact your service provider directly for more information.
Note
When sending via AS4 or Web API has failed from SAP Market Communication for Utilities to the AS4 or Web API service provider, the Error status is used.

When sending has failed for communication methods that use synchronized sending (such as email and AS2), the Error status is used.
Queued for Sending: The message is waiting to be sent via AS4 or Web API.
In Retry by System: If you have enabled automatic retry by system for messages that are in status Sending Failed, this status is displayed before the messages' processing status changes to Queued for Sending. The system will automatically attempt to send the message at configured intervals.

Filter by the name extracted from the NAD segment in the payload.

Narrow down your search quicker by using the Name filter along with the Address filter.

Note

When data from the NAD segment is stored (for the entire message), it is truncated after 5000 characters. For very large messages, the data could exceed that character limit. Keep this in mind when performing your search.

Display and download the status information for outbound AS4 and Web API messages.

For outbound market messages sent via AS4, this button displays the non-repudiation receipt (NRR) information. NRR provides proof that a message was received and processed, including details about integrity and authenticity.

For outbound Web API messages, this button displays the status response payload for the message. In case of a failure, the status information shows a description of the error.

Creates a readable summary of the negative CONTRL by using AI based on BDEW documents.

Note

This AI capability requires purchasing an SAP AI Units license. The eligible AI service is SAP Market Communication for Utilities, AI-assisted CONTRL-message explanation.

For more information about the AI services available for use and the applicable capacity unit values, refer to SAP AI Services List Information published on SAP site .

This explanation can be generated for the following scenarios:

Rejected By Internal CONTRL: An internal negative CONTRL generated by the market message transfer (MMT) component
Negative CONTRL Sent: A negative CONTRL sent to your market partner
Ext. Negative CONTRL Received: A negative CONTRL you receive from your market partner

When generating the explanation, AI uses the payload of the original message, the negative CONTRL, and the relevant BDEW document to describe the issues in plain language so that you can easily understand the cause and take corrective actions. Currently, DVGW documents aren't supported. You should verify the the.

Tip

See room for improvement? Help us refine the generated explanation by giving feedback.

Filter by the unique identifier that represents a physical point where energy consumption is measured, for example, DE471100000000000000001.

Note

When market location IDs are stored (for each transaction), duplicated location IDs are removed, and the data is truncated after 5000 characters. Keep this in mind when performing your search.

Filter by the address extracted from the NAD segment of the payload.

Narrow down your search by address-related information, such as street, postal code, and city.

Note

When data from the NAD segment is stored (for the entire message), it is truncated after 5000 characters. For very large messages, the data could exceed that character limit. Keep this in mind when performing your search.

Filter by the unique identifier that represents a point where energy is generated or consumed and that is associated with commercial and contractual obligations, for example, 5700000001.

Note

When market location IDs are stored (for each transaction), duplicated location IDs are removed, and the data is truncated after 5000 characters. Keep this in mind when performing your search.

Displays the general technical status of the market message processing.

For split market messages, the message processing status displayed in the header of the split message is determined by the status of the forwarded messages.

The following statuses are possible:

Started: The message processing has begun.
Error: The message processing ran into an error. Go to the error information to learn more.
If no data is found in the Display Message Exchange Issues app, report an incident.
Routing Pending: The message went to the routing service that tried to determine routing targets for the message and the contained transactions. However, the service has failed to determine a unique target for at least one of the transactions, which requires manual intervention by you using the Clarify Message Routing app.
Completed: 1. An inbound message has been received and handed over to a predefined market process or routed to a target receiver. In the case of an original message that has been split and routed, all transactions were split into new messages and successfully routed to a target receiver.
2. An outbound message has been sent out to the communication market partner. In the case of an original message that has been split and routed, all transactions were split into new messages and routed to a target receiver.
Completed with Negative Validation: 1. An inbound message failed the validation (the CONTRL or APERAK validation) for at least one transaction, and the corresponding rejection was sent back to the communication market partner. The transactions that passed the validation continue to be processed.
2. An outbound message coming from a market process or internal market partner failed the validation, and a rejection has been sent back to the process or internal market partner. The transactions that passed the validation continue to be processed.
Completed with Limitations (routing case only): No routing result was determined for one or more transactions within the maximum waiting time, and the fallback routing to the default receiver was used.
Completed Manually: The message processing is considered done, and the status was set manually by you or another user.
When this status is set, no technical change is made or triggered. It's for tracking purposes only, allowing you to clean up your list of market messages. This status is useful for scenarios like when the message had an issue that was later resolved, but the Error status never changed, among others.
Terminated Manually: The message processing is terminated, and the status was set manually by you or another user.
When this status is set, the message processing in the market communication system is stopped. This status is also displayed when you use the termination functionality in the Display Message Exchange Issues app to stop the processing of the market message along with the related message exchange issue.
Sending Failed: Sending the market message via AS4 or Web API from the AS4 or Web API service provider to the communication market partner failed.
You should actively monitor messages with this status. To find out more details about the cause, select Display Status Information to view the Web API status response payload (for Web API messages) or the NRR information (for AS4 messages).
To resolve the issue, try reprocessing the message. If reprocessing isn't successful, contact your AS4 or Web API service provider, or your market partner, depending on the cause of the failure. For example, if the status information message is "Receiver system not reachable" or "Receiver partner ID doesn't exist", contact your AS4 or Web API service provider. If the status information message is "Receiver AS4 certificate is expired" or "Receiver AS4 certificate is missing", you should contact your communication market partner directly.
Note If you use the integrated AS4 or Web API service provider, report an incident to SAP for more information. If you use an external AS4 or Web API service provider, contact your service provider directly for more information.
Note
When sending via AS4 or Web API has failed from SAP Market Communication for Utilities to the AS4 or Web API service provider, the Error status is used.

When sending has failed for communication methods that use synchronized sending (such as email and AS2), the Error status is used.
Queued for Sending: The message is waiting to be sent via AS4 or Web API.
In Retry by System: If you have enabled automatic retry by system for messages that are in status Sending Failed, this status is displayed before the messages' processing status changes to Queued for Sending. The system will automatically attempt to send the message at configured intervals.

Displays the general technical status of the market message processing.

For split market messages, the message processing status displayed in the header of the split message is determined by the status of the forwarded messages.

The following statuses are possible:

Started: The message processing has begun.
Error: The message processing ran into an error. Go to the error information to learn more.
If no data is found in the Display Message Exchange Issues app, report an incident.
Routing Pending: The message went to the routing service that tried to determine routing targets for the message and the contained transactions. However, the service has failed to determine a unique target for at least one of the transactions, which requires manual intervention by you using the Clarify Message Routing app.
Completed: 1. An inbound message has been received and handed over to a predefined market process or routed to a target receiver. In the case of an original message that has been split and routed, all transactions were split into new messages and successfully routed to a target receiver.
2. An outbound message has been sent out to the communication market partner. In the case of an original message that has been split and routed, all transactions were split into new messages and routed to a target receiver.
Completed with Negative Validation: 1. An inbound message failed the validation (the CONTRL or APERAK validation) for at least one transaction, and the corresponding rejection was sent back to the communication market partner. The transactions that passed the validation continue to be processed.
2. An outbound message coming from a market process or internal market partner failed the validation, and a rejection has been sent back to the process or internal market partner. The transactions that passed the validation continue to be processed.
Completed with Limitations (routing case only): No routing result was determined for one or more transactions within the maximum waiting time, and the fallback routing to the default receiver was used.
Completed Manually: The message processing is considered done, and the status was set manually by you or another user.
When this status is set, no technical change is made or triggered. It's for tracking purposes only, allowing you to clean up your list of market messages. This status is useful for scenarios like when the message had an issue that was later resolved, but the Error status never changed, among others.
Terminated Manually: The message processing is terminated, and the status was set manually by you or another user.
When this status is set, the message processing in the market communication system is stopped. This status is also displayed when you use the termination functionality in the Display Message Exchange Issues app to stop the processing of the market message along with the related message exchange issue.
Sending Failed: Sending the market message via AS4 or Web API from the AS4 or Web API service provider to the communication market partner failed.
You should actively monitor messages with this status. To find out more details about the cause, select Display Status Information to view the Web API status response payload (for Web API messages) or the NRR information (for AS4 messages).
To resolve the issue, try reprocessing the message. If reprocessing isn't successful, contact your AS4 or Web API service provider, or your market partner, depending on the cause of the failure. For example, if the status information message is "Receiver system not reachable" or "Receiver partner ID doesn't exist", contact your AS4 or Web API service provider. If the status information message is "Receiver AS4 certificate is expired" or "Receiver AS4 certificate is missing", you should contact your communication market partner directly.
Note If you use the integrated AS4 or Web API service provider, report an incident to SAP for more information. If you use an external AS4 or Web API service provider, contact your service provider directly for more information.
Note
When sending via AS4 or Web API has failed from SAP Market Communication for Utilities to the AS4 or Web API service provider, the Error status is used.

When sending has failed for communication methods that use synchronized sending (such as email and AS2), the Error status is used.
Queued for Sending: The message is waiting to be sent via AS4 or Web API.
In Retry by System: If you have enabled automatic retry by system for messages that are in status Sending Failed, this status is displayed before the messages' processing status changes to Queued for Sending. The system will automatically attempt to send the message at configured intervals.

Filter by the status that reflects the acknowledgment and validation state of messages exchanged with market partners.

The business status primarily reflects the outcomes of validation checks and related responses, such as Negative APERAK, but also includes additional cases, such as New and Message Reprocessed.

The following business statuses are possible:

Inbound Messages
Status	Message Format	Description
New	Non-CONTRL and non-APERAK message	The initial status when a message is received or created in SAP Market Communication for Utilities but has not yet undergone processing.
	APERAK message
	CONTRL message
Negative CONTRL	Non-CONTRL and non-APERAK message	The inbound message failed the CONTRL validation, but a negative CONTRL message has not yet been sent to your communication market partner.
	APERAK message
	CONTRL message	This business status can have one of the following meanings: The inbound CONTRL message failed the CONTRL validation, but a negative CONTRL message has not yet been sent to your communication market partner. The inbound CONTRL message failed the CONTRL validation, and a negative CONTRL message has been sent to your communication market partner.
Positive CONTRL	Non-CONTRL and non- APERAK message	The inbound message passed the CONTRL validation, but a positive CONTRL message has not yet been sent to your communication market partner. This business status is only valid for the gas division.
	APERAK message
	CONTRL message	This business status can have one of the following meanings: The inbound CONTRL message passed the CONTRL validation, but a positive CONTRL message has not yet been sent to your communication market partner. The inbound CONTRL message passed the CONTRL validation, and a positive CONTRL message has been sent to your communication market partner. This business status is only valid for the gas division.
Negative CONTRL Sent	Non-CONTRL and non-APERAK message	The inbound message failed the CONTRL validation, and a negative CONTRL message was sent to your communication market partner.
Negative CONTRL Sent	APERAK message
Positive CONTRL Sent	Non-CONTRL and non-APERAK message	The inbound message passed the CONTRL validation, and a positive CONTRL message was sent to the the communication market partner. This business status is only valid for the gas division.
Positive CONTRL Sent	APERAK message
Negative APERAK	Non-CONTRL and non-APERAK message	The inbound message failed the APERAK validation, but a negative APERAK message has not yet been sent to your communication market partner.
Negative APERAK Sent	Non-CONTRL and non-APERAK message	The inbound message failed the APERAK validation, and a negative APERAK message was sent to your communication market partner.
Int. Negative APERAK Received	APERAK message	The inbound APERAK message failed the internal APERAK validation, and an internal negative APERAK was generated by the MMT component.
Int. Negative CONTRL Received	CONTRL message	The inbound CONTRL message failed the internal CONTRL validation, and an internal negative CONTRL message was generated by the MMT component.
APERAK Missing	Non-CONTRL and non-APERAK message	At least one transaction in the message hasn't received or sent an APERAK message. In the scenario where some transactions haven't received an APERAK message and some have received a negative APERAK message, the business status Ext. Negative APERAK Received is given priority over the APERAK Missing status. This business status is only valid for the electricity division.
Positive APERAK	APERAK Message	The inbound message passed the APERAK validation, but a positive APERAK message has not yet been sent to your communication market partner. This business status is only valid for the electricity division.
Positive APERAK Sent	Non-CONTRL and non-APERAK message	All transactions in the inbound message passed the APERAK validation, and a positive APERAK message was sent to your communication market partner. This business status is only valid for the electricity division.
Positive APERAK Sent	APERAK message
Positive APERAK Received	Non-CONTRL and non-APERAK message	All transactions in the outbound message passed the APERAK validation, and a positive APERAK was received from your communication market partner. This business status is only valid for the electricity division.
Message Reprocessed	Non-CONTRL and non-APERAK message	The message was reimported into SAP Market Communication for Utilities or resent to your communication market partner.

Outbound Messages
Status	Message Format	Description
New	Non-CONTRL and non-APERAK message	The initial status when a message is received or created in SAP Market Communication for Utilities but has not yet undergone processing.
	APERAK message
	CONTRL message
Rejected by Internal CONTRL	Non-CONTRL and non-APERAK message	The outbound message failed the internal CONTRL validation, and an internal negative CONTRL message was generated by the MMT component.
Rejected by Internal CONTRL	APERAK message
Rejected by Internal APERAK	Non-CONTRL and non-APERAK message	The outbound message failed the internal APERAK validation, and an internal negative APERAK message was generated by the MMT component.
Sent	Non-CONTRL and non-APERAK message	The outbound message has been sent to the external market partner from the own market partner or the internal market partner.
Sent	APERAK message	The outbound APERAK message was sent to the communication market partner.
Positive CONTRL Received	Non-CONTRL and non-APERAK message	The outbound message received a positive CONTRL message from your communication market partner. This business status is only valid for the gas division.
Positive CONTRL Received	APERAK message
Ext. Negative CONTRL Received	Non-CONTRL and non-APERAK message	The outbound APERAK message failed the CONTRL validation, and a negative CONTRL message was received from the communication market partner.
Ext. Negative CONTRL Received	APERAK message
Ext. Negative APERAK Received	Non-CONTRL and non-APERAK message	The outbound message received a negative APERAK message from your communication market partner. In the scenario where some transactions haven't received an APERAK message and some have received a negative APERAK message, the business status Ext. Negative APERAK Received is given priority over the APERAK Missing status.
Positive APERAK	APERAK Message	The outbound message passed the APERAK validation, but a positive APERAK message has not yet been received by your communication market partner. This business status is only valid for the electricity division.
Positive APERAK Received	Non-CONTRL and non-APERAK message	All transactions in the outbound message passed the APERAK validation, and a positive APERAK was received from your communication market partner. This business status is only valid for the electricity division.
APERAK Missing	Non-CONTRL and non-APERAK message	At least one transaction in the message hasn't received or sent an APERAK message. In the scenario where some transactions haven't received an APERAK message and some have received a negative APERAK message, the business status Ext. Negative APERAK Received is given priority over the APERAK Missing status. This business status is only valid for the electricity division.
Internal Negative APERAK for 3rd Partner	Non-CONTRL and non-APERAK message	The outbound split message intended for a third party or an external market partner partially or entirely failed the internal APERAK validation. If the split message failed the internal APERAK validation partially, it is sent with only those transactions that passed the internal APERAK validation. If the split message failed the internal APERAK validation entirely, all transactions in the message failed the APERAK validation. The message isn't sent and is recorded only in the market communication system. The message can't be resent. Note This status is valid only for split messages.
Message Reprocessed	Non-CONTRL and non-APERAK message	The message was reimported into SAP Market Communication for Utilities or resent to your communication market partner.

Abbreviations: MMT - market message transfer.

Displays the status that reflects the acknowledgment and validation state of messages exchanged with market partners.

The business status primarily reflects the outcomes of validation checks and related responses, such as Negative APERAK, but also includes additional cases, such as New and Message Reprocessed.

The following business statuses are possible:

Inbound Messages
Status	Message Format	Description
New	Non-CONTRL and non-APERAK message	The initial status when a message is received or created in SAP Market Communication for Utilities but has not yet undergone processing.
	APERAK message
	CONTRL message
Negative CONTRL	Non-CONTRL and non-APERAK message	The inbound message failed the CONTRL validation, but a negative CONTRL message has not yet been sent to your communication market partner.
	APERAK message
	CONTRL message	This business status can have one of the following meanings: The inbound CONTRL message failed the CONTRL validation, but a negative CONTRL message has not yet been sent to your communication market partner. The inbound CONTRL message failed the CONTRL validation, and a negative CONTRL message has been sent to your communication market partner.
Positive CONTRL	Non-CONTRL and non- APERAK message	The inbound message passed the CONTRL validation, but a positive CONTRL message has not yet been sent to your communication market partner. This business status is only valid for the gas division.
	APERAK message
	CONTRL message	This business status can have one of the following meanings: The inbound CONTRL message passed the CONTRL validation, but a positive CONTRL message has not yet been sent to your communication market partner. The inbound CONTRL message passed the CONTRL validation, and a positive CONTRL message has been sent to your communication market partner. This business status is only valid for the gas division.
Negative CONTRL Sent	Non-CONTRL and non-APERAK message	The inbound message failed the CONTRL validation, and a negative CONTRL message was sent to your communication market partner.
Negative CONTRL Sent	APERAK message
Positive CONTRL Sent	Non-CONTRL and non-APERAK message	The inbound message passed the CONTRL validation, and a positive CONTRL message was sent to the the communication market partner. This business status is only valid for the gas division.
Positive CONTRL Sent	APERAK message
Negative APERAK	Non-CONTRL and non-APERAK message	The inbound message failed the APERAK validation, but a negative APERAK message has not yet been sent to your communication market partner.
Negative APERAK Sent	Non-CONTRL and non-APERAK message	The inbound message failed the APERAK validation, and a negative APERAK message was sent to your communication market partner.
Int. Negative APERAK Received	APERAK message	The inbound APERAK message failed the internal APERAK validation, and an internal negative APERAK was generated by the MMT component.
Int. Negative CONTRL Received	CONTRL message	The inbound CONTRL message failed the internal CONTRL validation, and an internal negative CONTRL message was generated by the MMT component.
APERAK Missing	Non-CONTRL and non-APERAK message	At least one transaction in the message hasn't received or sent an APERAK message. In the scenario where some transactions haven't received an APERAK message and some have received a negative APERAK message, the business status Ext. Negative APERAK Received is given priority over the APERAK Missing status. This business status is only valid for the electricity division.
Positive APERAK	APERAK Message	The inbound message passed the APERAK validation, but a positive APERAK message has not yet been sent to your communication market partner. This business status is only valid for the electricity division.
Positive APERAK Sent	Non-CONTRL and non-APERAK message	All transactions in the inbound message passed the APERAK validation, and a positive APERAK message was sent to your communication market partner. This business status is only valid for the electricity division.
Positive APERAK Sent	APERAK message
Positive APERAK Received	Non-CONTRL and non-APERAK message	All transactions in the outbound message passed the APERAK validation, and a positive APERAK was received from your communication market partner. This business status is only valid for the electricity division.
Message Reprocessed	Non-CONTRL and non-APERAK message	The message was reimported into SAP Market Communication for Utilities or resent to your communication market partner.

Outbound Messages
Status	Message Format	Description
New	Non-CONTRL and non-APERAK message	The initial status when a message is received or created in SAP Market Communication for Utilities but has not yet undergone processing.
	APERAK message
	CONTRL message
Rejected by Internal CONTRL	Non-CONTRL and non-APERAK message	The outbound message failed the internal CONTRL validation, and an internal negative CONTRL message was generated by the MMT component.
Rejected by Internal CONTRL	APERAK message
Rejected by Internal APERAK	Non-CONTRL and non-APERAK message	The outbound message failed the internal APERAK validation, and an internal negative APERAK message was generated by the MMT component.
Sent	Non-CONTRL and non-APERAK message	The outbound message has been sent to the external market partner from the own market partner or the internal market partner.
Sent	APERAK message	The outbound APERAK message was sent to the communication market partner.
Positive CONTRL Received	Non-CONTRL and non-APERAK message	The outbound message received a positive CONTRL message from your communication market partner. This business status is only valid for the gas division.
Positive CONTRL Received	APERAK message
Ext. Negative CONTRL Received	Non-CONTRL and non-APERAK message	The outbound APERAK message failed the CONTRL validation, and a negative CONTRL message was received from the communication market partner.
Ext. Negative CONTRL Received	APERAK message
Ext. Negative APERAK Received	Non-CONTRL and non-APERAK message	The outbound message received a negative APERAK message from your communication market partner. In the scenario where some transactions haven't received an APERAK message and some have received a negative APERAK message, the business status Ext. Negative APERAK Received is given priority over the APERAK Missing status.
Positive APERAK	APERAK Message	The outbound message passed the APERAK validation, but a positive APERAK message has not yet been received by your communication market partner. This business status is only valid for the electricity division.
Positive APERAK Received	Non-CONTRL and non-APERAK message	All transactions in the outbound message passed the APERAK validation, and a positive APERAK was received from your communication market partner. This business status is only valid for the electricity division.
APERAK Missing	Non-CONTRL and non-APERAK message	At least one transaction in the message hasn't received or sent an APERAK message. In the scenario where some transactions haven't received an APERAK message and some have received a negative APERAK message, the business status Ext. Negative APERAK Received is given priority over the APERAK Missing status. This business status is only valid for the electricity division.
Internal Negative APERAK for 3rd Partner	Non-CONTRL and non-APERAK message	The outbound split message intended for a third party or an external market partner partially or entirely failed the internal APERAK validation. If the split message failed the internal APERAK validation partially, it is sent with only those transactions that passed the internal APERAK validation. If the split message failed the internal APERAK validation entirely, all transactions in the message failed the APERAK validation. The message isn't sent and is recorded only in the market communication system. The message can't be resent. Note This status is valid only for split messages.
Message Reprocessed	Non-CONTRL and non-APERAK message	The message was reimported into SAP Market Communication for Utilities or resent to your communication market partner.

Abbreviations: MMT - market message transfer.

Displays the status that reflects the acknowledgment and validation state of messages exchanged with market partners.

The business status primarily reflects the outcomes of validation checks and related responses, such as Negative APERAK, but also includes additional cases, such as New and Message Reprocessed.

The following business statuses are possible:

Inbound Messages
Status	Message Format	Description
New	Non-CONTRL and non-APERAK message	The initial status when a message is received or created in SAP Market Communication for Utilities but has not yet undergone processing.
	APERAK message
	CONTRL message
Negative CONTRL	Non-CONTRL and non-APERAK message	The inbound message failed the CONTRL validation, but a negative CONTRL message has not yet been sent to your communication market partner.
	APERAK message
	CONTRL message	This business status can have one of the following meanings: The inbound CONTRL message failed the CONTRL validation, but a negative CONTRL message has not yet been sent to your communication market partner. The inbound CONTRL message failed the CONTRL validation, and a negative CONTRL message has been sent to your communication market partner.
Positive CONTRL	Non-CONTRL and non- APERAK message	The inbound message passed the CONTRL validation, but a positive CONTRL message has not yet been sent to your communication market partner. This business status is only valid for the gas division.
	APERAK message
	CONTRL message	This business status can have one of the following meanings: The inbound CONTRL message passed the CONTRL validation, but a positive CONTRL message has not yet been sent to your communication market partner. The inbound CONTRL message passed the CONTRL validation, and a positive CONTRL message has been sent to your communication market partner. This business status is only valid for the gas division.
Negative CONTRL Sent	Non-CONTRL and non-APERAK message	The inbound message failed the CONTRL validation, and a negative CONTRL message was sent to your communication market partner.
Negative CONTRL Sent	APERAK message
Positive CONTRL Sent	Non-CONTRL and non-APERAK message	The inbound message passed the CONTRL validation, and a positive CONTRL message was sent to the the communication market partner. This business status is only valid for the gas division.
Positive CONTRL Sent	APERAK message
Negative APERAK	Non-CONTRL and non-APERAK message	The inbound message failed the APERAK validation, but a negative APERAK message has not yet been sent to your communication market partner.
Negative APERAK Sent	Non-CONTRL and non-APERAK message	The inbound message failed the APERAK validation, and a negative APERAK message was sent to your communication market partner.
Int. Negative APERAK Received	APERAK message	The inbound APERAK message failed the internal APERAK validation, and an internal negative APERAK was generated by the MMT component.
Int. Negative CONTRL Received	CONTRL message	The inbound CONTRL message failed the internal CONTRL validation, and an internal negative CONTRL message was generated by the MMT component.
APERAK Missing	Non-CONTRL and non-APERAK message	At least one transaction in the message hasn't received or sent an APERAK message. In the scenario where some transactions haven't received an APERAK message and some have received a negative APERAK message, the business status Ext. Negative APERAK Received is given priority over the APERAK Missing status. This business status is only valid for the electricity division.
Positive APERAK	APERAK Message	The inbound message passed the APERAK validation, but a positive APERAK message has not yet been sent to your communication market partner. This business status is only valid for the electricity division.
Positive APERAK Sent	Non-CONTRL and non-APERAK message	All transactions in the inbound message passed the APERAK validation, and a positive APERAK message was sent to your communication market partner. This business status is only valid for the electricity division.
Positive APERAK Sent	APERAK message
Positive APERAK Received	Non-CONTRL and non-APERAK message	All transactions in the outbound message passed the APERAK validation, and a positive APERAK was received from your communication market partner. This business status is only valid for the electricity division.
Message Reprocessed	Non-CONTRL and non-APERAK message	The message was reimported into SAP Market Communication for Utilities or resent to your communication market partner.

Outbound Messages
Status	Message Format	Description
New	Non-CONTRL and non-APERAK message	The initial status when a message is received or created in SAP Market Communication for Utilities but has not yet undergone processing.
	APERAK message
	CONTRL message
Rejected by Internal CONTRL	Non-CONTRL and non-APERAK message	The outbound message failed the internal CONTRL validation, and an internal negative CONTRL message was generated by the MMT component.
Rejected by Internal CONTRL	APERAK message
Rejected by Internal APERAK	Non-CONTRL and non-APERAK message	The outbound message failed the internal APERAK validation, and an internal negative APERAK message was generated by the MMT component.
Sent	Non-CONTRL and non-APERAK message	The outbound message has been sent to the external market partner from the own market partner or the internal market partner.
Sent	APERAK message	The outbound APERAK message was sent to the communication market partner.
Positive CONTRL Received	Non-CONTRL and non-APERAK message	The outbound message received a positive CONTRL message from your communication market partner. This business status is only valid for the gas division.
Positive CONTRL Received	APERAK message
Ext. Negative CONTRL Received	Non-CONTRL and non-APERAK message	The outbound APERAK message failed the CONTRL validation, and a negative CONTRL message was received from the communication market partner.
Ext. Negative CONTRL Received	APERAK message
Ext. Negative APERAK Received	Non-CONTRL and non-APERAK message	The outbound message received a negative APERAK message from your communication market partner. In the scenario where some transactions haven't received an APERAK message and some have received a negative APERAK message, the business status Ext. Negative APERAK Received is given priority over the APERAK Missing status.
Positive APERAK	APERAK Message	The outbound message passed the APERAK validation, but a positive APERAK message has not yet been received by your communication market partner. This business status is only valid for the electricity division.
Positive APERAK Received	Non-CONTRL and non-APERAK message	All transactions in the outbound message passed the APERAK validation, and a positive APERAK was received from your communication market partner. This business status is only valid for the electricity division.
APERAK Missing	Non-CONTRL and non-APERAK message	At least one transaction in the message hasn't received or sent an APERAK message. In the scenario where some transactions haven't received an APERAK message and some have received a negative APERAK message, the business status Ext. Negative APERAK Received is given priority over the APERAK Missing status. This business status is only valid for the electricity division.
Internal Negative APERAK for 3rd Partner	Non-CONTRL and non-APERAK message	The outbound split message intended for a third party or an external market partner partially or entirely failed the internal APERAK validation. If the split message failed the internal APERAK validation partially, it is sent with only those transactions that passed the internal APERAK validation. If the split message failed the internal APERAK validation entirely, all transactions in the message failed the APERAK validation. The message isn't sent and is recorded only in the market communication system. The message can't be resent. Note This status is valid only for split messages.
Message Reprocessed	Non-CONTRL and non-APERAK message	The message was reimported into SAP Market Communication for Utilities or resent to your communication market partner.

Abbreviations: MMT - market message transfer.

Filter by entering the ID of the external market partner or internal market partner, who can be the original sender or receiver of the market message.

For inbound messages, the sender is the communication market partner, and the receiver is the own market partner. For outbound messages, it's the opposite.

For more information about communication market partners, see Managing Market Partner Data.

Filter by the standard communication type used for electronic data interchange (EDI) between market partners.

These message formats may include traditional EDI message formats such as ORDCHG and MSCONS or Web API request formats, such as endpoint calls like /maloId/request.

Filter by the unique code that classifies a message that is exchanged between different market partners.

For example, in the energy market in Germany, this is known as the application message identifier (AMID), which is a five-digit key that is used to identify a message pattern.

Displays how the system came to the routing result and determined the target for the message.

The following options are possible:

Routing Service: The routing service determined a target by scanning through your location lists and applying your routing rules.
Message Reference: The target was determined automatically based on a previous related message, for example, an inbound REMADV message that is a direct response to a previous outbound INVOIC message.
Override: The target was overruled manually in the Clarify Message Routing app, using the Override Routing Target button.
Default Receiver: The target is the original receiver of the message sent by the communication market partner since a target wasn’t determined via the routing service, message reference, or override.
In the case of a REMADV message with segment BGM 239, if no receiver was determined from the routing service, the fixed behavior is that the message doesn't pass on to the default receiver's system, but instead waits for you to take action in the Clarify Message Routing app.
Default Receiver of REMADV: When the determined target for the documents of a REMADV message with segment BGM 481 isn't the original receiver in the UNB segment, an additional routing service record is created with the original receiver as the target.

Displays the reason why the routing is still pending for the market message.

The following reasons are possible:

Non-unique routing result
No forwarding market partner
No market partner determined
Invalid market partner ID
No response from rules service
Multiple errors
Undefined error

Filter by how many minutes late the CONTRL message is for a market message.

This counter considers the difference between the time when the CONTRL message was received or sent and the time the original message was received or sent.

If the CONTRL is over a day late, the counter stops tracking, and only 1440 is displayed. In this case, the business status is Sent.

Filter by the segment and error code for why a negative APERAK or CONTRL was received.

Upload one or more TXT files or a single JSON file to manually create a (non-split) market message or a Web API JSON.

When sending market messages in this manner, internal APERAK and CONTRL validations are skipped.

The creation event can be reviewed in the reprocessing history of the message.

For more information, see Creating EDIFACT Market Messages Manually and Creating a Web API JSON Manually.

Retrigger the splitting and routing of the selected market messages manually.

Message Selection

By selecting Run for Filtered, you are rerunning the routing for the market messages that have been filtered out by your filter settings that are eligible for rerunning the routing, not just the ones currently loaded on the screen. The number of messages eligible for rerunning the routing may be smaller than the number of filtered out messages. If the number should be different, try changing your filter settings.

Note

Select Inbound in the Message Direction filter and Yes in the Split Message filter to find eligible messages more quickly.

By selecting Run for Selected, you are rerunning the routing only for the market messages you have individually selected.

General Information

The system automatically retries to split and route messages in the statuses Error and Routing Pending periodically.

When the routing is retriggered automatically or manually, information isn't sent again to the already supplied receivers or targets, only to new ones.

When the routing is rerun, each instance and its details are logged in the rerun-routing history of the message.

The system uses asynchronous background jobs to rerun routing for batches of market messages. You can view the logs of your jobs directly in the Display Async Job Logs app.

Eligibility

Only market messages that fill the following criteria are eligible for rerunning the routing:

Message processing status is other than Started
Business status is other than Rejected by Internal APERAK or Rejected by Internal CONTRL

Scenarios

Usually, you rerun routing manually in the following cases:

For market messages, excluding APERAKs and CONTRLs, that have a message processing status other than Started and don't have the business status Rejected by Internal APERAK or Rejected by Internal CONTRL, you can rerun the routing because of a change in the routing configuration, an error correction, or for other exceptional cases.
For messages that (partially) failed in the routing and are stuck in status Routing Pending, you can go to the clarification to get an idea of what went wrong and to fix the issue first.
After the clarification, it's best to supply the new routing targets immediately and not wait for the automatic retry.
For messages that are in one of the Completed statuses but have been sent to the wrong targets, you can fix the targets by going to the clarification.
After the clarification, you must rerun the routing because there are no automatic retries for completed messages.

Resend or reimport one or more market messages at the message level for error corrections.

The payload isn't changed during reprocessing. When resending a message that has been split, the split message, not the original message, is resent to your communication market partner. Any changes that were made in the communication configuration since the original sending or receiving are taken into account during reprocessing.

Note When reprocessing inbound messages, the system uses the UNB date as the message transfer date for validation.

Message Selection

By selecting Reprocess for Filtered, you are reprocessing all market messages that have been filtered out by your filter settings, not just the ones currently loaded on the screen.

Note

The Split Message and Communication Method filters must be filled in. The Message Direction filter is required for non-split messages only.

By selecting Reprocess for Selected, you are reprocessing only the market messages you have individually selected.

Note

You can only reprocess multiple messages simultaneously when they have the same message direction and communication method.

Non-Split Market Messages

For the Reprocess for Selected option, reprocessing isn't permitted for market messages with Started or Error as their message processing status.

Split Market Messages

For the Reprocess for Selected option, reprocessing isn't permitted for market messages in the following cases:

Messages with the message processing status Error or Started
Inbound messages with the business status Negative CONTRL Sent
Outbound messages with the business status Internal Negative APERAK For 3rd Partner
All CONTRL messages

Additional Information

In the Reprocessing Status field, a successful reprocessing displays the status Completed, while an unsuccessful attempt shows Error. Review the reprocessing history in the message details for more information.

For the Reprocess for Filtered option, you can view the job in the Display Async Job Logs app for more details.

For split messages, the message status should change from Transferred to Retransferred in the Split Messages section in the message details.

For more details and step-by-step instructions, see the following topics on the SAP Help Portal:

Reprocess your message considering the options provided in the dialogue box.

The scenario, such as non-split or split message, message direction, communication method, among others, dictates which options are presented. This information is a general overview considering all scenarios.

Caution

For optimal performance, don't reprocess more than 10,000 messages simultaneously.

If there's a discrepancy between the number of market messages on the list page and the number reported in this dialog box, the number in this dialog box is correct because it reflects real-time data. In contrast, the list page doesn't update instantly and requires a page refresh for real-time accuracy.

Sender and Receiver Information

Use Market Partners from Payload: Use the same own and communication market partners that are listed in the UNB segment of the original market message.
Use Market Partners from Message Header: Use the same own and communication market partners that are listed in the message header of the original market message.
Replace Market Partners: Replace one or both the own and communication market partners with another that you've maintained in the Manage Market Partners app for reprocessing.

Receivers for Reprocessing

When reprocessing split messages based on your filter settings, you have the following options to consider:

For reimporting, select the same own market partner from the message as the receiver.
For resending, select the same internal market partners used for copying and forwarding the message.

When reprocessing split messages that you've individually selected, you have the following options to consider:

For reimporting, select the same own market partner from the message as the receiver.
For resending, select any receiver that isn't your own market partner.

Additional Settings

Technical Response: Skip the technical response if you don't want to send any new response CONTRL to your market partner.
Positive APERAK Response: Skip resending a positive APERAK response to your market partner.

Other Information / Reprocess Reason

Reimport Reason: Explain why you reimported the message. This reason is shown in the reprocessing history of the message.
Resend Reason: Explain why you resent the message. This reason is shown in the reprocessing history of the message.

Filter by the reprocessing status, which indicates whether reprocessing of the message was successful or not.

The following statuses are possible:

Processing Started: Reprocessing has triggered.
Completed: Reprocessing was successful.
Error: Reprocessing failed due to a technical issue.

If the status stays in Processing Started significantly longer than a normal processing time, or the message processing status is Error, select Go to Error Information to review the issue in the Display Message Exchange Issues app. If the issue can't be fixed, or if the issue doesn't exist in the app, report an incident.

Note These fields are only displayed for market messages in the electricity division.

Number of Transactions Accepted by Positive APERAKs displays the number of transactions accepted by positive APERAK messages for the market message. When all transactions in the market message (excluding APERAK and CONTRL messages) received a positive APERAK, the market message has the Positive APERAK Received business status.

Number of Transactions Rejected by Negative APERAKs displays the number of transactions rejected by negative APERAK messages for the market message. When at least one transaction in the market message (excluding APERAK and CONTRL messages) received a negative APERAK, the market message has the Ext. Negative APERAK Received business status.

Number of Transactions Missing APERAKs displays the number of transactions missing APERAK messages for the market message. When at least one transaction in the market message (excluding APERAK and CONTRL messages) hasn't received an APERAK message, the market message has the APERAK Missing business status. However, if a negative APERAK has been received, the Ext. Negative APERAK Received business status is given priority.

If the market message was rejected by a negative CONTRL, these fields provide no information.

For market messages received before the format change on June 6, 2025, and the introduction of the positive APERAK message, no information is displayed for these fields.

Note For non-split REMADV messages, one of these fields shows the value "1" and the other fields show value "0".

Note For split REMADV messages that receive a response APERAK only on the header level one of these fields shows the value "1" and the other fields show "0", regardless of the number of transactions in the message.

Note For COMDIS messages that receive a response APERAK on the header level, one of these fields shows the value "1" and the other fields show value "0", regardless of the number of transactions in the message.

Note In a scenario where a market message such as UTILMD is rejected by an APERAK on the header level, all transactions in the message are rejected as well. In this case, the number of transactions missing APERAKs is updated based on the total number of transactions in the message.

Lists all the follow-up split messages that have been forwarded or copied to other market partners or systems for one original market message.

There is one entry per receiver and scenario. For example, a transaction of the original inbound message has been forwarded to one receiver using one follow-up message, and copied to another receiver using a second follow-up message. In this case, there are two entries, one with scenario Inbound Forwarding and one with Inbound Copying.

Note

Selecting a forwarded message and choosing Display Payload here, displays the payload of the forwarded or copied message only. While the Display Payload on the top of the screen displays the payload of the original message before the split.

Displays the transaction processing and routing history to monitor and view details of where transactions were routed.

Transaction Processing

In the inbound case, this table lists all the transactions included in the message that was copied to your own market partner as the target receiver, and consequently to your SAP for Utilities business system.

In the outbound case, this table lists all the transactions included in the message that was sent to your external market partner (who has an SAP for Utilities business system).

Note

For this information to be displayed, the receiver must be an SAP for Utilities business system. In addition, the related market process must be enabled with the new aggregation pattern, for example, the processes listed with the "Single Uploads and Aggregated Process Documents" aggregation pattern. See Aggregation-Enabled Message Formats.

You can navigate to the relevant process document and find the common access reference from the transaction details. When a transaction is routed and forwarded to an internal market partner, not processed by an SAP for Utilities business system, no common access reference is generated.

Transaction Routing History

Lists all transactions that belong to the current market message and the parameters by which their routing results were determined.

In the table, you might only see a subset of the applied routing parameters for a transaction. Choose Display Routing Parameters to display them all.

Note In the splitter case, each transaction here corresponds to one or more forwarded messages in the Split Messages table.

Lists all transactions that belong to the current market message and their details.

For non-split COMDIS messages, this section lists all transactions attached to the market message. For non-split REMADV messages, this section shows one transaction.

Displays the address the market message is sent to.

Note

In your test system, when you have configured a communication arrangement to skip sending outbound messages for test purposes in the Manage Communication Arrangements app, this field displays the value Suppressed.

For more information about communication arrangements, see:

AS4 connections: Manage Outbound Communication Arrangements for AS4
AS2 connections: Manage Communication Arrangements for AS2
Email connections: Manage Communication Arrangements for Email

Lists all other market messages that are directly related to the current message.

The most common related messages are acknowledgment messages like APERAK and CONTRL. In addition, there can be standard business responses to messages of certain types, for example, a payment advice (REMADV) in response to an invoice (INVOIC), or an order response (ORDRSP) to a previous order (ORDERS).

Displays the data exchange reference to the latest related APERAK message for the transaction.

The latest related APERAK has most recently impacted the transaction status.

Lists all other market messages that are directly related to the current message.

The most common related messages are acknowledgment messages like APERAK and CONTRL. In addition, there can be standard business responses to messages of certain types, for example, a payment advice (REMADV) in response to an invoice (INVOIC), or an order response (ORDRSP) to a previous order (ORDERS).

Lists each instance the market message was resent or reimported with additional details.

You can view who reprocessed the message and why for each instance.

Lists all market processes that are directly related to the current message and enables you to navigate to the Display Market Processes and Monitor Process Documents apps for further details.

By clicking the market process, you can navigate to the message details in the Display Market Processes app.

To view process details in the Monitor Process Documents app, select the related process and then choose Details.

Lists each instance the routing was rerun for the market message.

You can view who reran the routing and why for each instance.

Resend or reimport the selected split message again.

Resending

The Reprocess button allows you to resend a split message in the following cases:

It's an inbound market message from your communication market partner that is being copied or forwarded to an internal market partner.
It's your outbound market message being copied or forwarded to a communication market partner.

Reimporting

The Reprocess button allows you to reimport a split message in the following cases:

It's an inbound market message from your external partner that will be processed by SAP Market Communications for Utilities. In this case, the receiver is the own market partner who's listed in the message header.

Reimport the selected transactions again.

Transactions can be reimported for non-split and split inbound market messages that are forwarded to your own market partner. The message must have a completed message processing status. Transactions in negative APERAK, CONTRL, REMADV, or COMDIS messages can't be reimported.

Optional: Positive APERAK Response: When reprocessing transactions, you can skip sending a positive APERAK response to your market partner by selecting the option.

Once you've reprocessed a transaction, you can find the reprocessing information in the Reprocessing History section.

For more information see, Reprocessing a Transaction.

Displays the technical status of the processing of the split market message.

The following statuses are possible:

Grouped: This is the initial status. The message hasn't been split and sent to the target receiver yet.
Transferred: The split message has been forwarded or copied to the target receiver.
Transferred to Default: The split message has been forwarded or copied to the default receiver since a target was not determined via the routing service, message reference, or override before the maximum processing time was reached.
Note
The behavior is different for a REMADV message.

For example, when an inbound REMADV with BGM code 481 is received, the whole message is transferred to the own market partner (the original UNB receiver of the REMADV is always a target in this case). Since all the transactions have a target receiver, the Transferred to Default status is unnecessary. Or, in the case of a negative REMADV with BGM code 239, the Transferred to Default status is unnecessary because the own market partner (target receiver) can't handle these messages anyway.
Retransferred: The split message has been forwarded or copied again to the target receiver again, or reimported.
Queued for Sending: The message is waiting to be sent via AS4 or Web API.
Sending Failed: Sending the split market message via AS4 or Web API from the AS4 or Web API service provider to the communication market partner failed.
Error: An error occurred when processing or reprocessing the split message.
Obsolete: This split message is no longer relevant due to changes made in the routing configuration. A new split message has been created to replace it.