How To Fix /SAPCND/CUSTOMIZING026 - Initial access ID is not permitted

SAP Error Message - Details

• Message type: E = Error

• Message class: /SAPCND/CUSTOMIZING -

• Message number: 026

• Message text: Initial access ID is not permitted

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 /SAPCND/CUSTOMIZING026 - Initial access ID is not permitted ?

  The SAP error message /SAPCND/CUSTOMIZING026 Initial access ID is not permitted typically occurs in the context of SAP Converged Data Management (CDM) or when dealing with customizing settings in SAP systems. This error indicates that the initial access ID being used does not have the necessary permissions to perform the requested action.
  Cause:
  
  Authorization Issues: The user or access ID does not have the required authorizations to access the specific customizing settings or data.
  Incorrect Configuration: The access ID may not be correctly configured in the system, leading to permission issues.
  Role Assignment: The user may not have the appropriate roles assigned that include the necessary authorizations for the action being attempted.
  
  Solution:
  
  
  Check User Authorizations:
  
  Use transaction code SU53 immediately after the error occurs to check the authorization check failure. This will provide insights into which specific authorization is missing.
  Review the user’s roles and authorizations in transaction SU01 or PFCG to ensure that the necessary permissions are granted.
  
  
  
  Adjust Role Assignments:
  
  If the user lacks the required roles, assign the appropriate roles that include access to the customizing settings.
  Ensure that the roles are properly configured to include the necessary authorizations for the actions being performed.
  
  
  
  Consult with Basis Team:
  
  If you are unable to resolve the issue, consult with your SAP Basis team or security administrator. They can help review the authorization profiles and make necessary adjustments.
  
  
  
  Review Customizing Settings:
  
  Check if there are any specific customizing settings that restrict access to certain users or roles. This may involve reviewing the configuration in transaction SPRO.
  
  
  
  Testing:
  
  After making changes to roles or authorizations, test the access again to ensure that the issue is resolved.
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  SU01: User Maintenance
  PFCG: Role Maintenance
  SU53: Display Authorization Check
  SPRO: SAP Reference IMG (Implementation Guide)
  
  
  
  Documentation: Refer to SAP Help Portal or SAP Notes for specific guidance on authorization management and troubleshooting authorization issues.
  
  
  SAP Notes: Search for relevant SAP Notes that may address this specific error message or provide additional context.
  
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.