How To Fix GLE_MCA399 - Authorization check failed for company code &1, fiscal yr: &2, period: &3

SAP Error Message - Details

• Message type: E = Error

• Message class: GLE_MCA - Multicurrency Accounting

• Message number: 399

• Message text: Authorization check failed for company code &1, fiscal yr: &2, period: &3

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 GLE_MCA399 - Authorization check failed for company code &1, fiscal yr: &2, period: &3 ?

  The SAP error message GLE_MCA399 indicates that there is an authorization check failure for a specific company code, fiscal year, and period. This error typically occurs when a user attempts to perform a transaction or access data for which they do not have the necessary authorizations.
  Cause:
  
  Missing Authorizations: The user does not have the required authorization to access the specified company code, fiscal year, or period.
  Authorization Object: The relevant authorization object (e.g., F_BKPF_BES, F_BKPF_BUK, etc.) may not be assigned to the user's role.
  Role Assignment: The user may not be assigned to the correct role that includes the necessary authorizations for the financial transactions they are trying to perform.
  Company Code or Period Restrictions: There may be restrictions in place that limit access to certain company codes or periods based on the user's profile.
  
  Solution:
  
  
  Check User Authorizations:
  
  Use transaction code SU53 immediately after the error occurs to see which authorization check failed. This will provide insight into what specific authorization is missing.
  Review the user's roles and authorizations in transaction code SU01 or PFCG.
  
  
  
  Modify Roles:
  
  If the user lacks the necessary authorizations, you may need to modify their roles in transaction PFCG to include the required authorization objects.
  Ensure that the authorization objects related to financial transactions for the specific company code and fiscal year are included.
  
  
  
  Consult with Security Team:
  
  If you do not have the necessary permissions to change roles or authorizations, contact your SAP security team or administrator to request the necessary changes.
  
  
  
  Testing:
  
  After making changes to the roles or authorizations, have the user log out and log back in to ensure that the changes take effect.
  Test the transaction again to confirm that the issue has been resolved.
  
  
  
  Related Information:
  
  Authorization Objects: Familiarize yourself with the relevant authorization objects for financial transactions, such as F_BKPF_BES (Authorization for Document Type) and F_BKPF_BUK (Authorization for Company Code).
  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 authorization failure and implement the necessary changes to resolve the issue.