How To Fix PRF_CNTRL_MSG058 - Header data doesn't have values

SAP Error Message - Details

• Message type: E = Error

• Message class: PRF_CNTRL_MSG - Message Class for control messages of PRF

• Message number: 058

• Message text: Header data doesn't have values

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 PRF_CNTRL_MSG058 - Header data doesn't have values ?

  The SAP error message PRF_CNTRL_MSG058, which states "Header data doesn't have values," typically occurs in the context of creating or processing documents in SAP, such as purchase requisitions, purchase orders, or other transactional documents. This error indicates that the system expects certain header fields to be populated with values, but they are missing.
  Causes:
  
  Missing Mandatory Fields: The header of the document may have mandatory fields that are not filled in. This could include fields like document type, vendor, purchasing organization, or other critical information.
  Configuration Issues: There may be configuration settings in the SAP system that require certain fields to be filled in, and these settings may not be aligned with the data being entered.
  User Input Errors: Users may inadvertently skip filling in required fields or may not be aware of the necessary information needed for the document.
  Data Transfer Issues: If data is being transferred from another system or through an interface, there may be issues with the data mapping or transfer process that result in missing header values.
  
  Solutions:
  
  Check Mandatory Fields: Review the document you are trying to create or process and ensure that all mandatory header fields are filled in. You can usually find a list of required fields in the SAP documentation or by checking the field properties in the transaction.
  Review Configuration Settings: If you have access to the configuration settings, check the relevant settings for the document type you are working with. Ensure that the required fields are correctly configured.
  User Training: Provide training to users on the importance of filling in all required fields and how to properly create documents in SAP.
  Debugging and Logs: If the issue persists, consider using transaction codes like SLG1 (Application Log) to check for any logs related to the error. This can provide more context on what might be going wrong.
  Consult SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that might address this specific error message or provide additional troubleshooting steps.
  
  Related Information:
  
  Transaction Codes: Depending on the context, you may be using transaction codes like ME51N (Create Purchase Requisition), ME21N (Create Purchase Order), etc.
  SAP Documentation: Refer to SAP Help documentation for specific modules (e.g., MM for Materials Management) for detailed information on document creation and required fields.
  SAP Community: Engage with the SAP Community forums for insights from other users who may have encountered similar issues.
  
  If the problem continues after trying the above solutions, it may be necessary to involve your SAP support team or a consultant for further investigation.