How To Fix REXCES003 - Company code is not found in Customizing

SAP Error Message - Details

• Message type: E = Error

• Message class: REXCES -

• Message number: 003

• Message text: Company code is not found in Customizing

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 REXCES003 - Company code is not found in Customizing ?

  The SAP error message REXCES003, which states "Company code is not found in Customizing," typically occurs when the system cannot find the specified company code in the configuration settings. This can happen for several reasons, and here are the potential causes, solutions, and related information:
  Causes:
  
  Company Code Not Created: The company code may not have been created in the system.
  Incorrect Configuration: The company code may not be properly configured in the relevant customizing settings.
  Authorization Issues: The user may not have the necessary authorizations to access the company code.
  Data Inconsistency: There may be inconsistencies in the data or configuration that prevent the system from recognizing the company code.
  Transport Issues: If the company code was recently transported from another system, there may have been issues during the transport process.
  
  Solutions:
  
  
  Check Company Code Creation:
  
  Go to the transaction code OBY6 (or SPRO -> Financial Accounting -> General Settings -> Define Company Code) and verify if the company code exists.
  If it does not exist, create the company code.
  
  
  
  Verify Customizing Settings:
  
  Ensure that the company code is properly configured in the relevant customizing settings. Check the settings for financial accounting and any other relevant modules.
  
  
  
  Check User Authorizations:
  
  Ensure that the user has the necessary authorizations to access the company code. This can be checked in transaction SU53 or by consulting with your security team.
  
  
  
  Data Consistency Check:
  
  Run consistency checks to ensure that there are no inconsistencies in the configuration. You can use transaction SE38 to run relevant reports or checks.
  
  
  
  Review Transport Logs:
  
  If the company code was recently transported, check the transport logs for any errors or issues that may have occurred during the transport process.
  
  
  
  Consult SAP Notes:
  
  Check the SAP Support Portal for any relevant SAP Notes that may address this specific error message or provide additional troubleshooting steps.
  
  
  
  Related Information:
  
  
  Transaction Codes: 
  
  OBY6: Define Company Code
  SPRO: Access the SAP Reference IMG
  SU53: Display Authorization Check
  SE38: Execute ABAP Programs
  
  
  
  SAP Documentation: Refer to the official SAP documentation for detailed information on configuring company codes and financial accounting settings.
  
  
  SAP Community: Engage with the SAP Community forums for insights from other users who may have encountered similar issues.
  
  
  By following these steps, you should be able to identify the cause of the REXCES003 error and implement the appropriate solution.