How To Fix /SAPPO/ACR035 - &1: Messages exist but the header MORE_MSG is initial

SAP Error Message - Details

• Message type: E = Error

• Message class: /SAPPO/ACR -

• Message number: 035

• Message text: &1: Messages exist but the header MORE_MSG is initial

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 /SAPPO/ACR035 - &1: Messages exist but the header MORE_MSG is initial ?

  The SAP error message /SAPPO/ACR035 &1: Messages exist but the header MORE_MSG is initial typically indicates an issue with the handling of messages in the SAP system, particularly in the context of the SAP Purchase Order (PO) or related processes. This error suggests that there are messages that should be displayed, but the system is unable to retrieve or display them properly because the header information (MORE_MSG) is not initialized.
  Cause:
  
  Message Handling Issue: The system is trying to process messages related to a purchase order or another document, but the header that is supposed to contain the message information is not set up correctly.
  Data Inconsistency: There may be inconsistencies in the data or configuration that prevent the system from correctly linking the messages to the header.
  Custom Code or Enhancements: If there are custom developments or enhancements in the system, they might not be handling message processing correctly.
  System Bugs: There could be bugs in the SAP version you are using that affect message processing.
  
  Solution:
  
  Check Message Configuration: Ensure that the message types and their configurations are correctly set up in the system. This includes checking the message classes and ensuring that they are properly defined.
  Debugging: If you have access to the ABAP debugger, you can trace the execution to see where the MORE_MSG header is supposed to be initialized and why it is not.
  Review Custom Code: If there are any custom enhancements or modifications related to message handling, review them to ensure they are functioning as intended.
  SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that might address this specific error. There may be patches or updates available that resolve the issue.
  System Logs: Review system logs (transaction SLG1) for any additional error messages or warnings that could provide more context about the issue.
  Contact SAP Support: If the issue persists and you cannot find a resolution, consider reaching out to SAP Support for assistance.
  
  Related Information:
  
  Transaction Codes: You may want to use transaction codes like ME23N (Display Purchase Order) or ME22N (Change Purchase Order) to see if the issue is reproducible in the user interface.
  Message Types: Familiarize yourself with the message types used in your SAP system, as they can vary based on configuration and business processes.
  Documentation: Review SAP documentation related to message handling and error messages for further insights.
  
  By following these steps, you should be able to diagnose and potentially resolve the error message you are encountering.