How To Fix MC786 - No change authorization for shared basis table &1

SAP Error Message - Details

• Message type: E = Error

• Message class: MC - Aggregate: views, matchcodes, lock objects

• Message number: 786

• Message text: No change authorization for shared basis table &1

What causes this issue?

This maintenance view is based on shared basis tables. This means that
any changes made to the maintenance view can also trigger changes in the
shared container and hence can have wide ranging consequences in target
systems. This means that experts should be consulted and special
authorizations granted before a change of this type is made.

System Response

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

How to fix this error?

Contact the DDIC expert in your organization. The authorization in
question is the authorization object S_DD_MTSH with table <(>&<)>1 and
activity 02 (Change).

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message MC786 - No change authorization for shared basis table &1 ?

  The SAP error message MC786 "No change authorization for shared basis table &1" typically occurs when a user attempts to make changes to a shared basis table in the SAP system without having the necessary authorization. This error is common in the context of SAP's Material Management (MM) and Production Planning (PP) modules, where shared basis tables are used to store critical data.
  
  Cause:
  
  Authorization Issues: The user does not have the required authorization to modify the specified shared basis table. This could be due to missing roles or permissions in the user's profile.
  Table Locking: The table might be locked by another user or process, preventing changes.
  Configuration Settings: The system may be configured to restrict changes to certain tables for specific user roles.
  
  
  Solution:
  
  
  Check User Authorizations:
  
  Use transaction code SU53 immediately after the error occurs to check for missing authorizations.
  Review the user's roles and profiles in transaction PFCG to ensure they have the necessary