Message type: E = Error
Message class: AD - Data Dictionary application messages
Message number: 387
Message text: Create a database table
The logical ABAP/4 Dictionary table was created and activated. When a
table is activated online, the corresponding database table is not
created automatically.
During transport or update, database tables are flagged automatically
for creation in the database and are created by starting a separate
program.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Create the database table using transaction SE14.
Error message extract from SAP system. Copyright SAP SE.
AD387
- Create a database table ?The SAP error message AD387 typically indicates an issue related to the creation of a database table in the ABAP Dictionary (SE11). This error can arise due to various reasons, such as incorrect table definitions, issues with database connectivity, or authorization problems. Causes of Error AD387 Incorrect Table Definition: The table may have been defined incorrectly, such as missing required fields or incorrect data types. Database Connectivity Issues: There may be issues with the connection to the underlying database, which can prevent the creation of the table. Authorization Issues: The user may not have the necessary authorizations to create database objects. Existing Table with Same Name: If a table with the same name already exists, the system will not allow the creation of a new one. Database Constraints: There may be constraints or limitations imposed by the database itself that prevent the creation of the table. Solutions to Error AD387 Check Table Definition: Go to transaction SE11 and review
Get instant SAP help. Sign up for our Free Essentials Plan.
AD386
Table type change; check whether data updates are required
What causes this issue? The table type has changed from CLUSTER to POOL. For performance reasons no check was made to see whether the cluster table c...
AD385
Table type change. Convert data
What causes this issue? The table type has changed. The table already contains data, so conversion is necessary.System Response The system issues an...
AD388
INCLUDE not allowed for tables of type VIEW
What causes this issue? You tried to insert an <DS:TX.DDDOK_UNTERSTRUKTUR>include</> in a view, but an include can only be inserted in ta...
AD389
Fields were added; modify the table dynpro
What causes this issue? During the activation process fields were added to the table. The associated table screen (MST<table name>/1000) was no...
Click on this link to search all SAP messages.