How To Fix E2701 - Change from & to &; check the marking for selected databases

E2701 - Overview

• Message type: E = Error

• Message class: E2 - DE Data Dictionary

• Message number: 701

• Message text: Change from & to &; check the marking for selected databases

What causes this issue?

The table class is changed from pooled to transparent or from cluster to
transparent.

System Response

In the table marking there is reference to 'transparent on selected
databases'.

How to fix this error?

The table is always transparent on selected database systems. You can
see which ones during maintenance of the table class. On all other
database systems, the table was created thus far as a pooled or cluster
table.
Now you have to decide whether the table is to become transparent on all
databases. In this case the flag must not be set in front of the
databases in question. Reset the flag if you do not wish this. However,
if the table is to be transparent only on the selected named databases,
no further actions are necessary.

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

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 E2701 - Change from & to &; check the marking for selected databases ?

  The SAP error message E2701, which states "Change from & to &; check the marking for selected databases," typically occurs during database operations, particularly when there is an inconsistency in the marking of database objects or when changes are being made to database settings.
  
  Cause:
  
  Inconsistent Marking: The error often arises when there is a mismatch in the marking of database objects. For example, if a database object is marked for deletion or modification in one context but not in another, this inconsistency can trigger the error.
  Database 
  Configuration Issues: Changes made to the database configuration or settings that are not properly reflected across all relevant database instances can lead to this error.
  Transport Issues: If changes are transported between systems (e.g., from development to production) and the marking is not consistent, this error may occur.
  
  
  Solution:
  
  Check Database Marking: Review the marking of the database objects involved in the operation. Ensure that the marking is