How To Fix SRT_CORE274 - Message is split

SAP Error Message - Details

• Message type: E = Error

• Message class: SRT_CORE - Nachrichtenklasse für SOAP Runtime

• Message number: 274

• Message text: Message is split

What causes this issue?

Message is split into different messages for a distributed processing. A
split can be requested by a web service application in some error cases
(Error Split) or based on the proxy configuration. The message status
shows exactly the split reason.

System Response

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

How to fix this error?

No action required

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message SRT_CORE274 - Message is split ?

  The SAP error message SRT_CORE274 ("Message is split") typically occurs in the context of SAP Process Integration (PI) or SAP Process Orchestration (PO) when a message being processed is too large and exceeds the maximum size limit for a single message. This can happen during the communication between different systems, especially when using web services or when integrating with external applications.
  Cause:
  
  Message Size Exceeds Limit: The primary cause of this error is that the message being sent or received exceeds the maximum allowable size for a single message in the SAP system.
  Configuration Settings: The configuration settings for message size limits in the SAP system or the middleware may not be set appropriately.
  Network Issues: Sometimes, network issues can lead to message fragmentation, which can trigger this error.
  
  Solution:
  
  
  Increase Message Size Limit:
  
  Check the configuration settings in the SAP system for the maximum message size. You may need to increase this limit to accommodate larger messages.
  In SAP PI/PO, you can adjust the message size limits in the Integration Directory or in the relevant communication channel settings.
  
  
  
  Message Splitting:
  
  If increasing the message size limit is not feasible, consider implementing message splitting in your integration logic. This involves breaking down large messages into smaller chunks that can be processed individually.
  
  
  
  Review Payload:
  
  Analyze the payload of the message to see if it can be optimized. Reducing the size of the message by removing unnecessary data or compressing the payload can help.
  
  
  
  Check Network Configuration:
  
  Ensure that there are no network-related issues that could be causing message fragmentation. This includes checking firewalls, proxies, and other network devices that might impose size limits.
  
  
  
  Monitor and Log:
  
  Enable logging and monitoring for the integration scenarios to capture detailed information about the messages being processed. This can help identify patterns or specific messages that are causing the issue.
  
  
  
  Related Information:
  
  SAP Notes: Check for relevant SAP Notes that may provide additional insights or patches related to this error.
  Documentation: Refer to the official SAP documentation for Process Integration/Orchestration for guidelines on message handling and configuration.
  Community Forums: Engage with the SAP Community or forums where other users may have encountered similar issues and can share their solutions.
  
  By addressing the message size limit and optimizing the message payload, you should be able to resolve the SRT_CORE274 error effectively.