How To Fix FIGL_MTI000 - You have restricted authorization for selected company codes

SAP Error Message - Details

• Message type: E = Error

• Message class: FIGL_MTI - Messages for Manage Tax Items

• Message number: 000

• Message text: You have restricted authorization for selected company codes

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 FIGL_MTI000 - You have restricted authorization for selected company codes ?

  The SAP error message FIGL_MTI000, which states "You have restricted authorization for selected company codes," typically occurs when a user attempts to perform an action in SAP that requires access to certain company codes for which they do not have the necessary authorizations. This can happen in various modules, particularly in Financial Accounting (FI) or Controlling (CO).
  Cause:
  
  Authorization Restrictions: The user’s role or profile does not include the necessary authorizations for the company codes involved in the transaction.
  Company Code Assignment: The user may be assigned to specific company codes, and the action they are trying to perform involves company codes outside of their assigned permissions.
  Role Configuration: The roles assigned to the user may not be configured correctly to include the required company codes.
  
  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 using transaction code SU01 (User Maintenance) or PFCG (Role Maintenance).
  
  
  
  Modify User Roles:
  
  If the user requires access to additional company codes, the roles assigned to them need to be modified. This can be done by an SAP security administrator.
  In transaction PFCG, find the relevant role and add the necessary authorizations for the required company codes.
  
  
  
  Authorization Object:
  
  Check the relevant authorization objects, such as F_BKPF_BES (Accounting Document: Authorization for Company Code) and F_BKPF_BUK (Company Code: Authorization for Company Code).
  Ensure that the user has the necessary values assigned to these authorization objects.
  
  
  
  Testing:
  
  After making changes to the user’s 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 error has been resolved.
  
  
  
  Related Information:
  
  SAP Notes: Check SAP Notes for any specific guidance or updates related to this error message. Sometimes, there may be known issues or patches that can help.
  Documentation: Review SAP documentation on authorization management to understand how to effectively manage user roles and permissions.
  Security Audit: Conduct a security audit to ensure that users have the appropriate access levels and that there are no unnecessary permissions granted.
  
  If the issue persists after following these steps, it may be necessary to consult with your SAP Basis or Security team for further investigation.