How To Fix SRT_LOGGING036 - Sequence status manually changed from & to & by forwarded error handling

SAP Error Message - Details

• Message type: E = Error

• Message class: SRT_LOGGING -

• Message number: 036

• Message text: Sequence status manually changed from & to & by forwarded error handling

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message SRT_LOGGING036 - Sequence status manually changed from & to & by forwarded error handling ?

  The SAP error message SRT_LOGGING036 indicates that the sequence status of a message was manually changed from one state to another due to forwarded error handling. This typically occurs in the context of SAP's integration technologies, such as SAP Process Integration (PI) or SAP Process Orchestration (PO), where messages are processed and their statuses are tracked.
  Cause:
  The error message is triggered when:
  
  An error occurs during the processing of a message in the integration framework.
  The error handling mechanism is set to manually change the status of the message sequence.
  The status change is logged, indicating that the sequence has been altered from its original state (e.g., from "In Process" to "Error" or "Completed").
  
  Solution:
  To resolve this issue, you can take the following steps:
  
  
  Check the Error Handling Configuration:
  
  Review the error handling settings in your SAP PI/PO system. Ensure that the configuration aligns with your business requirements and that the manual status change is appropriate.
  
  
  
  Analyze the Logs:
  
  Use transaction codes like SXMB_MONI (for monitoring messages) or SRT_MONI (for monitoring web service messages) to check the logs for the specific message that triggered the error.
  Look for any underlying issues that caused the error, such as connectivity problems, data format issues, or system errors.
  
  
  
  Review the Message Sequence:
  
  Investigate the sequence of messages leading up to the error. Determine if there were any previous errors that may have contributed to the current status change.
  
  
  
  Manual Intervention:
  
  If necessary, manually change the status of the message sequence back to the desired state using the appropriate transaction or monitoring tool.
  Ensure that any manual changes are documented and communicated to relevant stakeholders.
  
  
  
  Testing:
  
  After addressing the underlying issues, test the integration scenario to ensure that messages are processed correctly without triggering the error again.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or support notes related to error handling in SAP PI/PO for more detailed guidance and best practices.
  
  
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that may provide additional insights or patches related to this error message.
  Integration Monitoring: Familiarize yourself with the tools available for monitoring and troubleshooting integration scenarios in SAP, such as the Integration Monitoring dashboard.
  Error Handling Strategies: Consider implementing robust error handling strategies, including automatic retries, alerts, and notifications, to minimize manual interventions in the future.
  
  By following these steps, you should be able to identify the root cause of the error and implement a solution to prevent it from recurring.