How To Fix ILM_STOR813 - Copying not possible, original table &1 is not active

ILM_STOR813 - Overview

• Message type: E = Error

• Message class: ILM_STOR -

• Message number: 813

• Message text: Copying not possible, original table &1 is not active

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.

ILM_STOR813 - Details

• The SAP error message ILM_STOR813, which states "Copying not possible, original table &1 is not active," typically occurs in the context of Information Lifecycle Management (ILM) when there is an attempt to copy data from a table that is not currently active or available for processing. This can happen for various reasons, such as the table being inactive, the data being archived, or the system configuration not being set up correctly.
  
  Cause:
  
  Inactive Table: The original table referenced in the error message is not active in the system. This could be due to the table being archived or not being properly configured.
  Data Archiving: If the data has been archived, the system may not be able to access it for copying.
  
  Configuration Issues: There may be issues with the ILM configuration or the specific settings for the table in question.
  Authorization Issues: The user may not have the necessary authorizations to access the table or