How To Fix AM290 - Entry missing in TSADRV; new address maintenance cannot be called

AM290 - Overview

• Message type: E = Error

• Message class: AM - Business Address Services

• Message number: 290

• Message text: Entry missing in TSADRV; new address maintenance cannot be called

What causes this issue?

The extended table maintenance (sm30) uses the (new) Business Address
Services for maintaining customizing object addresses as of Release
4.0A.
The associated entry in the Business Address Services control table
TSADRV does not exist.
A domain of the old address table is also used for the address in this
table.

System Response

The extended table maintenance calls the old address maintenance
function module. This causes errors in SAP developments.

How to fix this error?

Maintain the table TSADRV with the transaction SM30.
Make an entry for Dictionary table &V1&, Dictionary field &V2&.
Enter the address group:
All SAP customizing objects use the address group'CA01'. Make the
appropriate entry.
If it is a new development, the address number field should also refer
to the Business Address Services (AD_ADDRNUM) domains.

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 AM290 - Entry missing in TSADRV; new address maintenance cannot be called ?

  The SAP error message AM290 ("Entry missing in TSADRV; new address maintenance cannot be called") typically occurs when there is an attempt to access address maintenance functionality in SAP, but the system cannot find the necessary entries in the table TSADRV. This table is used to store address-related data for various applications in SAP.
  
  Cause:
  
  Missing Entries: The most common cause of this error is that the required entries for the address maintenance are missing from the TSADRV table. This can happen due to data inconsistencies, incomplete configuration, or if the relevant address data has not been set up properly in the system.
  Custom Development: If there are custom developments or modifications in the system that interact with address maintenance, they might not be correctly configured or might be referencing non-existent entries.
  Transport Issues: If the system has recently undergone a transport of changes, it is possible that the transport did not include the