How To Fix MDG_BS_CUST_BOLUI018 - Could not retrieve current company code

SAP Error Message - Details

• Message type: E = Error

• Message class: MDG_BS_CUST_BOLUI - MDG: messages for Cusomer UI related issues

• Message number: 018

• Message text: Could not retrieve current company code

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 MDG_BS_CUST_BOLUI018 - Could not retrieve current company code ?

  The SAP error message MDG_BS_CUST_BOLUI018: Could not retrieve current company code typically occurs in the context of SAP Master Data Governance (MDG) when the system is unable to determine or access the current company code for a specific operation or transaction. This can happen for various reasons, and here are some potential causes, solutions, and related information:
  Causes:
  
  Missing Configuration: The company code may not be properly configured in the system.
  Authorization Issues: The user may not have the necessary authorizations to access the company code.
  Data Inconsistencies: There may be inconsistencies in the master data that prevent the system from identifying the company code.
  Technical Issues: There could be underlying technical issues, such as problems with the database or application server.
  Session Context: The session context may not be set correctly, leading to the inability to retrieve the company code.
  
  Solutions:
  
  
  Check Configuration:
  
  Ensure that the company code is correctly defined in the system. You can check this in the SPRO configuration settings under Financial Accounting (FI) > General Ledger Accounting > Master Data > G/L Accounts > Prepare G/L Account Creation.
  
  
  
  Verify Authorizations:
  
  Check the user roles and authorizations to ensure that the user has the necessary permissions to access the company code. This can be done through transaction SU53 or by consulting with your security team.
  
  
  
  Review Master Data:
  
  Look for any inconsistencies in the master data that might affect the company code. Ensure that all relevant data is complete and correctly maintained.
  
  
  
  Check Technical Logs:
  
  Review the system logs (transaction SLG1) for any additional error messages or warnings that might provide more context about the issue.
  
  
  
  Session Management:
  
  If the issue is related to session context, try logging out and logging back into the system. Alternatively, you can clear the session cache.
  
  
  
  Consult SAP Notes:
  
  Check the SAP Support Portal for any relevant SAP Notes that might address this specific error message. There may be patches or updates available that resolve the issue.
  
  
  
  Contact SAP Support:
  
  If the issue persists after trying the above solutions, consider reaching out to SAP Support for further assistance. Provide them with detailed information about the error and the steps you have already taken.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SE11 (Data Dictionary), SE80 (Object Navigator), and SLG1 (Application Log) for troubleshooting.
  Documentation: Review the official SAP documentation for MDG to understand the context in which this error might occur and any specific prerequisites for the operations you are trying to perform.
  Community Forums: Engage with SAP community forums or user groups where similar issues may have been discussed, and solutions shared.
  
  By following these steps, you should be able to diagnose and resolve the error message MDG_BS_CUST_BOLUI018 effectively.