How To Fix 64839 - No authorization to change all price types

SAP Error Message - Details

• Message type: E = Error

• Message class: 64 - Treasury Management: Securities

• Message number: 839

• Message text: No authorization to change all price types

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 64839 - No authorization to change all price types ?

  The SAP error message 64839, which states "No authorization to change all price types," typically occurs when a user attempts to modify pricing information in a transaction or master data but lacks the necessary authorizations to perform that action. This error is often related to the authorization objects that control access to pricing data in SAP.
  Cause:
  
  Authorization Issues: The user does not have the required authorizations to change specific price types in the system. This can be due to missing roles or authorizations assigned to the user profile.
  Configuration Settings: The system may be configured to restrict changes to certain price types based on user roles or organizational policies.
  Transaction Restrictions: Certain transactions may have built-in restrictions that prevent users from changing all price types unless they have specific authorizations.
  
  Solution:
  
  
  Check User Authorizations:
  
  Use transaction code SU53 immediately after encountering the error to check which authorization check failed. This will provide insight into what specific authorization is missing.
  Review the user’s roles and authorizations in transaction SU01 or PFCG to ensure that the necessary authorizations for changing price types are included.
  
  
  
  Modify User Roles:
  
  If the user lacks the necessary authorizations, work with your SAP security team to modify the user’s roles or create a new role that includes the required authorizations for changing price types.
  Ensure that the authorization object K_NA (Customer Master) or K_NA_E (Customer Master - Sales Area) is included in the user’s profile, as these often control access to pricing data.
  
  
  
  Consult with SAP Security Team:
  
  If you are not authorized to make changes to user roles, contact your SAP security team or administrator to request the necessary changes.
  
  
  
  Testing:
  
  After adjustments are made, have the user log out and back into the system, then attempt the transaction again to see if the issue is resolved.
  
  
  
  Related Information:
  
  
  Authorization Objects: Familiarize yourself with the relevant authorization objects that control pricing changes, such as:
  
  K_NA: Customer Master Data
  K_NA_E: Customer Master Data - Sales Area
  KONP: Conditions (Pricing)
  
  
  
  Documentation: Review SAP documentation or internal guidelines regarding authorization management and pricing data changes to ensure compliance with organizational policies.
  
  
  Transaction Codes:
  
  SU53: Display Authorization Check
  SU01: User Maintenance
  PFCG: Role Maintenance
  
  
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.