Do you have any question about this error?
Message type: E = Error
Message class: R7 - BW: Data basis
Message number: 860
Message text: Database table &1 was deleted and recreated
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.
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.
R7860
- Database table &1 was deleted and recreated ?The SAP error message R7860 indicates that a database table has been deleted and then recreated. This situation can arise due to various reasons, such as changes in the data model, updates to the application, or manual interventions in the database.
Cause:
- Data Model Changes: Changes in the application or data model may require the deletion and recreation of a table to accommodate new fields, data types, or relationships.
- Transport Issues: If a transport request containing changes to the database structure is not properly imported, it may lead to inconsistencies.
- Manual Deletion: A database administrator or developer may have manually deleted the table for maintenance or testing purposes.
- System Upgrade: During system upgrades, certain tables may be dropped and recreated as part of the upgrade process.
Solution:
- Check Transport Logs: Review the transport logs to see if there were any issues during the import of changes related to the affected table.
- Recreate the Table: If the table is essential for the application, it may need to be recreated with the correct structure. This can often be done using the Data Dictionary (SE11) or through a transport request.
- Restore from Backup: If the table contained critical data, restoring it from a backup may be necessary.
- Check for Dependencies: Ensure that any dependent objects (like views, indexes, or foreign keys) are also recreated or adjusted accordingly.
- Consult Documentation: Review any relevant documentation or release notes that may provide insight into why the table was deleted and recreated.
Related Information:
If the problem continues or if you are unsure about the steps to take, it may be beneficial to consult with SAP support or your internal SAP team for further assistance.
Get instant SAP help. Start your 7-day free trial now.
R7859
First maintain the non-cumulative parameters ("Menu Extras")
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
R7858
Non-cumulative value validity table could not be deleted
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
R7861
Database table &1 could not be deleted or recreated
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
R7862
Error when reading the DDIC objects for InfoCube &1
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.