How To Fix /LIME/PI_CORE115 - Table &1 not intended for archiving

SAP Error Message - Details

• Message type: E = Error

• Message class: /LIME/PI_CORE -

• Message number: 115

• Message text: Table &1 not intended for archiving

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 /LIME/PI_CORE115 - Table &1 not intended for archiving ?

  The SAP error message /LIME/PI_CORE115 Table &1 not intended for archiving typically indicates that the specified table (denoted by &1) is not configured to support archiving in the SAP system. This can occur in various contexts, particularly when dealing with data management and archiving processes.
  
  Cause:
  
  Table Configuration: The table in question is not set up for archiving in the SAP Data Dictionary. This means that the table does not have the necessary archiving settings or indicators.
  Archiving Object: The archiving object associated with the table may not be defined or may not include the specified table.
  Custom Tables: If the table is a custom table, it may not have been designed with archiving capabilities in mind.
  
  
  Solution:
  
  
  Check Table Settings:
  
  Use transaction code SE11 (Data Dictionary) to check the properties of the table. Look for the archiving settings and ensure that the table is marked for archiving.
  
  
  
  Define Archiving Object:
  
  If the table is not intended for archiving,