How To Fix SAPBC_GLOBAL813 - Company code display only with authorization

SAP Error Message - Details

• Message type: E = Error

• Message class: SAPBC_GLOBAL - Messages for Package SAPBC_GLOBAL

• Message number: 813

• Message text: Company code display only with authorization

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 SAPBC_GLOBAL813 - Company code display only with authorization ?

  The SAP error message "SAPBC_GLOBAL813: Company code display only with authorization" typically indicates that a user is trying to access or display information related to a company code in SAP without having the necessary authorization. This is a common issue in SAP systems where access control is enforced to protect sensitive financial and organizational data.
  Cause:
  
  Lack of Authorization: The user does not have the required authorization to view or modify the company code data. This could be due to missing roles or authorizations in their user profile.
  Authorization Object: The specific authorization object related to company codes (e.g., F_BKPF_BES, F_BKPF_BUK, etc.) may not be assigned to the user.
  Role Configuration: The roles assigned to the user may not include the necessary permissions for the company code in question.
  
  Solution:
  
  
  Check User Authorizations:
  
  Use transaction code SU53 immediately after encountering the error to see which authorization check failed. This will provide insight into what specific authorization is missing.
  Alternatively, you can use transaction SU01 to view the user’s profile and check the assigned roles.
  
  
  
  Review Role Assignments:
  
  If you have the necessary permissions, review the roles assigned to the user in transaction PFCG. Ensure that the roles include the necessary authorizations for the company code.
  If the roles do not include the required authorizations, you may need to modify the role or create a new one that includes the necessary permissions.
  
  
  
  Consult with Security Team:
  
  If you do not have the necessary access to modify roles or authorizations, contact your SAP security team or administrator. Provide them with the details of the error and the company code you are trying to access.
  
  
  
  Testing:
  
  After adjustments are made, have the user log out and log back in to ensure that the new authorizations take effect. Test the access again to confirm that the issue is resolved.
  
  
  
  Related Information:
  
  
  Authorization Objects: Familiarize yourself with the relevant authorization objects that control access to company codes. Common objects include:
  
  F_BKPF_BES: Authorization for company code in financial accounting.
  F_BKPF_BUK: Authorization for company code in controlling.
  
  
  
  Transaction Codes:
  
  SU53: Display authorization check.
  SU01: User maintenance.
  PFCG: Role maintenance.
  
  
  
  Documentation: Refer to SAP documentation or your organization’s internal guidelines for managing user roles and authorizations.
  
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve the authorization issue.