How To Fix SOI1073 - Table &1: Actual names (start/target) on database could not be saved

SOI1073 - Overview

• Message type: E = Error

• Message class: SOI1 - Safe Online Import/Upgrade Messages continued

• Message number: 073

• Message text: Table &1: Actual names (start/target) on database could not be saved

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 SOI1073 - Table &1: Actual names (start/target) on database could not be saved ?

  The SAP error message SOI1073 indicates that there is an issue with saving the actual names of a database table in the context of the SAP System Object Interface (SOI). This error typically arises during operations involving database table definitions, such as when trying to activate or transport a table.
  
  Cause:
  The error can be caused by several factors, including:
  
  
  Database Constraints: There may be constraints or restrictions on the database that prevent the saving of the actual names. This could be due to naming conventions, reserved keywords, or existing objects with the same name.
  
  
  Authorization Issues: The user executing the operation may not have the necessary authorizations to modify the database schema or save changes.
  
  
  Database Connection Issues: There could be connectivity issues with the database, preventing the system from executing the required SQL commands.
  
  
  Inconsistent State: The system might be in an inconsistent state due to previous failed operations, which could lead to issues