How To Fix W5035 - No header texts available for purchase order &

SAP Error Message - Details

• Message type: E = Error

• Message class: W5 - Messages for MM-WEB Applications and BAPIs

• Message number: 035

• Message text: No header texts available for purchase order &

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 W5035 - No header texts available for purchase order & ?

  SAP Error Message:
  
  W5035 No header texts available for purchase order &
  
  Cause:
  This warning message appears when you try to display or process a Purchase Order (PO) in SAP, and the system cannot find any header texts associated with that PO. Header texts in a PO are typically used to provide additional information or instructions relevant to the entire order.
  The message indicates that the PO header does not contain any text entries in the header text fields (e.g., in the PO header text tab or long text).
  
  Explanation:
  
  Purchase Orders in SAP can have texts at different levels: header, item, and item schedule line.
  Header texts are stored in text objects linked to the PO header.
  If a transaction or report tries to display or print the PO header text but none exists, SAP issues this warning.
  This is a warning (W), not an error, so processing can continue, but the text will simply be missing.
  
  
  Common Scenarios When This Occurs:
  
  Viewing or printing a PO that was created without any header text.
  Running reports or forms that expect header text but none was maintained.
  Custom developments or enhancements that try to read header text but find none.
  
  
  Solution:
  
  
  Check and Maintain Header Text:
  
  Go to the PO display/change transaction (ME22N or ME23N).
  Navigate to the Header section.
  Open the Texts tab.
  Check if any header text exists.
  If needed, add the appropriate header text and save.
  
  
  
  Ignore if Not Required:
  
  Since this is a warning, if header text is not mandatory for your business process, you can ignore this message.
  
  
  
  Adjust Custom Code or Forms:
  
  If custom programs or print forms expect header text, modify them to handle the absence of header text gracefully.
  Add checks to avoid this warning or suppress it if appropriate.
  
  
  
  Check Text Object Configuration:
  
  Header texts for POs are stored under text object EKKO (Purchase Order Header).
  Ensure that the text object and text ID used are correctly configured and assigned.
  
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  ME21N – Create Purchase Order
  ME22N – Change Purchase Order
  ME23N – Display Purchase Order
  ME9F – Message Output for Purchase Orders (printing)
  
  
  
  Tables:
  
  EKKO – Purchase Order Header Data
  STXH and STXL – SAPscript texts storage tables
  
  
  
  SAP Notes:
  
  Check SAP Notes related to PO text handling if you encounter issues with text storage or retrieval.
  
  
  
  Text Maintenance:
  
  Use transaction SO10 for standard text maintenance (not directly related but useful for text management).
  
  
  
  
  Summary:
  
  Cause: No header text maintained for the PO.
  Effect: Warning message W5035 displayed when header text is requested.
  Solution: Add header text to the PO if required or ignore the warning if header text is not mandatory.
  
  
  If you need further assistance, please provide the transaction or process where this warning occurs, and any custom developments involved.