Do you have any question about this error?
Message type: E = Error
Message class: GLE_MCA - Multicurrency Accounting
Message number: 400
Message text: Authorization check failed for company code &1, posting date &2
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.
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.
GLE_MCA400
- Authorization check failed for company code &1, posting date &2 ?The SAP error message GLE_MCA400 indicates that there is an authorization check failure for a specific company code and posting date. This error typically occurs when a user attempts to perform a financial transaction (like posting a journal entry) but lacks the necessary authorizations for the specified company code or the date of the transaction.
Cause:
- Missing Authorizations: The user does not have the required authorization for the company code specified in the transaction.
- Authorization Object: The relevant authorization object (e.g.,
F_BKPF_BLA
,F_BKPF_BER
, etc.) may not be assigned to the user's role.- Company Code Restrictions: The user may be restricted from posting to certain company codes based on their role or profile.
- Posting Date Restrictions: There may be restrictions on posting to certain periods or dates, which could be defined in the configuration.
Solution:
- Check User Roles: Verify the roles assigned to the user in transaction
SU01
(User Maintenance). Ensure that the user has the necessary roles that include authorizations for the relevant company code.- Review Authorization Objects: Use transaction
SU53
immediately after the error occurs to check which authorization object failed. This will provide insight into what specific authorization is missing.- Adjust Authorizations: If the user lacks the necessary authorizations, work with your SAP security team to adjust the roles or create a new role that includes the required authorizations for the company code and posting date.
- Posting Period Configuration: Check the configuration for posting periods in transaction
OB52
to ensure that the posting date is open for posting. If the period is closed, you may need to open it or adjust the posting date.- Consult Documentation: Review SAP documentation or consult with your SAP Basis or Security team for any specific configurations that may affect authorizations.
Related Information:
SU01
: User MaintenanceSU53
: Display Authorization CheckPFCG
: Role MaintenanceOB52
: Change View "Posting Periods": OverviewF_BKPF_BLA
(Authorization for Document Type) and F_BKPF_BER
(Authorization for Company Code).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.
Get instant SAP help. Start your 7-day free trial now.
GLE_MCA399
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...
GLE_MCA398
Authorization check failed for company code: &1
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
GLE_MCA401
Ledger &1 is not assigned to a ledger group
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
GLE_MCA402
Ledger &1 is not assigned to a ledger group which also includes ledger &2
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.