How To Fix CM_EHHSS_RAS_COMMON026 - You are not authorized to collect amounts

SAP Error Message - Details

• Message type: E = Error

• Message class: CM_EHHSS_RAS_COMMON - Common Messages for Risk Assessment

• Message number: 026

• Message text: You are not authorized to collect amounts

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 CM_EHHSS_RAS_COMMON026 - You are not authorized to collect amounts ?

  The SAP error message CM_EHHSS_RAS_COMMON026 indicates that a user does not have the necessary authorization to collect amounts in the system. This error typically arises in the context of financial transactions, such as billing or payment processing, where specific permissions are required to perform certain actions.
  Cause:
  
  Authorization Issues: The user attempting to perform the action does not have the required authorization roles or permissions assigned in the SAP system.
  Role Configuration: The roles assigned to the user may not include the necessary transaction codes or authorization objects related to collecting amounts.
  User Profile: The user profile may not be set up correctly, or the user may be in a different organizational unit that does not have the required permissions.
  
  Solution:
  
  
  Check User Authorizations:
  
  Use transaction code SU53 immediately after encountering the error to check the authorization check that failed. This will provide insights into which specific authorization object is missing.
  Review the user’s roles and authorizations in transaction code SU01 (User Maintenance) or PFCG (Role Maintenance).
  
  
  
  Modify Roles:
  
  If the required authorization is missing, you may need to modify the user’s roles or create a new role that includes the necessary permissions.
  Ensure that the role includes the relevant authorization objects for collecting amounts, such as financial transaction codes.
  
  
  
  Consult with Security Team:
  
  If you do not have the necessary permissions to change roles or authorizations, contact your SAP security or basis team to request the required access.
  
  
  
  Testing:
  
  After changes are made, have the user log out and log back in to ensure that the new authorizations take effect.
  Test the transaction again to confirm that the error has been resolved.
  
  
  
  Related Information:
  
  Authorization Objects: Familiarize yourself with the relevant authorization objects that control access to financial transactions. Common objects include F_BKPF_BSA (Accounting Document) and F_BKPF_BSA (Document Type).
  SAP Notes: Check SAP Notes for any known issues or updates related to this error message. Sometimes, specific patches or updates may address authorization issues.
  Documentation: Review SAP documentation or training materials related to user roles and authorizations to better understand how to manage access in your organization.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve the authorization issue.