How To Fix FA108 - Company code without authorization excluded from selection

SAP Error Message - Details

• Message type: E = Error

• Message class: FA - Payment Advice Administration

• Message number: 108

• Message text: Company code without authorization excluded from selection

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 FA108 - Company code without authorization excluded from selection ?

  The SAP error message FA108 ("Company code without authorization excluded from selection") typically occurs when a user attempts to access or process data related to a company code for which they do not have the necessary authorizations. This is a common issue in SAP systems where user roles and authorizations are strictly managed to ensure data security and compliance.
  Cause:
  
  Lack of Authorization: The user does not have the required authorization to access the specified company code. This could be due to missing roles or authorizations in the user's profile.
  Incorrect User Role Assignment: The user may not be assigned to the correct roles that include access to the relevant company codes.
  Company Code Configuration: The company code may not be properly configured in the user's authorization profile.
  
  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 code SU01 to view the user's profile and check the assigned roles.
  
  
  
  Modify User Roles:
  
  If the user lacks the necessary authorizations, a system administrator or security officer should review and modify the user's roles to include the required authorizations for the company code in question.
  This may involve adding the user to a role that has access to the relevant company code or creating a custom role that includes the necessary authorizations.
  
  
  
  Authorization Object:
  
  Ensure that the relevant authorization objects (e.g., F_BKPF_BWA, F_BKPF_BWA, etc.) are included in the user's roles. These objects control access to financial documents and company codes.
  
  
  
  Testing:
  
  After making changes to the user’s roles or authorizations, have the user log out and log back in to test if the issue is resolved.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or your organization’s internal guidelines for managing user authorizations to ensure compliance with security policies.
  
  
  
  Related Information:
  
  Transaction Codes:
  
  SU01: User Maintenance
  SU53: Display Authorization Check
  PFCG: Role Maintenance
  
  
  Authorization Objects: Familiarize yourself with the relevant authorization objects that control access to company codes and financial transactions.
  Security Policies: Review your organization’s security policies regarding user access and authorization management to ensure compliance and proper access control.
  
  If the issue persists after following these steps, it may be necessary to consult with your SAP Basis or security team for further investigation.