How To Fix /CPD/CL_MSG371 - You are not authorized to change details of contact persons

SAP Error Message - Details

• Message type: E = Error

• Message class: /CPD/CL_MSG -

• Message number: 371

• Message text: You are not authorized to change details of contact persons

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 /CPD/CL_MSG371 - You are not authorized to change details of contact persons ?

  The SAP error message /CPD/CL_MSG371 indicates that a user is not authorized to change the details of contact persons in the system. This typically occurs in the context of customer or vendor master data management, where specific authorizations are required to modify contact information.
  Cause:
  
  Authorization Issues: The user does not have the necessary authorization roles or permissions assigned to modify contact person details.
  Role Configuration: The roles assigned to the user may not include the necessary transaction codes or object authorizations related to contact person management.
  Object-Specific Restrictions: There may be specific restrictions set up in the authorization objects that prevent changes to contact persons.
  
  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 SU01 to check the user's roles and authorizations.
  
  
  
  Review Role Assignments:
  
  Ensure that the user has the appropriate roles assigned that include permissions for changing contact person details. This may involve roles related to customer or vendor master data management.
  If necessary, consult with your SAP security team to review and adjust the roles.
  
  
  
  Adjust Authorization Objects:
  
  If you have access, review the relevant authorization objects (e.g., F_BKPF_BSA, F_LFA1_BSA, etc.) to ensure that the user has the necessary permissions to change contact person details.
  Make sure that the authorization profiles include the necessary activities (like create, change, display) for the relevant business objects.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or your organization's internal guidelines for managing user roles and authorizations to ensure compliance with security policies.
  
  
  
  Testing:
  
  After making changes to roles or authorizations, test the changes by attempting to modify the contact person details again.
  
  
  
  Related Information:
  
  Transaction Codes: 
  
  SU01 - User Maintenance
  PFCG - Role Maintenance
  SU53 - Display Authorization Check
  
  
  Authorization Objects: 
  
  Familiarize yourself with the relevant authorization objects that control access to customer/vendor master data and contact person management.
  
  
  SAP Notes: 
  
  Check for any relevant SAP Notes that may address specific issues or provide additional guidance on authorization management.
  
  
  
  If the issue persists after checking and adjusting authorizations, it may be necessary to involve your SAP Basis or security team for further investigation.