How To Fix RJ059 - Database table &1 is a local object -> long text

RJ059 - Overview

• Message type: E = Error

• Message class: RJ - BW Extractor Handling Message Class

• Message number: 059

• Message text: Database table &1 is a local object -> long text

What causes this issue?

You have chosen a local table as the basis for the DataSource.
This causes problems if the DataSource is defined as a DataSource that
can be transported: when it is imported into the target system, the
transport is terminated because the missing table causes inconsistency.

System Response

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

How to fix this error?

If you want to use generated tables as the basis for DataSources, the
DataSource cannot be transported and has to be assigned to a package
that cannot be transported.
Only define DataSources that can be transported for fixed delivered
tables or tables that can be transported.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message RJ059 - Database table &1 is a local object -> long text ?

  The SAP error message RJ059 indicates that a database table is defined as a "local object." In SAP, a local object is a development object that is not transported between systems (e.g., from development to quality assurance or production). This means that the object is only available in the local system where it was created.
  
  Cause:
  The primary cause of this error is that the database table you are trying to access or use is defined as a local object. Local objects are typically created in the development environment and are not intended to be transported to other environments. This can happen if:
  
  The table was created in a local package (usually prefixed with $TMP).
  The table is not part of a transportable package.
  
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check the Package Assignment:
  
  Go to the transaction SE11 (Data Dictionary) and check the package assignment of the table.
  If the table is assigned