/ACCGO/IC_MSG071 - Header data not found

SAP Error Message - Details

• Message type: E = Error

• Message class: /ACCGO/IC_MSG -

• Message number: 071

• Message text: Header data not found

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.

AnswerBot

• What is the cause and solution for SAP error message /ACCGO/IC_MSG071 - Header data not found ?

  The SAP error message /ACCGO/IC_MSG071 Header data not found typically occurs in the context of the SAP General Ledger (G/L) accounting module, particularly when dealing with intercompany transactions or postings. This error indicates that the system is unable to find the necessary header data for the transaction you are trying to process.
  Causes:
  
  Missing or Incomplete Data: The header data for the document you are trying to post may be missing or incomplete. This could be due to incorrect or missing entries in the relevant fields.
  Document Not Created: The document you are trying to reference may not have been created or saved properly in the system.
  Authorization Issues: The user may not have the necessary authorizations to access the header data for the transaction.
  Configuration Issues: There may be configuration issues in the intercompany settings or in the G/L account settings that prevent the system from retrieving the header data.
  Data Consistency Issues: There may be inconsistencies in the data, such as missing links between the header and line item data.
  
  Solutions:
  
  Check Document Existence: Verify that the document you are trying to post or reference actually exists in the system. You can do this by checking the relevant transaction codes (e.g., FB03 for displaying documents).
  Review Input Data: Ensure that all required fields in the header data are filled out correctly. Check for any mandatory fields that may have been overlooked.
  Authorization Check: Confirm that the user has the necessary authorizations to access and post the document. You may need to consult with your SAP security team.
  Configuration Review: Review the configuration settings for intercompany transactions and G/L accounts to ensure they are set up correctly. This may involve checking the settings in transaction codes like OX15 (for company codes) or OX19 (for intercompany settings).
  Data Consistency Check: Run consistency checks to identify any discrepancies in the data. This may involve using transaction codes like SE16 or SE11 to check the relevant database tables.
  Consult SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error message. There may be patches or updates that resolve known issues.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as FB03 (Display Document), FB02 (Change Document), and FBL1N (Vendor Line Item Display) to troubleshoot the issue.
  SAP Community: Engage with the SAP Community forums to see if other users have encountered similar issues and what solutions they found effective.
  Documentation: Review SAP documentation related to intercompany processes and G/L accounting for best practices and troubleshooting tips.
  
  If the issue persists after trying the above solutions, it may be necessary to involve your SAP support team or consult with an SAP expert for further assistance.