How To Fix BA279 - Info table &2 for archiving object &1 is not recognized

BA279 - Overview

• Message type: E = Error

• Message class: BA - Data Archiving

• Message number: 279

• Message text: Info table &2 for archiving object &1 is not recognized

What causes this issue?

Table &V2& contains application-specific information on archive files
for archiving object &V1&. Table &V2& is not recognized by the system.

System Response

Archiving of management data was terminated.

How to fix this error?

If archiving object &V1& was provided by SAP, report this information
to SAP. If it is a customer-specific archiving object, check that table
&V2& exists and that you have written the name correctly. You can
correct or remove the name of the table name for archiving object &V1&
in transaction AOBJ.

Procedure for System Administrators

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message BA279 - Info table &2 for archiving object &1 is not recognized ?

  The SAP error message BA279 indicates that the system is unable to recognize the info table associated with a specific archiving object. This can occur for various reasons, and understanding the cause and finding a solution is essential for resolving the issue.
  
  Cause:
  
  Missing or Incorrect Configuration: The info table for the specified archiving object may not be properly configured in the system. This could be due to missing entries in the relevant customizing tables.
  Transport Issues: If the archiving object was transported from another system, there may have been issues during the transport that led to missing or incomplete configurations.
  Version Compatibility: The archiving object may not be compatible with the current version of the SAP system you are using.
  Authorization Issues: Lack of proper authorizations to access the info table can also lead to this error.
  
  
  Solution:
  
  
  Check Configuration: 
  
  Go to transaction code SARA and check the configuration for the archiving object in question. Ensure