How To Fix GJ572 - No Record for Company High in &

SAP Error Message - Details

• Message type: E = Error

• Message class: GJ - Joint Venture Accounting

• Message number: 572

• Message text: No Record for Company High in &

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 GJ572 - No Record for Company High in & ?

  The SAP error message GJ572 ("No Record for Company High in &") typically occurs in the context of the SAP Real Estate Management (RE) module or when dealing with company codes and related financial transactions. This error indicates that the system could not find a record for the specified company code in the relevant database table.
  Causes:
  
  Missing Data: The company code or related data may not be set up correctly in the system. This could be due to missing entries in the relevant configuration tables.
  Incorrect Company Code: The company code specified in the transaction may be incorrect or does not exist in the system.
  Data Inconsistency: There may be inconsistencies in the data, such as missing master data for the company code.
  Authorization Issues: The user may not have the necessary authorizations to access the data for the specified company code.
  
  Solutions:
  
  
  Check Company Code Configuration:
  
  Verify that the company code exists in the system. You can do this by navigating to the relevant configuration settings in SAP (Transaction Code: OX02).
  Ensure that all necessary data for the company code is correctly maintained.
  
  
  
  Review Transaction Data:
  
  Check the transaction you are trying to execute and ensure that the company code is entered correctly.
  If applicable, verify that the relevant master data (e.g., business partner, property) is correctly set up for the company code.
  
  
  
  Data Consistency Check:
  
  Run consistency checks to identify any missing or inconsistent data related to the company code. This can often be done through specific reports or transaction codes in SAP.
  
  
  
  Authorization Check:
  
  Ensure that the user executing the transaction has the necessary authorizations to access the data for the specified company code. This may involve checking user roles and authorizations in the system.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or help resources for additional context on the error message and potential troubleshooting steps.
  
  
  
  Contact Support:
  
  If the issue persists after checking the above points, consider reaching out to your SAP support team or consulting SAP Notes for any known issues related to this error.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as OX02 (for company code configuration) and other related transactions in the RE module.
  SAP Notes: Search for SAP Notes related to error GJ572 for any specific patches or updates that may address the issue.
  User Forums: Engage with SAP community forums or user groups where similar issues may have been discussed.
  
  By following these steps, you should be able to identify the cause of the GJ572 error and implement a solution to resolve it.