How To Fix MC787 - No authorization to configure restriction on shared tables

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 787

• Message text: No authorization to configure restriction on shared tables

What causes this issue?

Any structure changes made to shared tables and any changes made to
maintenance views that are based on shared tables can generate shared
containers in multitenancy systems. This generation can take a very long
time.
In the case of emergency corrections in particular, it is important that
the import time is kept as short as possible. This means that the
changes mentioned above are not allowed in emergency correction systems.
An authorization is required to configure system-wide restrictions on
these changes.

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?

If you are unsure about the consequences of this configuration, contact
the DDIC expert in your organization. The authorization in question is
the authorization object S_DD_MTSH with table * 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 MC787 - No authorization to configure restriction on shared tables ?

  The SAP error message MC787 indicates that a user does not have the necessary authorization to configure restrictions on shared tables. This typically occurs in the context of SAP's Material Management (MM) or Logistics modules, where shared tables are used for various data management tasks.
  Cause:
  The error is caused by a lack of appropriate authorizations in the user's role. Specifically, the user may not have the necessary permissions to access or modify the configuration settings related to shared tables in the SAP system.
  Solution:
  To resolve this issue, you can follow these steps:
  
  
  Check User Roles and Authorizations:
  
  Verify the roles assigned to the user encountering the error. You can do this by using transaction code SU01 (User Maintenance) to check the user's profile.
  Look for roles that include authorization objects related to configuration and shared tables.
  
  
  
  Modify Authorizations:
  
  If the user lacks the necessary authorizations, you may need to modify their roles or create a new role that includes the required authorizations.
  The relevant authorization objects may include:
  
  S_TCODE: Authorization for transaction codes.
  S_TABU_DIS: Authorization for table display and maintenance.
  S_TABU_CLI: Authorization for client-specific table maintenance.
  
  
  Ensure that the user has the necessary permissions to access the configuration settings for shared tables.
  
  
  
  Consult with Security Team:
  
  If you do not have the necessary permissions to modify user roles, consult with your SAP security team or administrator. They can help you identify the correct roles and authorizations needed.
  
  
  
  Testing:
  
  After making changes to the user's roles or authorizations, have the user log out and log back in to ensure that the changes take effect.
  Test the functionality again to confirm that the error has been resolved.
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  SU01: User Maintenance
  PFCG: Role Maintenance (to create or modify roles)
  SU53: Display Authorization Check (to analyze authorization issues)
  
  
  
  Documentation:
  
  Refer to SAP's official documentation or help portal for detailed information on authorization objects and their usage.
  
  
  
  Best Practices:
  
  Regularly review user roles and authorizations to ensure they align with business needs and security policies.
  Implement a change management process for role modifications to maintain system integrity and security.
  
  
  
  By following these steps, you should be able to resolve the MC787 error and ensure that the user has the necessary authorizations to configure restrictions on shared tables.